http://bugzilla.novell.com/show_bug.cgi?id=531544
User gillon_devreese@scarlet.be added comment
http://bugzilla.novell.com/show_bug.cgi?id=531544#c8
Renaud GILLON changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Info Provider|gillon_devreese@scarlet.be |
--- Comment #8 from Renaud GILLON 2009-09-19 02:19:24 MDT ---
After a week of holiday, I resumed activities on this.
I followed your advice to boot with the rescue system. I mounted all the
devices you mentionned in your comment #3, plus all other volumes I have for
'/usr', '/var', '/etc', '/home', '/tmp', '/srv', and also the partition for
'/boot'. Then I did the 'chroot'.
The mkinitrd was still complaining about missing modules
The "rpm -V kernel-default" command was giving me one line with "missing
dependencies".
So I went on to re-install the kernel-default, but as I had only a network
install CD, I had to restart all services (a matter of trial and error).
Finally I could start yast2, download the latest kernel version
(2.6.27.29-0.1-default x86_64), install it, checked that mkinitrd was happy,
rebooted and all seems now OK.
Thanks for your help, the decisive thing was the indication on how to chroot.
PS : would be nice if a kernel update left an entry in the boot menu for the
old kernel (untill next update), then it would be easier to work around a
failure of the automatic update (does this imply a lot of complication / disk
space ?).
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.