aMule Forum
English => aMule Help => Topic started by: LucaTNT on June 18, 2008, 01:32:05 PM
-
Hi everyone!
I have aMule installed on my Linksys NSLU2, and it works fine.
The problem is that file sizes are wrong (always either 0 Mb or 1024 Mb) and so are upload/download speed, always locked at Kb/s though the file gets downloaded.
How can I solve this?
Thanks in advance.
-
Hi Luca,
which version of aMule are you using? Do you use the webserver interface?
-
Sorry, I forgot to write it.
I'm using version 2.1.3:
# amuled --version
amuled: OnInit - starting timer
aMuled 2.1.3 using v2.8.0 (Unicoded) (OS: Linux)
I am using the web interface, and of course it is the same version:
# amuleweb --version
amuleweb 2.1.3 using v2.8.0 (Unicoded)
If you need further details just ask me.
Thank you for your help!
-
We recently release a new version, 2.2.1, would it be possible for you to upgrade?
-
I upgraded through ipkg but with no luck, it still displays wrong sizes and speed.
I stopped amuled before upgrading and restarted it after.
# amuled --version
amuled: OnInit - starting timer
aMuled 2.2.1 using v2.8.7 (OS: Linux)
# amuleweb --version
amuleweb 2.2.1 using v2.8.7
-
Could you please use amulecmd to see if the display works correctly?
-
I tried searching some files with amulecmd, and sizes are correct.
I also tried to download one of the files I found, running "download <result number>": in the web interface it shows up in downloading files, but in amulecmd, when I try to run "show dl" it tells me "illegal instruction" and exits:
aMulecmd$ show DL
Illegal instruction
-
On NSLU2 you should be using Debian build. Optware compiler have bug in floating point instructions, which leads to incorrect display in webinterface and other glitches.
-
Thanks for the info, lfroen.
But I saw that for Debian it's avaible only version 2.1.3 and a SVN snapshot of June 8th of 2.2.
I'll try with 2.1.3, extracting manually .deb packages.
-
I did build on debian desktop set to cross-compiling. Unfortunately, I have no idea how to create correct config file for package building.
-
I had no luck extracting the packages, and tried to compile amule directly on the slug, but it can't find zlib, though the package is installed and I can see the files in /opt/lib:
# ls -l /opt/lib/libz.so*
lrwxrwxrwx 1 root root 13 May 16 03:40 /opt/lib/libz.so -> libz.so.1.2.3
lrwxrwxrwx 1 root root 13 May 16 03:40 /opt/lib/libz.so.1 -> libz.so.1.2.3
-rwxrwxrwx 1 root root 67764 Mar 20 00:00 /opt/lib/libz.so.1.2.3
Any suggestion on how to make the configure script understand that it is present? Could it be because I need a "zlib-dev" package or something similar?
-
On Debian like systems you'll need zlib-dev or similar, that's correct.
To extract deb packages, use the ar command with the x (extract) option. You'll get some files, extract data.tar.gz (or similar) to get the package content.
-
I extracted the data.tar.gz deb packages on my Kubuntu machine with Ark, then I copied through SSH the directory structure I obtained in the /opt dir of my slug.
It told me "incorret syntax" when I tried to run the amuled binary.
Could this be related to kernel issues? Unslung is Big Endian, while Debian is Little Endian.
-
When architecture doesn't match, you explicitly told about it. "incorrect syntax" - no idea where does it come from
-
Me too, it's strange, a script might have incorrect syntax, but it was a binary!
I also checked with cat and the shell went crazy as usual...
Any ideas about gzip?
-
What's the output of file `which amule`?
-
# file `which amule`
/opt/usr/bin/amule: ELF 32-bit LSB executable, ARM, version 1, for GNU/Linux 2.6.12, dynamically linked (uses shared libs), stripped
# amule
/opt/usr/bin/amule: /opt/usr/bin/amule: 1: Syntax error: word unexpected (expecting ")")
-
Couldn't it be due to the different kernel?
File says that it is "for GNU/Linux 2.6.12", while my kernel is 2.4.22-xfs
-
Yes, this is very well possible.
-
I found out how to make aMule's configure script find zlib, I had to use the --with-zlib=/opt parameter, now I'm compiling some dependancies, let's see if it works...
-
Yes, this is very well possible.
No, it is not. Kernel version is irrelevant. libc version - is important.
-
According to my understanding, there are various kernel API changes/extensions, which will prevent software using these new extensions on running on an older kernel. I didn't consider that these are abstracted through libc and aMule is unlikely to directly call these functions. Please excuse my misleading information.
-
Generally, as a "rule of thumb", executable created on system with different major kernels (2.4 vs. 2.6) will not be compatible, due to incompatible libc's on accompanying those kernels.