Ok,
First, *NEVER* overwrite your old kernel, until you have tested the new
one at least. Imagine what could havppen if you accidentally forget a
driver you need to boot your system, and you overwrote your old kernel?
Second, You did run LILO again, didn't you? You must run lilo every time
you make any changes to your boot configuration so that they take effect.
If you overwrote your old kernel, but did't tell LILO to boot from the new
one, you ARE asking for trouble. Just run "lilo" as root and reboot your
system.
You did reboot the system, didn't you?
Hope this helps,
Victor R. Rivarola
[EMAIL PROTECTED]
These words are mine only, and not my employer's.
On Sat, 9 May 1998, David Rice wrote:
> Well, i run kernel 2.0.33 and i have booted with this new kernel seeing
> as how /usr/src/linux/arch/ie86/boot/zImage was copied to /vmlinuz and
> lilo.conf looks at /vmlinuz to boot. So i have no idea whats going
> on...im reall very unhappy with this. i *need* it to play starcraft!!!
> hehehe. Please if someone has some info or a step by step way on how to
> get it working would be great. Maybe im missing a step or something.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> For daily digest info, email [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]
