[SOLVED] Salix won't boot anymore

[TheGatorade]

I solved the problem.
Grub was trying to boot /boot/vmlinuz
I changed it to /boot/vmlinuz-huge-smp-2.6.37.6-smp
Also changed 'insmod ext2' to 'insmod ext4' to avoid a mount error.

[Shador]

Grub was trying to boot /boot/vmlinuz
I changed it to /boot/vmlinuz-huge-smp-2.6.37.6-smp

Then you deleted the symlink /boot/vmlinuz or it's not pointing in the right location. But symlinks are no problem at all for grub2.
Anyway, editing that file is not such a good idea because the next run of grub-mkconfig/update-grub overwrites its content. Unless of course you take the necessary precautions and refrain from using those tools meant to make your life easier.

Also changed 'insmod ext2' to 'insmod ext4' to avoid a mount error.

That gives you a grub error then (nothing fails probably though). That's because grub2 only has an ext2 module which handles all ext* filesystems. This is possible because of he compatibility between the different versions when the filesystem is accessed read-only. In any case changing the filesystem module loaded in grub2, which is responsible for giving grub2 access to your kernel image, doesn't at all affect the linux kernel. That error message is because the kernel can't tell which version of ext2 it is and thus tries ext2/3/4 in that order. If you want that warnings to go away pass the kernel rootfstype=ext4.