[Rear-users] problem loading network driver with firmware

Joerg Schum joerg.schum at gmx.de
Wed Oct 27 12:37:29 CEST 2010

i have to implement ReaR as a disaster recovery solution on some servers 
running SLES11-64 SP1.
Server: HP Prolient DL580 G5
Networkadapter: HP NC373T PCIe Multifunktion Gigabit Server Adapter

I have tested with rear version 1.7.25-1 as also with version 
rear-snapshot-0.0.0152-3.1 from the 1.9 trunk.

The result in booth versions are the same.
After booting from the recovery ISO the system is not able to load the 
network driver. The driver (bnx2) seems to need load some firmware.

this is what i got when booting the recovery system:


waiting for udev  . . .   (this takes a very long time)

After the udevadm settle timeout, the eventqueue contains:

1845: /devices/pci000. . . . . ./firmware/000:08:00:0
1851: /devices/pci . . . . . . .
1853: /devices/pci . . . . . .

Host XXXXXXXXX using Backup NETFS and Output ISO
the program '/bin/bash' called 'udevsettle', it should use 'udevadm settle
<options>, this will stop working in a future release

Running 55-migrate-network-devices.sh . . .

the original network device eth0 00:11:22:33:44:55 is not available.
Please select another device:
1) Skip replacing the network device
                 Choose the network device to use:


This machine has 4 identical Network adapters. None of them are loading 
in the recovery environment.

At the same time i got this in /var/log/messages .....


Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v2.0.4 (Mar 03, 2010)
bnx2 0000:06:00.0: PCI INT A - GSI 16 (level, low) -> IRQ16
bnx2: can't load firmware file "bnx2/bnx2-mips-06-5.0.0.j6.fw"
bnx2 0000:06:00.0: PCI INT A disabled
bnx2: probe of 0000:06:00.0 failed with error -2


BTW: this are the same messages, as in rear version 1.7.25-1 where the 
driver tried to load with 'modprobe bnx2'

ahhhh, i have found the point where you load the driver ... :-)
in the /etc/udev/rules.d/00-rear.rules   you do a modprobe ...

I am not familiar with udev, but isn't it so, that if the 1'st rule 
matches then the others aren't read?

The normal way, the firmware would load, was in 
there was an entry

# firmware class requests
SUBSYSTEM=="firmware", ACTION=="add", RUN+="firmware.sh"

the script 'firmware.sh' was located in /lib/udev and is also available 
in the ISO. This should load the firmware.

So please is it possible to modify the driver load behavior in the ISO 
image so, to make it possible to load drivers with firmware?

Or is there someone with other Ideas who can point me to another way to 
make it possible to restore my original Servers


More information about the rear-users mailing list