kernel install/compile problems

[fataldreams]

I've got linux running on two different systems, a laptop and my desktop (which runs as a dual boot with Windows 98). I've been trying to install and compile kernel 2.4.18 on my desktop for quite awhile, and keep running into problems. This afternoon I decided to try and do it on the laptop, and everything ran perfectly smooth (though it took quite awhile on a Pentium 133). Same distribution (Slackware 8), and I did everything exactly the same, with the exception of the obvious like not adding usb support for a laptop that doesn't have usb, while adding it for the desktop which does, etc. With the desktop, I get to copying my new kernel, named vmlinuz-2.4.18, to the /boot directory so that I can then add it to lilo.conf and it stops giving me a command prompt. Just sits there with a cursor on an otherwise blank line.

Any ideas?

Thanks.
Jennifer

 

[Tiger]

What's your command look like?

cp vmlinuz-2.4.18 /boot/vmlinuz-2.4.18

 

[fataldreams]

cp bzImage /boot/vmlinuz-2.4.18

With appropriate directory, with me I've got the unpacked kernel source under /, so /kernel/linux/arch/i386/bzImage I believe.

 

[slackware1995]

After you do a "make bZimage" do a "make install" and it'll copy your new kernel image and install it with lilo.

Hope that helps.

 

[fataldreams]

Thanks, I'll give it a shot later tonight and see what happens.

Still, the thing that I don't understand is that I'm not doing anything different at all as far as commands go, when I cp bzImage to /boot/vmlinuz-2.4.18 on the laptop it copies in just a few seconds, I added it to lilo.conf and tested it, all works perfectly. I cp bzImage to /boot/vmlinuz-2.4.18 on the desktop and it sits there acting like it's doing something but I've let it sit for quite sometime and nothing happens, plus there is no disk activity.

Anyway, thanks again.
Jennifer

 

[slackware1995]

Is your /boot on a small partition (ie out of disk space?). Just a thought.

 

[cleverhandle]

Weird. Your commands are fine. And cp should give an error message if there's insufficient space. Perhaps the original bzImage got corrupted? I would think the compile would've choked if there were a disk error, but you never know. Given that the laptop is a pretty old machine, it seems possible.

 

[slackware1995]

Glad I could help