also sprach Kel Modderman <[EMAIL PROTECTED]> [2006.09.11.1207 +0200]:
> Can you please try the patch on madwifi.org ticket #776 [1] that reverts a
> scanning related "enhancement" that appears to help some, but hinder others.
Unfortunately, the patch does not address the problem.
--
.''`.
also sprach Matt Brown <[EMAIL PROTECTED]> [2006.09.11.1155 +0200]:
> Is there any chance that your access point is using an
> agere/orinoco/proxim chipset?
It's a Belkin, I have no idea what chipset it's using.
> If so you may be hitting http://madwifi.org/ticket/698
Sometimes it just works tho
On Monday 11 September 2006 19:24, martin f krafft wrote:
> Package: madwifi-source
> Version: 0.svnr1697.0.9.2-1
> Severity: important
>
> Ever since I upgraded to the madwifi-ng driver, it's become mostly
> unusable. I am using the latest 2.6.17 kernel from unstable. From
> time to time I get it
Hi Martin,
martin f krafft wrote:
> As said, from time to time it *does* work with the same
> configuration (-D madwifi, I never actually got it to work with
> wext). Also, other machines are associating fine with the AP, so it
> really seems to be an atheros problem.
Is there any chance that yo
Package: madwifi-source
Version: 0.svnr1697.0.9.2-1
Severity: important
Ever since I upgraded to the madwifi-ng driver, it's become mostly
unusable. I am using the latest 2.6.17 kernel from unstable. From
time to time I get it to work, but most of the time it cannot
establish an association with t
5 matches
Mail list logo
