[Bug 44911] Re: Broadcom wireless: ifconfig eth1 up result in hard-lockup

Andy Brook javahollic at gmail.com
Wed May 17 07:34:56 UTC 2006


Ive just dist-upgraded to catch all updates as of May17:

I ran the script again, it did its stuff and added files to
/lib/firmware as before.  If the firmware is in place (using the script)
and I do ifconfig eth1 up, I get an immediate hardware lockup.  If the
firmware isn't in place I get 'SIOCSIFFLAGS: No such file or directory'.

Using ndiswrapper I can load up the 64bit netbc564 driver but still
cannot get eth1 up, it results in the same error as above.  I wonder if
this boils down to an incompatibility with bcm43xx firmware and the
hardware I have '564'? different family or is it basically the same?  I
checked iwconfig, and it lists the device as a "Broadcom 4306" without
ndiswrapper drivers registered or firmware loaded into /lib/firmware -
so perhaps it is natively compatibile - so why this problem?

-- 
Broadcom wireless: ifconfig eth1 up result in hard-lockup
https://launchpad.net/bugs/44911




More information about the kernel-bugs mailing list