Well, my idea did not work. However, I did just install Lilo to the MBR, and it recognizes both Windows and Slack and can boot into both. And plus, now I know how to rebuild the MBR in the future if I have to. I guess my focus now is getting the 2.6.10 kernel working...I'm going to Google it, and see how to do this via pkgtool...if you have any other tips for my endeavor feel free to post them.

Thanks alot for the help guys.

Alright, so I could not find the /testing folder to look for the precompiled kernel....even after a Find Files search I did not locate it. I downloaded 2.6.11.9, and might could use a tip or two to install that. The last time I tried, I somehow got it to boot but with no modules installed, and had many fatal errors at boot due to this. Would anyone offer an installation method besides ./configure, make, make install?

Thanks.

Granted, I used a little more complex online install guide, but apparently I left out the line to configure modules, so if anyone could just give a step-by-step...thanks.

Basic step-by-step...

1. Download the kernel.
2. Unzip the kernel.
3. Make a symlink for /usr/src/linux that points to the current kernel source tree. (new module installs often only look there, rather than querying the kernel to find its source)
4. cd to /usr/src/linux
5. make mrproper
6. make menuconfig / make xconfig / copy your old .config to the /usr/src/linux
--> make menuconfig when in CLI mode.
--> make xconfig if you have QT installed. (comes with KDE packages)
--> To save time and keep the same kernel config as last time, you can just copy the file .config from the old Linux source directory to the new one. This only works if you're keeping within the same tree (2.6 or 2.4)
7. make
8. make modules_install
9. cp System.map /boot/System.map-(version)
10. cp arch/(arch)/boot/bzImage /boot/vmlinuz-(version)
--> (arch) depends on your CPU type. i386, most likely.
11. cd /boot
12. ln -s System.map-(version) System.map
13. ln -s vmlinuz-(version) vmlinuz
14. update your lilo.conf
15. run lilo
16. reboot.


When updating your lilo.conf, I suggest that you keep an option for the old/install kernel, so that you can revert if your kernel configuration is wrong. I don't know anybody who got the kernel right on their first try.