2.6.7 Kernel w/ fglrx 3.9.0 causes system hang when switching out of X?
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
2.6.7 Kernel w/ fglrx 3.9.0 causes system hang when switching out of X?
I don't know why, but for me, whenever I use the 2.6.6 or 2.6.7 kernel and I try to close X (xorg) when I'm using the fglrx module, my system just hangs. If I issue "reboot" or click on Quit from XFce4, the screen just goes black, and if I do ctrl+alt+backspace I get white bars going horizontally across the screen. the 2.4.22 kernel seems to display and function properly, but I'm having troubles with getting the USB mouse to work with it, and I'd rather use the 2.6.x kernel because of the updates. I'm using Slackware-current, which SHOULD be 10.0 right now (Swaret craps out on me on the last check when I do swaret --update). Does anyone know what I can/should do? Would it just be best to do a fresh install from the Slackware 10.0 disks?
I had the same problem when i first compiled 2.6.7 under slackware 10. I had to uncheck use 4k stacks in the kernel hacking menu. I use NVIDIA drivers which require the use of 8k stacks. By default kernel 2.6.7 check use 4k stacks. Maybe you could check into that. It worked for me.
Originally posted by EdwardA I had the same problem when i first compiled 2.6.7 under slackware 10. I had to uncheck use 4k stacks in the kernel hacking menu. I use NVIDIA drivers which require the use of 8k stacks. By default kernel 2.6.7 check use 4k stacks. Maybe you could check into that. It worked for me.
Hope that helps.
Will do as soon as I can. How'd you come across that solution, by the way?
Unchecking the 4k stacks didn't do anything. Whenever I exit X, the monitor goes into the powersaving mode and the system hangs. This means that I can't properly shut it off, and this is beginning to be a real pain. I guess this means that I'll have to use the standard drivers that come with X (ati), and I guess that also means no gaming
I have a feeling that this has something to do with my display settings with xorg.conf. I'm having very similar problems compared to this guy http://www.nvnews.net/vbulletin/showthread.php?t=29783 and he says his problem has to do with TVOut. I'll try playing around some more with xorg.conf and the display settings. If anyone can help, it would mean a lot.
Last edited by r_jensen11; 06-28-2004 at 12:03 PM.
Well, I'm using a Radeon 8500, the lowest you can go while still getting official ATI drivers. I don't know, though. It definately is the drivers, not X, I know that because when I use X's own drivers, it works fine, just can't do 3D stuff at any decent rate. Maybe I will go down to the 2.4 kernel. I'll have to see if there's any true reason why I should stick with the 2.6 series for now.
I don't know about the downgrading kernels, now.... I don't really think it's a KERNEL problem, but more of a settings problem with X. Like I said, it works fine while IN X, it's just when anything wants to kill X that the system hangs....
I'm thinking I'm going to just have to do my Unreal Tourny 2k3/2k4 demo gaming in Windows instead of Linux... I guess I'll have to get used to rebooting every time I switch a map....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.