Mailinglist Archive: opensuse (3637 mails)
| < Previous | Next > |
Kernel 2.4.2 installation booby-traps
- From: "Paul W. Abrahams" <abrahams@xxxxxxx>
- Date: Wed, 02 May 2001 12:05:48 -0400
- Message-id: <3AF0305C.4B5ED12E@xxxxxxx>
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.
Paul Abrahams
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.
Paul Abrahams
| < Previous | Next > |