All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Broadcom card totally not visible for system (lspci)
Date: Tue, 30 Mar 2010 12:48:03 -0500	[thread overview]
Message-ID: <4BB23953.9010104@lwfinger.net> (raw)
In-Reply-To: <b170af451003301031yd06f559j85fd30417af32113@mail.gmail.com>

On 03/30/2010 12:31 PM, Rafa? Mi?ecki wrote:
> 
> Is this possible it's disabled in BIOS by default and needs execution
> of some ACPI command or sth to make it work?
> 
> Yeah, trying to find some other reason than faulty WiFi... It's weird
> it was working fine "before a moment" on Windows.

Winblows can fiddle with the "Wake-on-LAN" setting in the BIOS, but AFAIK, the
BCM4306 does not have this capability. If the BIOS has that setting, it should
be turned off.

Larry

WARNING: multiple messages have this Message-ID (diff)
From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: Broadcom card totally not visible for system (lspci)
Date: Tue, 30 Mar 2010 12:48:03 -0500	[thread overview]
Message-ID: <4BB23953.9010104@lwfinger.net> (raw)
In-Reply-To: <b170af451003301031yd06f559j85fd30417af32113@mail.gmail.com>

On 03/30/2010 12:31 PM, Rafał Miłecki wrote:
> 
> Is this possible it's disabled in BIOS by default and needs execution
> of some ACPI command or sth to make it work?
> 
> Yeah, trying to find some other reason than faulty WiFi... It's weird
> it was working fine "before a moment" on Windows.

Winblows can fiddle with the "Wake-on-LAN" setting in the BIOS, but AFAIK, the
BCM4306 does not have this capability. If the BIOS has that setting, it should
be turned off.

Larry


  reply	other threads:[~2010-03-30 17:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30 16:56 Broadcom card totally not visible for system (lspci) Rafał Miłecki
2010-03-30 16:56 ` Rafał Miłecki
2010-03-30 17:19 ` Larry Finger
2010-03-30 17:19   ` Larry Finger
2010-03-30 17:31   ` Rafał Miłecki
2010-03-30 17:31     ` Rafał Miłecki
2010-03-30 17:48     ` Larry Finger [this message]
2010-03-30 17:48       ` Larry Finger
2010-03-30 19:02       ` Pavel Roskin
2010-03-30 19:02         ` Pavel Roskin
2010-03-30 19:06         ` Rafał Miłecki
2010-03-30 19:06           ` Rafał Miłecki
2010-03-30 19:41           ` Pavel Roskin
2010-03-30 19:41             ` Pavel Roskin
2010-03-30 19:29         ` Johannes Berg
2010-03-30 19:29           ` Johannes Berg
2010-03-31  6:39   ` Holger Schurig

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=4BB23953.9010104@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=b43-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=zajec5@gmail.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.