Xfree 4.2.0 + linux-2.4.19-lolo-r10_pre4 + Nvidia-kernel-3123 = Freeze Xfree freeze juste after trying to init the video mode. According to my tests, this doesn't seems to be related to AGP drivers (NVAGP, AGPART) or Xfree.
What desktop do you use? KDE or Gnome or something else (Flux, black -box, waimea, e16, e17 ..) This might be related to a bug (that I've submitted at least) in nvidias XRENDER implementation that makes it lock up X when AntiAliased fonts are in use, its a fresh start, and you have AGP enabled. sounds complex?
I use e16 but i tried to start X only and it's the same result. I also tried to start X without any AGP support and nothing changed. The last message in log is (II) NVIDIA(0): Setting mode "1152x864" and then X freeze and reboot my computer after 10-15 seconds.
Did you try a different kernel yet ?
Everything is fine with the linux-2.4.19-xfs-r1
preempt on in the kernels that break?
I tried with and without the preempt and it's the same result I also tried with lolo source pre5 and nothing changed.
Created attachment 4392 [details] config file for linux-2.4.19-lolo-r10_pre5 I join my .config, maybe this will help to find the problem :-)
Created attachment 4393 [details] Kernel config file I join my config file for linux-2.4.19-lolo-r10_pre5.
After having tested with differents kernel and configs, i found the bug : It's in the acpi4linux patch. The system freeze only when i use it
Truenough, fortunately the mroe recent acpi4linux patches fix the problem... try the latest lolo-sources for me.
Tolgam, are the newer kernel versions still locking up when you start X?
i'm sorry but i haven't tested it yet since my dsl connection is down i can't download any kernel source tarball
Everything works fine with new lolo sources ! :-) Here is my uname -a : Linux pen-pen.local.net 2.4.20-lolo-r1 #1 sam f
Everything works fine with new lolo sources ! :-) Here is my uname -a : Linux pen-pen.local.net 2.4.20-lolo-r1 #1 sam fév 1 12:00:57 CET 2003 i686 AMD Athlon(tm) XP 1700+ AuthenticAMD GNU/Linux
closed as per last comments that it was fixed on lolo/gentoo 2.4.20-r1