On Sat, 2021-01-30 at 08:36 +0100, Anton Lindqvist wrote: > On Fri, Jan 29, 2021 at 10:15:05PM +0200, Ville Valkonen wrote: > > Hi, > > > > I have a bit oldish Logitech M705 mouse, bought around 2010-2011. > > Regarding the dmesg (on below) I can see it gets attached correctly > > to > > uhiddp0 but doesn't report battery levels. Here's the line from > > dmesg: > > uhidpp0 at uhidev2 device 1 mouse "M705" serial xx-xx-x-xx, device > > 2 keyboard "K750" serial xx-xx-xx-xx. > > And corresponding sysctl values: > > hw.sensors.uhidpp0.raw0=unknown (battery levels) > > hw.sensors.uhidpp0.raw1=unknown (battery levels) > > hw.sensors.uhidpp0.percent0=unknown (battery level) > > hw.sensors.uhidpp0.percent1=unknown (battery level) > > > > Not sure if censoring of serial has any value, though. > > Glad to see it attaches fine to a receiver with more than one device > paired. I only have one device myself and have therefore never been > enable to verify this. > > Could you enable UHIDPP_DEBUG and send me the output? > > > On Ubuntu battery levels are detected correctly so I could probably > > take a USB dump with Wireshark and compare the differences. > > Taking a USB dump on your Linux machine would be very helpful.
Hi, Yes. Also remembered that you were mentioning about the debug flag but completely forgot that while testing. Then just before going to sleep recalled the debug flag. Here are the results with debug enabled: <dmesg_debug> uhidev0 at uhub0 port 1 configuration 1 interface 0 "Logitech USB Receiver" rev 2.00/12.10 addr 3 uhidev0: iclass 3/1 ukbd0 at uhidev0: 8 variable keys, 6 key codes wskbd1 at ukbd0 mux 1 wskbd1: connecting to wsdisplay0 uhidev1 at uhub0 port 1 configuration 1 interface 1 "Logitech USB Receiver" rev 2.00/12.10 addr 3 uhidev1: iclass 3/1, 8 report ids ums0 at uhidev1 reportid 2: 16 buttons, Z and W dir wsmouse2 at ums0 mux 0 uhid0 at uhidev1 reportid 3: input=4, output=0, feature=0 uhid1 at uhidev1 reportid 4: input=1, output=0, feature=0 uhid2 at uhidev1 reportid 8: input=1, output=0, feature=0 uhidev2 at uhub0 port 1 configuration 1 interface 2 "Logitech USB Receiver" rev 2.00/12.10 addr 3 uhidev2: iclass 3/0, 33 report ids uhidpp0 at uhidev2hidpp_send_report: 10 ff 83 b5 [30 00 00] uhidpp_intr: 11 ff 83 b5 [30 c4 b4 96 9e 04 00 00 00 01 00 00 00 00 00 00] hidpp_send_report: 10 ff 83 b5 [20 00 00] uhidpp_intr: 11 ff 83 b5 [20 09 08 10 1b 04 00 02 06 00 00 00 00 00 00 00] hidpp_send_report: 10 ff 83 b5 [40 00 00] uhidpp_intr: 11 ff 83 b5 [40 04 4d 37 30 35 00 00 00 00 00 00 00 00 00 00] device 1 mouse "M705" serial xx-xx-xx-9ehidpp_send_report: 10 ff 83 b5 [31 00 00] uhidpp_intr: 11 ff 83 b5 [31 8d 37 6a 6f 1a 40 00 00 03 00 00 00 00 00 00] hidpp_send_report: 10 ff 83 b5 [21 00 00] uhidpp_intr: 11 ff 83 b5 [21 08 14 40 02 04 00 01 07 00 00 00 00 00 00 00] hidpp_send_report: 10 ff 83 b5 [41 00 00] uhidpp_intr: 11 ff 83 b5 [41 04 4b 37 35 30 00 00 00 00 00 00 00 00 00 00] , device 2 keyboard "K750" serial xx-xx-xx-6fhidpp_send_report: 10 ff 83 b5 [32 00 00] uhidpp_intr: 10 ff 8f 83 [b5 03 00] hidpp_send_report: 10 ff 83 b5 [33 00 00] uhidpp_intr: 10 ff 8f 83 [b5 03 00] hidpp_send_report: 10 ff 83 b5 [34 00 00] uhidpp_intr: 10 ff 8f 83 [b5 03 00] hidpp_send_report: 10 ff 83 b5 [35 00 00] uhidpp_intr: 10 ff 8f 83 [b5 03 00] hidpp_send_report: 10 ff 80 00 [10 09 00] uhidpp_intr: 10 ff 80 00 [00 00 00] </dmesg_debug> That's when the mouse was off. When I switched on the mouse kernel panicked. I couldn't break into DDB or alternatively failed to type correct commands blindly. Eventually had to shutdown the system by pressing the power button. Picture of the panic is here: https://imgur.com/a/QRAD5v1 Btw. Time has passed since my previous kernel compile. I saw the procedure has changed a bit since then. I initially tried to compile debug flags by prepending `option UHIDPP_DEBUG` to sys/arch/amd64/compile/GENERIC.MP but couldn't see debug lines in dmesg. By doing the "old way" I got the debug lines: cd arch/amd64/conf cp GENERIC.MP HIDPP.MP # Add debug flags at this point config HIDPP.MP and compiling as usual. Is this the correct way to do it? I'll do the Wireshark later in the evening. -- Regards, Ville
