linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Noel Milton Vega <nmvega@computingarchitects.com>
To: Julian Calaby <julian.calaby@gmail.com>, ozan@pardus.org.tr
Cc: linux-wireless@vger.kernel.org
Subject: Re: SOLVED -- Need Linux driver (preferably 64 bit) for "Intel Corporation Centrino Advanced-N 6230 (rev 34)" WiFI & Bluetooth card ...
Date: Sat, 12 Feb 2011 10:43:37 -0800 (PST)	[thread overview]
Message-ID: <75608.46987.qm@web36108.mail.mud.yahoo.com> (raw)
In-Reply-To: <875258.44241.qm@web36104.mail.mud.yahoo.com>

Hello:

It is working now.

Integrating stable capat-wireless modules into the stock Fedora 14 (64bit)
kernel (2.6.35.10-74.fc14.x86_64) did not resolve the issue, so I turned my 
attention to compiling an entirely new kernel. Note that I only tried 
compat-wireless
version 2.6.35-1 (and none newer), as that was the only one whose compilation 
would
result in an iwlagn.ko (etc.) module being created (... compilations of newer
ones did not).

So after downloading and compiling kernel version 2.6.38-rc4 (kernel.org) (and
manually integrating other necessary subsystems too, like compiling the nVidia
graphics driver while booted to that kernel), I was finally able to get "wlan0"
up via the included "iwlagn.ko (etc)" driver, as confirmed by "ethtool -i 
wlan0".

I do, however, get the following *error* message when performing an
"ifconfig wlan0 up", but I suspect that that is because the hardware switch
(it's actually not a physical switch), might be in the blocked/off mode
when doing so:

    SIOCSIFFLAGS: Operation not possible due to RF-kill

Unless you look at the output of "rfkill list", it's hard to tell what state
that hardware switch in when the indicator LED is off because it only goes on
after two conditions are met: (1) the hardware switch is unblocked, and then
you perform an "ifconfig wlan0 up" (seemingly in that order). So basically I
do a "ifconfig wlan0 up", and if the above error occurs, hit "Fn + F12" to
toggle the RF switch, and then do the "ifconfig wlan0  up" again. That
combination seems to work (it was 4am, so I can't recall all right now).

If someone knows how to, -on boot-, automatically enable/unblock that RF
hardware switch, I'd love to know (probably an entry in modprobe.conf(5) - 
I'll search too).


So everything in this bleeding-edge laptop functions now, and I now can turn
my attention to it's purpose (compute intensive private cloud 
simulations).

Thank you again for your collective help (it was actually guidance in the
technical email exchanges that let to success).

Thanks & Best Regards,
Noel


      parent reply	other threads:[~2011-02-12 18:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-10 20:31 UPDATE -- Need Linux driver (preferably 64 bit) for "Intel Corporation Centrino Advanced-N 6230 (rev 34)" WiFI & Bluetooth card Noel Milton Vega
2011-02-10 21:25 ` John W. Linville
2011-02-10 23:08   ` Noel Milton Vega
2011-02-10 23:17     ` Larry Finger
2011-02-11  0:05 ` compat-wireless trial :: " Noel Milton Vega
2011-02-11  0:19   ` Julian Calaby
2011-02-11  0:30     ` Noel Milton Vega
2011-02-11  1:14     ` Noel Milton Vega
2011-02-12 18:43 ` Noel Milton Vega [this message]

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=75608.46987.qm@web36108.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 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).