RE: Can't find AP (BT voyager 1010USB, Fedora Core 3 k: 2.6.10)

Hi Haydn,

I might be missing a totally obvious solution here (eg: some specific
setting on your AP - tried with another AP?), but the first thing that
popped into my head was enabling International Roaming.
Although this probably wont do anything (your regulatory domain is MKK1
which includes all the WiFi channels 1-14 anyway) it still might be worth a
try (weird firmware?):

You can either: insert the module into the kernel and append on the end of
your 'modprobe' command:

international_roaming=1

or use iwpriv on the private ioctl 'intl_roaming' and set it to 1.

If that fails to rectify the situation, you might want to go into the
at76c503.c source file and look for the line beginning with:

static int debug = ...

What you'll want to do is set the 'debug' variable to a bitwise-OR
combination of the debug bits you'll find above in the source. You'll
probably find it especially helpful to show received beacons and other rx
data of your choosing. If showing the BSS table isn't enabled, you should
flick it on too. I found they were all very helpful when I was adding
International Roaming & (quasi-)Monitor mode to the driver... For example:

#define DBG_DEFAULTS (DBG_PROGRESS | DBG_PARAMS | DBG_BSS_TABLE |
DBG_DEVSTART | DBG_BSS_MATCH | DBG_KEVENT | DBG_PROC_ENTRY | DBG_PM |
DBG_WAIT_COMPLETE | DBG_BSS_TABLE_RM)
#define DBG_TX_RX    (DBG_TX_DATA | DBG_TX_DATA_CONTENT | DBG_TX_MGMT |
DBG_RX_DATA | DBG_RX_DATA_CONTENT | DBG_RX_MGMT | DBG_RX_BEACON |
DBG_RX_CTRL | DBG_RX_MGMT_CONTENT | DBG_RX_FRAGS | DBG_URB |
DBG_RX_ATMEL_HDR | DBG_RX_FRAGS_SKB )
static int debug = DBG_DEFAULTS | DBG_IOCTL | DBG_TX_RX;

This will enable pretty much everything... (be careful though as I have old
source and I think Joerg has changed the names around slightly)

Once you've changed the source, you'll obviously have to re-compile and
install the modules again. Then just watch your syslog!

Btw: turns out that the only reason I can connect to my Japanese (MKK1) AP
on channel 6 from my USB WiFi adapter (regulatory region France, channels
10-13) once I've enabled international roaming is because my AP actually
broadcasts its own regulatory region! I believe if an AP doesn't broadcast
this information then the Atmel firmware wont let you connect to a channel
outside the adapter's own regulatory region. Have you got access to a PCMCIA
card (eg: rebadged Orinoco, eg: Avaya) that you could use in true monitor
mode with Ethereal to analyse the beacon frames from your AP? Can anyone
else connect to your AP?

Hope that helps & good luck!

Balint

> -----Original Message-----
> From: [email protected] [mailto:at76c503a-user-
> [email protected]] On Behalf Of Haydn Haines
> Sent: Wednesday, 5 January 2005 8:26 AM
> To: [email protected]
> Subject: [at76c503a-user] Can't find AP (BT voyager 1010USB, Fedora Core 3
> k: 2.6.10)
> 
> Hi All,
> 
> I'm having problems getting the berlios driver working and would really
> appreciate some help. To me the problem appears to be a problem matching
> my wireless card & access points settings - but I'm not sure what I'm
> missing.
> 
> NOTE: This is a dual boot machine and the nic can see the AP with
> excellent reception  in win XP so that is not an issue.
> 
> FYI I'm running:
> 
>     Distro:               Fedore Core 3
>     Kernel:              2.6.10 (no patches)
>     Driver ver:         v1.72? Unsure - CVS from approx 2 weeks ago
>     wlan0 Device:    BT Voyager 1010 USB (VID: 0x69a, PID: 0x821)
>     AP:                    BT Voyager 2020
> 
> After make; make install is succesful and plugging in the device
> everything appears ok:
> 
> [root@U4ea log]# tail -5 messages
> Jan  4 19:27:02 U4ea kernel: usb 3-1: new full speed USB device using
> uhci_hcd and address 6
> Jan  4 19:27:03 U4ea kernel: /usr/todo/at76c503a/at76c503.c: $Id:
> at76c503.c,v 1.72 2004/10/19 20:45:25 jal2 Exp $ compiled Jan  4 2005
> 17:46:43
> Jan  4 19:27:03 U4ea kernel: /usr/todo/at76c503a/at76c503.c: firmware
> version 0.90.0 #44 (fcs_len 4)
> Jan  4 19:27:03 U4ea kernel: /usr/todo/at76c503a/at76c503.c: device's
> MAC 00:90:96:58:65:29, regulatory domain MKK1 (Japan) (id 65)
> Jan  4 19:27:03 U4ea kernel: /usr/todo/at76c503a/at76c503.c: registered
> wlan0
> 
> [root@U4ea log]# lsmod |grep at76
> at76c503_i3861         32772  0
> at76c503              100576  1 at76c503_i3861
> at76_usbdfu             6020  1 at76c503
> 
> 
> And the configuration also looks fine:
> 
> [root@U4ea log]# iwpriv wlan0 set_debug 0x180003
> [root@U4ea log]# iwconfig wlan0 mode managed channel 1 essid greenhill
> [root@U4ea log]# iwconfig wlan0
> wlan0     IEEE 802.11-DS  ESSID:"greenhill"  Nickname:"okuwlan"
>           Mode:Managed  Frequency:2.412GHz  Access Point:
> 00:00:00:00:00:00
>           Bit Rate:11Mb/s   Tx-Power=15 dBm
>           Retry limit:8   RTS thr=1536 B   Fragment thr=1536 B
>           Encryption key:off
>           Power Management:off
>           Link Quality:0  Signal level:0  Noise level:0
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
> 
> 
> [root@U4ea log]# ifconfig wlan0 netmask 255.255.255.240 192.168.1.5
> [root@U4ea log]# ifconfig wlan0
> wlan0     Link encap:Ethernet  HWaddr 00:90:96:58:65:29
>           inet addr:192.168.1.5  Bcast:192.168.1.255  Mask:255.255.255.240
>           inet6 addr: fe80::290:96ff:fe58:6529/64 Scope:Link
>           UP BROADCAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 b)  TX bytes:168 (168.0 b)
> 
> 
> As soon as I've run ifconfig my /var/log/kern.debug file starts filling
> up with unsucessful scans:
> 
> [root@U4ea log]# tail -15 kern.debug
> Jan  4 19:32:38 U4ea kernel: /usr/todo/at76c503a/at76c503.c: wlan0
> find_matching_bss: returned 00000000
> Jan  4 19:32:38 U4ea kernel: /usr/todo/at76c503a/at76c503.c: wlan0:
> state 6 -> 1 (SCANNING)
> Jan  4 19:32:38 U4ea kernel: /usr/todo/at76c503a/at76c503.c: wlan0:
> start_scan (use_essid = 0, intl = 0, channel = 1, probe_delay = 10000,
> scan_min_time = 10, scan_max_time = 120)
> Jan  4 19:32:38 U4ea kernel: /usr/todo/at76c503a/at76c503.c: wlan0
> handle_mgmt_timeout_scan:2021 got cmd_status 1 (istate 1, scan_runs 2)
> Jan  4 19:32:38 U4ea kernel: /usr/todo/at76c503a/at76c503.c: wlan0 BSS
> table (curr=00000000, new=00000000):
> Jan  4 19:32:38 U4ea kernel: /usr/todo/at76c503a/at76c503.c: wlan0:
> start_scan (use_essid = 1, intl = 0, channel = 1, probe_delay = 10000,
> scan_min_time = 10, scan_max_time = 120)
> Jan  4 19:32:38 U4ea kernel: /usr/todo/at76c503a/at76c503.c: wlan0
> handle_mgmt_timeout_scan:2021 got cmd_status 1 (istate 1, scan_runs 3)
> Jan  4 19:32:38 U4ea kernel: /usr/todo/at76c503a/at76c503.c: wlan0 BSS
> table (curr=00000000, new=00000000):
> Jan  4 19:32:38 U4ea kernel: /usr/todo/at76c503a/at76c503.c: wlan0:
> state 1 -> 6 (JOINING)
> Jan  4 19:32:38 U4ea kernel: /usr/todo/at76c503a/at76c503.c: wlan0
> find_matching_bss: returned 00000000
> Jan  4 19:32:38 U4ea kernel: /usr/todo/at76c503a/at76c503.c: wlan0:
> state 6 -> 1 (SCANNING)
> Jan  4 19:32:38 U4ea kernel: /usr/todo/at76c503a/at76c503.c: wlan0:
> start_scan (use_essid = 0, intl = 0, channel = 1, probe_delay = 10000,
> scan_min_time = 10, scan_max_time = 120)
> Jan  4 19:32:38 U4ea kernel: /usr/todo/at76c503a/at76c503.c: wlan0
> handle_mgmt_timeout_scan:2021 got cmd_status 1 (istate 1, scan_runs 2)
> Jan  4 19:32:38 U4ea kernel: /usr/todo/at76c503a/at76c503.c: wlan0 BSS
> table (curr=00000000, new=00000000):
> Jan  4 19:32:38 U4ea kernel: /usr/todo/at76c503a/at76c503.c: wlan0:
> start_scan (use_essid = 1, intl = 0, channel = 1, probe_delay = 10000,
> scan_min_time = 10, scan_max_time = 120)
> 
> 
> I've also tried to set the AP manually with iwconfig, but it still shows
> 00:00:00:00:00:00 for the AP after running:
> 
> [root@U4ea ~]# iwconfig wlan0 ap 00:90:96:62:F7:C3
> 
> 
> Please could someone advise me what I should try next to troubleshoot
> the problem? If you require any further logs please ask and I shall post
> them asap.
> 
> Thanks in advance for your help,
> 
> Haydn.
> 
> _______________________________________________
> at76c503a-user mailing list
> [email protected]
> http://lists.berlios.de/mailman/listinfo/at76c503a-user