Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.)
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.
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...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.