-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Phil Oester wrote: > Can anyone explain the ethernet probe order anaconda uses? In poking around the > code I found mention of sorting the modules alphabetically and loading in that > order, but I haven't found that to be true. I would expect PCI bus order, but > that hasn't happened either. <snip> > Anaconda ends up inserting modules in this order: > > * inserted /tmp/e100.ko > * inserted /tmp/tg3.ko > * inserted /tmp/e1000.ko > > Which is neither alphabetically or PCI bus order. Any ideas? Phil, If you are looking to control selected device drivers then please look at what Ronald Reed found around 5/4/2005: Ronald Reed wrote: >> This is what I have found so far: >> >> If you need a device parameter in your kickstart file, and you need more >> than 1 module loaded, then separate them with a colon ":". Example: >> >> device scsi aacraid:megaraid:aic7xxx So do you want, say, device eth e1000:tg3:e100 so that the devices are probed in this order? "On most PCI systems, the installation program will autoprobe for Ethernet and SCSI cards properly. On older systems and some PCI systems, however, kickstart needs a hint to find the proper devices. The device command, which tells the installation program to install extra modules... http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/custom-guide/s1-kickstart2-options.html Greg -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFDI5Jsxyxe5L6mr7IRAhuFAJ4qgcR1hvVhXrh4Zr67XElK+m2d0QCePTJU zh+OkbzI+YvSXZSyj1eUSNk= =/yMF -----END PGP SIGNATURE-----
