after having alot of issues m=with madwifi driver in ad-hoc mode, which freezed my system regularly after 60 seconds, I contacted the madwifi guys and got the hint to try madwifi-bsd (http://madwifi.sourceforge.net/dokuwiki/doku.php?id=bsd). which is much more stable in ad-hoc and gets lately much more development than the HEAD branch. I'd suggest do include a madwifi-bsd ebuild, which should solve all people's ad-hoc problems. Reproducible: Always Steps to Reproduce: 1. iwconfig ath0 mode ad-hoc, ifconfig .. 2. connection works 3. after 60/80 seconds system freezes completely Actual Results: freeze Expected Results: no freeze ;)
forgotten: of course madwifi-bsd works for me now like a charm!
Do you know of a location of cvs snapshots? Or did you use cvs to check it out directly? Do you have an proposed ebuild? (Should be cvs.eclass-based in the second case)
Created attachment 60568 [details] madwifi-bsd-0.1_pre20050602.ebuild proposed ebuild, can you please report if it works for you correctly?
thanks fixed
Stefan looks like madwifi is dead and this -bsd branch is going to become the default. Perhaps we want to move -bsd into -driver and update -tools ?
This seems like the natural solution to me.
madwifi-bsd ebuild is gone. and I can't help but it looks madwifi-drivers is still the old (unmaintained) branch of the driver .. am I wrong or is madwifi-driver now using madwifi-bsd cvs and just the latest not masked ebuild (june?) for madwifi(-bsd) is gone?? I'm a little confused ;) p.
Madwifi bsd branch was merged into HEAD, so you will get the latest version with renaming the madwifi-driver ebuild. Or unmasking the latest ebuild that has problems with WPA.
> so you will get the latest version with > renaming the madwifi-driver ebuild. renaming to what?
e.g. to madwifi-driver-20050913.ebuild .. depends on what version you want to run.
(In reply to comment #10) > e.g. to madwifi-driver-20050913.ebuild .. depends on what version you want to run. !!! Couldn't download madwifi-cvs-snapshot-3--.tar.bz2. Aborting. where snapshot-$v is the last number of the date in the ebuild name. e.g. emerge -pv madwifi-driver-20050910 it says: !!! Couldn't download madwifi-cvs-snapshot-0--.tar.bz2. Aborting.
# cd /usr/portage/net-wireless/madwifi-driver # cp madwifi-driver-0.1_pre20050809-r1.ebuild madwifi-driver-0.1_pre20050913.ebuild # emerge -va madwifi-driver --digest Should not be that hard .. and please talk to me in IRC or ICQ if you cant handle that. This bug is closed.
It is an amazing post https://bit.ly/3z53ohW
