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
tha
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
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
On Fri, 22 Jul 2005 14:46:46 +0100, Sevan / Venture37 wrote:
>I had the same problem, It turned out to be the whitelable oem Atheros card
>that I was using.
>
>http://www.mail-archive.com/misc@openbsd.org/msg04338.html
>
>
Well my dmesg lines don't look like either set of yours BUT disabling
802
- Original Message -
From: Sevan / Venture37 <[EMAIL PROTECTED]>
> I had the same problem, It turned out to be the whitelable oem
> Atheros card
> that I was using.
>
> http://www.mail-archive.com/misc@openbsd.org/msg04338.html
Does the above dmesg show the non-working card, and if so,
I had the same problem, It turned out to be the whitelable oem Atheros card
that I was using.
http://www.mail-archive.com/misc@openbsd.org/msg04338.html
I just laid hands on a Netgear WAG311 (as seen in the dmesg below).
The OS installed was i386 GENERIC snapshot 2005-07-12 and during
install I merely gave the ath0 an IP and left the final config until
post install. Lucky choice.
Putting in a hostname.ath0 line just like the example in the man pag
7 matches
Mail list logo
