Steffen Winterfeldt wrote
'insmod' was there to load modules that were (for whatever reason) not loaded automatically.
But that wasn't the intenton two years ago: -------- Original Message -------- Subject: Re: [opensuse-autoinstall] SuSE 10.1 autoyast and scsi device order Date: Tue, 22 May 2007 16:25:40 +0200 (CEST) From: Steffen Winterfeldt <snwint@suse.de> Steffen Winterfeldt wrote
starting with sles10, 'insmod=' options passed at the kernel command line are evaluated _before_ hardware detection.
So I guess it was intended exactly for what some of use used it: Force modules to be loaded before the system loads them automatically. I don't understand why udev must now run before?
My current problem is that the card reader devices fetch sda-sdd and the SATA disk is sde. I need the SATA disk to be sda and I can't start
You should really not rely on specific device names. The kernel does not guarantee a defined initialization order.
Not in theory, but in practice :-) I've heared this argument so many times over the last about 5 years, but when you ensure that the module of the hard disk you want to be the first one is loaded as first module, you will always get the disk with the first id of this controller as first hard disk. No controller is ever changing the order of its attached hard disks. We have IBM pSeries, Sun X2200 and X4100, IBM x335 and x345 and over 60 desktop clients from Tarox, HP, FSC, IBM and noname manufacturers. All of those are installed with the same autoyast profile, using "hda" or "sda" for partitioning. And with SLES10 we ensured that the right hard disk was always sda and hda with only three different pxelinux.cfg files. This just works great for us and our 150 hosts.
What is the 'main disk' for you? The one you will boot from? Then maybe /dev/disk/by-id/edd-int13_dev80 is a way.
We have enough PCs where this does not work, e.g. because the bios is too old or to restricted to list certain devices. And a bunch of problematic ASUS bioses which just have problem managing IDE and SCSI in parallel. Using the "load this module first, take sda/hda" always works.
So how can we ensure the sata disk is detected before the USB devices?
AFAIK, you can't (in a sensible way). If it's any help to you, you can get back the pre-SLES11/11.1 behavior with 'linuxrc.debug=-udev.mods' which will turn off module loading in udevd and linuxrc takes care again.
This definitely helps! Thanks! I know that you are all following the "clean" way that the kernel developers bring up, but the nice thing of Linux has always been that it was a Linux box and not an iPhone that I was managing, so I could always override the "good clean" way and hack all the dirty stuff, no matter how stupid it might look to others :-) Maybe you can return the now inofficial debug-feature into an official (so that we are sure it's kept) "let the user do whatever he wants" feature for SLES12. E.g. a linuxrc option "preins=e100" which loads the e100 module before *any* other module is loaded, so I can force linuxrc to use e100 instead of e1000. It wouldn't hurt to have an additional option, would it? But it would help those of us hackers who are just happy with the good old way. I don't know how to translate this, but when my kids play they often say "Ich bin jetzt mal der Bestimmer!" And that's what I want to be when I install Linux. I don't want to let udev take decisions for me that I can't override... Thanks for the debug option! And please think about a "preins" or sth :-) cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. * -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org