DSM 3.1 and ftdi_sio

All discussions/development regarding the Marvell mv6281 Chip can be placed here.
Forum rules
Synology Community is the new platform for the enthusiasts' interaction, and it will soon be available to replace the Forum.
pax
I'm New!
I'm New!
Posts: 8
Joined: Fri Oct 23, 2009 4:36 pm

DSM 3.1 and ftdi_sio

Unread post by pax » Sat Mar 05, 2011 9:56 am

I've had the module running for some time in DSM 3.0 on my DS209, but after upgrading to the DSM 3.1 I can no longer insmod the ftdi_sio module.
I can insmod the usbserial.ko without any problems, it was compiled with the same toolchain as the ftdi module...

If I try to insmod I get the error:
insmod: can't insert '/volume1/public/ftdi_sio.ko': unknown symbol in module, or unknown parameter

If I then run the dmesg command I get:

[ 53.890000] usb usb1: configuration #1 chosen from 1 choice
[ 53.890000] hub 1-0:1.0: USB hub found
[ 53.900000] hub 1-0:1.0: 1 port detected
[ 54.000000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 54.220000] usb 1-1: new high speed USB device using orion-ehci and address 2
[ 54.230000] Initializing USB Mass Storage driver...
[ 54.240000] usbcore: registered new interface driver usb-storage
[ 54.240000] USB Mass Storage support registered.
[ 54.350000] usbcore: registered new interface driver usblp
[ 54.380000] usb 1-1: configuration #1 chosen from 1 choice
[ 54.390000] hub 1-1:1.0: USB hub found
[ 54.390000] hub 1-1:1.0: 4 ports detected
[ 54.420000] Got empty serial number. Generate serial number from product.
[ 54.660000] usbcore: registered new interface driver hiddev
[ 54.690000] usb 1-1.3: new full speed USB device using orion-ehci and address 3
[ 54.730000] usbcore: registered new interface driver usbhid
[ 54.740000] usbhid: v2.6:USB HID core driver
[ 54.820000] usb 1-1.3: configuration #1 chosen from 1 choice
[ 76.080000] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 76.320000] svc: failed to register lockdv1 RPC service (errno 97).
[ 76.330000] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[ 76.340000] NFSD: unable to find recovery directory /var/lib/nfs/v4recovery
[ 76.350000] NFSD: starting 90-second grace period
[ 88.860000] usbip_common_mod: module is from the staging directory, the quality is unknown, you have been warned.
[ 88.900000] usbip_common_mod: usbip common driver1.0
[ 88.940000] usbip: module is from the staging directory, the quality is unknown, you have been warned.
[ 89.020000] usbip 1-1.3:1.0: this device 1-1.3 is not in match_busid table. skip!
[ 89.030000] usbcore: registered new interface driver usbip
[ 89.030000] usbip:Stub Driver for USB/IP:1.0
[ 90.270000] usbcore: registered new interface driver snd-usb-audio
[ 111.440000] findhostd uses obsolete (PF_INET,SOCK_PACKET)
[ 114.090000] usbcore: registered new interface driver usbserial
[ 114.090000] usbserial: USB Serial Driver core
[ 114.210000] ftdi_sio: Unknown symbol ___copy_to_user
[ 114.220000] ftdi_sio: Unknown symbol __arch_copy_from_user

What seems to be the problem? Do I need to wait for a new toolchain so I can recomile the ftdi_sio module? I hope not!

Alternative, Is there a way to safely downgrade to DSM 3.0?

User avatar
maxxfi
Compiler
Compiler
Posts: 6794
Joined: Sun Dec 27, 2009 12:13 pm
Location: Espoo, Finland

Re: DSM 3.1 and ftdi_sio

Unread post by maxxfi » Sat Mar 05, 2011 10:38 am

pax wrote: [ 114.090000] usbserial: USB Serial Driver core
[ 114.210000] ftdi_sio: Unknown symbol ___copy_to_user
[ 114.220000] ftdi_sio: Unknown symbol __arch_copy_from_user

What seems to be the problem? Do I need to wait for a new toolchain so I can recomile the ftdi_sio module? I hope not!

Alternative, Is there a way to safely downgrade to DSM 3.0?
I'm not 100% positive, but it looks like the kernel mus have changed and it doesn't offer now certain library
that old version was providing, so the module would need to be recompiled.
No longer using Synology NAS, moved to more open source solutions.
DS-106j > DS-210j > DS-411

pax
I'm New!
I'm New!
Posts: 8
Joined: Fri Oct 23, 2009 4:36 pm

Re: DSM 3.1 and ftdi_sio

Unread post by pax » Sat Mar 05, 2011 10:43 am

If I call uname -r I still get kernel version 2.6.32.12

But I gues something has changed....

Does anybody know when a new toolchain is released?
Or where the missing functions are defined?

I only did the update because it shuld be the same kernel, so this is ....

Thanks for any advice / help

pax
I'm New!
I'm New!
Posts: 8
Joined: Fri Oct 23, 2009 4:36 pm

Re: DSM 3.1 and ftdi_sio

Unread post by pax » Sun Mar 06, 2011 5:14 pm

As far as I can see the missing functions should be in the usbcore module...

Can anybody confirm that the usbcore module has changed? And is there a way to insert the old usbcore module?
What can go wrong if I exchange the new usbcore module with the old one?

User avatar
maxxfi
Compiler
Compiler
Posts: 6794
Joined: Sun Dec 27, 2009 12:13 pm
Location: Espoo, Finland

Re: DSM 3.1 and ftdi_sio

Unread post by maxxfi » Sun Mar 06, 2011 6:08 pm

Well, yes it seems the two functions disappeared from usbcore.ko,
and probably replaced with other two.
On my Linux desktop I uncompressed both the images for 3.0 and 3.1, and start
some comparisons.

In DSM-1337 (3.0):

Code: Select all

$ strings -a old/hda1/lib/modules/usbcore.ko | grep copy
___copy_to_user
__arch_copy_from_user
In DSM-1594 (3.1):

Code: Select all

$ strings -a new/hda1/lib/modules/usbcore.ko | grep copy
__copy_to_user
__copy_from_user
No longer using Synology NAS, moved to more open source solutions.
DS-106j > DS-210j > DS-411

foakss
I'm New!
I'm New!
Posts: 4
Joined: Sun Mar 08, 2009 12:41 pm

Re: DSM 3.1 and ftdi_sio

Unread post by foakss » Sun Mar 06, 2011 6:53 pm

copy_to_user and copy_from_user are elementary linux device driver functions.
I would assume usbcore is calling these functions and not supplying them.

pax
I'm New!
I'm New!
Posts: 8
Joined: Fri Oct 23, 2009 4:36 pm

Re: DSM 3.1 and ftdi_sio

Unread post by pax » Sun Mar 06, 2011 7:04 pm

I'm now trying to rmmod the usbcore, I have unmounted any usbfs that where mounted but I still cant rmmod...

rmmod: can't unload 'usbcore': Resource temporarily unavailable

What could be blocking the rmmod?

It would be nice to just try and insmod the old usbcore too see if it resolves the problem...

BTW. I still belive that thouse functions are in the usbcore module, but they might only be wrappers ofcouse...

The only dependencies I get from the ftdi_sio module is: usbserial and usbcore

pax
I'm New!
I'm New!
Posts: 8
Joined: Fri Oct 23, 2009 4:36 pm

Re: DSM 3.1 and ftdi_sio

Unread post by pax » Mon Mar 07, 2011 5:46 pm

Okey I succeded to remove the new usbcore module, but I'm still not able to insmod the old version, so I gues that foakss is right!

@foakss: do you know where thouse functions is defined?

s there anybody that knows when a new toolchain is released?

foakss
I'm New!
I'm New!
Posts: 4
Joined: Sun Mar 08, 2009 12:41 pm

Re: DSM 3.1 and ftdi_sio

Unread post by foakss » Mon Mar 07, 2011 11:38 pm

I used the 3.0 toolchain on a linux PC.
I used the command "make ARCH=arm menuconfig" and selected system type. Then selected ARM system type and changed it into Marvel Kirkwood.
After that I selected "Marvell Kirkwood implementation". Selected "Synology 6281 series NAS"
Recompiled the drivers with "make ARCH=arm modules".

inserted the driver. It seems to be working!
I guess you will need to insert usbserial also. (I use mobprobe to load ftdi_sio).

Haven't experienced any crash or other issue yet.

Do not know why in the synology toolchain directly downloaded from sourceforge a different system type is default selected (Feroceon-KW).

pax
I'm New!
I'm New!
Posts: 8
Joined: Fri Oct 23, 2009 4:36 pm

Re: DSM 3.1 and ftdi_sio

Unread post by pax » Tue Mar 08, 2011 6:24 am

hmmm,

I have inserted the usbserial, and that didn't give me any trouble... I compiled usbserial along with the ftdi_sio so can't see the problem.

I gues I'll try and recompile the whole thing when I get home from work today, I'm very glad hear that you could load the driver, now I just need to figure out what my problem is.

pax
I'm New!
I'm New!
Posts: 8
Joined: Fri Oct 23, 2009 4:36 pm

Re: DSM 3.1 and ftdi_sio

Unread post by pax » Tue Mar 08, 2011 9:52 pm

That was it!!!

I can't say what has changed since the DSM3.0 version, I did not need to set the system type when I compiled the drivers with DSM3.0. But after setting them as you said it works!!!

Many thanks for your help!

User avatar
decalco
I'm New!
I'm New!
Posts: 6
Joined: Thu Oct 01, 2009 9:32 pm
Location: France

Re: DSM 3.1 and ftdi_sio

Unread post by decalco » Wed Mar 09, 2011 10:29 am

Hi pax ! Hi foakss !

I'm in the same situation. I had to downgrade DSM to v3.0 to make my USB device work !
But I want to use this new version 3.1 of DSM.
I already used the 3.0 toolchain on a Virtual Machine on Ubuntu OS.

Could you please explain what you did exactly ?
Which module did you recompile ?

Thanks in advance.

pax
I'm New!
I'm New!
Posts: 8
Joined: Fri Oct 23, 2009 4:36 pm

Re: DSM 3.1 and ftdi_sio

Unread post by pax » Wed Mar 09, 2011 2:41 pm

I only had to recompile the ftdi driver, I just did as foakss wrote and set the ARM system type.

I inserted the new driver with insmod, no problem :-)

( I had some problem with my linux install so I had to reinstall every thing, includeing toolchain and GPL source, don't know if that was what made the difference)

Post Reply

Return to “Marvell mv6281 Development Room”