Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

freebsd-usb Digest, Vol 270, Issue 2

0 views

Skip to first unread message

freebsd-u...@freebsd.org

unread,

Jan 10, 2010, 6:54:06 AM1/10/10

to freeb...@freebsd.org

Send freebsd-usb mailing list submissions to
freeb...@freebsd.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
or, via email, send a message with subject or body 'help' to
freebsd-u...@freebsd.org

You can reach the person managing the list at
freebsd-...@freebsd.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-usb digest..."

Today's Topics:

1. Re: Getting a scanner to work with new usb stack? (Warren Block)
2. Utility to Suspend/Disable/Enable Power Off USB ports (jerry)
3. Re: Utility to Suspend/Disable/Enable Power Off USB ports
(Hans Petter Selasky)
4. Re: kern/141011: [usb] Encrypted root, geli password at boot;
enter key never released (p...@FreeBSD.org)
5. Re: kern/141011: [usb] Encrypted root, geli password at boot;
enter key never released (Hans Petter Selasky)
6. Re: kern/141011: [usb] Encrypted root, geli password at boot;
enter key never released (Hans Petter Selasky)
7. usb/142387: Netgear WPN111 not recognised by uath(4) after
uathload (Andrew)
8. Re: usb/142387: Netgear WPN111 not recognised by uath(4)
after uathload (Hans Petter Selasky)
9. Re: usb/142387: Netgear WPN111 not recognised by uath(4)
after uathload (Hans Petter Selasky)
10. Re: usb/142225: [patch] Patch to add Quirk for Western
Digital Mybook (tho...@FreeBSD.org)
11. Re: usb/142228: [usbdevs] [patch] add a USB-HDD to
usb_quirk.c and usbdevs (tho...@FreeBSD.org)
12. Re: libusb-config missing? (Daniel O'Connor)
13. Re: usb/142387: Netgear WPN111 not recognised by uath(4)
after uathload (Hans Petter Selasky)
14. Re: usb/142387: Netgear WPN111 not recognised by uath(4)
after uathload (Hans Petter Selasky)
15. Re: usb/142387: Netgear WPN111 not recognised by uath(4)
after uathload (Andrew)
16. Re: usb/142387: Netgear WPN111 not recognised by uath(4)
after uathload (Andrew)
17. Re: usb/142387: Netgear WPN111 not recognised by uath(4)
after uathload (Andrew)
18. Re: usb/142387: Netgear WPN111 not recognised by uath(4)
after uathload (Andrew)
19. usb/142427: EDIMAX EW7318USG should be added to usbdevs
(Yury Michurin)
20. Re: usb/142427: EDIMAX EW7318USG should be added to usbdevs
(Hans Petter Selasky)
21. Re: usb/142427: EDIMAX EW7318USG should be added to usbdevs
(Hans Petter Selasky)
22. problem USB wireless keyboard and mouse (tkor...@aim.com)
23. Re: problem USB wireless keyboard and mouse (Hans Petter Selasky)
24. Re: kern/141011: [usb] Encrypted root, geli password at boot;
enter key never released (Wiktor Niesiobedzki)
25. Re: Re: kern/141011: [usb] Encrypted root, geli password at
boot; enter key never release (Wiktor Niesiobedzki)
26. FreeBSD 8.0 and HPLIP - you also need execute permissions on
/dev/usb (Torfinn Ingolfsen)
27. Re: kern/141011: [usb] Encrypted root, geli password at boot;
enter key never release (Hans Petter Selasky)
28. Re: Calling for testers if_run rt3572 support
(Hans Petter Selasky)

----------------------------------------------------------------------

Message: 1
Date: Mon, 4 Jan 2010 09:38:21 -0700 (MST)
From: Warren Block <wbl...@wonkity.com>
Subject: Re: Getting a scanner to work with new usb stack?
To: Andrew Reilly <are...@bigpond.net.au>
Cc: freeb...@freebsd.org
Message-ID: <alpine.BSF.2.00.1...@wonkity.com>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

On Mon, 4 Jan 2010, Andrew Reilly wrote:

> For many years I've been happily (if only occasionally)
> using an AGFA Snapscan e20 flat-bed USB scanner, using
> xsane. This scanner (apparently) requires a "firmware
> upload", which I had managed to arrange with this
> line in /usr/local/etc/sane.d/snapscan.conf:
> firmware /usr/local/share/sane/snapscan/snape20.bin
>
> I don't know whether or not that is (or is related to) the
> problem, but it isn't working any more, and I've run out of
> ideas to try, so thought I'd ask here.
>
> sane-find-scanner finds:
> found USB scanner (vendor=0x06bd [AGFA ], product=0x2091 [SNAPSCAN]) at libusb:/dev/usb:/dev/ugen0.3
> # Your USB scanner was (probably) detected. It may or may not be supported by
> # SANE. Try scanimage -L and read the backend's manpage.
>
> But no amount of scanimage -d spellings or SANE_DEFAULT_DEVICE
> tweaking seems to make scanimage or xsane happy.
> ("snapscan:/dev/uscanner0" used to be what I used.)
>
> For what it's worth, I'm running -current as of Saturday, and my
> dmesg.boot says:
> ugen0.3: <AGFA> at usbus0

snapscan.conf should have

usb /dev/ugen0.3

(snapscan:libusb:/dev/usb:/dev/ugen0.3 from the command line, I think.)

Need new 0660 permissions to ugen0.3 (or ugen*, or usb/*) in
devfs.rules, too.

-Warren Block * Rapid City, South Dakota USA

------------------------------

Message: 2
Date: Wed, 06 Jan 2010 10:18:32 +0800
From: jerry <fre...@gmail.com>
Subject: Utility to Suspend/Disable/Enable Power Off USB ports
To: freeb...@freebsd.org
Message-ID: <4B43F2F8...@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed

Hi,
I am very happy to run "upower" on my laptop installed freebsd 7.2.
But can you make upower run on freebsd8?
Thank you!

------------------------------

Message: 3
Date: Wed, 6 Jan 2010 09:27:59 +0100
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: Utility to Suspend/Disable/Enable Power Off USB ports
To: freeb...@freebsd.org
Cc: jerry <fre...@gmail.com>
Message-ID: <201001060927....@c2i.net>
Content-Type: Text/Plain; charset="utf-8"

On Wednesday 06 January 2010 03:18:32 jerry wrote:
> Hi,
> I am very happy to run "upower" on my laptop installed freebsd 7.2.
> But can you make upower run on freebsd8?
> Thank you!

usbconfig -h

--HPS

------------------------------

Message: 4
Date: Wed, 6 Jan 2010 14:06:11 GMT
From: p...@FreeBSD.org
Subject: Re: kern/141011: [usb] Encrypted root, geli password at boot;
enter key never released
To: p...@FreeBSD.org, freebs...@FreeBSD.org, freeb...@FreeBSD.org
Message-ID: <201001061406....@freefall.freebsd.org>

Old Synopsis: [geli] Encrypted root, geli password at boot; enter key never released
New Synopsis: [usb] Encrypted root, geli password at boot; enter key never released

Responsible-Changed-From-To: freebsd-geom->freebsd-usb
Responsible-Changed-By: pjd
Responsible-Changed-When: śro 6 sty 2010 14:04:41 UTC
Responsible-Changed-Why:
The problem is more related to USB and ukbd than to GEOM or GELI.

http://www.freebsd.org/cgi/query-pr.cgi?pr=141011

------------------------------

Message: 5
Date: Wed, 6 Jan 2010 19:47:47 +0100
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: kern/141011: [usb] Encrypted root, geli password at boot;
enter key never released
To: freeb...@freebsd.org
Message-ID: <201001061947....@c2i.net>
Content-Type: Text/Plain; charset="iso-8859-15"

On Wednesday 06 January 2010 19:45:38 Hans Petter Selasky wrote:
> On Wednesday 06 January 2010 18:50:41 Pawel Jakub Dawidek wrote:
> > On Wed, Jan 06, 2010 at 03:21:03PM +0100, Hans Petter Selasky wrote:
> > > > Old Synopsis: [geli] Encrypted root, geli password at boot; enter key
> > > > never released New Synopsis: [usb] Encrypted root, geli password at
> > > > boot; enter key never released
> > >

Hi,

Could you try to comment it out:

/* read and discard the input, no one is waiting for it
*/ do {
c = ukbd_read_char(&sc->sc_kbd, 0);
} while (c != NOKEY);

In "ukbd_interrupt()" in "src/sys/dev/usb/input/ukbd.c" ?

--HPS

------------------------------

Message: 6
Date: Wed, 6 Jan 2010 19:50:04 GMT
From: Hans Petter Selasky <hsel...@freebsd.org>
Subject: Re: kern/141011: [usb] Encrypted root, geli password at boot;
enter key never released
To: freeb...@FreeBSD.org
Message-ID: <201001061950....@freefall.freebsd.org>

The following reply was made to PR kern/141011; it has been noted by GNATS.

From: Hans Petter Selasky <hsel...@freebsd.org>
To: freebsd-gn...@freebsd.org
Cc:
Subject: Re: kern/141011: [usb] Encrypted root, geli password at boot; enter key never released
Date: Wed, 6 Jan 2010 19:45:38 +0100

On Wednesday 06 January 2010 18:50:41 Pawel Jakub Dawidek wrote:
> On Wed, Jan 06, 2010 at 03:21:03PM +0100, Hans Petter Selasky wrote:

> > > Old Synopsis: [geli] Encrypted root, geli password at boot; enter key
> > > never released New Synopsis: [usb] Encrypted root, geli password at
> > > boot; enter key never released
> >
> > Hi,
> >
> > Could you try to comment out:
> >
> > /* read and discard the input, no one is waiting for it
> > */ do {
> > c = ukbd_read_char(&sc->sc_kbd, 0);
> > } while (c != NOKEY);
> >
> > In "ukbd_interrupt()" in "src/sys/dev/usb/input/ukbd.c" ?
>

--HPS

------------------------------

Message: 7
Date: Wed, 6 Jan 2010 20:26:03 GMT
From: Andrew <and...@flarn.com>
Subject: usb/142387: Netgear WPN111 not recognised by uath(4) after
uathload
To: freebsd-gn...@FreeBSD.org
Message-ID: <201001062026....@www.freebsd.org>

>Number: 142387
>Category: usb
>Synopsis: Netgear WPN111 not recognised by uath(4) after uathload
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-usb
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Wed Jan 06 20:30:06 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Andrew
>Release: 8-STABLE
>Organization:
>Environment:
FreeBSD XXXXXX 8.0-STABLE FreeBSD 8.0-STABLE #2: Tue Jan 5 21:34:37 GMT 2010 root@XXXXXX:/usr/obj/usr/src/sys/GENERIC amd64

>Description:
After running uathload the device changes from:
ugen3.2: <WPN111 Atheros Communications Inc> at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON

bLength = 0x0012
bDescriptorType = 0x0001
bcdUSB = 0x0200
bDeviceClass = 0x00ff
bDeviceSubClass = 0x0000
bDeviceProtocol = 0x0000
bMaxPacketSize0 = 0x0040
idVendor = 0x1385
idProduct = 0x5f01
bcdDevice = 0x0001
iManufacturer = 0x0001 <Atheros Communications Inc>
iProduct = 0x0002 <WPN111>
iSerialNumber = 0x0003 <1.0>
bNumConfigurations = 0x0001
to:
ugen3.2: <WPN111 Atheros Communications Inc> at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON

bLength = 0x0012
bDescriptorType = 0x0001
bcdUSB = 0x0200
bDeviceClass = 0x00ff
bDeviceSubClass = 0x0000
bDeviceProtocol = 0x0000
bMaxPacketSize0 = 0x0040
idVendor = 0x1385
idProduct = 0x5f02
bcdDevice = 0x0001
iManufacturer = 0x0001 <Atheros Communications Inc>
iProduct = 0x0002 <WPN111>
iSerialNumber = 0x0003 <1.0>
bNumConfigurations = 0x0001

Note: idProduct 0x5f01 -> 0x5f02 rather than 0x5f00
>How-To-Repeat:
Connect a Netgear WPN111, run uathload -d /dev/ugenX.X

>Fix:
Correct sys/dev/usb/usbdevs product id for WPN111 with firmware, patch attached.

uath now attachs:

dmesg:
ugen3.2: <Atheros Communications Inc> at usbus3 (disconnected)
ugen3.2: <Atheros Communications Inc> at usbus3
uath0: <Atheros Communications Inc WPN111, rev 2.00/0.01, addr 2> on usbus3

ifconfig uath0
uath0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 2290
ether 00:14:6c:ea:81:a4
media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
status: no carrier

Patch attached with submission follows:

--- usbdevs.orig 2010-01-06 20:15:02.000000000 +0000
+++ usbdevs 2010-01-05 21:28:03.000000000 +0000
@@ -2005,8 +2005,8 @@
product NETGEAR2 MA101B 0x4102 MA101 Rev B
product NETGEAR3 WG111T 0x4250 WG111T
product NETGEAR3 WG111T_NF 0x4251 WG111T (no firmware)
-product NETGEAR3 WPN111 0x5f00 WPN111
product NETGEAR3 WPN111_NF 0x5f01 WPN111 (no firmware)
+product NETGEAR3 WPN111 0x5f02 WPN111

/* Nikon products */
product NIKON E990 0x0102 Digital Camera E990

>Release-Note:
>Audit-Trail:
>Unformatted:

------------------------------

Message: 8
Date: Wed, 6 Jan 2010 21:43:56 +0100
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/142387: Netgear WPN111 not recognised by uath(4)
after uathload
To: freeb...@freebsd.org
Cc: Andrew <and...@flarn.com>, freebsd-gn...@freebsd.org
Message-ID: <201001062143....@c2i.net>
Content-Type: Text/Plain; charset="iso-8859-15"

On Wednesday 06 January 2010 21:26:03 Andrew wrote:
> >Number: 142387
> >Category: usb
> >Synopsis: Netgear WPN111 not recognised by uath(4) after uathload
> >Confidential: no
> >Severity: non-critical
> >Priority: low
> >Responsible: freebsd-usb
> >State: open
> >Quarter:
> >Keywords:
> >Date-Required:
> >Class: sw-bug
> >Submitter-Id: current-users
> >Arrival-Date: Wed Jan 06 20:30:06 UTC 2010
> >Closed-Date:
> >Last-Modified:
> >Originator: Andrew
> >Release: 8-STABLE
> >Organization:
> >Environment:
>
> FreeBSD XXXXXX 8.0-STABLE FreeBSD 8.0-STABLE #2: Tue Jan 5 21:34:37 GMT
> 2010 root@XXXXXX:/usr/obj/usr/src/sys/GENERIC amd64
>
> >Description:
>
> After running uathload the device changes from:
> ugen3.2: <WPN111 Atheros Communications Inc> at usbus3, cfg=0 md=HOST
> spd=HIGH (480Mbps) pwr=ON
>
> bLength = 0x0012
> bDescriptorType = 0x0001
> bcdUSB = 0x0200
> bDeviceClass = 0x00ff
> bDeviceSubClass = 0x0000
> bDeviceProtocol = 0x0000
> bMaxPacketSize0 = 0x0040
> idVendor = 0x1385
> idProduct = 0x5f01
> bcdDevice = 0x0001
> iManufacturer = 0x0001 <Atheros Communications Inc>
> iProduct = 0x0002 <WPN111>
> iSerialNumber = 0x0003 <1.0>
> bNumConfigurations = 0x0001
> to:
> ugen3.2: <WPN111 Atheros Communications Inc> at usbus3, cfg=0 md=HOST
> spd=HIGH (480Mbps) pwr=ON
>
> bLength = 0x0012
> bDescriptorType = 0x0001
> bcdUSB = 0x0200
> bDeviceClass = 0x00ff
> bDeviceSubClass = 0x0000
> bDeviceProtocol = 0x0000
> bMaxPacketSize0 = 0x0040
> idVendor = 0x1385
> idProduct = 0x5f02
> bcdDevice = 0x0001
> iManufacturer = 0x0001 <Atheros Communications Inc>
> iProduct = 0x0002 <WPN111>
> iSerialNumber = 0x0003 <1.0>
> bNumConfigurations = 0x0001
>
> Note: idProduct 0x5f01 -> 0x5f02 rather than 0x5f00
>
> >How-To-Repeat:
>
> Connect a Netgear WPN111, run uathload -d /dev/ugenX.X
>
> >Fix:
>
> Correct sys/dev/usb/usbdevs product id for WPN111 with firmware, patch
> attached.
>
> uath now attachs:
>
> dmesg:
> ugen3.2: <Atheros Communications Inc> at usbus3 (disconnected)
> ugen3.2: <Atheros Communications Inc> at usbus3
> uath0: <Atheros Communications Inc WPN111, rev 2.00/0.01, addr 2> on usbus3
>
>
> ifconfig uath0
> uath0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 2290
> ether 00:14:6c:ea:81:a4
> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
> status: no carrier
>
>
> Patch attached with submission follows:
>
> --- usbdevs.orig 2010-01-06 20:15:02.000000000 +0000
> +++ usbdevs 2010-01-05 21:28:03.000000000 +0000
> @@ -2005,8 +2005,8 @@
> product NETGEAR2 MA101B 0x4102 MA101 Rev B
> product NETGEAR3 WG111T 0x4250 WG111T
> product NETGEAR3 WG111T_NF 0x4251 WG111T (no firmware)
> -product NETGEAR3 WPN111 0x5f00 WPN111
> product NETGEAR3 WPN111_NF 0x5f01 WPN111 (no firmware)
> +product NETGEAR3 WPN111 0x5f02 WPN111
>
> /* Nikon products */
> product NIKON E990 0x0102 Digital Camera E990
>
> >Release-Note:
> >Audit-Trail:
> >Unformatted:

Hi,

Are you certain that product "0x5f00" is incorrect and that we shouldn't add
the new product, 0x5f02 instead?

--HPS

------------------------------

Message: 9
Date: Wed, 6 Jan 2010 20:50:09 GMT
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/142387: Netgear WPN111 not recognised by uath(4)
after uathload
To: freeb...@FreeBSD.org
Message-ID: <201001062050....@freefall.freebsd.org>

The following reply was made to PR usb/142387; it has been noted by GNATS.

From: Hans Petter Selasky <hsel...@c2i.net>
To: freeb...@freebsd.org
Cc: Andrew <and...@flarn.com>,
freebsd-gn...@freebsd.org
Subject: Re: usb/142387: Netgear WPN111 not recognised by uath(4) after uathload
Date: Wed, 6 Jan 2010 21:43:56 +0100

------------------------------

Message: 10
Date: Thu, 7 Jan 2010 00:34:18 GMT
From: tho...@FreeBSD.org
Subject: Re: usb/142225: [patch] Patch to add Quirk for Western
Digital Mybook
To: thoma...@fastmail.fm, tho...@FreeBSD.org,
freeb...@FreeBSD.org, tho...@FreeBSD.org
Message-ID: <201001070034....@freefall.freebsd.org>

Synopsis: [patch] Patch to add Quirk for Western Digital Mybook

State-Changed-From-To: open->patched
State-Changed-By: thompsa
State-Changed-When: Thu Jan 7 00:33:22 UTC 2010
State-Changed-Why:
Committed, thanks!

Responsible-Changed-From-To: freebsd-usb->thompsa
Responsible-Changed-By: thompsa
Responsible-Changed-When: Thu Jan 7 00:33:22 UTC 2010
Responsible-Changed-Why:
Committed, thanks!

http://www.freebsd.org/cgi/query-pr.cgi?pr=142225

------------------------------

Message: 11
Date: Thu, 7 Jan 2010 00:35:14 GMT
From: tho...@FreeBSD.org
Subject: Re: usb/142228: [usbdevs] [patch] add a USB-HDD to
usb_quirk.c and usbdevs
To: go...@on-link.jp, tho...@FreeBSD.org, freeb...@FreeBSD.org,
tho...@FreeBSD.org
Message-ID: <201001070035....@freefall.freebsd.org>

Synopsis: [usbdevs] [patch] add a USB-HDD to usb_quirk.c and usbdevs

State-Changed-From-To: open->patched
State-Changed-By: thompsa
State-Changed-When: Thu Jan 7 00:34:37 UTC 2010
State-Changed-Why:
Committed, thanks!

Responsible-Changed-From-To: freebsd-usb->thompsa
Responsible-Changed-By: thompsa
Responsible-Changed-When: Thu Jan 7 00:34:37 UTC 2010
Responsible-Changed-Why:
Committed, thanks!

http://www.freebsd.org/cgi/query-pr.cgi?pr=142228

------------------------------

Message: 12
Date: Thu, 7 Jan 2010 14:54:45 +1030
From: "Daniel O'Connor" <doco...@gsoft.com.au>
Subject: Re: libusb-config missing?
To: Hans Petter Selasky <hsel...@c2i.net>
Cc: freeb...@freebsd.org
Message-ID: <201001071454....@gsoft.com.au>
Content-Type: text/plain; charset="iso-8859-15"

Skipped content of type multipart/mixed-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: This is a digitally signed message part.
Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20100107/abbf43be/attachment-0001.pgp

------------------------------

Message: 13
Date: Thu, 7 Jan 2010 10:51:24 +0100
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/142387: Netgear WPN111 not recognised by uath(4)
after uathload
To: Andrew <and...@flarn.com>
Cc: freebsd-gn...@freebsd.org, freeb...@freebsd.org
Message-ID: <201001071051....@c2i.net>
Content-Type: Text/Plain; charset="iso-8859-1"

On Thursday 07 January 2010 10:32:06 Andrew wrote:
> 2010/1/6 Hans Petter Selasky <hsel...@c2i.net>:
> > On Wednesday 06 January 2010 21:26:03 Andrew wrote:
> >> >Number: 142387
> >> >Category: usb
> >> >Synopsis: Netgear WPN111 not recognised by uath(4) after uathload
> >> >Confidential: no
> >> >Severity: non-critical
> >> >Priority: low
> >> >Responsible: freebsd-usb
> >> >State: open
> >> >Quarter:
> >> >Keywords:
> >> >Date-Required:
> >> >Class: sw-bug
> >> >Submitter-Id: current-users
> >> >Arrival-Date: Wed Jan 06 20:30:06 UTC 2010
> >> >Closed-Date:
> >> >Last-Modified:
> >> >Originator: Andrew
> >> >Release: 8-STABLE
> >> >Organization:
> >> >Environment:
> >>
> >> FreeBSD XXXXXX 8.0-STABLE FreeBSD 8.0-STABLE #2: Tue Jan 5 21:34:37 GMT
> >> 2010 root@XXXXXX:/usr/obj/usr/src/sys/GENERIC amd64
> >>
> >> >Description:
> >>
> >> After running uathload the device changes from:
> >> ugen3.2: <WPN111 Atheros Communications Inc> at usbus3, cfg=0 md=HOST
> >> spd=HIGH (480Mbps) pwr=ON
> >>
> >> bLength = 0x0012
> >> bDescriptorType = 0x0001
> >> bcdUSB = 0x0200
> >> bDeviceClass = 0x00ff
> >> bDeviceSubClass = 0x0000
> >> bDeviceProtocol = 0x0000
> >> bMaxPacketSize0 = 0x0040
> >> idVendor = 0x1385
> >> idProduct = 0x5f01
> >> bcdDevice = 0x0001
> >> iManufacturer = 0x0001 <Atheros Communications Inc>
> >> iProduct = 0x0002 <WPN111>
> >> iSerialNumber = 0x0003 <1.0>
> >> bNumConfigurations = 0x0001
> >> to:
> >> ugen3.2: <WPN111 Atheros Communications Inc> at usbus3, cfg=0 md=HOST
> >> spd=HIGH (480Mbps) pwr=ON
> >>
> >> bLength = 0x0012
> >> bDescriptorType = 0x0001
> >> bcdUSB = 0x0200
> >> bDeviceClass = 0x00ff
> >> bDeviceSubClass = 0x0000
> >> bDeviceProtocol = 0x0000
> >> bMaxPacketSize0 = 0x0040
> >> idVendor = 0x1385
> >> idProduct = 0x5f02
> >> bcdDevice = 0x0001
> >> iManufacturer = 0x0001 <Atheros Communications Inc>
> >> iProduct = 0x0002 <WPN111>
> >> iSerialNumber = 0x0003 <1.0>
> >> bNumConfigurations = 0x0001
> >>
> >> Note: idProduct 0x5f01 -> 0x5f02 rather than 0x5f00
> >>
> >> >How-To-Repeat:
> >>
> >> Connect a Netgear WPN111, run uathload -d /dev/ugenX.X
> >>
> >> >Fix:
> >>
> >> Correct sys/dev/usb/usbdevs product id for WPN111 with firmware, patch
> >> attached.
> >>
> >> uath now attachs:
> >>
> >> dmesg:
> >> ugen3.2: <Atheros Communications Inc> at usbus3 (disconnected)
> >> ugen3.2: <Atheros Communications Inc> at usbus3
> >> uath0: <Atheros Communications Inc WPN111, rev 2.00/0.01, addr 2> on
> >> usbus3
> >>
> >>
> >> ifconfig uath0
> >> uath0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 2290
> >> ether 00:14:6c:ea:81:a4
> >> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
> >> status: no carrier
> >>
> >>
> >> Patch attached with submission follows:
> >>
> >> --- usbdevs.orig 2010-01-06 20:15:02.000000000 +0000
> >> +++ usbdevs 2010-01-05 21:28:03.000000000 +0000
> >> @@ -2005,8 +2005,8 @@
> >> product NETGEAR2 MA101B 0x4102 MA101 Rev B
> >> product NETGEAR3 WG111T 0x4250 WG111T
> >> product NETGEAR3 WG111T_NF 0x4251 WG111T (no firmware)
> >> -product NETGEAR3 WPN111 0x5f00 WPN111
> >> product NETGEAR3 WPN111_NF 0x5f01 WPN111 (no firmware)
> >> +product NETGEAR3 WPN111 0x5f02 WPN111
> >>
> >> /* Nikon products */
> >> product NIKON E990 0x0102 Digital Camera E990
> >>
> >> >Release-Note:
> >> >Audit-Trail:
> >> >Unformatted:
> >
> > Hi,
> >
> > Are you certain that product "0x5f00" is incorrect and that we shouldn't
> > add the new product, 0x5f02 instead?
>
> I can't be certain no, it was an assumption on my part that the WPN111
> id was incorrect as the WPN111_NF was correct for the device. Adding a
> second id for WPN111 will be enough for my hardware to work.

Could you create a new patch where an USB ID is added and not changed, in the
appropriate files?

--HPS

------------------------------

Message: 14
Date: Thu, 7 Jan 2010 10:00:15 GMT
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/142387: Netgear WPN111 not recognised by uath(4)
after uathload
To: freeb...@FreeBSD.org
Message-ID: <201001071000....@freefall.freebsd.org>

The following reply was made to PR usb/142387; it has been noted by GNATS.

From: Hans Petter Selasky <hsel...@c2i.net>
To: Andrew <and...@flarn.com>
Cc: freeb...@freebsd.org,
freebsd-gn...@freebsd.org
Subject: Re: usb/142387: Netgear WPN111 not recognised by uath(4) after uathload
Date: Thu, 7 Jan 2010 10:51:24 +0100

------------------------------

Message: 15
Date: Thu, 7 Jan 2010 09:32:06 +0000
From: Andrew <and...@flarn.com>
Subject: Re: usb/142387: Netgear WPN111 not recognised by uath(4)
after uathload
To: Hans Petter Selasky <hsel...@c2i.net>
Cc: freebsd-gn...@freebsd.org, freeb...@freebsd.org
Message-ID:
<54854a7a1001070132o729...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

2010/1/6 Hans Petter Selasky <hsel...@c2i.net>:
> On Wednesday 06 January 2010 21:26:03 Andrew wrote:
>> >Number: � � � � 142387
>> >Category: � � � usb
>> >Synopsis: � � � Netgear WPN111 not recognised by uath(4) after uathload
>> >Confidential: � no
>> >Severity: � � � non-critical
>> >Priority: � � � low
>> >Responsible: � �freebsd-usb
>> >State: � � � � �open
>> >Quarter:
>> >Keywords:
>> >Date-Required:
>> >Class: � � � � �sw-bug
>> >Submitter-Id: � current-users
>> >Arrival-Date: � Wed Jan 06 20:30:06 UTC 2010
>> >Closed-Date:
>> >Last-Modified:
>> >Originator: � � Andrew
>> >Release: � � � �8-STABLE
>> >Organization:
>> >Environment:
>>
>> FreeBSD XXXXXX 8.0-STABLE FreeBSD 8.0-STABLE #2: Tue Jan �5 21:34:37 GMT
>> �2010 � � root@XXXXXX:/usr/obj/usr/src/sys/GENERIC �amd64
>>
>> >Description:
>>
>> After running uathload the device changes from:
>> ugen3.2: <WPN111 Atheros Communications Inc> at usbus3, cfg=0 md=HOST
>> �spd=HIGH (480Mbps) pwr=ON
>>
>> � bLength = 0x0012
>> � bDescriptorType = 0x0001
>> � bcdUSB = 0x0200
>> � bDeviceClass = 0x00ff
>> � bDeviceSubClass = 0x0000
>> � bDeviceProtocol = 0x0000
>> � bMaxPacketSize0 = 0x0040
>> � idVendor = 0x1385
>> � idProduct = 0x5f01
>> � bcdDevice = 0x0001
>> � iManufacturer = 0x0001 �<Atheros Communications Inc>
>> � iProduct = 0x0002 �<WPN111>
>> � iSerialNumber = 0x0003 �<1.0>
>> � bNumConfigurations = 0x0001
>> to:
>> ugen3.2: <WPN111 Atheros Communications Inc> at usbus3, cfg=0 md=HOST
>> �spd=HIGH (480Mbps) pwr=ON
>>
>> � bLength = 0x0012
>> � bDescriptorType = 0x0001
>> � bcdUSB = 0x0200
>> � bDeviceClass = 0x00ff
>> � bDeviceSubClass = 0x0000
>> � bDeviceProtocol = 0x0000
>> � bMaxPacketSize0 = 0x0040
>> � idVendor = 0x1385
>> � idProduct = 0x5f02
>> � bcdDevice = 0x0001
>> � iManufacturer = 0x0001 �<Atheros Communications Inc>
>> � iProduct = 0x0002 �<WPN111>
>> � iSerialNumber = 0x0003 �<1.0>
>> � bNumConfigurations = 0x0001
>>
>> Note: idProduct 0x5f01 -> 0x5f02 rather than 0x5f00
>>
>> >How-To-Repeat:
>>
>> Connect a Netgear WPN111, run uathload -d /dev/ugenX.X
>>
>> >Fix:
>>
>> Correct sys/dev/usb/usbdevs product id for WPN111 with firmware, patch
>> �attached.
>>
>> uath now attachs:
>>
>> dmesg:
>> ugen3.2: <Atheros Communications Inc> at usbus3 (disconnected)
>> ugen3.2: <Atheros Communications Inc> at usbus3
>> uath0: <Atheros Communications Inc WPN111, rev 2.00/0.01, addr 2> on usbus3
>>
>>
>> ifconfig uath0
>> uath0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 2290
>> � � � � ether 00:14:6c:ea:81:a4
>> � � � � media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
>> � � � � status: no carrier
>>
>>
>> Patch attached with submission follows:
>>
>> --- usbdevs.orig � � �2010-01-06 20:15:02.000000000 +0000
>> +++ usbdevs � 2010-01-05 21:28:03.000000000 +0000
>> @@ -2005,8 +2005,8 @@
>> �product NETGEAR2 MA101B � � � � � � �0x4102 �MA101 Rev B
>> �product NETGEAR3 WG111T � � � � � � �0x4250 �WG111T
>> �product NETGEAR3 WG111T_NF � 0x4251 �WG111T (no firmware)
>> -product NETGEAR3 WPN111 � � � � � � �0x5f00 �WPN111
>> �product NETGEAR3 WPN111_NF � 0x5f01 �WPN111 (no firmware)
>> +product NETGEAR3 WPN111 � � � � � � �0x5f02 �WPN111
>>
>> �/* Nikon products */
>> �product NIKON E990 � � � � � 0x0102 �Digital Camera E990
>>
>> >Release-Note:
>> >Audit-Trail:
>> >Unformatted:
>
> Hi,
>
> Are you certain that product "0x5f00" is incorrect and that we shouldn't add
> the new product, 0x5f02 instead?

I can't be certain no, it was an assumption on my part that the WPN111
id was incorrect as the WPN111_NF was correct for the device. Adding a
second id for WPN111 will be enough for my hardware to work.

Thanks,
Andrew

------------------------------

Message: 16
Date: Thu, 7 Jan 2010 10:10:07 GMT
From: Andrew <and...@flarn.com>
Subject: Re: usb/142387: Netgear WPN111 not recognised by uath(4)
after uathload
To: freeb...@FreeBSD.org
Message-ID: <201001071010....@freefall.freebsd.org>

The following reply was made to PR usb/142387; it has been noted by GNATS.

From: Andrew <and...@flarn.com>
To: Hans Petter Selasky <hsel...@c2i.net>
Cc: freeb...@freebsd.org, freebsd-gn...@freebsd.org
Subject: Re: usb/142387: Netgear WPN111 not recognised by uath(4) after
uathload
Date: Thu, 7 Jan 2010 09:32:06 +0000

2010/1/6 Hans Petter Selasky <hsel...@c2i.net>:
> On Wednesday 06 January 2010 21:26:03 Andrew wrote:
>> >Number: =A0 =A0 =A0 =A0 142387
>> >Category: =A0 =A0 =A0 usb
>> >Synopsis: =A0 =A0 =A0 Netgear WPN111 not recognised by uath(4) after ua=
thload
>> >Confidential: =A0 no
>> >Severity: =A0 =A0 =A0 non-critical
>> >Priority: =A0 =A0 =A0 low
>> >Responsible: =A0 =A0freebsd-usb
>> >State: =A0 =A0 =A0 =A0 =A0open
>> >Quarter:
>> >Keywords:
>> >Date-Required:
>> >Class: =A0 =A0 =A0 =A0 =A0sw-bug
>> >Submitter-Id: =A0 current-users
>> >Arrival-Date: =A0 Wed Jan 06 20:30:06 UTC 2010
>> >Closed-Date:
>> >Last-Modified:
>> >Originator: =A0 =A0 Andrew
>> >Release: =A0 =A0 =A0 =A08-STABLE
>> >Organization:
>> >Environment:
>>
>> FreeBSD XXXXXX 8.0-STABLE FreeBSD 8.0-STABLE #2: Tue Jan =A05 21:34:37 G=
MT
>> =A02010 =A0 =A0 root@XXXXXX:/usr/obj/usr/src/sys/GENERIC =A0amd64
>>
>> >Description:
>>
>> After running uathload the device changes from:
>> ugen3.2: <WPN111 Atheros Communications Inc> at usbus3, cfg=3D0 md=3DHOS=
T
>> =A0spd=3DHIGH (480Mbps) pwr=3DON
>>
>> =A0 bLength =3D 0x0012
>> =A0 bDescriptorType =3D 0x0001
>> =A0 bcdUSB =3D 0x0200
>> =A0 bDeviceClass =3D 0x00ff
>> =A0 bDeviceSubClass =3D 0x0000
>> =A0 bDeviceProtocol =3D 0x0000
>> =A0 bMaxPacketSize0 =3D 0x0040
>> =A0 idVendor =3D 0x1385
>> =A0 idProduct =3D 0x5f01
>> =A0 bcdDevice =3D 0x0001
>> =A0 iManufacturer =3D 0x0001 =A0<Atheros Communications Inc>
>> =A0 iProduct =3D 0x0002 =A0<WPN111>
>> =A0 iSerialNumber =3D 0x0003 =A0<1.0>
>> =A0 bNumConfigurations =3D 0x0001
>> to:
>> ugen3.2: <WPN111 Atheros Communications Inc> at usbus3, cfg=3D0 md=3DHOS=
T
>> =A0spd=3DHIGH (480Mbps) pwr=3DON
>>
>> =A0 bLength =3D 0x0012
>> =A0 bDescriptorType =3D 0x0001
>> =A0 bcdUSB =3D 0x0200
>> =A0 bDeviceClass =3D 0x00ff
>> =A0 bDeviceSubClass =3D 0x0000
>> =A0 bDeviceProtocol =3D 0x0000
>> =A0 bMaxPacketSize0 =3D 0x0040
>> =A0 idVendor =3D 0x1385
>> =A0 idProduct =3D 0x5f02
>> =A0 bcdDevice =3D 0x0001
>> =A0 iManufacturer =3D 0x0001 =A0<Atheros Communications Inc>
>> =A0 iProduct =3D 0x0002 =A0<WPN111>
>> =A0 iSerialNumber =3D 0x0003 =A0<1.0>
>> =A0 bNumConfigurations =3D 0x0001
>>
>> Note: idProduct 0x5f01 -> 0x5f02 rather than 0x5f00
>>
>> >How-To-Repeat:
>>
>> Connect a Netgear WPN111, run uathload -d /dev/ugenX.X
>>
>> >Fix:
>>
>> Correct sys/dev/usb/usbdevs product id for WPN111 with firmware, patch
>> =A0attached.
>>
>> uath now attachs:
>>
>> dmesg:
>> ugen3.2: <Atheros Communications Inc> at usbus3 (disconnected)
>> ugen3.2: <Atheros Communications Inc> at usbus3
>> uath0: <Atheros Communications Inc WPN111, rev 2.00/0.01, addr 2> on usb=
us3
>>
>>
>> ifconfig uath0
>> uath0: flags=3D8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 2290
>> =A0 =A0 =A0 =A0 ether 00:14:6c:ea:81:a4
>> =A0 =A0 =A0 =A0 media: IEEE 802.11 Wireless Ethernet autoselect (autosel=
ect)
>> =A0 =A0 =A0 =A0 status: no carrier
>>
>>
>> Patch attached with submission follows:
>>
>> --- usbdevs.orig =A0 =A0 =A02010-01-06 20:15:02.000000000 +0000
>> +++ usbdevs =A0 2010-01-05 21:28:03.000000000 +0000
>> @@ -2005,8 +2005,8 @@
>> =A0product NETGEAR2 MA101B =A0 =A0 =A0 =A0 =A0 =A0 =A00x4102 =A0MA101 Re=
v B
>> =A0product NETGEAR3 WG111T =A0 =A0 =A0 =A0 =A0 =A0 =A00x4250 =A0WG111T
>> =A0product NETGEAR3 WG111T_NF =A0 0x4251 =A0WG111T (no firmware)
>> -product NETGEAR3 WPN111 =A0 =A0 =A0 =A0 =A0 =A0 =A00x5f00 =A0WPN111
>> =A0product NETGEAR3 WPN111_NF =A0 0x5f01 =A0WPN111 (no firmware)
>> +product NETGEAR3 WPN111 =A0 =A0 =A0 =A0 =A0 =A0 =A00x5f02 =A0WPN111
>>
>> =A0/* Nikon products */
>> =A0product NIKON E990 =A0 =A0 =A0 =A0 =A0 0x0102 =A0Digital Camera E990
>>
>> >Release-Note:
>> >Audit-Trail:
>> >Unformatted:
>
> Hi,
>
> Are you certain that product "0x5f00" is incorrect and that we shouldn't =
add
> the new product, 0x5f02 instead?

I can't be certain no, it was an assumption on my part that the WPN111
id was incorrect as the WPN111_NF was correct for the device. Adding a
second id for WPN111 will be enough for my hardware to work.

Thanks,
Andrew

------------------------------

Message: 17
Date: Thu, 7 Jan 2010 10:23:49 +0000
From: Andrew <and...@flarn.com>
Subject: Re: usb/142387: Netgear WPN111 not recognised by uath(4)
after uathload
To: Hans Petter Selasky <hsel...@c2i.net>
Cc: freebsd-gn...@freebsd.org, freeb...@freebsd.org
Message-ID:
<54854a7a1001070223n6c...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

2010/1/7 Andrew <and...@flarn.com>:
> 2010/1/6 Hans Petter Selasky <hsel...@c2i.net>:
>> On Wednesday 06 January 2010 21:26:03 Andrew wrote:
>>> >Number: � � � � 142387
>>> >Category: � � � usb
>>> >Synopsis: � � � Netgear WPN111 not recognised by uath(4) after uathload
>>> >Confidential: � no
>>> >Severity: � � � non-critical
>>> >Priority: � � � low
>>> >Responsible: � �freebsd-usb
>>> >State: � � � � �open
>>> >Quarter:
>>> >Keywords:
>>> >Date-Required:
>>> >Class: � � � � �sw-bug
>>> >Submitter-Id: � current-users
>>> >Arrival-Date: � Wed Jan 06 20:30:06 UTC 2010
>>> >Closed-Date:
>>> >Last-Modified:
>>> >Originator: � � Andrew
>>> >Release: � � � �8-STABLE
>>> >Organization:
>>> >Environment:
>>>
>>> FreeBSD XXXXXX 8.0-STABLE FreeBSD 8.0-STABLE #2: Tue Jan �5 21:34:37 GMT
>>> �2010 � � root@XXXXXX:/usr/obj/usr/src/sys/GENERIC �amd64
>>>
>>> >Description:
>>>
>>> After running uathload the device changes from:
>>> ugen3.2: <WPN111 Atheros Communications Inc> at usbus3, cfg=0 md=HOST
>>> �spd=HIGH (480Mbps) pwr=ON
>>>
>>> � bLength = 0x0012
>>> � bDescriptorType = 0x0001
>>> � bcdUSB = 0x0200
>>> � bDeviceClass = 0x00ff
>>> � bDeviceSubClass = 0x0000
>>> � bDeviceProtocol = 0x0000
>>> � bMaxPacketSize0 = 0x0040
>>> � idVendor = 0x1385
>>> � idProduct = 0x5f01
>>> � bcdDevice = 0x0001
>>> � iManufacturer = 0x0001 �<Atheros Communications Inc>
>>> � iProduct = 0x0002 �<WPN111>
>>> � iSerialNumber = 0x0003 �<1.0>
>>> � bNumConfigurations = 0x0001
>>> to:
>>> ugen3.2: <WPN111 Atheros Communications Inc> at usbus3, cfg=0 md=HOST
>>> �spd=HIGH (480Mbps) pwr=ON
>>>
>>> � bLength = 0x0012
>>> � bDescriptorType = 0x0001
>>> � bcdUSB = 0x0200
>>> � bDeviceClass = 0x00ff
>>> � bDeviceSubClass = 0x0000
>>> � bDeviceProtocol = 0x0000
>>> � bMaxPacketSize0 = 0x0040
>>> � idVendor = 0x1385
>>> � idProduct = 0x5f02
>>> � bcdDevice = 0x0001
>>> � iManufacturer = 0x0001 �<Atheros Communications Inc>
>>> � iProduct = 0x0002 �<WPN111>
>>> � iSerialNumber = 0x0003 �<1.0>
>>> � bNumConfigurations = 0x0001
>>>
>>> Note: idProduct 0x5f01 -> 0x5f02 rather than 0x5f00
>>>
>>> >How-To-Repeat:
>>>
>>> Connect a Netgear WPN111, run uathload -d /dev/ugenX.X
>>>
>>> >Fix:
>>>
>>> Correct sys/dev/usb/usbdevs product id for WPN111 with firmware, patch
>>> �attached.
>>>
>>> uath now attachs:
>>>
>>> dmesg:
>>> ugen3.2: <Atheros Communications Inc> at usbus3 (disconnected)
>>> ugen3.2: <Atheros Communications Inc> at usbus3
>>> uath0: <Atheros Communications Inc WPN111, rev 2.00/0.01, addr 2> on usbus3
>>>
>>>
>>> ifconfig uath0
>>> uath0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 2290
>>> � � � � ether 00:14:6c:ea:81:a4
>>> � � � � media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
>>> � � � � status: no carrier
>>>
>>>
>>> Patch attached with submission follows:
>>>
>>> --- usbdevs.orig � � �2010-01-06 20:15:02.000000000 +0000
>>> +++ usbdevs � 2010-01-05 21:28:03.000000000 +0000
>>> @@ -2005,8 +2005,8 @@
>>> �product NETGEAR2 MA101B � � � � � � �0x4102 �MA101 Rev B
>>> �product NETGEAR3 WG111T � � � � � � �0x4250 �WG111T
>>> �product NETGEAR3 WG111T_NF � 0x4251 �WG111T (no firmware)
>>> -product NETGEAR3 WPN111 � � � � � � �0x5f00 �WPN111
>>> �product NETGEAR3 WPN111_NF � 0x5f01 �WPN111 (no firmware)
>>> +product NETGEAR3 WPN111 � � � � � � �0x5f02 �WPN111
>>>
>>> �/* Nikon products */
>>> �product NIKON E990 � � � � � 0x0102 �Digital Camera E990
>>>
>>> >Release-Note:
>>> >Audit-Trail:
>>> >Unformatted:
>>
>> Hi,
>>
>> Are you certain that product "0x5f00" is incorrect and that we shouldn't add
>> the new product, 0x5f02 instead?
>
> I can't be certain no, it was an assumption on my part that the WPN111
> id was incorrect as the WPN111_NF was correct for the device. Adding a
> second id for WPN111 will �be enough for my hardware to work.

I have just seen this thread on -net:
http://lists.freebsd.org/pipermail/freebsd-net/2010-January/024182.html

Seems to be another Netgear uath(4) device that increments rather than
decrements it's productId, but that's by no means conclusive.

Regards,
Andrew

------------------------------

Message: 18
Date: Thu, 7 Jan 2010 10:30:06 GMT
From: Andrew <and...@flarn.com>
Subject: Re: usb/142387: Netgear WPN111 not recognised by uath(4)
after uathload
To: freeb...@FreeBSD.org
Message-ID: <201001071030....@freefall.freebsd.org>

The following reply was made to PR usb/142387; it has been noted by GNATS.

2010/1/7 Andrew <and...@flarn.com>:
> 2010/1/6 Hans Petter Selasky <hsel...@c2i.net>:
>> On Wednesday 06 January 2010 21:26:03 Andrew wrote:
>>> >Number: =A0 =A0 =A0 =A0 142387
>>> >Category: =A0 =A0 =A0 usb
>>> >Synopsis: =A0 =A0 =A0 Netgear WPN111 not recognised by uath(4) after u=
athload
>>> >Confidential: =A0 no
>>> >Severity: =A0 =A0 =A0 non-critical
>>> >Priority: =A0 =A0 =A0 low
>>> >Responsible: =A0 =A0freebsd-usb
>>> >State: =A0 =A0 =A0 =A0 =A0open
>>> >Quarter:
>>> >Keywords:
>>> >Date-Required:
>>> >Class: =A0 =A0 =A0 =A0 =A0sw-bug
>>> >Submitter-Id: =A0 current-users
>>> >Arrival-Date: =A0 Wed Jan 06 20:30:06 UTC 2010
>>> >Closed-Date:
>>> >Last-Modified:
>>> >Originator: =A0 =A0 Andrew
>>> >Release: =A0 =A0 =A0 =A08-STABLE
>>> >Organization:
>>> >Environment:
>>>
>>> FreeBSD XXXXXX 8.0-STABLE FreeBSD 8.0-STABLE #2: Tue Jan =A05 21:34:37 =
GMT
>>> =A02010 =A0 =A0 root@XXXXXX:/usr/obj/usr/src/sys/GENERIC =A0amd64
>>>
>>> >Description:
>>>
>>> After running uathload the device changes from:
>>> ugen3.2: <WPN111 Atheros Communications Inc> at usbus3, cfg=3D0 md=3DHO=
ST
>>> =A0spd=3DHIGH (480Mbps) pwr=3DON
>>>
>>> =A0 bLength =3D 0x0012
>>> =A0 bDescriptorType =3D 0x0001
>>> =A0 bcdUSB =3D 0x0200
>>> =A0 bDeviceClass =3D 0x00ff
>>> =A0 bDeviceSubClass =3D 0x0000
>>> =A0 bDeviceProtocol =3D 0x0000
>>> =A0 bMaxPacketSize0 =3D 0x0040
>>> =A0 idVendor =3D 0x1385
>>> =A0 idProduct =3D 0x5f01
>>> =A0 bcdDevice =3D 0x0001
>>> =A0 iManufacturer =3D 0x0001 =A0<Atheros Communications Inc>
>>> =A0 iProduct =3D 0x0002 =A0<WPN111>
>>> =A0 iSerialNumber =3D 0x0003 =A0<1.0>
>>> =A0 bNumConfigurations =3D 0x0001
>>> to:
>>> ugen3.2: <WPN111 Atheros Communications Inc> at usbus3, cfg=3D0 md=3DHO=
ST
>>> =A0spd=3DHIGH (480Mbps) pwr=3DON
>>>
>>> =A0 bLength =3D 0x0012
>>> =A0 bDescriptorType =3D 0x0001
>>> =A0 bcdUSB =3D 0x0200
>>> =A0 bDeviceClass =3D 0x00ff
>>> =A0 bDeviceSubClass =3D 0x0000
>>> =A0 bDeviceProtocol =3D 0x0000
>>> =A0 bMaxPacketSize0 =3D 0x0040
>>> =A0 idVendor =3D 0x1385
>>> =A0 idProduct =3D 0x5f02
>>> =A0 bcdDevice =3D 0x0001
>>> =A0 iManufacturer =3D 0x0001 =A0<Atheros Communications Inc>
>>> =A0 iProduct =3D 0x0002 =A0<WPN111>
>>> =A0 iSerialNumber =3D 0x0003 =A0<1.0>
>>> =A0 bNumConfigurations =3D 0x0001
>>>
>>> Note: idProduct 0x5f01 -> 0x5f02 rather than 0x5f00
>>>
>>> >How-To-Repeat:
>>>
>>> Connect a Netgear WPN111, run uathload -d /dev/ugenX.X
>>>
>>> >Fix:
>>>
>>> Correct sys/dev/usb/usbdevs product id for WPN111 with firmware, patch
>>> =A0attached.
>>>
>>> uath now attachs:
>>>
>>> dmesg:
>>> ugen3.2: <Atheros Communications Inc> at usbus3 (disconnected)
>>> ugen3.2: <Atheros Communications Inc> at usbus3
>>> uath0: <Atheros Communications Inc WPN111, rev 2.00/0.01, addr 2> on us=
bus3
>>>
>>>
>>> ifconfig uath0
>>> uath0: flags=3D8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 2290
>>> =A0 =A0 =A0 =A0 ether 00:14:6c:ea:81:a4
>>> =A0 =A0 =A0 =A0 media: IEEE 802.11 Wireless Ethernet autoselect (autose=
lect)
>>> =A0 =A0 =A0 =A0 status: no carrier
>>>
>>>
>>> Patch attached with submission follows:
>>>
>>> --- usbdevs.orig =A0 =A0 =A02010-01-06 20:15:02.000000000 +0000
>>> +++ usbdevs =A0 2010-01-05 21:28:03.000000000 +0000
>>> @@ -2005,8 +2005,8 @@
>>> =A0product NETGEAR2 MA101B =A0 =A0 =A0 =A0 =A0 =A0 =A00x4102 =A0MA101 R=
ev B
>>> =A0product NETGEAR3 WG111T =A0 =A0 =A0 =A0 =A0 =A0 =A00x4250 =A0WG111T
>>> =A0product NETGEAR3 WG111T_NF =A0 0x4251 =A0WG111T (no firmware)
>>> -product NETGEAR3 WPN111 =A0 =A0 =A0 =A0 =A0 =A0 =A00x5f00 =A0WPN111
>>> =A0product NETGEAR3 WPN111_NF =A0 0x5f01 =A0WPN111 (no firmware)
>>> +product NETGEAR3 WPN111 =A0 =A0 =A0 =A0 =A0 =A0 =A00x5f02 =A0WPN111
>>>
>>> =A0/* Nikon products */
>>> =A0product NIKON E990 =A0 =A0 =A0 =A0 =A0 0x0102 =A0Digital Camera E990
>>>
>>> >Release-Note:
>>> >Audit-Trail:
>>> >Unformatted:
>>
>> Hi,
>>
>> Are you certain that product "0x5f00" is incorrect and that we shouldn't=
add
>> the new product, 0x5f02 instead?
>
> I can't be certain no, it was an assumption on my part that the WPN111
> id was incorrect as the WPN111_NF was correct for the device. Adding a
> second id for WPN111 will =A0be enough for my hardware to work.

I have just seen this thread on -net:
http://lists.freebsd.org/pipermail/freebsd-net/2010-January/024182.html

Seems to be another Netgear uath(4) device that increments rather than
decrements it's productId, but that's by no means conclusive.

Regards,
Andrew

------------------------------

Message: 19
Date: Thu, 7 Jan 2010 16:53:16 GMT
From: Yury Michurin <yury.m...@gmail.com>
Subject: usb/142427: EDIMAX EW7318USG should be added to usbdevs
To: freebsd-gn...@FreeBSD.org
Message-ID: <201001071653....@www.freebsd.org>

>Number: 142427
>Category: usb
>Synopsis: EDIMAX EW7318USG should be added to usbdevs
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-usb
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: change-request
>Submitter-Id: current-users
>Arrival-Date: Thu Jan 07 17:00:08 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Yury Michurin
>Release: 7.2-STABLE
>Organization:
none
>Environment:
FreeBSD delta 7.2-STABLE FreeBSD 7.2-STABLE #5: Thu Jan 7 00:26:51 IST 2010 yury@delta:/usr/obj/usr/src/sys/delta amd64

>Description:
At http://www.freebsd.org/releases/7.2R/hardware.html is stated that Edimax EW-7318USG is supported by the rum(4) driver, however it's vendor / product ids are not listed in sys/dev/usb/usbdevs ( and neither in if_rum.c ) which should be:

vendor EDIMAX 0x7392 Edimax
/* Edimax products */
product EDIMAX EW7318USG 0x7318 USB Wirless dongle

I got this values from my wirless card and succefully recompiled the driver (after changing if_rum.c as well), it is now recognising the card:

Jan 7 18:43:05 delta kernel: rum0: <Ralink 802.11 bg WLAN, class 0/0, rev 2.00/0.01, addr 2> on uhub5
Jan 7 18:43:05 delta kernel: rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528
Jan 7 18:43:05 delta kernel: rum0: WARNING: using obsoleted IFF_NEEDSGIANT flag
Jan 7 18:43:05 delta kernel: rum0: Ethernet address: 00:1f:1f:xx:xx:xx

also succefully tested it in AP mode. ( haven't tested with other modes yet )
>How-To-Repeat:
N/A
>Fix:
add to sys/dev/usb/usbdevs:

vendor EDIMAX 0x7392 Edimax
/* Edimax products */
product EDIMAX EW7318USG 0x7318 USB Wirless dongle

add to sys/dev/usb/if_rum.c:
{ USB_VENDOR_EDIMAX, USB_PRODUCT_EDIMAX_EW7318USG }

>Release-Note:
>Audit-Trail:
>Unformatted:

------------------------------

Message: 20
Date: Thu, 7 Jan 2010 18:11:32 +0100
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/142427: EDIMAX EW7318USG should be added to usbdevs
To: freeb...@freebsd.org
Cc: Yury Michurin <yury.m...@gmail.com>,
freebsd-gn...@freebsd.org
Message-ID: <201001071811....@c2i.net>
Content-Type: Text/Plain; charset="iso-8859-15"

On Thursday 07 January 2010 17:53:16 Yury Michurin wrote:
> >Number: 142427
> >Category: usb
> >Synopsis: EDIMAX EW7318USG should be added to usbdevs
> >Confidential: no
> >Severity: non-critical
> >Priority: low
> >Responsible: freebsd-usb
> >State: open
> >Quarter:
> >Keywords:
> >Date-Required:
> >Class: change-request
> >Submitter-Id: current-users
> >Arrival-Date: Thu Jan 07 17:00:08 UTC 2010
> >Closed-Date:
> >Last-Modified:
> >Originator: Yury Michurin
> >Release: 7.2-STABLE
> >Organization:
>
> none
>
> >Environment:
>
> FreeBSD delta 7.2-STABLE FreeBSD 7.2-STABLE #5: Thu Jan 7 00:26:51 IST
> 2010 yury@delta:/usr/obj/usr/src/sys/delta amd64
>
> >Description:
>
> At http://www.freebsd.org/releases/7.2R/hardware.html is stated that Edimax
> EW-7318USG is supported by the rum(4) driver, however it's vendor /
> product ids are not listed in sys/dev/usb/usbdevs ( and neither in
> if_rum.c ) which should be:
>
>
> vendor EDIMAX 0x7392 Edimax
> /* Edimax products */
> product EDIMAX EW7318USG 0x7318 USB Wirless dongle
>
> I got this values from my wirless card and succefully recompiled the driver
> (after changing if_rum.c as well), it is now recognising the card:
>
> Jan 7 18:43:05 delta kernel: rum0: <Ralink 802.11 bg WLAN, class 0/0, rev
> 2.00/0.01, addr 2> on uhub5 Jan 7 18:43:05 delta kernel: rum0: MAC/BBP
> RT2573 (rev 0x2573a), RF RT2528 Jan 7 18:43:05 delta kernel: rum0:
> WARNING: using obsoleted IFF_NEEDSGIANT flag Jan 7 18:43:05 delta kernel:
> rum0: Ethernet address: 00:1f:1f:xx:xx:xx
>
> also succefully tested it in AP mode. ( haven't tested with other modes yet
> )
>
> >How-To-Repeat:
>
> N/A
>
> >Fix:
>
> add to sys/dev/usb/usbdevs:
>
> vendor EDIMAX 0x7392 Edimax
> /* Edimax products */
> product EDIMAX EW7318USG 0x7318 USB Wirless dongle
>
> add to sys/dev/usb/if_rum.c:
> { USB_VENDOR_EDIMAX, USB_PRODUCT_EDIMAX_EW7318USG }

Hi,

Committed to USB P4 (FreeBSD 8)

--HPS

------------------------------

Message: 21
Date: Thu, 7 Jan 2010 17:20:02 GMT
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/142427: EDIMAX EW7318USG should be added to usbdevs
To: freeb...@FreeBSD.org
Message-ID: <201001071720....@freefall.freebsd.org>

The following reply was made to PR usb/142427; it has been noted by GNATS.

From: Hans Petter Selasky <hsel...@c2i.net>
To: freeb...@freebsd.org
Cc: Yury Michurin <yury.m...@gmail.com>,
freebsd-gn...@freebsd.org
Subject: Re: usb/142427: EDIMAX EW7318USG should be added to usbdevs
Date: Thu, 7 Jan 2010 18:11:32 +0100

------------------------------

Message: 22
Date: Thu, 07 Jan 2010 17:31:16 -0500
From: tkor...@aim.com
Subject: problem USB wireless keyboard and mouse
To: freeb...@freebsd.org
Message-ID: <8CC5E004286F...@webmail-m061.sysops.aol.com>
Content-Type: text/plain; charset="us-ascii"

Hi,

I was directed by Kris of PC-BSD to this list to report following problem.

I have a HP Pavillion m7760 2006 PC with wireless keyboard and wireless mouse.
They work via a receiver which is connected in the PC by USB.
The problem is both do not react when installing PC-BSD first screen.
Same for FreeBSD8, as I tried to install as well.
There is no reaction on Ctrl+alt+F1.

In the messages previous the graphical install screen I managed to read the following;

USB alloc device 1586
USB alloc device 1624
device descriptor failed at addr2

later

uhub reattach port: 435: could not allocate new device.

According to Kris of PC-BSD it should be a problem wth the new USB subsystem of FreeBSD8.

This is an issue that should be resolved.
I still had a PS2 keyboard, but had to buy a PS2 mouse in order to install.
Well, buying a PS2 mouse is becoming quite hard.
They are all USB nowadays.
Without proper USB support BSD will not survive.

Besides this, BSD is the best OS I ever used. Stable, fast...a Linux-killer...

------------------------------

Message: 23
Date: Fri, 8 Jan 2010 09:04:15 +0100
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: problem USB wireless keyboard and mouse
To: freeb...@freebsd.org
Cc: tkor...@aim.com
Message-ID: <201001080904....@c2i.net>
Content-Type: Text/Plain; charset="iso-8859-1"

On Thursday 07 January 2010 23:31:16 tkor...@aim.com wrote:
> Hi,
>
> I was directed by Kris of PC-BSD to this list to report following problem.
>
> I have a HP Pavillion m7760 2006 PC with wireless keyboard and wireless
> mouse. They work via a receiver which is connected in the PC by USB.
> The problem is both do not react when installing PC-BSD first screen.
> Same for FreeBSD8, as I tried to install as well.
> There is no reaction on Ctrl+alt+F1.
>
> In the messages previous the graphical install screen I managed to read the
> following;
>
> USB alloc device 1586
> USB alloc device 1624
> device descriptor failed at addr2
>
> later
>
> uhub reattach port: 435: could not allocate new device.
>
> According to Kris of PC-BSD it should be a problem wth the new USB
> subsystem of FreeBSD8.
>
> This is an issue that should be resolved.
> I still had a PS2 keyboard, but had to buy a PS2 mouse in order to install.
> Well, buying a PS2 mouse is becoming quite hard.
> They are all USB nowadays.
> Without proper USB support BSD will not survive.
>
> Besides this, BSD is the best OS I ever used. Stable, fast...a
> Linux-killer...
>

Hi,

Do other USB devices work?

Does an ordinary USB keyboard work?

What I need is output from:

usbconfig dump_device_desc dump_curr_config_desc

Of your system when your mouse+keyboard device is plugged in.

It might also be a recent problem of ACPI where some resources were not
correctly mapped.

--HPS

------------------------------

Message: 24
Date: Sat, 9 Jan 2010 12:40:02 GMT
From: Wiktor Niesiobedzki <b...@w.evip.pl>
Subject: Re: kern/141011: [usb] Encrypted root, geli password at boot;
enter key never released
To: freeb...@FreeBSD.org
Message-ID: <201001091240....@freefall.freebsd.org>

The following reply was made to PR kern/141011; it has been noted by GNATS.

From: Wiktor Niesiobedzki <b...@w.evip.pl>
To: bug-followup <bug-fo...@FreeBSD.org>, leclercn <lecl...@videotron.ca>
Cc:
Subject: Re: kern/141011: [usb] Encrypted root, geli password at boot; enter
key never released
Date: Sat, 9 Jan 2010 13:22:15 +0100

Hi,

I've just tried your suggestion to comment out the code "read and
discard the input, no one is waiting for it". (I had to comment out
also uint32_t c declaration), but I don't see any improvement. Still
ukbd is behaving, as enter key hadn't been released.

Cheers,

Wiktor Niesiob=C4=99dzki

------------------------------

Message: 25
Date: Sun, 10 Jan 2010 00:20:05 GMT
From: Wiktor Niesiobedzki <b...@w.evip.pl>
Subject: Re: Re: kern/141011: [usb] Encrypted root, geli password at
boot; enter key never release
To: freeb...@FreeBSD.org
Message-ID: <201001100020....@freefall.freebsd.org>

The following reply was made to PR kern/141011; it has been noted by GNATS.

From: Wiktor Niesiobedzki <b...@w.evip.pl>
To: Hans Petter Selasky <hsel...@c2i.net>
Cc: bug-followup <bug-fo...@freebsd.org>
Subject: Re: Re: kern/141011: [usb] Encrypted root, geli password at boot;
enter key never release
Date: Sun, 10 Jan 2010 01:19:08 +0100

Hi,

I've just tested your patch. After full boot process the keyboard is
fully usable (that's the great improvement). But on the other hand, I
see that some of the characters are droped during input of passpharse
(it looks like every 10th or 15th - not sure if there is constant
value between characters). The character is dropped no matter how long
the key is pressed.

Any further hints?

Cheers,

Wiktor Niesiobedzki

2010/1/9 Hans Petter Selasky <hsel...@c2i.net>:
>
> ---------- =C2=A0Forwarded Message =C2=A0----------
>
> Subject: Re: kern/141011: [usb] Encrypted root, geli password at boot; en=
ter
> key never release
> Date: Friday 08 January 2010
> From: Hans Petter Selasky <hsel...@c2i.net>
> To: Guido van Rooij <gu...@gvr.org>
>
> Hi,
>
> Can you try the attached patch to ukbd.c . You might need to apply it by =
hand.
> I've attached the complete file aswell.
>
> --HPS
>
> -------------------------------------------------------
>

------------------------------

Message: 26
Date: Sun, 10 Jan 2010 02:39:13 +0100
From: Torfinn Ingolfsen <torfinn....@broadpark.no>
Subject: FreeBSD 8.0 and HPLIP - you also need execute permissions on
/dev/usb
To: freeb...@FreeBSD.org
Message-ID: <20100110023913.5fd34...@broadpark.no>
Content-Type: text/plain; charset=ISO-8859-1

Ok, I recently "upgraded" my main workstation to FreeBSD 8.0-stable
(clean install on a new slice):
tingo@kg-v2$ uname -a
FreeBSD kg-v2.kg4.no 8.0-STABLE FreeBSD 8.0-STABLE #1: Wed Jan 6 21:21:40 CET 2010 ro...@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64

After that I got the fun of install�ing all my ports again.

Anyway, this machine have a HP Photosmart 8250 printer connected to it
(via usb), and I have been using hplip from ports to controil it.
Before the upgrade (using FreeBSD 7.2-stable, I was running HPLIP
3.9.6b). Now I installed hplip 3.9.8 from ports, since it is the newest
i ports.

And of course it didn't print (nobody said it was going to be easy).
I had the necessary things in /etc/devfs.rules (or so I thought):
tingo@kg-v2$ more /etc/devfs.rules
[devfsrules_local=5]
add path 'usb*' group cups
add path 'usb*' mode 0660
add path 'usb/*' group cups
add path 'usb/*' mode 0660
add path 'uscanner*' group cups
add path 'uscanner*' mode 0660
add path 'ugen*' group cups
add path 'ugen*' mode 0660

But when listing the devices, I found a problem:
tingo@kg-v2$ ls -l /dev/ug* /dev/usb*
lrw-rw---- 1 root cups 9 Jan 6 22:46 /dev/ugen0.1 -> usb/0.1.0
lrw-rw---- 1 root cups 9 Jan 6 22:46 /dev/ugen0.2 -> usb/0.2.0
lrw-rw---- 1 root cups 9 Jan 6 22:46 /dev/ugen1.1 -> usb/1.1.0
lrw-rw---- 1 root cups 9 Jan 6 22:46 /dev/ugen1.2 -> usb/1.2.0
lrw-rw---- 1 root cups 9 Jan 6 22:46 /dev/ugen1.3 -> usb/1.3.0
lrw-rw---- 1 root cups 9 Jan 6 22:46 /dev/ugen2.1 -> usb/2.1.0
lrw-rw---- 1 root cups 9 Jan 6 22:46 /dev/ugen2.2 -> usb/2.2.0
lrw-rw---- 1 root cups 9 Jan 6 22:46 /dev/ugen3.1 -> usb/3.1.0
crw-rw---- 1 root cups 0, 63 Jan 6 22:46 /dev/usbctl

/dev/usb:
ls: 0.1.0: Permission denied
ls: 0.1.1: Permission denied
ls: 0.2.0: Permission denied
ls: 0.2.1: Permission denied
ls: 0.2.2: Permission denied
ls: 1.1.0: Permission denied
ls: 1.1.1: Permission denied
ls: 1.2.0: Permission denied
ls: 1.2.10: Permission denied
ls: 1.2.11: Permission denied
ls: 1.2.4: Permission denied
ls: 1.2.5: Permission denied
ls: 1.2.6: Permission denied
ls: 1.2.7: Permission denied
ls: 1.2.8: Permission denied
ls: 1.2.9: Permission denied
ls: 1.3.0: Permission denied
ls: 1.3.1: Permission denied
ls: 1.3.2: Permission denied
ls: 2.1.0: Permission denied
ls: 2.1.1: Permission denied
ls: 2.2.0: Permission denied
ls: 2.2.1: Permission denied
ls: 2.2.2: Permission denied
ls: 2.2.3: Permission denied
ls: 3.1.0: Permission denied
ls: 3.1.1: Permission denied
total 0

Ok, so you need execute permissions on /dev/usb as well (because it is a directory).
I fixed it by adding 'add path 'usb' mode 0770' to /etc/devfs.rules.

Is this the correct way to deal wih it?
--
Regards,
Torfinn Ingolfsen

------------------------------

Message: 27
Date: Sun, 10 Jan 2010 08:10:02 GMT
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: kern/141011: [usb] Encrypted root, geli password at boot;
enter key never release
To: freeb...@FreeBSD.org
Message-ID: <201001100810....@freefall.freebsd.org>

The following reply was made to PR kern/141011; it has been noted by GNATS.

From: Hans Petter Selasky <hsel...@c2i.net>
To: Wiktor Niesiobedzki <b...@w.evip.pl>
Cc: "bug-followup" <bug-fo...@freebsd.org>
Subject: Re: kern/141011: [usb] Encrypted root, geli password at boot; enter key never release
Date: Sun, 10 Jan 2010 08:59:44 +0100

On Sunday 10 January 2010 01:19:08 Wiktor Niesiobedzki wrote:
> Hi,
>
> I've just tested your patch. After full boot process the keyboard is
> fully usable (that's the great improvement). But on the other hand, I
> see that some of the characters are droped during input of passpharse
> (it looks like every 10th or 15th - not sure if there is constant
> value between characters). The character is dropped no matter how long
> the key is pressed.
>
> Any further hints?
>

Try to comment out:

/* read and discard the input, no one is waiting for it */
do {
c = ukbd_read_char(&sc->sc_kbd, 0);
} while (c != NOKEY);

In: ukbd_interrupt() in ukbd.c.

--HPS

------------------------------

Message: 28
Date: Sun, 10 Jan 2010 12:52:24 +0100
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: Calling for testers if_run rt3572 support
To: freebsd...@freebsd.org, freeb...@freebsd.org
Cc: PseudoCylon <moonlig...@yahoo.ca>
Message-ID: <201001101252....@c2i.net>
Content-Type: Text/Plain; charset="iso-8859-1"

On Sunday 10 January 2010 01:04:34 PseudoCylon wrote:
> Akinori

Hi,

Can you test and verify the following changes to your if_run driver?

http://p4web.freebsd.org/chv.cgi?CH=172914

http://perforce.freebsd.org/chv.cgi?CH=172914

And provide patches if something was broken.

Please try to resolve the remaining XXX marks.

--HPS

------------------------------

End of freebsd-usb Digest, Vol 270, Issue 2
*******************************************

0 new messages