Re: iBlitzz BWU613SB

Hi Anarcat,

> the real chipset behind this device. The FCC id is Q8NAWU2000B, which
> points to another company, AIN Communications. I can't figure out how
> to link to the search page, but here is the exhibit page:
>
> https://gullfoss2.fcc.gov/prod/oet/cf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout=500&calledFromFrame=N&application_id=423176&fcc_id='Q8NAWU2000B'
>
> Of course, the AIN COMM website doesn't provide anything more useful
> than the iBlitzz one. Indeed, both sites look religiously the same, in
> terms of drivers and documentation:
>
> http://www.aincomm.com.tw/prod_usb_awu2000b_feature.htm

the internal pictures are sometimes helpful in figuring out the
chips' names. And the pictures of your device are really sharp:
IMHO you got a 505A+RFMD2958 device, try to add your id to
at76c505-rfmd2958.c, compile, install and load.

Currently there are some threads running in the list with problems of
these devices with the 0.12betaN driver, you may consider to try 0.11
in any case of Oops etc.

> [syslogs removed]

Thanks for reading the support pages _before_ asking in the list!

> I notice that "find_matching_bss" always returns 00000000, but I do
> not understand the meaning of "If it always returns address 00000000,
> check your driver parameters (earlier in the syslog)."

0000000 means no BSS was selected, the above is only true if the wanted
BSS is in the list. I'll fix that.

If you still get an empty BSS list in the syslog (and your peer is
switched on), try the at76c505-rfmd.c instead of at76c505-rfmd2958.c
(but I've never seen a device with this firmware in the wild).

Come back to the list in any case (error or success)!

BTW, if you became a member of the list, your posting wouldn't need my
manual approval (which may take some days as your previous one).

Regards,
Jörg