Now that I've managed to free my head from betwixt my hindquarters the driver
works perfectly. I had my default gateway set to the right IP but through my
eth0 card so all traffic was going through the wired network instead of the
wireless card.
It's working great now! Is this code going to be merged into the kernel?
Keep up the great work!
--Steev
Quoting [email protected]:
> Sorry about the HTML messages...
> Here's what I see while debug is set to "iwpriv wlan0 set_debug 0x180003":
> Jul 23 23:05:51 simian /usr/src/at76c503a/at76c503.c: wlan0 BSS table
> (curr=00000000, new=00000000):
> Jul 23 23:05:51 simian /usr/src/at76c503a/at76c503.c: 0xd8cf0458: bssid
> 00:0c:41:d2:9b:fa channel 6 ssid supermonkeycollider
> (73757065726D6F6E6B6579636F6C6C69646572) capa x0401 rates 82 84 8B 96 24 30
> 48
> 6C rssi 48 link 0 noise 0
> Jul 23 23:05:51 simian /usr/src/at76c503a/at76c503.c: wlan0 BSS table
> (curr=00000000, new=00000000):
> Jul 23 23:05:51 simian /usr/src/at76c503a/at76c503.c: 0xd8cf0458: bssid
> 00:0c:41:d2:9b:fa channel 6 ssid supermonkeycollider
> (73757065726D6F6E6B6579636F6C6C69646572) capa x0401 rates 82 84 8B 96 24 30
> 48
> 6C rssi 43 link 0 noise 0
> Jul 23 23:05:51 simian /usr/src/at76c503a/at76c503.c: wlan0: state 1 -> 6
> (JOINING)
> Jul 23 23:05:51 simian /usr/src/at76c503a/at76c503.c: wlan0
> find_matching_bss:
> returned d8cf0458
> Jul 23 23:05:51 simian /usr/src/at76c503a/at76c503.c: wlan0 join addr
> 00:0c:41:d2:9b:fa ssid supermonkeycollider type 2 ch 6 timeout 2000
> Jul 23 23:05:52 simian /usr/src/at76c503a/at76c503.c: wlan0: state 6 -> 2
> (AUTHENTICATING)
> Jul 23 23:05:52 simian /usr/src/at76c503a/at76c503.c: wlan0: state 2 -> 3
> (ASSOCIATING)
> Jul 23 23:05:52 simian /usr/src/at76c503a/at76c503.c: wlan0: state 3 -> 6
> (JOINING)
> Jul 23 23:05:52 simian /usr/src/at76c503a/at76c503.c: wlan0
> find_matching_bss:
> returned 00000000
> Jul 23 23:05:52 simian /usr/src/at76c503a/at76c503.c: wlan0: state 6 -> 1
> (SCANNING)
> Jul 23 23:06:02 simian /usr/src/at76c503a/at76c503.c: wlan0 BSS table
> (curr=00000000, new=00000000):
> Jul 23 23:06:02 simian /usr/src/at76c503a/at76c503.c: 0xd8cf0458: bssid
> 00:0c:41:d2:9b:fa channel 6 ssid supermonkeycollider
> (73757065726D6F6E6B6579636F6C6C69646572) capa x0401 rates 82 84 8B 96 24 30
> 48
> 6C rssi 47 link 0 noise 0
> Jul 23 23:06:03 simian /usr/src/at76c503a/at76c503.c: wlan0 BSS table
> (curr=00000000, new=00000000):
> Jul 23 23:06:03 simian /usr/src/at76c503a/at76c503.c: 0xd8cf0458: bssid
> 00:0c:41:d2:9b:fa channel 6 ssid supermonkeycollider
> (73757065726D6F6E6B6579636F6C6C69646572) capa x0401 rates 82 84 8B 96 24 30
> 48
> 6C rssi 49 link 0 noise 0
> Jul 23 23:06:03 simian /usr/src/at76c503a/at76c503.c: wlan0: state 1 -> 6
> (JOINING)
> Jul 23 23:06:03 simian /usr/src/at76c503a/at76c503.c: wlan0
> find_matching_bss:
> returned d8cf0458
> Jul 23 23:06:03 simian /usr/src/at76c503a/at76c503.c: wlan0 join addr
> 00:0c:41:d2:9b:fa ssid supermonkeycollider type 2 ch 6 timeout 2000
> Jul 23 23:06:03 simian /usr/src/at76c503a/at76c503.c: wlan0: state 6 -> 2
> (AUTHENTICATING)
> Jul 23 23:06:03 simian /usr/src/at76c503a/at76c503.c: wlan0: state 2 -> 3
> (ASSOCIATING)
> Jul 23 23:06:03 simian /usr/src/at76c503a/at76c503.c: wlan0: state 3 -> 6
> (JOINING)
> Jul 23 23:06:03 simian /usr/src/at76c503a/at76c503.c: wlan0
> find_matching_bss:
> returned 00000000
> Jul 23 23:06:03 simian /usr/src/at76c503a/at76c503.c: wlan0: state 6 -> 1
> (SCANNING)
> Jul 23 23:06:07 simian /usr/src/at76c503a/at76c503.c: wlan0: state 1 -> 0
> (INIT)
> Jul 23 23:06:07 simian dhcpcd[2433]: terminating on signal 2
>
> It does seem to see my AP and occasionaly I do see the AP when I do `iwlist
>
> wlan0 scanning` but the interface never stays associated with my AP (linksys
>
> wireless router).
>
> I did have this working with the 2.4 kernel just last night but after I
> upgraded and recompiled with the latest code from CVS it just doesn't work.
>
>
> I did read the troubelshooting page but I am not using UHCI or usb_UHCI:
>
> ohci_hcd 18308 0
> emu10k1_gp 2688 0
> gameport 3712 1 emu10k1_gp
> snd_emu10k1 90248 0
> snd_rawmidi 19876 1 snd_emu10k1
> snd_pcm 82824 1 snd_emu10k1
> snd_timer 20868 1 snd_pcm
> snd_seq_device 6536 2 snd_emu10k1,snd_rawmidi
> snd_ac97_codec 64388 1 snd_emu10k1
> snd_page_alloc 8840 2 snd_emu10k1,snd_pcm
> snd_util_mem 3456 1 snd_emu10k1
> snd_hwdep 7172 1 snd_emu10k1
> snd 46308 8
>
snd_emu10k1,snd_rawmidi,snd_pcm,snd_timer,snd_seq_device,snd_ac97_codec,snd_util_mem,snd_hwdep
>
> e100 28800 0
> mii 4224 1 e100
> at76c505_rfmd2958 41220 0
> at76c503 80736 1 at76c505_rfmd2958
> usbdfu 5508 1 at76c503
> usbhid 29504 0
> aic7xxx 192088 0
> nvidia 4818292 14
> uhci_hcd 28176 0
> intel_agp 16796 1
> agpgart 26536 1 intel_agp
> sbp2 20616 0
> ohci1394 30340 0
> ieee1394 90292 2 sbp2,ohci1394
> usb_storage 25984 0
> usbcore 95712 9
> ohci_hcd,at76c505_rfmd2958,at76c503,usbdfu,usbhid,uhci_hcd,usb_storage
>
> should I mess with ohci_hcd and try another module?
>
> Thanks for your help!
> --Steev
>
> Quoting Joerg Albiwert <[email protected]>:
>
> > Hi,
> >
> >
> > On Fri, 23 Jul 2004, Steve Neuharth wrote:
> >
> > > ...
> > > I cannot, however, see my access point:
> > > ...
> > > The AP IS up and running, operating on channel 6, I use my laptop on it
>
> > just
> > > fine.
> > >
> > > I'm pretty sure that this is just a "user error" typa thing bit I'm just
>
> > > plain stuck. Does anyone have any ideas?
> >
> > Please turn on debugging in the driver ("iwpriv wlan0 set_debug 0x180003")
>
> > and try again. Have you read the troubleshooting section linked on
> > http://at76c503a.berlios.de ?
> >
> > BTW, please turn off _HTML_ postings.
> >
> > /Jörg
> >
> >
> > _______________________________________________
> > at76c503a-user mailing list
> > [email protected]
> > http://lists.berlios.de/mailman/listinfo/at76c503a-user
> >
> >
>
>
>
> _______________________________________________
> at76c503a-user mailing list
> [email protected]
> http://lists.berlios.de/mailman/listinfo/at76c503a-user
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.