Problem installing driver for FTDI converter cable on my linux system
I'm new to linux, so sorry if this turns out to be a no-brainer.
I'm trying to install an FTDI usb to serial converter driver on a linux machine (kernel: Linux 184.108.40.206, on a Phytec LPC3250 board) and it's not working for me. The driver itself comes with some c code and a makefile (got the driver from here: http://www.ftdichip.com/Drivers/VCP.htm, the 1.5.0 version for linux). When I try running make, I get the following error:
1 [root@nxp /ftdi_sio]# make
2 /ftdi_sio/Rules.make:24: /lib/modules/220.127.116.11/build/.config: No such file or directory
3 make: Warning: File `/ftdi_sio/Rules.make' has modification time 1.1e+09 s in the future
4 make: *** No rule to make target `/lib/modules/18.104.22.168/build/.config'. Stop.
where 1...4 are line numbers that I added for clarity.
When I try to access the /lib/modules/22.214.171.124/build/ directory, I find that it is a symbolic link to the /usr/src/linux directory, and when I cd to /usr, there is no src directory! I think this might be a problem with the way I configured my kernel or something, but I'm not sure.
I think I need to have a .config file or something, but I have no idea how to get it. I used the linux target image builder (ltib) to build my kernel, and I tried messing around with the options there to find something about the .config file, but no luck. I also tried looking around online and the ftdi website for any info about this type of problem, but no one else seems to have trouble installing the driver, just me...
Can anyone help? If you need more info, I'd be happy to provide it.
Thanks in advance.
Some sourcecode packages are rather simple to install (just "./configure && make && make install"). However, if all you have is a "Makefile" and a few *.c files, you'll need to review the Makefile.
I pulled down the 1.5.0 version for x86_64 and saw that it's pretty dry....
Easiest thing I can suggest is to look for /proc/config.gz (a copy of the .config stored in the running kernel). Just ungzip that puppy into your kernel source directory.
However, a word of warning....BACKUP YOUR KERNEL SOURCE FIRST!!!! I've seen poorly written drivers freak-out a system before, then you forget they're in your source-code directory when you go to recompile a kernel....
...What Linux Distribution are you running?
Thanks for your help. I was able to gunzip the config file and use it, and it solved my immediate problem. Hopefully I won't have too much more trouble with it.
FYI though, I'm using a general linux kernel (if that makes sense). It's just plain linux, on an embedded system.
|All times are GMT -5. The time now is 07:19 AM.|