Volkmar Glauche wrote:

On Tue, 29 Jul 2003, dfroehling wrote:

...

So I'm back at the beginning: How can I tell autoyast to load module eepro100 from modules3 disk? If I enter this at the bootprompt it will be ignored.

Why don't you let yast autoprobe your network card? Just give the network installation source/autoyast configuration location with something like

install=nfs://...

and let yast figure out itself that it needs a network card driver. This works great for me (also with onboard e100).

This was my very first version. But after booting from the SuSE bootdisk it asks for modules1 and loads some usb and so on from it. The next thing is starting hardware detection. After that it tells me that it can't find the installation configuration and switches to manual mode. There I can select to install network drivers and then it asks for modules3. The problem is: all the hundreds of machines for the next years will have no cdrom and only a floppy drive. From cdrom it wouldn't be a problem. But then a technician has to open the computer, connect a cdrom drive...

CU

Dierk

Volkmar Glauche wrote:

On Wed, 30 Jul 2003, dfroehling wrote:

...

...

install=nfs://...

and let yast figure out itself that it needs a network card driver. This works great for me (also with onboard e100).

This was my very first version. But after booting from the SuSE bootdisk it asks for modules1 and loads some usb and so on from it. The next thing is starting hardware detection. After that it tells me that it can't find the installation configuration and switches to manual mode.

Hmm. I am not sure, but for me I think it asked during boot. Do you also have

autoyast=nfs://...

in your command line? Otherwise you may be able to change modules1 (replace some unneeded modules in its initrd with the ones you need and adjust module.config - I haven't tried this for myself, but it might work). Here's an outline on how to do this:

1. loop mount the modules1 image
2. copy initrd out of this image
3. rename copy of initrd to initrd.gz and gunzip it
4. loop mount resulting initrd

... now you can change things in initrd and then put the new gzipped initrd back into the modules1 image

I tried it now in a similar way: 1.) read from bootdisk syslinux.cfg with mcopy 2.) modify it to default: installation and timeout infinite 3.) copy it back to boot disk (This is done, because I want to enter at boot prompt ip=192.168.255.xxx (whatever I need) and hostname=mynewhostname (this parameter is used by my pre install script)) 4.) mcopy from modules3 disk net-modules 5.) rename it to net-modules.gz 6.) gunzip it 7.) mount it as root with: mount -o loop net-modules mountpoint1 8.) mcopy from modules1 disk module.config and initrd 9.) rename initrd to initrd.gz 10.) gunzip it 11.) mount it as root with: mount -o loop initrd mountpoint2 12.) do as root cp mountpoint1/mii.o mountpoint2/modules/ 13.) do as root cp mountpoint1/eepro100.o mountpoint2/modules/ 14.) edit as root mountpoint2/modules/module.config by adding:

mii,,-,,,1,1 eepro100,,-,mii,,1,1

to the autoload section 15.) copy your info file to mountpoint2 example:

Language: de_DE Keytable: de-lat1-nd Install: nfs://192.168.255.12/kurzbackup/autoyast/dvd InstMode: nfs Netmask: 255.255.255.0 Netdevice: eth0 Domain: office.aycan.de AutoYaST: tftp://192.168.255.12/config AddSwap 1 Insmod: mii Insmod: eepro100

16.) umount mountpoint2 17.) gzip -9 initrd 19.) rename it to initrd and copy it back to modules1 19.) edit module.config (see #8) by adding:

[autoload] MoreModules=initrd ModDisk=1

mii,,-,,,1,1 eepro100,,-,mii,,1,1

as a new section 20.) copy module.config back to modules 21.) use these lines in your pre install script to get your commandline hostname:

/bin/hostname $(/bin/cat /proc/cmdline | /usr/bin/tr [:space:] "\n" \ | /bin/grep ^hostname | /usr/bin/cut -d "=" -f 2)

This works for me without dhcp and I can set ip-address and hostname at boot time. Maybe modification of one of the 2 module.config is not needed and also explicit insmod in info file isn't needed, but it works. Now I have to have a look at the strange partitioning behaviour of autoyast (every second partition is dropped).

CU

Dierk