Re: USB 3 strange behavior, lenovo x240
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 01/16/15 13:12, Sean Bruno wrote: On 01/16/15 11:48, Hans Petter Selasky wrote: On 01/16/15 19:00, Sean Bruno wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I'm seeing strange behavior when I enable USB 3 support on my laptop. Running head @r276878: Disabling USB 3 makes things behave better in that my wireless device will actually serve traffic and /dev/video0 will really exist when I switch over. Using USB 3 makes things behave erratically if at all. Devices don't appear after a reboot and I'm seeing issues using my USB 2 devices. Hi, Does setting: hw.usb.xhci.xhci_port_route=-1 In /boot/loader.conf Help? --HPS It does seem to help somewhat. Devices are available: % usbconfig ugen0.1: XHCI root HUB 0x8086 at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen1.1: EHCI root HUB Intel at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen1.2: product 0x8000 vendor 0x8087 at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen1.3: 802.11n NIC Realtek at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) ugen1.4: Integrated Camera SunplusIT INC. at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) sean _ Hrm ... yeah. devices like my USB network adapter and USB camera (integrated) are definitely not working. The camera doesn't work in USB2 nor USB3 mode. The USB wireless device only works reliably if I disable USB3. sean -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQF8BAEBCgBmBQJUv9n0XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5krCkH/2Cihq1EhBv52UZgTQ8L297W HG/fyMVKPZ7vFkijUEwDWuSIAb4N0G0gB6SIYSL5fmlVRxzsSFRQD24qxYfsr0p6 Tdx2C0YHM22bjYqcnjGN9U0aN1BzauQbImt6jDQbtP3uBcxlRavX+next16q5aV5 2+rbBIMUJSDM/kgM/8aSaHg4WYWvOP/vbK7uyyLmukNsbjO8VauJ4raVPsi0pBcQ pltJRkHYRIuJ9mWYu1mfthrcLYALSXEjbRIujQj2aymIc+zjKhzSDCSI1ic2k8NS rxr0/IOklgz1cGiiZZv0MLEf0jBQmDpz7mmSIRIqMm70Sa+gqLP8qnfJwrggPEw= =+DXZ -END PGP SIGNATURE- ___ 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: Problem with libusb20_dev_get_port_path()
On 2015-01-20 22:44, Hans Petter Selasky wrote: On 01/20/15 20:48, Uffe Jakobsen wrote: On 2015-01-20 12:45, Hans Petter Selasky wrote: It appears there is a minor bug in the kernel regarding this field. See below: https://svnweb.freebsd.org/changeset/base/277417 Should work now. Thanks for the quick response and fix How far back does the problem reach ? I think the IOCTL never worked except returning no path (0) like you observed. Ok, thanks Another observation around the cross-platform use of libusb20_dev_get_port_path() and libusb_get_port_numbers(): On FreeBSD it seems that one needs to perform the respective usb open calls for the device before the two calls above succeeds without an negative error code. Whereas the usb open calls does not seem to be needed with the linux impl of libusb. Different behaviour between libusb on FreeBSD and linux creates a compatibility problems where linux-maintained programs accessing libusb20_dev_get_port_path() and libusb_get_port_numbers() will fail on FreeBSD but works on linux. (I've just spent some hours with such program) :-) I've looked through the available documentation without finding anything substantial - and hence I do not know which one is right. /Uffe ___ 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: Problem with libusb20_dev_get_port_path()
On 2015-01-22 00:29, Uffe Jakobsen wrote: On 2015-01-20 22:44, Hans Petter Selasky wrote: On 01/20/15 20:48, Uffe Jakobsen wrote: On 2015-01-20 12:45, Hans Petter Selasky wrote: It appears there is a minor bug in the kernel regarding this field. See below: https://svnweb.freebsd.org/changeset/base/277417 Should work now. Thanks for the quick response and fix How far back does the problem reach ? I think the IOCTL never worked except returning no path (0) like you observed. Ok, thanks Another observation around the cross-platform use of libusb20_dev_get_port_path() and libusb_get_port_numbers(): On FreeBSD it seems that one needs to perform the respective usb open calls for the device before the two calls above succeeds without an negative error code. Whereas the usb open calls does not seem to be needed with the linux impl of libusb. Different behaviour between libusb on FreeBSD and linux creates a compatibility problems where linux-maintained programs accessing libusb20_dev_get_port_path() and libusb_get_port_numbers() will fail on FreeBSD but works on linux. (I've just spent some hours with such program) :-) I've looked through the available documentation without finding anything substantial - and hence I do not know which one is right. My previous post stated that libusb20_dev_get_port_path() is available on linux - it is not - libusb_get_port_numbers() is Sorry about that /Uffe ___ 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
