Re: New kernels do not work.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



su, 2008-05-25 kello 10:51 -0400, Steve kirjoitti:
> ---- "Antti J. Huhtala" <ahuhtal4@xxxxxxxxx> wrote: 
> > la, 2008-05-24 kello 15:52 -0400, Steve kirjoitti:
> > > ---- "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?
> > > 
> > Sorry, looking back at my cryptic hand-written notes I realize I forgot
> > to mention that I ran 'grub-install' before editing grub.conf. On the
> > basis of time-stamps of the files in /boot/grub, almost all files were
> > rewritten but grub.conf was not. My notes don't record whether I tried
> > rebooting after running grub-install but IIRC I probably did. I seem to
> > recollect that I was still stuck at "GRUB".
> > Therefore I edited grub.conf and tried again. This time reboot worked
> > for me so I didn't delve into it further.
> > Whether the real remedy was running grub-install or editing grub.conf
> > *or both*, I don't know. The fact remains I'm typing this with 'fully'
> > operational F9 system.
> > > Steve
> > Antti
> > 
> ...and I should have added in my note that after I edited grub.conf, rebooted and I was still stuck with just GRUB on the screen, that I re-installed grub from the DVD while in rescue mode and then rebooted again. No luck - still just GRUB. At this point I think my next move may be to do a complete re-install. <Sigh!>
> 
OK, let's be precise here. I did *not* reinstall grub from the DVD but
ran /sbin/grub-install script on my hard disk already. I used the DVD
"Rescue" option only to get to the "sh-3.2#" prompt.
Here's exactly what I did:

1) *Upgraded* my existing F8 using F9 DVD. After the _upgrade_
installation was over I rebooted and had a working F9 - of sorts. (My
printer didnt work, I couldn't mount my NTFS partitions, totem-xine
wouldn't show my movies, etc. - but that's another story.)
2) F9 PackageKit informed me that 199 packages needed updating and 15
packages needed installing, and I okayed that. Update was not successful
however, because of long list of conflicts. I couldn't see all of them,
so I
3) Tried 'yum update' which of course failed likewise, but now I could
see that the conflicts were caused only by two packages left from F8:
gnome-panel-2.20.3-1.fc8.i386 and gnome-applets-2.20.1-1.fc8.i386 (mine
is an x86_64 box). I 'yum remove'd those two packages and after that
successfully updated 199 packages and installed 15.
4) Because one of the 15 installed packages was kernel 2.6.26.3-18, I
rebooted the box. That's when booting stopped at "GRUB".
5) Did some googling with another (Centos 5.1) box to find advice. Armed
with this info I booted the non-working box with F9 DVD and chose
"Rescue".
6) Went to /boot/grub/ and ran grub-install (from /sbin on my HD).
7) Tried booting the box but it again stopped at "GRUB".
8) Booted the box with F9 DVD and again went to /boot/grub directory.
9) Started "vi grub.conf" and replaced the UUIDs on two 'kernel' lines
with VolGroup00/LogVol00 (my Linux LVM).
10) Rebooted successfully to F9.

HTH, Antti


-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux