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.
I know there are many threads and posts about booting the slackware installer from USB (if the cd/dvd drive can't boot the system, etc.) Strangely, I haven't seen that many about booting a slackware install from an external USB drive or USB stick.
I've installed slackware 12.2 to my USB stick. Before installation/setup (which I did using cds 1-3), I partitioned it this way:
/dev/sdb1 - vfat - 8 GB
/dev/sdb2 - ext2 - 23 GB
/dev/sdb3 - swap - 1 GB (just in case I actually need one)
Installed LILO to the MBR of the USB stick. It starts booting but along the way I get the VFS kernel panic message device (8,18). It says my boot options are /dev/sda or /dev/sda1. But sda is laptop harddisk, not my USB stick...which is sdb and root is on sdb2.
So what do I need get it to work? My guess is, an intird image - but which one and how do I get it into LILO?
(If it's relevant to the solution, I have slax on another USB which I use as a backup linux usb.)
I've tried specifying 'root='s at the 'tab' boot command options but none work (/dev/sdb , /dev/sdb2 , /dev/sdb1).
There is also the Best one for USB-installer for Slackware 12.2
With this and a 4GB or larger USB you can install Slackware-12.2 Full with all packages!
( http://www.slackware.com/~alien/tools/usbinstall/12.2/ )
Please tell me if you get it working...
Additionally there is the Netinstall 40MB Mini-install .iso which can be extracted to a folder-transferred to USB-then configured to boot from USB-but you must know the Slackware 12.2 mirror urls, etc when installing.
( http://www.slackware.com/~alien/slackboot/mini/12.2/ )
Did you have a look at the usb-and-pxe-installers directory? The documentation and boot-images there should get you going.
I know I need to create an initrd of sorts. However, I'm not looking to make a "USB installer". I installed slack 12.2 TO a USB and now I get the VFS kernel panic message half-way through the boot.
It looks similar to my lilo.cfg
A question-do you have slack installed to your USB like it's a HD?
The lilo.cfg is for the USB right?
I have never tried it that way...
Others here would know more about that...
But, you can also try several different methods-netinstall and usb install as I mentioned above-or additionally I think you can have the slack netinstall boot off the FAT32 partition, put the Slackware-12.2 DVD iso on the ext2 partition and then tell slack to find the iso at the menu prompt during setup-I think I saw that somewhere...?
It looks similar to my lilo.cfg
A question-do you have slack installed to your USB like it's a HD?
The lilo.cfg is for the USB right?
yes to both.
Quote:
Originally Posted by linus72
But, you can also try several different methods-netinstall and usb install as I mentioned above-or additionally I think you can have the slack netinstall boot off the FAT32 partition, put the Slackware-12.2 DVD iso on the ext2 partition and then tell slack to find the iso at the menu prompt during setup-I think I saw that somewhere...?
but that would help to install from USB, not to USB.
OH! I thought you trying to install from USB-sorry!
I don't understand what's wrong-here is my lilo.cfg from my HD sda1
Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
#compact # faster, but won't work on all systems.
# 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
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
prompt
timeout = 300
# VESA framebuffer console @ 800x600x256
vga = 771
# 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
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda1
label = Slackware12.2
read-only # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
I would think the USB is not being recognized or not recognized as a HD...
I'm sure somebody here knows...
Also, your booting lilo off the FAT32 partition?
Is that possible?
What is the FAT32 partition for?
Also, I'm pretty sure you're going to have to add a rootdelay line in your lilo.conf in order to give your system time to properly mount the usb stick.
I know there are some recent threads in this sub-forum regarding this. I was keen a couple of months back, but I'm happy with my extremely-customized slax usbstick at the moment, and I don't feel like scrapping it to make it pure Slackware (perhaps when 12.3 is released I'll give it a go....)
When I have a moment, I'll see if I can hook you up with those threads.
OH! I thought you trying to install from USB-sorry! ...
Also, your booting lilo off the FAT32 partition?
Is that possible?
What is the FAT32 partition for?
not booting off the FAT32 but it's there coz I wanted windows-readable space on the USB stick and read somewhere that windows wants/needs(?) the FAT* partition to be first to be able to read it.
this is the error (wrote it down):
(after 'md' devices...)
Code:
VFS: Cannot open root device "812" or unknown-block(8,18)
Please append a correct "root=" boot option; here are the available partitions
0800 ... sda driver: sd was detecting the harddrive
0801 ... sda1
0b00 sr0 driver: sr
Kernel panic...
Get similar errors when I use sda, sda1, sdb, sdb[12], etc.
Also, I'm pretty sure you're going to have to add a rootdelay line in your lilo.conf in order to give your system time to properly mount the usb stick.
Yup, that worked! :-)
tried
Code:
Slack122-1 rootdelay=10 root=/dev/sdb2
and
Code:
Slack122-1 rootdelay=10
(without explicitly specifying the root). Both worked.
So will now add an append line to lilo.conf, I think that would be easier/faster than modifying initrd, espcially since I don't have one right now. Will give it a try when I recompile the kernel.
Will first redo lilo and re-try the normal boot. Though I'm curious about how 'slax' does it coz there's no notable delay in the boot process.
...Though I'm curious about how 'slax' does it coz there's no notable delay in the boot process...
I haven't investigated, but there's probably a "sleep" function in the initrd for slax. The same guy who maintains slax is responsible for linux-live.org where he explains how to create a live distro, so there may be info there....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.