I have an IBM P4 system which actually has Gentoo 2005.1 loaded on it, dual booted with Windows. I just got the 2006.0 LiveCD last night. It boots fine on at least one other machine and comes up in the desktop, but this particular system is failing to start X when booting the 2006.0 LiveCD. I captured "lspci", "lsmod", "xorg.conf", "/var/log/messages" and "Xorg.0.log" from both the working Gentoo install (suffix ".working") and from the failed boot of the 2006.0 LiveCD (suffix ".livecd"). All of these are in the attached tarball. If there's anything else you want me to capture, either on the working system or with the LiveCD, let me know.
Created attachment 81003 [details] Tarball of log files Log files from both working Gentoo install and LiveCD boot that fails to start X. Suffix ".working" is the working install and ".livecd" is from the LiveCD boot that won't come up in X.
A couple things I forgot to say: 1. The machine where the LiveCD fails has two CD-ROM drives. Both behave the same way. 2. I tried booting both "gentoo" and "gentoo-nofb". Both fail the same way. I have now booted the same LiveCD on two more machines successfully, although one did require "gentoo-nofb" to boot up. Both came up in the desktop. It's just that one IBM P4 that seems to have problems. Since it already has a working Gentoo installed the old-fashioned way, it's not at all urgent that this gets solved for me.
How much video RAM is allocated in the BIOS? Is it 8MB?
I have the same issue, here are my specs on my system: Mobo/Chipset: Gigabyte GA-K8U Socket 754 ULi M1689 Proc: AMD Sempron 2800+ Video: Nvidia GeForce 5200
(In reply to comment #3) > How much video RAM is allocated in the BIOS? Is it 8MB? > I've lost access to the system. It was a leased unit, and the IT folks reclaimed it and sold it. Gentoo runs just fine on the new one, including the LiveCD.
Ryan, I can guarantee you that your issue will be independent of the cause of this one, as the IBM machines don't use NVIDIA cards. If you're willing to provide more information and testing for me, then please file a bug of your own. I'm marking this one as CANTFIX since the original bug poster no longer has access to the hardware.
