From: Pavel Roskin <proski@gnu.org>
To: Malte Gell <malte.gell@gmx.de>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: Kernel 2.6.33: ar9170.fw firmware file not found
Date: Thu, 11 Mar 2010 13:25:35 -0500 [thread overview]
Message-ID: <1268331935.1915.19.camel@mj> (raw)
In-Reply-To: <201003110933.18581.malte.gell@gmx.de>
On Thu, 2010-03-11 at 09:33 +0100, Malte Gell wrote:
> Pavel Roskin <proski@gnu.org> wrote
> > Please post your .config file. I guess you are missing something
> > obvious, like sysfs support or inotify.
>
> Thanx, okay. It is attached. But to me it seems sysfs and inotify is there...
I compiled a kernel with your config on plain 2.6.33. I'm using the
x86_64 architecture, so "make oldconfig" asked a few questions, but
nothing important.
I'm running that kernel with no problems. The driver loads and works
fine. Here's the output of udevadm monitor:
# udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[1268330587.328525] add /module/ar9170usb (module)
UDEV [1268330587.329955] add /module/ar9170usb (module)
KERNEL[1268330588.565742] remove /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0 (usb)
KERNEL[1268330588.565772] remove /devices/pci0000:00/0000:00:1d.7/usb1/1-8 (usb)
KERNEL[1268330588.565987] add /bus/usb/drivers/ar9170usb (drivers)
UDEV [1268330588.567718] add /bus/usb/drivers/ar9170usb (drivers)
UDEV [1268330588.569497] remove /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0 (usb)
UDEV [1268330588.571498] remove /devices/pci0000:00/0000:00:1d.7/usb1/1-8 (usb)
KERNEL[1268330589.868626] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8 (usb)
KERNEL[1268330589.869178] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0 (usb)
KERNEL[1268330591.158658] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/firmware/1-8 (firmware)
KERNEL[1268330591.161688] remove /devices/pci0000:00/0000:00:1d.7/usb1/1-8/firmware/1-8 (firmware)
UDEV [1268330591.162451] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/firmware/1-8 (firmware)
UDEV [1268330591.163424] remove /devices/pci0000:00/0000:00:1d.7/usb1/1-8/firmware/1-8 (firmware)
KERNEL[1268330591.736323] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/ieee80211/phy2 (ieee80211)
KERNEL[1268330591.736349] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/ieee80211/phy2/rfkill1 (rfkill)
KERNEL[1268330591.736503] change /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/ieee80211/phy2/rfkill1 (rfkill)
KERNEL[1268330591.737446] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/net/wlan0 (net)
KERNEL[1268330591.740066] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/leds/ar9170-phy2::tx (leds)
UDEV [1268330591.740094] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8 (usb)
KERNEL[1268330591.740105] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/leds/ar9170-phy2::assoc (leds)
UDEV [1268330591.745693] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0 (usb)
UDEV [1268330591.746816] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/leds/ar9170-phy2::assoc (leds)
UDEV [1268330591.748185] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/leds/ar9170-phy2::tx (leds)
KERNEL[1268330591.751861] move /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/net/wlan25 (net)
UDEV [1268330591.768580] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/ieee80211/phy2 (ieee80211)
UDEV [1268330591.771943] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/ieee80211/phy2/rfkill1 (rfkill)
UDEV [1268330591.775586] change /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/ieee80211/phy2/rfkill1 (rfkill)
UDEV [1268330591.789582] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/net/wlan25 (net)
UDEV [1268330591.799576] move /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/net/wlan25 (net)
It looks like you get no USB events. Also, the output looks
differently. KERNEL events are called UEVENT in your log.
Maybe you could try another USB port, just in case? I would probably
add debugging to the udev scripts to see what they are doing. Maybe
there is an update for udev for your system?
Perhaps you should find another forum to ask questions about udev. I
think the kernel is not a suspect anymore.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2010-03-11 18:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 7:35 Kernel 2.6.33: ar9170.fw firmware file not found Malte Gell
2010-03-04 8:57 ` Malte Gell
2010-03-05 22:26 ` Pavel Roskin
2010-03-05 22:31 ` Larry Finger
2010-03-06 2:42 ` Malte Gell
2010-03-10 5:37 ` Pavel Roskin
2010-03-10 7:52 ` Luis R. Rodriguez
2010-03-11 6:48 ` Malte Gell
2010-03-11 7:40 ` Pavel Roskin
2010-03-11 8:33 ` Malte Gell
2010-03-11 18:25 ` Pavel Roskin [this message]
2010-03-15 10:23 ` Malte Gell
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=1268331935.1915.19.camel@mj \
--to=proski@gnu.org \
--cc=linux-wireless@vger.kernel.org \
--cc=malte.gell@gmx.de \
--cc=mcgrof@gmail.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).