If you have a Dell server, dump it, or keep reading 😉
Well… to me it sounds like some copyright crap Broadcom is pulling, or perhaps Debian is trying to be more compliant with restricted drivers. Three ways I can think of to work around this:
- Download the deb package from http://packages.debian.org/etch/firmware-bnx2, copy it to a flash drive and insert when prompted during installation. You don’t have to mount anything… install process will automatically find and load the driver. Do not unpack the .deb package, copy it to your USB drive without any modifications. OS will access the file and extract what it needs accordingly.
- Install an old or supported NIC (Intel?) and proceed with installation. Once it’s done install the deb package and restart networking.
- Install without a NIC, then download and copy the file to a flash drive or CD, mount and install. Just make sure you’re not using Debian NetInst CD!
One of the readers suggested that I should also post a link to the page where different versions of the driver can be downloaded http://packages.debian.org/search?searchon=names&keywords=bnx2.
Updated Feb 18th 2010 by Mark (comment reply):
To the people struggling with BCM5716: Even the latest Lenny 5.0.4 stable installer (with kernel 2.6.26-2 rev 21lenny3) doesn’t yet have the PCI IDs required to load the drivers. Here is some useful info:
I’ve just spent the last 2 days working out how to roll my own Debian installer image with a patched kernel. All this work just to get some tiny changes into bnx2.ko and preseed the firmware
I’ve uploaded working Debian Lenny netinstall images:
Note: For anybody just looking for an install image containing the bnx2 firmware, this is for you too. Well, it works for me – YMMV.
btw, the next point release (5.0.5) of Lenny will work without any of these problems.”