From: Falk-Moritz Schaefer <falk.schaefer@tu-dortmund.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Firmware - ar9271.fw not found
Date: Fri, 16 Jul 2010 08:57:58 +0200 [thread overview]
Message-ID: <000701cb24b4$3c9c4aa0$b5d4dfe0$@schaefer@tu-dortmund.de> (raw)
In-Reply-To: <20100715233655.57k3wtsjk408k0c4-cebfxv@webmail.spamcop.net>
- Ubuntu 10.04 LTS with 2.6.32-21-generic
- compat-wireless from 27.06.2010
Let me clearify, that I am not using the compat ubuntu package but a self
compiled version, so consequently dev_set_uevent_suppress() does not matter.
The network-manager is deinstalled on both laptops. There are two TL-WN721N
cards both work on one laptop but not on the other.
BR
Falk
-----Urspr?ngliche Nachricht-----
Von: ath9k-devel-bounces at venema.h4ckr.net
[mailto:ath9k-devel-bounces at venema.h4ckr.net] Im Auftrag von Pavel Roskin
Gesendet: Freitag, 16. Juli 2010 05:37
An: Chase Douglas
Cc: Ubuntu Kernel Team; ath9k-devel at venema.h4ckr.net
Betreff: Re: [ath9k-devel] Firmware - ar9271.fw not found
Quoting Chase Douglas <chase.douglas@canonical.com>:
> Unless I've misread something, it sounds like we are just missing the
> firmware file. That should be an easy fix.
The original message was clear that the firmware file was available
and globally readable:
/lib/firmware$ ls -la ar*.fw
-rw-r--r-- 1 root root 51280 2010-07-15 08:51 ar9271.fw
I assume that ath9k_htc comes from linux-backport-modules
(compat-wireless packaged by Ubuntu). Then please check that it
doesn't have a bug fixed by this commit to the compat repository:
commit 524449c0184d44773d4947db8cd3bfd98a0a215f
Author: Grazvydas Ignotas <notasas@gmail.com>
Date: Thu Apr 22 16:54:02 2010 +0300
compat: fix uevent_suppress on 2.6.29 or older kernels
Missing uevent_suppress is causing two uevents instead of one, which is
confusing udev and sometimes causing firmware load to fail due to race
condition, so let's add it.
Since it's a race condition, it can explain why the same driver works
on one system but not on another one.
Please also check commit 8eca4cf0648fad100bd44a0779328f13e6b7d4ca from
April 28, 2010, also to "compat". It updates the firmware loading
code and adds further cleanups.
You can check if dev_set_uevent_suppress() is defined in
compat-2.6.30.h. If it's not, you are using an old version of
compat-wireless for the backport package and it should be updated.
--
Regards,
Pavel Roskin
_______________________________________________
ath9k-devel mailing list
ath9k-devel at lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
next prev parent reply other threads:[~2010-07-16 6:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Acsj8nAYqnXSDOFpRvG6musBv9reUQ==>
[not found] ` <1908737015270049666@unknownmsgid>
2010-07-15 17:17 ` [ath9k-devel] Firmware - ar9271.fw not found Luis R. Rodriguez
2010-07-16 2:22 ` Chase Douglas
2010-07-16 3:36 ` Pavel Roskin
2010-07-16 6:57 ` Falk-Moritz Schaefer [this message]
2010-07-18 2:50 ` Pavel Roskin
2010-07-19 6:34 ` Falk-Moritz Schaefer
2010-07-20 21:34 ` Pavel Roskin
2010-07-20 21:48 ` Luis R. Rodriguez
2010-07-20 21:58 ` Pavel Roskin
2010-07-20 22:04 ` Luis R. Rodriguez
2010-07-24 7:09 ` Pavel Roskin
2010-07-16 7:16 ` Stefan Bader
2010-07-16 12:15 ` Chase Douglas
2010-07-15 7:50 Falk-Moritz Schaefer
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='000701cb24b4$3c9c4aa0$b5d4dfe0$@schaefer@tu-dortmund.de' \
--to=falk.schaefer@tu-dortmund.de \
--cc=ath9k-devel@lists.ath9k.org \
/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.