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=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)
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
--
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
