On Thu, Jun 11, 2009 at 5:20 PM, Luis R. Rodriguez<mcgrof@xxxxxxxxx> wrote: > On Thu, Jun 11, 2009 at 5:13 PM, Luis R. Rodriguez<mcgrof@xxxxxxxxx> wrote: >> On Thu, Jun 11, 2009 at 5:06 PM, Marcel Holtmann<marcel@xxxxxxxxxxxx> wrote: >>> Hi Luis, >>> >>>> >> When I hit rfkill, I get: >>>> >> >>>> >> [18493.777231] btusb_intr_complete: hci0 urb cbe20000 failed to resubmit (19) >>>> >> [18493.777553] btusb_send_frame: hci0 urb f7d3c700 submission failed >>>> >> >>>> >> When I hit it again I get: >>>> >> >>>> >> [18531.488091] usb 1-1: new full speed USB device using uhci_hcd and address 7 >>>> >> [18531.651409] usb 1-1: configuration #1 chosen from 1 choice >>>> >> >>>> >> The device that disappears upon rfkill is my bluetooth controller: >>>> >> >>>> >> mcgrof@tesla ~ $ diff -u before-rfkill after-rfkill >>>> >> --- 1 2009-06-11 15:37:37.000000000 -0700 >>>> >> +++ 2 2009-06-11 15:37:49.000000000 -0700 >>>> >> @@ -6,7 +6,6 @@ >>>> >> Bus 003 Device 004: ID 046d:c040 Logitech, Inc. Corded Tilt-Wheel Mouse >>>> >> Bus 003 Device 003: ID 04b3:4485 IBM Corp. >>>> >> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >>>> >> -Bus 001 Device 006: ID 0a5c:2110 Broadcom Corp. Bluetooth Controller >>>> >> Bus 001 Device 004: ID 0483:2016 SGS Thomson Microelectronics >>>> >> Fingerprint Reader >>>> >> Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub >>>> >> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub >>>> >> >>>> >> Granted I tested this on 2.6.27 with bleeding edge compat-wireless but >>>> >> I think this is the same behaviour I will get with bleeding edge, will >>>> >> try now on wireless-testing. >>>> > >>>> > what are you trying to tell us. >>>> >>>> my 802.11 device is not rfkill'ed on the T61, some patches recently >>>> went in to add support for rfkill on ath5k. I do have thinkpad_acpi >>>> loaded on this ancient 2.6.27 kernel. >>>> >>>> I'll try on wireless-testing next, build is almost done. >>> >>> still are not getting what you wanna tell us. What has Bluetooh RFKILL >>> switch to do with WiFi. >> >> Nothing, I really was just unaware we rfkilled bluetooth as well. Plus >> like I said my 802.11 device is not being rfkilled, which is what I >> actually did expect. > > Yeah same thing with wireless-testing. Heh nevermind me, the 802.11 rfkill button is in a different place. Doh! Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
