Denny Lin | 21 Sep 17:59 2014
Picon

USB device repeatedly disconnected

Hi,

I have a Texas Instruments OMAP4440 connected via a USB cable to my
laptop running FreeBSD 10.0-RELEASE amd64.

This is the output of usbconfig -d 1.7 dump_device_desc:
ugen1.7: <OMAP4440 Texas Instruments> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (100mA)

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0210 
  bDeviceClass = 0x00ff 
  bDeviceSubClass = 0x00ff 
  bDeviceProtocol = 0x00ff 
  bMaxPacketSize0 = 0x0040 
  idVendor = 0x0451 
  idProduct = 0xd010 
  bcdDevice = 0x0000 
  iManufacturer = 0x0021  <Texas Instruments>
  iProduct = 0x0025  <OMAP4440>
  iSerialNumber = 0x0000  <no string>
  bNumConfigurations = 0x0001

For some reason, it repeatedly disconnects:
ugen1.7: <Texas Instruments> at usbus1 (disconnected)
ugen1.7: <Texas Instruments> at usbus1
ugen1.7: <Texas Instruments> at usbus1 (disconnected)
ugen1.7: <Texas Instruments> at usbus1
ugen1.7: <Texas Instruments> at usbus1 (disconnected)
ugen1.7: <Texas Instruments> at usbus1
(Continue reading)

Huang Wen Hui | 20 Sep 14:03 2014
Picon

xhci problem on UEFI boot MacBookPro 11,3

I try to UEFI boot 10-STABLE on MacBookPro 11,3, found that xhci does not
work anymore, It works in BIOS boot.
also try to set "hw.usb.xhci.msi=0" and hw.usb.xhci.xhci_port_route="-1",
no lucky.
verbose boot log can be found at :
http://sw.gddsn.org.cn/freebsd/uefi-messages.txt
usbconfig list show:
ugen0.1: <XHCI root HUB 0x8086> at usbus0, cfg=0 md=HOST spd=SUPER
(5.0Gbps) pwr=SAVE (0mA)

In BIOS boot, usbconfig list show:

ugen0.1: <XHCI root HUB 0x8086> at usbus0, cfg=0 md=HOST spd=SUPER
(5.0Gbps) pwr=SAVE (0mA)
ugen0.2: <BRCM20702 Hub Apple Inc.> at usbus0, cfg=0 md=HOST spd=FULL
(12Mbps) pwr=SAVE (94mA)
ugen0.3: <product 0x820a vendor 0x05ac> at usbus0, cfg=0 md=HOST spd=FULL
(12Mbps) pwr=ON (0mA)
ugen0.4: <product 0x820b vendor 0x05ac> at usbus0, cfg=0 md=HOST spd=FULL
(12Mbps) pwr=ON (0mA)
ugen0.5: <Bluetooth USB Host Controller Apple Inc.> at usbus0, cfg=0
md=HOST spd=FULL (12Mbps) pwr=ON (0mA)
ugen0.6: <Apple Internal Keyboard  Trackpad Apple Inc.> at usbus0, cfg=0
md=HOST spd=FULL (12Mbps) pwr=ON (40mA)
ugen0.7: <Card Reader Apple> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps)
pwr=ON (224mA)

Cheers,
Huang Wen Hui
(Continue reading)

bugzilla-noreply | 19 Sep 17:59 2014
Picon

[Bug 193775] New: [kernel/usb/u3g] GOBI2000/HP_UN2420 WWAN/GPS identification numbers

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193775

            Bug ID: 193775
           Summary: [kernel/usb/u3g] GOBI2000/HP_UN2420 WWAN/GPS
                    identification numbers
           Product: Base System
           Version: 10.0-RELEASE
          Hardware: Any
                OS: Any
            Status: Needs Triage
          Severity: Affects Many People
          Priority: ---
         Component: usb
          Assignee: freebsd-usb <at> FreeBSD.org
          Reporter: cederom <at> tlen.pl

Created attachment 147468
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=147468&action=edit
u3g.c and usbdevs patch

Adds recognition of GOBI2000/HP_UN2420 WWAN/GPS device by U3G kernel module.

--

-- 
You are receiving this mail because:
You are the assignee for the bug.
bugzilla-noreply | 19 Sep 11:59 2014
Picon

Problem reports for freebsd-usb <at> FreeBSD.org that need special attention

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status          |    Bug Id | Description
----------------+-----------+-------------------------------------------------
Needs MFC       |    193279 | Corsair K70 Gaming Keyboard will not function o 

1 problems total for which you should take action.
Ross Penner | 17 Sep 19:58 2014

USB ethernet adapter support

The following is a discussion I had on the freebsd-questions list. I've
decided to take the route of buying an adapter that works on FreeBSD 10
Release but, on suggestion, I thought I would ask on these lists if
there was anywhere I could mail my useless (to me) adapter so support
could be added.

----- Original message -----
From: Ross Penner <rossp <at> f-m.fm>
To: Roland Smith <rsmith <at> xs4all.nl>
Cc: freebsd-questions <at> freebsd.org
Subject: Re: USB ethernet adapter support
Date: Sun, 07 Sep 2014 15:06:05 -0700

On Sat, 30 Aug 2014, at 02:23 AM, Roland Smith wrote:
> On Fri, Aug 29, 2014 at 11:34:02PM -0700, Ross Penner wrote:
> > I have a USB ethernet adapter that doesn't seem to work out of the box
> > on my 10.0 system. I'm hoping somebody can help me figure out what
> > driver to load, or if there even is a driver available.
> > 
> > When I plug the device into the FreeBSD machine the only line on dmesg
> > is:
> > ugen4.2: <Linksys> at usbus4
> > 
> > It does work with my Ubuntu 14.04 system. I've added the dmesg output in
> > the hopes that it will be helpful:
> > [137513.415146] usb 1-1.5: new high-speed USB device number 6 using
> > ehci-pci
> > [137513.508489] usb 1-1.5: New USB device found, idVendor=13b1,
> > idProduct=0041
> > [137513.508493] usb 1-1.5: New USB device strings: Mfr=1, Product=2,
(Continue reading)

bugzilla-noreply | 16 Sep 21:24 2014
Picon

[Bug 156596] [ehci] Extremely high interrupt rate on ehci/uhci IRQ16 80% cpu utilization on CPU0

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=156596

bt <at> brandonthomson.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bt <at> brandonthomson.com

--- Comment #12 from bt <at> brandonthomson.com ---
Confirmed on this motherboard: Intel BOXDH61BEB3

As a temporary workaround, I found removing ehci from the kernel works
splendidly. Idle power consumption dropped from 41 watts to 28 watts.

--

-- 
You are receiving this mail because:
You are the assignee for the bug.
Vitaly Magerya | 15 Sep 13:43 2014
Picon

How to obtain the "ugen" that corresponds to an "ums", "uep" or "uhid"?

Hi, folks. Is there a way to obtain the name of an ugen device that
corresponds to a particular ums/uep/uhid device?

The situation I'm working with is this: there's a (custom) DEVD
rule that executes a script when any new "ums" or "uhid" device is
created. This script has access to the device name (and any other
info DEVD provides), and needs to figure out manufacturer name,
product name and ID numbers of this device. To do that, it parses
the output of this command:

     usbconfig -d ugen<unit>.<address> dump_device_desc

The question is how should the script obtain these <unit> and
<address> numbers?

Now, when a new device is attached DEVD receives a message like this:

     +uhid0 at bus=1 hubaddr=1 port=3 devaddr=2 interface=0
     vendor=0x0079 product=0x0011 devclass=0x00 devsubclass=0x00
     sernum="" release=0x0106 mode=host intclass=0x03 intsubclass=0x00
     intprotocol=0x00  on uhub0

     (The correct ugen for this device happens to be ugen3.2).

... or a message like this:

     +ums0 at bus=0 hubaddr=2 port=2 devaddr=3 interface=1
     vendor=0x046d product=0xc52b devclass=0x00 devsubclass=0x00
     sernum="" release=0x1201 mode=host intclass=0x03 intsubclass=0x01
     intprotocol=0x02  on uhub3
(Continue reading)

Lundberg, Johannes | 13 Sep 14:04 2014
Picon

libusb and non-root access problem

Hi

I tried now for hours but no luck with this.. I have a special usb device
to which I connect with libusb. Everything works find as root but I can
seem to be able to access with normal user no matter how I configure devfs.

I changed both conf and rules and even set myself as owner and group and
777 permission to /dev/ugen* /dev/usb and /dev/usb/* but no luck...

I can connect to the device and claim interface but then it fails at the
first libusb_control_transfer with error -4

I have done this before without problems. I am running the newest
11-CURRENT snapshot so could there be any bug that causes this or has
anything changed in configurations?

Grateful for any advice...
--
Johannes Lundberg

--

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
秘密保持について:この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。
もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、
複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。
---
CONFIDENTIALITY NOTE: The information in this email is confidential
and intended solely for the addressee.
Disclosure, copying, distribution or any other action of use of this
email by person other than intended recipient, is prohibited.
(Continue reading)

Andriy Gapon | 12 Sep 19:53 2014
Picon

usb printer vs cups


From my experience I think that cupsd executes backend tools with all uids and
gids set to cups and no supplementary groups.  In the case of USB printers the
backends need to access /dev/usbctl and /dev/usb/foobar that corresponds to a
printer.  That means that the access to those devices must be somehow granted to
cups:cups.
How do people solve this?  What kind of permissions / configuration do you use?

P.S.
Maybe I over-generalized the issue to all USB printers.  My personal experience
is with an HP printer handled by hplip / hplip-plugin.
-- 
Andriy Gapon

From my experience I think that cupsd executes backend tools with all uids and
gids set to cups and no supplementary groups.  In the case of USB printers the
backends need to access /dev/usbctl and /dev/usb/foobar that corresponds to a
printer.  That means that the access to those devices must be somehow granted to
cups:cups.
How do people solve this?  What kind of permissions / configuration do you use?

P.S.
Maybe I over-generalized the issue to all USB printers.  My personal experience
is with an HP printer handled by hplip / hplip-plugin.
--

-- 
Andriy Gapon
bugzilla-noreply | 10 Sep 05:32 2014
Picon

[Bug 175731] detaching USB keyboard freezes other USB keyboards

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=175731

Henry Hu <henry.hu.sh <at> gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |henry.hu.sh <at> gmail.com

--- Comment #8 from hselasky <at> c2i.net ---
On Thursday 14 February 2013 10:20:02 Norbert Koch wrote:
> The following reply was made to PR usb/175731; it has been noted by GNATS.
> 
> From: Norbert Koch <nkoch <at> demig.de>
> To: hselasky <at> c2i.net
> Cc: freebsd-usb <at> freebsd.org, bug-followup <at> freebsd.org, imp <at> freebsd.org
> Subject: Re: usb/175731: detaching USB keyboard freezes other USB keyboards
> Date: Thu, 14 Feb 2013 10:19:05 +0100
> 
>  Am 07.02.2013 22:26, schrieb Hans Petter Selasky:
>  > On Thursday 07 February 2013 13:10:01 Norbert Koch wrote:
>  >> The following reply was made to PR usb/175731; it has been noted by
>  >> GNATS.
>  >> 
>  >> From: Norbert Koch <nkoch <at> demig.de>
>  >> To: bug-followup <at> FreeBSD.org
>  >> Cc:
>  >> Subject: Re: usb/175731: detaching USB keyboard freezes other USB
>  >> keyboards Date: Thu, 07 Feb 2013 13:01:01 +0100
>  >> 
>  >>  Same problem with FreeBSD-9.1-RELEASE.
(Continue reading)

bugzilla-noreply | 3 Sep 13:32 2014
Picon

[Bug 193279] New: Corsair K70 Gaming Keyboard will not function on boot

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193279

            Bug ID: 193279
           Summary: Corsair K70 Gaming Keyboard will not function on boot
           Product: Base System
           Version: 9.0-STABLE
          Hardware: amd64
                OS: Any
            Status: Needs Triage
          Severity: Affects Only Me
          Priority: ---
         Component: usb
          Assignee: freebsd-usb <at> FreeBSD.org
          Reporter: luke <at> foolishgames.com

The Corsair K70 keyboard has the same issue as a K60 and requires a USB quirk
to function  under FreeBSD.  Without the quirk, the keyboard detects in dmesg,
but does not actually take input.  

These additions to usbdevs and usb_quirks.c seemed to fix it much like the
change for the K60.   

product CORSAIR K70             0x1b09  Corsair Vengeance K70 keyboard

 USB_QUIRK(CORSAIR, K70, 0x0000, 0xffff, UQ_KBD_BOOTPROTO),

--

-- 
You are receiving this mail because:
You are the assignee for the bug.
(Continue reading)


Gmane