Close, but has issues in postinstall. SuSE Pro 9.2 uses bcm5700 for install, after the first reboot just before my post install script runs tg3 is loaded somewhere. The code below does not prevent tg3 from being loaded, but also loads bcm5700, however it is tg3 that is being used. Other attempts to alter files in the post install yield the same result. i.e. I must reboot again after post install to get bcm5700. The problem is that I have code in the post install that must use the NIC. Attempts to unload the tg3 and load the bcm5700 in post install hang the system because tg3 is in use for NFS install. I think I need to remove tg3 from the install code. It is being autodetected and used after the first reboot before postinstall.

-----Original Message----- From: Andreas.Matthieu@tfa.brandenburg.de [mailto:Andreas.Matthieu@tfa.brandenburg.de] Sent: Friday, February 11, 2005 12:45 AM To: egan@sense.net; suse-autoinstall@suse.com Subject: AW: [suse-autoinstall] SuSE Pro 9.2 tg3 vs bcm5700

Hi,

...

I am having problems with tg3 and must use bcm5700 with SuSE Pro 9.2, how do I tell autoyast not to use tg3 for install or runtime?

you must specify bcm5700 module for the eth0 config. Try the following example: For device you can also specify: - interface: <device>eth-id-MAC</device> - module: <device>bus-pci-DEVICE-ID</device>

<?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <networking> <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>static-0</device> <module>bcm5700</module> <options></options> </module_entry> </modules> </networking> </configure> </profile>

Regards,

Andreas Matthieu

-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com