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 recently bought a new sony vaio and am in the process of installing debian as I have with my IBM laptop. Only I have not luck in compiling a kernel for it. I have searched and no one seems to have had a problem. The default kernel works with it and I can even get into X on the default kernel. I keep getting a kernel panic.
VFS: Cannot open root device "fe00" or unknown-block(254,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(254,0)
I have tried to compile different kernels. I have tried using lilo and grub. I am out of ideas on why this does not work.
The most common cause of kernel panic is that you don't have support
for your / (root) filesystem, or your hard drive's controller, built into (Y)
you kernel. These cannot be modules (M) unless you also install an
initial ram disk image (initrd).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.