Stupid noob decided to compile his kernel... HELP!
Ok, I FINALLY got Linux working, Slackware, which was a real pain. Everything that could have gone wrong, did. So then I decided to compile my own kernel... I got the 2.6.17 kernel, went through and tried to pick the correct options, then did,
Woohoo, I say to myself. That wasn't too hard...
Then, I load it up, and notice Lilo still has only one option.
The horror hits me... No... what have I done??!?!
For some reason I thought my old kernel would still be there, but it's not.
I bight my nails as I hit enter and wait...
The computer begins to load, goes to a fuzzy screen, and restarts...
NOOOOOOOOOO!!!! What have I DONE?!?! WHY did I try to install a new kernel?!?! WWwwwwhhhhyyy........
I tried making lilo.conf point to vmlinuz.old and vmlinuz-ide-2.4.whatever.
But no, it still just restarts when it tries to load the kernel.
HEEEELP MEEE! Please... I've spent weeks playing with Linux and it's getting very flustrating. Even after reading every tutorial on the net that I can find, I seem to screw everything up. My last install I ended up locking KDE up, locking it up AGAIN when it was trying to scan the uncleanly mounted disk, and ended up corrupting all my data. Is there anyway I can get my old kernel back?
EDIT: I mounted my slackware CD and looked around on it, I found a bzImage for bare.i (the kernel the CD uses to boot up) and then moved it to my /boot dir and told lilo to boot it. Again, it didn't work. I don't understand... shouldn't that have worked? What files are edited when "make install" runs?