LinuxQuestions.org
Visit the LQ Articles and Editorials section
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 06-24-2010, 01:25 PM   #1
adamschock
LQ Newbie
 
Registered: Dec 2008
Posts: 4

Rep: Reputation: 0
initrd and generic kernel fails to boot with errors after using mkinitrd generator


I'm just starting out with Slackware, so sorry for any stupid mistakes.
As suggested,I tried to switch to a generic kernel. I used the mkinitrd command generator script:
Code:
./mkinitrd_command_generator.sh /boot/vmlinuz-generic-smp-2.6.33.4-smp
,used the mkinitrd:
Code:
mkinitrd -c -k 2.6.33.4-smp -f ext4 -r /dev/sda1 -m jbd2:mbcache:ext4 -o /boot/initrd.gz
changed the lilo.conf:
Quote:
# Linux bootable partition config begins
# initrd created with 'mkinitrd -c -k 2.6.33.4-smp -f ext4 -r /dev/sda1 -m jbd2:mbcache:ext4 -o /boot/initrd.gz'
image = /boot/vmlinuz-generic-smp-2.6.33.4-smp
initrd = /boot/initrd.gz
root = /dev/sda1
label = 2.6.33.4-smp
read-only
# Linux bootable partition config ends
and ran lilo as recommended. It ran with one warning about lba assumed,my computer is old but can boot fine from whatever cylinder.
After reboot I got the error:
Code:
/boot/initrd.gz: loading kernel modules from initrd.image:
mount:mounting /dev/sda on /mnt failed:no such file or directory
ERROR: no /sbin/init found on root dev (or not mounted).Trouble ahead.
You can try and fix it. Type exit when things are done.
bin/sh: can't access tty:job control turned off.
Any attempt to intervene resulted in what looks like a kernel panic and a traceback.

My hardware: (old for learning purposes)
Linux mirkwood 2.6.33.4-smp #2 SMP Wed May 12 22:47:36 CDT 2010 i686 Intel(R) Pentium(R) 4 CPU 2.53GHz GenuineIntel GNU/Linux
I'm running an adaptec scsi controller which the huge kernel seems to run with the:
Quote:
Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
Could this be the missing driver?
I followed the instructions in README.initrd with all the expected results.
I checked this forum and it seems that others have had similar problems. http://www.linuxquestions.org/questi...orking-800757/

http://www.linuxquestions.org/questi...tor-sh-793557/

However, the fixes suggested involved things I was not sure about like changing symlinks in /boot (no mention of such in the docs) or things I had already done.

In light of other posts I am enclosing the output of the mkinitrd command generator,current lilo.conf and ls -al /boot

Quote:
output:
#
# mkinitrd_command_generator.sh revision 1.40
#
# This script will now make a recommendation about the command to use
# in case you require an initrd image to boot a kernel that does not
# have support for your storage or root filesystem built in
# (such as the Slackware 'generic' kernels').
# A suitable 'mkinitrd' command will be:

mkinitrd -c -k 2.6.33.4-smp -f ext4 -r /dev/sda1 -m jbd2:mbcache:ext4 -o /boot/initrd.gz
# An entry in 'etc/lilo.conf' for kernel '/boot/vmlinuz-generic-smp-2.6.33.4-smp' would look like this:
# Linux bootable partition config begins
# initrd created with 'mkinitrd -c -k 2.6.33.4-smp -f ext4 -r /dev/sda1 -m jbd2:mbcache:ext4 -o /boot/initrd.gz'
image = /boot/vmlinuz-generic-smp-2.6.33.4-smp
initrd = /boot/initrd.gz
root = /dev/sda1
label = 2.6.33.4-smp
read-only
# Linux bootable partition config ends

lilo.conf:
...
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda1
label = Linux
read-only
# Linux bootable partition config ends
#
# Linux bootable partition config begins
# initrd created with 'mkinitrd -c -k 2.6.33.4-smp -f ext4 -r /dev/sda1 -m jbd2:mbcache:ext4 -o /boot/initrd.gz'
image = /boot/vmlinuz-generic-smp-2.6.33.4-smp
initrd = /boot/initrd.gz
root = /dev/sda1
label = 2.6.33.4-smp
read-only

ls -al /boot:
total 24268
drwxr-xr-x 3 root root 4096 2010-06-24 15:40 ./
drwxr-xr-x 21 root root 4096 2010-06-21 18:31 ../
lrwxrwxrwx 1 root root 37 2010-06-21 18:10 README.initrd -> /usr/doc/mkinitrd-1.4.5/README.initrd
lrwxrwxrwx 1 root root 32 2010-06-21 18:09 System.map -> System.map-huge-smp-2.6.33.4-smp
-rw-r--r-- 1 root root 1282716 2010-05-13 08:00 System.map-generic-2.6.33.4
-rw-r--r-- 1 root root 1322225 2010-05-13 05:41 System.map-generic-smp-2.6.33.4-smp
-rw-r--r-- 1 root root 2041855 2010-05-13 08:28 System.map-huge-2.6.33.4
-rw-r--r-- 1 root root 2086543 2010-05-13 06:48 System.map-huge-smp-2.6.33.4-smp
-rw-r--r-- 1 root root 512 2010-06-21 18:34 boot.0800
-rw-r--r-- 1 root root 168 2010-06-21 18:34 boot_message.txt
lrwxrwxrwx 1 root root 28 2010-06-21 18:09 config -> config-huge-smp-2.6.33.4-smp
-rw-r--r-- 1 root root 108261 2010-05-13 08:00 config-generic-2.6.33.4
-rw-r--r-- 1 root root 108627 2010-05-13 05:41 config-generic-smp-2.6.33.4-smp
-rw-r--r-- 1 root root 108235 2010-05-13 08:28 config-huge-2.6.33.4
-rw-r--r-- 1 root root 108601 2010-05-13 06:48 config-huge-smp-2.6.33.4-smp
-rw-r--r-- 1 root root 5040 2010-02-16 22:44 diag1.img
drwxr-xr-x 11 root root 4096 2010-06-23 19:41 initrd-tree/
-rw-r--r-- 1 root root 1610432 2010-06-23 19:41 initrd.gz
-rw------- 1 root root 126976 2010-06-24 15:40 map
-rw-r--r-- 1 root root 14174 2010-02-15 03:57 slack.bmp
lrwxrwxrwx 1 root root 29 2010-06-21 18:09 vmlinuz -> vmlinuz-huge-smp-2.6.33.4-smp
-rw-r--r-- 1 root root 2545840 2010-05-13 08:00 vmlinuz-generic-2.6.33.4
-rw-r--r-- 1 root root 2662400 2010-05-13 05:41 vmlinuz-generic-smp-2.6.33.4-smp
-rw-r--r-- 1 root root 5243760 2010-05-13 08:28 vmlinuz-huge-2.6.33.4
-rw-r--r-- 1 root root 5421536 2010-05-13 06:48 vmlinuz-huge-smp-2.6.33.4-smp
Sorry,if there is too much detail. Can someone give me a good clue where I went wrong.

Thanks.
Adam
 
Old 06-24-2010, 01:37 PM   #2
piratesmack
Member
 
Registered: Feb 2009
Distribution: Slackware, Arch
Posts: 517

Rep: Reputation: 132Reputation: 132
Maybe it needs some more time to detect your hard drive.

Code:
mkinitrd -c -k 2.6.33.4-smp -f ext4 -r /dev/sda1 -m jbd2:mbcache:ext4 -w 10 -o /boot/initrd.gz
The '-w 10' will make it wait 10 seconds.

Last edited by piratesmack; 06-24-2010 at 01:39 PM.
 
Old 06-24-2010, 01:53 PM   #3
Chuck56
Member
 
Registered: Dec 2006
Location: Colorado
Distribution: Slackware
Posts: 421

Rep: Reputation: 58
Check the kernel names you have in /boot. I think 13.1 introduced a kernel name change to vmlinuz-generic-2.6.33.4. The smp is included in the kernel and no longer referenced in the name.
 
Old 06-24-2010, 02:01 PM   #4
ryerke
Member
 
Registered: Dec 2006
Location: Fresno CA
Distribution: Slackware 13 Slackware 13.37 ARMEDSlack 13.37
Posts: 89

Rep: Reputation: 21
I have an Adaptec AHA-2940U2W card and I found that the boot will be totally bungled up without the driver included in the -m. You need to add aic7xxx module to the initrd if you want the kernel to properly decipher your drives. It does not matter whether you have the boot on the card or not, you will still need the module loaded at boot time.You might try:
Code:
mkinitrd -c -k 2.6.33.4-smp -f ext4 -r /dev/sda1 -m jbd2:mbcache:ext4:iac7xxx -w 10 -o /boot/initrd.gz
I don't know what the "w" is for but I would try it without first and then with just in case.

Last edited by ryerke; 06-24-2010 at 02:02 PM.
 
Old 06-24-2010, 02:07 PM   #5
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,191

Rep: Reputation: Disabled
The aic7xxx module is definitely missing. I Have no idea why the mkinitrd_command_generator.sh script failed to find out that the module needs to be loaded if the root partition is on a SCSI drive.

Just add "aic7xxx" as an additional module to the "-m" parameter of mkinitrd, and then re-run lilo to make it permanent.

Quote:
Originally Posted by Chuck56 View Post
Check the kernel names you have in /boot. I think 13.1 introduced a kernel name change to vmlinuz-generic-2.6.33.4. The smp is included in the kernel and no longer referenced in the name.
That is only true for 64-bit Slackware which only ships a SMP kernel. The 32-bit version of Slackware still has separate SMP and UMP kernels.

Eric
 
Old 06-24-2010, 02:07 PM   #6
adamschock
LQ Newbie
 
Registered: Dec 2008
Posts: 4

Original Poster
Rep: Reputation: 0
kernel 2.6.33.4

I thought that the one without the smp in the name is the kernel included for machines that can't run smp kernels.
Besides,which,this is a fresh install and as far as I know the kernels in /boot are the ones that come with a "full" install.
 
Old 06-24-2010, 02:15 PM   #7
Chuck56
Member
 
Registered: Dec 2006
Location: Colorado
Distribution: Slackware
Posts: 421

Rep: Reputation: 58
Quote:
Originally Posted by Alien Bob View Post
That is only true for 64-bit Slackware which only ships a SMP kernel. The 32-bit version of Slackware still has separate SMP and UMP kernels.
Thanks for keeping me honest. I was so close yet so far!
 
Old 06-24-2010, 03:33 PM   #8
adamschock
LQ Newbie
 
Registered: Dec 2008
Posts: 4

Original Poster
Rep: Reputation: 0
Problem Solved

Mr.Hameleers and Ryerke,

You were apparently both correct:

uname -a
Linux mirkwood 2.6.33.4-smp #1 SMP Wed May 12 21:39:37 CDT 2010 i686 Intel(R) Pentium(R) 4 CPU 2.53GHz GenuineIntel GNU/Linux

Thank you very much for an unprecedented (for me)response.

Adam
 
Old 06-26-2010, 02:30 PM   #9
ryerke
Member
 
Registered: Dec 2006
Location: Fresno CA
Distribution: Slackware 13 Slackware 13.37 ARMEDSlack 13.37
Posts: 89

Rep: Reputation: 21
Quote:
Originally Posted by Alien Bob View Post
The aic7xxx module is definitely missing. I Have no idea why the mkinitrd_command_generator.sh script failed to find out that the module needs to be loaded if the root partition is on a SCSI drive.

Just add "aic7xxx" as an additional module to the "-m" parameter of mkinitrd, and then re-run lilo to make it permanent.



That is only true for 64-bit Slackware which only ships a SMP kernel. The 32-bit version of Slackware still has separate SMP and UMP kernels.

Eric
Not to try and revive this after it's been solved but I also did not get anything from mkinitrd_command_generator. I never sent any bug reports since I thought it was just because I was using something that was so old. Evidently the older Adapted U2W's aren't being seen by the script.

Last edited by ryerke; 06-26-2010 at 02:32 PM.
 
  


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
Generic kernel + initrd not working rpedrica Slackware 12 06-22-2010 10:17 AM
sudo mkinitrd -o /boot/initrd.img-2.6.32.9 2.6.32.9 sudo: mkinitrd: command not foun vishwas181 Linux - Newbie 1 02-27-2010 01:16 AM
Generic SMP kernel with no initrd? songangel Slackware 8 03-26-2009 06:12 PM
Slackware 12, changing to generic kernel on raid1, mkinitrd issue [GOD]Anck Slackware 15 02-14-2008 07:25 PM
mkinitrd fails after kernel update RGummi Suse/Novell 2 10-13-2007 02:38 AM


All times are GMT -5. The time now is 05:43 AM.

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