* b43 'hardware blocked' but only keyboard/led touch button
@ 2010-03-29 20:12 Philippe De Muyter
2010-03-29 23:10 ` Larry Finger
0 siblings, 1 reply; 22+ messages in thread
From: Philippe De Muyter @ 2010-03-29 20:12 UTC (permalink / raw)
To: linux-wireless
Hello wireless-linux experts,
I have installed yesterday the last opensuse 11.3 rc4 on a
hp pavilion dv6-1300sb laptop which is has a
02:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)
as wireless chip.
I needed to install such a bleeding edge distro because opensuse 11.2 does
not have the lp_phy driver yet.
with dmesg, I see :
[ 21.818415] b43 ssb0:0: firmware: requesting b43/ucode15.fw
[ 21.820519] b43 ssb0:0: firmware: requesting b43/lp0initvals15.fw
[ 21.823084] b43 ssb0:0: firmware: requesting b43/lp0bsinitvals15.fw
[ 21.975380] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
[ 22.076456] b43-phy0: Radio hardware status changed to DISABLED
[ 22.077743] b43-phy0: Radio turned on by software
[ 22.077747] b43-phy0: The hardware RF-kill button still turns the radio physically off. Press the button to turn it on.
[ 22.078413] ADDRCONF(NETDEV_UP): wlan0: link is not ready
this is confirmed by rfkill :
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
BUT, I DON'T SEE A HARDWARE RF-KILL button; I only see a red-lighted wireless
symbol, which is also a touch-key; in console mode, when I touch this
touch-key I get a message asking me to
'setkey e014 <keycode>'
I have already seen this symbol being blue-lighted in the first seconds of
linux booting, but I don't know what changes this color or if this has
an effect on the 'hardware' RF-kill button. In the BIOS there is no option
to enable or disable the wireless interface.
Any hint ?
Thanks already for the good work so far
Philippe
^ permalink raw reply [flat|nested] 22+ messages in thread* Re: b43 'hardware blocked' but only keyboard/led touch button 2010-03-29 20:12 b43 'hardware blocked' but only keyboard/led touch button Philippe De Muyter @ 2010-03-29 23:10 ` Larry Finger 2010-03-30 7:34 ` Philippe De Muyter 0 siblings, 1 reply; 22+ messages in thread From: Larry Finger @ 2010-03-29 23:10 UTC (permalink / raw) To: Philippe De Muyter; +Cc: linux-wireless On 03/29/2010 03:12 PM, Philippe De Muyter wrote: > Hello wireless-linux experts, > > I have installed yesterday the last opensuse 11.3 rc4 on a > hp pavilion dv6-1300sb laptop which is has a > > 02:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01) > > as wireless chip. > > I needed to install such a bleeding edge distro because opensuse 11.2 does > not have the lp_phy driver yet. > > with dmesg, I see : > > [ 21.818415] b43 ssb0:0: firmware: requesting b43/ucode15.fw > [ 21.820519] b43 ssb0:0: firmware: requesting b43/lp0initvals15.fw > [ 21.823084] b43 ssb0:0: firmware: requesting b43/lp0bsinitvals15.fw > [ 21.975380] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) > [ 22.076456] b43-phy0: Radio hardware status changed to DISABLED > [ 22.077743] b43-phy0: Radio turned on by software > [ 22.077747] b43-phy0: The hardware RF-kill button still turns the radio physically off. Press the button to turn it on. > [ 22.078413] ADDRCONF(NETDEV_UP): wlan0: link is not ready > > this is confirmed by rfkill : > > 0: phy0: Wireless LAN > Soft blocked: no > Hard blocked: yes > > BUT, I DON'T SEE A HARDWARE RF-KILL button; I only see a red-lighted wireless > symbol, which is also a touch-key; in console mode, when I touch this > touch-key I get a message asking me to > > 'setkey e014 <keycode>' > > I have already seen this symbol being blue-lighted in the first seconds of > linux booting, but I don't know what changes this color or if this has > an effect on the 'hardware' RF-kill button. In the BIOS there is no option > to enable or disable the wireless interface. > > Any hint ? > > Thanks already for the good work so far Is the module hp-wmi loaded? That module is designed to implement all of the special keys for HP laptops. Larry ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: b43 'hardware blocked' but only keyboard/led touch button 2010-03-29 23:10 ` Larry Finger @ 2010-03-30 7:34 ` Philippe De Muyter 2010-03-30 16:47 ` Dan Williams 0 siblings, 1 reply; 22+ messages in thread From: Philippe De Muyter @ 2010-03-30 7:34 UTC (permalink / raw) To: Larry Finger; +Cc: linux-wireless Hello Larry, On Mon, Mar 29, 2010 at 06:10:23PM -0500, Larry Finger wrote: > On 03/29/2010 03:12 PM, Philippe De Muyter wrote: > > Hello wireless-linux experts, > > > > I have installed yesterday the last opensuse 11.3 rc4 on a > > hp pavilion dv6-1300sb laptop which is has a > > > > 02:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01) > > > > as wireless chip. > > > > I needed to install such a bleeding edge distro because opensuse 11.2 does > > not have the lp_phy driver yet. > > > > with dmesg, I see : > > > > [ 21.818415] b43 ssb0:0: firmware: requesting b43/ucode15.fw > > [ 21.820519] b43 ssb0:0: firmware: requesting b43/lp0initvals15.fw > > [ 21.823084] b43 ssb0:0: firmware: requesting b43/lp0bsinitvals15.fw > > [ 21.975380] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) > > [ 22.076456] b43-phy0: Radio hardware status changed to DISABLED > > [ 22.077743] b43-phy0: Radio turned on by software > > [ 22.077747] b43-phy0: The hardware RF-kill button still turns the radio physically off. Press the button to turn it on. > > [ 22.078413] ADDRCONF(NETDEV_UP): wlan0: link is not ready > > > > this is confirmed by rfkill : > > > > 0: phy0: Wireless LAN > > Soft blocked: no > > Hard blocked: yes > > > > BUT, I DON'T SEE A HARDWARE RF-KILL button; I only see a red-lighted wireless > > symbol, which is also a touch-key; in console mode, when I touch this > > touch-key I get a message asking me to > > > > 'setkey e014 <keycode>' > > > > I have already seen this symbol being blue-lighted in the first seconds of > > linux booting, but I don't know what changes this color or if this has > > an effect on the 'hardware' RF-kill button. In the BIOS there is no option > > to enable or disable the wireless interface. > > > > Any hint ? > > > > Thanks already for the good work so far > > Is the module hp-wmi loaded? That module is designed to implement all of the > special keys for HP laptops. > > Larry No, thanks for the suggestion. Here is the log of my attempt : $ modprobe hp-wmi FATAL: Error inserting hp_wmi (/lib/modules/2.6.33-6-desktop/kernel/drivers/platform/x86/hp-wmi.ko): No such device and there is nothing in dmesg. If that can help, here is the output of lspci : 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03) 00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.3 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03) 00:1f.6 Signal processing controller: Intel Corporation 82801I (ICH9 Family) Thermal Subsystem (rev 03) 01:00.0 VGA compatible controller: ATI Technologies Inc M96 [Mobility Radeon HD 4650] 01:00.1 Audio device: ATI Technologies Inc RV710/730 02:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) 06:00.0 FireWire (IEEE 1394): JMicron Technology Corp. IEEE 1394 Host Controller 06:00.1 System peripheral: JMicron Technology Corp. SD/MMC Host Controller 06:00.2 SD Host controller: JMicron Technology Corp. Standard SD Host Controller 06:00.3 System peripheral: JMicron Technology Corp. MS Host Controller 06:00.4 System peripheral: JMicron Technology Corp. xD Host Controller Philippe ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: b43 'hardware blocked' but only keyboard/led touch button 2010-03-30 7:34 ` Philippe De Muyter @ 2010-03-30 16:47 ` Dan Williams 2010-03-30 17:11 ` Matthew Garrett 0 siblings, 1 reply; 22+ messages in thread From: Dan Williams @ 2010-03-30 16:47 UTC (permalink / raw) To: Philippe De Muyter; +Cc: Larry Finger, linux-wireless, Matthew Garrett On Tue, 2010-03-30 at 09:34 +0200, Philippe De Muyter wrote: > Hello Larry, Adding Matthew Garrett to the CC list, since he knows about such things... It could be that hp-wmi doesn't have support for these models yet, or that the dv6-1300sb is simply completely different. But for example, on my Elitebook 2530p, there's a softswitch that pokes BIOS, and when BIOS is softkilled, the onboard wifi becomes hardkilled. To unkill, I need to unblock BIOS, which then either unblocks wifi, or turns the wifi hardkill into a softkill. Convoluted. Dan > On Mon, Mar 29, 2010 at 06:10:23PM -0500, Larry Finger wrote: > > On 03/29/2010 03:12 PM, Philippe De Muyter wrote: > > > Hello wireless-linux experts, > > > > > > I have installed yesterday the last opensuse 11.3 rc4 on a > > > hp pavilion dv6-1300sb laptop which is has a > > > > > > 02:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01) > > > > > > as wireless chip. > > > > > > I needed to install such a bleeding edge distro because opensuse 11.2 does > > > not have the lp_phy driver yet. > > > > > > with dmesg, I see : > > > > > > [ 21.818415] b43 ssb0:0: firmware: requesting b43/ucode15.fw > > > [ 21.820519] b43 ssb0:0: firmware: requesting b43/lp0initvals15.fw > > > [ 21.823084] b43 ssb0:0: firmware: requesting b43/lp0bsinitvals15.fw > > > [ 21.975380] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) > > > [ 22.076456] b43-phy0: Radio hardware status changed to DISABLED > > > [ 22.077743] b43-phy0: Radio turned on by software > > > [ 22.077747] b43-phy0: The hardware RF-kill button still turns the radio physically off. Press the button to turn it on. > > > [ 22.078413] ADDRCONF(NETDEV_UP): wlan0: link is not ready > > > > > > this is confirmed by rfkill : > > > > > > 0: phy0: Wireless LAN > > > Soft blocked: no > > > Hard blocked: yes > > > > > > BUT, I DON'T SEE A HARDWARE RF-KILL button; I only see a red-lighted wireless > > > symbol, which is also a touch-key; in console mode, when I touch this > > > touch-key I get a message asking me to > > > > > > 'setkey e014 <keycode>' > > > > > > I have already seen this symbol being blue-lighted in the first seconds of > > > linux booting, but I don't know what changes this color or if this has > > > an effect on the 'hardware' RF-kill button. In the BIOS there is no option > > > to enable or disable the wireless interface. > > > > > > Any hint ? > > > > > > Thanks already for the good work so far > > > > Is the module hp-wmi loaded? That module is designed to implement all of the > > special keys for HP laptops. > > > > Larry > > No, thanks for the suggestion. Here is the log of my attempt : > > $ modprobe hp-wmi > FATAL: Error inserting hp_wmi (/lib/modules/2.6.33-6-desktop/kernel/drivers/platform/x86/hp-wmi.ko): No such device > > and there is nothing in dmesg. > > If that can help, here is the output of lspci : > > 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) > 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) > 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) > 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) > 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) > 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) > 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) > 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) > 00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03) > 00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03) > 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) > 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) > 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) > 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) > 00:1d.3 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) > 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) > 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) > 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) > 00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03) > 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03) > 00:1f.6 Signal processing controller: Intel Corporation 82801I (ICH9 Family) Thermal Subsystem (rev 03) > 01:00.0 VGA compatible controller: ATI Technologies Inc M96 [Mobility Radeon HD 4650] > 01:00.1 Audio device: ATI Technologies Inc RV710/730 > 02:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01) > 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) > 06:00.0 FireWire (IEEE 1394): JMicron Technology Corp. IEEE 1394 Host Controller > 06:00.1 System peripheral: JMicron Technology Corp. SD/MMC Host Controller > 06:00.2 SD Host controller: JMicron Technology Corp. Standard SD Host Controller > 06:00.3 System peripheral: JMicron Technology Corp. MS Host Controller > 06:00.4 System peripheral: JMicron Technology Corp. xD Host Controller > > Philippe > -- > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: b43 'hardware blocked' but only keyboard/led touch button 2010-03-30 16:47 ` Dan Williams @ 2010-03-30 17:11 ` Matthew Garrett 2010-03-30 19:26 ` Philippe De Muyter 0 siblings, 1 reply; 22+ messages in thread From: Matthew Garrett @ 2010-03-30 17:11 UTC (permalink / raw) To: Dan Williams; +Cc: Philippe De Muyter, Larry Finger, linux-wireless On Tue, Mar 30, 2010 at 09:47:37AM -0700, Dan Williams wrote: > It could be that hp-wmi doesn't have support for these models yet, or > that the dv6-1300sb is simply completely different. But for example, on > my Elitebook 2530p, there's a softswitch that pokes BIOS, and when BIOS > is softkilled, the onboard wifi becomes hardkilled. To unkill, I need > to unblock BIOS, which then either unblocks wifi, or turns the wifi > hardkill into a softkill. Convoluted. Yeah. I'd be interested in seeing the output of acpidump on this machine, but right now it sounds like b43 is behaving correctly - the fact that the light is out implies that the bios is killing it. -- Matthew Garrett | mjg59@srcf.ucam.org ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: b43 'hardware blocked' but only keyboard/led touch button 2010-03-30 17:11 ` Matthew Garrett @ 2010-03-30 19:26 ` Philippe De Muyter 2010-03-30 19:31 ` Matthew Garrett 0 siblings, 1 reply; 22+ messages in thread From: Philippe De Muyter @ 2010-03-30 19:26 UTC (permalink / raw) To: Matthew Garrett; +Cc: Dan Williams, Larry Finger, linux-wireless [-- Attachment #1: Type: text/plain, Size: 1225 bytes --] On Tue, Mar 30, 2010 at 06:11:39PM +0100, Matthew Garrett wrote: > On Tue, Mar 30, 2010 at 09:47:37AM -0700, Dan Williams wrote: > > > It could be that hp-wmi doesn't have support for these models yet, or > > that the dv6-1300sb is simply completely different. But for example, on > > my Elitebook 2530p, there's a softswitch that pokes BIOS, and when BIOS > > is softkilled, the onboard wifi becomes hardkilled. To unkill, I need > > to unblock BIOS, which then either unblocks wifi, or turns the wifi > > hardkill into a softkill. Convoluted. > > Yeah. I'd be interested in seeing the output of acpidump on this > machine, but right now it sounds like b43 is behaving correctly - the > fact that the light is out implies that the bios is killing it. Here you are : linux-vcsl:~ # acpidump > /tmp/acpidump.out Wrong checksum for DSDT! Wrong checksum for SLIC Wrong checksum for SSDT Wrong checksum for DSDT! Wrong checksum for SLIC! Wrong checksum for SSDT! acpidump.out is attached (tar-compressed) I must also add that I currently cannot boot without acpi=off Philippe -- Philippe De Muyter phdm at macqel dot be Tel +32 27029044 Macq Electronique SA rue de l'Aeronef 2 B-1140 Bruxelles Fax +32 27029077 [-- Attachment #2: acpidump.tgz --] [-- Type: application/x-compressed-tar, Size: 75518 bytes --] ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: b43 'hardware blocked' but only keyboard/led touch button 2010-03-30 19:26 ` Philippe De Muyter @ 2010-03-30 19:31 ` Matthew Garrett 2010-03-30 20:00 ` Philippe De Muyter 2010-04-19 11:53 ` Philippe De Muyter 0 siblings, 2 replies; 22+ messages in thread From: Matthew Garrett @ 2010-03-30 19:31 UTC (permalink / raw) To: Philippe De Muyter; +Cc: Dan Williams, Larry Finger, linux-wireless On Tue, Mar 30, 2010 at 09:26:29PM +0200, Philippe De Muyter wrote: > I must also add that I currently cannot boot without acpi=off That's your bug, then. -- Matthew Garrett | mjg59@srcf.ucam.org ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: b43 'hardware blocked' but only keyboard/led touch button 2010-03-30 19:31 ` Matthew Garrett @ 2010-03-30 20:00 ` Philippe De Muyter 2010-03-30 20:06 ` Matthew Garrett 2010-04-19 11:53 ` Philippe De Muyter 1 sibling, 1 reply; 22+ messages in thread From: Philippe De Muyter @ 2010-03-30 20:00 UTC (permalink / raw) To: Matthew Garrett; +Cc: Dan Williams, Larry Finger, linux-wireless On Tue, Mar 30, 2010 at 08:31:29PM +0100, Matthew Garrett wrote: > On Tue, Mar 30, 2010 at 09:26:29PM +0200, Philippe De Muyter wrote: > > > I must also add that I currently cannot boot without acpi=off I shoudl have written ; linux does not boot without acpi=off, and the messages I get with ignore_loglevel debug do never stop at the same place. Do you know how to reliably find where the apci problem is. I noticed this message : ACPI: I/O resource 0000:00:1f.3 [0x8000-0x801f] conflicts with ACPI region SMBI [0x8000-0x800f] (copied by hand) but linux seems to continue to boot past that. > > That's your bug, then. Any hint on what I can do to diagnose more what the problem(s) is/are ? Philippe PS: without acpi=off, the led is blue, but I have no linux :( -- Philippe De Muyter phdm at macqel dot be Tel +32 27029044 Macq Electronique SA rue de l'Aeronef 2 B-1140 Bruxelles Fax +32 27029077 ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: b43 'hardware blocked' but only keyboard/led touch button 2010-03-30 20:00 ` Philippe De Muyter @ 2010-03-30 20:06 ` Matthew Garrett 2010-03-30 20:43 ` Philippe De Muyter 0 siblings, 1 reply; 22+ messages in thread From: Matthew Garrett @ 2010-03-30 20:06 UTC (permalink / raw) To: Philippe De Muyter; +Cc: Dan Williams, Larry Finger, linux-wireless On Tue, Mar 30, 2010 at 10:00:39PM +0200, Philippe De Muyter wrote: > ACPI: I/O resource 0000:00:1f.3 [0x8000-0x801f] conflicts with ACPI region SMBI [0x8000-0x800f] (copied by hand) That's harmless. It just indicates that ACPI is telling us not to drive your SMBus controller directly. > > > > That's your bug, then. > > Any hint on what I can do to diagnose more what the problem(s) is/are ? Best plan would be to post a complete description of the problem to linux-acpi@vger.kernel.org. -- Matthew Garrett | mjg59@srcf.ucam.org ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: b43 'hardware blocked' but only keyboard/led touch button 2010-03-30 20:06 ` Matthew Garrett @ 2010-03-30 20:43 ` Philippe De Muyter 0 siblings, 0 replies; 22+ messages in thread From: Philippe De Muyter @ 2010-03-30 20:43 UTC (permalink / raw) To: Matthew Garrett; +Cc: Dan Williams, Larry Finger, linux-wireless On Tue, Mar 30, 2010 at 09:06:42PM +0100, Matthew Garrett wrote: > On Tue, Mar 30, 2010 at 10:00:39PM +0200, Philippe De Muyter wrote: > > > ACPI: I/O resource 0000:00:1f.3 [0x8000-0x801f] conflicts with ACPI region SMBI [0x8000-0x800f] (copied by hand) > > That's harmless. It just indicates that ACPI is telling us not to drive > your SMBus controller directly. > > > > > > > That's your bug, then. > > > > Any hint on what I can do to diagnose more what the problem(s) is/are ? > > Best plan would be to post a complete description of the problem to > linux-acpi@vger.kernel.org. Thanks I will do that Philippe ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: b43 'hardware blocked' but only keyboard/led touch button 2010-03-30 19:31 ` Matthew Garrett 2010-03-30 20:00 ` Philippe De Muyter @ 2010-04-19 11:53 ` Philippe De Muyter 2010-04-19 14:51 ` Matthew Garrett 1 sibling, 1 reply; 22+ messages in thread From: Philippe De Muyter @ 2010-04-19 11:53 UTC (permalink / raw) To: Matthew Garrett; +Cc: Dan Williams, Larry Finger, linux-wireless On Tue, Mar 30, 2010 at 08:31:29PM +0100, Matthew Garrett wrote: > On Tue, Mar 30, 2010 at 09:26:29PM +0200, Philippe De Muyter wrote: > > > I must also add that I currently cannot boot without acpi=off > > That's your bug, then. I now boot with acpi. Summary : I have a hp pavilion dv6-1300sb laptop with a b43 wifi device, and a touchkey to disable or enable wifi with a red/blue led as feedback. hp-wmi is loaded when I touch the wifi key, I get the following messages (with 2.6.34-rc4) : [ 256.039395] atkbd.c: Unknown key pressed (translated set 2, code 0x94 on isa0060/serio0). [ 256.039408] atkbd.c: Use 'setkeycodes e014 <keycode>' to make it known. [ 256.062313] atkbd.c: Unknown key released (translated set 2, code 0x94 on isa0060/serio0). [ 256.062321] atkbd.c: Use 'setkeycodes e014 <keycode>' to make it known. and the blue/red led doesn't change color, and wifi state does not change either. Any hint ? Philippe ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: b43 'hardware blocked' but only keyboard/led touch button 2010-04-19 11:53 ` Philippe De Muyter @ 2010-04-19 14:51 ` Matthew Garrett 2010-04-19 15:00 ` Philippe De Muyter 0 siblings, 1 reply; 22+ messages in thread From: Matthew Garrett @ 2010-04-19 14:51 UTC (permalink / raw) To: Philippe De Muyter; +Cc: Dan Williams, Larry Finger, linux-wireless On Mon, Apr 19, 2010 at 01:53:29PM +0200, Philippe De Muyter wrote: > and the blue/red led doesn't change color, and wifi state does not change > either. What's the output of the rfkill command now? -- Matthew Garrett | mjg59@srcf.ucam.org ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: b43 'hardware blocked' but only keyboard/led touch button 2010-04-19 14:51 ` Matthew Garrett @ 2010-04-19 15:00 ` Philippe De Muyter 2010-04-19 15:06 ` Matthew Garrett 0 siblings, 1 reply; 22+ messages in thread From: Philippe De Muyter @ 2010-04-19 15:00 UTC (permalink / raw) To: Matthew Garrett; +Cc: Dan Williams, Larry Finger, linux-wireless On Mon, Apr 19, 2010 at 03:51:07PM +0100, Matthew Garrett wrote: > On Mon, Apr 19, 2010 at 01:53:29PM +0200, Philippe De Muyter wrote: > > > and the blue/red led doesn't change color, and wifi state does not change > > either. > > What's the output of the rfkill command now? Sorry, I cannot answer before friday (not my laptop). Philippe ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: b43 'hardware blocked' but only keyboard/led touch button 2010-04-19 15:00 ` Philippe De Muyter @ 2010-04-19 15:06 ` Matthew Garrett 2010-04-24 5:42 ` Philippe De Muyter 0 siblings, 1 reply; 22+ messages in thread From: Matthew Garrett @ 2010-04-19 15:06 UTC (permalink / raw) To: Philippe De Muyter; +Cc: Dan Williams, Larry Finger, linux-wireless On Mon, Apr 19, 2010 at 05:00:50PM +0200, Philippe De Muyter wrote: > On Mon, Apr 19, 2010 at 03:51:07PM +0100, Matthew Garrett wrote: > > On Mon, Apr 19, 2010 at 01:53:29PM +0200, Philippe De Muyter wrote: > > > > > and the blue/red led doesn't change color, and wifi state does not change > > > either. > > > > What's the output of the rfkill command now? > > Sorry, I cannot answer before friday (not my laptop). No problem. The best command to run will be rfkill list and then just attach the output. Thanks, -- Matthew Garrett | mjg59@srcf.ucam.org ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: b43 'hardware blocked' but only keyboard/led touch button 2010-04-19 15:06 ` Matthew Garrett @ 2010-04-24 5:42 ` Philippe De Muyter 2010-04-24 15:21 ` Matthew Garrett 0 siblings, 1 reply; 22+ messages in thread From: Philippe De Muyter @ 2010-04-24 5:42 UTC (permalink / raw) To: Matthew Garrett; +Cc: Dan Williams, Larry Finger, linux-wireless Hello Matthew, On Mon, Apr 19, 2010 at 04:06:28PM +0100, Matthew Garrett wrote: > On Mon, Apr 19, 2010 at 05:00:50PM +0200, Philippe De Muyter wrote: > > On Mon, Apr 19, 2010 at 03:51:07PM +0100, Matthew Garrett wrote: > > > On Mon, Apr 19, 2010 at 01:53:29PM +0200, Philippe De Muyter wrote: > > > > > > > and the blue/red led doesn't change color, and wifi state does not change > > > > either. > > > > > > What's the output of the rfkill command now? > > > > Sorry, I cannot answer before friday (not my laptop). > > No problem. The best command to run will be > > rfkill list > > and then just attach the output. Here you are : Led is blue, wifi does not work (testing with airodump-ng) linux-m1ew:~ # rfkill list 0: hp-wifi: Wireless LAN Soft blocked: yes Hard blocked: no 1: phy0: Wireless LAN Soft blocked: yes Hard blocked: no linux-m1ew:~ # rfkill unblock hp-wifi Bogus unblock argument 'hp-wifi'. linux-m1ew:~ # rfkill unblock 0 linux-m1ew:~ # rfkill list 0: hp-wifi: Wireless LAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: yes Hard blocked: no linux-m1ew:~ # rfkill list 0: hp-wifi: Wireless LAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: yes Hard blocked: no linux-m1ew:~ # rfkill unblock 1 linux-m1ew:~ # rfkill list 0: hp-wifi: Wireless LAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no linux-m1ew:~ # Led is still blue, wifi works Touching the soft key Led stays blue, wifi does not work anymore (testing with airodump-ng) linux-m1ew:~ # rfkill list 0: hp-wifi: Wireless LAN Soft blocked: no Hard blocked: yes 1: phy0: Wireless LAN Soft blocked: no Hard blocked: yes linux-m1ew:~ # dmesg | tail [ 494.758041] b43 ssb0:0: firmware: requesting b43/lp0bsinitvals15.fw [ 1390.158487] atkbd serio0: Unknown key pressed (translated set 2, code 0x94 on isa0060/serio0). [ 1390.158501] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known. [ 1390.165406] atkbd serio0: Unknown key released (translated set 2, code 0x94 on isa0060/serio0). [ 1390.165418] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known. [ 1390.988287] b43-phy0: Radio hardware status changed to DISABLED [ 1390.992840] b43-phy0: Radio turned on by software [ 1390.992854] b43-phy0: The hardware RF-kill button still turns the radio physically off. Press the button to turn it on. linux-m1ew:~ # Touching the soft key again Led stays blue, wifi works again (testing with airodump-ng) linux-m1ew:~ # rfkill list 0: hp-wifi: Wireless LAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no linux-m1ew:~ # dmesg | tail [ 1390.988287] b43-phy0: Radio hardware status changed to DISABLED [ 1390.992840] b43-phy0: Radio turned on by software [ 1390.992854] b43-phy0: The hardware RF-kill button still turns the radio physically off. Press the button to turn it on. [ 1447.758302] atkbd serio0: Unknown key pressed (translated set 2, code 0x94 on isa0060/serio0). [ 1447.758312] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known. [ 1447.764038] atkbd serio0: Unknown key released (translated set 2, code 0x94 on isa0060/serio0). [ 1447.764048] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known. [ 1451.008317] b43-phy0: Radio hardware status changed to ENABLED [ 1451.252283] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) [ 1456.785018] ADDRCONF(NETDEV_UP): wlan0: link is not ready linux-m1ew:~ # So the problems are : - often wifi is blocked, but (except for `sudo rfkill' now) my daughter had no way to enable it, - the led does not reflect the wifi enabled/disabled state. - messages from kernel about `Unknown key pressed' Philippe Philippe De Muyter phdm at macqel dot be Tel +32 27029044 Macq Electronique SA rue de l'Aeronef 2 B-1140 Bruxelles Fax +32 27029077 ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: b43 'hardware blocked' but only keyboard/led touch button 2010-04-24 5:42 ` Philippe De Muyter @ 2010-04-24 15:21 ` Matthew Garrett 2010-04-24 19:56 ` Philippe De Muyter 0 siblings, 1 reply; 22+ messages in thread From: Matthew Garrett @ 2010-04-24 15:21 UTC (permalink / raw) To: Philippe De Muyter; +Cc: Dan Williams, Larry Finger, linux-wireless On Sat, Apr 24, 2010 at 07:42:10AM +0200, Philippe De Muyter wrote: > - often wifi is blocked, but (except for `sudo rfkill' now) my daughter had > no way to enable it, > - the led does not reflect the wifi enabled/disabled state. > - messages from kernel about `Unknown key pressed' Does this laptop also have bluetooth? -- Matthew Garrett | mjg59@srcf.ucam.org ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: b43 'hardware blocked' but only keyboard/led touch button 2010-04-24 15:21 ` Matthew Garrett @ 2010-04-24 19:56 ` Philippe De Muyter 2010-04-24 20:02 ` Matthew Garrett 0 siblings, 1 reply; 22+ messages in thread From: Philippe De Muyter @ 2010-04-24 19:56 UTC (permalink / raw) To: Matthew Garrett; +Cc: Dan Williams, Larry Finger, linux-wireless On Sat, Apr 24, 2010 at 04:21:07PM +0100, Matthew Garrett wrote: > On Sat, Apr 24, 2010 at 07:42:10AM +0200, Philippe De Muyter wrote: > > > - often wifi is blocked, but (except for `sudo rfkill' now) my daughter had > > no way to enable it, > > - the led does not reflect the wifi enabled/disabled state. > > - messages from kernel about `Unknown key pressed' > > Does this laptop also have bluetooth? No Philippe ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: b43 'hardware blocked' but only keyboard/led touch button 2010-04-24 19:56 ` Philippe De Muyter @ 2010-04-24 20:02 ` Matthew Garrett 2010-04-25 19:50 ` Philippe De Muyter 0 siblings, 1 reply; 22+ messages in thread From: Matthew Garrett @ 2010-04-24 20:02 UTC (permalink / raw) To: Philippe De Muyter; +Cc: Dan Williams, Larry Finger, linux-wireless On Sat, Apr 24, 2010 at 09:56:30PM +0200, Philippe De Muyter wrote: > On Sat, Apr 24, 2010 at 04:21:07PM +0100, Matthew Garrett wrote: > > Does this laptop also have bluetooth? > > No Hm. I have no idea why hitting the key doesn't change the colour then, I'm afraid. On the other hand, it sounds like things are working now? The only thing I can suggest is attempting to clear the CMOS data in the BIOS menu and see if that changes things. -- Matthew Garrett | mjg59@srcf.ucam.org ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: b43 'hardware blocked' but only keyboard/led touch button 2010-04-24 20:02 ` Matthew Garrett @ 2010-04-25 19:50 ` Philippe De Muyter 2010-04-25 20:11 ` Larry Finger 0 siblings, 1 reply; 22+ messages in thread From: Philippe De Muyter @ 2010-04-25 19:50 UTC (permalink / raw) To: Matthew Garrett; +Cc: Dan Williams, Larry Finger, linux-wireless Hello Matthew, On Sat, Apr 24, 2010 at 09:02:18PM +0100, Matthew Garrett wrote: > On Sat, Apr 24, 2010 at 09:56:30PM +0200, Philippe De Muyter wrote: > > On Sat, Apr 24, 2010 at 04:21:07PM +0100, Matthew Garrett wrote: > > > Does this laptop also have bluetooth? > > > > No > > Hm. I have no idea why hitting the key doesn't change the colour then, > I'm afraid. On the other hand, it sounds like things are working now? > The only thing I can suggest is attempting to clear the CMOS data in the > BIOS menu and see if that changes things. Just some more info : when I power-on this laptop, the wifi led is red. The wifi led stays red while in the bios and in grub and during the very start of linux boot. It becomes blue simultaneously with the displaying of the following message : ACPI: Core revision 20100121 (I started 2.6.34-rc5 with boot_delay=1000 to be sure) When I touch the wifi led, sometimes I can see it flash red and directly return to blue, but often I do not see this flash : the led simply remains blue. What's the use of having a soft blocking system when one also has a 'hard' blocking system ? (and actually sometimes there is also a third one, because NetworkManager has wirelessEnabled=false in his state file) Just for completeness about bluetooth, you'll find below the output of lspci -vnn. Philippe 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) Subsystem: Hewlett-Packard Company Device [103c:3628] Flags: bus master, fast devsel, latency 0 Capabilities: [e0] Vendor Specific Information: Len=0a <?> 00:01.0 PCI bridge [0604]: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port [8086:2a41] (rev 07) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 00007000-00007fff Memory behind bridge: da000000-da0fffff Prefetchable memory behind bridge: 00000000c0000000-00000000cfffffff Capabilities: [88] Subsystem: Hewlett-Packard Company Device [103c:3628] Capabilities: [80] Power Management version 3 Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [a0] Express Root Port (Slot+), MSI 00 Capabilities: [100] Virtual Channel Capabilities: [140] Root Complex Link Kernel driver in use: pcieport 00:1a.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 03) (prog-if 00 [UHCI]) Subsystem: Hewlett-Packard Company Device [103c:3628] Flags: bus master, medium devsel, latency 0, IRQ 16 I/O ports at 80e0 [size=32] Capabilities: [50] PCI Advanced Features Kernel driver in use: uhci_hcd 00:1a.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 03) (prog-if 00 [UHCI]) Subsystem: Hewlett-Packard Company Device [103c:3628] Flags: bus master, medium devsel, latency 0, IRQ 21 I/O ports at 80c0 [size=32] Capabilities: [50] PCI Advanced Features Kernel driver in use: uhci_hcd 00:1a.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 03) (prog-if 20 [EHCI]) Subsystem: Hewlett-Packard Company Device [103c:3628] Flags: bus master, medium devsel, latency 0, IRQ 19 Memory at da105c00 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port: BAR=1 offset=00a0 Capabilities: [98] PCI Advanced Features Kernel driver in use: ehci_hcd 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 03) Subsystem: Hewlett-Packard Company dv6-1190en [103c:3628] Flags: bus master, fast devsel, latency 0, IRQ 32 Memory at da100000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [130] Root Complex Link Kernel driver in use: HDA Intel 00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 03) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: 00006000-00006fff Memory behind bridge: d9000000-d9ffffff Prefetchable memory behind bridge: 00000000d0000000-00000000d0ffffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Hewlett-Packard Company Device [103c:3628] Capabilities: [a0] Power Management version 2 Capabilities: [100] Virtual Channel Capabilities: [180] Root Complex Link Kernel driver in use: pcieport 00:1c.1 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 [8086:2942] (rev 03) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: 00005000-00005fff Memory behind bridge: d8000000-d8ffffff Prefetchable memory behind bridge: 00000000d1000000-00000000d1ffffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Hewlett-Packard Company Device [103c:3628] Capabilities: [a0] Power Management version 2 Capabilities: [100] Virtual Channel Capabilities: [180] Root Complex Link Kernel driver in use: pcieport 00:1c.3 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 [8086:2946] (rev 03) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=05, subordinate=05, sec-latency=0 I/O behind bridge: 00004000-00004fff Memory behind bridge: d7000000-d7ffffff Prefetchable memory behind bridge: 00000000d2000000-00000000d2ffffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Hewlett-Packard Company Device [103c:3628] Capabilities: [a0] Power Management version 2 Capabilities: [100] Virtual Channel Capabilities: [180] Root Complex Link Kernel driver in use: pcieport 00:1c.4 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 [8086:2948] (rev 03) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=06, subordinate=06, sec-latency=0 I/O behind bridge: 00003000-00003fff Memory behind bridge: d6000000-d6ffffff Prefetchable memory behind bridge: 00000000d3000000-00000000d3ffffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Hewlett-Packard Company Device [103c:3628] Capabilities: [a0] Power Management version 2 Capabilities: [100] Virtual Channel Capabilities: [180] Root Complex Link Kernel driver in use: pcieport 00:1c.5 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 [8086:294a] (rev 03) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=07, subordinate=09, sec-latency=0 I/O behind bridge: 00002000-00002fff Memory behind bridge: d5000000-d5ffffff Prefetchable memory behind bridge: 00000000d4000000-00000000d4ffffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Hewlett-Packard Company Device [103c:3628] Capabilities: [a0] Power Management version 2 Capabilities: [100] Virtual Channel Capabilities: [180] Root Complex Link Kernel driver in use: pcieport 00:1d.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 03) (prog-if 00 [UHCI]) Subsystem: Hewlett-Packard Company Device [103c:3628] Flags: bus master, medium devsel, latency 0, IRQ 20 I/O ports at 80a0 [size=32] Capabilities: [50] PCI Advanced Features Kernel driver in use: uhci_hcd 00:1d.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 03) (prog-if 00 [UHCI]) Subsystem: Hewlett-Packard Company Device [103c:3628] Flags: bus master, medium devsel, latency 0, IRQ 19 I/O ports at 8080 [size=32] Capabilities: [50] PCI Advanced Features Kernel driver in use: uhci_hcd 00:1d.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 03) (prog-if 00 [UHCI]) Subsystem: Hewlett-Packard Company Device [103c:3628] Flags: bus master, medium devsel, latency 0, IRQ 16 I/O ports at 8060 [size=32] Capabilities: [50] PCI Advanced Features Kernel driver in use: uhci_hcd 00:1d.3 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 03) (prog-if 00 [UHCI]) Subsystem: Hewlett-Packard Company Device [103c:3628] Flags: bus master, medium devsel, latency 0, IRQ 18 I/O ports at 8040 [size=32] Capabilities: [50] PCI Advanced Features Kernel driver in use: uhci_hcd 00:1d.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 03) (prog-if 20 [EHCI]) Subsystem: Hewlett-Packard Company Device [103c:3628] Flags: bus master, medium devsel, latency 0, IRQ 20 Memory at da105800 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port: BAR=1 offset=00a0 Capabilities: [98] PCI Advanced Features Kernel driver in use: ehci_hcd 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev 93) (prog-if 01 [Subtractive decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=0a, subordinate=0a, sec-latency=32 Capabilities: [50] Subsystem: Hewlett-Packard Company Device [103c:3628] 00:1f.0 ISA bridge [0601]: Intel Corporation ICH9M LPC Interface Controller [8086:2919] (rev 03) Subsystem: Hewlett-Packard Company Device [103c:3628] Flags: bus master, medium devsel, latency 0 Capabilities: [e0] Vendor Specific Information: Len=0c <?> 00:1f.2 SATA controller [0106]: Intel Corporation ICH9M/M-E SATA AHCI Controller [8086:2929] (rev 03) (prog-if 01 [AHCI 1.0]) Subsystem: Hewlett-Packard Company dv6-1190en [103c:3628] Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 31 I/O ports at 8108 [size=8] I/O ports at 8114 [size=4] I/O ports at 8100 [size=8] I/O ports at 8110 [size=4] I/O ports at 8020 [size=32] Memory at da105000 (32-bit, non-prefetchable) [size=2K] Capabilities: [80] MSI: Enable+ Count=1/16 Maskable- 64bit- Capabilities: [70] Power Management version 3 Capabilities: [a8] SATA HBA v1.0 Capabilities: [b0] PCI Advanced Features Kernel driver in use: ahci 00:1f.3 SMBus [0c05]: Intel Corporation 82801I (ICH9 Family) SMBus Controller [8086:2930] (rev 03) Subsystem: Hewlett-Packard Company dv6-1190en [103c:3628] Flags: medium devsel, IRQ 18 Memory at da106000 (64-bit, non-prefetchable) [size=256] I/O ports at 8000 [size=32] 00:1f.6 Signal processing controller [1180]: Intel Corporation 82801I (ICH9 Family) Thermal Subsystem [8086:2932] (rev 03) Subsystem: Hewlett-Packard Company dv6-1190en [103c:3628] Flags: fast devsel, IRQ 11 Memory at da104000 (64-bit, non-prefetchable) [size=4K] Capabilities: [50] Power Management version 3 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc M96 [Mobility Radeon HD 4650] [1002:9480] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company ATI Mobility Radeon HD 4650 [dv6-1190en] [103c:3628] Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at c0000000 (32-bit, prefetchable) [size=256M] I/O ports at 7000 [size=256] Memory at da000000 (32-bit, non-prefetchable) [size=64K] Expansion ROM at da020000 [disabled] [size=128K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> 01:00.1 Audio device [0403]: ATI Technologies Inc RV710/730 [1002:aa38] Subsystem: Hewlett-Packard Company ATI RV710/730 [dv6-1190en] [103c:3628] Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at da010000 (32-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Kernel driver in use: HDA Intel 02:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:1508] Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at d9000000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [58] Vendor Specific Information: Len=78 <?> Capabilities: [e8] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [d0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [13c] Virtual Channel Capabilities: [160] Device Serial Number 00-00-00-ff-ff-00-ff-ff Capabilities: [16c] Power Budgeting <?> Kernel driver in use: b43-pci-bridge 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 02) Subsystem: Hewlett-Packard Company Device [103c:3628] Flags: bus master, fast devsel, latency 0, IRQ 30 I/O ports at 5000 [size=256] Memory at d1010000 (64-bit, prefetchable) [size=4K] Memory at d1000000 (64-bit, prefetchable) [size=64K] Expansion ROM at d1020000 [disabled] [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/2 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Count=2 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00 Kernel driver in use: r8169 06:00.0 FireWire (IEEE 1394) [0c00]: JMicron Technology Corp. IEEE 1394 Host Controller [197b:2380] (prog-if 10 [OHCI]) Subsystem: Hewlett-Packard Company Device [103c:3628] Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at d6000000 (32-bit, non-prefetchable) [size=2K] Memory at d6000d00 (32-bit, non-prefetchable) [size=128] Memory at d6000c80 (32-bit, non-prefetchable) [size=128] Memory at d6000c00 (32-bit, non-prefetchable) [size=128] Capabilities: [44] Power Management version 3 Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [94] MSI: Enable- Count=1/1 Maskable- 64bit- Kernel driver in use: ohci1394 06:00.1 System peripheral [0880]: JMicron Technology Corp. SD/MMC Host Controller [197b:2382] Subsystem: Hewlett-Packard Company Device [103c:3628] Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at d6000b00 (32-bit, non-prefetchable) [size=256] Capabilities: [a4] Power Management version 3 Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [94] MSI: Enable- Count=1/1 Maskable- 64bit- Kernel driver in use: sdhci-pci 06:00.2 SD Host controller [0805]: JMicron Technology Corp. Standard SD Host Controller [197b:2381] (prog-if 01) Subsystem: Hewlett-Packard Company Device [103c:3628] Flags: fast devsel, IRQ 16 Memory at d6000a00 (32-bit, non-prefetchable) [size=256] Capabilities: [a4] Power Management version 3 Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [94] MSI: Enable- Count=1/1 Maskable- 64bit- 06:00.3 System peripheral [0880]: JMicron Technology Corp. MS Host Controller [197b:2383] Subsystem: Hewlett-Packard Company Device [103c:3628] Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at d6000900 (32-bit, non-prefetchable) [size=256] Capabilities: [a4] Power Management version 3 Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [94] MSI: Enable- Count=1/1 Maskable- 64bit- Kernel driver in use: jmb38x_ms 06:00.4 System peripheral [0880]: JMicron Technology Corp. xD Host Controller [197b:2384] Subsystem: Hewlett-Packard Company Device [103c:3628] Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at d6000800 (32-bit, non-prefetchable) [size=256] Capabilities: [a4] Power Management version 3 Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [94] MSI: Enable- Count=1/1 Maskable- 64bit- ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: b43 'hardware blocked' but only keyboard/led touch button 2010-04-25 19:50 ` Philippe De Muyter @ 2010-04-25 20:11 ` Larry Finger 2010-05-01 12:17 ` BCM4312 802.11b/g LP-PHY (rev 01) dma & led problems Philippe De Muyter 0 siblings, 1 reply; 22+ messages in thread From: Larry Finger @ 2010-04-25 20:11 UTC (permalink / raw) To: Philippe De Muyter; +Cc: Matthew Garrett, Dan Williams, linux-wireless On 04/25/2010 02:50 PM, Philippe De Muyter wrote: > Hello Matthew, > > On Sat, Apr 24, 2010 at 09:02:18PM +0100, Matthew Garrett wrote: >> On Sat, Apr 24, 2010 at 09:56:30PM +0200, Philippe De Muyter wrote: >>> On Sat, Apr 24, 2010 at 04:21:07PM +0100, Matthew Garrett wrote: >>>> Does this laptop also have bluetooth? >>> >>> No >> >> Hm. I have no idea why hitting the key doesn't change the colour then, >> I'm afraid. On the other hand, it sounds like things are working now? >> The only thing I can suggest is attempting to clear the CMOS data in the >> BIOS menu and see if that changes things. > > Just some more info : > > when I power-on this laptop, the wifi led is red. The wifi led stays > red while in the bios and in grub and during the very start of linux boot. > It becomes blue simultaneously with the displaying of the following message : > > ACPI: Core revision 20100121 This makes it clear that b43 is not controlling that LED as the change to blue on my system only occurs after the interface comes up under the control of ifup or NetworkManager. Larry ^ permalink raw reply [flat|nested] 22+ messages in thread
* BCM4312 802.11b/g LP-PHY (rev 01) dma & led problems 2010-04-25 20:11 ` Larry Finger @ 2010-05-01 12:17 ` Philippe De Muyter 2010-05-01 16:04 ` Gábor Stefanik 0 siblings, 1 reply; 22+ messages in thread From: Philippe De Muyter @ 2010-05-01 12:17 UTC (permalink / raw) To: Larry Finger; +Cc: Matthew Garrett, Dan Williams, linux-wireless This is a followup on my attempt to use b43 (now from 2.6.34-rc6) on a HP Pavilion dv6-1300sb. With 2.6.34-rc6, I have not had any boot problem (blocking around ssb/b43) so far. But, dma mode gives an error (like before) and driver now switches automatically to PIO mode (new). [ 89.830222] device mon0 entered promiscuous mode [ 101.965896] NOHZ: local_softirq_pending 08 [ 101.969431] NOHZ: local_softirq_pending 08 [ 101.972230] NOHZ: local_softirq_pending 08 [ 101.975041] NOHZ: local_softirq_pending 08 [ 101.977771] NOHZ: local_softirq_pending 08 [ 101.984651] NOHZ: local_softirq_pending 08 [ 101.988808] NOHZ: local_softirq_pending 08 [ 101.991562] NOHZ: local_softirq_pending 08 [ 101.994363] NOHZ: local_softirq_pending 08 [ 101.997116] NOHZ: local_softirq_pending 08 [ 111.816257] hpet1: lost 1 rtc interrupts [ 112.131040] hpet1: lost 1 rtc interrupts [ 112.133343] hpet1: lost 1 rtc interrupts [ 112.135528] hpet1: lost 1 rtc interrupts [ 112.137722] hpet1: lost 1 rtc interrupts [ 112.139911] hpet1: lost 1 rtc interrupts [ 112.142089] hpet1: lost 1 rtc interrupts [ 112.146370] hpet1: lost 1 rtc interrupts [ 112.150637] hpet1: lost 1 rtc interrupts [ 112.152849] hpet1: lost 1 rtc interrupts [ 113.100932] b43-phy0 ERROR: Fatal DMA error: 0x00000000, 0x00000800, 0x00000000, 0x00000000, 0x00000000, 0x00000000 [ 113.100949] b43-phy0 ERROR: This device does not support DMA on your system. Please use PIO instead. [ 113.100957] b43-phy0: Controller RESET (DMA error) ... [ 113.336119] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) [ 118.853353] b43-phy0: Controller restarted During the switch, the led switches from blue to red and returns to blue after some seconds. Touching the led switches the hardware blocking on and off, but the led color does not change. I then tried with the broadcom supplied hybrid driver, and there the touch/led functionality works as expected : led is red whenever I touch the button (enabling hardware blocking) or when I issue a rfkill block 0 (enabling software blocking). Led is blue only when both blocking are disabled. But, hybrid driver does not give monitor functionality :( (and of course, also no injection). [10703.172776] wl: module license 'unspecified' taints kernel. [10703.172791] Disabling lock debugging due to kernel taint [10703.174286] wl: Unknown symbol lib80211_get_crypto_ops [10778.692746] lib80211: common routines for IEEE802.11 drivers [10778.692759] lib80211_crypt: registered algorithm 'NULL' [10783.823152] wl 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [10783.823188] wl 0000:02:00.0: setting latency timer to 64 [10783.921236] lib80211_crypt: registered algorithm 'TKIP' [10783.921623] eth1: Broadcom BCM4315 802.11 Hybrid Wireless Controller 5.60.48.36 Any idea on what I could do to debug more / fix the dma and led problems ? Philippe Here the output of lspci -nvv for that chip : linux-m1ew:~ # lspci -nvv -s 02:00.0 02:00.0 0280: 14e4:4315 (rev 01) Subsystem: 103c:1508 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 16 Region 0: Memory at d9000000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=2 PME- Capabilities: [58] Vendor Specific Information: Len=78 <?> Capabilities: [e8] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [d0] Express (v1) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <4us, L1 <64us ClockPM+ Surprise- LLActRep- BwNot- LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr+ BadTLP- BadDLLP- Rollover- Timeout+ NonFatalErr+ CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 14, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [13c v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb: Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 Status: NegoPending- InProgress- Capabilities: [160 v1] Device Serial Number 00-00-00-ff-ff-00-ff-ff Capabilities: [16c v1] Power Budgeting <?> Kernel driver in use: b43-pci-bridge ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: BCM4312 802.11b/g LP-PHY (rev 01) dma & led problems 2010-05-01 12:17 ` BCM4312 802.11b/g LP-PHY (rev 01) dma & led problems Philippe De Muyter @ 2010-05-01 16:04 ` Gábor Stefanik 0 siblings, 0 replies; 22+ messages in thread From: Gábor Stefanik @ 2010-05-01 16:04 UTC (permalink / raw) To: Philippe De Muyter Cc: Larry Finger, Matthew Garrett, Dan Williams, linux-wireless On Sat, May 1, 2010 at 2:17 PM, Philippe De Muyter <phdm@macqel.be> wrote: > This is a followup on my attempt to use b43 (now from 2.6.34-rc6) on > a HP Pavilion dv6-1300sb. > > With 2.6.34-rc6, I have not had any boot problem (blocking around ssb/b43) > so far. > > But, dma mode gives an error (like before) and driver now switches > automatically to PIO mode (new). > > [ 89.830222] device mon0 entered promiscuous mode > [ 101.965896] NOHZ: local_softirq_pending 08 > [ 101.969431] NOHZ: local_softirq_pending 08 > [ 101.972230] NOHZ: local_softirq_pending 08 > [ 101.975041] NOHZ: local_softirq_pending 08 > [ 101.977771] NOHZ: local_softirq_pending 08 > [ 101.984651] NOHZ: local_softirq_pending 08 > [ 101.988808] NOHZ: local_softirq_pending 08 > [ 101.991562] NOHZ: local_softirq_pending 08 > [ 101.994363] NOHZ: local_softirq_pending 08 > [ 101.997116] NOHZ: local_softirq_pending 08 > [ 111.816257] hpet1: lost 1 rtc interrupts > [ 112.131040] hpet1: lost 1 rtc interrupts > [ 112.133343] hpet1: lost 1 rtc interrupts > [ 112.135528] hpet1: lost 1 rtc interrupts > [ 112.137722] hpet1: lost 1 rtc interrupts > [ 112.139911] hpet1: lost 1 rtc interrupts > [ 112.142089] hpet1: lost 1 rtc interrupts > [ 112.146370] hpet1: lost 1 rtc interrupts > [ 112.150637] hpet1: lost 1 rtc interrupts > [ 112.152849] hpet1: lost 1 rtc interrupts > [ 113.100932] b43-phy0 ERROR: Fatal DMA error: 0x00000000, 0x00000800, 0x00000000, 0x00000000, 0x00000000, 0x00000000 > [ 113.100949] b43-phy0 ERROR: This device does not support DMA on your system. Please use PIO instead. > [ 113.100957] b43-phy0: Controller RESET (DMA error) ... > [ 113.336119] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) > [ 118.853353] b43-phy0: Controller restarted > > During the switch, the led switches from blue to red and returns to blue > after some seconds. Touching the led switches the hardware blocking on > and off, but the led color does not change. > > I then tried with the broadcom supplied hybrid driver, and there the > touch/led functionality works as expected : led is red whenever > I touch the button (enabling hardware blocking) or when I issue > a rfkill block 0 (enabling software blocking). Led is blue only when > both blocking are disabled. But, hybrid driver does not give monitor > functionality :( (and of course, also no injection). > [10703.172776] wl: module license 'unspecified' taints kernel. > [10703.172791] Disabling lock debugging due to kernel taint > [10703.174286] wl: Unknown symbol lib80211_get_crypto_ops > [10778.692746] lib80211: common routines for IEEE802.11 drivers > [10778.692759] lib80211_crypt: registered algorithm 'NULL' > [10783.823152] wl 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 > [10783.823188] wl 0000:02:00.0: setting latency timer to 64 > [10783.921236] lib80211_crypt: registered algorithm 'TKIP' > [10783.921623] eth1: Broadcom BCM4315 802.11 Hybrid Wireless Controller 5.60.48.36 > > Any idea on what I could do to debug more / fix the dma and led problems ? Nothing, unfortunately. We are working on this issue; apparently some workarounds are missing from our PCI-E init implementation. > > Philippe > > Here the output of lspci -nvv for that chip : > > linux-m1ew:~ # lspci -nvv -s 02:00.0 > 02:00.0 0280: 14e4:4315 (rev 01) > Subsystem: 103c:1508 > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 0, Cache Line Size: 64 bytes > Interrupt: pin A routed to IRQ 16 > Region 0: Memory at d9000000 (64-bit, non-prefetchable) [size=16K] > Capabilities: [40] Power Management version 3 > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) > Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=2 PME- > Capabilities: [58] Vendor Specific Information: Len=78 <?> > Capabilities: [e8] MSI: Enable- Count=1/1 Maskable- 64bit+ > Address: 0000000000000000 Data: 0000 > Capabilities: [d0] Express (v1) Endpoint, MSI 00 > DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited > ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- > DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- > RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- > MaxPayload 128 bytes, MaxReadReq 128 bytes > DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend- > LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <4us, L1 <64us > ClockPM+ Surprise- LLActRep- BwNot- > LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+ > ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt- > LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- > Capabilities: [100 v1] Advanced Error Reporting > UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- > UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- > UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- > CESta: RxErr+ BadTLP- BadDLLP- Rollover- Timeout+ NonFatalErr+ > CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ > AERCap: First Error Pointer: 14, GenCap+ CGenEn- ChkCap+ ChkEn- > Capabilities: [13c v1] Virtual Channel > Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 > Arb: Fixed- WRR32- WRR64- WRR128- > Ctrl: ArbSelect=Fixed > Status: InProgress- > VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- > Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- > Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 > Status: NegoPending- InProgress- > Capabilities: [160 v1] Device Serial Number 00-00-00-ff-ff-00-ff-ff > Capabilities: [16c v1] Power Budgeting <?> > Kernel driver in use: b43-pci-bridge > -- > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) ^ permalink raw reply [flat|nested] 22+ messages in thread
end of thread, other threads:[~2010-05-01 16:05 UTC | newest] Thread overview: 22+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2010-03-29 20:12 b43 'hardware blocked' but only keyboard/led touch button Philippe De Muyter 2010-03-29 23:10 ` Larry Finger 2010-03-30 7:34 ` Philippe De Muyter 2010-03-30 16:47 ` Dan Williams 2010-03-30 17:11 ` Matthew Garrett 2010-03-30 19:26 ` Philippe De Muyter 2010-03-30 19:31 ` Matthew Garrett 2010-03-30 20:00 ` Philippe De Muyter 2010-03-30 20:06 ` Matthew Garrett 2010-03-30 20:43 ` Philippe De Muyter 2010-04-19 11:53 ` Philippe De Muyter 2010-04-19 14:51 ` Matthew Garrett 2010-04-19 15:00 ` Philippe De Muyter 2010-04-19 15:06 ` Matthew Garrett 2010-04-24 5:42 ` Philippe De Muyter 2010-04-24 15:21 ` Matthew Garrett 2010-04-24 19:56 ` Philippe De Muyter 2010-04-24 20:02 ` Matthew Garrett 2010-04-25 19:50 ` Philippe De Muyter 2010-04-25 20:11 ` Larry Finger 2010-05-01 12:17 ` BCM4312 802.11b/g LP-PHY (rev 01) dma & led problems Philippe De Muyter 2010-05-01 16:04 ` Gábor Stefanik
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).