So, in chasing an issue with mouse pairing in another thread I was asked
to upgrade to Fedora 20 to see if my mouse pairing issue was
reproducible on bluez5 given that bluez4 is pretty dead now.
But the same mouse that could be found and paired on bluez4 (Fedora 19)
is not even being found during the search on bluez5 (Fedora 20) on the
exact same hardware (same machine in fact). Bluez5 did manage to see
and pair a headset though, just not this mouse.
What information/tests can I provide to help figure this out?
Cheers,
b.
On Thu, 2013-12-12 at 14:53 +0100, Bastien Nocera wrote:
>
> Is the headset still in the list of paired devices though?
Could be.
> If so, it
> wouldn't show up in the list in the wizard.
That makes sense. I wonder if that was/is the case with the mouse then.
> If you do:
> info 00:0D:E6:68:B4:6F
> in bluetoothctl, you should also see which services your headset uses.
> Some of them aren't supported yet in Fedora (HandsFree for example)
> because the support was removed in bluez itself.
[bluetooth]# info 00:0D:E6:68:B4:6F
Device 00:0D:E6:68:B4:6F
Name: Samsung WEP850
Alias: Samsung WEP850
Class: 0x200404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
> I've just double-checked, and it's not installed by default in F19.
Right. I never had it installed in F19. But my dongle worked anyway,
pressumably without having to use hid2hci
> Maybe you installed it and don't remember, or upgraded from an earlier
> version that had it installed but disabled by default (there used to be
> a separate config file to enable it after installation).
No. I still have my F19 system. I checked and it's not installed. So
clearly this needing it on F20 is something new with bluez5.
> There's plenty of SELinux warnings in there. Maybe you need to enable
> permissive mode, and/or file bugs about those.
Interesting that I don't get that that SELinux troubleshooter icon
notifying me of any problems, and nothing new is in the SELinux Alert
Browser.
b.
On Thu, 2013-12-12 at 14:53 +0100, Bastien Nocera wrote:
<snip>
> There's plenty of SELinux warnings in there. Maybe you need to enable
> permissive mode, and/or file bugs about those.
Never mind, confusing with another headset issue I'm working on :/
On Thu, 2013-12-12 at 07:15 -0500, Brian J. Murrell wrote:
> On Wed, 2013-12-11 at 22:49 +0100, Bastien Nocera wrote:
> >
> > I don't see why it would be a problem in the wizard. You basically
> > didn't have a Bluetooth adapter before you installed bluez-hid2hci.
>
> But of course I also tried the wizard after correcting that. I most
> certainly could understand that the wizard would not have worked before
> running hid2hci and would only assert that the wizard is not working by
> trying it after installing bluez-hid2hci.
>
> So just to be clear, I have a mouse working, so the adapter is
> definitely in a state where bluetooth-wizard should work (right?), yet
> it is not finding the headset I have sitting here in pairing mode right
> this minute.
Is the headset still in the list of paired devices though? If so, it
wouldn't show up in the list in the wizard.
> bluetoothctl certainly sees it:
>
> $ bluetoothctl
> [NEW] Controller 00:02:72:1E:E0:12 pc.interlinx.bc.ca-0 [default]
> [NEW] Device 00:0D:E6:68:B4:6F Samsung WEP850
> [NEW] Device 70:F3:95:3E:92:34 brian-laptop
> [NEW] Device 7C:1E:52:6E:59:D2 Microsoft Sculpt Touch Mouse
If you see it in bluetoothctl without typing scan, that means that
either it was discovered less than 3 minutes ago, or that it's a known
device (so paired or trusted, paired in the case of headsets).
If you do:
info 00:0D:E6:68:B4:6F
in bluetoothctl, you should also see which services your headset uses.
Some of them aren't supported yet in Fedora (HandsFree for example)
because the support was removed in bluez itself.
> > > > Maybe that was somehow auto-run with
> > > > your previous installation?
> > >
> > > I don't really know. It was F19. And that means bluez4. So I guess
> > > this is going to be a transition issue/bug I need to raise on F20.
> >
> > bluez-hid2hci was already an optional package in F19.
>
> But since I didn't have it installed on F19, apparently needing it on
> F20 is a new requirement of Bluez5.
I've just double-checked, and it's not installed by default in F19.
Maybe you installed it and don't remember, or upgraded from an earlier
version that had it installed but disabled by default (there used to be
a separate config file to enable it after installation).
> But really, I don't want to argue about it. I have my machine working
> and have gained a bit of operational knowledge about Bluez5 that will
> serve me well as I migrate machines to F20. I have filed a ticket with
> the Fedora project alerting them to the new requirement. It's now up to
> them to decide how important it is that their F20 users don't have the
> same problem that I had.
There's plenty of SELinux warnings in there. Maybe you need to enable
permissive mode, and/or file bugs about those.
On Wed, 2013-12-11 at 22:49 +0100, Bastien Nocera wrote:
>
> I don't see why it would be a problem in the wizard. You basically
> didn't have a Bluetooth adapter before you installed bluez-hid2hci.
But of course I also tried the wizard after correcting that. I most
certainly could understand that the wizard would not have worked before
running hid2hci and would only assert that the wizard is not working by
trying it after installing bluez-hid2hci.
So just to be clear, I have a mouse working, so the adapter is
definitely in a state where bluetooth-wizard should work (right?), yet
it is not finding the headset I have sitting here in pairing mode right
this minute.
bluetoothctl certainly sees it:
$ bluetoothctl
[NEW] Controller 00:02:72:1E:E0:12 pc.interlinx.bc.ca-0 [default]
[NEW] Device 00:0D:E6:68:B4:6F Samsung WEP850
[NEW] Device 70:F3:95:3E:92:34 brian-laptop
[NEW] Device 7C:1E:52:6E:59:D2 Microsoft Sculpt Touch Mouse
> > > Maybe that was somehow auto-run with
> > > your previous installation?
> >
> > I don't really know. It was F19. And that means bluez4. So I guess
> > this is going to be a transition issue/bug I need to raise on F20.
>
> bluez-hid2hci was already an optional package in F19.
But since I didn't have it installed on F19, apparently needing it on
F20 is a new requirement of Bluez5.
But really, I don't want to argue about it. I have my machine working
and have gained a bit of operational knowledge about Bluez5 that will
serve me well as I migrate machines to F20. I have filed a ticket with
the Fedora project alerting them to the new requirement. It's now up to
them to decide how important it is that their F20 users don't have the
same problem that I had.
Cheers and thanks much for the help!
b.
On Wed, 2013-12-11 at 15:13 -0500, Brian J. Murrell wrote:
> On Wed, 2013-12-11 at 21:25 +0200, Johan Hedberg wrote:
> > Hi Brian,
>
> Hi Johan,
>
> > I'm not sure if I'm interpreting this right, but it seems the device is
> > in HID mode and not HCI (normal Bluetooth) mode?
>
> I dunno. I'm just the user. :-)
>
> > Have you tried running
> > the hid2hci tool (part of BlueZ)?
>
> Not yet. It wasn't installed by default on F20. When I did though,
> things went much better:
>
> $ bluetoothctl
> [NEW] Controller 00:02:72:1E:E0:12 pc.interlinx.bc.ca-0 [default]
> [NEW] Device 00:0D:E6:68:B4:6F Samsung WEP850
> [NEW] Device 70:F3:95:3E:92:34 brian-laptop
> [NEW] Device 7C:1E:52:6E:59:D2 Microsoft Sculpt Touch Mouse
<snip>
> So it looks like it's a gnome bluetooth-wizard problem. I will raise
> some tickets.
I don't see why it would be a problem in the wizard. You basically
didn't have a Bluetooth adapter before you installed bluez-hid2hci.
> > Maybe that was somehow auto-run with
> > your previous installation?
>
> I don't really know. It was F19. And that means bluez4. So I guess
> this is going to be a transition issue/bug I need to raise on F20.
bluez-hid2hci was already an optional package in F19.
On Wed, 2013-12-11 at 21:25 +0200, Johan Hedberg wrote:
> Hi Brian,
Hi Johan,
> I'm not sure if I'm interpreting this right, but it seems the device is
> in HID mode and not HCI (normal Bluetooth) mode?
I dunno. I'm just the user. :-)
> Have you tried running
> the hid2hci tool (part of BlueZ)?
Not yet. It wasn't installed by default on F20. When I did though,
things went much better:
$ bluetoothctl
[NEW] Controller 00:02:72:1E:E0:12 pc.interlinx.bc.ca-0 [default]
[NEW] Device 00:0D:E6:68:B4:6F Samsung WEP850
[NEW] Device 70:F3:95:3E:92:34 brian-laptop
[NEW] Device 7C:1E:52:6E:59:D2 Microsoft Sculpt Touch Mouse
[bluetooth]# agent on
Agent registered
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:02:72:1E:E0:12 Discovering: yes
[CHG] Device 7C:1E:52:6E:59:D2 RSSI: -59
[bluetooth]# scan off
[CHG] Device 7C:1E:52:6E:59:D2 RSSI is nil
Discovery stopped
[CHG] Controller 00:02:72:1E:E0:12 Discovering: no
[bluetooth]# pair 7C:1E:52:6E:59:D2
Attempting to pair with 7C:1E:52:6E:59:D2
[CHG] Device 7C:1E:52:6E:59:D2 Connected: yes
[CHG] Device 7C:1E:52:6E:59:D2 Paired: yes
Pairing successful
[CHG] Device 7C:1E:52:6E:59:D2 Connected: no
[bluetooth]# connect 7C:1E:52:6E:59:D2
Attempting to connect to 7C:1E:52:6E:59:D2
[CHG] Device 7C:1E:52:6E:59:D2 Connected: yes
Connection successful
[CHG] Device 7C:1E:52:6E:59:D2 Modalias: usb:v045Ep077Cd011E
[CHG] Device 7C:1E:52:6E:59:D2 Modalias: usb:v045Ep077Cd011E
[bluetooth]# trust 7C:1E:52:6E:59:D2
Changing 7C:1E:52:6E:59:D2 trust succeeded
[bluetooth]# quit
[DEL] Controller 00:02:72:1E:E0:12 pc.interlinx.bc.ca-0 [default]
So it looks like it's a gnome bluetooth-wizard problem. I will raise
some tickets.
> Maybe that was somehow auto-run with
> your previous installation?
I don't really know. It was F19. And that means bluez4. So I guess
this is going to be a transition issue/bug I need to raise on F20.
Cheers and thanks so much!
b.
Hi Brian,
On Wed, Dec 11, 2013, Brian J. Murrell wrote:
> [ 1472.102375] usb 2-1: USB disconnect, device number 2
> [ 1472.102386] usb 2-1.1: USB disconnect, device number 9
> [ 1472.127401] usb 2-1.2: USB disconnect, device number 10
> [ 1472.141932] usb 2-1.3: USB disconnect, device number 11
> [ 1479.644058] usb 2-1: new full-speed USB device number 12 using ohci-pci
> [ 1479.844081] usb 2-1: New USB device found, idVendor=0a5c, idProduct=4500
> [ 1479.844093] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> [ 1479.844099] usb 2-1: Product: BCM2046B1
> [ 1479.844104] usb 2-1: Manufacturer: Broadcom
> [ 1479.847670] hub 2-1:1.0: USB hub found
> [ 1479.850082] hub 2-1:1.0: 3 ports detected
> [ 1480.151074] usb 2-1.1: new full-speed USB device number 13 using ohci-pci
> [ 1480.250070] usb 2-1.1: New USB device found, idVendor=0a5c, idProduct=4502
> [ 1480.250077] usb 2-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber
> [ 1480.260236] input: HID 0a5c:4502 as /devices/pci0000:00/0000:00:02.0/usb2/2-1
> [ 1480.261860] hid-generic 0003:0A5C:4502.0004: input,hidraw1: USB HID v1.11 Key
> [ 1480.330068] usb 2-1.2: new full-speed USB device number 14 using ohci-pci
> [ 1480.430070] usb 2-1.2: New USB device found, idVendor=0a5c, idProduct=4503
> [ 1480.430079] usb 2-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber
> [ 1480.441241] input: HID 0a5c:4503 as /devices/pci0000:00/0000:00:02.0/usb2/2-1
> [ 1480.442349] hid-generic 0003:0A5C:4503.0005: input,hidraw2: USB HID v1.11 Mou
> [ 1480.513076] usb 2-1.3: new full-speed USB device number 15 using ohci-pci
> [ 1480.626069] usb 2-1.3: New USB device found, idVendor=0a5c, idProduct=2148
> [ 1480.626081] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber
> [ 1480.626088] usb 2-1.3: Product: BCM92046DG-CL1ROM
> [ 1480.626093] usb 2-1.3: Manufacturer: Broadcom Corp
> [ 1480.626098] usb 2-1.3: SerialNumber: XXXXXXXXXXXXXXX
I'm not sure if I'm interpreting this right, but it seems the device is
in HID mode and not HCI (normal Bluetooth) mode? Have you tried running
the hid2hci tool (part of BlueZ)? Maybe that was somehow auto-run with
your previous installation?
Johan
On Wed, 2013-12-11 at 11:21 +0200, Johan Hedberg wrote:
> Hi Brian,
Hi Johan,
> For one thing, it'd be good to determine whether this is a GUI thing (I
> assume you're using the GNOME UI?)
Yeah.
> or something in BlueZ. The way to do
> that would be to use the bluetoothctl tool that's part of BlueZ 5. The
> commands you'd give it would go something like:
>
> agent on
> power on
> scan on
> <wait for mouse to show up>
> scan off
> pair <mouse addr> (optional if the mouse doesn't support pairing)
> connect <mouse addr>
> trust <mouse addr>
Here is what I get:
$ bluetoothctl
[bluetooth]# agent on
Agent registration enabled
[bluetooth]# power on
No default controller available
[bluetooth]# scan on
No default controller available
[bluetooth]#
$ lsb
...
Bus 002 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Unplugging the BT dongle and plugging it back in yields:
[ 1472.102375] usb 2-1: USB disconnect, device number 2
[ 1472.102386] usb 2-1.1: USB disconnect, device number 9
[ 1472.127401] usb 2-1.2: USB disconnect, device number 10
[ 1472.141932] usb 2-1.3: USB disconnect, device number 11
[ 1479.644058] usb 2-1: new full-speed USB device number 12 using ohci-pci
[ 1479.844081] usb 2-1: New USB device found, idVendor=0a5c, idProduct=4500
[ 1479.844093] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1479.844099] usb 2-1: Product: BCM2046B1
[ 1479.844104] usb 2-1: Manufacturer: Broadcom
[ 1479.847670] hub 2-1:1.0: USB hub found
[ 1479.850082] hub 2-1:1.0: 3 ports detected
[ 1480.151074] usb 2-1.1: new full-speed USB device number 13 using ohci-pci
[ 1480.250070] usb 2-1.1: New USB device found, idVendor=0a5c, idProduct=4502
[ 1480.250077] usb 2-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber
[ 1480.260236] input: HID 0a5c:4502 as /devices/pci0000:00/0000:00:02.0/usb2/2-1
[ 1480.261860] hid-generic 0003:0A5C:4502.0004: input,hidraw1: USB HID v1.11 Key
[ 1480.330068] usb 2-1.2: new full-speed USB device number 14 using ohci-pci
[ 1480.430070] usb 2-1.2: New USB device found, idVendor=0a5c, idProduct=4503
[ 1480.430079] usb 2-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber
[ 1480.441241] input: HID 0a5c:4503 as /devices/pci0000:00/0000:00:02.0/usb2/2-1
[ 1480.442349] hid-generic 0003:0A5C:4503.0005: input,hidraw2: USB HID v1.11 Mou
[ 1480.513076] usb 2-1.3: new full-speed USB device number 15 using ohci-pci
[ 1480.626069] usb 2-1.3: New USB device found, idVendor=0a5c, idProduct=2148
[ 1480.626081] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber
[ 1480.626088] usb 2-1.3: Product: BCM92046DG-CL1ROM
[ 1480.626093] usb 2-1.3: Manufacturer: Broadcom Corp
[ 1480.626098] usb 2-1.3: SerialNumber: XXXXXXXXXXXXXXX
Cheers,
b.
Hi Brian,
On Tue, Dec 10, 2013, Brian J. Murrell wrote:
> So, in chasing an issue with mouse pairing in another thread I was asked
> to upgrade to Fedora 20 to see if my mouse pairing issue was
> reproducible on bluez5 given that bluez4 is pretty dead now.
>
> But the same mouse that could be found and paired on bluez4 (Fedora 19)
> is not even being found during the search on bluez5 (Fedora 20) on the
> exact same hardware (same machine in fact). Bluez5 did manage to see
> and pair a headset though, just not this mouse.
>
> What information/tests can I provide to help figure this out?
For one thing, it'd be good to determine whether this is a GUI thing (I
assume you're using the GNOME UI?) or something in BlueZ. The way to do
that would be to use the bluetoothctl tool that's part of BlueZ 5. The
commands you'd give it would go something like:
agent on
power on
scan on
<wait for mouse to show up>
scan off
pair <mouse addr> (optional if the mouse doesn't support pairing)
connect <mouse addr>
trust <mouse addr>
Johan