On Thu, 16 Sep 2004, Henrik Grevelund wrote:
> Hi There
>
> uname -r
> does answer: 2.4.20-8 the old kernel
>
> I do not use grup or lilo. I start on a boot disk. Its running under
> vmware and has a partition on the disk, so a had to start it with a
> (virtuel)disk.
>
> The hd partition hasn't changed. And i don't se anything else on the
> boot disk that could point to the old kernel.
>
> where does uname get the kernel version from ?
>
I imagine it gets the kernel version from the running kernel, and I'll
bet it gets it from the kernel by looking in /proc/sys/kernel/osrelease.
If you're feeling daring, you could try
echo 2.4.20-31.9 > /proc/sys/kernel/osrelease
> Henrik
>
>
> -----Oprindelig meddelelse-----
> Fra: Steven J. Yellin [mailto:yellin@xxxxxxxxxxxxxxxxx]
> Sendt: 16. september 2004 20:57
> Til: Discussion of Red Hat Linux 9 (Shrike)
> Emne: Re: SV: After an update som modules points to the old kernel
>
> Does "uname -r" show you to be running 2.4.20-8? If so, you should
> figure out how you got to be running a different kernel from what's in
> /boot. If, for example, you use grub, maybe grub.conf points to the
> wrong partition for its kernel.
>
> On Thu, 16 Sep 2004, Henrik Grevelund wrote:
>
> > Hi Michael
> >
> > depmod -ae says:
> > depmod: Can't open /lib/modules/2.4.20-8/modules.dep
> >
> > /boot
> > Contains:
> > config-2.4.20-31.9
> > config-2.4.20-31.9smp
> >
> > initrd-2.4.20-31.9.img
> > initrd-2.4.20-31.9smb.img
> >
> > module-info-2.4.20-31.9
> > module-info-2.4.20-31.9smp
> > module-info -> module-info-2.4.20-31.9
> >
> > system.map-2.4.20-31.9
> > system.map-2.4.20-31.9smp
> > system.map -> system.map-2.4.20-31.9
> >
> > vmlinux-2.4.20-31.9
> > vmlinux-2.4.20-31.9smp
> >
> > vmlinuz-2.4.20-31.9
> > vmlinuz-2.4.20-31.9smp
> > vmlinuz -> vmlinuz-2.4.20-31.9
> >
> > boot.b
> > chain.b
> > grub
> > kernel.h
> > message
> > message.ja
> > os2_d.b
> >
> >
> > /lib/modules
> > contains 2 dirs:
> > 2.4.20-31.9
> > 2.4.20-31.9smp
> >
> > What does the smart man do ?
> >
> >
> > Henrik
> >
> >
> > -----Oprindelig meddelelse-----
> > Fra: Michael Schwendt [mailto:fedora@xxxxxxxxxxxxxxxxx]
> > Sendt: 15. september 2004 07:23
> > Til: Discussion of Red Hat Linux 9 (Shrike)
> > Emne: Re: After an update som modules points to the old kernel
> >
> > On Tue, 14 Sep 2004 21:33:03 +0200, Henrik Grevelund wrote:
> >
> > > I just downloaded all the updates for the RH9 and the i runned:
> > > rpm -Fhv *.rpm
> > >
> > > That was including the kernel upgrade. Now i have no cdrom and
> > network.
> > >
> > > /var/log/messages:
> > > server modprobe: modprobe: Can't open dependencies file
> > > /lib/modules/2.4.20-8/modules.dep (No such file or directory)
> > >
> > > how come this didn't get updated, and how do i correct this.
> >
> > With the new kernel running, run "depmod -ae" as root user.
> > What do /boot and /lib/modules look like?
> >
> > --
> > Fedora Core release 2 (Tettnang) - Linux 2.6.7-1.494.2.2
> > loadavg: 1.01 0.98 0.67
> >
> >
> >
>
> --
> Steven Yellin
>
>
>
--
Steven Yellin
--
Shrike-list mailing list
Shrike-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/shrike-list
