Linux - KernelThis forum is for all discussion relating to the Linux kernel.
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.
EFI Variables Facility 0.00 2004-May-17
Key type dns resolver registered
Registered taskstats version 1
hd: no drives specified - use hd=cyl,head,sectors on kernel command line
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Bios EDD facility v0.16 2004-Jun-25, 1 devices found
VFS: Cannot open root device "803" or unknown block (8,3); error -6
Please append a correct "root=" partition; here are the available partitions:
Kernel Panic - not syncing VFS: Unable to mount root fs on unknown-block(8,3)
The box is a Samsung 350V - Intel Panther Point (HM76?) chipset.
It looks like there's something fairly fundamental wrong. It's obviously not finding the disk. The kernel config is so massive these days it's hard for a luser to be sure he has everything. I obviously don't. What I found online was to enable AHCI in the bios and I did that. No dice.
Seems to me that you have disabled something you need.
Use the config of the 3.6 generic kernel as a starting point, use make oldconfig to generate a valid config file.
Then compile that kernel and test if it boots (don't forget to generate an initrd for that kernel with the modules you need).
If it works simply use that kernel or use it as starting point for further trimming. If you decide to trim further at first disable all things that are not needed for sure (like floppy support or similar things). Make notes what you change, so that troubleshooting is easier. Compile and test again.
If you don't want to use an initrd enable the drivers you need (disk controller, AHCI support should be sufficient for you, and filesystems). Compile and test again.
And so on.
I should have been clearer. I started with 3.2.29(Known working on an AMD box), went through it after a make oldconfig removing AMD options and adding INTEL ones (This is an intel based box). Because of UEFI issues I never actually booted 3.6.10. But I have the working kernel config from 3.2.29 with Slackware's huge kernel so I can use that
Probably a more direct route would be
take 3.2.29 (Known working) and make oldconfig. That's an hour choosing, but it's safer.
Thanks for the link. I'm sorted and running on 3.7.1.
I have a better chance than a lot of users at understanding this because of my background, but it's things like CEPH, Netlink, Various Namespaces, ciphers and the like which are new concepts hacked out by gigabytes of debate on lmkl and numerous patches. On a new box, it's getting tough to work up your config. Even simple old usb now has ohci, uhci, ehci, xhci, & vhci drivers at least. As this is a new box, how do I find the hardware? I ran lsusb, lspci, and sensors-detect as appropriate. I wanted to find a driver for the Sony Microvault card reader in the box - it's read only, but other sd card readers are rw on the same card. SSD options are all over the place.