Slackware on USB

XGizzmo · 07-05-2009, 08:25 AM

Did you add the required append="rootdelay=10" to lilo.conf?
it should look something like this.

Code:

  # Append any additional kernel parameters:
  append=" vt.default_utf8=0 rootdelay=10"
  boot = /dev/sda

The huge kernel should have everything it needs to boot without an initrd,
I have done it many times. Make sure the root= and boot= lines are correct.

onebuck · 07-05-2009, 08:43 AM

Hi,

And the problem with using a 'initrd' to insure that you boot is?

XGizzmo · 07-05-2009, 09:01 AM

Quote:

Originally Posted by onebuck

And the problem with using a 'initrd' to insure that you boot is?

There is nothing wrong with using an initrd, but if he can't get it to boot with the huge kernel there is almost 0% chance of getting it to work with an initrd. Since hugh kernel has all the usb filesystem and other bits needed to boot the system what should he add to an initrd the make it work?

onebuck · 07-05-2009, 09:35 AM

Hi,

A 'initrd' will not require the need to compile/re-compile of the kernel. I for one would not use the huge kernels since they are installer kernels. The generic kernels would be better suited for use on most systems. Sure in that case you will need a 'initrd'. But still easier than re-compiling all the time.

If you need to utilize delays to insure settling or recognition then you can use within '/etc/lilo.conf' the parameter 'rootdelay=10' in the stanza for the image you wish to boot. Or even in the global section of the of the config file. If used globally then all images would be treated.

Another way would be to create the 'initrd' then edit the '/boot/initrd-tree/init' and modify the 'sleep' variable. Of course after you modify the 'init' you would have to move the copy to the device. Do a search here on LQ to get a recipe or look at 'Install_Linux_to_removable_USB_disk' for a general idea.

I do like to make stanza specific reference within my '/etc/lilo.conf' so that the possible problems with 'global' settings can be alleviated by not providing information to other images that is not needed.

vharishankar · 07-05-2009, 11:08 AM

Quote:

Originally Posted by XGizzmo

There is nothing wrong with using an initrd, but if he can't get it to boot with the huge kernel there is almost 0% chance of getting it to work with an initrd. Since hugh kernel has all the usb filesystem and other bits needed to boot the system what should he add to an initrd the make it work?

Does the huge kernel compile these filesystems and other required drivers as modules or in-built in the kernel? Does the Slackware installer use initrd? (I don't know about this, so I'm asking a genuine question)

Because even if it is compiled as modules, you'll still not be able to boot off it, because there's no way to load the required modules before reading the filesystem without an initrd.

initrd on the other hand, provides a mechanism to load the kernel modules required to read the filesystems and the device drivers required for IDE/SATA/PATA/SCSI/RAID etc.

XGizzmo · 07-05-2009, 02:27 PM

Quote:

Originally Posted by harishankar

Does the huge kernel compile these filesystems and other required drivers as modules or in-built in the kernel? Does the Slackware installer use initrd? (I don't know about this, so I'm asking a genuine question)

Everything that is needed to boot 98% of the systems out there is compiled in the huge* kernels. I am NOT saying don't use an initrd, I am saying don't start adding more problems until you get the first one fixed. Get the thing booting with the huge kernel first before you start trying to use a generic kernel with an initrd.

onebuck · 07-05-2009, 10:09 PM

Hi,

Quote:

Originally Posted by XGizzmo

Everything that is needed to boot 98% of the systems out there is compiled in the huge* kernels. I am NOT saying don't use an initrd, I am saying don't start adding more problems until you get the first one fixed. Get the thing booting with the huge kernel first before you start trying to use a generic kernel with an initrd.

No one is stating too change things. The huge kernels are not the choice to use as a running kernel;

Quote:

excerpt from 'CHANGES_AND_HINTS.TXT';

As stated earlier, it is recommended that you use one of the generic kernels
rather than the huge kernels; the huge kernels are primarily intended as
"installer" and "emergency" kernels in case you forget to make an initrd.
For most systems, you should use the generic SMP kernel if it will run,
even if your system is not SMP-capable. Some newer hardware needs the
local APIC enabled in the SMP kernel, and theoretically there should not be
a performance penalty with using the SMP-capable kernel on a uniprocessor
machine, as the SMP kernel tests for this and makes necessary adjustments.
Furthermore, the kernel sources shipped with Slackware are configured for
SMP usage, so you won't have to modify those to build external modules
(such as NVidia or ATI proprietary drivers) if you use the SMP kernel.

But to stay with a particular kernel because of your exclusion conditions on troubleshooting will only continue to build on the situation thus not correcting the situation. Changing to the generic is not that difficult. Especially since the OP is still experiencing problems. Try it! It might work.

@harishankar;

The huge kernels have everything but the kitchen sink compiled in to be used as 'installer' kernels. The 'initrd' will include by default when created any associative modules that you include with the primary module. Meaning if a support module is needed you don't have to specify it. Just the primary module. So when you specify a filesystem then any support modules for that specification will be included.

noidea · 07-06-2009, 02:57 AM

try slax it takes a 300 mb download and one command to install it and thats it. Very good.

igadoter · 07-07-2009, 02:17 AM

OK guys,

It is very interesting what you have said about initrd,
but how I can create an initrd without the first boot?

igadoter · 07-07-2009, 02:22 AM

Quote:

Originally Posted by XGizzmo

Did you add the required append="rootdelay=10" to lilo.conf?
it should look something like this.

Code:

  # Append any additional kernel parameters:
  append=" vt.default_utf8=0 rootdelay=10"
  boot = /dev/sda

The huge kernel should have everything it needs to boot without an initrd,
I have done it many times. Make sure the root= and boot= lines are correct.

Yes ,I added rootdelay but instead of

boot = /dev/...

there is

root = UUID=.....

According to lilo man, as I understand, if there is no boot option then
the root device is the device where is currently mounted a
root directory.

XGizzmo · 07-07-2009, 06:11 AM

You need to quote the root= arguments if using UUID due to a second '=' if you have not done so.

root="UUID=MyDisk"

igadoter · 07-08-2009, 03:15 AM

Quote:

Originally Posted by XGizzmo

You need to quote the root= arguments if using UUID due to a second '=' if you have not done so.

root="UUID=MyDisk"

Yes, I did that.

janhe · 07-09-2009, 03:20 AM

What does it say after the kernel panic?

The most often seen error is "cannot mount sda2" or something like that.

The exact error message might give another clue about the problem.

igadoter · 07-11-2009, 04:02 AM

Quote:

Originally Posted by onebuck

Hi,

No one is stating too change things. The huge kernels are not the choice to use as a running kernel;

But to stay with a particular kernel because of your exclusion conditions on troubleshooting will only continue to build on the situation thus not correcting the situation. Changing to the generic is not that difficult. Especially since the OP is still experiencing problems. Try it! It might work.

@harishankar;

The huge kernels have everything but the kitchen sink compiled in to be used as 'installer' kernels. The 'initrd' will include by default when created any associative modules that you include with the primary module. Meaning if a support module is needed you don't have to specify it. Just the primary module. So when you specify a filesystem then any support modules for that specification will be included.

As my main goal is to create a system on a USB stick and let
say to put this stick into my pocket and run this system
on any other machine I want to, I suppose it is a good choice
to have a hugesmp.s kernel ( possible hugest) as running,
as you cannot expect some kind of fixed hardware configuration,
I want to say that the kernel should be big enough to
to launch the system on many machines: notebooks, laptops,
workstations ,etc.

igadoter · 07-11-2009, 04:23 AM

Quote:

Originally Posted by janhe

What does it say after the kernel panic?

The most often seen error is "cannot mount sda2" or something like that.

The exact error message might give another clue about the problem.

As for me the kernel when it is launching does not create necessary
/dev entry in the system. I mean that a USB stick is clearly visible
for the kernel, USB is recognized as SCSI device the name say sdc
is given but it seems that the /dev/ entry is created after
the root device is mounted.

Perhaps the solution is how to say to the kernel that /dev/
entry for usb should be created before mounting the root?

Before the kernel panic the kernel lists the possible devices
where the root can be placed. There are appears the ide-disks,
sata hardisks, cd-roms. No usb.