Thread: [Madwifi-users] Cross Compile to ARM9 (MOXA IA241 Board)
Status: Beta
Brought to you by:
otaku
From: Jin Y. <yun...@gm...> - 2006-12-22 21:31:34
|
Dear all Has anyone have any idea how to cross compile the MadWiFi driver to the MOXA IA241 Board? Thanks YY |
From: Pavel R. <pr...@gn...> - 2006-12-22 21:52:15
|
On Sat, 2006-12-23 at 05:31 +0800, Jin YunYe wrote: > Dear all > > Has anyone have any idea how to cross compile the MadWiFi driver to > the MOXA IA241 Board? I suggest that you follow the documentation and post the exact errors if you get any. -- Regards, Pavel Roskin |
From: saravanan c. <sar...@ho...> - 2006-12-23 14:52:23
|
<html><div style='background-color:'><DIV class=RTE> <P>Hi YY,</P> <P>Try to compile as like below and then post your error wrt to your target board.</P> <P>root # make install KERNELPATH=/your_linux_kernel_path CROSSCOMPILE=arm-linux-gcc MODPATH=/your installation path</P> <P>Check out the makefile under /hal and xscale-le/be-elf wrt to your arch under hal/public.</P> <P><BR>Hope this helps you.</P> <P>Sara<BR></P></DIV> <DIV></DIV> <BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #a0c6e5 2px solid; MARGIN-RIGHT: 0px"><FONT style="FONT-SIZE: 11px; FONT-FAMILY: tahoma,sans-serif"> <HR color=#a0c6e5 SIZE=1> <DIV></DIV>From: <I>"Jin YunYe" <yun...@gm...></I><BR>To: <I>Mad...@li...</I><BR>Subject: <I>[Madwifi-users] Cross Compile to ARM9 (MOXA IA241 Board)</I><BR>Date: <I>Sat, 23 Dec 2006 05:31:30 +0800</I><BR> <DIV></DIV><BR>Dear all<BR><BR>Has anyone have any idea how to cross compile the MadWiFi driver to the MOXA IA241 Board?<BR><BR>Thanks<BR><BR>YY<BR> <DIV></DIV> <DIV></DIV><BR> <P>>-------------------------------------------------------------------------<BR>>Take Surveys. Earn Cash. Influence the Future of IT<BR>>Join SourceForge.net's Techsay panel and you'll get the chance to share your<BR>>opinions on IT & business topics through brief surveys - and earn cash<BR>>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV<BR> <P>>_______________________________________________<BR>>Madwifi-users mailing list<BR>>Mad...@li...<BR>>https://lists.sourceforge.net/lists/listinfo/madwifi-users<BR> <P></FONT></P></BLOCKQUOTE></div><br clear=all><hr>Tried the new MSN Messenger? Its cool! <a href="http://g.msn.com/8HMAENIN/2749??PS=47575" target="_top">Download now.</a> </html> |
From: Pavel R. <pr...@gn...> - 2006-12-28 22:25:43
|
Hello! On Sat, 2006-12-23 at 20:22 +0530, saravanan chanemouganandam wrote: > Hi YY, > > Try to compile as like below and then post your error wrt to your > target board. > > root # make install KERNELPATH=/your_linux_kernel_path > CROSSCOMPILE=arm-linux-gcc MODPATH=/your installation path > It should be CROSS_COMPILE, not CROSSCOMPILE. Besides, "gcc" should not be included. CROSS_COMPILE is the part that is prepended to the standard tool name. > Check out the makefile under /hal and xscale-le/be-elf wrt to your > arch under hal/public. There is no makefile there. I have updated the INSTALL file in the Subversion repository to discuss cross-compiling in more details. -- Regards, Pavel Roskin |
From: Jin Y. <yun...@gm...> - 2006-12-28 22:53:30
|
Dear Pavel and Sara I am still working on this. Just want to say thanks so much to you all. Truly YY On 12/29/06, Pavel Roskin <pr...@gn...> wrote: > > Hello! > > On Sat, 2006-12-23 at 20:22 +0530, saravanan chanemouganandam wrote: > > Hi YY, > > > > Try to compile as like below and then post your error wrt to your > > target board. > > > > root # make install KERNELPATH=/your_linux_kernel_path > > CROSSCOMPILE=arm-linux-gcc MODPATH=/your installation path > > > It should be CROSS_COMPILE, not CROSSCOMPILE. Besides, "gcc" should not > be included. CROSS_COMPILE is the part that is prepended to the > standard tool name. > > > Check out the makefile under /hal and xscale-le/be-elf wrt to your > > arch under hal/public. > > There is no makefile there. > > I have updated the INSTALL file in the Subversion repository to discuss > cross-compiling in more details. > > -- > Regards, > Pavel Roskin > > > |
From: Jin Y. <yun...@gm...> - 2006-12-27 15:10:53
|
Dear Pavel and Sara Thanks for your replies, here is the message after I do "make clean" and then "make TARGET=arm9-le-thumb-elf", I coloured the whole thing and highlighted the error message. root:~/Desktop/madwifi-0.9.2.1 # make TARGET=arm9-le-thumb-elf Checking requirements... ok. Checking kernel configuration... ok. make -C /lib/modules/2.6.16.21-0.25-smp/build SUBDIRS=/root/Desktop/madwifi- 0.9.2.1 modules make[1]: Entering directory `/usr/src/linux-2.6.16.21-0.25-obj/i386/smp' make -C ../../../linux-2.6.16.21-0.25 O=../linux-2.6.16.21-0.25-obj/i386/smp modules CC [M] /root/Desktop/madwifi- 0.9.2.1/ath/ah_osdep.o cc1: error: unrecognized command line option "-mthumb" cc1: error: unrecognized command line option "-mlittle-endian" make[5]: *** [/root/Desktop/madwifi- 0.9.2.1/ath/ah_osdep.o] Error 1 make[4]: *** [/root/Desktop/madwifi-0.9.2.1/ath ] Error 2 make[3]: *** [_module_/root/Desktop/madwifi-0.9.2.1] Error 2 make[2]: *** [modules] Error 2 make[1]: *** [modules] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.16.21-0.25-obj/i386/smp' make: *** [modules] Error 2 I figure it may be the problem of the gcc compiler, I am using SuSe10.1, the gcc's version is 4.1.0 Thanks Truly Yours YY On 12/23/06, Jin YunYe <yun...@gm...> wrote: > > Dear all > > Has anyone have any idea how to cross compile the MadWiFi driver to the > MOXA IA241 Board? > > Thanks > > YY > |
From: Pavel R. <pr...@gn...> - 2006-12-28 22:47:40
|
Hello! On Wed, 2006-12-27 at 23:10 +0800, Jin YunYe wrote: > Thanks for your replies, here is the message after I do "make clean" > and then "make TARGET=arm9-le-thumb-elf", I coloured the whole thing > and highlighted the error message. Please, write in plain text without HTML and don't top-post. It will make it much easier to reply to your messages. I think visual effects are not worth the trouble. > root:~/Desktop/madwifi-0.9.2.1 # make TARGET=arm9-le-thumb-elf > Checking requirements... ok. > Checking kernel configuration... ok. > make -C /lib/modules/2.6.16.21-0.25-smp/build It seems to me the build system is using a wrong kernel. You need to use KERNELPATH to point the build system to the configured sources of the kernel you are compiling for. > SUBDIRS=/root/Desktop/madwifi- 0.9.2.1 modules > make[1]: Entering directory `/usr/src/linux- > 2.6.16.21-0.25-obj/i386/smp' > make -C ../../../linux-2.6.16.21-0.25 > O=../linux-2.6.16.21-0.25-obj/i386/smp modules > CC [M] /root/Desktop/madwifi- 0.9.2.1/ath/ah_osdep.o > cc1: error: unrecognized command line option "-mthumb" > cc1: error: unrecognized command line option "-mlittle-endian" Apparently, the native compiler is used. You should specify CROSS_COMPILE. It turns out that cross compilation was badly documented in the sources. I have added some more information to the INSTALL file in Subversion: http://madwifi.org/browser/trunk/INSTALL > I figure it may be the problem of the gcc compiler, I am using > SuSe10.1, the gcc's version is 4.1.0 > You need a cross-compiler, quite obviously. The native compiler cannot compile for ARM. -- Regards, Pavel Roskin |
From: Jin Y. <yun...@gm...> - 2006-12-29 09:03:43
|
Hi, Pavel Thanks for your reply. There is still two problem I am not so sure. First, how should I configure the Linux Kernel? The one in the embedded computer is version 2.6.9. The embedded computer is using ARM9 32-bit RISC CPU, 192 MHz. Anything I must specify in the "menuconfig"? Second, if we ignore the kernel configuration thing for the time being, and do "linux-rucz:~/Desktop/madwifi-0.9.2.1 # make KERNELPATH=/root/Desktop/linux269 CROSS_COMPILE=arm-linux-" Error message is like "Checking requirements... ok. Checking kernel configuration... ok. make -C /root/Desktop/linux269 SUBDIRS=/root/Desktop/madwifi-0.9.2.1 modules /root/Desktop/linux269/scripts/gcc-version.sh: line 11: arm-linux-gcc: command not found /root/Desktop/linux269/scripts/gcc-version.sh: line 12: arm-linux-gcc: command not found make[1]: Entering directory `/root/Desktop/linux269' CC [M] /root/Desktop/madwifi-0.9.2.1/ath/ah_osdep.o /bin/sh: arm-linux-gcc: command not found make[3]: *** [/root/Desktop/madwifi-0.9.2.1/ath/ah_osdep.o] Error 127 make[2]: *** [/root/Desktop/madwifi-0.9.2.1/ath] Error 2 make[1]: *** [_module_/root/Desktop/madwifi-0.9.2.1] Error 2 make[1]: Leaving directory `/root/Desktop/linux269' make: *** [modules] Error 2 " Do I have to change anything in the gcc-version.sh file to tell compiler where the arm-linux-gcc is? On my host computer, arm-linux-gcc is installed in /usr/local/arm-linux Thanks YY On 12/29/06, Pavel Roskin <pr...@gn...> wrote: > Hello! > > On Wed, 2006-12-27 at 23:10 +0800, Jin YunYe wrote: > > > Thanks for your replies, here is the message after I do "make clean" > > and then "make TARGET=arm9-le-thumb-elf", I coloured the whole thing > > and highlighted the error message. > > Please, write in plain text without HTML and don't top-post. It will > make it much easier to reply to your messages. I think visual effects > are not worth the trouble. > > > root:~/Desktop/madwifi-0.9.2.1 # make TARGET=arm9-le-thumb-elf > > Checking requirements... ok. > > Checking kernel configuration... ok. > > make -C /lib/modules/2.6.16.21-0.25-smp/build > > It seems to me the build system is using a wrong kernel. You need to > use KERNELPATH to point the build system to the configured sources of > the kernel you are compiling for. > > > SUBDIRS=/root/Desktop/madwifi- 0.9.2.1 modules > > make[1]: Entering directory `/usr/src/linux- > > 2.6.16.21-0.25-obj/i386/smp' > > make -C ../../../linux-2.6.16.21-0.25 > > O=../linux-2.6.16.21-0.25-obj/i386/smp modules > > CC [M] /root/Desktop/madwifi- 0.9.2.1/ath/ah_osdep.o > > cc1: error: unrecognized command line option "-mthumb" > > cc1: error: unrecognized command line option "-mlittle-endian" > > Apparently, the native compiler is used. You should specify > CROSS_COMPILE. > > It turns out that cross compilation was badly documented in the sources. > I have added some more information to the INSTALL file in Subversion: > > http://madwifi.org/browser/trunk/INSTALL > > > I figure it may be the problem of the gcc compiler, I am using > > SuSe10.1, the gcc's version is 4.1.0 > > > You need a cross-compiler, quite obviously. The native compiler cannot > compile for ARM. > > -- > Regards, > Pavel Roskin > > > |
From: Frank <fra...@ya...> - 2006-12-29 15:52:30
|
--- Jin YunYe <yun...@gm...> wrote: > Hi, Pavel > > Thanks for your reply. There is still two problem I am not so > sure. > > First, how should I configure the Linux Kernel? The one in the > embedded computer is version 2.6.9. The embedded computer is > using > ARM9 32-bit RISC CPU, 192 MHz. Anything I must specify in the > "menuconfig"? > > Second, if we ignore the kernel configuration thing for the > time being, and do > > "linux-rucz:~/Desktop/madwifi-0.9.2.1 # make > KERNELPATH=/root/Desktop/linux269 CROSS_COMPILE=arm-linux-" > Error message is like > "Checking requirements... ok. > Checking kernel configuration... ok. > make -C /root/Desktop/linux269 > SUBDIRS=/root/Desktop/madwifi-0.9.2.1 modules > /root/Desktop/linux269/scripts/gcc-version.sh: line 11: > arm-linux-gcc: > command not found > /root/Desktop/linux269/scripts/gcc-version.sh: line 12: > arm-linux-gcc: > command not found > make[1]: Entering directory `/root/Desktop/linux269' > CC [M] /root/Desktop/madwifi-0.9.2.1/ath/ah_osdep.o > /bin/sh: arm-linux-gcc: command not found > make[3]: *** [/root/Desktop/madwifi-0.9.2.1/ath/ah_osdep.o] > Error 127 > make[2]: *** [/root/Desktop/madwifi-0.9.2.1/ath] Error 2 > make[1]: *** [_module_/root/Desktop/madwifi-0.9.2.1] Error 2 > make[1]: Leaving directory `/root/Desktop/linux269' > make: *** [modules] Error 2 > " > Do I have to change anything in the gcc-version.sh file to > tell > compiler where the arm-linux-gcc is? > > On my host computer, arm-linux-gcc is installed in > /usr/local/arm-linux > > Thanks > > YY export PATH=/usr/local/arm-linux:$PATH __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
From: Pavel R. <pr...@gn...> - 2006-12-29 17:15:02
|
On Fri, 2006-12-29 at 17:03 +0800, Jin YunYe wrote: > Hi, Pavel > > Thanks for your reply. There is still two problem I am not so sure. > > First, how should I configure the Linux Kernel? The one in the > embedded computer is version 2.6.9. The embedded computer is using > ARM9 32-bit RISC CPU, 192 MHz. Anything I must specify in the > "menuconfig"? Specify ARCH=arm on the command line. Then you will be asked about ARM options. > Second, if we ignore the kernel configuration thing for the time being, and do > > "linux-rucz:~/Desktop/madwifi-0.9.2.1 # make > KERNELPATH=/root/Desktop/linux269 CROSS_COMPILE=arm-linux-" > Error message is like > "Checking requirements... ok. > Checking kernel configuration... ok. > make -C /root/Desktop/linux269 SUBDIRS=/root/Desktop/madwifi-0.9.2.1 modules > /root/Desktop/linux269/scripts/gcc-version.sh: line 11: arm-linux-gcc: > command not found If arm-linux-gcc is not in PATH, provide full path in CROSS_COMPILE, e.g. make CROSS_COMPILE=/usr/local/arm-linux/bin/arm-linux- > Do I have to change anything in the gcc-version.sh file to tell > compiler where the arm-linux-gcc is? Generally, it's better to avoid changing any files that are not specifically designated for that purpose. In most cases, there are other ways to affect the desired behavior. -- Regards, Pavel Roskin |
From: Jin Y. <yun...@gm...> - 2007-01-03 18:37:36
|
Dear folks, I followed what you have taught me, there is a long list of error message, I copy part of it below: linux-rucz:~/Desktop/madwifi-0.9.2.1 # make KERNELPATH=/root/Desktop/linux269 CROSS_COMPILE=/usr/local/arm-linux/bin/arm-linux- TARGET=arm9-le-thumb-elf Error Message Sample 1: include/linux/elf.h:222: warning: type defaults to `int' in declaration of `r_info' include/linux/elf.h:222: warning: data definition has no type or storage class include/linux/elf.h:223: error: parse error before "r_addend" include/linux/elf.h:223: warning: type defaults to `int' in declaration of `r_addend' include/linux/elf.h:223: warning: data definition has no type or storage class include/linux/elf.h:224: warning: type defaults to `int' in declaration of `Elf64_Rela' include/linux/elf.h:224: warning: data definition has no type or storage class include/linux/elf.h:227: error: parse error before "Elf32_Word" include/linux/elf.h:227: warning: no semicolon at end of struct or union include/linux/elf.h:228: warning: type defaults to `int' in declaration of `st_value' Error Message Sample 2: /root/Desktop/madwifi-0.9.2.1/hal/ah.h:493: error: parse error before "lpAckDuration" /root/Desktop/madwifi-0.9.2.1/hal/ah.h:493: warning: type defaults to `int' in declaration of `lpAckDuration' /root/Desktop/madwifi-0.9.2.1/hal/ah.h:493: warning: data definition has no type or storage class /root/Desktop/madwifi-0.9.2.1/hal/ah.h:494: error: parse error before "spAckDuration" /root/Desktop/madwifi-0.9.2.1/hal/ah.h:494: warning: type defaults to `int' in declaration of `spAckDuration' /root/Desktop/madwifi-0.9.2.1/hal/ah.h:494: warning: data definition has no type or storage class /root/Desktop/madwifi-0.9.2.1/hal/ah.h:495: warning: type defaults to `int' in declaration of `info' /root/Desktop/madwifi-0.9.2.1/hal/ah.h:495: error: `info' used prior to declaration /root/Desktop/madwifi-0.9.2.1/hal/ah.h:495: warning: data definition has no type or storage class Error message sample 4 (in the end) include/linux/elf.h:438: warning: array `_DYNAMIC' assumed to have one element include/linux/sched.h:217: error: storage size of `mmap_sem' isn't known include/linux/sched.h:251: error: storage size of `default_kioctx' isn't known include/linux/sched.h:276: error: storage size of `shared_pending' isn't known include/linux/sched.h:380: error: storage size of `wall_to_prev' isn't known include/linux/sched.h:511: error: storage size of `start_time' isn't known include/linux/sched.h:522: error: storage size of `rlim' isn't known include/linux/sched.h:530: error: storage size of `thread' isn't known include/linux/sched.h:542: error: storage size of `pending' isn't known include/linux/stat.h:68: error: storage size of `atime' isn't known include/linux/stat.h:69: error: storage size of `mtime' isn't known include/linux/stat.h:70: error: storage size of `ctime' isn't known include/linux/fs.h:277: error: storage size of `ia_atime' isn't known include/linux/fs.h:278: error: storage size of `ia_mtime' isn't known include/linux/fs.h:279: error: storage size of `ia_ctime' isn't known include/linux/quota.h:223: error: storage size of `dq_dqb' isn't known include/linux/fs.h:357: error: storage size of `bd_sem' isn't known include/linux/fs.h:358: error: storage size of `bd_mount_sem' isn't known include/linux/fs.h:432: error: storage size of `i_atime' isn't known include/linux/fs.h:433: error: storage size of `i_mtime' isn't known include/linux/fs.h:434: error: storage size of `i_ctime' isn't known include/linux/fs.h:442: error: storage size of `i_sem' isn't known include/linux/fs.h:443: error: storage size of `i_alloc_sem' isn't known include/linux/fs.h:449: error: storage size of `i_data' isn't known include/linux/fs.h:576: error: storage size of `f_owner' isn't known include/linux/fs.h:754: error: storage size of `s_umount' isn't known include/linux/fs.h:755: error: storage size of `s_lock' isn't known include/linux/fs.h:782: error: storage size of `s_vfs_rename_sem' isn't known make[3]: *** [/root/Desktop/madwifi-0.9.2.1/ath/ah_osdep.o] Error 1 make[2]: *** [/root/Desktop/madwifi-0.9.2.1/ath] Error 2 make[1]: *** [_module_/root/Desktop/madwifi-0.9.2.1] Error 2 make[1]: Leaving directory `/root/Desktop/linux269' make: *** [modules] Error 2 Sorry I cannot provide the full error message list because I do not know the way to get them all in a file. Please teach me so if you know and I will send you the file. Thanks and Happy New Year!! YY |
From: Pavel R. <pr...@gn...> - 2007-01-03 18:52:42
|
Hello! On Thu, 2007-01-04 at 02:37 +0800, Jin YunYe wrote: > Dear folks, I followed what you have taught me, there is a long list > of error message, I copy part of it below: > > linux-rucz:~/Desktop/madwifi-0.9.2.1 # make > KERNELPATH=/root/Desktop/linux269 > CROSS_COMPILE=/usr/local/arm-linux/bin/arm-linux- > TARGET=arm9-le-thumb-elf > > Error Message Sample 1: > > include/linux/elf.h:222: warning: type defaults to `int' in > declaration of `r_info' > include/linux/elf.h:222: warning: data definition has no type or storage class > include/linux/elf.h:223: error: parse error before "r_addend" You omitted an important part, namely what the build system was trying to compile. The error reported is in Linux kernel. I suggest that you fix your build system so you can build the kernel. This is not related to MadWifi. There are forums for ARM and cross compiling. Please ask there. Once you can compile the kernel, please try compiling MadWifi and report the problems here. > Sorry I cannot provide the full error message list because I do not > know the way to get them all in a file. Please teach me so if you know > and I will send you the file. make >log 2>&1 This redirects both stdout and stderr to the same file in the order in which it would normally appear on screen. -- Regards, Pavel Roskin |
From: Jin Y. <yun...@gm...> - 2007-01-04 00:44:57
|
On 1/4/07, Pavel Roskin <pr...@gn...> wrote: > Hello! > > On Thu, 2007-01-04 at 02:37 +0800, Jin YunYe wrote: > > Dear folks, I followed what you have taught me, there is a long list > > of error message, I copy part of it below: > > > > linux-rucz:~/Desktop/madwifi-0.9.2.1 # make > > KERNELPATH=/root/Desktop/linux269 > > CROSS_COMPILE=/usr/local/arm-linux/bin/arm-linux- > > TARGET=arm9-le-thumb-elf > > > > Error Message Sample 1: > > > > include/linux/elf.h:222: warning: type defaults to `int' in > > declaration of `r_info' > > include/linux/elf.h:222: warning: data definition has no type or storage class > > include/linux/elf.h:223: error: parse error before "r_addend" > > You omitted an important part, namely what the build system was trying > to compile. > > The error reported is in Linux kernel. I suggest that you fix your > build system so you can build the kernel. This is not related to > MadWifi. There are forums for ARM and cross compiling. Please ask > there. Once you can compile the kernel, please try compiling MadWifi > and report the problems here. > > > Sorry I cannot provide the full error message list because I do not > > know the way to get them all in a file. Please teach me so if you know > > and I will send you the file. > > make >log 2>&1 > > This redirects both stdout and stderr to the same file in the order in > which it would normally appear on screen. > > -- > Regards, > Pavel Roskin I have build the driver successfully!!! I transfer it to USB storage and mount the usb on the board. I tried wlanconfig and it seems to work. Thanks so much to you folks for all the help. You really have taught me so much. Now, when I plug in the PCMCIA card (NetGear 511T using Atheros) and do a ifconfig (the command comes with the board's operating system) I still cannot find it. modprobe ath_pci doesn't seems to work. If I am not wrong, this command is not available in that embedded linux system. Could someone teach me how to activate the card on the embedded board? Thanks again. YY P.S. Sorry for the top postings... |
From: Jin Y. <yun...@gm...> - 2007-01-04 15:55:47
|
On 1/4/07, Jin YunYe <yun...@gm...> wrote: > On 1/4/07, Pavel Roskin <pr...@gn...> wrote: > > Hello! > > > > On Thu, 2007-01-04 at 02:37 +0800, Jin YunYe wrote: > > > Dear folks, I followed what you have taught me, there is a long list > > > of error message, I copy part of it below: > > > > > > linux-rucz:~/Desktop/madwifi-0.9.2.1 # make > > > KERNELPATH=/root/Desktop/linux269 > > > CROSS_COMPILE=/usr/local/arm-linux/bin/arm-linux- > > > TARGET=arm9-le-thumb-elf > > > > > > Error Message Sample 1: > > > > > > include/linux/elf.h:222: warning: type defaults to `int' in > > > declaration of `r_info' > > > include/linux/elf.h:222: warning: data definition has no type or storage class > > > include/linux/elf.h:223: error: parse error before "r_addend" > > > > You omitted an important part, namely what the build system was trying > > to compile. > > > > The error reported is in Linux kernel. I suggest that you fix your > > build system so you can build the kernel. This is not related to > > MadWifi. There are forums for ARM and cross compiling. Please ask > > there. Once you can compile the kernel, please try compiling MadWifi > > and report the problems here. > > > > > Sorry I cannot provide the full error message list because I do not > > > know the way to get them all in a file. Please teach me so if you know > > > and I will send you the file. > > > > make >log 2>&1 > > > > This redirects both stdout and stderr to the same file in the order in > > which it would normally appear on screen. > > > > -- > > Regards, > > Pavel Roskin > > I have build the driver successfully!!! I transfer it to USB storage > and mount the usb on the board. I tried wlanconfig and it seems to > work. Thanks so much to you folks for all the help. You really have > taught me so much. > > Now, when I plug in the PCMCIA card (NetGear 511T using Atheros) and > do a ifconfig (the command comes with the board's operating system) I > still cannot find it. modprobe ath_pci doesn't seems to work. If I am > not wrong, this command is not available in that embedded linux > system. > > Could someone teach me how to activate the card on the embedded board? > > Thanks again. > > YY > P.S. Sorry for the top postings... > I successully cross compiled the madwifi for my board. I put the built folder in a usb storage drive and mount the driver in my Moxa IA 241 board.' Now the problem is I cannot load modules I first do modprobe ath_pci. there is no available command like modprobe provided in the board Linux 2.6.9. So I cd to /ath and did a root@Moxa:/mnt/usbstorage/madwifi-0.9.2.1/ath# insmod ath_pci.ko the following information comes out Using ath_pci.ko insmod: cannot insert `ath_pci.ko': Invalid module format (-1): Exec format error Could you tell me what this means and how could I do a load? Thx |
From: Pavel R. <pr...@gn...> - 2007-01-04 16:21:11
|
On Thu, 2007-01-04 at 23:55 +0800, Jin YunYe wrote: > I successully cross compiled the madwifi for my board. I put the built > folder in a usb storage drive and mount the driver in my Moxa IA 241 > board.' > > Now the problem is I cannot load modules > > I first do modprobe ath_pci. there is no available command like > modprobe provided in the board Linux 2.6.9. > > So I cd to /ath and did a > > root@Moxa:/mnt/usbstorage/madwifi-0.9.2.1/ath# insmod ath_pci.ko > > the following information comes out > > Using ath_pci.ko > insmod: cannot insert `ath_pci.ko': Invalid module format (-1): Exec > format error See kernel messages using dmesg. Most likely cause is compiler version mismatch, i.e. the kernel and the module were compiled by different versions of gcc. It's also possible that the module was compiled for a different architecture. Try following commands: file ath_pci.ko modinfo ath_pci.ko -- Regards, Pavel Roskin |
From: Jin Y. <yun...@gm...> - 2007-01-04 18:40:20
|
On 1/5/07, Pavel Roskin <pr...@gn...> wrote: > On Thu, 2007-01-04 at 23:55 +0800, Jin YunYe wrote: > > I successully cross compiled the madwifi for my board. I put the built > > folder in a usb storage drive and mount the driver in my Moxa IA 241 > > board.' > > > > Now the problem is I cannot load modules > > > > I first do modprobe ath_pci. there is no available command like > > modprobe provided in the board Linux 2.6.9. > > > > So I cd to /ath and did a > > > > root@Moxa:/mnt/usbstorage/madwifi-0.9.2.1/ath# insmod ath_pci.ko > > > > the following information comes out > > > > Using ath_pci.ko > > insmod: cannot insert `ath_pci.ko': Invalid module format (-1): Exec > > format error > > See kernel messages using dmesg. > > Most likely cause is compiler version mismatch, i.e. the kernel and the > module were compiled by different versions of gcc. It's also possible > that the module was compiled for a different architecture. Try > following commands: > > file ath_pci.ko > modinfo ath_pci.ko > > -- > Regards, > Pavel Roskin > Hi, thanks. Here is the outcome of the above two command linux-rucz:~/Desktop/madwifi-0.9.2.1/ath # file ath_pci.ko ath_pci.ko: ELF 32-bit LSB relocatable, ARM, version 1 (ARM), not stripped linux-rucz:~/Desktop/madwifi-0.9.2.1/ath # modinfo ath_pci.ko filename: ath_pci.ko author: Errno Consulting, Sam Leffler description: Support for Atheros 802.11 wireless LAN cards. version: 0.9.2.1 license: Dual BSD/GPL vermagic: 2.6.9-moxa ARMv3 gcc-3.3 depends: ath_hal,ath_rate_sample,wlan alias: pci:v0000168Cd00000007sv*sd*bc*sc*i* alias: pci:v0000168Cd00000012sv*sd*bc*sc*i* alias: pci:v0000168Cd00000013sv*sd*bc*sc*i* alias: pci:v0000A727d00000013sv*sd*bc*sc*i* alias: pci:v000010B7d00000013sv*sd*bc*sc*i* alias: pci:v0000168Cd00001014sv*sd*bc*sc*i* alias: pci:v0000168Cd0000101Asv*sd*bc*sc*i* alias: pci:v0000168Cd00000015sv*sd*bc*sc*i* alias: pci:v0000168Cd00000016sv*sd*bc*sc*i* alias: pci:v0000168Cd00000017sv*sd*bc*sc*i* alias: pci:v0000168Cd00000018sv*sd*bc*sc*i* alias: pci:v0000168Cd00000019sv*sd*bc*sc*i* alias: pci:v0000168Cd0000001Asv*sd*bc*sc*i* alias: pci:v0000168Cd0000001Bsv*sd*bc*sc*i* alias: pci:v0000168Cd0000001Csv*sd*bc*sc*i* alias: pci:v0000168Cd0000001Dsv*sd*bc*sc*i* alias: pci:v0000168Cd00009013sv*sd*bc*sc*i* parm: ath_debug:Load-time debug output enable parm: autocreate:Create ath device in [sta|ap|wds|adhoc|ahdemo|monitor] mode. defaults to sta, use 'none' to disable parm: rfkill:Enable/disable RFKILL capability parm: xchanmode:Enable/disable extended channel mode parm: outdoor:Enable/disable outdoor use parm: countrycode:Override default country code Thanks YY |
From: Pavel R. <pr...@gn...> - 2007-01-04 19:01:39
|
On Fri, 2007-01-05 at 02:40 +0800, Jin YunYe wrote: > On 1/5/07, Pavel Roskin <pr...@gn...> wrote: > > See kernel messages using dmesg. Whether you are top-posting or not, if you quote the message wholesale and don't reply to it point-by-point, you will miss something. The kernel messages are essential to understanding the problem. It you don't have dmesg, tcheck the logs in /var/log. If klogd is not running try "cat /proc/kmsg" > Hi, thanks. Here is the outcome of the above two command > > linux-rucz:~/Desktop/madwifi-0.9.2.1/ath # file ath_pci.ko > ath_pci.ko: ELF 32-bit LSB relocatable, ARM, version 1 (ARM), not stripped OK, at least we know that the architecture is ARM. > linux-rucz:~/Desktop/madwifi-0.9.2.1/ath # modinfo ath_pci.ko > filename: ath_pci.ko > author: Errno Consulting, Sam Leffler > description: Support for Atheros 802.11 wireless LAN cards. > version: 0.9.2.1 > license: Dual BSD/GPL > vermagic: 2.6.9-moxa ARMv3 gcc-3.3 > depends: ath_hal,ath_rate_sample,wlan It's possible that you didn't load the dependencies. insmod doesn't load the required modules automatically. You should load them individually: insmod ath_hal.ko insmod wlan.ko insmod ath_rate_sample.ko insmod ath_pci.ko insmod wlan_scan_ap.ko -- Regards, Pavel Roskin |
From: Jin Y. <yun...@gm...> - 2007-01-05 01:39:56
|
Hi On 1/5/07, Pavel Roskin <pr...@gn...> wrote: > On Fri, 2007-01-05 at 02:40 +0800, Jin YunYe wrote: > > On 1/5/07, Pavel Roskin <pr...@gn...> wrote: > > > See kernel messages using dmesg. > > Whether you are top-posting or not, if you quote the message wholesale > and don't reply to it point-by-point, you will miss something. The > kernel messages are essential to understanding the problem. It you > don't have dmesg, tcheck the logs in /var/log. If klogd is not running > try "cat /proc/kmsg" Here is the relevant message about the compiler when I do cat /proc/kmsg <3>ath_hal: version magic '2.6.9-moxa ARMv3 gcc-3.3' should be '2.6.9-uc0 ARMv4 gcc-3.3' Does that mean I installed the wrong arm-linux version? The one I am currently using is from the manufacture of the board. > > > Hi, thanks. Here is the outcome of the above two command > > > > linux-rucz:~/Desktop/madwifi-0.9.2.1/ath # file ath_pci.ko > > ath_pci.ko: ELF 32-bit LSB relocatable, ARM, version 1 (ARM), not stripped > > OK, at least we know that the architecture is ARM. > > > linux-rucz:~/Desktop/madwifi-0.9.2.1/ath # modinfo ath_pci.ko > > filename: ath_pci.ko > > author: Errno Consulting, Sam Leffler > > description: Support for Atheros 802.11 wireless LAN cards. > > version: 0.9.2.1 > > license: Dual BSD/GPL > > vermagic: 2.6.9-moxa ARMv3 gcc-3.3 > > depends: ath_hal,ath_rate_sample,wlan > > It's possible that you didn't load the dependencies. insmod doesn't > load the required modules automatically. You should load them > individually: > > insmod ath_hal.ko > insmod wlan.ko > insmod ath_rate_sample.ko > insmod ath_pci.ko > insmod wlan_scan_ap.ko When I try to do insmod ath_hal.ko It says that root@Moxa:/mnt/usbstorage/madwifi-0.9.2.1/ath# insmod ath_hal.o Using ath_hal.o insmod: cannot insert `ath_hal.o': Invalid module format (-1): Exec format error Thanks YY > > -- > Regards, > Pavel Roskin > > > |
From: Pavel R. <pr...@gn...> - 2007-01-05 03:12:39
|
Quoting Jin YunYe <yun...@gm...>: > Here is the relevant message about the compiler when I do cat /proc/kmsg > > <3>ath_hal: version magic '2.6.9-moxa ARMv3 gcc-3.3' should be > '2.6.9-uc0 ARMv4 gcc-3.3' > > Does that mean I installed the wrong arm-linux version? The one I am > currently using is from the manufacture of the board. It means that you compiled the driver for a different kernel. The kernel version mismatches, which means that the sources are different. The CPU "flavor" mismatches, which means that the kernels were configured for different processors. Either use your kernel on the board (if you actually have the board specific code and configuration, of course) or find the sources and the configuration of the kernel you are running and compile MadWifi for it. > When I try to do insmod ath_hal.ko > It says that > > root@Moxa:/mnt/usbstorage/madwifi-0.9.2.1/ath# insmod ath_hal.o > Using ath_hal.o > insmod: cannot insert `ath_hal.o': Invalid module format (-1): Exec format > error The order will matter once this problem is fixed. -- Regards, Pavel Roskin |
From: Jin Y. <yun...@gm...> - 2007-01-05 03:31:37
|
On 1/4/07, Pavel Roskin <pr...@gn...> wrote: > Quoting Jin YunYe <yun...@gm...>: > > > Here is the relevant message about the compiler when I do cat /proc/kmsg > > > > <3>ath_hal: version magic '2.6.9-moxa ARMv3 gcc-3.3' should be > > '2.6.9-uc0 ARMv4 gcc-3.3' > > > > Does that mean I installed the wrong arm-linux version? The one I am > > currently using is from the manufacture of the board. > > It means that you compiled the driver for a different kernel. The kernel > version mismatches, which means that the sources are different. The CPU > "flavor" mismatches, which means that the kernels were configured for different > processors. Does it mean that the '2.6.9-uc0 ARMv4 is the kernel version which is running on my Embedded board? And I somehow compile it against the '2.6.9-moxa ARMv3? > Either use your kernel on the board (if you actually have the board specific > code and configuration, of course) or find the sources and the configuration of > the kernel you are running and compile MadWifi for it. The manufacturer does not provide the much information about their kernel or source code. But I doubt it is the uClinux OS. > > > When I try to do insmod ath_hal.ko > > It says that > > > > root@Moxa:/mnt/usbstorage/madwifi-0.9.2.1/ath# insmod ath_hal.o > > Using ath_hal.o > > insmod: cannot insert `ath_hal.o': Invalid module format (-1): Exec format > > error > > The order will matter once this problem is fixed. > > -- > Regards, > Pavel Roskin > |
From: Pavel R. <pr...@gn...> - 2007-01-05 06:01:28
|
Quoting Jin YunYe <yun...@gm...>: > Does it mean that the '2.6.9-uc0 ARMv4 is the kernel version which is > running on my Embedded board? And I somehow compile it against the > '2.6.9-moxa ARMv3? Yes. > > Either use your kernel on the board (if you actually have the board > specific > > code and configuration, of course) or find the sources and the > configuration of > > the kernel you are running and compile MadWifi for it. > > The manufacturer does not provide the much information about their > kernel or source code. But I doubt it is the uClinux OS. Actually, "uc0" probably means that the kernel sources are from the uClinux project. Board specific patches are unlikely to have any effect on MadWifi modules, so you can compile it against plain 2.6.9-uc0. You also need to set the configuration so that the modules are marked ARMv4. Looking at a current kernel, it seems that you need CONFIG_CPU_32v4T or CONFIG_CPU_32v4 defined in .config, then arch/arm/Makefile defines __LINUX_ARM_ARCH__ to 4, and this goes to the module magic in include/asm-arm/module.h Then chances are you'll get MadWifi to work. -- Regards, Pavel Roskin |
From: Jin Y. <yun...@gm...> - 2007-01-05 10:58:36
|
On 1/5/07, Pavel Roskin <pr...@gn...> wrote: > Actually, "uc0" probably means that the kernel sources are from the uClinux > project. Board specific patches are unlikely to have any effect on MadWifi > modules, so you can compile it against plain 2.6.9-uc0. I download standard Linux 2.6.9 and patched it with the uClinux 2.6.9 patch > You also need to set the configuration so that the modules are marked ARMv4. > Looking at a current kernel, it seems that you need CONFIG_CPU_32v4T or > CONFIG_CPU_32v4 defined in .config, then arch/arm/Makefile defines > __LINUX_ARM_ARCH__ to 4, and this goes to the module magic in > include/asm-arm/module.h I did that in .config, I add fhe following lines CONFIG_CPU_32v4=y CONFIG_PCI=y The second line is added because otherwise the make process will ask me to enable PCI support. > Then chances are you'll get MadWifi to work. After did all that above and compile the madwifi against this kernel, I connect to the board and do: root@Moxa:/mnt/usbstorage/madwifiarm/ath# insmod ath_hal.ko Using ath_hal.ko which is successful But when I try to do root@Moxa:/mnt/usbstorage/madwifiarm/ath# insmod ath_pci.ko Using ath_pci.ko insmod: cannot insert `ath_pci.ko': Unknown symbol in module (-1): No such file or directory Same happens to wlan.ko and ath_rate_sample.ko So I cat /proc/kmsg again and have: <4>ath_hal: module license 'Proprietary' taints kernel. <6>ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413, REGOPS_FUNC) <4>ath_pci: Unknown symbol ath_rate_tx_complete <4>ath_pci: Unknown symbol ieee80211_encap <4>ath_pci: Unknown symbol ieee80211_input <4>ath_pci: Unknown symbol ieee80211_ifattach <4>ath_pci: Unknown symbol ieee80211_beacon_update <4>ath_pci: Unknown symbol ieee80211_find_channel <4>ath_pci: Unknown symbol ieee80211_find_rxnode <4>ath_pci: Unknown symbol ath_rate_attach <4>ath_pci: Unknown symbol ether_sprintf <4>ath_pci: Unknown symbol ieee80211_vap_setup <4>ath_pci: Unknown symbol ieee80211_ifdetach <4>ath_pci: Unknown symbol ieee80211_free_node <4>ath_pci: Unknown symbol ieee80211_input_monitor <4>ath_pci: Unknown symbol ath_rate_newassoc <4>ath_pci: Unknown symbol ieee80211_crypto_newkey <4>ath_pci: Unknown symbol ieee80211_crypto_setkey <4>ath_pci: Unknown symbol ath_rate_dynamic_proc_register <4>ath_pci: Unknown symbol ieee80211_dump_pkt <4>ath_pci: Unknown symbol ieee80211_ioctl_create_vap <4>ath_pci: Unknown symbol ieee80211_dfs_test_return <4>ath_pci: Unknown symbol ieee80211_stop_running <4>ath_pci: Unknown symbol ieee80211_cipher_none <4>ath_pci: Unknown symbol ieee80211_note <4>ath_pci: Unknown symbol ieee80211_crypto_delkey <4>ath_pci: Unknown symbol capable <4>ath_pci: Unknown symbol ieee80211_media_change <4>ath_pci: Unknown symbol ieee80211_beacon_miss <4>ath_pci: Unknown symbol ieee80211_beacon_alloc <4>ath_pci: Unknown symbol ieee80211_getcfframe <4>ath_pci: Unknown symbol ieee80211_iterate_nodes <4>ath_pci: Unknown symbol netpoll_trap <4>ath_pci: Unknown symbol ieee80211_vap_attach <4>ath_pci: Unknown symbol ieee80211_ibss_merge <4>ath_pci: Unknown symbol ath_rate_node_cleanup <4>ath_pci: Unknown symbol ieee80211_send_qosnulldata <4>ath_pci: Unknown symbol ath_rate_detach <4>ath_pci: Unknown symbol ieee80211_create_vap <4>ath_pci: Unknown symbol ieee80211_wme_acnames <4>ath_pci: Unknown symbol ieee80211_input_all <4>ath_pci: Unknown symbol ieee80211_media_status <4>ath_pci: Unknown symbol ieee80211_start_running <4>ath_pci: Unknown symbol ieee80211_vap_detach <4>ath_pci: Unknown symbol ieee80211_announce <4>ath_pci: Unknown symbol ieee80211_mark_dfs <4>ath_pci: Unknown symbol ieee80211_chan2ieee <4>ath_pci: Unknown symbol ieee80211_state_name <4>ath_pci: Unknown symbol ath_rate_node_init <4>ath_pci: Unknown symbol ath_rate_findrate <4>ath_pci: Unknown symbol ieee80211_dturbo_switch <4>ath_pci: Unknown symbol ieee80211_crypto_encap <4>ath_pci: Unknown symbol ieee80211_chan2mode <4>ath_pci: Unknown symbol ieee80211_getrssi <4>ath_pci: Unknown symbol ieee80211_find_txnode <4>ath_pci: Unknown symbol ath_rate_newstate <4>ath_pci: Unknown symbol ath_rate_setupxtxdesc Thanks YY |
From: Pavel R. <pr...@gn...> - 2007-01-09 02:58:30
|
On Fri, 2007-01-05 at 18:58 +0800, Jin YunYe wrote: > Using ath_pci.ko > insmod: cannot insert `ath_pci.ko': Unknown symbol in module (-1): No > such file or directory > > Same happens to wlan.ko and ath_rate_sample.ko > > So I cat /proc/kmsg again and have: > > <4>ath_hal: module license 'Proprietary' taints kernel. > <6>ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, > RF5413, REGOPS_FUNC) > <4>ath_pci: Unknown symbol ath_rate_tx_complete [skip] > <4>ath_pci: Unknown symbol ath_rate_setupxtxdesc I don't see error messages about wlan and ath_rate_sample. When using insmod, the order of loading is important. You tried to load ath_pci before its dependencies, so it failed. It's an expected failure. You can use modinfo to find the dependencies. -- Regards, Pavel Roskin |