Summary: | madwifi-driver 0.1_pre20050420 has performance issues | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Olliver Schinagl <oliver> |
Component: | New packages | Assignee: | Mobile Herd (OBSOLETE) <mobile+disabled> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | horton, solar |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 94914 | ||
Bug Blocks: |
Description
Olliver Schinagl
2005-05-25 16:23:17 UTC
We did not write the software but rather are the packagers. Please check with upstream. Closing as UPSTREAM. which is why i'm saying the current cvs snapshot package doesn't work properly under load. We need to either go back one version, or go up one if possible. This clearly goes under gentoo packaging. Are you saying that this is fixed in upstream CVS? I don't know. I do know that the current version has this problem and it should be masked or similar. My proposal therefore is go back one version. I don't know if it is fixed in the current CVS. But since nobody can even confirm this issue ... What card are you powering with madwifi? It has already been explained in the mailing list (see the archive). The result is that development in madwifi head cvs has stopped and only moves on in madwifi-bsd. The old developers of madwifi-head are not active in madwifi project (workin on bsd atheros driver version) anymore and now we have chosen to take over the responsibility for that. Furthermore, anyone who thinks he is able to contribute (coding, documentation, howtos, bug reports) to madwifi is welcome. -- Regards, Sebastian Weitzel Hey guys, I think it's update time. I have a: 0000:02:02.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01) which came with my IBM T42 thinkpad. Please do this. emerge sync emerge unmerge madwifi-driver madwifi-tools ACCEPT_KEYWORDS="~x86" emerge -v madwifi-bsd Using madwifi-bsd should correct your problem. We are currently working on updating madwifi* horton, thanks. I think this answer is sufficent enough to close this bug. |