From: Larry Finger <Larry.Finger@lwfinger.net>
To: wireless <linux-wireless@vger.kernel.org>
Cc: "Bernhard M. Wiedemann" <bernhardout@lsmod.de>
Subject: Problem with AR5001 on eeepc900A after disable with RFKILL switch
Date: Tue, 20 Apr 2010 13:04:04 -0500 [thread overview]
Message-ID: <4BCDEC94.2080202@lwfinger.net> (raw)
This problem is reported at
https://bugzilla.novell.com/show_bug.cgi?id=595586.
Although not mentioned in the bug report, the kernel is 2.6.33.
The initial part of the report is as follows:
======================================================================
After disabling WLAN on Asus eeepc 900A using rfkill button (Fn+F2) it
does not get back into a working state without a reboot.
Reproducible: Always
Steps to Reproduce:
1. boot up eeepc900A with WLAN enabled
2. press Fn+F2 (rfkill button) to disable WLAN
3. press Fn+F2 again to enable WLAN
Actual Results:
-----
1. lspci before rfkill
01:00.0 Ethernet controller: Atheros Communications AR8121/AR8113/AR8114
Gigabit or Fast Ethernet (rev b0)
02:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless
Network Adapter (rev 01)
-----
2. lspci after rfkill
01:00.0 Ethernet controller: Attansic Technology Corp. Atheros
AR8121/AR8113/AR8114 PCI-E Ethernet Controller (rev b0)
02:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless
Network Adapter (rev ff)
======================================================================
The curious thing is that the lspci output is different for both the
wired and wireless cards.
Any ideas on why setting rfkill should change data in this way?
Thanks,
Larry
next reply other threads:[~2010-04-20 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 18:04 Larry Finger [this message]
2010-04-22 19:52 ` Problem with AR5001 on eeepc900A after disable with RFKILL switch Bob Copeland
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=4BCDEC94.2080202@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bernhardout@lsmod.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).