From: Philippe De Muyter <phdm@macqel.be>
To: Matthew Garrett <mjg@redhat.com>
Cc: Dan Williams <dcbw@redhat.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
linux-wireless@vger.kernel.org
Subject: Re: b43 'hardware blocked' but only keyboard/led touch button
Date: Tue, 30 Mar 2010 21:26:29 +0200 [thread overview]
Message-ID: <20100330192629.GA24060@frolo.macqel> (raw)
In-Reply-To: <20100330171139.GA28367@srcf.ucam.org>
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
On Tue, Mar 30, 2010 at 06:11:39PM +0100, Matthew Garrett wrote:
> On Tue, Mar 30, 2010 at 09:47:37AM -0700, Dan Williams wrote:
>
> > It could be that hp-wmi doesn't have support for these models yet, or
> > that the dv6-1300sb is simply completely different. But for example, on
> > my Elitebook 2530p, there's a softswitch that pokes BIOS, and when BIOS
> > is softkilled, the onboard wifi becomes hardkilled. To unkill, I need
> > to unblock BIOS, which then either unblocks wifi, or turns the wifi
> > hardkill into a softkill. Convoluted.
>
> Yeah. I'd be interested in seeing the output of acpidump on this
> machine, but right now it sounds like b43 is behaving correctly - the
> fact that the light is out implies that the bios is killing it.
Here you are :
linux-vcsl:~ # acpidump > /tmp/acpidump.out
Wrong checksum for DSDT!
Wrong checksum for SLIC
Wrong checksum for SSDT
Wrong checksum for DSDT!
Wrong checksum for SLIC!
Wrong checksum for SSDT!
acpidump.out is attached (tar-compressed)
I must also add that I currently cannot boot without acpi=off
Philippe
--
Philippe De Muyter phdm at macqel dot be Tel +32 27029044
Macq Electronique SA rue de l'Aeronef 2 B-1140 Bruxelles Fax +32 27029077
[-- Attachment #2: acpidump.tgz --]
[-- Type: application/x-compressed-tar, Size: 75518 bytes --]
next prev parent reply other threads:[~2010-03-30 19:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 20:12 b43 'hardware blocked' but only keyboard/led touch button Philippe De Muyter
2010-03-29 23:10 ` Larry Finger
2010-03-30 7:34 ` Philippe De Muyter
2010-03-30 16:47 ` Dan Williams
2010-03-30 17:11 ` Matthew Garrett
2010-03-30 19:26 ` Philippe De Muyter [this message]
2010-03-30 19:31 ` Matthew Garrett
2010-03-30 20:00 ` Philippe De Muyter
2010-03-30 20:06 ` Matthew Garrett
2010-03-30 20:43 ` Philippe De Muyter
2010-04-19 11:53 ` Philippe De Muyter
2010-04-19 14:51 ` Matthew Garrett
2010-04-19 15:00 ` Philippe De Muyter
2010-04-19 15:06 ` Matthew Garrett
2010-04-24 5:42 ` Philippe De Muyter
2010-04-24 15:21 ` Matthew Garrett
2010-04-24 19:56 ` Philippe De Muyter
2010-04-24 20:02 ` Matthew Garrett
2010-04-25 19:50 ` Philippe De Muyter
2010-04-25 20:11 ` Larry Finger
2010-05-01 12:17 ` BCM4312 802.11b/g LP-PHY (rev 01) dma & led problems Philippe De Muyter
2010-05-01 16:04 ` Gábor Stefanik
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=20100330192629.GA24060@frolo.macqel \
--to=phdm@macqel.be \
--cc=Larry.Finger@lwfinger.net \
--cc=dcbw@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mjg@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.