Bug#638921: firmware-netxen: HP NC375i network card fails to autonegotiate with a 100full cisco switch
Hello Ben, thanks for the reply.
>Right, if autonegotiation fails then it is possible for 'parallel
>detection' to establish a 100HD link. The question is why autoneg
>failed.
I concur. I suspect the driver.
I should mention that this sounds like a similar issue:
http://h30499.www3.hp.com/t5/Networking/Problem-with-NC375i-and-NC375T-on-Re
dHat-Linux5/td-p/4712102
I assume nx_nic drivers are in nx3fwct.bin and phanfw.bin contains the
netxen_nic drivers. I guess the installer overrides nx3fwct.bin if it
finds phanfw.bin because lsmod has only shown netxen_nic drivers loaded
in both of my install attempts.
I suppose I could try deleting phanfw.bin from my removable media to leave
only nx3fwct.bin there and see what happens with the different drivers.
>When you say that the installation failed, do you mean that you
>were unable to complete the installation, or that the installation
>was broken because it could not set up the network connection?
Sorry for that ambiguity. The installer ran fine to completion. I meant
"failed" in the sense that end result was that the NIC card still failed to
autonegotiate after rebooting after installation.
Thanks
======================================
On Mon, Aug 22, 2011 at 06:53:44PM -0400, Michael Mastrogiacomo wrote:
> Package: firmware-netxen
> Version: 0.28
> Severity: critical
> Justification: breaks the whole system
>
> The HP NC375i network card on an HP ML370 G6 server with Debian
> squeeze OS installed as problems.
> The server is connected to a switch that does only 100/full and it
> fails to autonegotiate correctly during reboot. A network
> connection can be used if the switch side gets locked to 100 half
> however which seems to be what the HP card assumes if negotiaton
> fails.
Right, if autonegotiation fails then it is possible for 'parallel
detection' to establish a 100HD link. The question is why autoneg
failed.
[...]
> A perhaps related issue is that during install nx3fwct.bin is
> requested by the installer but are not available in the non-free zip
> file.
The file phanfw.bin should also work, and I understand that this
is the preferred firmware file.
> I tried 2 different installs, both which failed; one involved
> skippin that file during the install by just hitting next at the
> installer prompt; the other way involved extracting the file from an
> rpm provided for redhat installs...I got that RPM from the HP
> website, hp-nx-nic-tools_4.0_520-6_all.rpm
When you say that the installation failed, do you mean that you
were unable to complete the installation, or that the installation
was broken because it could not set up the network connection?
If the installation failed, you should report a bug against
'installation-reports'.
If the installation is broken, does the installed system actually have
the package firmware-netxen installed?
Ben.
-----Original Message-----
From: Ben Hutchings [mailto:ben@decadent.org.uk]
Sent: Monday, August 22, 2011 8:36 PM
To: Michael Mastrogiacomo; 638921@bugs.debian.org
Subject: Re: Bug#638921: firmware-netxen: HP NC375i network card fails to
autonegotiate with a 100full cisco switch
On Mon, Aug 22, 2011 at 06:53:44PM -0400, Michael Mastrogiacomo wrote:
> Package: firmware-netxen
> Version: 0.28
> Severity: critical
> Justification: breaks the whole system
>
> The HP NC375i network card on an HP ML370 G6 server with Debian
> squeeze OS installed as problems.
> The server is connected to a switch that does only 100/full and it
> fails to autonegotiate correctly during reboot. A network
> connection can be used if the switch side gets locked to 100 half
> however which seems to be what the HP card assumes if negotiaton
> fails.
Right, if autonegotiation fails then it is possible for 'parallel
detection' to establish a 100HD link. The question is why autoneg
failed.
[...]
> A perhaps related issue is that during install nx3fwct.bin is
> requested by the installer but are not available in the non-free zip
> file.
The file phanfw.bin should also work, and I understand that this
is the preferred firmware file.
> I tried 2 different installs, both which failed; one involved
> skippin that file during the install by just hitting next at the
> installer prompt; the other way involved extracting the file from an
> rpm provided for redhat installs...I got that RPM from the HP
> website, hp-nx-nic-tools_4.0_520-6_all.rpm
When you say that the installation failed, do you mean that you
were unable to complete the installation, or that the installation
was broken because it could not set up the network connection?
If the installation failed, you should report a bug against
'installation-reports'.
If the installation is broken, does the installed system actually have
the package firmware-netxen installed?
Ben.
--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus
Reply to: