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

Re: kernel update problem



Hi,

     You need to run lilo, the rpm installation doesn't do that.  I think
you can get awaywith leaving /boot/vmlinuz in your lilo.conf.  If not,
change it to vmlinuz-2.4.1-0.1.14 and rerun lilo.





          HTH.
          Bill in Denver


On Thu, 1 Mar 2001, Mate Wierdl wrote:

> I had a problem with my wolverine installation, and then running the
> system: my netgear card on my Athlon (600MHz)  system is using the
> tulip driver, and somehow I can connect to remote boxes using IP
> numbers only (even during installation, I had to use IP numbers to
> specify the ftp server with wolverine on it).  Since I am using static
> IP, this problem was unexpected.  Nevertheless, I got a hint that the
> kernel package in rawhide fixes the problem.
>
> So I installed the kernel-2.4.1-0.1.14 rpm (rpm -Uvh in single user
> mode).  But even after rebooting, it seems that the important players
> still think that I have kernel-2.4.1-0.1.9:
>
> modprobe, depmod are looking for stuff in /lib/modules/2.4.1-0.1.9.
>
> # cat /proc/version
> Linux version 2.4.1-0.1.9 (root porky devel redhat com) (gcc version
> 2.96 20000731 (Red Hat Linux 7.1 2.96-75)) #1 Thu Feb 22 23:36:02 EST 2001
>
> # cat /etc/issue
>
> Red Hat Linux release 7.0.91 (Wolverine)
> Kernel 2.4.1-0.1.9 on an i686
>
>
> Can anybody tell me what to change (I know how to change /etc/issue,
> but not the others).
>
> In /etc/lilo.conf, I have
>
> # cat /etc/lilo.conf
> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
> prompt
> timeout=50
> message=/boot/message
> linear
> default=linux
>
> image=/boot/vmlinuz
> 	label=linux
> 	read-only
> 	root=/dev/hdb1
>
> and
>
> # ls -l /boot/
> total 3444
> -rw-r--r--    1 root     root          512 Feb 20 16:11 boot.0300
> -rw-r--r--    1 root     root         5824 Jan 12 09:26 boot.b
> -rw-r--r--    1 root     root          612 Jan 12 09:26 chain.b
> lrwxrwxrwx    1 root     root           14 Feb 28 16:16 kernel.h ->
> kernel.h-2.4.1
> -rw-r--r--    1 root     root            0 Feb 28 16:16 kernel.h-2.4.1
> -rw-------    1 root     root        12288 Feb 28 16:38 map
> -rw-r--r--    1 root     root        23108 Jan 12 09:26 message
> lrwxrwxrwx    1 root     root           24 Feb 28 16:15 module-info ->
> module-info-2.4.1-0.1.14
> -rw-r--r--    1 root     root        13598 Feb 22 22:51
> module-info-2.4.1-0.1.14-rw-r--r--    1 root     root          640 Jan
> 12 09:26 os2_d.b
> lrwxrwxrwx    1 root     root           23 Mar  1 08:55 System.map ->
> System.map-2.4.1-0.1.14
> -rw-r--r--    1 root     root       409138 Feb 22 22:51
> System.map-2.4.1-0.1.14
> -rwxr-xr-x    1 root     root      2245484 Feb 22 22:51
> vmlinux-2.4.1-0.1.14
> lrwxrwxrwx    1 root     root           20 Feb 28 16:15 vmlinuz ->
> vmlinuz-2.4.1-0.1.14
> -rw-r--r--    1 root     root       778224 Feb 22 22:51
> vmlinuz-2.4.1-0.1.14
>
> and it is weird that kernel.h-2.4.1 is a 0 length file.
>
> Thx
>
> Mate
>




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