Description of problem: My F9 system fails to start up unless I remove rhgb in /etc/grub.conf. Version-Release number of selected component (if applicable): rhgb-9.0.0-6.fc9.i386 How reproducible: Every time Steps to Reproduce: 1. Start system. Actual results: After the message "Starting udev [OK]" the screen goes blank. Sometimes it enters powersave, sometimes not. Sometimes I briefly see the default X mouse cursor. There is no further disk activity after this. Expected results: System to start normally. Additional info: system-config-display reports my adapter as an "Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device". This may be a dupe of "442492: i686 LiveCD only succeeds if rhgb is omitted".
Further info: I have an FC5 partition on the same machine for which rhgb works fine. Also, rhgb was working fine when I first installed F9, unfortunately I can't put my finger on how long ago it broke.
Leon: Which pre F9 version did you install ? Where any updates applied to it at all before you saw the error ?
I installed Fedora 9 Beta from the DVD ISO. I then applied updates in the normal way, i.e. when I got the icon in the top right of the GNOME desktop prompting me that updates were available. So yes, I've applied many updates.
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I'm seeing the same issue since upgrading (with yum) from updated F9 to current rawhide. I can't boot kernel 2.6.27 at all, because after removing 'rhgb' from the boot command, the X server still seems to be started early in the boot process, and from there on the screen stays black. If I go back to 2.6.25.14-108.fc9.i686 and boot without rhgb, gdm comes up normally. ThinkPad T43, kernel-2.6.27-0.323.rc6.fc10.i686, xorg-x11-server-common-1.5.0-6.fc10.i386, plymouth-0.6.0-0.2008.09.10.1.fc10.i386
what if you add nomodeset to the grub kernel commandline ?
(In reply to comment #6) > what if you add nomodeset to the grub kernel commandline ? I get a text-mode screen with a white progress-type bar at the bottom, with light and dark blue blocks to its right, and then a normal gdm screen. Thanks for the suggestion! BTW: that's with kernel-2.6.27-0.323.rc6.fc10.i686.
(In reply to comment #7) > (In reply to comment #6) > > what if you add nomodeset to the grub kernel commandline ? > > I get a text-mode screen with a white progress-type bar at the bottom, with > light and dark blue blocks to its right, and then a normal gdm screen. Thanks > for the suggestion! BTW: that's with kernel-2.6.27-0.323.rc6.fc10.i686. ...and if I also remove 'rhgb', I get a normal text-mode boot--well, almost: the cursor jumps to the top of the screen after the first few lines, and overwrites those lines, but otherwise a normal boot.
reassigning to kernel
Kernel kernel-2.6.27-0.352.rc7.git1.fc10.i686 boots fine without nomodeset, both with and without rhgb--thanks!
Actually, this bug changed into something else. Now it is apparently duplicate of bug 462980. Closing. *** This bug has been marked as a duplicate of bug 462980 ***
*** This bug has been marked as a duplicate of bug 464896 ***