Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 51208 - new madwifi_pre20040514 ebuild should be changed to 0515 or 0516
Summary: new madwifi_pre20040514 ebuild should be changed to 0515 or 0516
Status: VERIFIED TEST-REQUEST
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All All
: High normal (vote)
Assignee: Mobile Herd (OBSOLETE)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-16 07:48 UTC by Andrew Gaffney (RETIRED)
Modified: 2004-12-29 06:23 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Gaffney (RETIRED) gentoo-dev 2004-05-16 07:48:59 UTC
There was a major change committed to the madwifi CVS yesterday that fixes the 'ath0: NETDEV WATCHDOG: transmit timed out' messages for people with Atheros 5211 chipsets (most Atheros a/b cards) on the x86 platform. It was checked in around noon CDT on 20040515. I would give a URL to the message on the madwifi-users mailing list archive, but SF stopped archiving the list around April for some reason.
Comment 1 Peter Johanson (RETIRED) gentoo-dev 2004-05-17 19:15:21 UTC
Okay, thanks for the info. I will try to get an updated version in later this week, if not sooner.
Comment 2 solar (RETIRED) gentoo-dev 2004-09-06 12:38:51 UTC
madwifi-driver-0.1_pre20040906 and madwifi-tools-0.1_pre20040906 
are both in the tree now. This should work for everybody.

emerge rsync
ACCEPT_KEYWORDS=~x86 emerge madwifi-driver madwifi-tools

Please test and CLOSE appropriate bugs if this solves the problem anybody was
having.
Comment 3 Doug Goldstein (RETIRED) gentoo-dev 2004-09-22 09:47:12 UTC
Once again... Test Request since it's been 4 months and we've worked on this situation extensively.
Comment 4 Andrew Gaffney (RETIRED) gentoo-dev 2004-09-22 09:51:50 UTC
Sorry, I haven't really used my laptop in about 4 months. Even when I have, I already managed to get madwifi working, so I don't want to mess with it.
Comment 5 Henrik Brix Andersen 2004-12-29 06:23:18 UTC
Closing due to lack of feedback.