From: Thomas Ilnseher <illth@gmx.de>
To: linux-wireless@vger.kernel.org
Subject: b43 doesn't reset hardware when loaded/unloaded [severity: minor]
Date: Mon, 04 Feb 2008 20:32:55 +0100 [thread overview]
Message-ID: <1202153575.8270.7.camel@note.localnet> (raw)
Hi!
I upgraded my kernel to 2.6.24, and
so I also upgraded from bcm43xx to b43.
There used to be a problem with bcm43xx that after
resuming from Supend-To-Ram, wireless didn't work anymore.
This however could be fixed with bcm43xx using the following
sequence:
killall dhcpcd
killall wpa_supplicant
ifconfig wlan0 down #nb: the if was renamed from eth1 to wlan0 via udev
rmmod bcm43xx
modprobe bcm43xx
ifconfig wlan0 up
wpa_supplicant -iwlan0 -Dwext -c/etc/wpa_supplicant/wpa_supplicant.conf\
-B -P/var/run/wpa_supplicant.pid
dhcpcd wlan0
It doesn't work with b43. (of course replacing bcm43xx with b43).
I *assume* that the core isn't completely reseted on insmod'ing.
regards,
tom
PS: keep the good work!
also, tux-on-ice works, so this is just a minor annoyance.
--
Thomas Ilnseher <illth@gmx.de>
next reply other threads:[~2008-02-04 19:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 19:32 Thomas Ilnseher [this message]
2008-02-04 20:06 ` b43 doesn't reset hardware when loaded/unloaded [severity: minor] Stefano Brivio
2008-02-04 20:12 ` Michael Buesch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1202153575.8270.7.camel@note.localnet \
--to=illth@gmx.de \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).