The build of slugosbe-image (5.5_alpha BTW) completed with no errors. I haven't
actually put it into a slug yet but thought it was worth a note.
Thanks again for the assistance.

--- In nslu2-linux@yahoogroups.com, Mike Westerhof <mwester@...> wrote:
>
> Harsh wrote:
> >
> >
> > Thanks a bunch for the direction! Probably saved me a lot of pain in
> > the process.
> >
> > I'll try and give it a go with the latest snapshot and tweak the OE
> > build to see how it goes.
> >
> > -H
> >
> I just checked my autobuilder -- apparently it too is suffering from the
> python "msg" problem.  Looks like the OE folks now require at least
> version 1.10 of bitbake.  So, edit the Makefile, find the two lines that
> reference bitbake 1.8 versions, and change them to 1.10 and 1.10.1
> respectively.   I'm not sure that SlugOS will build with this new
> bitbake version, though.
>
> I'm not sure if this was an intentional change on the part of the OE
> team; this happened in the past week and I don't recall seeing an
> announcement from them.  If it was intentional, we'll have to update the
> master Makefile, I guess.
>
> -Mike
>
>
> > --- On *Sun, 31/10/10, Mike Westerhof /<mwester@...>/* wrote:
> >
> >
> >     From: Mike Westerhof <mwester@...>
> >     Subject: Re: [nslu2-linux] Re: Cross-compile toolchain
> >     To: nslu2-linux@yahoogroups.com
> >     Date: Sunday, 31 October, 2010, 12:00 AM
> >
> >
> >
> >     Steve wrote:
> >     > Well... It appears that it is broken with a python global name
> >     'msg' not defined. I 'updated' a previous build directory on
> >     Ubuntu 10.04 and managed to break it too. When it works, it is
> >     amazing but I suspect it lacks maintenance these days.
> >     >
> >
> >     You'll need a build host who age matches the 5.3 SlugOS release --
> >     basically, the host tools (compilers, libraries, python, etc) have
> >     all
> >     changed in ways incompatible with the Openembedded build tools
> >     from that
> >     era.
> >
> >     If you're using ubuntu, I'd go back to one of the 09.xx releases, or
> >     even the 08.xx releases (with no updates applied) and try that. For
> >     Fedora users, I would suggest something in the range of Fedora 9 to
> >     perhaps Fedora 11 might work.
> >
> >     You *could* try to fix up the recipes and python libraries that
> >     make up
> >     the OE build tool -- cherry pick patches from the latest Openembedded
> >     GIT repo -- but the OE folks have dropped support for a lot of the
> >     cross-compilation tools we used with SlugOS 5.3, so that approach is
> >     unlikely to work very well. I can tell you that selecting a snapshot
> >     from last November of the OE build system will get you a SlugOS
> >     5.4-alpha that worked very nicely indeed. In fact, if my job
> >     situation
> >     hadn't changed so dramatically last December, I would have released
> >     SlugOS 5.4-beta at the end of December... c'est la vie.
> >
> >     -Mike (mwester)
> >
> >     > Steve
> >     >
> >     > --- In nslu2-linux@yahoogroups.com
> >     </mc/compose?to=nslu2-linux%40yahoogroups.com>, Harsh
> >     <harshbaste@> wrote:
> >     >
> >     >> Hello,
> >     >>
> >     >> I'm looking for instructions on how to setup a cross-compile
> >     toolchain for the NSLU2 for SlugOS 5.3 BE. I'm running Ubuntu
> >     10.10 on my PC and found native compiling too painful to use so
> >     decided with this instead, but cant find much recent info on it.
> >     Any help would be appreciated.
> >     >>
> >     >> Thanks,
> >     >> H
> >     >>
> >     >>
> >
>

--- In nslu2-linux@yahoogroups.com, Harsh <harshbaste@...> wrote:
>
> Thanks a bunch for the direction! Probably saved me a lot of pain in the
process.
>
> I'll try and give it a go with the latest snapshot and tweak the OE build to
see how it goes.
>

It is not clear to me whether you need the cross-compiler in order to compile
slugos itself (or maybe additional kernel modules), or whether you just want to
compile applications to run on Slugos 5.3. If it's the former, then Mike is the
expert and you do what he says. But if it is the latter, then you really do not
need to get involved with all the OE stuff at all.

Even the machinery for cross compiling Optware is more complex than it needs to
be IMHO.

I have constructed a cross-compiler which will compile for both slugos 4.8 and
slugos 5.3, including both big and little endian versions of each, depending on
just how you call it, and making use of the library and include files already
available with the respective distributions, without making any versions of its
own. It is still a bit hairy (I had to cheat the gcc Makefiles in a few places,
which is why it is not ready for publication yet).

I think I've got everything installed, but cups won't start. The error I get is:

/opt/sbin/cupsd: relocation error: /opt/lib/libldap-2.3.so.0: symbol sys_nerr,
version GLIBC_2.4 not defined in file libc.so.6 with link time reference

I don't really know what that means.  I search around the net seems like maybe
GLIBC isn't installed.  If that's the case, where to i get it?  I can't seem to
find anything in the ipkg or opkg feeds.

Any pointers?

Thanks,
kevin

hello,
thank you for your GoldMine like forum  :-)
I'm looking for a special build of ffmpeg with h264 + aac support available.
My platform is Qnap TS-219P
from uname -a I got "armv5tel"
from /proc/cpuinfo I got :
Processor       : Feroceon 88FR131 rev 1 (v5l)
BogoMIPS        : 1199.30
Features        : swp half thumb fastmult edsp
CPU implementer : 0x56
CPU architecture: 5TE
CPU variant     : 0x2
CPU part        : 0x131
CPU revision    : 1

Hardware        : QNAP TS-119/TS-219/TS-419
Revision        : 0000
Serial          : 0000000000000000

Thank you sooo much In advance!

Cheers!

nico

In message <ibp0km+4gm3@eGroups.com>, nicod_lyon <nicod.lyon@...>
writes
>hello,
>thank you for your GoldMine like forum  :-)
>I'm looking for a special build of ffmpeg with h264 + aac support available.

The current Optware version of ffmpeg is quite dated,  an early SVN
snapshot dated 2008.  Reading through the release notes indicates that
support for h264 and aac is available from versions 0.50 onwards dated
from march 2009 onwards.

I think all that is needed is for the package build to be updated to a
later version.
--
Robert Hammond
PGP:0x154144DA
592B 0199 2D7F FC05 C4B1 0404 2258 4471 1541 44DA

Hello,

I am running SlogOS 4.8.  Rarely and irregurarly my slug has the following
behavior:

1. stops accepting ssh connections
2. does not allow NFS connections
3. does not allow connections to the imap server
4. stops logging

but

5. it replies to ping commands
6. port scan shows imap port open, ssh and nfs ports closed
7. the 2 attached HD leds show normal activity (i.e. similar to when the system
works normally)

Pushing the power button does not power off the slug but Ready/Status and
Ethernet leds change their behavior to continuous activity.  To power off I have
to pull the plug.  After restoring power and pressing the power button the slug
reboot normally.

This becomes a big problem when it happens when I am away from the slug.  Then I
am out of service (sometimes it can be the best part of a week) until I reboot
it, as mentioned above.

It seems to me that this is not a complete crash.  I would like to investigate
the situation further in order to find a remedy or a way to recover remotely.

I have thought of writing a cron script that would check if ssh is running or
not and restart it if needed.  But this requires cron to be running and I am not
sure this is the case.

I would appreciate any short of help on how to resolve this situation.

Thank you.
Antonis

> I am running SlogOS 4.8.  Rarely and irregurarly my slug has the following
behavior:
>
> 1. stops accepting ssh connections
> 2. does not allow NFS connections
> 3. does not allow connections to the imap server
> 4. stops logging
>
I would first check the power supply voltage under load.
There is a long tradition of PSU slowly failing (due to capacitor decay), I had
to replace mine with a pro unit after struggling for weeks to understand why I
kept having issues with a hub connected hard drive till I realized that the
provided voltage was not enough to power everything.
The advantage of this pro PSU was that I could use it to feed the NLSU (and its
current replacement the sheevaplug), the hub (and the attached 2" hd) and also a
green switch (Linksys if I remember correctly) which works on just 5v.
Also it is far more efficient than 3 cheap PSU and requires 1 power plug.

Just my 0.000000000005 cents! ;-)

Max

On Tuesday, November 23, 2010 10:04:03 am you wrote:
> Hi all,
>
> Just wanted to know what experiences people have had with USB sound
> dongles on the NSLU2 / SlugOS. The site lists really old and eol'd
> hardware so wanted recommendations on newer hardware if possible.
> Does anyone have any experience with a Creative SB1140 USB card e.g.
> How good does it sound / is there any distortion?

My only experience is with very old USB sound adapters that sold for
under $5.

They did work, the main problem I had was I had to find an mp3 player
that did not use floating point. I finally did find an integer-based
player, but it was so long ago I forget which one it was.

I think these units used one of the C-Media chips, but again it was a
long time ago.

Hi Martin,

Did you solve the problem?
I got the same error...

Regards,
Torsten

--- In nslu2-linux@yahoogroups.com, "emtisoft" <martintittel@...> wrote:
>
> --- In nslu2-linux@yahoogroups.com, "dannyboy1121x" <dan_cc_keating@> wrote:
> >
> > What are the permissions on the directories in question? :)
> >
>
> I am starting minidlna from a root shell, the directories belong to a user
"name" and group "everyone".
>
> The permissions were 770, I changed them to 777.
> Same errors as before...
>
> Regards,
> Martin
>

Hi All,

I noticed that libxml2 was updated last week and since then I have been getting
this error:
==============================
$ ./rt2mei
03/12/10 19:45:42: Job started
/opt/bin/php: /opt/lib/libxml2.so.2: no version information available (required
by /opt/bin/php)
/opt/bin/php: /opt/lib/libxml2.so.2: no version information available (required
by /opt/bin/php)
/opt/bin/php: /opt/lib/libxml2.so.2: no version information available (required
by /opt/bin/php)
/opt/bin/php: /opt/lib/libxml2.so.2: no version information available (required
by /opt/bin/php)
/opt/bin/php: /opt/lib/libxml2.so.2: no version information available (required
by /opt/bin/php)
/opt/bin/php: /opt/lib/libxml2.so.2: no version information available (required
by /opt/bin/php)
/opt/bin/php: /opt/lib/libxml2.so.2: no version information available (required
by /opt/bin/php)
/opt/bin/php: /opt/lib/libxml2.so.2: no version information available (required
by /opt/bin/php)
rt2mei.php 1.1a started: 03/12/2010 19:45:44

Config data will be read from file "/public/rt2mei/rt2mei.cfg"
Favourites will be written to file "/public/rt2mei/rt2mei.mcl"
MEI data will be written to file "/public/rt2mei/MyStuff.mei"
==============================

This is what I have installed:

# ipkg info php
Package: php
Version: 5.2.14-1
Depends: bzip2, openssl, zlib, libxml2, libxslt, gdbm, libdb, pcre,
cyrus-sasl-libs, openldap-libs
Status: install user installed
Section: net
Architecture: armeb
Maintainer: Josh Parsons <jbparsons@...>
MD5Sum: 23a5426c2e632af6bac05b7e869821f8
Size: 1766398
Filename: php_5.2.14-1_armeb.ipk
Source: http://static.php.net/www.php.net/distributions//php-5.2.14.tar.bz2
Description: The php scripting language
Installed-Size: 4279106

# ipkg info libxml2
Package: libxml2
Version: 2.7.8-1
Depends: zlib (>=1.2.5)
Status: install user installed
Section: libs
Architecture: armeb
Maintainer: NSLU2 Linux <nslu2-linux@yahoogroups.com>
MD5Sum: 079fb14d11acc937d388d14e3a10795c
Size: 904903
Filename: libxml2_2.7.8-1_armeb.ipk
Source: ftp://xmlsoft.org/libxml2/libxml2-2.7.8.tar.gz
Description: Libxml2 is the XML C parser and toolkit developed for the Gnome
project.

How do I fix this?
--
Regards,
Mick

I have been sucessfully used my slug in past times with Debian install. Now,
after unknown event, slug cannot wake up. On original power supply Power LED
blinks. With replaced power suply Power LED stays on and Ready/Status LED
blinks. RS-232 terminal shows only repeating "+" mark. It looks like reset
loops. I try to bypass power on electronics and give power directly to USB
supply lines with same results - slug cannot wake up. Bricked?

Finally I was replaced power supplier to new one - 5V, 2A. All bad syndroms was
gone. Only "Power" LED stays on switch undependently - I cannot turn off this
LED without remove power supply plug. I dont remember is this  normal or not.
For me it depends on specific GPIO8 pin state...

So after the three years of work original Linksys power supplier starts behave
bizarre. Do not use weak replacements!

--- In nslu2-linux@yahoogroups.com, "nsluv2" <miednica@...> wrote:
>
> I have been sucessfully used my slug in past times with Debian install. Now,
after unknown event, slug cannot wake up. On original power supply Power LED
blinks. With replaced power suply Power LED stays on and Ready/Status LED
blinks. RS-232 terminal shows only repeating "+" mark. It looks like reset
loops. I try to bypass power on electronics and give power directly to USB
supply lines with same results - slug cannot wake up. Bricked?
>

Is there any chance of getting the udp driver compiled into the lirc package?  I
am running the tomato firmware on my wireless router (tomato uses the wrt
optware repository) and I am hoping to be configure it to receive ir signals
over ethernet.

Hello,

I am trying to fine-tune bash at Synology DS110j.
I created unprivileged user 'pavel' and set /opt/bin/bash as shell for
him in /etc/passwd
I copied /etc/profile to his $HOME/.profile and customized it -
changed prompt and HOME.
But it seems that bash do not read $HOME/.profile at all unless there
are no /etc/profile.
In /etc/profile there is HOME=/root definition while in $HOME/.profile
HOME is defined as /var/services/homes/pavel.
When I login either as 'root' or 'pavel' and do echo $HOME, I get /root
The only way to get bash to read $HOME/.profile is to delete
/etc/profile at all.
Is there a way to fix such a behaviour?

--
Pavel Parkhomenko

I had a standard nslu2 and I flashed the firmware with
slugosbe-5.3-beta-nslu2.bin (8192 KB). Now I can't access the device at all.
can't ping, can't telnet, nothing. Does the new firmware default to dhcp? I
tried the usual 192.168.1.77 and also 192.168.0.1 but got no response, I don't
know what to do next.

eh?

--------------------------------------------------
From: <harperhoe@...>
Sent: Sunday, December 19, 2010 9:38 AM
To: <nslu2-linux@yahoogroups.com>
Subject: [nslu2-linux] Vacation reply

>
>
> You have reached me at an email account that I do not check often. To get
> in touch with me sooner please email me at harperhoe(at)gmail.com.
>
>
> Thanks,
> Harper
>
>
>
>

as an update I'm still having this problem and there are some things I've
tried but not worked.
1) I booted the slug and watched the traffic its trafic in wireshark. Each
time it boots it sends out three dhcp discovery pings (then the device beeps
3 times) but it never picks up an address. Other devices connected to my
router have no problem picking up an address. This slug worked perfectly on
the network before the flash upgrade.
2) I tried the 'all upgrade utility' thing but it caused havoc on three out
of four windows pc's and when it did finally run it couldn't find the slug.
3) I then tried upslug2 from a linux pc but that can't find the slug either.
I'm running out of ideas so any help appreciated.
--
View this message in context:
http://old.nabble.com/newbie%3A-firmware-flash-now-cannot-access-slug-tp30491664\
p30491871.html
Sent from the Nslu2 - Linux mailing list archive at Nabble.com.

 

as an update I'm still having this problem and there are some things I've
tried but not worked.
1) I booted the slug and watched the traffic its trafic in wireshark. Each
time it boots it sends out three dhcp discovery pings (then the device beeps
3 times) but it never picks up an address. Other devices connected to my
router have no problem picking up an address. This slug worked perfectly on
the network before the flash upgrade.
2) I tried the 'all upgrade utility' thing but it caused havoc on three out
of four windows pc's and when it did finally run it couldn't find the slug.
3) I then tried upslug2 from a linux pc but that can't find the slug either.
I'm running out of ideas so any help appreciated.
--
View this message in context: http://old.nabble.com/newbie%3A-firmware-flash-now-cannot-access-slug-tp30491664p30491871.html
Sent from the Nslu2 - Linux mailing list archive at Nabble.com.

On 12/18/2010 4:53 PM, harrycat78 wrote:
> I had a standard nslu2 and I flashed the firmware with
> slugosbe-5.3-beta-nslu2.bin (8192 KB). Now I can't access the device
> at all. can't ping, can't telnet, nothing. Does the new firmware
> default to dhcp? I tried the usual 192.168.1.77 and also 192.168.0.1
> but got no response, I don't know what to do next.

The SlugOS firmware uses whatever settings were left behind by the
previous Linksys, Unslung, or SlugOS firmware.  So if it had a fixed IP
address before, it has the same one now.  If it was set to DHCP, it will
DHCP (although not all routers will issue the same IP address after the
firmware change).

Ping will work, but telnet will not -- you need to us an SSH client for
SlugOS.

-Mike (mwester)

On 12/19/2010 4:38 AM, tonjg wrote:
>
> as an update I'm still having this problem and there are some things I've
> tried but not worked.
> 1) I booted the slug and watched the traffic its trafic in wireshark. Each
> time it boots it sends out three dhcp discovery pings (then the device beeps
> 3 times) but it never picks up an address. Other devices connected to my
> router have no problem picking up an address. This slug worked perfectly on
> the network before the flash upgrade.

Do you see replies to the DCHP requests?  Can you post the traffic that
you do see, so we can try to help?

> 2) I tried the 'all upgrade utility' thing but it caused havoc on three out
> of four windows pc's and when it did finally run it couldn't find the slug.

Not sure what you mean by that utility -- is that the sercomm upgrade
utility -- the one that you are sternly warned NOT to use in the wiki?
Just a reminder to the list -- the use of that utility is highly
dangerous, as it erases the NSLU2 bootloader along with everything else
-- if anything at all goes wrong with the flash, it will leave you with
a totally useless NSLU2, one that can be recovered only by soldering
JTAG wires to the circuit board and reloading firmware using JTAG.

But anyway, the fact that it can't find the NSLU2 indicates that either
you have network problems (bad cable?  bad port on a switch or router?
are your hosts and the NSLU2 on the same side of a routed network
segment?), or that you weren't in upgrade mode to begin with -- the wiki
article on how to enter upgrade mode using the reset button is the one
you need, and pay close attention to the timing and led color notes on
that page; it is very easy to miss the fraction of a second window you
need in order to be successful.

> 3) I then tried upslug2 from a linux pc but that can't find the slug either.
> I'm running out of ideas so any help appreciated.

You might let us know (by posting URLs so that there is no ambiguity)
which wiki articles you are following or trying, and provide detailed
information (cut and paste log files, etc) with the results.  There's a
lot of information on the wiki, some of which is obsolete and
non-helpful, some of which might be for other firmwares and non-helpful
to you, and some of which (sadly, but reality for any open wiki) is just
plain wrong.

-Mike (mwester)

In message <idhfr6+coj8@eGroups.com>, brett.presnell
<bdp@...> writes
>Is there any chance of getting the udp driver compiled into the lirc
>package?  I am running the tomato firmware on my wireless router
>(tomato uses the wrt optware repository) and I am hoping to be
>configure it to receive ir signals over ethernet.
>
Done in lirc_0.8.1-3


--
Robert Hammond
PGP:0x154144DA
592B 0199 2D7F FC05 C4B1 0404 2258 4471 1541 44DA

sdm485 wrote:
>
> Can you confirm that you are getting the slug into upgrade mode? If it
> is not in that mode, upslug2 will never see it. You hold the reset
> button in while turning it on and after about 10-15seconds, the top LED
> starts blinking between red and green. You must release the reset button
> immediately upon seeing the first LED change.

yes I've read and re-read the upgrade article and tried the upgrade many
times but my slug will not do what its supposed to. During the boot,
regardless of whether the reset button is pressed in or not I never get the
top led blinking red and green. Never. The only lights I get are either
blinking orange or blinking green. Pressing the reset button in makes no
difference to the startup sequence of the slug. Here is a little video of
the boot sequence. (5Mb)
http://www.zen187664.zen.co.uk/linksys/slugbootup.avi
--
View this message in context:
http://old.nabble.com/newbie%3A-firmware-flash-now-cannot-access-slug-tp30491664\
p30494174.html
Sent from the Nslu2 - Linux mailing list archive at Nabble.com.