I have not been able to successfully boot a custom kernel lately, no matter how hard I try.
Every time I try to build one, even from an existing kernel (for example, Ubuntu’s kernel image), I get a kernel panic on boot indicating that it cannot access my drive. From what I can see, it has something to do with the PATA interface my motherboard uses (a standard Intel one, from what I can tell) and not being able to get at the drive after the initial bootstrap takes place.
It frustrates me.
I completely reinstalled Ubuntu because of this, thinking there may be some issue with the install, but now I’m stuck on the latest Ubuntu kernel with the libata kernel interface which slows access to my drives to a crawl. I even tried to use another distro, momentarily, thinking it was just Ubuntu. It wasn’t. Every other recent kernel simply will not successfully boot on my hardware, while I have never had issues with it before.
I seriously believe that it has to do with the new libata interface in the kernel, that it has somehow completely messed up access to my drive via the older, more reliable ATA/IDE method, which doesn’t work either.
Yeah, I’m frustrated. Times like these when I want to throw Linux away and move to *BSD. I then remember how frustrating BSD can be and stay, hoping things will work out.
EDIT: Well, I did something that made it all right, finally. Boots up fine, drives show up as /dev/hd* as they should, and hdparm shows them properly using DMA and optimized access to the drive as they should, which they could not do under sd* (libata).
Happy again.