Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Something went wrong with my kernel build--it caused kernel panic when I booted it. So I went to kpackage to uninstall it. While I was doing so, I noticed it say something to the effect of "vmlinuz is a broken link." I've booted Linux enough times to know that a line with "vmlinuz" appears near the top, so am I correct in guessing this was important? Could it be why my kernel didn't work?
Do you have a sym link /vmlinuz atm? Is it a broken link? That's what the message sounds like to me. But regardless, vmlinuz is the name of the kernel externally and panics occur within the kernel, so the issues are unrelated.
I'm not sure if I have that symlink--I'd have to build this kernel again and check. I was just hoping that fixing this broken link might be the magic bullet.
Well, this was ultimately related to making my SATA hard drive work, and both building a new kernel and reconfiguring the old one failed to do that. I'm beaten. I will send the drive back to Newegg soon, and I accept that I'll never know why Linux wouldn't detect it. This should be my last post on it, and certainly the last thread.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.