[Bug 273873] Bluedevil 1.04-3.1 and blueman do not function on KDE 4.6.0 and HP tm2t-2200

Andy Lavarre alavarre at gmail.com
Wed Jun 6 00:32:50 BST 2012


https://bugs.kde.org/show_bug.cgi?id=273873

--- Comment #10 from Andy Lavarre <alavarre at gmail.com> ---
BT hasn't worked on this machine (HP Touchsmart TM2T, OpenSuSE 12.1, 
Ralink BT/WIFI adapter) since very soon after I got it.

Today I bought a Targus Micro USB BT ADB10US1 (ADB73) adapter. It doesn't work
either.

The Internal Ralink is recognized by YaST Hardware Info in extensive detail
reported above, but also after my signature for ease.

The Targus (Broadcom) USB is not recognized at all, neither by yast2 hwinfo nor
by dmesg.

hcitool scan returns... nothing.

hcitool dev returns
    devices: hci0 CC:52:AF:50:0D:FE
This is the MAC of the internal adapter. If you repeat this with the 
Targus removed you get the same result.
So the USB is not being recognized.

tm2t:~ # hcitool name CC:52:AF:50:0D:FE
Device is not available.

hcitool inq returns nothing.

=====

The stack is bluez plus BlueDevil for KDE. Standard OpenSuSE 12.1.

But I've tried this with the Gnome stack and it doesn't do any better.

I thought that maybe getting the new outboard adapter would solve 
things. The BlueDevil developer Alex says the problems are "upstream", so it 
appears to be a problem with the Bluez stack.

Regardless, neither Broadcom nor Ralink work.

Cheers, Andy
=========Output from yast2 hwinfo================
39: USB 00.0: 11500 Bluetooth Device
  [Created at usb.122]
  Unique ID: JPTW.tGttqvOhWG9
  Parent ID: FKGF.0j9+vWlqL56
  SysFS ID: /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0
  SysFS BusID: 2-1.3:1.0
  Hardware Class: bluetooth
  Model: "Ralink Bluetooth Device"
  Hotplug: USB
  Vendor: usb 0x148f "Ralink Technology, Corp."
  Device: usb 0x1000 
  Revision: "52.76"
  Driver: "btusb"
  Driver Modules: "btusb"
  Speed: 12 Mbps
  Module Alias: "usb:v148Fp1000d5276dcE0dsc01dp01icE0isc01ip01"
  Driver Info #0:
    Driver Status: btusb is active
    Driver Activation Cmd: "modprobe btusb"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #36 (Hub)

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list