I have just updated nload from 0.6.0-2 to 0.7.1-1 and now get the following error on trying to run it:
Illegal instruction
Anybody else seeing this?
Using 1.9.2.7-8 on WL500gx, I have reinstalled all packages from the optware feed and get the "Segementation error" when running nload.
In the live options screen, accessed using the 'O' key, I get the error when I exit the option screen, using 'O', or when using the cursor down key.
Any ideas?
I have just updated nload from 0.6.0-2 to 0.7.1-1 and now get the following error on trying to run it:
Illegal instruction
Anybody else seeing this?
try to force update libuclibc++ and ncurses and then report here if it does not work.
Hi Oleo
No luck I am afraid.
Code:[admin@Server root]$ ipkg install -force_reinstall libuclibc++ ncurses Reinstalling libuclibc++ (0.2.2-6) on /opt/... Downloading http://ipkg.nslu2-linux.org/feeds/optware/oleg/cross/stable/libuclibc++_0.2.2-6_mipsel.ipk Reinstalling ncurses (5.6-3) on /opt/... Downloading http://ipkg.nslu2-linux.org/feeds/optware/oleg/cross/stable/ncurses_5.6-3_mipsel.ipk Configuring libuclibc++ Configuring ncurses update-alternatives: Linking //opt/bin/clear to /opt/bin/ncurses-clear Successfully terminated. [admin@Server root]$ nload -h Illegal instruction [admin@Server root]$
I confirm. Before upgrade it worked fine, after upgrade to 0.7.1-1 it returns "Illegal instruction"
Sadly to say that nload 0.7.1 is another c++app that does not build with uclibc++.
http://trac.nslu2-linux.org/optware/changeset/7920 will rebuild using libstdc++
after upgrade to 0.7.1-2 there is no "Illegal instruction" anymore. nload starts ok. However, it is still unusable. The numbers are represented as some junk chars. There is a screenshot here: http://www.wl500g.info/showpost.php?p=86817&postcount=9
Same here with the junk characters.
Whether this is just new to features of 0.7.1 but the 'o' and left/right cursor keys no longer bring up a screen allowing changes to the scaling of the displayed data.
Ed: Just noticed that F2 now brings up the options screen I was referring to, and the original "Segmentation fault" problem I was having is now gone.
Last edited by sebw; 07-03-2008 at 15:21.
Strangely it worked for me on kamikaze, so I cannot blame uclibc but rather toolchain.
http://trac.nslu2-linux.org/optware/changeset/7929 will solve this issue for all uclibc based platforms.