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.
You may need to create an initrd (Read /boot/README.initrd) or you can try the script "/usr/share/mkinitrd/mkinitrd_command_generator.sh" to help create one.
This didn't work for me, and I usually have no problems making an initrd.gz and running the generic kernel it failed with the following error
Quote:
mounting /dev/sda1 on /mnt failed
ERROR: no /sbin/init found on rootdev
This didn't work for me, and I usually have no problems making an initrd.gz and running the generic kernel it failed with the following error
samac
Samac, why did mkinitrd_command_generator.sh not work for you? I want this script to function in all cases if possible. If you have any error output and PC configuration details, I'd appreciate it.
samac@quad:~$ su
Password:
root@quad:/home/samac# /usr/share/mkinitrd/mkinitrd_command_generator.sh
#
# 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:
root@quad:/home/samac# uname -a
Linux quad 2.6.33 #1 SMP Wed Mar 3 21:51:23 GMT 2010 x86_64 Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz GenuineIntel GNU/Linux
root@quad:/home/samac#
Quote:
root@quad:/home/samac# cat /etc/lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda
compact
lba32
# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255
# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt
# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
default = Linux
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 20
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# 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
image = /boot/vmlinuz-generic-2.6.33
root = /dev/sda1
initrd = /boot/initrd.gz
label = Slackware64
read-only
# Linux bootable partition config ends
root@quad:/home/samac#
Not sure how to get the boot error message as I have to reboot the machine but the post above gives the general idea. How much detail do you need on the hardware or in uname -a enough?
There is nothing in /var/log/syslog, as I suspected, because it does not boot passed the initrd.gz into the system on the disk, but thanks for the idea.
Not sure how to get the boot error message as I have to reboot the machine but the post above gives the general idea. How much detail do you need on the hardware or in uname -a enough?
samac
No need for the exact boot error message I think; what you posted was OK.
When the tool suggests this line:
was that what you would have used as well?
And did you actually run this command to create the initrd.gz (not thinking you're dumb, just have to ask this to be very sure) and then run lilo? Because your system setup really does not look all that exotic and the command should have produced a working initrd/
which I cut and modified from the initrd.readme in /boot ie. mkinitrd -c -k 2.6.32.3 -m ext4 -f ext4 -r /dev/sdb3. I then used your script /usr/share/mkinitrd/mkinitrd_command_generator.sh and it returned
I was also missing a working 32-bit extensions because libuuid had been moved from e2fsprogs to util-linux-ng and I had to create a new compat32 version.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.