Bash errors after kernel compile
 

I recompiled and updated my kernel (2.4.7-10 to 2.4.9-10) to add support for my network card SiS900. I added the new kernel to grub.conf. Now when I boot into the new kernel imediately after login I get multiple bash errors..

bash: id: comand not found
[: =: unary operator expected
bash: id: comand not found
[: =: unary operator expected
bash: id: comand not found
[: =: unary operator expected
bash: id: comand not found
bash: dircolors: command not found
bash: id: comand not found
bash: id: comand not found
bash: id: comand not found
[: too many arguements

Once I get to the prompt only the bash commands work, I can't run any extended commands.

I then navigate to /usr and find that that partition is not mounted (appears empty). It does however mount when I boot to my old kernel. (This explains why none of my extended commands run.)

Anyone know what I did (or am doing) wrong.

Well, this isn't a lot of help, but might point you in the right direction.. it's sound to me like there is something missing out of the new kernel you compiled.. I would recommend loading up the config you used in your old kernel into the new kernel and then adding the new support option. That away you have an exact duplicate kernel with the added support you need. Then see what happens.

The config is stored as ' .config ' in your kernel directory.. just copy it over to the new kernel directory.

I just tried a third kernel compile to no avail, but I do see what the problem is a bit more clearly now. None of my partitions are being mounted at all. I can mount them all manually and get most of my apps to work, but I don't think that's a good solution.

Where are all of the mount points defined? Maybe that file is moved or just not writen properly.

/etc/fstab defines all your mount points at startup.

the mount problem probably comes from a problem in the file system types compiled into the kernel. if you have reiser on your main partition, you need to get reiser compiled in - if it's ext2, you need to make sure that the "second extended" file system is chosen. file systems need to be compiled into the kernel - not modules - if they're modules, then the kernel can't reach them, because it needs them to find where they are...

I got it, thanks for your help.
Linux dropped support for the EXT3 journaling file system in kernel 2.4.9.
Now I feel dumb.

Thanks