From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev seems to not recognize some devices when plugging them
Date: Wed, 13 Oct 2010 13:40:27 +0000 [thread overview]
Message-ID: <20101013134027.GC8975@kroah.com> (raw)
In-Reply-To: <AANLkTimRDapMMB3+v2YNF6TrLn3B4+RnZYmBzUseGYuh@mail.gmail.com>
On Wed, Oct 13, 2010 at 11:34:45AM +0200, Pedro Aguilar wrote:
> Hi,
>
> I'm working on a set-top-box that needs a wireless network using an
> usb wireless adapter such as the d-link dwl-122 that is supported
> under Linux.
> I have a kernel 2.6.23.17, libc 2.6 and udev 129. For several reasons
> I cannot upgrade the kernel :(
>
> My problem is that after compiling the kernel with all the necessary
> wireless modules (like mac80211), compiling and insmoding the usb
> wireless driver (rt73), copying its fw, and connecting the usb
> adapter, I have the following behaviour:
>
> There isn't any change in /sys/. I would expect a new dir in
> /sys/class/net (something like /sys/class/net/wlan0).
> # ls /sys/class/net/
> eth0 lo
>
> If I write a 00-test.rules, when I connect the usb adapter it matches
> and calls the test.sh script.
> ACTION="add", SUBSYSTEM="usb", ATTR{idVendor}="07d1",
> ATTR{idProduct}="3c0f", RUN+="/usr/bin/test.sh"
> so I think the kernel is sending the event to udev, but I don't see
> any net iface.
>
> iwconfig doesn't give any wireless interface:
> # iwconfig
> eth0 no wireless extensions.
> lo no wireless extensions.
>
> lsusb and cat /proc/bus/usb/devices give the right ouput:
> # lsusb
> Bus 001 Device 011: ID 07d1:3c0f D-Link System
> ...
>
> # cat /proc/bus/usb/devices
> T: Bus\x01 Lev\x02 Prnt\x02 Port\x02 Cnt\x01 Dev#= 11 SpdH0 MxCh= 0
> D: Ver= 2.00 Cls\0(>ifc ) Sub\0 Prot\0 MxPSd #Cfgs= 1
> P: Vendor\ad1 ProdID<0f Rev= 1.01
> S: Manufacturer=Ralink
> S: Product\x11g Adapter
> S: SerialNumber=1.0
> C:* #Ifs= 1 Cfg#= 1 Atr€ MxPwrE0mA
> I:* If#= 0 Alt= 0 #EPs= 7 Clsÿ(vend.) Subÿ Protÿ Driver=(none)
The problem is you don't have a driver bound to this device at all, so
there's nothing for udev, or anything else in userspace to be able to
control or notice.
Are you sure you have built the rt2x00 driver in your kernel? That
driver will control this device on the latest kernel versions.
good luck,
greg k-h
next prev parent reply other threads:[~2010-10-13 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 9:34 udev seems to not recognize some devices when plugging them Pedro Aguilar
2010-10-13 12:00 ` Kay Sievers
2010-10-13 13:40 ` Greg KH [this message]
2010-10-14 17:04 ` Pedro Aguilar
2010-10-14 17:39 ` Jim Paris
2010-10-14 18:19 ` Greg KH
2010-10-19 14:32 ` Pedro Aguilar
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=20101013134027.GC8975@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.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 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).