Jonathan Gray schrieb:
On Tue, Feb 03, 2009 at 08:08:45PM +0100, Dorian B?ttner wrote:
Feb 3 19:02:55 eee /bsd: ugen0 at uhub2 port 1 "vendor 0x0d98 Avaya
Wireless USB Adapter" rev 1.10/0.00 addr 2
According to http://www.wifihowto.org/?mo=HowTo;Item=14 it should work
with the wi driver, but wi doesn't attach, I only get the ugen0.
PC24E-H-FC is printed on the sticker at the bottom, and it's most likely
rebranded lucent or proxim.
Is there a quick hack to attach a wi instance to it?
Thanks again,
Dorian
The page you linked says nothing of USB devices, it could require
firmware to be loaded or be a different chipset entirely.
Assuming usbdevs -v shows 0x0300 for the product id try this:
It does :-)
cd /usrc/src
patch -p0 < /path/to/diff
cd /usrc/src/sys/dev/usb
make
compile a kernel as usual
Index: sys/dev/usb/usbdevs
===================================================================
RCS file: /cvs/src/sys/dev/usb/usbdevs,v
retrieving revision 1.405
diff -u -p -r1.405 usbdevs
--- sys/dev/usb/usbdevs 19 Jan 2009 10:20:05 -0000 1.405
+++ sys/dev/usb/usbdevs 3 Feb 2009 23:39:21 -0000
@@ -416,6 +416,7 @@ vendor SMC3 0x0d5c SMC
vendor PEN 0x0d7d Pen Drive
vendor ABC 0x0d8c ABC
vendor CONCEPTRONIC 0x0d8e Conceptronic
+vendor AVAYA 0x0d98 Avaya
vendor MSI 0x0db0 Micro Star International
vendor ELCON 0x0db7 ELCON Systemtechnik
vendor SITECOMEU 0x0df6 Sitecom Europe
@@ -873,6 +874,9 @@ product AUDIOVOX PC5740 0x3701 PC5740 E
/* Avance Logic products */
product AVANCELOGIC USBAUDIO 0x0100 USB Audio Speaker
+
+/* Avaya products */
+product AVAYA ORINOCO_GOLD 0x0300 Orinoco Gold
/* Averatec products */
product AVERATEC USBWLAN 0x4013 WLAN
Index: sys/dev/usb/if_wi_usb.c
===================================================================
RCS file: /cvs/src/sys/dev/usb/if_wi_usb.c,v
retrieving revision 1.44
diff -u -p -r1.44 if_wi_usb.c
--- sys/dev/usb/if_wi_usb.c 11 Oct 2007 18:33:14 -0000 1.44
+++ sys/dev/usb/if_wi_usb.c 3 Feb 2009 23:39:21 -0000
@@ -228,6 +228,7 @@ const struct wi_usb_type {
{{ USB_VENDOR_ADAPTEC, USB_PRODUCT_ADAPTEC_AWN8020 }, 0 },
{{ USB_VENDOR_AMBIT, USB_PRODUCT_AMBIT_WLAN }, 0 },
{{ USB_VENDOR_ASUSTEK, USB_PRODUCT_ASUSTEK_WL140 }, 0 },
+ {{ USB_VENDOR_AVAYA, USB_PRODUCT_AVAYA_ORINOCO_GOLD }, 0 },
{{ USB_VENDOR_AVERATEC, USB_PRODUCT_AVERATEC_USBWLAN }, 0 },
{{ USB_VENDOR_COMPAQ, USB_PRODUCT_COMPAQ_W100 }, 0 },
{{ USB_VENDOR_COMPAQ, USB_PRODUCT_COMPAQ_W200 }, 0 },
Patch applies cleanly - can you please not commit it? Attaching the
device raises following message(s):
Feb 4 14:24:28 LT213 /bsd: wi0 at uhub2
Feb 4 14:24:28 LT213 /bsd: port 1 "Avaya Orinoco Gold" rev 1.10/0.00
addr 2
Feb 4 14:24:28 LT213 /bsd: wi0: open intr pipe failed: BAD_ADDRESS
Feb 4 14:24:28 LT213 /bsd: wi0: open pipes failed
unplugging it drops into ddb:
uvm_fault(0xd080ea80, 0x0, 0, 3) -> e
kernel: page fault trap, code=0
Stopped at wi_usb_activate+0x21: movl $0x1,0x4(%eax)
Thanks,
Dorian
