linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Noel Milton Vega <nmvega@nyceyes.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Julian Calaby <julian.calaby@gmail.com>,
	ozan@pardus.org.tr, linux-wireless@vger.kernel.org
Subject: Re: UPDATE -- Need Linux driver (preferably 64 bit) for "Intel Corporation Centrino Advanced-N 6230 (rev 34)" WiFI & Bluetooth card ...
Date: Thu, 10 Feb 2011 15:08:38 -0800 (PST)	[thread overview]
Message-ID: <937938.34583.qm@web36102.mail.mud.yahoo.com> (raw)
In-Reply-To: <20110210212508.GA2508@tuxdriver.com>


  > > In working with the kernel.org linux-wireless  developers, the conclusion
  > > from one developer was that, though generally  speaking the
  > > "Centrino Advanced-N 6230 AGN" card is supported by the  "iwlagn" kernel
  > > module, it seems that the stock kernel module provided  in the
  > > Fedora 14 kernel package (circa 2.6.35.10-74.fc14.x86_64), does  not
  > > support the this card.
  > > 
  > > In other words, though code  in the main kernel.org git repository does
  > > show support for the card  (via iwlagn kernel module), Fedora 14's
  > > rendition/distribution of that  does not.
  > 
  > The point you seem to be missing is that your hardware is very  new,
  > and the current Fedora 14 kernel is an "ancient" 6+ months  old.
  >
The point wasn't missed. In fact I highlighted the Fedora kernel
version, and my card model to expressly make the point. Moreover,
one of my suggested work-arounds was to try a newer kernel module
(via compat-wireless) so as to bridge bridge that gap for this issue.

  > > Command  output during my debugging session with the developers is
  > > shown below  for completeness, and in case the Fedora folks are
  > >  monitoring.
  > 
  > I'm sorry, but your acquisition of bleeding-edge hardware  does not
  > merit a change in the normal Fedora release  policy.
  >
Nothing in my email asked or expected them to. Still, the community
in general should know what's going on. And, I did suggest two
work-arounds in my email, neither of which asks anything of Fedora. 

  > P.S. I apologize if this seems rude -- that is  not my intent.
  >
Ah... This postscript repairs everything.





----- Original Message ----
> From: John W. Linville <linville@tuxdriver.com>
> To: Noel Milton Vega <nmvega@nyceyes.com>
> Cc: Julian Calaby <julian.calaby@gmail.com>; ozan@pardus.org.tr; 
>linux-wireless@vger.kernel.org; Noel Milton Vega 
><nmvega@ComputingArchitects.Com>
> Sent: Thu, February 10, 2011 4:25:08 PM
> Subject: Re: UPDATE -- Need Linux driver (preferably 64 bit) for "Intel 
>Corporation Centrino Advanced-N 6230 (rev 34)" WiFI & Bluetooth card ...
> 
> On Thu, Feb 10, 2011 at 12:31:02PM -0800, Noel Milton Vega wrote:
> 
> > Hi  Friends....
> > 
> > UPDATE:
> > 
> > In working with the kernel.org linux-wireless  developers, the conclusion
> > from one developer was that, though generally  speaking the
> > "Centrino Advanced-N 6230 AGN" card is supported by the  "iwlagn" kernel
> > module, it seems that the stock kernel module provided  in the
> > Fedora 14 kernel package (circa 2.6.35.10-74.fc14.x86_64), does  not
> > support the this card.
> > 
> > In other words, though code  in the main kernel.org git repository does
> > show support for the card  (via iwlagn kernel module), Fedora 14's
> > rendition/distribution of that  does not.
> 
> The point you seem to be missing is that your hardware is very  new,
> and the current Fedora 14 kernel is an "ancient" 6+ months  old.
> 
> > "lspci(8) -v" did show the hardware (Intel Corporation Centrino  Advanced-N 
>6230
> > (rev 34)), the necessary driver and firmware packages  were installed, and 
>the
> > laptop RF toggle switches are set to enable  wireless communications.
> > Yet manually performing "modprobe(8) iwlagn"  does not produce a wlan0
> > interface in "ifconfig(8) -a" output; and  although "dmesg(8)" shows the
> > module being loaded, it does not show it  detecting the card.
> > 
> > The two work arounds were suggested (I  haven't tried either):
> > 
> >   (1) Update the kernel. Since I  have the latest one provided
> >       by Fedora for Fedora  14, this implies a manual compile
> >       of a kernel.org  kernel. Note that if Fedora is not aware of
> >       this  issue, it's not likely that the next kernel update
> >        will remedy this.
> 
> You could update to a Fedora Rawhide kernel.
> 
> As  root:
> 
>     yum install  fedora-release-rawhide
> 
>     yum --enablerepo=rawhide  install kernel
> 
> Please note that Rawhide is not known for its  stability...
> 
> >   (2) Using a compat-wireless technique described  here,
> >        http://wireless.kernel.org/en/users/Download
> > 
> > 
> > Command  output during my debugging session with the developers is
> > shown below  for completeness, and in case the Fedora folks are
> >  monitoring.
> 
> I'm sorry, but your acquisition of bleeding-edge hardware  does not
> merit a change in the normal Fedora release  policy.
> 
> John
> 
> P.S.  I apologize if this seems rude -- that is  not my intent.
> -- 
> John W. Linville         Someday the world will need a hero, and you
> linville@tuxdriver.com             might be all we have.  Be ready.
> 

  reply	other threads:[~2011-02-10 23:08 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 [this message]
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 ` SOLVED -- " 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=937938.34583.qm@web36102.mail.mud.yahoo.com \
    --to=nmvega@nyceyes.com \
    --cc=julian.calaby@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --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).