We will definately want to get you running on the 2.6 kernel. That's the only one we test and support. So there's a good chance something may not work with 2.4. When you wrote:

"initrd.......[some stuff i can't catch]saved defaultboot

and the system restarts"

Can you offer more details? How far into the installation do you get? You get to the partioning and 1st phase setup (which uses the red/blue text interface), up to the first reboot? Then on the first reboot, do you get prompted to enter the device and activation code? Does it then do it's installation of all the packages? do you get the installation complete message?

What CPU are you using? Our kernel is for 686, which means AMD Athlon, Duron, Sempron, Athlon 64 and Intel Pentium 2, Pentium 3, Pentium 4, Pentium M and derivatives of these. I used to see lock-ups and reboots just after the kernel is loaded (loke you seem to see) when using an earlier CPU than the kernel was built for. We don't have a 386 version of the kernel shipping.

If your CPU is from the range specified above, then I would need some more info on your hardware configuration.

I, too, am having this problem. I just installed 2.6 kernel. It never asked for the activation code. The installation process seemed to go smoothly. It partitioned the hard drive and installed the base packages. Set up DHCP, and installed the kernel. Then, it says to take the cd out and reboot. It boots to Grub, and goes into a reboot loop. If I type the commands manually, I find that the constant reboot happens on the last step..."boot". Any help would be much appreciated, as we are interested in looking at this system to install with our home automation packages.

That's odd. Pentium 2 is 686. I have a Pentium 2 (Slot 1) at home and it works with a 686 kernel similar to Pluto's kernel. Pentium MMX is 586 and AMD's K6-2 is 586, so those wouldn't work, but Pentium 2 should work, even if it's not that powerful.