SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Hi, the last time I compile my own kernel is 2.6.18.3, and now Im trying to compile the new 2.6.20 with the same .config file from my last success compilation but the 2.6.20 couldnt boot, it says something like this:
cannot mount /dev/sda7 to /mnt
freeing kernel init memory
# ... and the boot stopped
Im sure it's not the initrd, because I already did what the initrd.readme that I have to load the ext3, jbd, and adjust the root to /dev/sda7 (which is my root partition).
I already try to compile the kernel with * at all my filesystem related, but still dont work.
I'm not sure what is going on, just that it shouldn't be mounting on "/mnt", but on "/". As suggested above, it could be a bootloader problem. Check all of your configure scripts very carefully.
Regards,
Bill
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.