Did you rerun lilo?
On 9 Mar 2001, Arkaitz wrote:
>Hi,
>
>I used kernel-package to build a new 2.4.2 kernel package for my woody
>machine, and installed it ok. The problem is that if I do "uname -r", it
>still says that the kernel version is 2.2.17.
>I think everything is configured ok, in lilo.
Thanks to all that answered!
The problem was that lilo was writing the new config to a partition
while the computer was using the MBR to boot. Anyway, the machine
running woody is actually VMware, and I get no problem with kernel
2.2.17, but it does a "kernel panic" when trying to mount the root
fi
On Fri, Mar 09, 2001 at 07:51:28PM +0100, Arkaitz wrote:
> I used kernel-package to build a new 2.4.2 kernel package for my woody
> machine, and installed it ok. The problem is that if I do "uname -r", it
> still says that the kernel version is 2.2.17.
> I think everything is configured ok, in lilo
Arkaitz <[EMAIL PROTECTED]> writes:
> I used kernel-package to build a new 2.4.2 kernel package for my
> woody machine, and installed it ok. The problem is that if I do
> "uname -r", it still says that the kernel version is 2.2.17. I
> think everything is configured ok, in lilo.conf the default /
Hi,
I used kernel-package to build a new 2.4.2 kernel package for my woody
machine, and installed it ok. The problem is that if I do "uname -r", it
still says that the kernel version is 2.2.17.
I think everything is configured ok, in lilo.conf the default /vmlinuz
image is a link to the 2.4.2 imag
5 matches
Mail list logo
