Hello All! In short: I need to integrate an HP-delivered DUD in my network-based autoyast-configuration with loopback mounted installation sources. Here's the whole story (sorry for the lengthy description): I have an existing environment with a PXE-server and an autoyast install server. I have to install some HP blades (460c G6) with a FLEX10 emulated NIC that needs a newer version of kernel module bnx2x than provided by the SLES10SP2 initrd. Concerning the initrd, I replaced the initrd on the PXE-server with the one provided by HP according to : << http://h18006.www1.hp.com/products/servers/management/rdp/knowledgebase/0000... 197.html>> The installation is started from pxelinux.cfg/default with the following lines: --snip label auto10sp2_x86_64 menu label SLES10 SP2 (64 Bit) Automatische Installation kernel sles10sp2_x86_64/linux append initrd=sles10sp2_x86_64/initrd ramdisk_size=131072 vga=791 splash=0 install=http://myserver.mydomain/inst_srv/SLES10_x86_64/SUSE-SLES-10-Service- Pack-Version-2/DVD1 textmode=1 lang=de_DE autoyast=http://myserver.mydomain/inst_srv/autoyast/sles10sp2_x86_64-default/ --snap So far everything works fine, the first stage of the autoyast installation runs without problems. Now I have to tell autoyast to use the HP-provided Driver Update Disk to install the module to the installed system. HP delivers a file that is to be renamed to "driverupdate" and to be placed in the installation source. The installation source consists of loopback mounts of the SLES10-DVDs. The Problem is, that autoyast seems to look for the file "driverupdate" which is the root of DVD1. Since this is an ISO9660 I can't place the file there. When I copy the whole DVD to the filesystem of the install server an put the driverupdate there, the installation works, but since disk space is an issue on my install server, this is not a long term solution. Now I was playing around with some ways to change the path to driverupdate. 1) I tried to hand over some command line options to the kernel, like "dud=http://myserver...." Or "driverupdate=http://myserver....", like described in << http://en.opensuse.org/Linuxrc#p_dud>> but none of them worked. Then I found << http://www.suse.de/~ug/autoyast_doc/info_file_format.html>> stating no "dud" or "driverupdate" parameter. Hm,...? 2) I tried to put the info file section in my autoyast profile like in 7.3.3 of << http://www.suse.de/~ug/autoyast_doc/invoking_autoinst.html#id339566>> but that also didn't work: --snip <init> <![CDATA[ # # Don't remove the following line: # start_linuxrc_conf install=http://myserver.mydomain/inst_srv/SLES10_x86_64/SUSE-SLES-10-Service- Pack-Version-2/DVD1 dud: http:// myserver.mydomain /inst_srv/SLES10_x86_64/SUSE-SLES-10-Service-Pack-Version-2/driverupdate # end_linuxrc_conf # Do not remove the above comment # ]]> </init> --snap As far as I understood, linuxrc looks for the info file but if this fails it looks for additional parameters on the kernel commandline. Could it be that "dud" or "driverupdate" isn't supported in SLES10SP2? Do I have to look for a bug in the HP initrd? I looked inside the initrd, but can't seem to find any file named "info". Any hints or experiences with that topic? Greetz Thomas -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org