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

Re: No network interface detected



On Mon, Apr 11, 2011 at 01:07:55PM +0530, Ravi Roy wrote:
> I have included the firmware in initrd and repacked the same as mentioend
> under http://wiki.debian.org/Firmware
> and recreated the ISO. After installation I see the following :
> 
> user@myhost:/$ <myhost@noiclt22572:/$> dmesg | grep bnx2
> [    1.406185] Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v2.0.3
> (Dec 03, 2009)
> [    1.406212] bnx2 0000:04:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
> [    1.406536] bnx2 0000:04:00.0: firmware: requesting
> bnx2/bnx2-mips-06-5.0.0.j3.fw
> [    1.420742] bnx2 0000:04:00.0: firmware: requesting
> bnx2/bnx2-rv2p-06-5.0.0.j3.fw
> [    1.424689] bnx2 0000:06:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> [    1.425081] bnx2 0000:06:00.0: firmware: requesting
> bnx2/bnx2-mips-06-5.0.0.j3.fw
> [    1.430974] bnx2 0000:06:00.0: firmware: requesting
> bnx2/bnx2-rv2p-06-5.0.0.j3.fw
> [    9.447544] bnx2 0000:04:00.0: irq 34 for MSI/MSI-X
> [    9.552008] bnx2: eth0: using MSI
> [    9.560738] bnx2 0000:06:00.0: irq 35 for MSI/MSI-X
> [    9.657533] bnx2: eth1: using MSI
> [   12.720974] bnx2: eth1 NIC Copper Link is Up, 1000 Mbps full duplex,
> receive & transmit flow control ON
> [   12.818878] bnx2: eth0 NIC Copper Link is Up, 1000 Mbps full duplex
> and drivers are installed and link is operational, but at the time of
> installation it just says 'no network interface is detected', at this point
> I have press continue and everything is okay.
> 
> As this error message is annoying How can is tackle this ? Any suggestion ?

You are probably hitting the other bug a few people have hit that some
gigabit ports are slow to come up and the network detection code is much
too impatient to wait for the link to be ready.  I remember a number of
people reporting this a few months ago.

Other than retrying the network detection step (which I guess preseed
can't do), I don't know a workaround.

-- 
Len Sorensen


Reply to: