On Sat, May 24, 2008 at 3:52 PM, Steve <zephod@xxxxxxxxxx> wrote: > > ---- "Antti J. Huhtala" <ahuhtal4@xxxxxxxxx> wrote: >> pe, 2008-05-23 kello 05:47 +0300, Antti J. Huhtala kirjoitti: >> > to, 2008-05-22 kello 19:15 -0400, slamp slamp kirjoitti: >> > > Please help. PC stuck in grub> prompt. >> > > >> > The latest kernel update 2.6.25.3-18.fc9 - or one of the 199 files >> > updated at the same time - rewrote grub.conf so that (in my case) the >> > line which should have read: >> > >> > kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00 >> > rhgb quiet >> > >> > actually read: >> > >> > kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro >> > root=UUID=ab562fb5-0a9a-4458-9f30-61c8a23f774a rhgb quiet >> > >> > Somehow my /dev/VolGroup... had been changed to UUID=... >> > >> > The same error had been applied to the previous kernel (2.6.25-14.fc9) >> > so that neither would boot. >> > >> Bugzilla # 448132. > > I have the same problem except that correcting my grub.conf file did not help. I'm still stuck with just GRUB showing on the screen. Also I did not get any sounds. > > Any futher suggestions? > > Steve > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > well my issue was either fedora or grub not being able work well with "fakeraid". anything i tried nothing helped. i reinstalled grub to the right fakeraid device and it did not help. so what i did was deleted the "fakeraid" from intel bios and just did a software raid (mdadm). this works better than dmraid and grub or fedora seems to properly use the /dev/md* device. "fakeraid" sucks, too bad i did not catch this when i bought my pc (powerspec e361). -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
