Results 1 to 8 of 8
Hi, i have compiled kernel-2.6.17.3 (this is not the first time ive compiled a kernel, but im pretty new to it anyway)
And it boots fine and fast, however, when ...
- 07-02-2006 #1
Kernel stuff makes xorg hang
Hi, i have compiled kernel-2.6.17.3 (this is not the first time ive compiled a kernel, but im pretty new to it anyway)
And it boots fine and fast, however, when i try and start xorg,(startx or /etc/init.d/gdm start)
it loads up, giving me a screen, with gnome splash (without any icons) and a mouse cursor.
Thats pretty much it, i can move the mouse cursor, but keyboard is totally dead, i cant even ctrl+alt+del or ctrl+alt+shift.
I can however login over ssh, and see that xorg hangs using 100% cpu.
Theres nothing in the logfiles about it...
I cant kill the process, not even with signal 9 :/
- 07-02-2006 #2
more info
by poking around a bit, it seems to hang when using
"ati" og "fglrx" drivers, but boots up fine with vesa ? now im confuzed
- 07-02-2006 #3Linux Guru
- Join Date
- Nov 2004
- Posts
- 6,110
You will most likely need to reload your ATI drivers, these generate kernel modules which are most likely incompatible with your new kernel build. Just set you xorg.conf to run X in vesa mode and go ahead and reinstall the latest proprietary ATI drivers.
- 07-02-2006 #4
Hi, thank you for your response
i just discovered that trying to run the ati driver install script also causes the system to lock up, so i might have a deeper problem somewhere :/
Also, the "ati" driver is one that comes with xorg
- 07-02-2006 #5Linux Guru
- Join Date
- Nov 2004
- Posts
- 6,110
Have you had any errors show up yet in any of your logs?
- 07-02-2006 #6
nope, no errors in logs, thogh at the very early stage of the boot, something fatal with some modules are happening, but it does not show up in dmesg and i cant halt it to get time to see what it is, but i assume it tries to load modules that are compiled into the kernell :/
- 07-03-2006 #7Just Joined!
- Join Date
- Jul 2006
- Posts
- 8
After you built your kernel, did you run "make modules" and "make modules-install"? Your current modules might not be for your current kernel.
Fernando
- 07-03-2006 #8
Hi, sorry for not updating the thread
makeing kernel the debian way makes modules too,
i found out that some bug that i dont even know if is filed in 2.6.17 is causing the problem
kernel 2.6.16.19 worked for me however.


Reply With Quote
