linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Vas Dias <jason.vas.dias@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: HP6715b laptop's wireless radio on LED went off after 1st boot of 3.9.6 from 3.4.4 - please help / any ideas ?
Date: Thu, 27 Jun 2013 21:38:30 +0100	[thread overview]
Message-ID: <CALyZvKxCYaU47jb98FcbwNSMxnQ8pVCj17MYm0B3V99Uw2_nDA@mail.gmail.com> (raw)

After building and installing 3.9.6 kernel & modules on
my 2.2ghz HP6715b x86-64 Turion dual core laptop ,
which has always run Linux with no b43 wireless problems
since 2007, now has no access to its onboard broadcom 4311
wireless radio .  I had always used the b43
driver with the correct firmware installed
under /lib/firmware/b43 with b43-fwcutter
as per instructions at http://wireless.kernel.org/en/users/Drivers/b43
, which I've just now redone again, but since booting
3.9.6, which I believe resulted in a firmware download
via udev at first boot, the wireless radio "on" blue LED
indicator goes off after BIOS POST .  It has always been
the case that if the blue LED indicator is off after BIOS
POST ,  then the kernel does not see the device, and I
have no wireless until a hard poweroff and pressing
the touch sensitive wireless on button during BIOS POST.
But now the wireless LED goes on for @ 1 second during
BIOS POST , and never comes on again ,  and there are
no responses to touching wireless-on button after reboot,
though there are to other buttons next to it.  In short,
I've lost wireless access (and home internet access for
my pc - I'm sending this from my mobile) . Can anyone help?
How can I force the card to download the re-installed
b43-fwcutter firmware, if the device no longer appears
in lspci output?  Anyway to force the kernel to ignore
the wireless button ( it could be that the kernel & bios
think this button is in the off state - any way to force
its state to "on") ?  Any ideas / suggestions would be much
appreciated.
Thanks & Regards, Jason

                 reply	other threads:[~2013-06-27 20:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CALyZvKxCYaU47jb98FcbwNSMxnQ8pVCj17MYm0B3V99Uw2_nDA@mail.gmail.com \
    --to=jason.vas.dias@gmail.com \
    --cc=linux-kernel@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).