antena

I'm trying to solve this problem too, and have been investigating for 2 months now, perhaps even more. Here are my findings. Hardware: AMD Athlon II X3 455 (Triple core 3.3 GHz) CPU AMD Radeon 7750 (7700 Series) GPU 8GB RAM Software: Arch Linux x86_64 Issue: I have the same issue. And when you say that it hangs, boy does it hang. But, I've found out that what hangs is not the whole system. Only the graphics stack, and the culprit is most assuredly fglrx driver. When it hangs, the kernel is still responsive, as you are able to SysRq+REISUB (provided you have magic sysrq enabled), or SSH into the machine and issue reboot command. To me it seems that the driver hangs at some point, and in turn stops responding to any communication from the rest of the software stack. Which is evidenced by not being able to even switch to console, which usually helps with soft driver lockups. This seems to be a hard lockup, and it seems as if driver locks up the GPU itself and is unresolvable by any normal means short of rebooting the system, which power cycles teh card, and therefore restores it's normal functionality. (When you issue the reboot command, the screen doesn't change from the KSP locked-up one until the power cycle happens and only then can I see GPUBIOS and BIOS messages). Culprit and a solution (kind-of): The de-facto culprit for these issues, as far as I am able to figure it out are AMD Catalyst drivers (duh!), specifically version 14. Once I downgraded to Catalyst 13.12 and Xorg 1.14 the problem stopped. Or to say, the problem almost stopped. It still seems to lock up once in at least 10 hours (I've encountered it only once and played ca. 10 hours since the downgrade). Downgrade instructions Update your Vi0l0 repository lines in pacman.conf to look like this (as per AMD Catalyst ArchWiki): [xorg114] Server = http://catalyst.wirephire.com/repo/xorg114/$arch [catalyst-stable-13.12] Server = http://catalyst.wirephire.com/repo/catalyst/$arch And then issue: # pacman -Syyuu The solution is a "kind of" because we all don't really run Arch in order to run older software. But AMD drivers is a special kind borked in Linux software stack, so there's that. Hello mr. sal_vager. I've been mostly lurking for quite some time, but I want to use this opportunity to thank you for your work and dedication to these issues and helping us, other players. That being said, please take note of my message here, so that you are aware the issue is not segfault or offset related, as the game doesn't actually segfalt or crap out in any way. When the lock up happens, the game is still runing, it's just that the communication between the system and GPU has ceased completely and screen isn't updating. Your links send us (Arch users) in an infinite loop between Arch Wiki and this thread :-). I've noticed that most users here are still running older (13.x) Catalyst drivers, and that might be the reason that Ubuntu and other users don't see this problem (yet!). But if I'm correct, the problem will hit all once the driver gets updated to (14.x). Again, thank you for your work and dedication. This thread has been of awesomely great help the last several months. Please correct me if Ubuntu users are using the 14 driver already without issues. It's important for me to know this and try to pinpoint the root cause of the problem as much as possible. I'd love to hear from the rest of you guys and your thoughts on this.