From: Larry Finger <Larry.Finger@lwfinger.net>
To: werner <w.landgraf@ru.ru>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
dave.taht@gmail.com, rientjes@google.com, arend@broadcom.com,
toralf.foerster@gmx.de, wey-yi.w.guy@intel.com,
ilw@linux.intel.com, larry.finger@gmail.com
Subject: Re: 3.1-rc9 wifi problem
Date: Sun, 16 Oct 2011 21:16:56 -0500 [thread overview]
Message-ID: <4E9B9018.1000002@lwfinger.net> (raw)
In-Reply-To: <web-627302724@zbackend1.aha.ru>
On 10/16/2011 08:33 PM, werner wrote:
> I have to wait until the friend with the laptop comes back, perhaps this week.
> Then I can look what wireless card is in it.
>
> However, now I remember me: that laptop worked only good since 2.6.39 with the
> new kernel-embedded modules. Before, it didn't work normally, i.e. on booting
> the wireless almost never didn't switch on; only ocasionally .
>
>
> And, beside of kernel 2.6.39, and the normal wifi software, I still had him to
> install a file iwlwifi-1000-3.ucode or .5 ucode (i'm not sure, the number can
> also be 5000), and I had the problem to search long time for that file because
> one find only .2 or .4 in internet but what don't work at that wifi card. You
> could improve the kernel-module so that everything is included so that one don't
> need to search such files.
That will not happen. In fact, the trend is from having firmware be a part of
the driver to having it be external.
I don't know what distro you use, but mine (openSUSE) maintains a package called
kernel-firmware that contains all the redistributable firmware that is available
from tne linux-firmware git tree. If that package is installed, then you do not
have to search for firmware in most cases. If your distro does not have such a
package, then complain or find another distro.
> Then, with this kernel and that file however, it worked without any problem.
>
> I hope from these informations you can find out what wifi card or what driver is
> in the laptop.
We can tell that you have an Intel card, but not much more.
Larry
next prev parent reply other threads:[~2011-10-17 2:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-15 21:43 3.1-rc9 wifi problem werner
2011-10-16 2:42 ` Larry Finger
2011-10-17 1:33 ` werner
2011-10-17 2:16 ` Larry Finger [this message]
2011-10-17 1:34 ` Guy, Wey-Yi
[not found] <web-626864831@zbackend1.aha.ru>
2011-10-15 18:38 ` Arend van Spriel
2011-10-15 19:21 ` David Täht
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=4E9B9018.1000002@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=arend@broadcom.com \
--cc=dave.taht@gmail.com \
--cc=ilw@linux.intel.com \
--cc=larry.finger@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rientjes@google.com \
--cc=toralf.foerster@gmx.de \
--cc=w.landgraf@ru.ru \
--cc=wey-yi.w.guy@intel.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 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).