MLDonkey on Synology DS207+ (Marvell CPU)

[Lapin]

Hi folks,

I'm planning to buy a DS207+ NAS. After reading many forums, MLDOnkey seems to be the best P2P client. However it seems that there is so far no binary available for the new Synology platform (Marvell 500MHz using an ARM CPU).
I saw a couple of messages from fabtar on the development forum of Synology concerning little-endianess/big-endianess of this new platform.

I was wondering if a new MLDonkey version for this platform was planned to be compiled or is it a more complex problem ??

By the way, thanks for your work

PS: Just a quick introduction of my-self: French guy living closed to Paris, which is planning to setup a NAS in order to avoid to left my PC on all the day (torrents) + planning to buy a PS3 as a BR/DVD player and media center player.

[fabtar]

Hi,
It is not matter of mldonkey version, in order to create a version for a particular platform you need to compile mldonkey on the same architecture.
I have verified that your box is little-endian.
My compiled cores are little endian ARM too.. they have worked well on other MArvell ARM boxes (linkstation).
Currently I am waiting a kernel log from a Synology 207+ with (I hope) more data.
At the moment I don't understand the reason for the "Illegal instruction" ..(core dump) problem.
I hope it could be related to a wrong usage (I have to go deep on Synology OS configuration, user policy and folder structure) and not to a hardware issue.
I think to look at this on sunday moning but I can't assure a solution.

Another chanche is to wait for a Synology power user to compile Mldonkey directly on your box.

P.s:I hope that Spiralvoice and Pango have alternative explanations/suggestions for "Illegal instruction" ..(core dump) problem.
http://www.synology.com/enu/forum/viewtopic.php?f=38&t=5528
_________________
ARM,ARMEL,MIPS,MIPSEL,POWERPC mldonkey cores: http://fabtar.ygrek.org.ua/

[fabtar]

If you are looking for Bittorrent only, perhaps Synology boxes have a pre-installed client. Mldonkey rules for edonkey network or for combined usage.
Cheers

P.s:Welcome into community
_________________
ARM,ARMEL,MIPS,MIPSEL,POWERPC mldonkey cores: http://fabtar.ygrek.org.ua/

[ma2xfr]

Hi Fabtar, did you recieved my last email? Maybe I missed somthing to install the ARM Precompiled version on the Synology?

Historic:

My first was to try the ARM precompiled version on the Synology 107+
but, I got a core dumped.

http://mldonkey.sourceforge.net/phpBB2/viewtopic.php?t=4825

All the Synology x07+ have the same architecture. And if we find a solution for the 107+, you will find a solution for the 207+.

I'm dealing with this issue with Fabtar, but to progress, we need the kernel.log file of the Synology when I experienced the core dumped.
I do not know how to setup the Syslogd of the Synology. If anyone is interested by compilinng a version for Synology x07+ series, he could try to reproduce the same error as me (the core dumped) and provide to Fabtar the kernel.log?

Thank you.
ma2xfr

[Lapin]

Thanks for the welcome.


Also thanks for all explanations. Hopefully you will solve this issue, because the integrated torrent client in Synology box are not as good as your own client
If you make it works, then owner DS107+, DS207+ & DS407 will be very happy !

[fabtar]

@spiralvoice ..pango or other developers

These are the specifications of my emulated arm platform(CPUinfo):

[spiralvoice]

Maybe the CPUID bug again?
http://mldonkey.sourceforge.net/forums/viewtopic.php?p=27524#27524
_________________
Link overview and precompiled cores here: http://mldonkey.sourceforge.net/DownloadLinks

[fabtar]

So CPUID issues could affect ARM cpus too...
In this situation Synology users have to upgrade or compile a fresh new kernel.
I have other 2 things to try first and then I'll suggest to try kernel upgrade.

Thanks for the tip
_________________
ARM,ARMEL,MIPS,MIPSEL,POWERPC mldonkey cores: http://fabtar.ygrek.org.ua/

[ma2xfr]

Hi,

I do not know how to help the community... but I want!
@fabtar - Do you still need the kernel.log?

[fabtar]

Yes, I need the log.
I'm currently reading synology howtos.I'll post a bunch of suggestions this eavining.
I'm also looking into CPUID issue.
Your board is a SoC Orion one which 'll be supported by vanilla kernels from 2.6.25 version.
Perhaps something lacks in the kernel which prevents from trapping the illegal instruction signal.
Cheers

There is also a segmentation fault I'm looking in...
http://mldonkey.org/forum/viewtopic.php?f=2&t=7814&start=0&st=0&sk=t&sd=a
_________________
ARM,ARMEL,MIPS,MIPSEL,POWERPC mldonkey cores: http://fabtar.ygrek.org.ua/

[spiralvoice]

Check cpuinfo output for CPUID support:

[fabtar]

Sinilogy users usully log as root.
I have already asked for logs but they haven't find them, I have supposed mldonkey fails first of opening log file.
Perhaps It is my fault and I haven't thought that they don't know where to look exactly.

@Synology users.

Take a look in to

[spiralvoice]

I do not think that the screen output of MLdonkey before the crash
is written to mlnet.log. It is well possible that the same error happens
when MLDonkey is started at the console prompt. These messages
are of interest for me. I think I know where the bug happens but
I need a confirmation about this before I start to code something.

@synology users: Please start MLDonkey at the console prompt and post the
complete screen output of it, including the error message.

@fabtar: Could you please post the MLDonkey ./configure output related to
utsname functions, like this?

[fabtar]

[spiralvoice]