Re: Touchpad/trackpad not working
On 08/14/15 15:58, Anders Bolt-Evensen wrote: It seems that my solution was to add ums_load="YES" to /boot/loader.conf. After adding that the touchpad works fine for now: Mouse pointer moves when moving fingers across the touchpad Tapping works (annoyingly) Left-clicking works Right-clicking works Scrolling does not work, but I can live with that. Thanks to everyone who helped me solve my problem. Anders Hi, This probably means uhid is picking the device up before ums. Your solution is valid :-) --HPS ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Touchpad/trackpad not working
It seems that my solution was to add ums_load="YES" to /boot/loader.conf. After adding that the touchpad works fine for now: Mouse pointer moves when moving fingers across the touchpad Tapping works (annoyingly) Left-clicking works Right-clicking works Scrolling does not work, but I can live with that. Thanks to everyone who helped me solve my problem. Anders ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Touchpad/trackpad not working
On Aug 12, 2015, at 01:08 PM, Hans Petter Selasky wrote: On 08/12/15 12:32, Hans Petter Selasky wrote: On 08/12/15 11:31, Anders Bolt-Evensen wrote: When you don't see any activity, can you issue a reset of the touchpad: usbconfig -d X.Y reset while "usbdump" is running on the same device? --HPS Sure. usbconfig -d 0.3 reset results in the following output from the usbdump command: Can you run: sysctl hw.usb.ums.debug=15 Then re-run the "usbconfig -d X.Y reset" and send resulting dmesg? --HPS Hi, The issue might be that the BIOS is re-programming the USB device somehow. I see the HID descriptor has support for different modes, and possible the device is not re-setting its internal state upon re-enumeration. You can try: usbconfig -d X.Y power_off usbconfig -d X.Y reset Maybe if you disable USB legacy support in the BIOS it will work. Sadly, there is no such thing in the BIOS of this computer (an Acer Aspire VN7-791G). The only legacy thing in this BIOS is to choose between UEFI (which I'm using) and the older CSM. I cannot see anything related to USB in this BIOS other than in the boot order and in that case I can only choose the boot order of USB storage devices. BTW: The log you sent appears to be from a USB keyboard only device and not a USB mouse! Also try: kldload ums Can you send output from: usbconfig show_ifdrv Here is the output of usbconfig show_ifdrv: ugen0.1: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen0.1.0: uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> ugen1.1: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen1.1.0: uhub1: ugen2.1: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen2.1.0: uhub2: ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) ugen1.2: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen1.2.0: uhub3: ugen2.2: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen2.2.0: uhub4: ugen0.3: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) ugen0.3.0: uhid0: ugen0.4: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) usbconfig dump_device_desc dump_curr_config_desc When it works and when it doesn't work? When the touchpad is not working, here is the output of usbconfig dump_device_desc dump_curr_config_desc: https://www.dropbox.com/s/utllovfkamnqi9p/usbconfig_dump_device_desc_curr_config_desc_not_working.txt?dl=0 Now, I connected the external USB receiver and rebooted the system. Now, because the external device is connected, the touchpad works just fine. Here is the output of usbconfig dump_device_desc dump_curr_config_desc: https://www.dropbox.com/s/r3pnqsk9aul1z8e/usbconfig_dump_device_desc_curr_config_desc_working.txt?dl=0 Output from dmesg is also appreciated. Output of the verbose boot messages without the external mouse: https://www.dropbox.com/s/ukpoyg6rsl3jjgd/dmesg_without_external_usb.txt?dl=0 Output of the verbose boot messages with the external mouse: https://www.dropbox.com/s/uga7p5zlxh7knsj/dmesg_with_external_usb.txt?dl=0 Can you run: sysctl hw.usb.ums.debug=15 Then re-run the "usbconfig -d X.Y reset" and send resulting dmesg? If I run sysctl.hw.usb.ums.debug=15 without the external USB device, sysctl returns: sysctl: unknown oid 'hw.usb.ums.debug': No such file or directory. I decided to go ahead and run the other commands (usbconfig -d 0.3 reset) and post the resulting messages from dmesg: uhid0: at uhub0, port 7, addr 2 (disconnected) hid_get_item: Number of items truncated to 255 uhid0: on usbus0 hid_get_item: Number of items truncated to 255 hid_get_item: Number of items truncated to 255 hid_get_item: Number of items truncated to 255 random: harvesting attach, 8 bytes (4 bits) from uhid0 Full output from lsusb without the external usb receiver: Bus /dev/usb Device /dev/ugen0.4: ID 04f2:b474 Chicony Electronics Co., Ltd Bus /dev/usb Device /dev/ugen0.3: ID 06cb:2970 Synaptics, Inc. Bus /dev/usb Device /dev/ugen2.2: ID 8087:8000 Bus /dev/usb Device /dev/ugen1.2: ID 8087:8008 Bus /dev/usb Device /dev/ugen0.2: ID 0bda:0129 Realtek Semiconductor Corp. Bus /dev/usb Device /dev/ugen2.1: ID : Bus /dev/usb Device /dev/ugen1.1: ID : Bus /dev/usb Device /dev/ugen0.1: ID : With the receiver plugged in, running sysctl hw.usb.ums.debug=15 and then usbconfig -d 0.4 reset, results in the following dmesg (when I reboot with the external usb receiver plugged in, according to lsusb, the device node for the Synaptics (touchpad) device changes from /dev/ugen0.3 to /dev/ugen0.4): ums1: at uhub0, port 7, addr 3 (disconnected) ums_detach: sc=0xf80027409800 ums_close: ums_close: hid_get_item: Number of items truncated to 255 ums_probe: hid_get_item: Number of items truncated to 255 ums_probe: hid_get_item: Number of items truncated to 255 ums_attach: sc=0xf80027409800 ums1: on usbus0 hid_get_item: Number of items truncated to 255 hid_get_
Re: Touchpad/trackpad not working
On 08/12/15 12:32, Hans Petter Selasky wrote: On 08/12/15 11:31, Anders Bolt-Evensen wrote: When you don't see any activity, can you issue a reset of the touchpad: usbconfig -d X.Y reset while "usbdump" is running on the same device? --HPS Sure. usbconfig -d 0.3 reset results in the following output from the usbdump command: Can you run: sysctl hw.usb.ums.debug=15 Then re-run the "usbconfig -d X.Y reset" and send resulting dmesg? --HPS Hi, The issue might be that the BIOS is re-programming the USB device somehow. I see the HID descriptor has support for different modes, and possible the device is not re-setting its internal state upon re-enumeration. You can try: usbconfig -d X.Y power_off usbconfig -d X.Y reset Maybe if you disable USB legacy support in the BIOS it will work. BTW: The log you sent appears to be from a USB keyboard only device and not a USB mouse! Also try: kldload ums Can you send output from: usbconfig show_ifdrv usbconfig dump_device_desc dump_curr_config_desc When it works and when it doesn't work? Output from dmesg is also appreciated. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: Touchpad/trackpad not working
On 08/12/15 11:31, Anders Bolt-Evensen wrote: When you don't see any activity, can you issue a reset of the touchpad: usbconfig -d X.Y reset while "usbdump" is running on the same device? --HPS Sure. usbconfig -d 0.3 reset results in the following output from the usbdump command: Can you run: sysctl hw.usb.ums.debug=15 Then re-run the "usbconfig -d X.Y reset" and send resulting dmesg? --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: Touchpad/trackpad not working
On Aug 12, 2015, at 09:56 AM, Hans Petter Selasky wrote: On 08/12/15 09:28, Anders Bolt-Evensen wrote: On Aug 11, 2015, at 05:03 PM, Hans Petter Selasky wrote: On 08/11/15 16:40, Anthony Jenkins via freebsd-usb wrote: hid_is_mouse() is failing to tell that your Synaptics USB HID device is a mouse, but /only/ when there's no other USB (HID) device on that USB bus (usbus0). I suspect it has to do with the hid_get_item() warnings about chopping stuff off. I can't tell from the source code for hid_get_item() (a 313-line function) why it's behaving that way, or why a totally different HID device (Logitech mouse) causes it to behave differently for this HID device (Synaptics touchpad). I've added freebsd-usb@ to see if they know what's going on. ajenkins@kubuntu-ajenkins:~/Downloads$ grep usbus0 dmesg_with_external_usb.txt usbus0: waiting for BIOS to give up control usbus0 on xhci0 random: harvesting attach, 8 bytes (4 bits) from usbus0 usbus0: 5.0Gbps Super Speed USB v3.0 ugen0.1: <0x8086> at usbus0 uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 Root mount waiting for: usbus2 usbus1 usbus0 ugen0.2: at usbus0 ukbd0: on usbus0 Root mount waiting for: usbus0 ugen0.3: at usbus0 Root mount waiting for: usbus0 ugen0.4: at usbus0 ugen0.5: at usbus0 Root mount waiting for: usbus0 Root mount waiting for: usbus0 [snip] Root mount waiting for: usbus0 Root mount waiting for: usbus0 ugen0.6: at usbus0 (disconnected) ums0: on usbus0 ums1: on usbus0 uhid0: on usbus0 What possessed the laptop manufacturer to hang the Synaptics touchpad device off a USB 3.0 controller is beyond me... I have problems booting FreeBSD off USB 3.0 mass storage devices. Hi, Does your mouse only fail to work in X-org, or also the console? Run "usbdump -i usbusX -f Y -s 65536 -vvv" to catch USB events for ugenX.Y. That might give some further clues. If using X.org, do you use hald or devd backend? --HPS It fails in both X-org and console. In X, recently I've only been using devd. When trying to use the command usbdump -i usbus0 -f 3 -s 65536 -vvv on my touchpad (without any external usb receiver connected), nothing happens at all. No left-click, no right-click, nothing. However, if I insert an external USB receiver and then reboot the computer, the touchpad works just fine in both console and in X-org. If I now do the command above, since I've connected the receiver and done the reboot, I get the following output (just note that during the reboot, the address of the touchpad was changed from ugen0.3 to ugen0.4): https://www.dropbox.com/s/ktj757okcq61ljc/usbdump_i_usbusX_f_Y_s_65536_vvv.txt?dl=0 On Aug 11, 2015, at 05:46 PM, Zoran Kolic wrote: What do you have in device.hints? Zoran When you don't see any activity, can you issue a reset of the touchpad: usbconfig -d X.Y reset while "usbdump" is running on the same device? --HPS Sure. usbconfig -d 0.3 reset results in the following output from the usbdump command: 11:24:32.121246 usbus0.3 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 00 09 00 00 00 00 00 00 -- -- -- -- -- -- -- -- || flags 0x10 status 0xca1a3 11:24:32.121619 usbus0.3 DONE-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0 frame[0] WRITE 8 bytes flags 0x10 status 0xca1a1 11:24:32.499707 usbus0.3 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 80 06 00 01 00 00 08 00 -- -- -- -- -- -- -- -- || frame[1] READ 8 bytes flags 0x10 status 0xea1a3 11:24:32.501363 usbus0.3 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 8 bytes 12 01 00 02 00 00 00 08 -- -- -- -- -- -- -- -- || flags 0x10 status 0xea1a1 11:24:32.501467 usbus0.3 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 80 06 00 01 00 00 12 00 -- -- -- -- -- -- -- -- || frame[1] READ 18 bytes flags 0x10 status 0xca1a3 11:24:32.502123 usbus0.3 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=20,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 18 bytes 12 01 00 02 00 00 00 08 CB 06 70 29 08 00 01 02 |..p)| 0010 00 01 -- -- -- -- -- -- -- -- -- -- -- -- -- -- |.. | flags 0x10 status 0xca1a1 11:24:32.502231 usbus0.3 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 80 06 00 02 00 00 09 00 -- -- -- -- -- -- -- -- || frame[1] READ 9 bytes flags 0x10 status 0xea1a3 11:24:32.502630 usbus0.3 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=12,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 9 bytes 09 02 29 00 01 01 00 A0 32 -- -- -- -- -- -- -- |..).2 | flags 0x10 status 0xea1a1 11:24:32.502735 usbus0.3 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 80 06 00 02 00 00 29 00 -- -- -- -- -- -- -- -- |..).| frame[1] READ 41 bytes flags 0x10 s
Re: Touchpad/trackpad not working
On 08/12/15 09:28, Anders Bolt-Evensen wrote: On Aug 11, 2015, at 05:03 PM, Hans Petter Selasky wrote: On 08/11/15 16:40, Anthony Jenkins via freebsd-usb wrote: hid_is_mouse() is failing to tell that your Synaptics USB HID device is a mouse, but /only/ when there's no other USB (HID) device on that USB bus (usbus0). I suspect it has to do with the hid_get_item() warnings about chopping stuff off. I can't tell from the source code for hid_get_item() (a 313-line function) why it's behaving that way, or why a totally different HID device (Logitech mouse) causes it to behave differently for this HID device (Synaptics touchpad). I've added freebsd-usb@ to see if they know what's going on. ajenkins@kubuntu-ajenkins:~/Downloads$ grep usbus0 dmesg_with_external_usb.txt usbus0: waiting for BIOS to give up control usbus0 on xhci0 random: harvesting attach, 8 bytes (4 bits) from usbus0 usbus0: 5.0Gbps Super Speed USB v3.0 ugen0.1: <0x8086> at usbus0 uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 Root mount waiting for: usbus2 usbus1 usbus0 ugen0.2: at usbus0 ukbd0: on usbus0 Root mount waiting for: usbus0 ugen0.3: at usbus0 Root mount waiting for: usbus0 ugen0.4: at usbus0 ugen0.5: at usbus0 Root mount waiting for: usbus0 Root mount waiting for: usbus0 [snip] Root mount waiting for: usbus0 Root mount waiting for: usbus0 ugen0.6: at usbus0 (disconnected) ums0: on usbus0 ums1: on usbus0 uhid0: on usbus0 What possessed the laptop manufacturer to hang the Synaptics touchpad device off a USB 3.0 controller is beyond me... I have problems booting FreeBSD off USB 3.0 mass storage devices. Hi, Does your mouse only fail to work in X-org, or also the console? Run "usbdump -i usbusX -f Y -s 65536 -vvv" to catch USB events for ugenX.Y. That might give some further clues. If using X.org, do you use hald or devd backend? --HPS It fails in both X-org and console. In X, recently I've only been using devd. When trying to use the command usbdump -i usbus0 -f 3 -s 65536 -vvv on my touchpad (without any external usb receiver connected), nothing happens at all. No left-click, no right-click, nothing. However, if I insert an external USB receiver and then reboot the computer, the touchpad works just fine in both console and in X-org. If I now do the command above, since I've connected the receiver and done the reboot, I get the following output (just note that during the reboot, the address of the touchpad was changed from ugen0.3 to ugen0.4): https://www.dropbox.com/s/ktj757okcq61ljc/usbdump_i_usbusX_f_Y_s_65536_vvv.txt?dl=0 On Aug 11, 2015, at 05:46 PM, Zoran Kolic wrote: What do you have in device.hints? Zoran When you don't see any activity, can you issue a reset of the touchpad: usbconfig -d X.Y reset while "usbdump" is running on the same device? --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: Touchpad/trackpad not working
On Aug 11, 2015, at 05:03 PM, Hans Petter Selasky wrote: On 08/11/15 16:40, Anthony Jenkins via freebsd-usb wrote: hid_is_mouse() is failing to tell that your Synaptics USB HID device is a mouse, but /only/ when there's no other USB (HID) device on that USB bus (usbus0). I suspect it has to do with the hid_get_item() warnings about chopping stuff off. I can't tell from the source code for hid_get_item() (a 313-line function) why it's behaving that way, or why a totally different HID device (Logitech mouse) causes it to behave differently for this HID device (Synaptics touchpad). I've added freebsd-usb@ to see if they know what's going on. ajenkins@kubuntu-ajenkins:~/Downloads$ grep usbus0 dmesg_with_external_usb.txt usbus0: waiting for BIOS to give up control usbus0 on xhci0 random: harvesting attach, 8 bytes (4 bits) from usbus0 usbus0: 5.0Gbps Super Speed USB v3.0 ugen0.1: <0x8086> at usbus0 uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 Root mount waiting for: usbus2 usbus1 usbus0 ugen0.2: at usbus0 ukbd0: on usbus0 Root mount waiting for: usbus0 ugen0.3: at usbus0 Root mount waiting for: usbus0 ugen0.4: at usbus0 ugen0.5: at usbus0 Root mount waiting for: usbus0 Root mount waiting for: usbus0 [snip] Root mount waiting for: usbus0 Root mount waiting for: usbus0 ugen0.6: at usbus0 (disconnected) ums0: on usbus0 ums1: on usbus0 uhid0: on usbus0 What possessed the laptop manufacturer to hang the Synaptics touchpad device off a USB 3.0 controller is beyond me... I have problems booting FreeBSD off USB 3.0 mass storage devices. Hi, Does your mouse only fail to work in X-org, or also the console? Run "usbdump -i usbusX -f Y -s 65536 -vvv" to catch USB events for ugenX.Y. That might give some further clues. If using X.org, do you use hald or devd backend? --HPS It fails in both X-org and console. In X, recently I've only been using devd. When trying to use the command usbdump -i usbus0 -f 3 -s 65536 -vvv on my touchpad (without any external usb receiver connected), nothing happens at all. No left-click, no right-click, nothing. However, if I insert an external USB receiver and then reboot the computer, the touchpad works just fine in both console and in X-org. If I now do the command above, since I've connected the receiver and done the reboot, I get the following output (just note that during the reboot, the address of the touchpad was changed from ugen0.3 to ugen0.4): https://www.dropbox.com/s/ktj757okcq61ljc/usbdump_i_usbusX_f_Y_s_65536_vvv.txt?dl=0 On Aug 11, 2015, at 05:46 PM, Zoran Kolic wrote: What do you have in device.hints? Zoran /boot/device.hints has the following contents: hint.fdc.0.at="isa" hint.fdc.0.port="0x3F0" hint.fdc.0.irq="6" hint.fdc.0.drq="2" hint.fd.0.at="fdc0" hint.fd.0.drive="0" hint.fd.1.at="fdc0" hint.fd.1.drive="1" hint.atkbdc.0.at="isa" hint.atkbdc.0.port="0x060" hint.atkbd.0.at="atkbdc" hint.atkbd.0.irq="1" hint.psm.0.at="atkbdc" hint.psm.0.irq="12" hint.sc.0.at="isa" hint.sc.0.flags="0x100" hint.uart.0.at="isa" hint.uart.0.port="0x3F8" hint.uart.0.flags="0x10" hint.uart.0.irq="4" hint.uart.1.at="isa" hint.uart.1.port="0x2F8" hint.uart.1.irq="3" hint.ppc.0.at="isa" hint.ppc.0.irq="7" hint.atrtc.0.at="isa" hint.atrtc.0.port="0x70" hint.atrtc.0.irq="8" hint.attimer.0.at="isa" hint.attimer.0.port="0x40" hint.attimer.0.irq="0" hint.wbwd.0.at="isa" hint.acpi_throttle.0.disabled="1" hint.p4tcc.0.disabled="1" ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Touchpad/trackpad not working
On Aug 11, 2015, at 05:04 PM, Hans Petter Selasky wrote: On 08/11/15 16:40, Anthony Jenkins via freebsd-usb wrote: hid_is_mouse() is failing to tell that your Synaptics USB HID device is a mouse, but /only/ when there's no other USB (HID) device on that USB bus (usbus0). I suspect it has to do with the hid_get_item() warnings about chopping stuff off. I can't tell from the source code for hid_get_item() (a 313-line function) why it's behaving that way, or why a totally different HID device (Logitech mouse) causes it to behave differently for this HID device (Synaptics touchpad). I've added freebsd-usb@ to see if they know what's going on. ajenkins@kubuntu-ajenkins:~/Downloads$ grep usbus0 dmesg_with_external_usb.txt usbus0: waiting for BIOS to give up control usbus0 on xhci0 random: harvesting attach, 8 bytes (4 bits) from usbus0 usbus0: 5.0Gbps Super Speed USB v3.0 ugen0.1: <0x8086> at usbus0 uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 Root mount waiting for: usbus2 usbus1 usbus0 ugen0.2: at usbus0 ukbd0: on usbus0 Root mount waiting for: usbus0 ugen0.3: at usbus0 Root mount waiting for: usbus0 ugen0.4: at usbus0 ugen0.5: at usbus0 Root mount waiting for: usbus0 Root mount waiting for: usbus0 [snip] Root mount waiting for: usbus0 Root mount waiting for: usbus0 ugen0.6: at usbus0 (disconnected) ums0: on usbus0 ums1: on usbus0 uhid0: on usbus0 What possessed the laptop manufacturer to hang the Synaptics touchpad device off a USB 3.0 controller is beyond me... I have problems booting FreeBSD off USB 3.0 mass storage devices. Hi, Does your mouse only fail to work in X-org, or also the console? Run "usbdump -i usbusX -f Y -s 65536 -vvv" to catch USB events for ugenX.Y. That might give some further clues. If using X.org, do you use hald or devd backend? --HPS It fails in both X-org and console. In X, recently I've only been using devd. When trying to use the command usbdump -i usbus0 -f 3 -s 65536 -vvv on my touchpad (without any external usb receiver connected), nothing happens at all. No left-click, no right-click, nothing. However, if I insert an external USB receiver and then reboot the computer, the touchpad works just fine in both console and in X-org. If I now do the command above, since I've connected the receiver and done the reboot, I get the following output (just note that during the reboot, the address of the touchpad was changed from ugen0.3 to ugen0.4): https://www.dropbox.com/s/ktj757okcq61ljc/usbdump_i_usbusX_f_Y_s_65536_vvv.txt?dl=0 On Aug 11, 2015, at 05:46 PM, Zoran Kolic wrote: What do you have in device.hints? Zoran /boot/device.hints has the following contents: hint.fdc.0.at="isa" hint.fdc.0.port="0x3F0" hint.fdc.0.irq="6" hint.fdc.0.drq="2" hint.fd.0.at="fdc0" hint.fd.0.drive="0" hint.fd.1.at="fdc0" hint.fd.1.drive="1" hint.atkbdc.0.at="isa" hint.atkbdc.0.port="0x060" hint.atkbd.0.at="atkbdc" hint.atkbd.0.irq="1" hint.psm.0.at="atkbdc" hint.psm.0.irq="12" hint.sc.0.at="isa" hint.sc.0.flags="0x100" hint.uart.0.at="isa" hint.uart.0.port="0x3F8" hint.uart.0.flags="0x10" hint.uart.0.irq="4" hint.uart.1.at="isa" hint.uart.1.port="0x2F8" hint.uart.1.irq="3" hint.ppc.0.at="isa" hint.ppc.0.irq="7" hint.atrtc.0.at="isa" hint.atrtc.0.port="0x70" hint.atrtc.0.irq="8" hint.attimer.0.at="isa" hint.attimer.0.port="0x40" hint.attimer.0.irq="0" hint.wbwd.0.at="isa" hint.acpi_throttle.0.disabled="1" hint.p4tcc.0.disabled="1" ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: Touchpad/trackpad not working
On 08/11/15 16:40, Anthony Jenkins via freebsd-usb wrote: hid_is_mouse() is failing to tell that your Synaptics USB HID device is a mouse, but /only/ when there's no other USB (HID) device on that USB bus (usbus0). I suspect it has to do with the hid_get_item() warnings about chopping stuff off. I can't tell from the source code for hid_get_item() (a 313-line function) why it's behaving that way, or why a totally different HID device (Logitech mouse) causes it to behave differently for this HID device (Synaptics touchpad). I've added freebsd-usb@ to see if they know what's going on. ajenkins@kubuntu-ajenkins:~/Downloads$ grep usbus0 dmesg_with_external_usb.txt usbus0: waiting for BIOS to give up control usbus0 on xhci0 random: harvesting attach, 8 bytes (4 bits) from usbus0 usbus0: 5.0Gbps Super Speed USB v3.0 ugen0.1: <0x8086> at usbus0 uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 Root mount waiting for: usbus2 usbus1 usbus0 ugen0.2: at usbus0 ukbd0: on usbus0 Root mount waiting for: usbus0 ugen0.3: at usbus0 Root mount waiting for: usbus0 ugen0.4: at usbus0 ugen0.5: at usbus0 Root mount waiting for: usbus0 Root mount waiting for: usbus0 [snip] Root mount waiting for: usbus0 Root mount waiting for: usbus0 ugen0.6: at usbus0 (disconnected) ums0: on usbus0 ums1: on usbus0 uhid0: on usbus0 What possessed the laptop manufacturer to hang the Synaptics touchpad device off a USB 3.0 controller is beyond me... I have problems booting FreeBSD off USB 3.0 mass storage devices. Hi, Does your mouse only fail to work in X-org, or also the console? Run "usbdump -i usbusX -f Y -s 65536 -vvv" to catch USB events for ugenX.Y. That might give some further clues. If using X.org, do you use hald or devd backend? --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: Touchpad/trackpad not working
[Adding freebsd-usb@] On 08/11/2015 02:03 AM, Anders Bolt-Evensen wrote: > > > On Aug 10, 2015, at 06:33 PM, Anthony Jenkins via freebsd-mobile > wrote: > >> >> >> On 08/10/2015 02:29 AM, Anders Bolt-Evensen wrote: >>> >>> >>> On Aug 09, 2015, at 03:07 AM, Anthony Jenkins >>> wrote: >>> >>>> >>>> >>>> On 08/07/15 02:19, Anders Bolt-Evensen wrote: >>>>> >>>>> >>>>> On Aug 06, 2015, at 07:01 PM, Anthony Jenkins >>>>> wrote: >>>>> >>>>>> >>>>>> >>>>>> On 08/06/2015 01:42 AM, Anders Bolt-Evensen wrote: >>>>>>> >>>>>>> >>>>>>> On Aug 05, 2015, at 07:48 PM, Anthony Jenkins >>>>>>> >>>>>>> wrote: >>>>>>> >>>>>>>> [Dropping current@] >>>>>>>> >>>>>>>>> >>>>>>>>> From: Anders Bolt-Evensen >>>>>>>>> To: freebsd-curr...@freebsd.org; freebsd-mob...@freebsd.org Sent: >>>>>>>>> Wednesday, August 5, 2015 11:38 AM >>>>>>>>> Subject: Touchpad/trackpad not working >>>>>>>>> >>>>>>>>> >>>>>>>>> Hello, everyone! >>>>>>>>> On my Acer Aspire V17 Nitro I have a little problems with my >>>>>>>>> touchpad/trackpad: >>>>>>>>> When I boot the system, in this case, on FreeBSD Current (the >>>>>>>>> problem also exists on FreeBSD 10) without an external USB >>>>>>>>> receiver >>>>>>>>> connected, my trackpad does not work at all, neither in >>>>>>>>> console or >>>>>>>>> in X. >>>>>>>>> In other words I am not able to do a left or right click and >>>>>>>>> moving >>>>>>>>> the pointer does not work either. >>>>>>>>> I cannot see any mention of it when I take a look at dmesg, other >>>>>>>>> than a message that says "psm0: unable to allocate IRQ" >>>>>>>>> Today I installed sysutils/usbutils to see if I could get any >>>>>>>>> more >>>>>>>>> info about my problem and then took a look at output of the >>>>>>>>> command >>>>>>>>> "lsusb". >>>>>>>>> I see the following output: >>>>>>>>> Bus /dev/usb Device /dev/ugen0.5: ID 046d:c52b Logitech, Inc. >>>>>>>>> Bus /dev/usb Device /dev/ugen0.4: ID 04f2:b474 Chicony >>>>>>>>> Electronics >>>>>>>>> Co., Ltd >>>>>>>>> Bus /dev/usb Device /dev/ugen0.3: ID 06cb:2970 Synaptics, Inc. >>>>>>>> >>>>>>>> Weird...first time seeing a Synaptics device on USB. I know psm(4) >>>>>>>> generally handles Synaptics protocol in FreeBSD (if you enable >>>>>>>> synaptics >>>>>>>> support), but your device isn't hanging off the >>>>>>>> atkbd(4)/psm(4). I'd >>>>>>>> expect ums(4) to attach then... no idea why it isn't, or if it >>>>>>>> supports >>>>>>>> the Synaptics protocol. >>>>>>>> >>>>>>>> Can you tell me what the following command reports: >>>>>>>> >>>>>>>> usbconfig -d ugen0.3 dump_device_desc >>>>>>>> >>>>>>>> I think the device needs to report itself as a USB HID device for >>>>>>>> ums(4) >>>>>>>> to attach. >>>>>>>> >>>>>>>> Also, do you have moused(8) running? >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Anthony Jenkins >>>>>>> >>>>>>> In /etc/rc.conf I do have moused_enable="YES", but sudo >>>>>>> /etc/rc.d/moused status reports >>>>>>> "moused is not running". I assume it is because of missing psm0. >>>>>>> >>>>>>
