From: Noel Milton Vega <nmvega@computingarchitects.com>
To: "Ozan Çağlayan" <ozan@pardus.org.tr>
Cc: julian.calaby@gmail.com, linux-wireless@vger.kernel.org
Subject: Re: Need Linux driver (preferably 64 bit) for "Intel Corporation Centrino Advanced-N 6230 (rev 34)" WiFI & Bluetooth card ...
Date: Wed, 9 Feb 2011 23:21:57 -0800 (PST) [thread overview]
Message-ID: <762759.49884.qm@web36101.mail.mud.yahoo.com> (raw)
In-Reply-To: <201102100821.39020.ozan@pardus.org.tr>
One more time... hopefully this one doesn't wrap around
on anyone on this list (apologies for the repeat send).
Hello Ozan:
You know that's actually a great point. You just reminded
me of something! I have noticed that, while the laptop
Bluetooth indicator light does toggle On-and-Off each
time I press Fn-12; the WiFi laptop indicator light does
*not*. It has never turned on (*ever*), no matter how many
times I press Fn-11 (the key combination to toggle WiFi
On-and-Off). I just assumed it was the driver issue I
was having (and it may still be).
Here are your rfkill outputs...
Executed when Bluetooth light was on - RX/TX enabled; WiFi light is off.)
root@p170hm# rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Note: Don't let the above 2nd bluetooth interface
beguile you. This is a tiny bluetooth dongle I
temporarily attached to a USB port because this
same N-6320 card also provides the laptop's bluetooth
capability. But being connected to a USB port, Fn-12
will not affect it showing up in the output of rfkill
(see later below - it will remain in the output).
1: hci1: Bluetooth
Soft blocked: no
Hard blocked: no
(Executed when Bluetooth light was off -- RX/TX disabled; WiFi light is off)
root@# rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
In either case, I see no reference to a WiFi device.
Hope that helps some more.
Regards & Thanks,
Noel
----- Original Message ----
> From: Ozan Çağlayan <ozan@pardus.org.tr>
> To: Noel Milton Vega <nmvega@computingarchitects.com>
> Cc: Julian Calaby <julian.calaby@gmail.com>; linux-wireless@vger.kernel.org
> Sent: Thu, February 10, 2011 1:21:38 AM
> Subject: Re: Need Linux driver (preferably 64 bit) for "Intel Corporation
>Centrino Advanced-N 6230 (rev 34)" WiFI & Bluetooth card ...
>
> Perşembe 10 Şubat 2011 günü (saat 07:25:12) Noel Milton Vega şunları
yazmıştı:
> > Hi Julian,
> >
> > Thank you for the extended reply. It's appreciated. Your output wish is
> > my command. Here they are (and then some):
>
> Can you run
>
> rfkill list
>
> and send the output? Are there any WLAN toggles on your laptop (a hard switch
>or Fn + Fx combination)?
> If yes try playing with them.
>
> ---
> Ozan Çağlayan
> TUBITAK/UEKAE - Pardus Linux
> http://www.pardus.org.tr/eng
>
next prev parent reply other threads:[~2011-02-10 7:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 3:31 FWD: Need Linux driver (preferably 64 bit) for "Intel Corporation Centrino Advanced-N 6230 (rev 34)" WiFI & Bluetooth card Noel Milton Vega
2011-02-10 4:15 ` Julian Calaby
2011-02-10 5:25 ` Noel Milton Vega
2011-02-10 6:11 ` Julian Calaby
2011-02-10 6:21 ` Ozan Çağlayan
2011-02-10 7:21 ` Noel Milton Vega [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-10 6:59 Noel Milton Vega
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=762759.49884.qm@web36101.mail.mud.yahoo.com \
--to=nmvega@computingarchitects.com \
--cc=julian.calaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=ozan@pardus.org.tr \
/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.