SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Are you able to boot slackware with the huge kernel?
Yes, I am using a custom kernel right now. Earlier I commented out the custom kernel thoughtlessly, expecting the generic kernel to work, so I had to use a livedisk to uncomment the custom kernel via some tricky chroot of my /dev/sda2 into the livedisk environment, which I found interesting.
I am not sure what is going on, since when I run 'lilo -v' it gives me verbose information and updates my lilo to MBR without any errors or warnings.
I am thinking to keep the custom kernel and forget this issue.
try booting the huge kernel rerun the scripts to create an initrd.gz for the generic kernel and see if that helps. The only possible problem with this is if you are using an initrd.gz to boot your custom kernel.
My new redhat 9 installation is not booting, it says: <0>kernel panic: Attempted to kill init!
I've tried different machines but will get the same error. How should i correct this
@ stfwala you need to start a new thread with your question to prevent confusion. This is a Slackware problem and not any way related to a redhat problem.
try booting the huge kernel rerun the scripts to create an initrd.gz for the generic kernel and see if that helps. The only possible problem with this is if you are using an initrd.gz to boot your custom kernel.
No, I would not use an initrd.gz to start the custom kernel, as I already have an entry for it in the lilo.conf. I'll try this with huge.
try booting the huge kernel rerun the scripts to create an initrd.gz for the generic kernel and see if that helps. The only possible problem with this is if you are using an initrd.gz to boot your custom kernel.
Yes, the solution was that. The creation of a custom kernel unrelated to the huge kernel that comes with the generic results in a bad initrd.gz.
I switched to the huge kernel, then ran the command:
/usr/share/mkinitrd/mkinitrd_command_generator.sh
This produced the right initrd.gz. So I learned from this, the initrd.gz for a generic can only be produced with the right huge kernel related to it, and not with a custom kernel.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.