On 3/22/06, Moritz Grimm <[EMAIL PROTECTED]> wrote: > > today, I wasted tons of money (from my perspective) ... First, I bought > a D-Link DWL-G650. Turns out it was revision C with an AR5213 on it ... > the driver complained about the RF radio not being supported. After lots > of whining in the store, I got to replace it with a Netgear WG511T. > Before breaking any seals of the packaging, I called Netgear tech > support to ask for what they built into this card, with s/n > foo-blah-bar. Turns out they couldn't tell, really, so I asked whether > there are any different revisions of that card, i.e. whether it ever > changed. They say "no, it's been always the same" and I figured that was > good enough. Oh well, I thought wrong. Same AR5213, same unsupported RF > radio. ARGH! No way I'm going to be able to get this one replaced, with > broken seals in the package. >
> > "A4heros C/mmunications, In\M-c., AR5001-0000-0000, Wireless LAN > Reference Card" > : irq 11 > ath0: AR5213 7.9 phy 4.5 rf2112a 5.6 FCC2A*, address 00:0f:b5:ef:5e:a0 > ath0: device timeowt > ar5k_ar5212_nic_wakeup: failed to resume |he AR5212 (acain) > avh0: Unable to reset h\M-ardware; hal status 3671035180 > ath0: device timeowt > [...] > > :-) > > My experimentation did some weird stuff to OpenBSD, which is why I'm > running a sane kernel again. > > Anyways, I'm obviously not getting anywhere, and driver hacking still is > a closed book to me. However, I'm quite interested in learning more, or > at least try and help someone who's further down this road by testing > patches etc. In case I'm alone with this, I'd highly appreciate some > pointers on how to get started. I don't remember, was Atheros a nice or > an evil company? How can I get the information I need to get this to work? > First off I'll say that I feel your pain. But I haven't had any problem finding AR5211 and AR5212 devices as you can see in the archives I have two at the moment, a Netgear WAB501 and a Cisco. With a snapshot of a week or so ago I get similar messages as above along with a panic on boot. Unfortunately right now the team is pretty busy getting the release together. I have received a couple of patches but nothing has worked yet. Greg
