So now I know why "bigboy" can't boot modern kernels
LinuxQuestions.org Member Success StoriesJust spent four hours configuring your favorite program? Just figured out a Linux problem that has been stumping you for months?
Post your Linux Success Stories here.
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.
So now I know why "bigboy" can't boot modern kernels
This was really getting me down. I couldn't boot anything later than 4.13 on my trusty old desktop without getting a kernel panic. Of course I couldn't see how the panic started (at this stage there is no display), only how it ended, with a string of errors relating to the acpi driver.
This was in LFS, so the kernel was home-rolled. If I booted it with "acpi=off" or just didn't build the acpi driver at all, there was no panic, but this obviously wasn't a good solution. It did, though, seem to show that this was an acpi problem.
Then I did a git bisect on the kernel and managed to find the bad commit. To my surprise, it had nothing to do with acpi; it was a memory management thing. For some reason the change just threw the acpi driver and not some other part of the kernel.
There's a lovely man called Michael Shell on the LFS support list and he led me to the actual code change and told me which lines had to be reinstated. And now I can build modern kernels that actually boot! I'm using one now: 4.15.3, the native kernel of LFS 8.2.
It doesn't seem to be a common problem. There is a mention of it in the latest Crux install instructions, but that might just be because I'm on the Crux mailing list so they knew of one person who had been having boot problems.
Of course "roll your own" isn't the answer for binary distros. Something needs to be done about the actual kernel code. I've been given the names and addresses of the relevant kernel hackers and I've sent them an email. Naturally I'll be happy to carry out any tests they suggest. After all, I'm the one with the misbehaving hardware!
Most of those aren't tech-speak, they're management-speak, which is much worse! I love the definition of crowdfunding as "begging for money on the Internet" and also the cloud as "the place where we steal user data." Incidentally, do you know the definition of cyberspace as "where telephone conversations happen"?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.