turning off the dm1 Bluetooth

[UBoontuzilla]

Sorry but I don't own any BT devices to test it with. I know other people were having issues connecting to their devices, but I don't know if they ever solved the issues. sorry.

It didn't fix. I hope RT people read ours post
I installed another dongle, it detect a mobile but it cannot browse or reach other services. It seems to be a major problem with bluetooth

[nefan]

It didn't fix. I hope RT people read ours post

I don't think there's much hope for that. I asked on the rt2x00 mailinglist where they told me to ask at the linux-bluetooth list. I did that but got no answer.

Is your problem still turning bluetooth on or is it the discovery problem? What is the output of 'hcitool dev' and 'hcitool scan'? Is btusb loaded? Sometimes '/etc/init.d/bluetooth restart' is necessary to get mine working.

[Redblade20XX]

I don't think there's much hope for that. I asked on the rt2x00 mailinglist where they told me to ask at the linux-bluetooth list. I did that but got no answer.

Is your problem still turning bluetooth on or is it the discovery problem? What is the output of 'hcitool dev' and 'hcitool scan'? Is btusb loaded? Sometimes '/etc/init.d/bluetooth restart' is necessary to get mine working.

The problem I have with the dm1z internal bluetooth is not turning on the bluetooth but discovering something.

$ hciconfig -a
hci0:   Type: BR/EDR  Bus: USB
        BD Address: 90:00:4E:A4:63:EC  ACL MTU: 310:10  SCO MTU: 64:8
        UP RUNNING PSCAN ISCAN 
        RX bytes:1579 acl:0 sco:0 events:45 errors:0
        TX bytes:1874 acl:0 sco:0 commands:43 errors:0
        Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x87
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
        Link policy: RSWITCH HOLD SNIFF PARK 
        Link mode: SLAVE ACCEPT 
        Name: 'user-HP-dm1z-0'
        Class: 0x580100
        Service Classes: Capturing, Object Transfer, Telephony
        Device Class: Computer, Uncategorized
        HCI Version: 3.0 (0x5)  Revision: 0x1aa1
        LMP Version: 3.0 (0x5)  Subversion: 0x1aa1
        Manufacturer: Cambridge Silicon Radio (10)

$ hcitool dev
Devices:
        hci0    90:00:4E:A4:63:EC

$ hcitool info 90:00:4E:A4:63:EC
Device is not available or not connected.

$ hcitool name 90:00:4E:A4:63:EC 
Device is not available.

$ hcitool scan 
Scanning ...
$

Which leads me to believe that the bluez stack can't detect the combo wifi/bluetooth driver. RT5390 for wifi and Motorola BC8 3.0+ Adapter for bluetooth.

[nefan]

Which leads me to believe that the bluez stack can't detect the combo wifi/bluetooth driver. RT5390 for wifi and Motorola BC8 3.0+ Adapter for bluetooth.

ok, my dm1 has a RT539f wifi/bluetooth combo card which might explain the differences. Apart from that, I experienced exactly the symptoms you describe (including the hcitool info and name output) but the boot in windows workaround has solved it for me.