#1711: Netgear WG511T (AR5212) not working for kernels past 2.6.18
----------------------------------+-----------------------------------------
Reporter: anonymous | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: madwifi: driver | Version: trunk
Resolution: | Keywords:
Patch_attached: 0 |
----------------------------------+-----------------------------------------
Changes (by mentor):
* summary: Netgear WG511T (AR5212) not working for kernels past 2.2.18
=> Netgear WG511T (AR5212) not working for
kernels past 2.6.18
Old description:
> I have several time now built new kernels 2.2.19, 2.2.20, 2.2.21, etc
> each time updating mad wifi currently I have latest 'svn r3085'. In each
> case the modules load just fine and the card connects to the ap. This is
> true at home with wpa and at cafe's with no encryption. There is no
> indication of anything wrong in the logs, everything looks good. BUT you
> pinging the ap just fails as does any attempt to lookup a name, etc. In
> other words the card connects just fine, but then seems to utterly fail
> at any further communication with the ap.
>
> For example, at home I connect and get assigned the address 192.168.1.4 I
> can see that the card is connected from my computer with iwconfig and
> from another computer I can check that the ap thinks my card is
> connected, but I cannot access the ap or anything else on the web from my
> computer.
>
> About this time the kernel changed to a new wireless interface - new
> modules - mac80211, ieee80211, and cfg80211. There must be some obvious
> way to make things work again, but I cannot find any instructions or
> others having these problems.
>
> I'll attach my kernel configuration...
New description:
I have several time now built new kernels 2.6.19, 2.6.20, 2.6.21, etc each
time updating Madwifi currently I have latest 'svn r3085'. In each case
the modules load just fine and the card connects to the AP. This is true
at home with WPA and at cafe's with no encryption. There is no indication
of anything wrong in the logs, everything looks good, but you pinging the
AP just fails as does any attempt to lookup a name, etc. In other words
the card connects just fine, but then seems to utterly fail at any further
communication with the AP.
For example, at home I connect and get assigned the address 192.168.1.4; I
can see that the card is connected from my computer with iwconfig and from
another computer, I can check that the AP thinks my card is connected.
However, I cannot access the AP or anything else on the web from my
computer.
About this time the kernel changed to a new wireless interface - new
modules - mac80211, ieee80211, and cfg80211. There must be some obvious
way to make things work again, but I cannot find any instructions or
others having these problems.
I'll attach my kernel configuration...
Comment:
Updated description
--
Ticket URL: <http://madwifi.org/ticket/1711#comment:2>
madwifi.org <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
