Bug 94914 – madwifi-bsd-0.1_pre20050602 (New Package)

• Product: Gentoo Linux
• Status: RESOLVED WONTFIX

[Description phaidros 2005-06-03 06:17:16 UTC]

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 ;)

[Comment 1 phaidros 2005-06-03 06:18:37 UTC]

forgotten: of course madwifi-bsd works for me now like a charm!

[Comment 2 Stefan Schweizer (RETIRED) 2005-06-03 07:20:02 UTC]

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)

[Comment 3 Stefan Schweizer (RETIRED) 2005-06-04 04:17:04 UTC]

Created attachment 60568 [details]
madwifi-bsd-0.1_pre20050602.ebuild

proposed ebuild, can you please report if it works for you correctly?

[Comment 4 Stefan Schweizer (RETIRED) 2005-06-04 08:54:03 UTC]

thanks fixed

[Comment 5 solar (RETIRED) 2005-06-04 09:12:52 UTC]

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 ?

[Comment 6 Henrik Brix Andersen 2005-06-04 10:32:56 UTC]

This seems like the natural solution to me.

[Comment 7 phaidros 2005-09-13 03:06:27 UTC]

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.

[Comment 8 Stefan Schweizer (RETIRED) 2005-09-13 04:07:28 UTC]

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.

[Comment 9 phaidros 2005-09-13 11:09:43 UTC]

> so you will get the latest version with
> renaming the madwifi-driver ebuild.

renaming to what?

[Comment 10 Stefan Schweizer (RETIRED) 2005-09-13 11:14:21 UTC]

e.g. to madwifi-driver-20050913.ebuild .. depends on what version you want to run.

[Comment 11 phaidros 2005-09-13 11:22:43 UTC]

(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.

[Comment 12 Stefan Schweizer (RETIRED) 2005-09-13 11:28:14 UTC]

# 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.

[Comment 13 HazelMiller 2021-07-16 09:32:21 UTC]

It is an amazing post https://bit.ly/3z53ohW