Running Quake 3 invariably locks up the computer very hard. To the point where the X log does not show anything unusual after reboot. If either LIBGL_ALWAYS_INDIRECT or R300_NO_TCL is set then the game runs fine, though it's much slower with the first option. Reproducible: Always Steps to Reproduce: 1. Run quake3 with neither LIBGL_ALWAYS_INDIRECT nor R300_NO_TCL set. Actual Results: Everything locks up anywhere under 30 seconds after running the game. My computer is an Apple PowerBook G4 15" with a Radeon Mobility 9600 M10 chip.
This isn't a game bug. If an X application can lock up your system it's usually a driver issue.
Thanks for the quick response! First off, maybe this information is useful to you in terms of unmasking Quake 3 for PPC. Secondly, should this then go to the Gentoo people in charge of drivers or straight to the Xorg people?
Hello, which xorg-driver package do you use? Michael
This is from the output of ``emerge --info xorg-drivers'': x11-base/xorg-drivers-1.9 was built with the following: USE="" INPUT_DEVICES="evdev keyboard mouse synaptics -acecad -aiptek -elographics -fpit -joystick -penmount -tslib -virtualbox -vmmouse -void -wacom" VIDEO_CARDS="fbdev radeon -apm -ark -ast -chips -cirrus -dummy -epson -fglrx -geode -glint -i128 -i740 -impact -intel -mach64 -mga -neomagic -newport -nouveau -nv (-nvidia) -r128 -rendition -s3 -s3virge -savage -siliconmotion -sis -sisusb -sunbw2 -suncg14 -suncg3 -suncg6 -sunffb -sunleo -suntcx -tdfx -tga -trident -tseng -v4l -vesa -via -virtualbox -vmware -voodoo -xgi"
emerge --info please
You didn't post your `emerge --info' output or `lsmod' output. Since it still isn't clear if in fact you are using the VIDEO_CARDS=radeon driver (x11-drivers/xf86-video-ati) or the other one (x11-drivers/ati-drivers), one of which might be causing the problem. Also, run an sshd service and see if you can still access the system after the crash - for all we know it could be an X server problem unrelated to the kernel. And we dont know anything yet about your X server. The problem might well turn out to be in quake3 itself after all, but since we don't have a proper bug report right now, it's hard to tell anything for sure. Why don't you first try to figure out what the actual bug is you're trying to report, and then reopen this bug report with all the required information (emerge --info, for instance), as well as the necessary information to identify the bug uniquely. You could use our <http://forums.gentoo.org/> web forums for that purpose, or more directly chat about the issue you're not seeing yet at <irc://chat.freenode.net/#gentoo>, our IRC channel.
