udev seems to not recognize some devices when plugging them

udev seems to not recognize some devices when plugging them

[Pedro Aguilar]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1252", Size: 2533 bytes --]

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)
E:  Ad(I) Atr\x02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad\x01(O) Atr\x02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad\x02(O) Atr\x02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad\x03(O) Atr\x02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad\x04(O) Atr\x02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad\x05(O) Atr\x02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad\x06(O) Atr\x02(Bulk) MxPS= 512 Ivl=0ms

Here's the output I get when I connect the usb wireless adapter with
the kernel's usb debugging active:

usb 1-1.3: new high speed USB device using stm-ehci and address 10
usb 1-1.3: Product: 11g Adapter
usb 1-1.3: Manufacturer: Ralink
usb 1-1.3: SerialNumber: 1.0
usb 1-1.3: configuration #1 chosen from 1 choice

Other devices like usb mass storage devices work smoothly as well as
usb mice and keyboards. This happens with the usb wireless adapter
that I have tested.

I'm not sure if the problem is because I have old versions of
udev/kernel/libc or if I'm missing something.
Any ideas/hints?

Thanks in advance!

Regards,
--
Pedro Aguilar
http://www.paguilar.org/blog

Re: udev seems to not recognize some devices when plugging them

[Kay Sievers]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1252", Size: 3082 bytes --]

On Wed, Oct 13, 2010 at 11:34, Pedro Aguilar
<pedro.aguilar.iniestra@gmail.com> wrote:
> 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)
> E:  Ad(I) Atr\x02(Bulk) MxPS= 512 Ivl=0ms
> E:  Ad\x01(O) Atr\x02(Bulk) MxPS= 512 Ivl=0ms
> E:  Ad\x02(O) Atr\x02(Bulk) MxPS= 512 Ivl=0ms
> E:  Ad\x03(O) Atr\x02(Bulk) MxPS= 512 Ivl=0ms
> E:  Ad\x04(O) Atr\x02(Bulk) MxPS= 512 Ivl=0ms
> E:  Ad\x05(O) Atr\x02(Bulk) MxPS= 512 Ivl=0ms
> E:  Ad\x06(O) Atr\x02(Bulk) MxPS= 512 Ivl=0ms
>
> Here's the output I get when I connect the usb wireless adapter with
> the kernel's usb debugging active:
>
> usb 1-1.3: new high speed USB device using stm-ehci and address 10
> usb 1-1.3: Product: 11g Adapter
> usb 1-1.3: Manufacturer: Ralink
> usb 1-1.3: SerialNumber: 1.0
> usb 1-1.3: configuration #1 chosen from 1 choice
>
> Other devices like usb mass storage devices work smoothly as well as
> usb mice and keyboards. This happens with the usb wireless adapter
> that I have tested.
>
> I'm not sure if the problem is because I have old versions of
> udev/kernel/libc or if I'm missing something.
> Any ideas/hints?

Udev is not involved in detecting any device, it does not make things
show up in /sys. It might only load a kernel module, by just blindly
calling modprobe for all devices which could possibly have a driver.
To check that you can just call modprobe manually.

There is no other logic in userspace. All the other stuff, which makes
devices to show up is inside the kernel, not in userspace.

Kay

Re: udev seems to not recognize some devices when plugging them

[Greg KH]

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

Re: udev seems to not recognize some devices when plugging them

[Pedro Aguilar]

Hi,

I built the rt2x00 as modules from compat-wireless-old-2009-12-11
since it has support for the kernel 2.6.23.17.
After building the kernel with the right options (that were required
by compat-wireless-old) I insmoded the modules in this order

ieee80211_crypt.ko
ieee80211.ko
cfg80211.ko
mac80211.ko
rt2x00lib.ko
rt2x00usb.ko
rt2500usb.ko
rt73usb.ko

but it still seems to not have a driver bound for this device, I don't
see any changes in /sys/class/net, only the usb subsystem shows
something inside /sys/bus/usb .

I have the same problem with other devices (not usb wireless adapters)
so may be I could be missing some kernel configurations parameters.
However, as I mentioned before, mass storage and i/o devices work as
expected.

Do you have any ideas what could cause the kernel not to bound a
driver to a device even though the driver exists?

Thanks again for your support!

Regards,
-- 
Pedro Aguilar
http://www.paguilar.org/blog



On Wed, Oct 13, 2010 at 3:40 PM, Greg KH <greg@kroah.com> wrote:
> 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
>

Re: udev seems to not recognize some devices when plugging them

[Jim Paris]

Pedro Aguilar wrote:
> Hi,
> 
> I built the rt2x00 as modules from compat-wireless-old-2009-12-11
> since it has support for the kernel 2.6.23.17.
> After building the kernel with the right options (that were required
> by compat-wireless-old) I insmoded the modules in this order
> 
> ieee80211_crypt.ko
> ieee80211.ko
> cfg80211.ko
> mac80211.ko
> rt2x00lib.ko
> rt2x00usb.ko
> rt2500usb.ko
> rt73usb.ko
> 
> but it still seems to not have a driver bound for this device, I don't
> see any changes in /sys/class/net, only the usb subsystem shows
> something inside /sys/bus/usb .
> 
> I have the same problem with other devices (not usb wireless adapters)
> so may be I could be missing some kernel configurations parameters.
> However, as I mentioned before, mass storage and i/o devices work as
> expected.
> 
> Do you have any ideas what could cause the kernel not to bound a
> driver to a device even though the driver exists?
> 
> Thanks again for your support!

(Please don't top-quote)

The drivers in compat-wireless-old-2009-12-11 don't support your device:

pilot:/tmp/compat-wireless-2.6-old$ grep -ir 0x07d1 .
./drivers/net/wireless/ar9170/main.c:   { USB_DEVICE(0x07d1, 0x3c10) },
./drivers/net/wireless/rt2x00/rt73usb.c:        { USB_DEVICE(0x07d1, 0x3c03), USB_DEVICE_DATA(&rt73usb_ops) },
./drivers/net/wireless/rt2x00/rt73usb.c:        { USB_DEVICE(0x07d1, 0x3c04), USB_DEVICE_DATA(&rt73usb_ops) },
./drivers/net/wireless/rt2x00/rt73usb.c:        { USB_DEVICE(0x07d1, 0x3c06), USB_DEVICE_DATA(&rt73usb_ops) },
./drivers/net/wireless/rt2x00/rt73usb.c:        { USB_DEVICE(0x07d1, 0x3c07), USB_DEVICE_DATA(&rt73usb_ops) },
pilot:/tmp/compat-wireless-2.6-old$ grep -ir 0x3c0f .
pilot:/tmp/compat-wireless-2.6-old$ 

I don't think your chipset is supported by those drivers.  Really,
upgrading your kernel would be the best solution.  This really isn't
related to udev at all.

-jim

Re: udev seems to not recognize some devices when plugging them

[Greg KH]

On Thu, Oct 14, 2010 at 07:04:59PM +0200, Pedro Aguilar wrote:
> Hi,
> 
> I built the rt2x00 as modules from compat-wireless-old-2009-12-11
> since it has support for the kernel 2.6.23.17.

Is that the kernel version you are stuck with?

That's the issue, please upgrade to a newer, modern kernel version
(yours is more than 3 years old, before the hardware you are trying to
use was around.)

good luck,

greg k-h

Re: udev seems to not recognize some devices when plugging them

[Pedro Aguilar]

Hi,

I bought the supported hw revision of the d-link dwl-122 usb wireless
adapter that is C1 (I was using E1) and with the
compat-wireless-old-2009-12-11 it worked, but only with an unencrypted
connection that is not very useful. I still had problems with the
kernel when trying to establish a wpa2-based connection, so at the end
I'm upgrading the kernel as you suggested.

Thanks a lot for your help!
-- 
Pedro Aguilar
http://www.paguilar.org/blog


On Thu, Oct 14, 2010 at 8:19 PM, Greg KH <greg@kroah.com> wrote:
> On Thu, Oct 14, 2010 at 07:04:59PM +0200, Pedro Aguilar wrote:
>> Hi,
>>
>> I built the rt2x00 as modules from compat-wireless-old-2009-12-11
>> since it has support for the kernel 2.6.23.17.
>
> Is that the kernel version you are stuck with?
>
> That's the issue, please upgrade to a newer, modern kernel version
> (yours is more than 3 years old, before the hardware you are trying to
> use was around.)
>
> good luck,
>
> greg k-h
>