Re: bluetooth mouse and keyboard stop working after some time
Thanks for the suggestions. After some more experiments I think that it's not a timeout/power problem, but it's probably a bug related to suspend/resume.
Re: bluetooth mouse and keyboard stop working after some time
Hi Federico, Quoting Federico Beffa (2019-11-18 20:54:37) > I recently purchased bluetooth mouse and keyboard to use with a Debian > 9 machine. I could pair the devices without problems and they do work > for some time. However, after some time they stop working. I suspect > that some timeout triggers. (After a reboot they start working again > for some time.) > > I'm using kernel linux-image-4.19.0-0.bpo.6-amd6. > > Below is an excerpt from /var/log/syslog showing that the Bluetooth > module is shutting down. > > Any suggestions? Try disable power management for the bluetooth device driver. Easiest to play with that is probably to install and use powertop, which hints at what it changes so that (if succesful) you can transfer those changes to e.g. lines in a new file /etc/sysctl.d/local-powersave.conf NB! You may need to disable power management not only from device driver but also drivers of underlying bus. You can get a topological view of the USB bus with this command: lsusb --tree ...and a topological view of your whole machine with this: lshw | less - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
bluetooth mouse and keyboard stop working after some time
Hi, I recently purchased bluetooth mouse and keyboard to use with a Debian 9 machine. I could pair the devices without problems and they do work for some time. However, after some time they stop working. I suspect that some timeout triggers. (After a reboot they start working again for some time.) I'm using kernel linux-image-4.19.0-0.bpo.6-amd6. Below is an excerpt from /var/log/syslog showing that the Bluetooth module is shutting down. Any suggestions? Nov 18 15:03:23 lupo NetworkManager[717]: [1574085803.9156] device (wlp2s0): set-hw-addr: set MAC address to EA:9D:A4:E8:88:99 (scanning) Nov 18 15:03:23 lupo kernel: [ 6888.646262] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready Nov 18 15:03:23 lupo NetworkManager[717]: [1574085803.9227] device (wlp2s0): supplicant interface state: inactive -> disabled Nov 18 15:03:23 lupo NetworkManager[717]: [1574085803.9463] device (wlp2s0): supplicant interface state: disabled -> inactive Nov 18 15:03:23 lupo wpa_supplicant[1140]: wlp2s0: Reject scan trigger since one is already pending Nov 18 15:05:44 lupo kernel: [ 7029.363271] usb 1-4: USB disconnect, device number 3 Nov 18 15:05:44 lupo systemd[1]: Starting Load/Save RF Kill Switch Status... Nov 18 15:05:44 lupo systemd[1]: bluetooth.target: Unit not needed anymore. Stopping. Nov 18 15:05:44 lupo systemd[1]: Stopped target Bluetooth. Nov 18 15:05:44 lupo systemd[1]: Started Load/Save RF Kill Switch Status. Nov 18 15:05:44 lupo /usr/lib/gdm3/gdm-x-session[1292]: (II) config/udev: removing device MX Master 3 Keyboard Nov 18 15:05:44 lupo /usr/lib/gdm3/gdm-x-session[1292]: (**) Option "fd" "50" Nov 18 15:05:44 lupo /usr/lib/gdm3/gdm-x-session[1292]: (II) UnloadModule: "libinput" Nov 18 15:05:44 lupo /usr/lib/gdm3/gdm-x-session[1292]: (II) systemd-logind: releasing fd for 13:85 Nov 18 15:05:44 lupo /usr/lib/gdm3/gdm-x-session[1292]: (II) config/udev: removing device MX Master 3 Mouse Nov 18 15:05:44 lupo /usr/lib/gdm3/gdm-x-session[1292]: (**) Option "fd" "51" Nov 18 15:05:44 lupo /usr/lib/gdm3/gdm-x-session[1292]: (II) UnloadModule: "libinput" Nov 18 15:05:44 lupo /usr/lib/gdm3/gdm-x-session[1292]: (II) systemd-logind: releasing fd for 13:86 Nov 18 15:05:44 lupo /usr/lib/gdm3/gdm-x-session[1292]: (II) config/udev: removing device MX Keys Keyboard Nov 18 15:05:44 lupo /usr/lib/gdm3/gdm-x-session[1292]: (**) Option "fd" "54" Thanks, Fede
Re: Upgrade from Jessie to Stretch: Bluetooth mouse is not working.
On Thu, 31 May 2018 11:04:10 -0500 "Martin McCormick" wrote: > You might search web archives and internet discussion > groups to see if there is a replacement driver for the mouse > which is a real shame since it used to work but that particular > module doesn't work which is valuable information but not, of > course, what you wanted to know. Any hints where to start and what to look for? I bought this mouse because it was really silent and cheap (APOINT M302) and it was working with Debian Jessie. https://www.aliexpress.com/item/New-Bluetooth-Ultra-thin-Rechargeable-Wireless-Mouse-Silent-Button-2015-computer-mouse-for-laptop-gift-mice/32368987723.html?spm=a2g0s.9042311.0.0.27424c4dCuQb1a Officially Linux support was not mentioned, so it might be difficult to find a drivers for it. I wonder what was changed between Debian releases that this mouse is no longer working correctly? For me looks like a regression which should be fixed. Should I reported this as a bug? If "yes" then which module/driver should I specify as a victim? > Can you get any other bluetooth device to pair and > actually work with the dongle such as a headset or keyboard? Yes, I was able to successfully connect some remote controller/gamepad which also has mouse option: https://www.amazon.de/ddLUCK-Universal-Wireless-Controller-Bluetooth-Remote/dp/B01ICYZ7ZI/ref=sr_1_12/262-6869085-0156757?ie=UTF8&qid=1527838130&sr=8-12&keywords=mocute Maybe I should also try with another BT mouse to see if it has the same issue or not. > There are a lot of moving parts here such as the usb > driver for the dongle and then there is the communication between > the bluetooth device and the dongle. > > dmesg and syslog are very good tools in cases like this > but the messages you will read aren't always the answers to the > question of why this or that is happening. They certainly do > help you ask new questions and sometimes rule out rabbit holes > you don't need to waste your time going down which is a blessing > as the world of making the technology work for you is a regular > warren of rabbit holes and anything that narrows down the > solution is a force multiplier. > > One guess is that the driver for the bluetooth dongle is > causing the grief because it sees events that it doesn't > understand from the mouse. It should understand every mouse move > and button press so they can be passed on to the appropriate > function calls related to mouse activity. The OS has mouse > function calls and the driver translates mouse movement data in > to steps that are either along the X or Y axese. It doesn't have > to do anything but feed those steps to the OS by making the > appropriate function calls for movement and clicks. It > apparently can't do that so you need a different driver. > > It might also be that another bluetooth mouse speaks a > different language and the driver understands it and works > properly so I hope this gives you more food for thought. > > I don't really know anything specific to your problem so > I am speaking in generalities as I have seen a number of usb > devices such as a usb apple modem that shows activity in syslog > when you plug it in to a usb port but due to a lack of a driver, > it does absolutely nothing under Linux but get slightly warm to > the touch. Plug it in to a Mac and you're in to the dialup > business. > > Martin McCormick > Thanks for elaborate explanation. Kind regards, Piotr
Re: Upgrade from Jessie to Stretch: Bluetooth mouse is not working.
Piotr wrote: > See the new log file. But still it says that destination is null. > > What next to check? your log is not complete it was seeing before dict entry( string "ActiveState" variant string "inactive" ) dict entry( string "SubState" variant string "dead" )
Re: Upgrade from Jessie to Stretch: Bluetooth mouse is not working.
Piotr writes: > dmesg gave me this (relevant lines when BT mouse was connected) > > [ 4218.671838] hid-generic 0005:0A5C:0001.0004: unknown main item tag 0x0 > [ 4218.676386] input: Bluetooth 3.0 Mouse as > /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/bluetooth/hci0/hci0:3/0005:0A5C:0001.0004/input/input21 > [ 4218.679232] hid-generic 0005:0A5C:0001.0004: input,hidraw1: BLUETOOTH > HID v1.29 Mouse [Bluetooth 3.0 Mouse] on 00:15:83:0c:bf:eb > [ 4245.882600] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 > [ 4245.885751] input: Bluetooth 3.0 Mouse as > /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/bluetooth/hci0/hci0:4/0005:0A5C:0001.0005/input/input22 > [ 4245.887779] hid-generic 0005:0A5C:0001.0005: input,hidraw1: BLUETOOTH > HID v1.29 Mouse [Bluetooth 3.0 Mouse] on 00:15:83:0c:bf:eb > [ 4276.111082] hid-generic 0005:0A5C:0001.0006: unknown main item tag 0x0 > [ 4276.115032] input: Bluetooth 3.0 Mouse as > /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/bluetooth/hci0/hci0:5/0005:0A5C:0001.0006/input/input23 > [ 4276.118450] hid-generic 0005:0A5C:0001.0006: input,hidraw1: > BLUETOOTH HID v1.29 Mouse [Bluetooth 3.0 Mouse] on 00:15:83:0c:bf:eb > > But I do not know what should I do with this. It is basically an accident report stating that this mouse won't work with that module. You might search web archives and internet discussion groups to see if there is a replacement driver for the mouse which is a real shame since it used to work but that particular module doesn't work which is valuable information but not, of course, what you wanted to know. If you do find out that another kernel module or driver does exist, that is the time to use /etc/modules to load it first since the automatic detection is getting your the wrong one. I used to have an 8-port serial converter box with 8 RS-232 ports and a usb connector going to the computer. It needed a proprietary driver that the company did provide to Linux users for free but no kernel modules loaded at all when you connected the device without the driver. It worked fine until we had a gigantic electrical storm one day and all 8 ports went deaf and mute forever even though it appeared as though they were okay and just waiting to be connected to something. The replacement 8-port box loads kernel modules and works without any proprietary drivers. Can you get any other bluetooth device to pair and actually work with the dongle such as a headset or keyboard? There are a lot of moving parts here such as the usb driver for the dongle and then there is the communication between the bluetooth device and the dongle. dmesg and syslog are very good tools in cases like this but the messages you will read aren't always the answers to the question of why this or that is happening. They certainly do help you ask new questions and sometimes rule out rabbit holes you don't need to waste your time going down which is a blessing as the world of making the technology work for you is a regular warren of rabbit holes and anything that narrows down the solution is a force multiplier. One guess is that the driver for the bluetooth dongle is causing the grief because it sees events that it doesn't understand from the mouse. It should understand every mouse move and button press so they can be passed on to the appropriate function calls related to mouse activity. The OS has mouse function calls and the driver translates mouse movement data in to steps that are either along the X or Y axese. It doesn't have to do anything but feed those steps to the OS by making the appropriate function calls for movement and clicks. It apparently can't do that so you need a different driver. It might also be that another bluetooth mouse speaks a different language and the driver understands it and works properly so I hope this gives you more food for thought. I don't really know anything specific to your problem so I am speaking in generalities as I have seen a number of usb devices such as a usb apple modem that shows activity in syslog when you plug it in to a usb port but due to a lack of a driver, it does absolutely nothing under Linux but get slightly warm to the touch. Plug it in to a Mac and you're in to the dialup business. Martin McCormick
Re: Upgrade from Jessie to Stretch: Bluetooth mouse is not working.
On Thu, 31 May 2018 14:58:59 +0200 deloptes wrote: > you sure about init? ps -A | head -3 This is what I got. user@localhost:~$ ps -A | head -3 PID TTY TIME CMD 1 ?00:00:01 init 2 ?00:00:00 kthreadd > so what is the dbus-monitor output now See the new log file. But still it says that destination is null. What next to check? Regards, Piotr signal time=1527772847.995587 sender=:1.3 -> destination=(null destination) serial=264 path=/org/bluez/hci0/dev_DC_2C_26_F8_43_A7; interface=org.freedesktop.DBus.Properties; member=PropertiesChanged string "org.bluez.Device1" array [ dict entry( string "Class" variant uint32 1408 ) dict entry( string "Icon" variant string "input-mouse" ) dict entry( string "Connected" variant boolean true ) ] array [ ] method call time=1527772848.000769 sender=:1.43 -> destination=org.bluez serial=254 path=/org/bluez/hci0/dev_DC_2C_26_F8_43_A7; interface=org.freedesktop.DBus.Introspectable; member=Introspect method return time=1527772848.001241 sender=:1.3 -> destination=:1.43 serial=265 reply_serial=254 string "http://www.freedesktop.org/standards/dbus/1.0/introspect.dtd";> " method call time=1527772848.007401 sender=:1.43 -> destination=org.bluez serial=255 path=/org/bluez/hci0/dev_DC_2C_26_F8_43_A7; interface=org.freedesktop.DBus.Properties; member=GetAll string "org.bluez.Device1" method return time=1527772848.007917 sender=:1.3 -> destination=:1.43 serial=266 reply_serial=255 array [ dict entry( string "Address" variant string "DC:2C:26:F8:43:A7" ) dict entry( string "Name" variant string "Bluetooth 3.0 Mouse" ) dict entry( string "Alias" variant string "Bluetooth 3.0 Mouse" ) dict entry( string "Class" variant uint32 1408 ) dict entry( string "Icon" variant string "input-mouse" ) dict entry( string "Paired" variant boolean true ) dict entry( string "Trusted" variant boolean false ) dict entry( string "Blocked" variant boolean false ) dict entry( string "LegacyPairing" variant boolean true ) dict entry( string "Connected" variant boolean true ) dict entry( string "UUIDs" variant array [ string "1000--1000-8000-00805f9b34fb" string "1124--1000-8000-00805f9b34fb" string "1200--1000-8000-00805f9b34fb" ] ) dict entry( string "Modalias" variant string "usb:v0A5Cp0001d0129" ) dict entry( string "Adapter" variant object path "/org/bluez/hci0" ) dict entry( string "ServicesResolved" variant boolean false ) ] method call time=1527772848.012017 sender=:1.43 -> destination=org.freedesktop.DBus serial=256 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',sender='org.freedesktop.DBus',path='/org/freedesktop/DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0='org.bluez'" method return time=1527772848.012121 sender=org.freedesktop.DBus -> destination=:1.43 serial=125 reply_serial=256 method call time=1527772848.013964 sender=:1.43 -> destination=org.freedesktop.DBus serial=257 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=GetNameOwner string "org.bluez" method return time=1527772848.014089 sender=org.freedesktop.DBus -> destination=:1.43 serial=126 reply_serial=257 string ":1.3" method call time=1527772848.015379 sender=:1.43 -> destination=org.freedesktop.DBus serial=258 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',sender='org.bluez',path='/org/bluez/hci0/dev_DC_2C_26_F8_43_A7',interface='org.freedesktop.DBus.Properties',member='PropertiesChanged'" method return time=1527772848.015539 sender=org.freedesktop.DBus -> destination=:1.43 serial=127 reply_serial=258 method call time=1527772848.017622 sender=:1.43 -> destination=org.bluez serial=259 path=/; interface=org.freedesktop.DBus.Introspectable; member=Introspect method return time=1527772848.018027 sender=:1.3 -> destination=:1.43 serial=267 reply_serial=259 string "http://www.freedesktop.org/standards/dbus/1.0/introspect.dtd";> " method call time=1527772848.019801 sender=:1.43 -> destination=org.bluez serial=260 path=/org/bluez/hci0; interface=org.freedesktop.DBus.Introspectable; member=Introspect method return time=152
Re: Upgrade from Jessie to Stretch: Bluetooth mouse is not working.
Piotr wrote: >> ps -A | head -3 >> PID TTY TIME CMD >> 1 ? 00:00:33 init >> 2 ? 00:00:01 kthreadd > > OK, I booted as you suggested, but the mouse problem remains. Any other > suggestions? you sure about init? ps -A | head -3 so what is the dbus-monitor output now regards
Re: Upgrade from Jessie to Stretch: Bluetooth mouse is not working.
On Thu, May 31, 2018 at 02:00:10PM +0200, Piotr wrote: > Was Jessie already using systemd by default? Yes. Both on new installs and on upgrades from wheezy.
Re: Upgrade from Jessie to Stretch: Bluetooth mouse is not working.
On Thu, 31 May 2018 12:10:13 +0200 deloptes wrote: > You see all works fine until systemd gets in the game. > As I refused to use systemd I can't help much, but this needs to be > investigated Was Jessie already using systemd by default? If "yes" then maybe this is not the source of the problem as the mouse was working correctly on Jessie? I connected another BT controller (chinese MOCUTE BT controller, which can be used as keypad or mouse) and it was working correctly. > Here you see sender=:1.0 -> destination=(null destination) > > signal time=1527752498.410215 sender=:1.0 -> destination=(null destination) > serial=4147 path=/org/freedesktop/systemd1; > interface=org.freedesktop.systemd1.Manager; member=UnitRemoved > > Can you try booting without systemd ? You need sysvinit and add > init=/lib/sysvinit/init to your kernal command line. > When system is up check > > ps -A | head -3 > PID TTY TIME CMD > 1 ?00:00:33 init > 2 ?00:00:01 kthreadd OK, I booted as you suggested, but the mouse problem remains. Any other suggestions? Regards, Piotr
Re: Upgrade from Jessie to Stretch: Bluetooth mouse is not working.
Piotr wrote: >> dbus-monitor --system >> >> and switch mouse on/off to reconnect. Tell us what you see. > > I see the change was logged when I connected BT mouse (see > dbus-monitor.log) > > >> If mouse is >> correctly discovered and selected by BT you have to look at higher level >> - the X system. >> First check if you have events captured by X perhaps with >> >> xev > > xev gives me nothing when I use the BT mouse. > > What next? Excellent work Piotr. You see all works fine until systemd gets in the game. As I refused to use systemd I can't help much, but this needs to be investigated > path=/org/freedesktop/systemd1/unit/sys_2ddevices_2dpci_3a00_2d_3a00_3a1d_2e0_2dusb2_2d2_5cx2d1_2d2_5cx2d1_3a1_2e0_2dbluetooth_2dhci0_2dhci0_3a9_2edevice; > interface=org.freedesktop.DBus.Properties; member=PropertiesChanged string > "org.freedesktop.systemd1.Unit" array [ > dict entry( > string "ActiveState" > variant string "inactive" > ) > dict entry( > string "SubState" > variant string "dead" > ) Here you see sender=:1.0 -> destination=(null destination) signal time=1527752498.410215 sender=:1.0 -> destination=(null destination) serial=4147 path=/org/freedesktop/systemd1; interface=org.freedesktop.systemd1.Manager; member=UnitRemoved Can you try booting without systemd ? You need sysvinit and add init=/lib/sysvinit/init to your kernal command line. When system is up check ps -A | head -3 PID TTY TIME CMD 1 ?00:00:33 init 2 ?00:00:01 kthreadd Otherwise you should look for why systemd is not doing this right. regards
Re: Upgrade from Jessie to Stretch: Bluetooth mouse is not working.
On Tue, 29 May 2018 22:55:51 +0200 deloptes wrote: > dbus-monitor --system > > and switch mouse on/off to reconnect. Tell us what you see. I see the change was logged when I connected BT mouse (see dbus-monitor.log) > If mouse is > correctly discovered and selected by BT you have to look at higher level - > the X system. > First check if you have events captured by X perhaps with > > xev xev gives me nothing when I use the BT mouse. What next? Regards, Piotr signal time=1527752478.126670 sender=:1.3 -> destination=(null destination) serial=211 path=/org/bluez/hci0/dev_DC_2C_26_F8_43_A7; interface=org.freedesktop.DBus.Properties; member=PropertiesChanged string "org.bluez.Device1" array [ dict entry( string "Connected" variant boolean true ) ] array [ ] signal time=1527752478.129526 sender=:1.0 -> destination=(null destination) serial=4140 path=/org/freedesktop/systemd1; interface=org.freedesktop.systemd1.Manager; member=UnitNew string "sys-devices-pci:00-:00:1d.0-usb2-2\x2d1-2\x2d1:1.0-bluetooth-hci0-hci0:9.device" object path "/org/freedesktop/systemd1/unit/sys_2ddevices_2dpci_3a00_2d_3a00_3a1d_2e0_2dusb2_2d2_5cx2d1_2d2_5cx2d1_3a1_2e0_2dbluetooth_2dhci0_2dhci0_3a9_2edevice" signal time=1527752478.129628 sender=:1.0 -> destination=(null destination) serial=4141 path=/org/freedesktop/systemd1; interface=org.freedesktop.systemd1.Manager; member=UnitNew string "sys-subsystem-bluetooth-devices-hci0:9.device" object path "/org/freedesktop/systemd1/unit/sys_2dsubsystem_2dbluetooth_2ddevices_2dhci0_3a9_2edevice" method call time=1527752478.133231 sender=:1.51 -> destination=org.bluez serial=337 path=/org/bluez/hci0/dev_DC_2C_26_F8_43_A7; interface=org.freedesktop.DBus.Introspectable; member=Introspect method return time=1527752478.134333 sender=:1.3 -> destination=:1.51 serial=212 reply_serial=337 string "http://www.freedesktop.org/standards/dbus/1.0/introspect.dtd";> " method call time=1527752478.138316 sender=:1.51 -> destination=org.bluez serial=338 path=/org/bluez/hci0/dev_DC_2C_26_F8_43_A7; interface=org.freedesktop.DBus.Properties; member=GetAll string "org.bluez.Device1" method return time=1527752478.139445 sender=:1.3 -> destination=:1.51 serial=213 reply_serial=338 array [ dict entry( string "Address" variant string "DC:2C:26:F8:43:A7" ) dict entry( string "Name" variant string "Bluetooth 3.0 Mouse" ) dict entry( string "Alias" variant string "Bluetooth 3.0 Mouse" ) dict entry( string "Class" variant uint32 1408 ) dict entry( string "Icon" variant string "input-mouse" ) dict entry( string "Paired" variant boolean true ) dict entry( string "Trusted" variant boolean true ) dict entry( string "Blocked" variant boolean false ) dict entry( string "LegacyPairing" variant boolean false ) dict entry( string "Connected" variant boolean true ) dict entry( string "UUIDs" variant array [ string "1000--1000-8000-00805f9b34fb" string "1124--1000-8000-00805f9b34fb" string "1200--1000-8000-00805f9b34fb" ] ) dict entry( string "Modalias" variant string "usb:v0A5Cp0001d0129" ) dict entry( string "Adapter" variant object path "/org/bluez/hci0" ) dict entry( string "ServicesResolved" variant boolean false ) ] method call time=1527752478.141842 sender=:1.51 -> destination=org.freedesktop.DBus serial=339 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',sender='org.freedesktop.DBus',path='/org/freedesktop/DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0='org.bluez'" method return time=1527752478.141939 sender=org.freedesktop.DBus -> destination=:1.51 serial=185 reply_serial=339 method call time=1527752478.143190 sender=:1.51 -> destination=org.freedesktop.DBus serial=340 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=GetNameOwner string "org.bluez" method return time=1527752478.143516 sender=org.freedesktop.DBus -> destination=:1.51 serial=186 reply_serial=340 string ":1.3" method call time=1527752478.144389 sender=:1.51 -> destination=org.freedesktop.DBus serial=341 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',sender='org.bluez',path='/org/bluez/hci0/dev_DC_2C_26_F8_43_A7',interface='org.freedeskt
Re: Upgrade from Jessie to Stretch: Bluetooth mouse is not working.
_kms_helper snd_pcm86016 3 snd_hda_intel,snd_hda_codec,snd_hda_core snd_timer 28672 1 snd_pcm snd57344 13 snd_hda_intel,snd_hwdep,snd_hda_codec,snd_timer,snd_hda_codec_generic,snd_hda_codec_realtek,snd_pcm soundcore 16384 1 snd i2c_algo_bit 16384 1 i915 shpchp 32768 0 ac 16384 0 video 36864 2 samsung_laptop,i915 acpi_cpufreq 20480 1 button 16384 1 i915 parport_pc 28672 0 sunrpc249856 1 ppdev 20480 0 lp 20480 0 parport40960 3 lp,parport_pc,ppdev ip_tables 20480 0 x_tables 20480 1 ip_tables autofs436864 2 ext4 499712 3 crc16 16384 2 bluetooth,ext4 jbd2 77824 1 ext4 crc32c_generic 16384 0 fscrypto 24576 1 ext4 ecb16384 0 lrw16384 0 ablk_helper16384 0 cryptd 20480 1 ablk_helper aes_i586 20480 5 mbcache16384 4 ext4 xts16384 3 gf128mul 20480 2 lrw,xts algif_skcipher 20480 0 af_alg 16384 1 algif_skcipher dm_crypt 24576 1 dm_mod 94208 12 dm_crypt sd_mod 40960 3 ata_generic16384 0 psmouse 118784 0 ata_piix 32768 2 i2c_i801 24576 0 i2c_smbus 16384 1 i2c_i801 libata192512 2 ata_piix,ata_generic scsi_mod 180224 3 sd_mod,libata,sg uhci_hcd 40960 0 ehci_pci 16384 0 ehci_hcd 65536 1 ehci_pci usbcore 184320 6 uvcvideo,usbhid,ehci_hcd,uhci_hcd,btusb,ehci_pci usb_common 16384 1 usbcore r8169 77824 0 mii16384 1 r8169 fan16384 0 thermal20480 0 > > Notice the psmouse module. You'll hopefully have something > comparable for the bluetooth mouse. It may not appear until you > try to pair your mouse with bluetooth. I redirected lsmod when there was no BT mouse connection to file 1 and when it was connected to file 2. The "diff 1 2" gave this: user@localhost:~$ diff 1 2 2c2 < hidp 24576 0 --- > hidp 24576 1 46c46 < bluetooth 434176 40 btrtl,hidp,btintel,bnep,btbcm,rfcomm,btusb --- > bluetooth 434176 44 btrtl,hidp,btintel,bnep,btbcm,rfcomm,btusb 57c57 < evdev 20480 22 --- > evdev 20480 23 > Finally, there is a file in /etc called modules. Any > module whose name appears on a line in that file will be loaded > on boot. In my system the file only contains comments. > I used to have trouble on this system with sound from > the built-in sound chip set on the mother board. It would > usually be a no-show as sound card 0 and a usb sound card would > intermittently show up as card 0. By using /etc/modules to load > the sound module for the built-in card, it is always card 0. Should I add some module in my case to this file? > Use that feature carefully since modules you don't > actually need just waste resources. > > That should get you started with an afternoon of > head-scratching/banging as these things can be frustrating so > patience is a virtue. Patience I have. What I do not is the knowledge where to look and which dots to connect. Thanks for helping. Regards, Piotr
Re: Upgrade from Jessie to Stretch: Bluetooth mouse is not working.
Piotr Martyniuk wrote: > I am using USB dongle for blue-tooth connections. I can pair the mouse and > connect to it. However moving a mouse and/or clicking has no effect > (cursor stays where it was, clicks are not recognized). No make model for mouse or BT device in your PC. I don't know if bluetooth in jessie was bluez4 or bluez5. It could be that you are missing privileges. It all goes via dbus now. Use dbus-monitor --system and switch mouse on/off to reconnect. Tell us what you see. If mouse is correctly discovered and selected by BT you have to look at higher level - the X system. First check if you have events captured by X perhaps with xev IMO it is somewhere inbetween those two actors. regards
Re: Upgrade from Jessie to Stretch: Bluetooth mouse is not working.
Piotr Martyniuk writes: > Dear all, > > Recently I upgraded from Jessie to Stretch in order to be able to install > new > package versions. > The upgrade seems to be successful (I did not have any errors in the > process), > but I noticed that the Blue tooth mouse is not working (it was working > fine > in > Jessie). > > I am using USB dongle for blue-tooth connections. I can pair the mouse and > connect to it. However moving a mouse and/or clicking has no effect > (cursor > stays where it was, clicks are not recognized). > > I would include more info (output from some commands, logs), however I am > not > sure what is relevant, so I would need some guidance in this. > > Kind regards, > Piotr You might get some information from dmesg. dmesg lists all the electronic devices your system knows about when it booted up such as sound cards, disk controllers and network interfaces. Your computer should make note of the bluetooth interface and might even throw an error message if it doesn't like something about it. The mouse should pair with the bluetooth system on your computer and since your installation is an upgrade, this may be an indication of trouble with the module associated with the mouse. You can also see which modules your system loaded on boot by using the command lsmod At least this is true in a number of Linux versions. You don't even have to be root. wb5agz martin tmp $lsmod Module Size Used by binfmt_misc20480 1 fuse 90112 1 ppdev 20480 0 dcdbas 16384 0 nouveau 1359872 1 pcspkr 16384 0 serio_raw 16384 0 evdev 20480 1 mxm_wmi16384 1 nouveau snd_usb_audio 131072 0 wmi16384 2 mxm_wmi,nouveau psmouse 118784 0 scsi_mod 180224 6 sd_mod,usb_storage,libata,uas,sr_mod,sg 3c59x 45056 0 mii16384 1 3c59x usbcore 184320 12 usbhid,snd_usb_audio,usb_storage,ehci_hcd,ohci_pci,uhci_hcd,ftdi_sio,usbserial,snd_usbmidi_lib,uas,ohci_hcd,ehci_pci i2c_piix4 20480 0 usb_common 16384 1 usbcore floppy 57344 0 Those were just some of the 81 modules that popped up on the old Dell Dimension I am using, here. Notice the psmouse module. You'll hopefully have something comparable for the bluetooth mouse. It may not appear until you try to pair your mouse with bluetooth. Finally, there is a file in /etc called modules. Any module whose name appears on a line in that file will be loaded on boot. I used to have trouble on this system with sound from the built-in sound chip set on the mother board. It would usually be a no-show as sound card 0 and a usb sound card would intermittently show up as card 0. By using /etc/modules to load the sound module for the built-in card, it is always card 0. Use that feature carefully since modules you don't actually need just waste resources. That should get you started with an afternoon of head-scratching/banging as these things can be frustrating so patience is a virtue. Martin McCormick WB5AGZ since October 1969 Alive since 1951.
Upgrade from Jessie to Stretch: Bluetooth mouse is not working.
Dear all, Recently I upgraded from Jessie to Stretch in order to be able to install new package versions. The upgrade seems to be successful (I did not have any errors in the process), but I noticed that the Blue tooth mouse is not working (it was working fine in Jessie). I am using USB dongle for blue-tooth connections. I can pair the mouse and connect to it. However moving a mouse and/or clicking has no effect (cursor stays where it was, clicks are not recognized). I would include more info (output from some commands, logs), however I am not sure what is relevant, so I would need some guidance in this. Kind regards, Piotr -- System Information: Debian Release: 9.4 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.9.0-6-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Re: Bluetooth mouse disconnect while laptop runs with cell
wg...@china.com wrote: > I think the reason is the function of bluetooth power save while the cell > is used. So I want to turn off the function of bluetooth power save, but I > can not find where to define it. Would you please tell me how to turn off > the function of bluetooth power save? I don't know exactly, but you might look at the bt kernel module - perhaps there is an option
Bluetooth mouse disconnect while laptop runs with cell
Hi, everyone! I use my laptop (Thinkpad X1 Carbon 5th) with a bluetooth mouse. The mouse work fine while the laptop runs with AC power supply. But The bluetooth mouse is a trouble while the laptop runs with the embed cell. The mouse will disconnect if it is not be used after several seconds. So I want use the mouse, it must reconnect to the laptop and spend several seconds. it is very inconvenient! I think the reason is the function of bluetooth power save while the cell is used. So I want to turn off the function of bluetooth power save, but I can not find where to define it. Would you please tell me how to turn off the function of bluetooth power save? My Debian version is the buster, and it is upgraded everyday. Best regards, Gulfstream
Re: Bluetooth mouse problems on Jessie
On 18 May 2015 at 20:05, iain wrote: > On 29/04/15 09:10, Johann Spies wrote: > > Since the weekend (and Jessie becoming Stable) I could not use my > > bluetooth mouse which I have been using for years. I get the message > > "successfully added but failed to connect". > > I can confirm that the rodent did not die. I have tried the bluetooth mouse with a Apple Macbook Pro and it works without a problem. The problem is thus a Debian Jessie one. Maybe I should do a bugreport. Regards Johann -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3)
Re: Bluetooth mouse problems on Jessie
On 29/04/15 09:10, Johann Spies wrote: > Since the weekend (and Jessie becoming Stable) I could not use my > bluetooth mouse which I have been using for years. I get the message > "successfully added but failed to connect". > > When I delete the device in the bluetooth setup and try to set it up > again, the device seems to be detected, then it disappears and reappears > about every second. > > This is happened on two different laptops so I do not think it is a > hardware problem. > > Anyone else having similar problems? Yup. Same problem here. I was using a Logitech Bluetooth mouse on my old Wheezy laptop, bought a new one which required Jessie to be installed, now I cannot get the mouse (or anything bluetooth) to pair. I'm thinking it may have something to do with DBus communications. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/mjd9m4$cib$1...@ger.gmane.org
Re: Bluetooth mouse problems on Jessie
On Wed, 29 Apr 2015 17:23:08 +0200 Johann Spies wrote: Hello Johann, >On 29 April 2015 at 11:40, Brad Rogers wrote: >> As Lisi says, you've not eliminated the mouse as the problem (in fact, >> you've probably done the opposite). >Correct! Thanks for opening my eyes for that possibility. You're welcome. >Yes, I have tested it with other batteries also. Do you have access to another mouse you could try? BTW; No need to Cc me, as I'm subbed to the list and will see your replies. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" Keep your drink just give em the money U & Ur Hand - P!nk pgpLFyjE6i3s8.pgp Description: OpenPGP digital signature
Re: Bluetooth mouse problems on Jessie
On Wednesday 29 April 2015 16:23:08 Johann Spies wrote: > On 29 April 2015 at 11:40, Brad Rogers wrote: > > On Wed, 29 Apr 2015 09:10:25 +0200 > > Johann Spies wrote: > > > > Hello Johann, > > > > >mouse which I have been using for years. I get the message > > >"successfully added but failed to connect". > > > > As Lisi says, you've not eliminated the mouse as the problem (in fact, > > you've probably done the opposite). > > Correct! Thanks for opening my eyes for that possibility. > > > Try the simple things first; Batteries failing, perhaps? > > Yes, I have tested it with other batteries also. Can you use the mouse with another operating system or distro? Can it be made to work anywhere? Presumably bluetooth mice die sometimes as do other rodents. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201504291718.18747.lisi.re...@gmail.com
Re: Bluetooth mouse problems on Jessie
On 29 April 2015 at 11:40, Brad Rogers wrote: > On Wed, 29 Apr 2015 09:10:25 +0200 > Johann Spies wrote: > > Hello Johann, > > >mouse which I have been using for years. I get the message > >"successfully added but failed to connect". > > As Lisi says, you've not eliminated the mouse as the problem (in fact, > you've probably done the opposite). > Correct! Thanks for opening my eyes for that possibility. > > Try the simple things first; Batteries failing, perhaps? > Yes, I have tested it with other batteries also. Regards Johann -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3)
Re: Bluetooth mouse problems on Jessie
On Wed, 29 Apr 2015 09:10:25 +0200 Johann Spies wrote: Hello Johann, >mouse which I have been using for years. I get the message >"successfully added but failed to connect". As Lisi says, you've not eliminated the mouse as the problem (in fact, you've probably done the opposite). Try the simple things first; Batteries failing, perhaps? -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" Bet you thought you knew what I was about Problem - Sex Pistols pgpV3voA6aKxg.pgp Description: OpenPGP digital signature
Re: Bluetooth mouse problems on Jessie
On Wednesday 29 April 2015 08:10:25 Johann Spies wrote: > This is happened on two different laptops so I do not think it is a > hardware problem. The mouse is hardware. This test does not exclude the possibility that it is the mouse that is faulty. It merely suggests (not proves) that the laptops are not. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201504291020.46976.lisi.re...@gmail.com
Bluetooth mouse problems on Jessie
Since the weekend (and Jessie becoming Stable) I could not use my bluetooth mouse which I have been using for years. I get the message "successfully added but failed to connect". When I delete the device in the bluetooth setup and try to set it up again, the device seems to be detected, then it disappears and reappears about every second. This is happened on two different laptops so I do not think it is a hardware problem. Anyone else having similar problems? Regards Johann -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3)
[wheezy] Pairing/connecting a bluetooth mouse
Hello, I am experiencing trouble getting my bluetooth mouse to pair with my machine in wheezy. I have tried the following commands hidd --connect Also tried bluez-test-input connect dmesg shows a succesful pair and connect [90666.443913] hid-generic 0005:03F0:024C.0020: unknown main item tag 0x0 [90666.444019] input: Broadcom Bluetooth Wireless Mouse as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:38/0005:03F0:024C.0020/input/input41 [90666.444556] hid-generic 0005:03F0:024C.0020: input,hidraw3: BLUETOOTH HID v1.03 Mouse [Broadcom Bluetooth Wireless Mouse] on c4:d9:87:82:dd:58 However the mouse does not work. I have paired a bluetooth keyboard, which works. I am using a backported kernel 3.14-0.bpo.2-686-pae #1 SMP Debian 3.14.15-2~bpo70+1. Using the backported kernel to fix a audio stutter issue that happens on the Intel NUC hardware I am using. Any ideas on what I should be trying to figure this out ? Thanks, Prashant -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87fb5fac4e9282e07c490dcb563f7...@mykolab.com
Re: Bluetooth mouse? (Solved)
On Mon, 29 Sep 2014 10:08:02 +0200 Johann Spies wrote: > Apologies for the noise. Playing again with blueman-manager I found > an option 'create paring' and after that I could connect to the mouse > and it is working now. > > Regards > Johann Johann, Great to hear you got it fixed. What's the benefit of a bluetooth mouse over an RF mouse like the Logitech 310? Thanks, SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140929111847.76085...@mydesq2.domain.cxm
Re: Bluetooth mouse? (Solved)
Apologies for the noise. Playing again with blueman-manager I found an option 'create paring' and after that I could connect to the mouse and it is working now. Regards Johann -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3)
Bluetooth mouse?
I have used a bluetooth mouse for the past 4 years without problems. Since tha advent of systemd I cannot. When I run blueman-manager, it detects the device, but the setup wants to pair the mouse which of cause I cannot do (typing in a code on the mouse). If I proceed without paring and and mark it as a trusted device it looks fine in blueman-manager, but the mouse stays unusable. So how do I get my bluetooth mouse working again? Regards Johann -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3)
Bluetooth mouse and keyboard not detected after pause
Hi all! The following message remained unanswered on debian-powerpc NG. I hope there is somebody among the many more followers of this list who may have had a similar problem with Squeeze. I'm particularly curious to know whether upgrading to Wheezy could solve the problem. Thanks for your attention. Ennio - quote My wireless Apple keyboard and mouse are not aumatically detected after being inactive for 15-20 minutes and must be paired again with the aid of a usb keyboard or an iPad (giving "hidd --search" from command line). This happens with: . Mac Mini PowerPC G4 mid 2005 1.42GHz . Linux ... 2.6.32-powerpc and Debian/Squeeze . bluetooth 4.101-3 newer than version in archive . bluez/squeeze uptodate 4.66-3 . ps | grep bluetooth: root 443 0.0 0.0 0 0 ?S21:21 0:00 \_ [bluetooth] root 1243 0.0 0.3 5864 1644 ?Ss 21:21 0:00 /usr/sbin/bluetoothd root 1485 0.0 0.1 2564 772 ?S21:21 0:00 /usr/bin/bluetooth-agent ennio 1867 0.0 1.2 81076 6252 tty6 S21:23 0:00 \_ bluetooth-applet Do you have similar experience? Is there any workaround? Thanks in advance for any help. -- unquote - -- [Perche' usare Win$ozz (dico io) se ..."anche uno sciocco sa farlo. \\?// Fa' qualche cosa di cui non sei capace!" (diceva Henry Miller) ](°|°) [Why use Win$ozz (I say) if ... "even a fool can do that. )=( Do something you aren't good at!" (as Henry Miller used to say) ] -- 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/20131129181952.ga5...@deby.ei.hnet
Re: remapping bluetooth mouse buttons (microsoft notebook presenter 8000)
On Tue, 18 Aug 2009 12:12:58 +0300 Micha Feigin wrote: > Hello, > > I go myself one of these toys, the microsoft wireless notebook presenter 8000 > mouse which is a bluetooth mouse that can switch from mouse mode to > presentation mode (it's got several presentation buttons on the back). Its > recognized via bluetooth, all the top buttons are recognized (9 of them) and > works well. > > The problem is with the presentation buttons, they work, but unlike most > presentation hardware, instead of sending page up/page down they are sending > some other key. xev says its 166/167 and the xfce keyboard mapping tool > recognizes it as XF86Forward/XF86Back buttons. > > I want to get it to work with acrobat presentation which means that I need to > remap these to pageup/pagedown. I want to do this preferable only for the > mouse > as the keyboard also has XF86Forward/XF86Back keys that I would rather leave > as > they are. > > I'm guessing that there is some hal option but I'm not sure how to do it. > > Any guidance is welcome. > > Thanks > > Also tried lshal -m which shows: Start monitoring devicelist: - 13:23:04.575: bluetooth_acl_1dd8340a09_logicaldev_input condition ButtonPressed = play 13:23:09.038: bluetooth_acl_1dd8340a09_logicaldev_input condition ButtonPressed = forward 13:23:10.499: bluetooth_acl_1dd8340a09_logicaldev_input condition ButtonPressed = back 13:23:14.790: bluetooth_acl_1dd8340a09_logicaldev_input condition ButtonPressed = play-pause 13:23:26.442: bluetooth_acl_1dd8340a09_logicaldev_input condition ButtonPressed = forward 13:23:27.523: bluetooth_acl_1dd8340a09_logicaldev_input condition ButtonPressed = back 13:23:29.362: bluetooth_acl_1dd8340a09_logicaldev_input condition ButtonPressed = play-pause 13:23:30.056: bluetooth_acl_1dd8340a09_logicaldev_input condition ButtonPressed = volume-down 13:23:30.954: bluetooth_acl_1dd8340a09_logicaldev_input condition ButtonPressed = volume-up 13:23:34.534: bluetooth_acl_1dd8340a09_logicaldev_input condition ButtonPressed = close It looks like according to hal this is acting as a media player instead of a presentation tool -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: remapping bluetooth mouse buttons (microsoft notebook presenter 8000)
On Tue, 18 Aug 2009 12:12:58 +0300
Micha Feigin wrote:
> Hello,
>
> I go myself one of these toys, the microsoft wireless notebook presenter 8000
> mouse which is a bluetooth mouse that can switch from mouse mode to
> presentation mode (it's got several presentation buttons on the back). Its
> recognized via bluetooth, all the top buttons are recognized (9 of them) and
> works well.
>
> The problem is with the presentation buttons, they work, but unlike most
> presentation hardware, instead of sending page up/page down they are sending
> some other key. xev says its 166/167 and the xfce keyboard mapping tool
> recognizes it as XF86Forward/XF86Back buttons.
>
> I want to get it to work with acrobat presentation which means that I need to
> remap these to pageup/pagedown. I want to do this preferable only for the
> mouse
> as the keyboard also has XF86Forward/XF86Back keys that I would rather leave
> as
> they are.
>
> I'm guessing that there is some hal option but I'm not sure how to do it.
>
> Any guidance is welcome.
>
> Thanks
>
I dug a bit deeper and tried adding a file to /etc/hal/fdi/policy/ with the
content:
167:117
166:112
and lshal | grep keymap shows
input.keymap.data = {'167:117', '166:112'} (string list)
but it doesn't seem to have any effect
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
remapping bluetooth mouse buttons (microsoft notebook presenter 8000)
Hello, I go myself one of these toys, the microsoft wireless notebook presenter 8000 mouse which is a bluetooth mouse that can switch from mouse mode to presentation mode (it's got several presentation buttons on the back). Its recognized via bluetooth, all the top buttons are recognized (9 of them) and works well. The problem is with the presentation buttons, they work, but unlike most presentation hardware, instead of sending page up/page down they are sending some other key. xev says its 166/167 and the xfce keyboard mapping tool recognizes it as XF86Forward/XF86Back buttons. I want to get it to work with acrobat presentation which means that I need to remap these to pageup/pagedown. I want to do this preferable only for the mouse as the keyboard also has XF86Forward/XF86Back keys that I would rather leave as they are. I'm guessing that there is some hal option but I'm not sure how to do it. Any guidance is welcome. Thanks -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bluetooth mouse not connecting using Lenny
Hi List, Since my upgrade to Lenny, my mouse doesn't connect automatically anymore. To get my mouse working, I have to remove my USB bluetooth dongle and put it back. I've compared the modules before and after but everything is the same. Any one a suggestion what's going wrong? Kind regards, wimpunk. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bluetooth mouse not connecting using Lenny
Hi List, Since my upgrade to Lenny, my mouse doesn't connect automatically anymore. To get my mouse working, I have to remove my USB bluetooth dongle and put it back. I've compared the modules before and after but everything is the same. Any one a suggestion what's going wrong? Kind regards, wimpunk. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bluetooth mouse scroll wheel on Etch: mh2 and lvm crypt
On Wed, 23 May 2007 17:10:12 +0200 Douglas Allan Tutty <[EMAIL PROTECTED]> wrote: > On Wed, May 23, 2007 at 10:38:00AM -0400, [EMAIL PROTECTED] wrote: > > On Tue, 22 May 2007 06:10:07 +0200 > > Martin Manns <[EMAIL PROTECTED]> wrote: > > > > > What is the best way to get a kernel with the patch booting from > > > the encrypted root (and maintain the patch on kernel updates)? Is > > > there a step-by-step wiki around that I missed? > > > > No-one? Is this in the FAQ and I missed it? > > > > You're not being ignored but I just use a normal mouse. OK, it works now. Just a follow-up: One has to compile the kernel from the vanilla kernel.org sources. I used 2.6.21.3 and patched it with patch-2.6.21-mh1.gz from http://www.bluez.org/patches.html in order to make the mouse wheel work. Apparently the 2.6.20 mh2 patch from bluez does not work with the debian sid 2.6.20 kernel and lets it panic (even though compilation works all right). Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bluetooth mouse scroll wheel on Etch: mh2 and lvm crypt
On Wed, May 23, 2007 at 10:38:00AM -0400, [EMAIL PROTECTED] wrote: > On Tue, 22 May 2007 06:10:07 +0200 > Martin Manns <[EMAIL PROTECTED]> wrote: > > > What is the best way to get a kernel with the patch booting from the > > encrypted root (and maintain the patch on kernel updates)? Is there a > > step-by-step wiki around that I missed? > > No-one? Is this in the FAQ and I missed it? > You're not being ignored but I just use a normal mouse. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bluetooth mouse scroll wheel on Etch: mh2 and lvm crypt
On Tue, 22 May 2007 06:10:07 +0200 Martin Manns <[EMAIL PROTECTED]> wrote: > What is the best way to get a kernel with the patch booting from the > encrypted root (and maintain the patch on kernel updates)? Is there a > step-by-step wiki around that I missed? No-one? Is this in the FAQ and I missed it? Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bluetooth mouse scroll wheel on Etch: mh2 and lvm crypt
Hi, I just switched to Debian (Etch) with the 2.6.20 binary kernel from sid and root lvm encryption via the installer. Now, I have the problem that the scroll wheel of my bluetooth mouse does not work (/dev/input/mice does not produce any output on a wheel move, everything else works fine). I found the mh2 kernel patch that should address the problem and downloaded the sid 2.6.20 kernel sources, patched them and compiled the kernel. Now I am stuck. The compiled kernel does not find the mh2 module in the old initrd file and I could not find the proper way to generate a new and working initrd file. (I hesitate installing the libc sid packages that the respective kernel header packages seemingly depend on.) What is the best way to get a kernel with the patch booting from the encrypted root (and maintain the patch on kernel updates)? Is there a step-by-step wiki around that I missed? Should I use something like an overlay for kernel patches / sid packages and how does this work in debian? Thanks in advance Martin (BTW. is there any reason, why the mh2 patch is not part of the debian unstable kernel?) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bluetooth Mouse
Hi! I want to buy a new mouse, for example - NGS Wireless Optical Mini Mouse With Bluetooth Technology or - Anycom CC3141 BTM-100 Bluetooth MINI Mouse Does anybody work with this mouses or know other ones which work with SID and Gnome Bluetooth works (a few month ago). I download a picture from my mobile Thanks in advance CU Michael -- ,''`. Michael Ott, e-mail: michael at zolnott dot de : :' : Debian SID on Thinkpad T43: `. `'http://www.zolnott.de/laptop/ibm-t43-uc34nge.html `- pgpJ7RAz08sSE.pgp Description: PGP signature
