crosscompile problem about wireless USB adapter TL-wn321g

Live forum:


31-07-2008 09:33:07

I have a arm9 platform(s3c2410) with linux kernel 2.4.18 -rlmk7 which is cross compiled by arm-linux-gcc 2.95.3. Now i have to have my wireless USB adapter work on this arm board. I tried to download the source packet RT73_Linux_STA_Drv1.0.3.6 & RT73_Linux_STA_Drv1.0.4.0, and to cross compile them by the toolchain. Every time there are no correct results.
Besides I downloaded the newest CVS rt73-cvs-2008072903. I also crosscompiled it without correct results.
Can any one here tell me where is not set right or what should i do to work it out? Your help is greatly appreciated!
here is the Makefile script, the Configure file and the compile results ( RT73_Linux_STA_Drv1.0.4.0)


31-07-2008 09:46:42

RT73_Linux_STA_Drv1.0.3.6 & RT73_Linux_STA_Drv1.0.4.0[/quote271uktfm]

As mentioned in countless other topics (and apparently is a very surprising and shocking news for users)
We only support drivers released by this project.

Either download the driver from our website and if that driver fails too raise a support request here, or use a driver from a different website and ask support there.


31-07-2008 12:05:16

Really sorry for the mistake!
OK, go straightly to the point.
I have tried the newly CVS downloaded from here too. It's rt73-cvs-2008072903. I think i have rendered the correct command. I am wondering where is it not wright. Below are the results
(BTW The kernel version on the targetboard is linux 2.4.18-rmk7-pxa1, and the toolchain is arm-linux-gcc 2.95.3)

[root@localhost root]# cd /root/rt73-cvs-2008072903/Module
[root@localhost Module]# make KERNDIR=/root/EBD2410 PATCHLEVEL=4 arm
make[1] Entering directory `/root/EBD2410'
scripts/split-include include/linux/autoconf.h include/config
make -C /root/rt73-cvs-2008072903/Module CFLAGS="-D__KERNEL__ -I/root/EBD2410/i
nclude -Wall -Wstrict-prototypes -Wno-trigraphs -Os -mapcs -fno-strict-aliasing
-fno-common -fno-common -pipe -mapcs-32 -march=armv4 -mtune=arm9tdmi -mshort-loa
d-bytes -msoft-float -DMODULE" MAKING_MODULES=1 modules
make[2] Entering directory `/root/rt73-cvs-2008072903/Module'
/usr/local/arm/2.95.3/bin/arm-linux-gcc -D__KERNEL__ -I/root/EBD2410/include -Wa
ll -Wstrict-prototypes -Wno-trigraphs -Os -mapcs -fno-strict-aliasing -fno-commo
n -fno-common -pipe -mapcs-32 -march=armv4 -mtune=arm9tdmi -mshort-load-bytes -m
BUILD_BASENAME=rtmp_main -c -o rtmp_main.o rtmp_main.c
In file included from rtmp_main.c36
rt_config.h93 linux/firmware.h No such file or directory
In file included from rt_config.h202,
from rtmp_main.c36
rtmp.h715 warning unnamed struct/union that defines no instances
rtmp_main.c In function `usb_rtusb_init'
rtmp_main.c2287 `FIRMWARE_NAME_MAX' undeclared (first use in this function)
rtmp_main.c2287 (Each undeclared identifier is reported only once
rtmp_main.c2287 for each function it appears in.)
make[2] *** [rtmp_main.o] Error 1
make[2] Leaving directory `/root/rt73-cvs-2008072903/Module'
make[1] *** [_mod_/root/rt73-cvs-2008072903/Module] Error 2
make[1] Leaving directory `/root/EBD2410'
rt73.o failed to build!
make *** [arm] Error 1
[root@localhost Module]#

Thanks by the way!


31-07-2008 17:38:33

Is there any firmware loading mechanism compiled in your kernel? Then, you'll also need the relevant user-level tools, such as hotplug or udev (though I'm not sure if that last one can be used with 2.4 kernels).



31-07-2008 20:32:25


Assuming your kernel sources are properly installed, then your compiler may be too old.

If you upgrade your compiler, you may find you need to also install this kernel patch [urlkb8thger][/urlkb8thger]
in order to get a clean compile.


01-08-2008 00:17:48

Firstly,thanks for your advice.
However, i have no better choice than compiling the source code by this arm-linux-gcc 2.95.3. For the kernel codes and other programs are all crosscompiled by this toolchain.
Do you have any method to solve the problem instead of upgrading the gcc version of the cross compiler?


01-08-2008 01:05:38

Hi peterhu,

As long as your kernel sources are installed correctly, then I'm afraid not. Time moves on and code is added to our and other drivers that depends on recent versions of gcc to compile correctly. Resources to do downrev builds simply do not exist.

The most straightforward course I can see is to apply the kernel patch, upgrade your compiler, and rebuild the whole kernel.

If you really want a version of the driver that will build under gcc 2.95, I will do so on a fee basis. Post me a private message with your contact info, and we'll take it from there offline to the forum.



01-08-2008 13:54:56

hi,guys, i have got the rt73.o and when i entered "insmod rt73.o" in the terminal, it gave a message like this
rt73.o unresolved symbol wireless_send_event
what does this mean?


01-08-2008 15:38:17

That you must enabled wireless support (wireless extensions) in your kernel.


13-10-2008 19:06:45

hi there Vern, you wrote

[quote101pf5yz]If you really want a version of the driver that will build under gcc 2.95, I will do so on a fee basis. Post me a private message with your contact info, and we'll take it from there offline to the forum.



Seeing as your in a good mood for payment , I would like to pay you a great deal of money for you
to compile for me


in ARM Code for kernel 2.4.20 to run on a Sharp SL-C1000

I have tried tirelessly like the others in here to do this myself, but have only managed to xcompile
the 2.4.20 kernel and create a zImage. If I try then to xcompile your rt73 code, I get a lot
of error messages.

please put me out of my misery and help me ! ARRGGGHH!


13-10-2008 19:17:01

peterhu , you wrote

[quote12cs9due]hi,guys, i have got the rt73.o[/quote12cs9due]

what computer is this module for ? and what kernel version are you using ?

What is your toolchain ? and where did you get it from ?

Thanks for answering these ;-)


13-10-2008 19:47:25

Hi boltblue,

Could you provide the compiler version you're using - e.g the output of "gcc -v"?

As I mentioned earlier, it's always preferable to use the latest version of the compiler. If you're using gcc 2.95 because later versions don't compile your kernel, there is a patch available from for early 2.4 kernels that fixes that. So that is the preferred first step.

Also, can you try your compilation and attach a gzipped copy of the error messages to a posting here? e.g. Like this[code2w6rb67s]make clean all 2>errs
gzip errs[/code2w6rb67s]and attach errs.gz to your post.