Would it be too much to ask somebody to compile the ftdi module from the patched 2.6.18.1 kernel, so it can be used with Puppy 2.13? I tried downloading devx_2.13.sfs so that I could try to compile it myself, but its just too big a file for my dialup connection.
Thanks in anticipation
John
Compliling FTDI module for Puppy 2.13
- Eastern Counties
- Posts: 145
- Joined: Tue 31 Jan 2006, 18:09
- Location: UK
+1
I am a Linux noob and have been working with Puppy 2.13 for 2 days. Please be gentle...
I googled for "ftdi_sio.ko" and "2.6.18" and found an RPM for Fedora Core 6. I downloaded 15 MB, extracted the file and tried to insmod it... to no avail.
insmod ftdi_sio.ko
insmod: error inserting 'ftdi_sio.ko': -1 Invalid module format
dmesg reported:
ftdi_sio: disagrees about version of symbol struct_module
So, like Eastern Counties, I'm looking for a build of ftdi_sio.ko compatible with Puppy 2.13. Thanks!
I am a Linux noob and have been working with Puppy 2.13 for 2 days. Please be gentle...
I googled for "ftdi_sio.ko" and "2.6.18" and found an RPM for Fedora Core 6. I downloaded 15 MB, extracted the file and tried to insmod it... to no avail.
insmod ftdi_sio.ko
insmod: error inserting 'ftdi_sio.ko': -1 Invalid module format
dmesg reported:
ftdi_sio: disagrees about version of symbol struct_module
So, like Eastern Counties, I'm looking for a build of ftdi_sio.ko compatible with Puppy 2.13. Thanks!
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
- Eastern Counties
- Posts: 145
- Joined: Tue 31 Jan 2006, 18:09
- Location: UK
Thanks for the reply, tempestuous.
A little more digging indicates that the ftdi_sio module is created/installed only when activated, similar to how usbserial.ko behaves.
At bootup using the Live CD (Puppy 2.13) or on my HD installed version (also Puppy 2.13), neither of those modules appears to be present.
But... after I issue commands:
modprobe usbserial
modprobe ftdi_sio
... the .ko files appear in /lib/modules/2.6.18.1/kernel/drivers/usb/serial
This is progress! Maybe this is enough for you, Eastern Counties?
Unfortunately, my software isn't able to connect to the device that dmesg says has been attached to ttyUSB0. I will do some more digging here.
Edit: My software expects the character device to be /dev/ttyUSB0, not /dev/usb/ttyUSB0 as seems to be created so I created a logical link and now my software is working!!!
(Later, I suspect some work will have to be done in modules.conf to get things to auto-detect and auto-launch, though I would be content to add the required modprobe calls to my init scripts, if need be.)
A little more digging indicates that the ftdi_sio module is created/installed only when activated, similar to how usbserial.ko behaves.
At bootup using the Live CD (Puppy 2.13) or on my HD installed version (also Puppy 2.13), neither of those modules appears to be present.
But... after I issue commands:
modprobe usbserial
modprobe ftdi_sio
... the .ko files appear in /lib/modules/2.6.18.1/kernel/drivers/usb/serial
This is progress! Maybe this is enough for you, Eastern Counties?
Unfortunately, my software isn't able to connect to the device that dmesg says has been attached to ttyUSB0. I will do some more digging here.
Edit: My software expects the character device to be /dev/ttyUSB0, not /dev/usb/ttyUSB0 as seems to be created so I created a logical link and now my software is working!!!
(Later, I suspect some work will have to be done in modules.conf to get things to auto-detect and auto-launch, though I would be content to add the required modprobe calls to my init scripts, if need be.)
- Eastern Counties
- Posts: 145
- Joined: Tue 31 Jan 2006, 18:09
- Location: UK
Thanks for that, The Squire. Now my modem is working again (via its FTDI USB-serial adapter).
Strangely, even though both the usbserial and ftdi_sio modules appear in
/lib/modules/2.6.18.1/kernel/drivers/usb/serial, the ftdi one was still not picked up. I copied it to /usr/lib/modules and edited my rc.local file to load it on startup and now all is fine.
Thanks again
John
Strangely, even though both the usbserial and ftdi_sio modules appear in
/lib/modules/2.6.18.1/kernel/drivers/usb/serial, the ftdi one was still not picked up. I copied it to /usr/lib/modules and edited my rc.local file to load it on startup and now all is fine.
Thanks again
John
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Since version 2.12 Puppy holds the full set of kernel modules in a separate "zdrv" file.
Your modules are "fetched" on-demand. It's worth reading the release notes -
http://www.puppylinux.com/download/release-2.12.htm
Your modules are "fetched" on-demand. It's worth reading the release notes -
http://www.puppylinux.com/download/release-2.12.htm
- Eastern Counties
- Posts: 145
- Joined: Tue 31 Jan 2006, 18:09
- Location: UK