On Sat, 4 Feb 2006 21:41:58 +0100 "Steven F. Christ" <fedora-core-list@xxxxxxxx> wrote: > On Sat, 4 Feb 2006 11:39:41 -0800 > Kam Leo <kam.leo@xxxxxxxxx> wrote: > > > On 2/4/06, Ernest <kong_an563@xxxxxxxxx> wrote: > > > New Kernel image 2.6.15-1.1830_FC4 > > > is causing problems with gdm. > > > > > > After boot: > > > the kernel is running, but gdm has crashed at the point where a > > > user login screen should appear. > > > All that appears is a blue background speckled with white dots. > > > It might be that gdm has not crashed, but the boot process has > > > left something in an incompatible state. > > > > > > It is possible to login to this machine, from another desktop, > > > using ssh. Once logged onto the fedora system and issuing the > > > command "gdm-restart", the gdm user login screen appears on the > > > fedora system console. > > > > > > What has changed between 2.6.15-1.1830_FC4 > > > and 2.6.14-1.1656.FC4? > > > > > > Where do I start? > > > What information is needed? > > > > > > System is an older Gateway PIII, 384MB RAM, ATI Radeon graphics > > > card in the AGP slot. > > > X.org detects and configures this video card properly. The > > > earlier kernel worked fine, until the system was booted with > > > kernel 2.6.15-1. Now kernel 2.6.14-1 exhibits the same problem. > > > > > > > Your problem was answered in this thread "Issues with kernel 2.6.15 > > and other updates this morning". Go to > > http://www.redhat.com/archives/fedora-test-list/2006-February/msg00179.html > > for more information, then get this file > > http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/4/module-init-tools-3.2-0.pre9.0.FC4.1.i386.rpm > > .and update modules-init-tools. > > > After updating module-init-tools there seems to be a problem with the > grapgic driver for the ati radeon 9800 (fglrx). see syslog.. > > ---------------------------------------------- > Bad page state at free_hot_cold_page (in process 'X', page c193ac14) > flags:0x80000414 mapping:00000000 mapcount:0 count:0 (Tainted: P ) > Backtrace: > Trying to fix it up, but a reboot is needed > [fglrx] Kernel AGP support doesn't provide agplock functionality. > [fglrx] AGP detected, AgpState = 0x1f004a1b (hardware caps of > chipset) agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0. > agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode > agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode > [fglrx] AGP enabled, AgpCommand = 0x1f004312 (selected caps) > Bad page state at free_hot_cold_page (in process 'X', page c193ac14) > flags:0x80000414 mapping:00000000 mapcount:0 count:0 (Tainted: P ) > Backtrace: > [<c014d91e>] bad_page+0x8c/0xc3 [<c014e21c>] > free_hot_cold_page+0x3a/0x126 > [<c014ea24>] __pagevec_free+0x1f/0x2e [<c01541e0>] > release_pages+0x119/0x194 > [<c0161665>] free_pages_and_swap_cache+0x74/0xb6 [<c015d743>] > unmap_region+0xff/0x115 > [<c015d9c7>] do_munmap+0xb9/0xf4 [<c015da4e>] sys_munmap+0x4c/0x65 > [<c0104035>] syscall_call+0x7/0xb > Trying to fix it up, but a reboot is needed > ---------------------------------------------- > > after that, the system is freezing again! > ok, helped my self out, livna is on the road... http://bugzilla.livna.org/show_bug.cgi?id=760 sfc