[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#522206: marked as done (firmware-bnx2: Unable to use bnx2 firmware (.15) in modern kernels (5709 card))

Your message dated Fri, 23 Oct 2009 04:58:52 +0100
with message-id <1256270332.3916.172.camel@localhost>
and subject line Re: firmware-bnx2: Unable to use bnx2 firmware (.15) in modern kernels (5709 card)
has caused the Debian Bug report #522206,
regarding firmware-bnx2: Unable to use bnx2 firmware (.15) in modern kernels (5709 card)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
522206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522206
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: firmware-bnx2
Severity: important


Hi, I'm currently setting up some new Dell Poweredge 1950 servers that
happen to use the Broadcom 5709 GigE cards.  I've set up similiar
poweredge servers in the past that also used bnx2 cards, and have had a
similiar issue.

Here's what happened from the perspective of a Debian user doing a fresh
install(I apologize if this may be a bit hazy, as I've been rapidly trying out
different configurations to see what sticks but you'll get the idea):

- Grabbing stable netinstall, followed by weekly build netinstall
- Later trying out stable CD1

-- Depending on the installer, they either will not recognize the
existance of a card at all (older installers), or will ask for the
driver off of removable media.  I threw the firmware-bnx2 file on a USB
key, which was recognized, and then after going through network setup I
would get fun results like "Autoconfiguration succeeded" immediately
followed by "Network config failed" and no resulting net connection.
This may be an installer issue more then a firmware issue, but I'm not
sure.

- Tried many variations of .26 to .29 linux-images (amd64) with the current
firmware-bnx2 packages. (.15 and .14). Some would load the module, but
I could not get any to work as-is.

- Eventually I grabbed my known working 2.6.26-1-amd64 and 0.13~bpo40+1
firmware-bnx2 debs and installed them (off of the usb key) after having
done a networkless debian install.  And, suddenly the network interfaces
are working again.  Note that I cannot use this old bnx package with any
newer kernels past .26 as of this time.

What I'm curious from a usability standpoint is why the old .13 firmware
package seems to be the only one to work, and why the newer kernels+bnx
firwmare in the archive don't seem to have the support that older
versions did.  This seems to be a widespread issue according to what
I've been able to dig up via Google, and there must be a solution taht
Debian can offer.  Either by re-doing the firmware package or by
including some useful documentation with the package?  I unfortunately
don't have the answer, just my own experiences and a package that seems
to hold what I need but won't actually work as-is without significant
hoop-jumping.

My current solution is to compile a newer kernel from source and compile
in the broadcom drivers directly from their site.  But that of course
doesn't help other Debian users who I'm sure are relying or would like
to be able to use this package as advertised on their new hardware.
Preferably directly from the installer (and the installer recognizing
the debs from a USB key is a huge step that never worked before for me, so
congratulations to whoever pulled that off)

If there's anything I can do to help, like compiling or testing out
newer firmware package versions under the requisite hardware and newer
kernels, please let me know.  This has been a major headache, and I know
it would be handy to have support for one of Dell's more common NICs work
smoothly.

Thanks for your time.

- Erik

--- End Message ---
--- Begin Message --- 
I believe this was fixed by a kernel update.

Ben.

-- 
Ben Hutchings
If God had intended Man to program,
we'd have been born with serial I/O ports.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: