Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #224907 > unrolled thread

bluetooth keyboard

Started bymick crane <mick.crane@gmail.com>
First post2020-07-17 21:10 +0200
Last post2020-07-18 21:40 +0200
Articles 8 — 4 participants

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  bluetooth keyboard mick crane <mick.crane@gmail.com> - 2020-07-17 21:10 +0200
    Re: bluetooth keyboard Dan Ritter <dsr@randomstring.org> - 2020-07-17 22:20 +0200
      Re: bluetooth keyboard mick crane <mick.crane@gmail.com> - 2020-07-17 23:30 +0200
        Re: bluetooth keyboard riveravaldez <riveravaldezmail@gmail.com> - 2020-07-18 01:00 +0200
        Re: bluetooth keyboard deloptes <deloptes@gmail.com> - 2020-07-18 02:20 +0200
          Re: bluetooth keyboard mick crane <mick.crane@gmail.com> - 2020-07-18 14:50 +0200
            Re: bluetooth keyboard deloptes <deloptes@gmail.com> - 2020-07-18 21:10 +0200
              Re: bluetooth keyboard mick crane <mick.crane@gmail.com> - 2020-07-18 21:40 +0200

#224907 — bluetooth keyboard

Frommick crane <mick.crane@gmail.com>
Date2020-07-17 21:10 +0200
Subjectbluetooth keyboard
Message-ID<AtDU5-8k7-7@gated-at.bofh.it>
hello,
somebody gave me an old macmini and a bluetooth keyboard.
I don't know anything about bluetooth.
I'd like to use the keyboard with buster because the wired keyboard wire 
is not long enough.
I got a usb bluetooth dongle (whatever they are called)
The kernel seems to see it from dmesg

[   84.976912] usb 3-2: new low-speed USB device number 3 using uhci_hcd
[   85.173975] usb 3-2: New USB device found, idVendor=046d, 
idProduct=c31c, bcdDevice=64.00
[   85.173979] usb 3-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[   85.173982] usb 3-2: Product: USB Keyboard
[   85.173984] usb 3-2: Manufacturer: Logitech
[   85.210624] input: Logitech USB Keyboard as 
/devices/pci0000:00/0000:00:1a.1/usb3/3-2/3-2:1.0/0003:046D:C31C.0002/input/input20
[   85.269388] hid-generic 0003:046D:C31C.0002: input,hidraw1: USB HID 
v1.10 Keyboard [Logitech USB Keyboard] on usb-0000:00:1a.1-2/input0
[   85.303712] input: Logitech USB Keyboard Consumer Control as 
/devices/pci0000:00/0000:00:1a.1/usb3/3-2/3-2:1.1/0003:046D:C31C.0003/input/input21
[   85.361073] input: Logitech USB Keyboard System Control as 
/devices/pci0000:00/0000:00:1a.1/usb3/3-2/3-2:1.1/0003:046D:C31C.0003/input/input22
[   85.361251] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID 
v1.10 Device [Logitech USB Keyboard] on usb-0000:00:1a.1-2/input1

but the desktop menu item to select the bluetooth adapter does not find 
any adapter.
It appears to be there.

root@slinky:~$ rfkill
ID TYPE      DEVICE      SOFT      HARD
  0 bluetooth hci0   unblocked unblocked
root@slinky:~$ bluetoothctl
Agent registered
[bluetooth]# devices
No default controller available
[bluetooth]#

what to do to enable the adapter and get keyboard working ?

regards

mick
-- 
Key ID    4BFEBB31

[toc] | [next] | [standalone]


#224908

FromDan Ritter <dsr@randomstring.org>
Date2020-07-17 22:20 +0200
Message-ID<AtEZP-u8-1@gated-at.bofh.it>
In reply to#224907
mick crane wrote: 
> hello,
> somebody gave me an old macmini and a bluetooth keyboard.
> I don't know anything about bluetooth.
> I'd like to use the keyboard with buster because the wired keyboard wire is
> not long enough.
> I got a usb bluetooth dongle (whatever they are called)
> The kernel seems to see it from dmesg
> 
> [   84.976912] usb 3-2: new low-speed USB device number 3 using uhci_hcd
> [   85.173975] usb 3-2: New USB device found, idVendor=046d, idProduct=c31c,
> bcdDevice=64.00
> [   85.173979] usb 3-2: New USB device strings: Mfr=1, Product=2,
> SerialNumber=0
> [   85.173982] usb 3-2: Product: USB Keyboard
> [   85.173984] usb 3-2: Manufacturer: Logitech
> [   85.210624] input: Logitech USB Keyboard as /devices/pci0000:00/0000:00:1a.1/usb3/3-2/3-2:1.0/0003:046D:C31C.0002/input/input20
> [   85.269388] hid-generic 0003:046D:C31C.0002: input,hidraw1: USB HID v1.10
> Keyboard [Logitech USB Keyboard] on usb-0000:00:1a.1-2/input0
> [   85.303712] input: Logitech USB Keyboard Consumer Control as /devices/pci0000:00/0000:00:1a.1/usb3/3-2/3-2:1.1/0003:046D:C31C.0003/input/input21
> [   85.361073] input: Logitech USB Keyboard System Control as /devices/pci0000:00/0000:00:1a.1/usb3/3-2/3-2:1.1/0003:046D:C31C.0003/input/input22
> [   85.361251] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID v1.10
> Device [Logitech USB Keyboard] on usb-0000:00:1a.1-2/input1

That's not a bluetooth keyboard. That's a Logitech proprietary
dongle wireless keyboard. Nothing wrong with that.

Since the kernel sees it as a HID (human interface device), it
should be a keyboard already.

> what to do to enable the adapter and get keyboard working ?

It should be working. If you're in X, maybe you don't have
permissions to use /dev/input/* ? Put yourself in the input
group.

-dsr-

[toc] | [prev] | [next] | [standalone]


#224909

Frommick crane <mick.crane@gmail.com>
Date2020-07-17 23:30 +0200
Message-ID<AtG5z-169-5@gated-at.bofh.it>
In reply to#224908
On 2020-07-17 21:16, Dan Ritter wrote:
> mick crane wrote:
>> hello,
>> somebody gave me an old macmini and a bluetooth keyboard.
>> I don't know anything about bluetooth.
>> I'd like to use the keyboard with buster because the wired keyboard 
>> wire is
>> not long enough.
>> I got a usb bluetooth dongle (whatever they are called)
>> The kernel seems to see it from dmesg
>> 
>> [   84.976912] usb 3-2: new low-speed USB device number 3 using 
>> uhci_hcd
>> [   85.173975] usb 3-2: New USB device found, idVendor=046d, 
>> idProduct=c31c,
>> bcdDevice=64.00
>> [   85.173979] usb 3-2: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=0
>> [   85.173982] usb 3-2: Product: USB Keyboard
>> [   85.173984] usb 3-2: Manufacturer: Logitech
>> [   85.210624] input: Logitech USB Keyboard as 
>> /devices/pci0000:00/0000:00:1a.1/usb3/3-2/3-2:1.0/0003:046D:C31C.0002/input/input20
>> [   85.269388] hid-generic 0003:046D:C31C.0002: input,hidraw1: USB HID 
>> v1.10
>> Keyboard [Logitech USB Keyboard] on usb-0000:00:1a.1-2/input0
>> [   85.303712] input: Logitech USB Keyboard Consumer Control as 
>> /devices/pci0000:00/0000:00:1a.1/usb3/3-2/3-2:1.1/0003:046D:C31C.0003/input/input21
>> [   85.361073] input: Logitech USB Keyboard System Control as 
>> /devices/pci0000:00/0000:00:1a.1/usb3/3-2/3-2:1.1/0003:046D:C31C.0003/input/input22
>> [   85.361251] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID 
>> v1.10
>> Device [Logitech USB Keyboard] on usb-0000:00:1a.1-2/input1
> 
> That's not a bluetooth keyboard. That's a Logitech proprietary
> dongle wireless keyboard. Nothing wrong with that.
> 
> Since the kernel sees it as a HID (human interface device), it
> should be a keyboard already.
> 
>> what to do to enable the adapter and get keyboard working ?
> 
> It should be working. If you're in X, maybe you don't have
> permissions to use /dev/input/* ? Put yourself in the input
> group.
> 
> -dsr-

added myself to input group but no joy.
keyboard has sticker "Generic Bluetooth Apple keyboard".
I use wireless mouse which Just Works.
Bluetooth Dongle I think was described as for Apple.
keyboard and dongle worked on macmini.
I'd have thought that Blueman would see the adapter.

mick
-- 
Key ID    4BFEBB31

[toc] | [prev] | [next] | [standalone]


#224910

Fromriveravaldez <riveravaldezmail@gmail.com>
Date2020-07-18 01:00 +0200
Message-ID<AtHuG-1Ok-1@gated-at.bofh.it>
In reply to#224909
> added myself to input group but no joy.
> keyboard has sticker "Generic Bluetooth Apple keyboard".
> I use wireless mouse which Just Works.
> Bluetooth Dongle I think was described as for Apple.
> keyboard and dongle worked on macmini.
> I'd have thought that Blueman would see the adapter.

Just in case?

«make sure you have bluetoothctl and hcitool installed.»[1]

[1] https://wiki.archlinux.org/index.php/Apple_Keyboard#Magic_Keyboard_does_not_connect

[toc] | [prev] | [next] | [standalone]


#224911

Fromdeloptes <deloptes@gmail.com>
Date2020-07-18 02:20 +0200
Message-ID<AtIK5-2HK-1@gated-at.bofh.it>
In reply to#224909
mick crane wrote:

> added myself to input group but no joy.
> keyboard has sticker "Generic Bluetooth Apple keyboard".
> I use wireless mouse which Just Works.
> Bluetooth Dongle I think was described as for Apple.
> keyboard and dongle worked on macmini.
> I'd have thought that Blueman would see the adapter.

[bluetooth]# show

gives the controller (the dongle)

[bluetooth]# discoverable on

enables visibility

[bluetooth]# scan on

searches for devices

when (and if) found do the pairing and trust the device.

[toc] | [prev] | [next] | [standalone]


#224927

Frommick crane <mick.crane@gmail.com>
Date2020-07-18 14:50 +0200
Message-ID<AtUrT-1dQ-3@gated-at.bofh.it>
In reply to#224911
On 2020-07-18 01:11, deloptes wrote:
> mick crane wrote:
> 
>> added myself to input group but no joy.
>> keyboard has sticker "Generic Bluetooth Apple keyboard".
>> I use wireless mouse which Just Works.
>> Bluetooth Dongle I think was described as for Apple.
>> keyboard and dongle worked on macmini.
>> I'd have thought that Blueman would see the adapter.
> 
> [bluetooth]# show
> 
> gives the controller (the dongle)
> 
> [bluetooth]# discoverable on
> 
> enables visibility
> 
> [bluetooth]# scan on
> 
> searches for devices
> 
> when (and if) found do the pairing and trust the device.

root@slinky:~$ lsusb
....
Bus 004 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 004 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
....
root@slinky:~$ hciconfig
hci0:   Type: Primary  Bus: USB
         BD Address: 00:1A:7D:DA:71:11  ACL MTU: 679:9  SCO MTU: 48:16
         DOWN
         RX bytes:2296 acl:0 sco:0 events:120 errors:0
         TX bytes:1472 acl:0 sco:0 commands:120 errors:0

root@slinky:~$ hciconfig -a hci0 up
Can't init device hci0: Operation not supported (95)

root@slinky:~$ systemctl start bluetooth
root@slinky:~$ bluetoothctl
Agent registered
[bluetooth]# show
No default controller available

seems a lot have people have trouble with this cheap bluetooth dongle
Bus 004 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)

As I don't really know what I'm doing I give up, I'll move the PC.

mick
-- 
Key ID    4BFEBB31

[toc] | [prev] | [next] | [standalone]


#224935

Fromdeloptes <deloptes@gmail.com>
Date2020-07-18 21:10 +0200
Message-ID<Au0nD-4Vh-3@gated-at.bofh.it>
In reply to#224927
mick crane wrote:

> On 2020-07-18 01:11, deloptes wrote:
>> mick crane wrote:
>> 
>>> added myself to input group but no joy.
>>> keyboard has sticker "Generic Bluetooth Apple keyboard".
>>> I use wireless mouse which Just Works.
>>> Bluetooth Dongle I think was described as for Apple.
>>> keyboard and dongle worked on macmini.
>>> I'd have thought that Blueman would see the adapter.
>> 
>> [bluetooth]# show
>> 
>> gives the controller (the dongle)
>> 
>> [bluetooth]# discoverable on
>> 
>> enables visibility
>> 
>> [bluetooth]# scan on
>> 
>> searches for devices
>> 
>> when (and if) found do the pairing and trust the device.
> 
> root@slinky:~$ lsusb
> ....
> Bus 004 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120
> Bus 004 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
> Dongle (HCI mode)
> ....
> root@slinky:~$ hciconfig
> hci0:   Type: Primary  Bus: USB
>          BD Address: 00:1A:7D:DA:71:11  ACL MTU: 679:9  SCO MTU: 48:16
>          DOWN
>          RX bytes:2296 acl:0 sco:0 events:120 errors:0
>          TX bytes:1472 acl:0 sco:0 commands:120 errors:0
> 
> root@slinky:~$ hciconfig -a hci0 up
> Can't init device hci0: Operation not supported (95)
> 
> root@slinky:~$ systemctl start bluetooth
> root@slinky:~$ bluetoothctl
> Agent registered
> [bluetooth]# show
> No default controller available
> 
> seems a lot have people have trouble with this cheap bluetooth dongle
> Bus 004 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
> Dongle (HCI mode)
> 
> As I don't really know what I'm doing I give up, I'll move the PC.
> 
> mick

Seems that I have this too

$ lsusb
Bus 002 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
Dongle (HCI mode)

I've been using this since 2007 - all rocks

When I looked in the Google glass it told me this

https://forum.manjaro.org/t/bluetooth-usb-adapter-not-being-recognized/142636/12
which lead to this
https://www.reddit.com/r/AnnePro/comments/e76ij8/csr_40_bluetooth_dongle_on_linux/

Are you sure it is not one of those described in the articles. If so - it's
bad luck. Meanwhile I am rethinking my position on dead penalty for
producers of fakes. It is really really bad out there. An the price is not
always a guarantee for good quality, but cheep is usually a sign for bad
quality.

In case it is not one of those reported not working, when enabled, below is
some output to compare. I also never had to use hciconfig to configure it -
it is systemd doing it via I don't know what - probably udev.

I was also thinking of some details:
- Does it work on other machines - different kernel or OS?
- Here ATM it is running on 4.19.
- I'm just not sure if it needs firmware. I have not rebooted the PC for
months and I can't find anything in the logs.
- What about groups (are you in bluetooth)?
- What about dbus?

regards

# hciconfig
hci0:   Type: Primary  Bus: USB
        BD Address: 00:10:60:xx:xx:xx ACL MTU: 310:10  SCO MTU: 64:8
        UP RUNNING PSCAN
        RX bytes:126491975 acl:406135 sco:3168 events:4620 errors:0
        TX bytes:707462 acl:3276 sco:3173 commands:1463 errors:0

# systemctl status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
   Active: active (running) since Sat 2020-07-18 20:53:04 CEST; 2s ago
     Docs: man:bluetoothd(8)
 Main PID: 7509 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   Memory: 2.1M
   CGroup: /system.slice/bluetooth.service
           └─7509 /usr/lib/bluetooth/bluetoothd

Jul 18 20:53:04 fujitsu systemd[1]: Starting Bluetooth service...
Jul 18 20:53:04 fujitsu bluetoothd[7509]: Bluetooth daemon 5.50
Jul 18 20:53:04 fujitsu bluetoothd[7509]: Starting SDP server
Jul 18 20:53:04 fujitsu systemd[1]: Started Bluetooth service.
Jul 18 20:53:04 fujitsu bluetoothd[7509]: Bluetooth management interface
1.14 initialized
Jul 18 20:53:04 fujitsu bluetoothd[7509]: Sap driver initialization failed.
Jul 18 20:53:04 fujitsu bluetoothd[7509]: sap-server: Operation not
permitted (1)
Jul 18 20:53:04 fujitsu bluetoothd[7509]: Endpoint registered: sender=:1.35
path=/MediaEndpoint/A2DPSource
Jul 18 20:53:04 fujitsu bluetoothd[7509]: Endpoint registered: sender=:1.35
path=/MediaEndpoint/A2DPSink


# hciconfig -a version hci0
Warning: unknown command - "hci0"
hci0:   Type: Primary  Bus: USB
        BD Address: 00:10:60:xx:xx:xx  ACL MTU: 310:10  SCO MTU: 64:8
        UP RUNNING PSCAN
        RX bytes:126493351 acl:406135 sco:3168 events:4725 errors:0
        TX bytes:718970 acl:3276 sco:3173 commands:1568 errors:0
        Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x83
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'fujitsu'
        Class: 0x3c0104
        Service Classes: Rendering, Capturing, Object Transfer, Audio
        Device Class: Computer, Desktop workstation
        HCI Version: 2.1 (0x4)  Revision: 0x12e7
        LMP Version: 2.1 (0x4)  Subversion: 0x12e7
        Manufacturer: Cambridge Silicon Radio (10)

[toc] | [prev] | [next] | [standalone]


#224937

Frommick crane <mick.crane@gmail.com>
Date2020-07-18 21:40 +0200
Message-ID<Au0QG-54G-9@gated-at.bofh.it>
In reply to#224935
On 2020-07-18 20:08, deloptes wrote:
<snipped>
> When I looked in the Google glass it told me this
> 
> https://forum.manjaro.org/t/bluetooth-usb-adapter-not-being-recognized/142636/12
> which lead to this
> https://www.reddit.com/r/AnnePro/comments/e76ij8/csr_40_bluetooth_dongle_on_linux/
<snipped>

yup looks exactly the same, can't be bothered to take it to bits to look 
at chip or start patching modules.
Still, got more of a clue about bluetooth now.
cheers
mick
-- 
Key ID    4BFEBB31

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web