linux-kernel - bcm43xx from 2.6.20-rc1-mm1 on HPC nx6325 (x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <458C1633.1040606@lwfinger.net>
Date:	Fri, 22 Dec 2006 11:30:27 -0600
From:	Larry Finger <Larry.Finger@...inger.net>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
CC:	LKML <linux-kernel@...r.kernel.org>,
	bcm43xx devel <Bcm43xx-dev@...ts.berlios.de>,
	netdev <netdev@...r.kernel.org>
Subject: bcm43xx from 2.6.20-rc1-mm1 on HPC nx6325 (x86_64)

I'm trying to make the bcm43xx driver out of the 2.6.20-rc1-mm1 kernel work on
an HPC nx6325, with no luck, so far, although I'm using a firmware that has
been reported to work with these boxes
(http://gentoo-wiki.com/HARDWARE_Gentoo_on_HP_Compaq_nx6325#Onboard_Wireless_.28802.11.29).

The driver loads and seems to operate the hardware to some extent, but there
seems to be a problem with interrupts. Namely, the chip doesn't seem to
generate any.
Raphael J. Wysocki wrote:

 > Right after a fresh 'modprobe bcm43xx' I get the following messages in dmesg:

 > bcm43xx driver
 > ACPI: PCI Interrupt 0000:30:00.0[A] -> GSI 18 (level, low) -> IRQ 18
 > PCI: Setting latency timer of device 0000:30:00.0 to 64
 > bcm43xx: Chip ID 0x4311, rev 0x1
 > bcm43xx: Number of cores: 4
 > bcm43xx: Core 0: ID 0x800, rev 0x11, vendor 0x4243
 > bcm43xx: Core 1: ID 0x812, rev 0xa, vendor 0x4243
 > bcm43xx: Core 2: ID 0x817, rev 0x3, vendor 0x4243
 > bcm43xx: Core 3: ID 0x820, rev 0x1, vendor 0x4243
 > bcm43xx: PHY connected
 > bcm43xx: Detected PHY: Version: 4, Type 2, Revision 8
 > bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
 > bcm43xx: Radio turned off
 > bcm43xx: Radio turned off
 > PM: Adding info for No Bus:eth1
 > printk: 3 messages suppressed.
 > SoftMAC: ASSERTION FAILED (0) at: > 
net/ieee80211/softmac/ieee80211softmac_wx.c:306:ieee80211softmac_wx_get_rate()
 >
 > but, strangely enough, eth1 does not appear, but eth2 appears instead:
 >

Usually the problem generates an oops, but I think your problem is due to the changes in the work 
struct in 2.6.20-rc1. There is a fix in the pipeline, but it has not propagated through the system.

You should apply the work_struct2 patch attached. If your computer has a switch to kill the RF, you 
may also wish to apply the radio_hwenable patch, which should cause the radio LED to be turned on.

The selection of eth2 rather than eth1 is probably due to the rules in 
/etc/udev/rules.d/30-net_persistent_names.rules. When I boot a softmac version, my bcm43xx device is 
wlan0, but when I boot the d80211 version, it is eth1. I have a second bcm43xx card, which becomes 
eth2 under softmac.

Larry

View attachment "work_struct2" of type "text/plain" (2017 bytes)

View attachment "radio_hwenable" of type "text/plain" (5799 bytes)