Re: [[email protected]: USB host controllers and Device 12fd 1001 (aincomm awu2000b or IBlitzz BWU613B)]

Yes, I had the very same problem in the beginning; because
I did not understand that "the" berlios driver was in reality
a collection of drivers.

Get the latest version from CVS. Unpack, compile, make install
(as root).

The driver you need for the 12fd-1001 device is the
at76c505_rfmd2958 module. "modprobe" it and the other
drivers, namely usbdfu (firmware upload) and at76c503
(generic atmel layer, despite its name) are recursively
modprobed/insmodded.

Greetings,
Enver



# lsmod
Module                  Size  Used by
rfcomm                 33820  1
l2cap                  19844  5 rfcomm
hci_usb                 9088  0
bluetooth              41828  5 rfcomm,l2cap,hci_usb
at76c505_rfmd2958      40836  0
at76c503               79328  1 at76c505_rfmd2958
usbdfu                  5248  1 at76c503


David A. De Graaf wrote:
> Resending in response to your failure message at
> [email protected]
> 
> 
> 
> ----- Forwarded message from "David A. De Graaf" <dad-ucVp/[email protected]> -----
> 
> Date: Tue, 13 Apr 2004 22:46:17 -0400
> From: "David A. De Graaf" <dad-ucVp/[email protected]>
> Subject: [Atmel-WLAN-USB] USB host controllers and Device 12fd 1001 (aincomm
> 	awu2000b or IBlitzz BWU613B)
> To: atmel-wlan-usb-ikZNBd7uB5wQUIZIPwn63sWURRETrGNnG9Ur7JDdleE@public.gmane.org
> Cc: [email protected]
> 
> Enver Haase ehaase at inf.fu-berlin.de 
> reported that he managed to make the  Device 12fd 1001 (aincomm
> awu2000b or IBlitzz BWU613B) work.  That's great news!
> I've been struggling to accomplish this since Dec. 2003 without 
> success.
> 
> This was achieved with "kernel 2.6.4 using the "berlios" driver",
> but no other details were offered.  It would be helpful to know
> exactly what was done.
> 
> I am working with Fedora Core 1, kernel 2.4.22-1.2174.nptl, and
> at76c503-0.11.tar.gz.  The vendor/product numbers reported by my
> Blitzz BWU 613B device of 0x12fd and 0x1001 are not known in any 
> of the drivers of this package so the USB device is not "claimed"
> by any driver.  I have tried adding these lines to at76c503-rfmd.c
> 
> #define VENDOR_ID_BLITZZ              0x12fd
> #define PRODUCT_ID_BLITZZ_BWU613B     0x1001 /* Blitzz BWU613B buy 12/03 */
> 
>         { USB_DEVICE(VENDOR_ID_BLITZZ,   PRODUCT_ID_BLITZZ_BWU613B ) },
> 
> This allows the driver to recognize the device and configure wlan0.
> However, no radio communication occurs.  Pinging another Ad-Hoc
> station by IP number generates activity on the wlan0 interface,
> but the other station hears nothing.  Pinging in the opposite
> direction also produces no reception in the Blitzz device.
> 'ifconfig wlan0' reports transmitted packets but zero received packets.
> 
> Since I don't know what's inside this device, I tried adding the
> Blitzz parameters to each of the six possible drivers in turn.
> Once in a while the at76C505-rfmd2958 driver would seem to recognize
> the device, but it wouldn't communicate.
> 
> Has anyone succeeded in making the Blitzz USB wireless device work?
> If so, how?  Thanks.
>