On Sat, 23 Jul 2005 18:59:13 +1000, Damien Miller wrote: >Rod.. Whitworth wrote: >> Well my dmesg lines don't look like either set of yours BUT disabling >> 802.11a didn't fix it but disabling 802.11g as well leaves me with a >> working 11b. After I paid for a brandname a/b/g, dammit! >> >> One day there will be hardware makers across the range of product lines >> that will be trying as hard as OpenBSD developers to attain perfection >> and open docs, sigh.... > >There are known a/g problems on ath(4), IIRC reyk@ is actively looking >at them. > >-d >
Thanx Damien, I'd have bet on that being true. If only the distances between us were smaller I'd have volunteered to help because originally I'm a hardware guy and I could have done testing stuff if we both had the same card and he needed somebody with a (small) lab who could thrash it a bit. Meanwhile, knowing how frustrating it can be dealing with hardware that is not fully specced, I'm making sure not to put <any> pressure on him for solutions. He will do what he can do and in his own good (very good from what I've seen so far) time. Reyk, if you are reading this and need any testing done you can find me here: ash1 at witworx dot no spam com I have Prism 2.5 cards for compatibility tests plus an IBM ^H^H^H Lenovo R50e with an Atheros AR5212 that works fine on OpenBSD 3.7 current 050712 so I can see if a and g work too. I haven't tried it as an AP, hmmm, is that a valuable datum too? I don't have another 5212 to test it against but if it doesn't lock up on me we will know something we don't know now. No demands, no expected scheduled dates, no abuse if it can't be done. Optimism and hope is all. Thanks for work so far. Rod/ In the beginning was The Word and The Word was Content-type: text/plain The Word of Rod. Do NOT CC me - I am subscribed to the list. Replies to the sender address will fail except from the list-server.
