LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 11-18-2012, 02:17 PM   #16
michijo
Member
 
Registered: Apr 2011
Posts: 162

Original Poster
Rep: Reputation: 0

Quote:
Originally Posted by colorpurple21859 View Post
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.

Last edited by michijo; 11-18-2012 at 02:47 PM.
 
Old 11-18-2012, 04:05 PM   #17
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,342

Rep: Reputation: 184Reputation: 184
If your custom kernel works and the generic kernel doesn't, there must be something missing/wrong with your initrd.gz for the generic kernel.
 
Old 11-18-2012, 06:10 PM   #18
michijo
Member
 
Registered: Apr 2011
Posts: 162

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by colorpurple21859 View Post
If your custom kernel works and the generic kernel doesn't, there must be something missing/wrong with your initrd.gz for the generic kernel.
I only used the commands to automatically create the initrd.gz. So it is only what the system told me.

Though it can be maybe that the custom kernel I made has created an initrd.gz incompatible with the 3.2.29 generic kernel?
 
Old 11-18-2012, 08:54 PM   #19
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,342

Rep: Reputation: 184Reputation: 184
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.
 
Old 11-18-2012, 09:40 PM   #20
stfwala
LQ Newbie
 
Registered: Dec 2011
Posts: 2

Rep: Reputation: Disabled
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
 
Old 11-18-2012, 09:53 PM   #21
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,342

Rep: Reputation: 184Reputation: 184
@ 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.
 
Old 11-18-2012, 10:17 PM   #22
michijo
Member
 
Registered: Apr 2011
Posts: 162

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by colorpurple21859 View Post
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.
 
Old 11-19-2012, 01:33 PM   #23
michijo
Member
 
Registered: Apr 2011
Posts: 162

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by colorpurple21859 View Post
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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] lilo says my 2.6 kernel image is to large&new problem kernel will not boot smeezekitty Linux - Newbie 3 10-13-2009 08:41 PM
Kernel Header files needed for lilo (config.h no longer in kernel!) gvp87 Linux - Software 1 04-29-2008 02:32 PM
Upgraded kernel, lilo.conf, didn't run /sbin/lilo dtashima Linux - Newbie 4 10-18-2004 11:21 AM
No new kernel-option in LILO after editing lilo.conf corwax Debian 3 08-26-2003 08:55 PM
new kernel causes lilo crash; /sbin/lilo = Warning: device 0x0305 exceeds 1024 cylind dandysf Linux - Software 0 08-26-2003 04:50 PM


All times are GMT -5. The time now is 07:02 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration