installing a wifi driver gives no such file or directory. please help

zonemikel · 08-26-2006, 09:02 PM

hey i was trying to install this driver for my wifi device and i cant even get it to "make" i think this is something screwy with my path or some file or something here is the output

Code:

[root@localhost rt2570-k2wrlz-1.4.0]# cd Module
[root@localhost Module]# ls
assoc.c     md5.c   rt2570.h        rtmp_tkip.c   rtusb.h       sanity.c
auth.c      md5.h   rt2570sw.h      rtmp_type.h   rtusb_info.c  sha1.h
auth_rsp.c  mlme.c  rt_config.h     rtmp_wep.c    rtusb_init.c  sync.c
connect.c   mlme.h  rtmp_ckipmic.h  rtusb_bulk.c  rtusb_io.c    wpa.c
Makefile    oid.h   rtmp_def.h      rtusb_data.c  rtusb_main.c  wpa.h
[root@localhost Module]# make
make: *** /lib/modules/2.6.17-1.2174_FC5smp/build: No such file or directory.  Stop.
rt2570.ko failed to build!
make: *** [module] Error 1
[root@localhost Module]#

also any time i type a command like lspci or lsusb i hafto go to my sbin dir and run it like ./lsusb... shouldnt i be able to type this anywhere and have it run ? TIA

***UPDATE****
Ive tried to install diferent versions of this driver and it always trys to install to '/usr/src/linux-2.6.17-1.2174_FC5smp' but i have looked in the /usr/src/ dir and there is nothing there .. i know this is my problem but how do i fix it ?

MensaWater · 08-26-2006, 09:29 PM

The answer to your latter question is yes. /sbin should be in your PATH (as root at least).

Type "echo $PATH" to see what is in your PATH.

You can add a directory to a PATH by typing:

PATH=$PATH:/path_to_add

Where path_to_add is the one you want so it would be:

PATH-$PATH:/sbin

You may have hosed your path inadvertently. Simply logging out and logging back in will make it reread your bash rc or profile files and may reset it.

Your original problem isn't PATH directly. It tells you it specifically can't find the directory:
/lib/modules/2.6.17-1.2174_FC5smp/build

Since it gives the full path it knows where it should be but is telling you it isn't there.

Doing ls -l /lib/modules will show you the directories that are there. It may be it is looking for the wrong version in the Makefile and you just need to edit it to put in the one you find. You'd have to look at the notes for the package to determine that.

zonemikel · 08-26-2006, 10:06 PM

Ive been reading through several forums and had just about given up when i came back to this i added my sbin to my path and it is great i can type everything without hafting to type the path .. thanks that was very bothersome.
About the other problem i went in and created a build dir and it didnt help, the instruction for the drivers just say make make install anyway here is the printout of what you said and the error message i get now that i made the dir manually.

Code:

[monsteruser@localhost ~]$ ls -l /lib/modules
total 32
drwxr-xr-x 5 root root 4096 Dec  8  2006 2.6.15-1.2054_FC5smp
drwxr-xr-x 5 root root 4096 Aug 17 14:23 2.6.17-1.2174_FC5
drwxr-xr-x 5 root root 4096 Aug 17 14:23 2.6.17-1.2174_FC5kdump
drwxr-xr-x 6 root root 4096 Aug 26 21:41 2.6.17-1.2174_FC5smp

Code:

[monsteruser@localhost Module]$ make
make[1]: Entering directory `/lib/modules/2.6.17-1.2174_FC5smp/build'
make[1]: *** No rule to make target `modules'.  Stop.
make[1]: Leaving directory `/lib/modules/2.6.17-1.2174_FC5smp/build'
rt2570.ko failed to build!
make: *** [module] Error 1

so i dont know if i hurt it or helped it by making the build dir in that folder ?
It says the same thing with another driver (different though) ... im really stumped ive spent days looking for dependencies for programs and slews of problems installing them but ive never really installed drivers before on linux ... thanks ill check back in about 10 min if nothing ill hafto wait till tommorow

MensaWater · 08-27-2006, 08:56 AM

Haven't done Wi-Fi on Linux or many makes (mostly use commercial RH EL AS). However looking at what you've written and my own systems it appears that for some reason the Make is trying to use a different version of kernel than the one you have available in the directory.

Type "uname -a" to see what version of kernel you're actually running.

For example on a desktop I use I see:

/lib/modules > ls -l
total 24
drwxr-xr-x 3 root root 4096 Jun 20 14:28 2.6.11-1.1369_FC4
drwxr-xr-x 3 root root 4096 Jun 20 14:29 2.6.11-1.1369_FC4smp
drwxr-xr-x 5 root root 4096 Jul 19 18:03 2.6.17-1.2142_FC4smp

/lib/modules > uname -a
Linux hostname.domain.com 2.6.17-1.2142_FC4smp #1 SMP Tue Jul 11 22:57:02 EDT 2006 i686

From the above I see there are two an SMP (Symmetrical Multi-Processing) kernel module directories in /lib/modules. The uname shows the active kernel is the one dated Jul 19.

In your case the message you get is complaining about 2.6.17-1.2174_FC5smp but before you did the mkdir all you had was the 2.6.15-1.2054_FC5smp directory. I suspect your uname is going to show the 2.6.17-1.2174_FC5smp. If so you either copied the kernel you booted from another system to this one (and shouldn't have) or you have somehow inadvertantly deleted the modules directory associated with the kernel you have.

Look in /boot at the vmlinuz and initrd files to see what kernels you have there. During boot up you probably get a choice of which kernel to boot from (if not you need to explore grub.conf). Booting from the lower version may for which you DO have a modules directory may help you complete the make. The downside is if you have installed anything already that needs the higher kernel version you might have issues.

What I'd do is try booting from the lower kernel then verifying nothing appears to have quit working. If not then I'd do the make and see if it completed using the correct modules directory. Alternatively you can try to find the modules for the higher kernel by googling.

zonemikel · 08-27-2006, 08:17 PM

well i didnt copy another kernel and it may have been inadvertant action, lord knows ive done so much crap on this system that i had no idea what i did but later it worked so everything was ok. But i truly think it was evil ass trolls .... just kidding. Its amazing how much i know about windows and dos and php and hordes of other stuff but linux still seems so damn mysterious to me ?
anyway this is what i get ill try to boot the older kernel later .. since this is a webserver hosting several pages i dont shut it down alot but ill get back to you when i do but as i recall there was no other kernel to boot but ill look itz been at least a few months since ive powered this machine down

Code:

[monsteruser@localhost Module]$ make
make[1]: Entering directory `/lib/modules/2.6.17-1.2174_FC5smp/build'
make[1]: *** No rule to make target `modules'.  Stop.
make[1]: Leaving directory `/lib/modules/2.6.17-1.2174_FC5smp/build'
rt2570.ko failed to build!
make: *** [module] Error 1
[monsteruser@localhost Module]$ uname -a
Linux localhost.localdomain 2.6.17-1.2174_FC5smp #1 SMP Tue Aug 8 16:00:39 EDT 2006 i686 i686 i386 GNU/Linux
[monsteruser@localhost Module]$ ls -l /lib/modules
total 32
drwxr-xr-x 5 root root 4096 Dec  8  2006 2.6.15-1.2054_FC5smp
drwxr-xr-x 5 root root 4096 Aug 17 14:23 2.6.17-1.2174_FC5
drwxr-xr-x 5 root root 4096 Aug 17 14:23 2.6.17-1.2174_FC5kdump
drwxr-xr-x 6 root root 4096 Aug 26 21:41 2.6.17-1.2174_FC5smp
[monsteruser@localhost Module]$

MensaWater · 08-28-2006, 10:33 AM

Your uname shows what I expected. You're running the later kernel version. Since you said you created the 2.6.17-1.2174_FC5smp modules directory in an earlier post it likely isn't what you need. On my system the kernel subdirectories under /lib/modules have several items in them which presumably are specific to those kernel versions. Simply creating the directory wouldn't be sufficient. You'd need to have the items (modules) as well.

It may be copying the ones from 2.6.15-1.2054_FC5smp to 2.6.17-1.2174_FC5smp in /lib/modules would get it going but I'm not sure what impact you might see down the road from that. It would be best if you could find the 2.6.17-1.2174_FC5smp modules somewhere. (Possibly on another server in your environment?). Alternatively you might try to actually bump up to an even later kernel version and get its modules.

WARNING: It occurs to me now that not having the modules in 2.6.17-1.2174_FC5smp may mean you wouldn't be able to boot up with that kernel after testing the earlier one. You may wish to disregard my advise to do the reboot.

Having said that, were it me, I'd probably schedule a window and do it anyway on the theory that I'd rather find out in a planned maintenance that I couldn't boot the newer kernel than find it out after a system crash from some hardware failure or other cause.

zonemikel · 08-28-2006, 01:16 PM

well thanks, itz not that important of a server that i cant shut it down (yet). What i did do was got yum to update a bunch of stuff and maybe that will help? I plan on ripping a pci wifi card out of my p4 that i never use and install it in the server i want to have several wifi cards/usb connected at the same time to split up my bandwidth and webpages to different isps.. but that is for another post.. im gonnna go restart the machine and hopefully it will restart with this pci card ill get back to you with a update.

zonemikel · 08-28-2006, 02:07 PM

well i started it and in grub i chose the .15 kernel as opposed to the .17 there were 3 alltogether 2 17 and one 15 anyway i started it up and tried to install the driver but it gave me the same errors just with 15s where before there were 17s ... wouldnt this problem prevent me from installing programs or anything that you hafto "make" ? what would you suggest i do ?
another thing i knoticed when i did the make in the .15 kernel it made what looks like a shortcut called build and source (2) they are unwriteable by normal users ... i remember it did that before when i was using the .17 kernel and i deleted it as root and made a dir there called build and thats how i got where i am .. it was a symbolic link i just delted the dirs i made (and the source symbolic link) and tried again

Code:

[root@localhost Module]# make
make: *** /lib/modules/2.6.17-1.2174_FC5smp/build: No such file or directory.  Stop.
rt2570.ko failed to build!
make: *** [module] Error 1
[root@localhost Module]#

??

zonemikel · 08-28-2006, 08:55 PM

I dont mean to beg ... or bump but i am desprate ive been searching this all day and im getting no where does anyone have any ideas ?

zonemikel · 09-03-2006, 07:52 PM

So am i just like screwed and on my own with this problem ? (as usual with these forums) dosent anyone have any suggestions ? i always end up finding the solution to my own problem and posting it here that really dosent help me ... and most of the stuff i post is simple for those who know

orie0943 · 09-05-2006, 04:27 AM

Hi Zonemikel,

I'm pretty sure I know what is going wrong here. On my machine, the build directory is actully a simlink, to the kernel src files in /usr/src/kernels. Basically, you problem is that whilst you have the kernel installed through yum, you don't have the source files, which are included in the package kernel-smp-devel. Firstly, you should delete that build directory your created, then as root do

yum install kernel-smp-devel

If you now look in the /lib/modules/2.6.17-1.2174_FC5smp/ directory, you should have a new link to the source directory. Then, try make again.

Good Luck

zonemikel · 09-05-2006, 10:31 PM

Ok i will try that and update this message .. thanks alot !

zonemikel · 09-06-2006, 09:31 AM

Well i deleted the dirs and installed with yum just as you suggested. Yum did alot of stuff then it installed the kernel-dvl thing and i went to the dir and i get the same error... i looked in the /lib/modules/fcwhatever dirs and none of them have a build dir .... here is the output

PHP Code:



[root@localhost Module]# make 
make: *** /lib/modules/2.6.17-1.2174_FC5smp/build: No such file or directory.  Stop. 
[root@localhost Module]#

should i have restarted ? ill try a restart later ...

orie0943 · 09-07-2006, 09:48 AM

Hi Zonemikel,

did you have any luck? If it still didn't work, have a look in /usr/src/kernels, and see if anything is in there. If you got the right package from yum, then there should be a directory in there to match the kernel you're using. If there is, then try making a symbolic link from to it, within your /lib/module/kernel*/ directory, and try make again.

Good Luck