kernel panic after building custom kernel for macbook
Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
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've compiled a custom kernel but now when I try and boot into linux I get the following:
i8042.c: No controller found.
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (0,0)
Kernel alive
kernel direct mapping tables up to 10000000 @ 800)-d000
I went into the rescue system using the install cd and there was no lilo.conf in /etc, even tho I put one there after compilation, before I tried to reboot. So I created a new lilo.conf with the following:
I also tried with sda3, just incase. And also without the append, so just 'root=/dev/sda4'
and then tried to run lilo but it said something about a read only file system and didn't do anything. When I go back into the rescue console again the lilo.conf file is gone again.
I only can guess, however
1. I think your problem is that / cannot be mounted, reason can be either controller, file system or whatever is not supported by kernel, (if supported by module, you need initrd)
2. With rescue disk, I think / is on CD, which is read only. So, wherever you think /etc is not wherever you want.
3. You need to know where your penguin lives. /dev/sda /dev/sdb.... This is where you picked through fdisk. This is not "try and error"
post here
a. what file system and controller you have. and related kernel options
b. cfdisk output
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.