bluetooth keyboard done gone nuts
i use a logitech k270 keyboard and mouse for several years we had power outage for a couple of days now the keyboard is nuts the mouse works i get odd multiple sequences with a few, not all, keys if i type "ls" i get "l7s9u" space is "[ " there are a dozen or so other keys that are screwy this machine is running bullseye i plugged the dongle into a machine running bookworm and the same i got to a console via ctrl+alt+f1 and the same keyboard has fresh batteries
Re: bluetooth keyboard
On 2021-08-09 02:47, Polyna-Maude Racicot-Summerside wrote: Does this help ? OK, it is no great hardship to wait a second or two. mick -- Key ID4BFEBB31
Re: bluetooth keyboard
Klaus Singvogel wrote: > This means, that I can't change nor access my BIOS / UEFI settings by a BT > keyboard? It depends on the hardware and BIOS. Some newer especially with integrated BT would implement a HID driver, so that you could, but if it would work with each keyboard etc. no idea. It is risky ... keep one with USB cable around for the case. -- FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
Re: bluetooth keyboard
Polyna-Maude Racicot-Summerside wrote: > On 2021-08-08 6:14 p.m., mick crane wrote: > > I like the little generic bluetooth keyboards but it is annoying that > > when they go to sleep it takes a few seconds for everything to wake up > > so you can commence typing. [...] > It's also one of the > reason that make it impossible to use a Bluetooth keyboard to > communicate with GRUB or another bootloader or simply access the system > configuration of your PC. This means, that I can't change nor access my BIOS / UEFI settings by a BT keyboard? Thanks in advance. Best regards, Klaus. -- Klaus Singvogel GnuPG-Key-ID: 1024R/5068792D 1994-06-27
Re: bluetooth keyboard
Hi, On 2021-08-08 6:14 p.m., mick crane wrote: > Debian 11 > I like the little generic bluetooth keyboards but it is annoying that > when they go to sleep it takes a few seconds for everything to wake up > so you can commence typing. > Is it perhaps to do with the PC polling the keyboard for activity and > can that be made quicker ? No, this is related to the way the bluetooth stack work. When you use a hardware keyboard (USB or PS/2 for example), the interface is purely thru the use of a driver in the kernel (USB driver or PS/2 driver). When you use a Bluetooth keyboard, the driver in the kernel or as a module is only responsible for the dongle itself. There's a software stack that manage authentication, connection to devices and more. This software stack has to be launched so the keyboard can communicate with the PC (or the PC get info from the keyboard). This take much more time than a simple USB driver. It's also one of the reason that make it impossible to use a Bluetooth keyboard to communicate with GRUB or another bootloader or simply access the system configuration of your PC. Does this help ? > mick Sincerely, with solidarity, -- Polyna-Maude R.-Summerside -Be smart, Be wise, Support opensource development OpenPGP_signature Description: OpenPGP digital signature
bluetooth keyboard
Debian 11 I like the little generic bluetooth keyboards but it is annoying that when they go to sleep it takes a few seconds for everything to wake up so you can commence typing. Is it perhaps to do with the PC polling the keyboard for activity and can that be made quicker ? mick -- Key ID4BFEBB31
Re: external bluetooth keyboard / mouse paired but not used
Il 15/07/20 10:39, deloptes ha scritto: Andrea Borgia wrote: Devices are connected and show up in logs, that is where it gets weird. Next week I'm home and I'll be able to try a physical kbd / touchpad combo. You may have a look at the X server configuration. I don't use BT inputs, but I recall there could be some additional settings in the following sections, or needed to add those. I'm sure you can find instructions. I have plugged in a dongle for a wireless keyboard (non BT) and that worked out of the box without restarting. A proper BT kbd / touchpad combo also works as expected, so the Linux configuration seems to be just fine, without any changes. I'll give feedback to the author of the app, we'll see if it can be fixed. Thanks, Andrea.
Re: bluetooth keyboard
On 2020-07-18 20:08, deloptes wrote: 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/ 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 ID4BFEBB31
Re: bluetooth keyboard
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)
Re: bluetooth keyboard
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 ID4BFEBB31
Re: bluetooth keyboard
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.
Re: bluetooth keyboard
> 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
Re: bluetooth keyboard
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/pci:00/: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-:00:1a.1-2/input0 [ 85.303712] input: Logitech USB Keyboard Consumer Control as /devices/pci:00/: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/pci:00/: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-: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 ID4BFEBB31
Re: bluetooth keyboard
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/pci:00/: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-:00:1a.1-2/input0 > [ 85.303712] input: Logitech USB Keyboard Consumer Control as > /devices/pci:00/: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/pci:00/: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-: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-
bluetooth keyboard
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/pci:00/: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-:00:1a.1-2/input0 [ 85.303712] input: Logitech USB Keyboard Consumer Control as /devices/pci:00/: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/pci:00/: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-: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 ID4BFEBB31
Re: external bluetooth keyboard / mouse paired but not used
Il 15/07/20 10:39, deloptes ha scritto: You may have a look at the X server configuration. I don't use BT inputs, but I recall there could be some additional settings in the following sections, or needed to add those. I'm sure you can find instructions. I don't have a server config file, only a snippet which I have added to force taptoclick for the internal touchpad. I'll try adding another one as you suggested and report back once I have also tried a real BT mouse / kbd combo. In the meanwhile, this is an excerpt from Xorg.log: [ 5691.217] (II) config/udev: Adding input device abo-motog5splus Keyboard (/dev/input/event21) [ 5691.217] (**) abo-motog5splus Keyboard: Applying InputClass "libinput keyboard catchall" [ 5691.217] (II) Using input driver 'libinput' for 'abo-motog5splus Keyboard' [ 5691.217] (**) abo-motog5splus Keyboard: always reports core events [ 5691.217] (**) Option "Device" "/dev/input/event21" [ 5691.217] (**) Option "_source" "server/udev" [ 5691.220] (II) event21 - abo-motog5splus Keyboard: is tagged by udev as: Keyboard [ 5691.220] (II) event21 - abo-motog5splus Keyboard: device is a keyboard [ 5691.221] (II) event21 - abo-motog5splus Keyboard: device removed [ 5691.237] (**) Option "config_info" "udev:/sys/devices/virtual/misc/uhid/0005:001D:1200.0009/input/input33/event21" [ 5691.237] (II) XINPUT: Adding extended input device "abo-motog5splus Keyboard" (type: KEYBOARD, id 17) [ 5691.237] (**) Option "xkb_model" "pc102" [ 5691.237] (**) Option "xkb_layout" "us" [ 5691.237] (WW) Option "xkb_variant" requires a string value [ 5691.237] (**) Option "xkb_options" "compose:ralt,terminate:ctrl_alt_bksp" [ 5691.242] (II) event21 - abo-motog5splus Keyboard: is tagged by udev as: Keyboard [ 5691.243] (II) event21 - abo-motog5splus Keyboard: device is a keyboard [ 5691.247] (II) config/udev: Adding input device abo-motog5splus Mouse (/dev/input/event22) [ 5691.247] (**) abo-motog5splus Mouse: Applying InputClass "libinput pointer catchall" [ 5691.247] (II) Using input driver 'libinput' for 'abo-motog5splus Mouse' [ 5691.247] (**) abo-motog5splus Mouse: always reports core events [ 5691.247] (**) Option "Device" "/dev/input/event22" [ 5691.247] (**) Option "_source" "server/udev" [ 5691.249] (II) event22 - abo-motog5splus Mouse: is tagged by udev as: Mouse [ 5691.250] (II) event22 - abo-motog5splus Mouse: device is a pointer [ 5691.250] (II) event22 - abo-motog5splus Mouse: device removed [ 5691.285] (**) Option "config_info" "udev:/sys/devices/virtual/misc/uhid/0005:001D:1200.0009/input/input34/event22" [ 5691.285] (II) XINPUT: Adding extended input device "abo-motog5splus Mouse" (type: MOUSE, id 18) [ 5691.290] (**) Option "AccelerationScheme" "none" [ 5691.293] (**) abo-motog5splus Mouse: (accel) selected scheme none/0 [ 5691.293] (**) abo-motog5splus Mouse: (accel) acceleration factor: 2.000 [ 5691.293] (**) abo-motog5splus Mouse: (accel) acceleration threshold: 4 [ 5691.296] (II) event22 - abo-motog5splus Mouse: is tagged by udev as: Mouse [ 5691.297] (II) event22 - abo-motog5splus Mouse: device is a pointer [ 5691.299] (II) config/udev: Adding input device abo-motog5splus Consumer Control (/dev/input/event23) [ 5691.299] (**) abo-motog5splus Consumer Control: Applying InputClass "libinput keyboard catchall" [ 5691.299] (II) Using input driver 'libinput' for 'abo-motog5splus Consumer Control' [ 5691.299] (**) abo-motog5splus Consumer Control: always reports core events [ 5691.299] (**) Option "Device" "/dev/input/event23" [ 5691.299] (**) Option "_source" "server/udev" [ 5691.301] (II) event23 - abo-motog5splus Consumer Control: is tagged by udev as: Keyboard [ 5691.301] (II) event23 - abo-motog5splus Consumer Control: device is a keyboard [ 5691.302] (II) event23 - abo-motog5splus Consumer Control: device removed [ 5691.321] (II) libinput: abo-motog5splus Consumer Control: needs a virtual subdevice [ 5691.321] (**) Option "config_info" "udev:/sys/devices/virtual/misc/uhid/0005:001D:1200.0009/input/input35/event23" [ 5691.321] (II) XINPUT: Adding extended input device "abo-motog5splus Consumer Control" (type: MOUSE, id 19) [ 5691.324] (**) Option "AccelerationScheme" "none" [ 5691.328] (**) abo-motog5splus Consumer Control: (accel) selected scheme none/0 [ 5691.328] (**) abo-motog5splus Consumer Control: (accel) acceleration factor: 2.000 [ 5691.328] (**) abo-motog5splus Consumer Control: (accel) acceleration threshold: 4 [ 5691.331] (II) event23 - abo-motog5splus Consumer Control: is tagged by udev as: Keyboard [ 5691.332] (II) event23 - abo-motog5splus Consumer Control: device is a keyboard [ 5691.334] (**) abo-motog5splus Consumer Control: Applying InputClass "libinput keyboard catchall" [ 5691.334] (II) Using input driver 'libinput' for 'abo-motog5splus Consumer Control' [ 5691.334] (**) abo-motog5splus Consumer Control: always reports core events [ 5691.334] (**) Option
Re: external bluetooth keyboard / mouse paired but not used
Andrea Borgia wrote: > Devices are connected and show up in logs, that is where it gets weird. > Next week I'm home and I'll be able to try a physical kbd / touchpad > combo. You may have a look at the X server configuration. I don't use BT inputs, but I recall there could be some additional settings in the following sections, or needed to add those. I'm sure you can find instructions. Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5 6 7" EndSection
Re: external bluetooth keyboard / mouse paired but not used
Il 14/07/20 23:56, Bob Weber ha scritto: On 7/14/20 1:11 PM, Andrea Borgia wrote: I bought a bluetooth keyboard with the intention to use it with our Samsung tablets. It just worked in KDE to my surprise. Is the mouse a part of the keyboard or a separate device? It is in an app which emulates multiple devices at the same time. Also, the bt adapter is embedded in the laptop, no need to have an external adapter in my case. Have you gotten audio through to a bt device? Not my use case and at the moment I don't have a headset to test it anyway. If there no bt widget in the tray click on the up arrow to bring up the "Status and Notifications" panel and see if bt is there. If so click on bt and enable bt for the system. Devices are connected and show up in logs, that is where it gets weird. Next week I'm home and I'll be able to try a physical kbd / touchpad combo. Regards, Andrea.
Re: external bluetooth keyboard / mouse paired but not used
On 7/14/20 1:11 PM, Andrea Borgia wrote: Il 12/07/20 20:17, Andrea Borgia ha scritto: After the pairing, I can see in the logs that there are 3 new devices (keyboard, mouse, multimedia controls) as input devices but that's it: it doesn't work in parallel with the internal touchpad and keyboard. I've tried both with KDE and on console, no go. Are there any special settings I have to make? No ideas? I bought a bluetooth keyboard with the intention to use it with our Samsung tablets. It just worked in KDE to my surprise. Is the mouse a part of the keyboard or a separate device? These comments are for KDE. I use bluetooth all the time to play audio on bt headphones and through a bt gateway to my HIFI for audio. I've been able to connect a bt headphone and the bt gateway at the same time but I don't think audio worked after that until I disconnected both and then reconnected to just one. So try using just ONE bt device (like the keyboard) and see if that works. If so you may need to get another usb bt device (plugs into your computer) for the mouse. Have you gotten audio through to a bt device? Do you have the bt tray widget visible ... a bt symbol in the tray. If so then you should be able to see what is connected. Make sure only one device is connected. Some devices tend to auto connect after pairing so turn off all bt devices except the one your are testing. You might have to reboot after you are sure just one device is on. There is also an application bluetoothctl that can restart bt devices but it is just as easy to reboot. If there no bt widget in the tray click on the up arrow to bring up the "Status and Notifications" panel and see if bt is there. If so click on bt and enable bt for the system. -- *...Bob*
Re: external bluetooth keyboard / mouse paired but not used
Il 12/07/20 20:17, Andrea Borgia ha scritto: After the pairing, I can see in the logs that there are 3 new devices (keyboard, mouse, multimedia controls) as input devices but that's it: it doesn't work in parallel with the internal touchpad and keyboard. I've tried both with KDE and on console, no go. Are there any special settings I have to make? No ideas?
external bluetooth keyboard / mouse paired but not used
Hello. I'm trying to use this app on my phone to have a spare BT mouse / keyboard combo: https://play.google.com/store/apps/details?id=io.appground.blek Tested with WIndows on my laptop, it works out of the box, no special settings required beyond pairing. When running Linux on the same system, I can perform the pairing... well, actually, I have to: unless you copy the BT keys from Windows to Linux or viceversa, you'll have to anyway. After the pairing, I can see in the logs that there are 3 new devices (keyboard, mouse, multimedia controls) as input devices but that's it: it doesn't work in parallel with the internal touchpad and keyboard. I've tried both with KDE and on console, no go. Are there any special settings I have to make? Thanks, Andrea.
Re: bluetooth keyboard prevents suspend
On 28/01/18 10:32, Karol Augustin wrote: I know that id doesn't fix the problem but as you won't be able to use usb wakup functionality with bluetooth keyboard anyway maybe just disable it in BIOS and it should fix the problem for now. My idea is to rely on another usb device to wake up the computer. For now, my logitech (wireless) mouse doesn't do that but I think it is possible. I will look into it. So disable the BT keyboard, wake up with the mouse. Pétùr
Re: bluetooth keyboard prevents suspend
On 28/01/18 14:28, tv.deb...@googlemail.com wrote: Hello, I am not very familiar with Bluetooth which I tend to disable entirely on my computers, but in case of such problems with buggy hardware I use the TLP package. The configuration allows to precisely choose what hardware (pointing devices, gpu...) or service (wifi, bluetooth...) to enable/disable during sleep and wake-ups. Maybe it can handle your keyboard too. Thanks, it's help! TLP allows indeed to disable specificly one USB device: # Set to 0 to disable, 1 to enable USB autosuspend feature. USB_AUTOSUSPEND=1 # Exclude listed devices from USB autosuspend (separate with spaces). # Use lsusb to get the ids. # Note: input devices (usbhid) are excluded automatically USB_BLACKLIST="0a12:0001" I disabled my usb connected bluetooth dongle (so my usb keyboard doesn't wake up my system). Thanks again! Pétùr
Re: bluetooth keyboard prevents suspend
On 2018-01-28 8:02, Pétùr wrote: > I have set my BIOS configuration to allow usb devices to wake up the > computer. I used my mouse or my usb keyboard to wake up the system. > > But I just replaced my usb keyboard with a bluetooth one. My bluetooth > adapter is a dongle connected to a usb port. > > Everytime I suspend (no matter which method), the computer wake up > immediately (because it detects some connecting activity from the > bluetooth keyboard). > > I have to disconnect the bluetooth keyboard with the hardware button > before suspending. Then I can suspend and wakeup with the mouse. > > Is there a way to suspend without turning off the buetooth keyboard first? > > Cheers, > Pétùr I know that id doesn't fix the problem but as you won't be able to use usb wakup functionality with bluetooth keyboard anyway maybe just disable it in BIOS and it should fix the problem for now. -- Karol Augustin ka...@augustin.pl http://karolaugustin.pl/ +353 85 775 5312
Re: bluetooth keyboard prevents suspend
On 28/01/2018 13:32, Pétùr wrote: I have set my BIOS configuration to allow usb devices to wake up the computer. I used my mouse or my usb keyboard to wake up the system. But I just replaced my usb keyboard with a bluetooth one. My bluetooth adapter is a dongle connected to a usb port. Everytime I suspend (no matter which method), the computer wake up immediately (because it detects some connecting activity from the bluetooth keyboard). I have to disconnect the bluetooth keyboard with the hardware button before suspending. Then I can suspend and wakeup with the mouse. Is there a way to suspend without turning off the buetooth keyboard first? Cheers, Pétùr Hello, I am not very familiar with Bluetooth which I tend to disable entirely on my computers, but in case of such problems with buggy hardware I use the TLP package. The configuration allows to precisely choose what hardware (pointing devices, gpu...) or service (wifi, bluetooth...) to enable/disable during sleep and wake-ups. Maybe it can handle your keyboard too. Hope it helps.
bluetooth keyboard prevents suspend
I have set my BIOS configuration to allow usb devices to wake up the computer. I used my mouse or my usb keyboard to wake up the system. But I just replaced my usb keyboard with a bluetooth one. My bluetooth adapter is a dongle connected to a usb port. Everytime I suspend (no matter which method), the computer wake up immediately (because it detects some connecting activity from the bluetooth keyboard). I have to disconnect the bluetooth keyboard with the hardware button before suspending. Then I can suspend and wakeup with the mouse. Is there a way to suspend without turning off the buetooth keyboard first? Cheers, Pétùr
Re: Bluetooth keyboard trouble
On Thursday 01 April 2010 15.01.12 Stephen Powell wrote: On Thu, 1 Apr 2010 03:34:18 -0400 (EDT), Andrei Popescu wrote: On Thu,01.Apr.10, 07:47:49, martin wrote: This last days my keyboard has stop working. If I just let the computer start as normal, nothing works. The keyboard in question is a logitech dinovo edge with bluetooth connection, using the included receiver. I have observe the following: * When trying to type on the keyboard, a red bluetooth icon appears on the keyboard * In grub the keyboard works as normal * If continuously pressing enter in grub to until the network has been setup, the keyboard will work for a while. If leaving the computer and coming back later, the may or may not work keyboard. * There is a built in mouse that is affected as well. I'm currently running up-to-date testing. keyboard is fully charge. Any ideas what can be wrong is appreciated :) It sounds to me like some power management feature... That would be my guess too. You might want to put your monitor to sleep to save energy, but you definitely don't want to put your keyboard to sleep to save energy. And if the mouse is built-in to the keyboard, it's even worse. There's no way to wake it up again, unless you can login remotely via ssh, or something like that. I currently have an usb cable mouse connected to the computer and that one always works. it's only the keyboard that is failing. Did this behavior begin with a kernel upgrade? That would be my first guess. Try booting the old kernel and see if the problem persists. I try booting 2.6.26 five times and there work keyboard without problem. In 2.6.32-trunk it only works if I tap enter key some times around Start INIT 2.85 (or at least until the computer has been left alone for an hour or so). I did a module compare, in 2.6.32 there are some extra modules that can be releated: bluetooth, btusb and hid_logitech. When was the last kernel upgrade? (the system is currently up-to-date) Martin -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201004020901.30957.martin.juh...@home.se
Re: Bluetooth keyboard trouble
On Fri, 2 Apr 2010 03:01:30 -0400 (EDT), martin wrote: I try booting 2.6.26 five times and there work keyboard without problem. In 2.6.32-trunk it only works if I tap enter key some times around Start INIT 2.85 (or at least until the computer has been left alone for an hour or so). I did a module compare, in 2.6.32 there are some extra modules that can be releated: bluetooth, btusb and hid_logitech. When was the last kernel upgrade? (the system is currently up-to-date) I'm not sure of the exact date, but the previous kernel was 2.6.32-trunk and you were having problems with it too. But if 2.6.26 works fine, then the problem is almost certainly a kernel problem. I'd search the bug reports for linux-2.6, and if you can't find one that seems to describe your problem, I recommend that you report a bug against the kernel. -- .''`. Stephen Powellzlinux...@wowway.com : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/896492803.717091270214027363.javamail.r...@md01.wow.synacor.com
Re: Bluetooth keyboard trouble
On Thu,01.Apr.10, 07:47:49, martin wrote: Hi, This last days my keyboard has stop working. If I just let the computer start as normal, nothing works. The keyboard in question is a logitech dinovo edge with bluetooth connection, using the included receiver. I have observe the following: * When trying to type on the keyboard, a red bluetooth icon appears on the keyboard * In grub the keyboard works as normal * If continuously pressing enter in grub to until the network has been setup, the keyboard will work for a while. If leaving the computer and coming back later, the may or may not work keyboard. * There is a built in mouse that is affected as well. I'm currently running up-to-date testing. keyboard is fully charge. Any ideas what can be wrong is appreciated :) It sounds to me like some power management feature... Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: Bluetooth keyboard trouble
On Thu, 1 Apr 2010 03:34:18 -0400 (EDT), Andrei Popescu wrote: On Thu,01.Apr.10, 07:47:49, martin wrote: This last days my keyboard has stop working. If I just let the computer start as normal, nothing works. The keyboard in question is a logitech dinovo edge with bluetooth connection, using the included receiver. I have observe the following: * When trying to type on the keyboard, a red bluetooth icon appears on the keyboard * In grub the keyboard works as normal * If continuously pressing enter in grub to until the network has been setup, the keyboard will work for a while. If leaving the computer and coming back later, the may or may not work keyboard. * There is a built in mouse that is affected as well. I'm currently running up-to-date testing. keyboard is fully charge. Any ideas what can be wrong is appreciated :) It sounds to me like some power management feature... That would be my guess too. You might want to put your monitor to sleep to save energy, but you definitely don't want to put your keyboard to sleep to save energy. And if the mouse is built-in to the keyboard, it's even worse. There's no way to wake it up again, unless you can login remotely via ssh, or something like that. Did this behavior begin with a kernel upgrade? That would be my first guess. Try booting the old kernel and see if the problem persists. -- .''`. Stephen Powellzlinux...@wowway.com : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1956360032.514271270126872339.javamail.r...@md01.wow.synacor.com
Bluetooth keyboard trouble
Hi, This last days my keyboard has stop working. If I just let the computer start as normal, nothing works. The keyboard in question is a logitech dinovo edge with bluetooth connection, using the included receiver. I have observe the following: * When trying to type on the keyboard, a red bluetooth icon appears on the keyboard * In grub the keyboard works as normal * If continuously pressing enter in grub to until the network has been setup, the keyboard will work for a while. If leaving the computer and coming back later, the may or may not work keyboard. * There is a built in mouse that is affected as well. I'm currently running up-to-date testing. keyboard is fully charge. Any ideas what can be wrong is appreciated :) Martin -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201004010747.50001.martin.juh...@home.se
bluetooth keyboard
Merhaba, Microsoftun bluetooth klavye ve mousunu satin aldim gecen gun. Su anda da gayet iyi kullanabiliyorum. Problem her bilgisayari yeniden baslattigimda root olup bluetooth la baglamak zorunda kaliyorum. hidd --connect 00:50... komutuyla. Bunu otomatik yapilabilcek bir yol varmi. internette Peter Klausler in yazdigi yaziyi buldum. Bi program yazmis bununla ilgili olarak onuda indirdim. make install yaptigimda rc-update komutunu bulamadigini soyledi. debian kullaniyorum bende komut farkliligi diye tahmin ettim ve make file icinden rc-update i update-rc.d diye degistirdim once calisir gibi gozuktu sonra baska bir hata verdi update-rc.d:/etc/init.d/add: file does not exist bununla ilgili bir bilgisi olan yardim edebilirmi cok tesekkurler. Bu arada Peter Klausler e de mail atmayi denedim ama yazili mail adresi calismiyor.
Re: bluetooth keyboard
Merhaba, Şunu deneyin bir de.. /etc/init.d/ dizini altında herhangi bir isimle bir dosya oluşturun ve içine şu satırları yazın: #! /bin/bash hidd --connect 00:50... Ve sonrasında kaydedin, chmod a+x dosyaadi ile çalışma hakkı verin. Sonrasında rcconf kurulu değilse kurun ve içerisinden yeni oluşturduğunuz dosyayı seçin. Hepsi bu.. Sisteminizi tekrar başlattığınızda sorunsuz çalışması lazım. Kolay gelsin.. kerem yazici yazmış: Merhaba, Microsoftun bluetooth klavye ve mousunu satin aldim gecen gun. Su anda da gayet iyi kullanabiliyorum. Problem her bilgisayari yeniden baslattigimda root olup bluetooth la baglamak zorunda kaliyorum. hidd --connect 00:50... komutuyla. Bunu otomatik yapilabilcek bir yol varmi. internette Peter Klausler in yazdigi yaziyi buldum. Bi program yazmis bununla ilgili olarak onuda indirdim. make install yaptigimda rc-update komutunu bulamadigini soyledi. debian kullaniyorum bende komut farkliligi diye tahmin ettim ve make file icinden rc-update i update-rc.d diye degistirdim once calisir gibi gozuktu sonra baska bir hata verdi update-rc.d:/etc/init.d/add: file does not exist bununla ilgili bir bilgisi olan yardim edebilirmi cok tesekkurler. Bu arada Peter Klausler e de mail atmayi denedim ama yazili mail adresi calismiyor. begin:vcard fn:Alper KANAT n:KANAT;Alper adr;quoted-printable:;;;Istanbul;;;T=C3=BCrkiye email;internet:[EMAIL PROTECTED] x-mozilla-html:FALSE url:http://raptiye.org version:2.1 end:vcard
Re: bluetooth keyboard
Merhabalar, update-rc.d komutunu listede daha öncede duydum ancak bir türlü kullanamadım. Muhtemelen böyle bir yol kullanmak daha düzgün olacaktır. Ancak daha az düzgün bir yol da kafi derseniz, şöyle bir yöntem olabilir: Sistem açılışında /etc/rcS.d/ dizinindeki dosyaların hepsi alfabetik sıra ile çalıştırılır. Bu işi yapan betik ise /etc/init.d/rcS dir. /etc/rcS.d/ klasöründeki dosyalar SNNisim (NN - iki haneli bir numara) şeklinde isimlendirilir. Benim size az düzgün bir yol olarak tavsiyem (ben de yaptım bunu gerektiğinde), /etc/rcS.d/ dizinine S99herhangibiryazi gibi bir isimle bir dosya yaratmanız ve dosyanın içine komutunuzu yazmanız (99 sayısını tavsiye ederim, çünkü /etc/rcS/ dizinindeki rakamlardan küçük rakamları kullanırsanız bluetooth sisteminin hazır olmamış bir anda komutunuzu çalıştırmaya çalışmış olabilirsiniz). Burada unutmamanız gereken bir nokta, kabuk betiği (shell script) yazdığımız için dosyanın en başına aşağıdaki satırın tamamını koymaktır. #! /bin/sh bu satır sh kabuğunu kullandığımızı belirtir. Bundan sonra komut satırından verdiğimiz herhangi bir komutu yazabiliriz. Mesela sizin komutunuz hidd --connect 00:50... bu komut açılışta diğer komutlar gibi çalışacaktır, işiniz de görülecektir. Tam hatırmadığım bir nokta da şu, sanırım yarattığımız bu dosyanın çalıştırılabilir durumda olması gerekiyor. Bunu yapmak için de chmod a+x S99herhangibiryazi komutunu kullanabiliriz. Kolay gelsin. Can Kavaklıoğlu Merhaba, Microsoftun bluetooth klavye ve mousunu satin aldim gecen gun. Su anda da gayet iyi kullanabiliyorum. Problem her bilgisayari yeniden baslattigimda root olup bluetooth la baglamak zorunda kaliyorum. hidd --connect 00:50... komutuyla. Bunu otomatik yapilabilcek bir yol varmi. internette Peter Klausler in yazdigi yaziyi buldum. Bi program yazmis bununla ilgili olarak onuda indirdim. make install yaptigimda rc-update komutunu bulamadigini soyledi. debian kullaniyorum bende komut farkliligi diye tahmin ettim ve make file icinden rc-update i update-rc.d diye degistirdim once calisir gibi gozuktu sonra baska bir hata verdi update-rc.d:/etc/init.d/add: file does not exist bununla ilgili bir bilgisi olan yardim edebilirmi cok tesekkurler. Bu arada Peter Klausler e de mail atmayi denedim ama yazili mail adresi calismiyor.
