Strange problems when upgrading kernel
Alexandre Strube
surak at surak.eti.br
Sat Jan 10 22:41:39 UTC 2004
Em Sáb, 2004-01-10 às 12:31, ne... escreveu:
> On Jan 10, 2004 at 04:19, Alexandre Strube in a soothing rage wrote:
:-)
> >VFS: Cannot open root device "LABEL=/" or 00:00
> >Please append a correct "root=" boot option
> >Kernel Panic: VFS: Unable to mount root fs on 00:00
> In the past, this has been a sign of a bad mkinitrd. I use
> mkinitrd-3.5.17-1. You may need mkinitrd-3.5.14 or mkinitrd-3.5.15.
I managed to make it work changing the line on grub.conf, now it is
kernel /vmlinuz-2.4.22-1.2140.nptl ro root=/dev/hda2 hdc=ide-scsi rhgb
^^^^^^^^
this did the trick.
I'm using mkinitrd-3.5.16.1-1
I couldn't see how does this work, anyway.
> >Sound is gone also. I was using ALSA, but now this happens:
> >[root at casa archives]# modprobe snd-via82xx;modprobe snd-pcm-oss;modprobe
> >snd-mixer-oss;modprobe snd-seq-oss
> >/lib/modules/2.4.22-1.2140.nptl/kernel/sound/snd.o: unresolved symbol
> >schedule_work
> Get the updated rpms from freshrpms. For each kernel upgrade you do,
> you need to update the kernel-alsa rpms as well.
The file was there - I always upgrade kernel-module-alsa together with
kernel rpm. Today there was a alsa-driver update, and it begun to work
again.
Thanks for your reply!
--
[]s
Alexandre Ganso
500 FOUR vermelha - Diretor Steel Goose Moto Group
More information about the fedora-list
mailing list