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 downloaded and compiled a new kernel, and broke my menu.lst file so that I can't boot into the old or new kernel. Is there anyway short of a complete reinstall to fix this? Thanks
you probably have just either made a bad kernel or set your menu.lst up wrong.
in /boot does the kernel image you want to use correspond to the one in menu.lst. If not you need to modify that. If the kernel I would suggest keeping the old kernel in the menu so that you can still get in if the new on is borked. in any event you can use knoppix or similar to repair any damage...
what did you call your new kernel? vmlinuz? or what? please explain the steps you took from the begining
I used the steps on the installationo wiki on this site, but I couldn't get the /sbin/mkinitrd /boot/initrd-x.x.x.img x.x.x to work. It couldn't find certain files in the initrf.img file, which confused me. I looked around, and I think I got caught switching horses mid stream instead of starting over from scratch. Anyway, my computer tries to boot, gets locked up, and defaults to an empty line. It takes and responds to text, but most commands do not work. Exit works, and it tells me about my kernel being in distress because it can't mount my root. I am pretty sure it is because I broke menu.lst or some file it is dependent on, but I can't get to it to edit it. I have a live CD, but I can't figure out how to access my hard drive from it in order to make corrections.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.