on SLES10 SP2 the bnx2 driver has the problem, that it takes ages (up to 60s) for it to raise up the network device. Until then, no network is available. That can disturb the automatic installation. First of all, if your installation source is on a network device, YaST can not connect that installation source. That issue was fixed for SP2 (see
bugzilla).
Still there are problems when you have init-scripts with a <location>
that requires network (like HTTP, FTP,...) because after configuring the network device by autoyast, it takes another 60 seconds to raise the device and the <location> is evaluated after the network configuration. As a workaround you have to add an inline post-script that waits for 60 seconds:
<scripts>
<post-scripts config:type="list">
<script>
<network_needed config:type="boolean">false</network_needed>
<filename>wait.sh</filename>
<interpreter>shell</interpreter>
<source><![CDATA[
sleep 60
]]>
</source>
</script>
</post-scripts>
<init-scripts config:type="list">
<script>
<location>http://.....</location>
...
</script>
</init-scripts>
</scripts>
that script will wait 60 seconds and then network should be available and the remote init-scripts can be fetched.If you need network in your init-script too, then you have to wait again for 60 seconds or so in your init-script.
I know, that sucks but the driver is broken and the description above is just a workaround for a broken network device driver.
1 comment:
Interesting story as for me. I'd like to read something more about this topic. The only thing that blog needs is some pictures of some devices.
David Trider
Cell phone blocker
Post a Comment