rt73 on ARM without hotplug or udev

daniel_matthes · **Joined:** Thu Oct 25, 2007 12:21 pm **Posts:** 50

Hello,

I have the task to get run the USB wireless adapter DWL-G122 on a Linux ARM System. I have crosscompiled the rt73 driver without any error.

insmod /lib/modules/'uname -r'/extra/rt73.ko results:

rtusb init ====>
idVendor = 0x7d1, idProduct = 0x3c03
rt73: Failed to request_firmware. Check your firmware file location
rt73: probe of 1-1:1.0 failed with error -2
usbcore: registered new interface driver rt73

so I read here, I have to use udev or hotplug to fix this problem. But I got the rule to release this problem without this tool.

Is someone able to give me help, which steps i've to be observed.

- create a device link
- load the firmware manually

hennichodernich · **Posted:** Fri Oct 26, 2007 6:51 am

daniel_matthes wrote:

so I read here, I have to use udev or hotplug to fix this problem.

Correct.

daniel_matthes wrote:

But I got the rule to release this problem without this tool.

Who made that rule? Your boss?

daniel_matthes wrote:

- create a device link

What do you mean by that? A device _node_? You won't need one.

daniel_matthes wrote:

- load the firmware manually

You could try that, run

Code:

echo 1 > /sys/$DEVPATH/loading
cat $HOTPLUG_FW_DIR/$FIRMWARE > /sys/$DEVPATH/data
echo 0 > /sys/$DEVPATH/loading

by hand. You'll have to get the variables (and the timing!) right, that's why this action is usually triggered by udev or hotplug.

The other possibility is to rewrite the driver source to have the firmware compiled in. I remember some guy mentioning this in one of these forums.

Should be no big deal if it's a commercial project you're working on.

regards
Henning

Viper · **Joined:** Sun Nov 04, 2007 12:26 pm **Posts:** 7

daniel_matthes wrote:

Hello,

I have the task to get run the USB wireless adapter DWL-G122 on a Linux ARM System. I have crosscompiled the rt73 driver without any error.

insmod /lib/modules/'uname -r'/extra/rt73.ko results:

rtusb init ====>
idVendor = 0x7d1, idProduct = 0x3c03
rt73: Failed to request_firmware. Check your firmware file location
rt73: probe of 1-1:1.0 failed with error -2
usbcore: registered new interface driver rt73

so I read here, I have to use udev or hotplug to fix this problem. But I got the rule to release this problem without this tool.

Is someone able to give me help, which steps i've to be observed.

- create a device link
- load the firmware manually

Did you manage to do this? I'm facing nearly the same problem, but I cannot compile the module

/for 2.6.22/

Vern · **Posted:** Mon Nov 05, 2007 8:21 pm

Hi daniel_matthes,

Please provide the following info:
* driver version (including the date if it's a CVS build)
* hardware description - CPU, adapter Mfr. & model, AP if known.
* distrobution name and version
* kernel version

Thanks,

daniel_matthes · **Joined:** Thu Oct 25, 2007 12:21 pm **Posts:** 50

Hello everybody,

@Vern:

Vern wrote:

driver version (including the date if it's a CVS build)

driver version: rt73-cvs-2007101206

Vern wrote:

hardware description - CPU, adapter Mfr. & model, AP if known.

CPU: AT91RM9200
adapter: DWL-G122 H/W: C1
AP: DWL-900AP+

Vern wrote:

distrobution name and version

self compiled linux kernel, no known distribution

Vern wrote:

kernel version

kernel-version: 2.6.19

Now I would describe you my current progress.:

1. Compiling the wlan driver for my debian lenny distribution with linux kernel 2.6.22

make, make install with no warnings and errors
modprobe rt73 with no errors
ifup wlan0 with no errors

wlan-adapter works perfectly including WEP encryption

2. Create Makefile for the embedded Linux System, based on the original

Quote:

# Tool names
ARCH = arm
CROSS_COMPILE = ${ARCH}-linux-
AS = ${CROSS_COMPILE}as
AR = ${CROSS_COMPILE}ar
CC = ${CROSS_COMPILE}gcc
CPP = ${CC} -E
LD = ${CROSS_COMPILE}ld
NM = ${CROSS_COMPILE}nm
OBJCOPY = ${CROSS_COMPILE}objcopy
OBJDUMP = ${CROSS_COMPILE}objdump
RANLIB = ${CROSS_COMPILE}ranlib
READELF = ${CROSS_COMPILE}readelf
SIZE = ${CROSS_COMPILE}size
STRINGS = ${CROSS_COMPILE}strings
STRIP = ${CROSS_COMPILE}strip

export AS AR CC XPP LD NM OBJCOPY OBJDUMP RANLIB READELF SIZE STRINGS STRIP

MODULE_NAME := rt73
IF_NAME := wlan*

FIRM_DIR := $(PRJROOT)/rootfs/lib/firmware
FIRMWARES := rt73.bin

$(MODULE_NAME)-objs := rtmp_main.o mlme.o connect.o rtusb_bulk.o rtusb_io.o \
sync.o assoc.o auth.o auth_rsp.o rtusb_data.o \
rtmp_init.o sanity.o rtmp_wep.o rtmp_info.o \
rtmp_tkip.o wpa.o md5.o rt2x00debug.o

obj-m += $(MODULE_NAME).o

KDIR := $(PRJROOT)/kernel/linux
PWD := $(shell pwd)

MODULE_ROOT := /lib/modules/2.6.19-etwarm/extra
MODULE_OBJECT := $(MODULE_NAME).ko

all: module

MODULE_CHECK := if ! [ -f $(MODULE_OBJECT) ]; then \
echo "$(MODULE_OBJECT) failed to build!"; \
exit 1; \
fi; \
if [ `du -b $(MODULE_OBJECT) | sed -e 's/\t.*//g'` -gt 1000000 ]; then \
echo "!!! WARNING: Module file much too big (>1MB)"; \
echo "!!! Check your kernel settings or use 'strip'"; \
fi; \
echo "*** Module $(MODULE_OBJECT) built successfully"

module:
@$(MAKE) ARCH=$(ARCH) CROSS_COMPILE=$(CROSS_COMPILE) -C $(KDIR) SUBDIRS=$(PWD) 'EXTRA_CFLAGS=-DDBG modules; \
$(MODULE_CHECK)

clean:
@rm -f *.o .*.{cmd,flags}
@rm -f $(MODULE_NAME).{o,ko,mod.{o,c}} built-in.o $(VERSION_HEADER) *~
@rm -fr .tmp_versions Module.symvers

modules_install:
@if ! [ -f $(MODULE_OBJECT) ]; then \
echo "!!! $(MODULE_OBJECT) does not exit: run 'make'"; \
exit 1; \
fi
@echo "*** Install module in $(MODULE_ROOT) ..."

$(MAKE) ARCH=$(ARCH) CROSS_COMPILE=$(CROSS_COMPILE) -C $(KDIR) SUBDIRS=$(PWD) INSTALL_MOD_PATH=$(PRJROOT)/rootfs/ modules_install

install: modules_install
@echo "*** Install firmware in $(FIRM_DIR) ..."; \
if ! [ -d $(FIRM_DIR) ]; then \
mkdir $(FIRM_DIR); \
fi; \
cp -f $(FIRMWARES) $(FIRM_DIR)

3. Create a new zImage

including:
- support for hot-pluggable devices CONFIG_HOTPLUG
- userspace firmware loading support CONFIG_FW_LOADER
- wireless LAN drivers (non-hamradio) & wireless extensions CONFIG_NET_RADIO
- OHCI HCD support CONFIG_OHCI_HCD

this includes are necessary for compiling the driver without errors.

4. Run make in the wlan driver folder "Module"

debug output:

Quote:

make[1]: Entering directory `/home/embedded-linux/kernel/linux-etwarm'
CC [M] /home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/rtmp_main.o
CC [M] /home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/mlme.o
CC [M] /home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/connect.o
CC [M] /home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/rtusb_bulk.o
CC [M] /home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/rtusb_io.o
CC [M] /home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/sync.o
CC [M] /home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/assoc.o
CC [M] /home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/auth.o
CC [M] /home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/auth_rsp.o
CC [M] /home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/rtusb_data.o
CC [M] /home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/rtmp_init.o
CC [M] /home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/sanity.o
CC [M] /home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/rtmp_wep.o
CC [M] /home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/rtmp_info.o
/home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/rtmp_info.c: In function `rt_ioctl_siwessid':
/home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/rtmp_info.c:905: Warnung: Anweisung ohne Effekt
/home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/rtmp_info.c: In function `RTMPSetInformation':
/home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/rtmp_info.c:1474: Warnung: Anweisung ohne Effekt
/home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/rtmp_info.c: In function `Set_SSID_Proc':
/home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/rtmp_info.c:3972: Warnung: Anweisung ohne Effekt
/home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/rtmp_info.c: In function `rt73_ioctl':
/home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/rtmp_info.c:2777: Warnung: Anweisung ohne Effekt
CC [M] /home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/rtmp_tkip.o
CC [M] /home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/wpa.o
CC [M] /home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/md5.o
CC [M] /home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/rt2x00debug.o
LD [M] /home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/rt73.o
Building modules, stage 2.
MODPOST 1 modules
CC /home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/rt73.mod.o
LD [M] /home/embedded-linux/Ralink/rt73-cvs-2007101206/Module/rt73.ko
make[1]: Leaving directory `/home/embedded-linux/kernel/linux-etwarm'
*** Module rt73.ko built successfully

"Anweisung ohne Effekt" means "instruction without effect"

I dont know how to prevent the warnings, so I ignored them. Maybe they are the reason of my further problems???

5. make install

--> rt73.bin in /lib/firmware
--> rt73.ko in /lib/modules/2.6.19-etwarm/extra/

6. insmod /lib/modules/2.6.19-etwarm/extra/rt73.ko results:

Quote:

rtusb init ====>
idVendor = 0x7d1, idProduct = 0x3c03
rt73: Failed to request_firmware. Check your firmware file location
rt73: probe of 1-1:1.0 failed with error -2
usbcore: registered new interface driver rt73

[/quote]

7. I solved this problem

a) I forgot to mount sysfs

add "sysfs /sys sysfs defaults" in /etc/fstab

b) add hotplug-script (because I would not use hotplug or udev)

- add textfile "hotplug" in /proc/sys/kernel with entry "/sbin/hotplug"
- create executable file "hotplug" under /sbin

Quote:

#!/bin/sh

# Simple hotplug script sample:
#
# Both $DEVPATH and $FIRMWARE are already provided in the environment.

HOTPLUG_FW_DIR=/lib/firmware

echo 1 > /sys/$DEVPATH/loading
cat $HOTPLUG_FW_DIR/$FIRMWARE > /sys/$DEVPATH/data
echo 0 > /sys/$DEVPATH/loading

# To cancel the load in case of error:
#
# echo -1 > /sys/$DEVPATH/loading
#
#

thanks to hennig

8. Include ifupdown and run-parts to the busybox, add wireless_tools to my embedded linux systems, add the following params to /etc/network/interfaces

Quote:

auto wlan0
iface wlan0 inet static
address 141.57.27.165
netmask 255.255.252.0
network 141.57.24.0
broadcast 141.57.27.255
gateway 141.57.24.3
pre-up ifconfig wlan0 up

pre-up iwconfig wlan0 essid "*******"
pre-up iwconfig wlan0 mode Managed
pre-up iwconfig wlan0 channel 8

pre-up iwpriv wlan0 set AuthMode=WEPAUTO
pre-up iwpriv wlan0 set EncrypType=WEP
pre-up iwpriv wlan0 set Key1=**********
pre-up iwpriv wlan0 set SSID="*******"

9. insmod /lib/modules/2.6.19-etwarm/extra/rt73.ko results now:

Quote:

rtusb init ====>
idVendor = 0x7d1, idProduct = 0x3c03
usbcore: registered new interface driver rt73

10. ifup wlan0 results:

Quote:

rt73 driver version - 1.0.3.6 CVS
***rt73***: Interface goes up for the first time, activating permanent MAC
***rt73***: Active MAC is: 00:19:5b:74:bf:3e

11. ifconfig and iwconfig output:

Quote:

wlan0 Link encap:Ethernet HWaddr 00:19:5B:74:BF:3E
inet addr:141.57.27.165 Bcast:141.57.27.255 Mask:255.255.252.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:91514 errors:0 dropped:0 overruns:0 frame:0
TX packets:9180 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7118377 (6.7 MiB) TX bytes:716040 (699.2 KiB)

wlan0 RT73 WLAN ESSID:"FTZwlan"
Mode:Managed Frequency=2.447 GHz Bit Rate:54 Mb/s
RTS thr:off Fragment thr:off
Encryption key:0A1B-2C3D-4E
Link Quality=0/100 Signal level:-121 dBm Noise level:-115 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Here you can see my current problem. There is no link quality.

iwlist wlan0 scanning results:

Quote:

wlan0 No scan results

ifdown wlan0 results:

Quote:

wlan0: unable to signal thread

<--- ????

But the interface goes down

--> Actually I have no idea, what are the reasons of this problem.

Maybe somebody has an idea???

Regards Daniel

Viper · **Joined:** Sun Nov 04, 2007 12:26 pm **Posts:** 7

I'm still having the same problem on an ARM system. Kernel is 2.6.22, with wireless extension in, but getting the same result as you (FW cannot be loaded).

How did you solve that one? I'm not having sysfs or hotplug... Should I compule udev from it's source?

Vern · **Posted:** Wed Nov 07, 2007 2:29 am

daniel_mathes wrote:

I dont know how to prevent the warnings, so I ignored them. ...

What version of the compiler are you using? Mine doesn't complain, but its a good catch. Here's what it doesn't like:

Code:

memcpy(Ssid.Ssid, "", 0);

Since memcpy won't copy zero bytes of data, there's probably no real harm, but the intended effect is not produced, either.

It turns out I screwed up a fix that was intended to improve operation in an SMP environment. I've backed that out, and incorporated a patch by Graham Gower which is needed to load firmware under 2.4 kernels into CVS. The fixed source should be available in the latest CVS tarball for rt73 by now. Sorry for the mess up.

Graham has also provided a patch to implement firmware loading in the same way that Ralink's version of the driver does. I've gzipped it and attached it to this posting exactly as he provided it. If you apply it, you should be able to get by without depending on hotplug and/or udev. Let me know your results.

Thanks,

Viper · **Joined:** Sun Nov 04, 2007 12:26 pm **Posts:** 7

Vern wrote:

Graham has also provided a patch to implement firmware loading in the same way that Ralink's version of the driver does. I've gzipped it and attached it to this posting exactly as he provided it. If you apply it, you should be able to get by without depending on hotplug and/or udev. Let me know your results.

Applied the patch (compained about rtmp_main.c -> cannot comment out goto_no_firmware), complied well, inserted the module. Loaded also well, but I cannot configure the Wireless Network:

Code:

rtusb init ====>
idVendor = 0x148f, idProduct = 0x2573
usbcore: registered new interface driver rt73
root@(none):/etc/Wireless/RT73STA# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

tunl0     no wireless extensions.

gre0      no wireless extensions.

wlan0     RT73 WLAN
          Link Quality:0  Signal level:0  Noise level:113
          Rx invalid nwid:0  invalid crypt:0  invalid misc:0

root@(none):/etc/Wireless/RT73STA# iwconfig wlan0 essid ViperNET
Error for wireless request "Set ESSID" (8B1A) :
    SET failed on device wlan0 ; Network is down.
root@(none):/etc/Wireless/RT73STA# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0D:33:44:57:05
          inet addr:1.1.1.35  Bcast:1.1.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2104 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1382 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:465421 (454.5 KiB)  TX bytes:187913 (183.5 KiB)
          Interrupt:24 Base address:0xc000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1032 (1.0 KiB)  TX bytes:1032 (1.0 KiB)

root@(none):/etc/Wireless/RT73STA# ifconfig wlan0 1.1.1.34 mask 255.255.255.0
ifconfig: SIOCSIFFLAGS: Input/output error
root@(none):/etc/Wireless/RT73STA# ifconfig wlan0 1.1.1.34 mask 255.255.255.0 up
ifconfig: SIOCSIFFLAGS: Input/output error
root@(none):/etc/Wireless/RT73STA# ifconfig wlan0 up
ifconfig: SIOCSIFFLAGS: Input/output error

iwlist scanning is also not working - not supported by interface...

Any idea?

daniel_matthes · **Joined:** Thu Oct 25, 2007 12:21 pm **Posts:** 50

Viper wrote:

How did you solve that one? I'm not having sysfs or hotplug... Should I compule udev from it's source?

Maybe you do not read my whole post. You do not need udev!

Bevor compiling the kernel, set
CONFIG_HOTPLUG=y and CONFIG_SYSFS=y
--> now you have sysfs and hotplug

Afterwards follow step 7 in my last post.

Then firmware loading shout work.

daniel_matthes · **Joined:** Thu Oct 25, 2007 12:21 pm **Posts:** 50

Vern wrote:

What version of the compiler are you using?

arm-linux-gcc 3.4.4

Vern wrote:

Here's what it doesn't like:

Code:

memcpy(Ssid.Ssid, "", 0);

Yes I know. This warnings are completly memcpy problems

Vern wrote:

Graham has also provided a patch to implement firmware loading ... you should be able to get by without depending on hotplug and/or udev.

OK, but firmware loading is not my current problem. Firmware loading works with the shell script described in step seven of my last post

My problem is:

daniel_matthes wrote:

iwlist wlan0 scanning results:

wlan0 No scan results

ifdown wlan0 results:

wlan0: unable to signal thread

modprobe rt73 brings no errors.

I can configure my adapter and bring them up. The activity led blinks. But the adapter doesnt find any ap.

Regards
Daniel

daniel_matthes · **Joined:** Thu Oct 25, 2007 12:21 pm **Posts:** 50

When I probe rt73 with "debug=31", after 'ifup wlan0' I got the attached output.

Maybe someone get an idea by reading this attached textfile.

Viper · **Joined:** Sun Nov 04, 2007 12:26 pm **Posts:** 7

daniel_matthes wrote:

Viper wrote:

How did you solve that one? I'm not having sysfs or hotplug... Should I compule udev from it's source?

Maybe you do not read my whole post. You do not need udev!

Bevor compiling the kernel, set
CONFIG_HOTPLUG=y and CONFIG_SYSFS=y
--> now you have sysfs and hotplug

Afterwards follow step 7 in my last post.

Then firmware loading shout work.

No sysfs in 2.6.22 with ARCH=arm... (even if I edit .config by hand...)

daniel_matthes · **Joined:** Thu Oct 25, 2007 12:21 pm **Posts:** 50

Viper wrote:

No sysfs in 2.6.22 with ARCH=arm... (even if I edit .config by hand...)

CONFIG_SYSFS is part of 2.6.22!!!

--> make ARCH=arm menuconfig
--> shift+7
--> search for sysfs

You should find the location of SYSFS

Vern · **Posted:** Thu Nov 08, 2007 6:03 pm

daniel_matthes wrote:

When I probe rt73 with "debug=31", after 'ifup wlan0' I got the attached output.

What do you regard as the problem there?

It's best to run with debug=15, then attach a gzipped copy of /var/log/debug if you can.

Thanks,

Viper · **Joined:** Sun Nov 04, 2007 12:26 pm **Posts:** 7

daniel_matthes wrote:

Viper wrote:

No sysfs in 2.6.22 with ARCH=arm... (even if I edit .config by hand...)

CONFIG_SYSFS is part of 2.6.22!!!

--> make ARCH=arm menuconfig
--> shift+7
--> search for sysfs

You should find the location of SYSFS

Finally I've found it (also had to enable CONFIG_EMBEDDED), but it didn't help my problem

Any other idea? Should I build a debug driver and try that one?

rt2x00.serialmonkey.com

Forum rules

rt73 on ARM without hotplug or udev

Who is online