Can't boot new Linux kernel 2.6
 

With the help of a more Linux-savvy friend, I am currently running Debian Linux 2.4.18. He decided I needed to upgrade to 2.6 in order to get all my hardware working properly, and since he had work to do elsewhere in SSHed into my computer and did all the kernel compiling work for me. He left me with a Debian package which I dpkged and whatnot. I think it modified lilo.conf for me but I don't remember. Anyway, I rebooted and selected Linux from the LILO menu (LinuxOld was there, so yes lilo.conf was configured) and when it got to line "Uncompressing linux.......ok booting the kernel" it just sat there. Later he tried to use Apt-Get which not only produced the same result as before but messed with my lilo.conf so that I had to do a rescue with the CD to get the original kernel back. Today I just tried compiling the kernel myself and setting everything up manually via instructions I found on the web for general kernel compiling and installation. Well that also led to the same result. So I guess my question now is what could I possibly be doing wrong?

check this site out as it tells u how to compile the "debian way" :
http://www.desktop-linux.net/debkernel.htm

It doesn't help. I've compiled the kernel at least 6 times now and none of them make a difference. It always stops at "Uncompressing Linux... Ok, botting the kernel." Since there's no error message I'm not sure what the problem is.

youve obviously compiled it for a different model processor.

Compile one made to work ona a 386 processor, I bet itll work then.

this can be found using make menuconfig

under Processor Family.

I've got an Athlon, and that's what I selected.

Do you have an nforce2 motherboard? Thats what I have and I get that all the time when I try to install new distros. I blame it on that because I can't think of anything else to blame it on. (except myself)

Still haven't figured out how to fix it.

I must have compiled Gentoo about as many times as you have, but every time it stuck there. Never figured out what was wrong.

So if anyone else has any suggestions I also would like to hear them.

No, it's an ASUS. I keep forgetting the model number, but I got it last year when it was pretty new.