Jack Malone wrote:
At 12:05 PM 5/2/2001 -0400, you wrote:
I've finally managed to get the 2.4.2 kernel installation working (except for the network card -- I'll describe that in a different post). But it took a long time. The problem I encountered was that the new kernel couldn't locate most of the modules it needed, or so it seemed, even though I had installed the newer modutils package.
It turned out that the problem was that I was still booting the default kernel, named "linux". With "uname -a" I discovered that I was still running the 2.4.0 kernel, not the 2.4.2 kernel, so I had a kernel version mismatch. The repair was to rejigger my /etc/lilo.conf file so that the default linux kernel would be the new one. I also put some symlinks in /boot so that I didn't have to rename too many vmlinux.xxx files and thereby lose track of which was which. After these fixed I reran lilo, and aside from the networking problem the problem is solved.
Just wondering, did you use the rpm's from the suse ftp site for 2.4.2 kernel. I just did this last week an after using yast to install the kernel an new module rpm's i ran lilo an exited out of lilo. I did not make any changes just ran it. then rebooted an off it went. I'm just wondering is all. all works with network support an all.
I did use the rpms from the SuSE website (k_deft-2.4.2-something-or-other.rpm and modutils.rpm) and installed them using rpm -U as recommended on the website (page entitled "Updating your kernel using RPM packages"). But I also tried doing it with Yast1 earlier and had no better results. Didn't do the uname -a check the first time, though. Paul Abrahams