rt2x00.serialmonkey.com

Support forum for the rt2x00 project
It is currently Fri May 24, 2013 5:26 pm

All times are UTC




Post new topic Reply to topic  [ 10 posts ] 
Author Message
PostPosted: Sun Dec 28, 2008 12:56 am 
Offline

Joined: Sun Dec 28, 2008 12:24 am
Posts: 3
Hello,

My usb network adapter is a D-Link WUA-1340 using the Ralink 2571 (RT73) chipset.

From the rt73-cvs-daily.tar.gz file, I tried, as root, to compile the driver sources using make and received the following error:
[root@localhost Module]# make
make[1]: Entering directory `/lib/modules/2.6.9-78.0.8.EL/build1'
make[1]: *** No rule to make target `WUA-1340/Driver/Linux/cvs/rt73-cvs-2008122517 /Module'. Stop.
make[1]: Leaving directory `/lib/modules/2.6.9-78.0.8.EL/build1'
rt73.ko failed to build!
make: *** [module] Error 1

The kernel source tree was built using "The Complete Fedora Kernel Headers" article since RHEL4 was built from Fedora 4 and originally placed in the /usr/src/redhat/BUILD/kernel-2.6.9-78.0.8.EL/linux-2.6.9 folder. The contents were then copied to the /lib/modules/2.6.9-78.0.8.EL/build1 folder.

I have read the README and TESTING files in the tar.gz file, the "make in the folder root fails" article in this forum, and various articles on the internet to no avail. Does someone have a suggestion to solve this problem.

Thank you,
John


Top
 Profile  
 
PostPosted: Mon Jan 05, 2009 6:15 pm 
Offline

Joined: Sun Jun 26, 2005 10:26 am
Posts: 1685
Location: Marseille, France
Hello,
Is there a space somewhere in the absolute path of the directory you are trying to compile the module in? If so, try to compile the module elsewhere.

Regards,
Romain

_________________
RutilT developer


Top
 Profile  
 
PostPosted: Fri Jan 09, 2009 9:35 pm 
Offline

Joined: Sun Dec 28, 2008 12:24 am
Posts: 3
Helllo Romain,

Yes, I have a space in the absolute directory. I am now upgrading to RHEL5 Client-Desktop and will try compiling the rt73 module after doing this.

Thank you very much for your help,
John


Top
 Profile  
 
PostPosted: Sat Jan 10, 2009 5:48 pm 
Offline
User avatar

Joined: Sat Jan 14, 2006 6:29 pm
Posts: 897
Location: Carlsbad, California
Hi j_75080,

Also, could you post that path here? Maybe there's something clever we can do.

Thanks,

_________________
Yr Hmbl Obt Svt & c
Bryan - In favor of Big Oil. Big fan of General Grievous.


Top
 Profile  
 
PostPosted: Sun Jan 11, 2009 6:22 pm 
Offline

Joined: Sun Jun 26, 2005 10:26 am
Posts: 1685
Location: Marseille, France
By the way Vern, if my memory serves me well, ALL legacy drivers fail to compile whenever there is a space in the absolute path of the directory the tarball is extracted in, this is easily reproductable.

_________________
RutilT developer


Top
 Profile  
 
PostPosted: Tue Jan 20, 2009 5:55 pm 
Offline
User avatar

Joined: Sat Jan 14, 2006 6:29 pm
Posts: 897
Location: Carlsbad, California
Hi Spy,

Any ideas for a fix? Too much thinking on my own makes my brain sore.

Thanks,

_________________
Yr Hmbl Obt Svt & c
Bryan - In favor of Big Oil. Big fan of General Grievous.


Top
 Profile  
 
PostPosted: Thu Jan 22, 2009 10:52 pm 
Offline

Joined: Sun Jun 26, 2005 10:26 am
Posts: 1685
Location: Marseille, France
Hi,
I had a look, and tried a few things on the top of my mind, but I couldn't get things to work, it seems that the kernel makefile does not like spaces at all. I tried with another out of kernel module (not from ours), and run into the same issue.
We could simply add a check in the Makefiles to warn people about this.

Romain

_________________
RutilT developer


Top
 Profile  
 
PostPosted: Fri Jan 23, 2009 4:05 am 
Offline
User avatar

Joined: Sat Jan 14, 2006 6:29 pm
Posts: 897
Location: Carlsbad, California
Hi Spy,

Thanks for taking a look at this. Could you post an example of the path format that's causing the problem? Maybe that'll give me a clue as to what's happening.

Thanks,

_________________
Yr Hmbl Obt Svt & c
Bryan - In favor of Big Oil. Big fan of General Grievous.


Top
 Profile  
 
PostPosted: Mon Jan 26, 2009 6:04 pm 
Offline

Joined: Sun Jun 26, 2005 10:26 am
Posts: 1685
Location: Marseille, France
Just put your sources in a directory with a space in its name, say "rt73 my_module", the whole path could then be :
Code:
/home/vern/rt73 Module/

Which will cause an error like this :
Code:
make[1]: Entering directory `<kernel sources path>'
make[1]: *** No rule to make target `my_module'.  Stop.
make[1]: Leaving directory `<kernel sources path>'

_________________
RutilT developer


Top
 Profile  
 
PostPosted: Mon Feb 02, 2009 10:31 pm 
Offline

Joined: Sun Dec 28, 2008 12:24 am
Posts: 3
Hello Vern,

My path used to originally compile the sources was:
/root/Desktop/D-Link WUA-1340/Driver/Linux/cvs/2008122517/rt73-cvs-2008122517/Module

with the space between D-Link and WUA-1340. It gave an error:
r[root@localhost Module]# make
make[1]: Entering directory `/lib/modules/2.6.9-78.0.8.EL/build1'
make[1]: *** No rule to make target `WUA-1340/Driver/Linux/cvs/rt73-cvs-2008122517 /Module'. Stop.
make[1]: Leaving directory `/lib/modules/2.6.9-78.0.8.EL/build1'
rt73.ko failed to build!
make: *** [module] Error 1

After upgrading from RHEL4 WS to RHEL5 Client and updating with 3 RHEL5 Updates (5 kernels in a month), I compiled and installed the rt73 module and the RutilT utility. Everything works well now thanks to Romain's catch of the space in the absolute directory path.

Thanks again,
John
j_75080 :D :D


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 10 posts ] 

All times are UTC


Who is online

Users browsing this forum: No registered users and 0 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group