godot
01-17-2001, 04:46 PM
I'm using debian with 2.2.17 kernel.
I compiled 2.4, worked great. Problems arose when i edited lilo.conf and rebooted.
Debian is a little different from the NFH here, lilo.conf boots from /vmlinuz with is a link to /boot/vmlinuz-2.2.17 on my machine. I made a new link /vmlinuz.old pointing to /boot/vmlinuz-2.2.17 then made a new /vmlinuz pointing to my new compiled kernel /boot/vmlinuz-2.4.0. The system maps were also somewhat confusing. The old one is /boot/system.map-2.2.17 so i copied the new one to system.map-2.4.0. Is that a problem, how are they read since there's nothing related to it in lilo.conf? I had two boot options, Linux and old, old pointed to /vmlinuz.old and Linux to /vmlinuz. I also noticed that the compiled 2.4 kernel wasn't executable but the 2.2.17 kernel was, so chmod +x vmlinuz-2.4.0. When I rebooted it started loading linux, said it was loading the kernel and just stopped. Can anyone see where i went wrong?
I compiled 2.4, worked great. Problems arose when i edited lilo.conf and rebooted.
Debian is a little different from the NFH here, lilo.conf boots from /vmlinuz with is a link to /boot/vmlinuz-2.2.17 on my machine. I made a new link /vmlinuz.old pointing to /boot/vmlinuz-2.2.17 then made a new /vmlinuz pointing to my new compiled kernel /boot/vmlinuz-2.4.0. The system maps were also somewhat confusing. The old one is /boot/system.map-2.2.17 so i copied the new one to system.map-2.4.0. Is that a problem, how are they read since there's nothing related to it in lilo.conf? I had two boot options, Linux and old, old pointed to /vmlinuz.old and Linux to /vmlinuz. I also noticed that the compiled 2.4 kernel wasn't executable but the 2.2.17 kernel was, so chmod +x vmlinuz-2.4.0. When I rebooted it started loading linux, said it was loading the kernel and just stopped. Can anyone see where i went wrong?