On Wed, Oct 13, 2010 at 11:34, Pedro Aguilar
<pedro.aguilar.iniestra@xxxxxxxxx> 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=01 Lev=02 Prnt=02 Port=02 Cnt=01 Dev#= 11 Spd=480 MxCh= 0
> D: ÂVer= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= Â1
> P: ÂVendor=07d1 ProdID=3c0f Rev= 1.01
> S: ÂManufacturer=Ralink
> S: ÂProduct=11g Adapter
> S: ÂSerialNumber=1.0
> C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=450mA
> I:* If#= 0 Alt= 0 #EPs= 7 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
> E: ÂAd=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
> E: ÂAd=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
> E: ÂAd=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
> E: ÂAd=03(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
> E: ÂAd=04(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
> E: ÂAd=05(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
> E: ÂAd=06(O) Atr=02(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
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
