I just saw that some user named m1complex placed a new mount_optext file which
can take up to an hour to run.  Since it can take up to an hour to run so if you
placed it before the db or hbmgr.sh scripts are run and it can't find the drive,
then you have to wait over an hour before your mypogoplug.com service is loaded.
That call to the script has to be placed after everything else or it bogs down
loading the rest of the rcS if it cannot find the opt drive.  Check to make sure
your opt drive is not corrupted.  If you have any issues with that script,
please contact m1complex.

--- In nslu2-general@yahoogroups.com, "al"  wrote:
>
> I have a pogoplug series 4 that I was trying to install optware on and I think
I may have messed up my boot process. I added the line calling for
/etc/init.d/mount _optext higher than was specified thinking that the line in
the rcS mounting the USB was interfering with the optext mount.
> I don't have ssh access anymore but the device is on the network and pingable.
I can't do anything from the mypogoplug.com setup page as it does not see any
hard drive attached. I would think that I have the device in a loop, looking for
a device with an opt directory every 60 seconds.
>
> Any help?
>
> Thanks,
>
> Shannon
>

Thanks for the prompt reply.
I don't have the lines of code in front of me, but I was having trouble getting
the mount_optext to load and mount my USB flash.
I made a decision based on the fact that my drives were showing up in the
mypogoplug.com that something was interfering with the script.
I know I was supposed to put it at the end, but I made a quick decision without
considering the results.

As it turns out, prior to checking back here, I went back to mypogoplug.com and
did what you had suggested (toggle ssh) and it seem to have worked. My drives
show up again, and everything appears to have righted itself.
When I get home I will go back to stock and try again after some more reading.
My DNS forwarder wasn't on due to a beta alt-f install and my wan ip jumped this
afternoon shortly after my error.
Thanks again.
I may try your script this next go around. I went with the other, as it seemed
tailored to the series 4 pp.

I have been very pleased with my slug, and I hope that I fond this iteration of
software to be as useful as that (almost)outdated workhorse.

Thanks,

Shannon

--- In nslu2-general@yahoogroups.com, "oddballhero"  wrote:
>
>
>
> There is nothing in the mount_optext script that should be interfering with db
dropbear loading or the pogoplug service.  Actually if you do not have your
optware drive plugged in, it doesn't do anything.  There is no loop in the
script unless you modified it, it just goes through the sda/sdb/sdc/sdd one time
and ends.
>
>   What do you mean, the line in rcS mounting the USB?
>
>   Where did you get the idea to put the call for mount_optext ahead of
anything?
>
>   You might have accidentally deleted some lines (the ones calling db or
hbmgr.sh).  If the device is showing up in mypogoplug.com, then hbmgr.sh is
loaded and you can hotplug a regular usb drive after booting and it should show
up.  You can also retry turning on SSH access since that sometimes turns off,
happened to me a while back and caused some mild panic.
>
> Also if your optware drive was loaded while you were installing and you shut
off the the pogoplug with out issuing an "sync" and a "halt" command, basically
just pulling the plug, the optware drive is then corrupted and can't be seen by
the pogoplug after bootup.  It needs to fixed with e2fsck.  On pogoplugs, it
does not matter what type of drive you plug in (ntfs, fat32, ext2 or 3), if you
shut it down without ejecting it from mypogogplug.com or not issuing
"sync"/"halt", then you can corrupt your drives easily, optware or not, and they
won't show up.  You need to mount them on your desktop and check and fix the
drives with whatever utility you need to use.
>
>   If none of this works, then you have to make and install a serial cable. 
See http://archlinuxarm.org/forum/viewtopic.php?f=3&t=2284 .
>
> Please read through everything above before responding.
>
> --- In nslu2-general@yahoogroups.com, "al"  wrote:
> >
> > I have a pogoplug series 4 that I was trying to install optware on and I
think I may have messed up my boot process. I added the line calling for
/etc/init.d/mount _optext higher than was specified thinking that the line in
the rcS mounting the USB was interfering with the optext mount.
> > I don't have ssh access anymore but the device is on the network and
pingable. I can't do anything from the mypogoplug.com setup page as it does not
see any hard drive attached. I would think that I have the device in a loop,
looking for a device with an opt directory every 60 seconds.
> >
> > Any help?
> >
> > Thanks,
> >
> > Shannon
> >
>

Cool, the "NSLU2 slug" is still pretty useful, mine are still going strong.  The
stock Series 4 Pogoplug with Optware is basically an Unslung setup with more
connectivity (USB 3.0 et al).

   It is slower than previous Pogoplugs and de-enhanced in terms of
functionality.  I installed bash to /bin and my own busybox (built with one of
the 2009 toolchains).  I've also built static versions of e2fsck and dosfsck
which checks my drives on startup.

   The problem some people may be having with loading the /opt is the
mypogoplug.com service indexing every new drive added which adds a delay the
first time and it's slower to show the drives.  Confirm this with "fdisk -l". 
My series 4 actually shows this and lists the devices.  If it doesn't show on
yours, then they must have updated the firmware since mine (I bought one of the
first).  I've disabled their service after installing Optware and have not been
updated since.

   If you check yours remotely and it has been plugged in at home, then it
probably passed the required hour for the mount_optext script to time out.  You
can probably add the ampersand(&) at the end of the script invocation and have
it run in the background so that even if you move it to the end of the rcS
script, it does not affect anything in the future (feel free to Google that). 
Still, if you use it, it is probably best in the end.

   My mount_optextX (X = 2 or 3) scripts have a 10 second delay at the beginning
which can be adjusted depending how slow you drives show up.  If re-indexing
takes a while, this delay can be adjusted.  (the original V1 and V2 Pogoplugs
did not really need this, the V3 Oxnas and later, including the V4s do.

   Again, I have to stress the importance of shutting down the system properly. 
Like any other Linux box.  On mine, I have even gone so far as to add a shutdown
script in my inittab to properly shut down the system (see
http://www.nslu2-linux.org/wiki/Optware/PlugComputers ).  You have to
tailor/configure it to your needs (do this all at your own risk, no warranty
implied).  So eject drives from mypogoplug.com and/or "sync", "sync", "halt".

--- In nslu2-general@yahoogroups.com, "al"  wrote:
>
> Thanks for the prompt reply.
> I don't have the lines of code in front of me, but I was having trouble
getting the mount_optext to load and mount my USB flash.
> I made a decision based on the fact that my drives were showing up in the
mypogoplug.com that something was interfering with the script.
> I know I was supposed to put it at the end, but I made a quick decision
without considering the results.
>
> As it turns out, prior to checking back here, I went back to mypogoplug.com
and did what you had suggested (toggle ssh) and it seem to have worked. My
drives show up again, and everything appears to have righted itself.
> When I get home I will go back to stock and try again after some more reading.
> My DNS forwarder wasn't on due to a beta alt-f install and my wan ip jumped
this afternoon shortly after my error.
> Thanks again.
> I may try your script this next go around. I went with the other, as it seemed
tailored to the series 4 pp.
>
> I have been very pleased with my slug, and I hope that I fond this iteration
of software to be as useful as that (almost)outdated workhorse.
>
> Thanks,
>
> Shannon
>
> --- In nslu2-general@yahoogroups.com, "oddballhero"  wrote:
> >
> >
> >
> > There is nothing in the mount_optext script that should be interfering with
db dropbear loading or the pogoplug service.  Actually if you do not have your
optware drive plugged in, it doesn't do anything.  There is no loop in the
script unless you modified it, it just goes through the sda/sdb/sdc/sdd one time
and ends.
> >
> >   What do you mean, the line in rcS mounting the USB?
> >
> >   Where did you get the idea to put the call for mount_optext ahead of
anything?
> >
> >   You might have accidentally deleted some lines (the ones calling db or
hbmgr.sh).  If the device is showing up in mypogoplug.com, then hbmgr.sh is
loaded and you can hotplug a regular usb drive after booting and it should show
up.  You can also retry turning on SSH access since that sometimes turns off,
happened to me a while back and caused some mild panic.
> >
> > Also if your optware drive was loaded while you were installing and you shut
off the the pogoplug with out issuing an "sync" and a "halt" command, basically
just pulling the plug, the optware drive is then corrupted and can't be seen by
the pogoplug after bootup.  It needs to fixed with e2fsck.  On pogoplugs, it
does not matter what type of drive you plug in (ntfs, fat32, ext2 or 3), if you
shut it down without ejecting it from mypogogplug.com or not issuing
"sync"/"halt", then you can corrupt your drives easily, optware or not, and they
won't show up.  You need to mount them on your desktop and check and fix the
drives with whatever utility you need to use.
> >
> >   If none of this works, then you have to make and install a serial cable. 
See http://archlinuxarm.org/forum/viewtopic.php?f=3&t=2284 .
> >
> > Please read through everything above before responding.
> >
> > --- In nslu2-general@yahoogroups.com, "al"  wrote:
> > >
> > > I have a pogoplug series 4 that I was trying to install optware on and I
think I may have messed up my boot process. I added the line calling for
/etc/init.d/mount _optext higher than was specified thinking that the line in
the rcS mounting the USB was interfering with the optext mount.
> > > I don't have ssh access anymore but the device is on the network and
pingable. I can't do anything from the mypogoplug.com setup page as it does not
see any hard drive attached. I would think that I have the device in a loop,
looking for a device with an opt directory every 60 seconds.
> > >
> > > Any help?
> > >
> > > Thanks,
> > >
> > > Shannon
> > >
> >
>

Hi everybody.
I'm using transmission 2.73 (13592) with authentication  enabled and
whitelist disabled. I can access torrent list using a web  browser from
any PC in my network and authentication is correctly  working, but when
I try to get torrent list with transmission-remote  from an SSH session
I get the following error:

Unexpected response: <h1>401: Unauthorized</h1>Unauthorized Usere:
application/x-www-form-urlencoded

I use the following script:

#!/bin/sh
transmission-remote -l --auth username:password

The script is perfectly working if I disable rpc authentication in
settings.json.
If I add the debug option (-b) this is what i get:

posting:
--------
{"arguments":{"fields":["error","errorString","eta","id","isFinished","l\
eftUntilDone","name","peersGettingFromUs","peersSendingToUs","rateDownlo\
ad","rateUpload","sizeWhenDone","status","uploadRatio"]},"method":"torre\
nt-get","tag":4}

--------
> POST /transmission/rpc/ HTTP/1.1
User-Agent: transmission-remote/2.73 (13592)
Host: localhost:9091
Accept: */*
Accept-Encoding: deflate, gzip
Content-Length: 233
Content-Type: application/x-www-form-urlencoded

< HTTP/1.1 401 Unauthorized
< Server: Transmission
< WWW-Authenticate: Basic realm="Transmission"
< Date: Tue, 08 Jan 2013 15:24:45 GMT
< Content-Length: 43
< Content-Type: text/html; charset=ISO-8859-1
<
Unexpected response: <h1>401: Unauthorized</h1>Unauthorized Usere:
application/x-www-form-urlencoded

Note that if I issue the command

transmission-remote -b -l

I have the following output:

posting:
--------
{"arguments":{"fields":["error","errorString","eta","id","isFinished","l\
eftUntilDone","name","peersGettingFromUs","peersSendingToUs","rateDownlo\
ad","rateUpload","sizeWhenDone","status","uploadRatio"]},"method":"torre\
nt-get","tag":4}

--------
> POST /transmission/rpc/ HTTP/1.1
User-Agent: transmission-remote/2.73 (13592)
Host: localhost:9091
Accept: */*
Accept-Encoding: deflate, gzip
Content-Length: 233
Content-Type: application/x-www-form-urlencoded

< HTTP/1.1 401 Unauthorized
< Server: Transmission
< WWW-Authenticate: Basic realm="Transmission"
< Date: Tue, 08 Jan 2013 15:26:37 GMT
< Content-Length: 43
< Content-Type: text/html; charset=ISO-8859-1
<
Unexpected response: <h1>401: Unauthorized</h1>Unauthorized Usere:
application/x-www-form-urlencoded

It seems that sent data does not contain authentication even if this is
given on the command line, as Content-Length is always 233.

Any idea?

Thanks,
Stefano


[Non-text portions of this message have been removed]

The other rcS thread reminded me to ask my question.

I have the native pogoplug rcS call an rcS_opt.sh (which calls the
mount_optext2, etc.

I also have the rcS_opt.sh call the launch files for sickbeard and SABnzbd, as
well as samba but when I reboot the pogoplug, neither sickbeard nor SABnzbd are
running when I go to log in (but SAMBA is!).  If I manually run rcS_opt.sh both
sickbeard and SABnzbd both start successfully.  Any ideas?  I've tried adding
more delays but that hasn't seemed to help at all.

May have to specify full path to the binaries. Afaik, the init scripts
don't set the PATH variable...


On Tue, Jan 8, 2013 at 10:18 AM, adamant628 <adam.suhy@...> wrote:

> **
>
>
> The other rcS thread reminded me to ask my question.
>
> I have the native pogoplug rcS call an rcS_opt.sh (which calls the
> mount_optext2, etc.
>
> I also have the rcS_opt.sh call the launch files for sickbeard and
> SABnzbd, as well as samba but when I reboot the pogoplug, neither sickbeard
> nor SABnzbd are running when I go to log in (but SAMBA is!). If I manually
> run rcS_opt.sh both sickbeard and SABnzbd both start successfully. Any
> ideas? I've tried adding more delays but that hasn't seemed to help at all.
>
>
>


[Non-text portions of this message have been removed]

Try transmission-remote --auth=username:password -l

--- In nslu2-general@yahoogroups.com, "Stefano"  wrote:
>
> Hi everybody.
> I'm using transmission 2.73 (13592) with authentication  enabled and
> whitelist disabled. I can access torrent list using a web  browser from
> any PC in my network and authentication is correctly  working, but when
> I try to get torrent list with transmission-remote  from an SSH session
> I get the following error:
>
> Unexpected response: <h1>401: Unauthorized</h1>Unauthorized Usere:
> application/x-www-form-urlencoded
>
> I use the following script:
>
> #!/bin/sh
> transmission-remote -l --auth username:password
>
> The script is perfectly working if I disable rpc authentication in
> settings.json.
> If I add the debug option (-b) this is what i get:
>
> posting:
> --------
> {"arguments":{"fields":["error","errorString","eta","id","isFinished","l\
> eftUntilDone","name","peersGettingFromUs","peersSendingToUs","rateDownlo\
> ad","rateUpload","sizeWhenDone","status","uploadRatio"]},"method":"torre\
> nt-get","tag":4}
>
> --------
> > POST /transmission/rpc/ HTTP/1.1
> User-Agent: transmission-remote/2.73 (13592)
> Host: localhost:9091
> Accept: */*
> Accept-Encoding: deflate, gzip
> Content-Length: 233
> Content-Type: application/x-www-form-urlencoded
>
> < HTTP/1.1 401 Unauthorized
> < Server: Transmission
> < WWW-Authenticate: Basic realm="Transmission"
> < Date: Tue, 08 Jan 2013 15:24:45 GMT
> < Content-Length: 43
> < Content-Type: text/html; charset=ISO-8859-1
> <
> Unexpected response: <h1>401: Unauthorized</h1>Unauthorized Usere:
> application/x-www-form-urlencoded
>
> Note that if I issue the command
>
> transmission-remote -b -l
>
> I have the following output:
>
> posting:
> --------
> {"arguments":{"fields":["error","errorString","eta","id","isFinished","l\
> eftUntilDone","name","peersGettingFromUs","peersSendingToUs","rateDownlo\
> ad","rateUpload","sizeWhenDone","status","uploadRatio"]},"method":"torre\
> nt-get","tag":4}
>
> --------
> > POST /transmission/rpc/ HTTP/1.1
> User-Agent: transmission-remote/2.73 (13592)
> Host: localhost:9091
> Accept: */*
> Accept-Encoding: deflate, gzip
> Content-Length: 233
> Content-Type: application/x-www-form-urlencoded
>
> < HTTP/1.1 401 Unauthorized
> < Server: Transmission
> < WWW-Authenticate: Basic realm="Transmission"
> < Date: Tue, 08 Jan 2013 15:26:37 GMT
> < Content-Length: 43
> < Content-Type: text/html; charset=ISO-8859-1
> <
> Unexpected response: <h1>401: Unauthorized</h1>Unauthorized Usere:
> application/x-www-form-urlencoded
>
> It seems that sent data does not contain authentication even if this is
> given on the command line, as Content-Length is always 233.
>
> Any idea?
>
> Thanks,
> Stefano
>
>
> [Non-text portions of this message have been removed]
>

AH AH AH!!
I can't believe it!!
It WORKS!! It's just a problem of parameters order...
Thankyou very much!

Cheers
Stefano

--- In nslu2-general@yahoogroups.com, "oddballhero"  wrote:
>
> Try transmission-remote --auth=username:password -l
>
> --- In nslu2-general@yahoogroups.com, "Stefano"  wrote:
> >
> > Hi everybody.
> > I'm using transmission 2.73 (13592) with authentication  enabled and
> > whitelist disabled. I can access torrent list using a web  browser from
> > any PC in my network and authentication is correctly  working, but when
> > I try to get torrent list with transmission-remote  from an SSH session
> > I get the following error:
> >
> > Unexpected response: <h1>401: Unauthorized</h1>Unauthorized Usere:
> > application/x-www-form-urlencoded
> >
> > I use the following script:
> >
> > #!/bin/sh
> > transmission-remote -l --auth username:password
> >
> > The script is perfectly working if I disable rpc authentication in
> > settings.json.
> > If I add the debug option (-b) this is what i get:
> >
> > posting:
> > --------
> > {"arguments":{"fields":["error","errorString","eta","id","isFinished","l\
> > eftUntilDone","name","peersGettingFromUs","peersSendingToUs","rateDownlo\
> > ad","rateUpload","sizeWhenDone","status","uploadRatio"]},"method":"torre\
> > nt-get","tag":4}
> >
> > --------
> > > POST /transmission/rpc/ HTTP/1.1
> > User-Agent: transmission-remote/2.73 (13592)
> > Host: localhost:9091
> > Accept: */*
> > Accept-Encoding: deflate, gzip
> > Content-Length: 233
> > Content-Type: application/x-www-form-urlencoded
> >
> > < HTTP/1.1 401 Unauthorized
> > < Server: Transmission
> > < WWW-Authenticate: Basic realm="Transmission"
> > < Date: Tue, 08 Jan 2013 15:24:45 GMT
> > < Content-Length: 43
> > < Content-Type: text/html; charset=ISO-8859-1
> > <
> > Unexpected response: <h1>401: Unauthorized</h1>Unauthorized Usere:
> > application/x-www-form-urlencoded
> >
> > Note that if I issue the command
> >
> > transmission-remote -b -l
> >
> > I have the following output:
> >
> > posting:
> > --------
> > {"arguments":{"fields":["error","errorString","eta","id","isFinished","l\
> > eftUntilDone","name","peersGettingFromUs","peersSendingToUs","rateDownlo\
> > ad","rateUpload","sizeWhenDone","status","uploadRatio"]},"method":"torre\
> > nt-get","tag":4}
> >
> > --------
> > > POST /transmission/rpc/ HTTP/1.1
> > User-Agent: transmission-remote/2.73 (13592)
> > Host: localhost:9091
> > Accept: */*
> > Accept-Encoding: deflate, gzip
> > Content-Length: 233
> > Content-Type: application/x-www-form-urlencoded
> >
> > < HTTP/1.1 401 Unauthorized
> > < Server: Transmission
> > < WWW-Authenticate: Basic realm="Transmission"
> > < Date: Tue, 08 Jan 2013 15:26:37 GMT
> > < Content-Length: 43
> > < Content-Type: text/html; charset=ISO-8859-1
> > <
> > Unexpected response: <h1>401: Unauthorized</h1>Unauthorized Usere:
> > application/x-www-form-urlencoded
> >
> > It seems that sent data does not contain authentication even if this is
> > given on the command line, as Content-Length is always 233.
> >
> > Any idea?
> >
> > Thanks,
> > Stefano
> >
> >
> > [Non-text portions of this message have been removed]
> >
>

Would that explain why running the same script manually would work?


[Non-text portions of this message have been removed]

It might, since the shell isn't loaded for init scripts. I had similar
issues getting a java-based program to launch other processes.
If you'll notice, in the init scripts anything that isn't a part of the
built-in commands has a full path specified to it.


On Wed, Jan 9, 2013 at 11:10 AM, Adam Suhy <adam.suhy@...> wrote:

> **
>
>
> Would that explain why running the same script manually would work?
>
> [Non-text portions of this message have been removed]
>
>
>


[Non-text portions of this message have been removed]

Hello all,

We would like to cleanup asterisk packages in the feeds.
We will start by removing asterisk 1.2:
  - asterisk
  - asterisk-sounds (obsolete by asterisk14 sound packages)

Is there anyone still using asterisk 1.4 or 1.6?
  - asterisk14
  - asterisk14-chan-capi
  - asterisk16
  - asterisk16-addons
We would like to remove the above versions if not used anymore.

The officially maintained versions are asterisk 1.8 and asterisk 10:
  - asterisk-gui
  - asterisk14-core-sounds*
  - asterisk14-extra-sounds*
  - asterisk14-moh*
  - asterisk18
  - asterisk10


Regards,
Ovidiu Sas

Hi again guys.

Guess I didn't learn after the first time.
After screwing up my rcS file, I was able to correct it and regain access to ssh
and to my series 4 pogoplug again.
I then followed directions off of
http://www.nslu2-linux.org/wiki/Main/PlugComputers and found I was running
busybox 1.16.
According to this instructions, I needed to set up my series 4 like a pro
device.
I again edited my rcS file, putting the "mount /dev/sda1 /opt" and continued
with the config stuff.
On reboot, I didn't get anything except flashing green lights.
I figured, no biggie, was prepared to wire up to the jtag and try to recover. I
used a 485 converter box to talk to it and got the boot sequence showing up, but
no access. Since I had only held the wires on the points, I thought I would get
a better result soldering to it.
After soldering to the points, I booted up and no more flashing green light, and
no real communication showed up in my terminal. The Ethernet tx and rx lights
are barely glowing, and not sure what happened.
Nothing appears shorted out, and the two resistors on the jtag rx and tx are
still intact.
Any ideas?
If I cleared out or corrupted the NAND, can I set up a tftp to flash it back
somehow?
Hoping that someone has some ideas.
Thanks again,
Shannon

Putting in the mount command in the rcS does not break anything.  You could have
just placed the mount script at the end of rcS like the readme file where you
got your "mount_optext" script.  Did you verify the mount /dev/sda1 to /opt by
typing "mount" to verify the usb drive mounted like the directions mentioned?

Did you take out the invocation to the mount_optext that you had, if you didn't,
the flashing green light (only one in front) would have kept flashing since it
wouldn't load the mypogoplug.com service (db and hbmgr.sh) for another hour. 
That's what keeps the green light flashing.

You have a jtag?  Pretty drastic.  That was probably beyond the scope of that
archlinuxarm page.  Just a serial connection - ca-42 - usb to 3.3V ttl.  After
the boot sequence, it should show the prompt.  Did you hit enter/return to see
if you could get the prompt?  Did you take anti-static precautions?  Did you use
a low wattage iron?  The pads are near the power plug.  If you have a jtag and
soldering iron you should be experienced with this.  You can check with the
archlinuxarm guys or http://forum.doozan.com/ and see if anybody there has any
ideas, at least if they have a nand image.

--- In nslu2-general@yahoogroups.com, "al"  wrote:
>
> Hi again guys.
>
> Guess I didn't learn after the first time.
> After screwing up my rcS file, I was able to correct it and regain access to
ssh and to my series 4 pogoplug again.
> I then followed directions off of
http://www.nslu2-linux.org/wiki/Main/PlugComputers and found I was running
busybox 1.16.
> According to this instructions, I needed to set up my series 4 like a pro
device.
> I again edited my rcS file, putting the "mount /dev/sda1 /opt" and continued
with the config stuff.
> On reboot, I didn't get anything except flashing green lights.
> I figured, no biggie, was prepared to wire up to the jtag and try to recover.
I used a 485 converter box to talk to it and got the boot sequence showing up,
but no access. Since I had only held the wires on the points, I thought I would
get a better result soldering to it.
> After soldering to the points, I booted up and no more flashing green light,
and no real communication showed up in my terminal. The Ethernet tx and rx
lights are barely glowing, and not sure what happened.
> Nothing appears shorted out, and the two resistors on the jtag rx and tx are
still intact.
> Any ideas?
> If I cleared out or corrupted the NAND, can I set up a tftp to flash it back
somehow?
> Hoping that someone has some ideas.
> Thanks again,
> Shannon
>

I may have jumped the gun a little when I posted earlier. You're right on
several things.
I didn't have a jtag. It's been a few years since I've had to do some
programming like that. My experience with that is limited to saving old wrt54g
routers and old Xbox eeproms. I used the serial connection on the pogo board.
I also did not comment out the other mount command. I was working from my iPhone
with a ssh app that allowed me to use vi so after a little while of the tedious
process of trying to make sure the script was right, I may have overlooked that.
Hindsight shows now that I put myself right back into the same state I was to
begin with the other day with my series of posts.
I have to admit, I didn't use proper static precautions. I think I was getting
ahead o myself. I believe I just got ahead of myself there.

With the soldering, it wasn't that bad. The pads were more accessible than some
of the Xbox stuff I've worked on, so I wasn't too concerned. I maintained heat
awareness and didn't leave the iron there too long. I believe it's a 25 w iron,
I'm sure 15 might have been a better choice.

All in all, I think I may just set it up on the shelf if I cant find anything
right now. I finished school a few weeks ago, and I kinda just dove into a
project with about a weeks worth of research on it.

In response to your question regarding the prompt, I never got one. After the
boot info showed up, about 8 or 9 lines of CE/ repeated showed on the screen,
but wouldn't let me do anything. I did press buttons on the keyboard, but didn't
see anything show up.

I'll post I I find anything more and thanks for the tips for the two other
sites. I'll check them out.

Thanks again.

Shannon


--- In nslu2-general@yahoogroups.com, "oddballhero"  wrote:
>
> Putting in the mount command in the rcS does not break anything.  You could
have just placed the mount script at the end of rcS like the readme file where
you got your "mount_optext" script.  Did you verify the mount /dev/sda1 to /opt
by typing "mount" to verify the usb drive mounted like the directions mentioned?
>
> Did you take out the invocation to the mount_optext that you had, if you
didn't, the flashing green light (only one in front) would have kept flashing
since it wouldn't load the mypogoplug.com service (db and hbmgr.sh) for another
hour.  That's what keeps the green light flashing.
>
> You have a jtag?  Pretty drastic.  That was probably beyond the scope of that
archlinuxarm page.  Just a serial connection - ca-42 - usb to 3.3V ttl.  After
the boot sequence, it should show the prompt.  Did you hit enter/return to see
if you could get the prompt?  Did you take anti-static precautions?  Did you use
a low wattage iron?  The pads are near the power plug.  If you have a jtag and
soldering iron you should be experienced with this.  You can check with the
archlinuxarm guys or http://forum.doozan.com/ and see if anybody there has any
ideas, at least if they have a nand image.
>
> --- In nslu2-general@yahoogroups.com, "al"  wrote:
> >
> > Hi again guys.
> >
> > Guess I didn't learn after the first time.
> > After screwing up my rcS file, I was able to correct it and regain access to
ssh and to my series 4 pogoplug again.
> > I then followed directions off of
http://www.nslu2-linux.org/wiki/Main/PlugComputers and found I was running
busybox 1.16.
> > According to this instructions, I needed to set up my series 4 like a pro
device.
> > I again edited my rcS file, putting the "mount /dev/sda1 /opt" and continued
with the config stuff.
> > On reboot, I didn't get anything except flashing green lights.
> > I figured, no biggie, was prepared to wire up to the jtag and try to
recover. I used a 485 converter box to talk to it and got the boot sequence
showing up, but no access. Since I had only held the wires on the points, I
thought I would get a better result soldering to it.
> > After soldering to the points, I booted up and no more flashing green light,
and no real communication showed up in my terminal. The Ethernet tx and rx
lights are barely glowing, and not sure what happened.
> > Nothing appears shorted out, and the two resistors on the jtag rx and tx are
still intact.
> > Any ideas?
> > If I cleared out or corrupted the NAND, can I set up a tftp to flash it back
somehow?
> > Hoping that someone has some ideas.
> > Thanks again,
> > Shannon
> >
>

hi all, sorry if this is a noob question but i've been trying to flash openwrt
to a NSLU2 for the last couple of days and it's starting to feel like i'm
bashing my head on a wall ;)

i think i managed to flash the openwrt firmware correctly (i'm using 10.3.1)
with upslug2 but i can't connect to the device:

i tried both connecting the NSLU2 to a switch and directly to my computer.
when i try to telnet (or ping) the device on 192.168.1.1 or 192.168.1.77 it
doesn't respond and when i connect it to the switch it doesn't show up on the
DHCP table.
when i boot the NSLU2 it flashes all the leds and then shows only the ethernet
led.

any help would be REALLY appreciated!
Thanks in advance!
Marcello

Hi all, back with a new challenge (for me at least). Have been running a number
of programs without any real problems, Transmission, Samba2, Vsftpd. But now and
then when i need to use the original Pogoplug software that came on my plug it
takes forever to respond (if at all).  I came to the conclusion (after finding
it more responsive after a reboot) that its probably struggling with memory
loss. Can anyone tell me if there is a work around, virtual memory or something
like to help out. Thanks in advance for any help offered.

The things you mentioned below for your version of OpenWRT actually sound
correct.  Make sure you have read
http://www.nslu2-linux.org/wiki/OpenWrt/HomePage (especially the section
Configuring DHCP and USB ports in OpenWRT Kamikaze 8.09 and Backfire 10.03) and
http://wiki.openwrt.org/toh/linksys/nslu2 .  The default installation of 10.03
(unless things have changed in a year, ok,maybe 2) is a static ip setup on
192.168.1.1.  It will not show up on your dhcp table because it is static.  You
have to make sure you are on the same subnet as your slug. So make the ip
address of you computer something like 192.168.1.254 temporarily until you
change the slug network setup.  The LED setup that you see,10.03 has most of the
lights turned off (except for Ethernet), is the default and you have to program
what you want those LEDs to do.  See the bottom of the above pages.  You can
setup the stuff with Luci or the setup files.

--- In nslu2-general@yahoogroups.com, "Marcello"  wrote:
>
> hi all, sorry if this is a noob question but i've been trying to flash openwrt
to a NSLU2 for the last couple of days and it's starting to feel like i'm
bashing my head on a wall ;)
>
> i think i managed to flash the openwrt firmware correctly (i'm using 10.3.1)
with upslug2 but i can't connect to the device:
>
> i tried both connecting the NSLU2 to a switch and directly to my computer.
> when i try to telnet (or ping) the device on 192.168.1.1 or 192.168.1.77 it
doesn't respond and when i connect it to the switch it doesn't show up on the
DHCP table.
> when i boot the NSLU2 it flashes all the leds and then shows only the ethernet
led.
>
> any help would be REALLY appreciated!
> Thanks in advance!
> Marcello
>

Depends on your type of Pogoplug.  The V1 and V2s had a fair amount of memory
and shouldn't be hurting.  The mypogoplug.com service itself may be having
problems after being idle for a while (you can kill and restart the service
"/etc/init.d/hbmgr.sh restart").  First, check "ps", check memory use with
"free", then check "top" (ipkg install procps if you don't have it, or atop, or
htop).  Finally read
http://www.nslu2-linux.org/wiki/SlugOS/InstallandTurnupABasicSlugOSSystem .  I
know it is for a SlugOS NSLU2 system, but mwester did a nice writeup of "Adding
a swapfile" and an arm/linux is an arm/linux ...., although you probably don't
need one (DONT do this in your nand space if you decide to implement one, only
should be done on external drive).  This will probably not speed up anything and
may cause things to run slower.  Again do this at your own risk.

--- In nslu2-general@yahoogroups.com, "stigslims"  wrote:
>
> Hi all, back with a new challenge (for me at least). Have been running a
number of programs without any real problems, Transmission, Samba2, Vsftpd. But
now and then when i need to use the original Pogoplug software that came on my
plug it takes forever to respond (if at all).  I came to the conclusion (after
finding it more responsive after a reboot) that its probably struggling with
memory loss. Can anyone tell me if there is a work around, virtual memory or
something like to help out. Thanks in advance for any help offered.
>

Judging by the cautious warning and the small gain from effort involved, i think
its easier to deal with it shortcomings as they arise rather than potentially
cause more harm than good
(after all i am what would be described as a novice). Thanks for the help none
the less, but rest assured i will be back at some point on a search for info.

-- In nslu2-general@yahoogroups.com, "oddballhero"  wrote:
>
>
>
> Depends on your type of Pogoplug.  The V1 and V2s had a fair amount of memory
and shouldn't be hurting.  The mypogoplug.com service itself may be having
problems after being idle for a while (you can kill and restart the service
"/etc/init.d/hbmgr.sh restart").  First, check "ps", check memory use with
"free", then check "top" (ipkg install procps if you don't have it, or atop, or
htop).  Finally read
http://www.nslu2-linux.org/wiki/SlugOS/InstallandTurnupABasicSlugOSSystem .  I
know it is for a SlugOS NSLU2 system, but mwester did a nice writeup of "Adding
a swapfile" and an arm/linux is an arm/linux ...., although you probably don't
need one (DONT do this in your nand space if you decide to implement one, only
should be done on external drive).  This will probably not speed up anything and
may cause things to run slower.  Again do this at your own risk.
>
> --- In nslu2-general@yahoogroups.com, "stigslims"  wrote:
> >
> > Hi all, back with a new challenge (for me at least). Have been running a
number of programs without any real problems, Transmission, Samba2, Vsftpd. But
now and then when i need to use the original Pogoplug software that came on my
plug it takes forever to respond (if at all).  I came to the conclusion (after
finding it more responsive after a reboot) that its probably struggling with
memory loss. Can anyone tell me if there is a work around, virtual memory or
something like to help out. Thanks in advance for any help offered.
> >
>

Hello,
Can someone help me out?  I am trying to build the latest kernel (3.7.2) on my
NSLU2 that is on Debian.  The reason is so I can enable and build the EM28xx USB
video capture modules.The build starts out but winds up with file not found
errors looking up the file(s) in Google result with a bunch of people saying I
need toolchain...  Do I really need the toolchain when building for the same
processor?arm-linux-gnueabi-objdump
Ah I see Debian issues go to a new list now.   Sorry for the spam.
I'm willing to donate if someone does it for me.  I've wasted days on this
reading many outdated howto's and helpguides.
Using build command - foobar:/usr/src/linux-3.7.2# fakeroot make-kpkg --initrd
--revision=1.custom.1.0 kernel_image kernel_headers
build buiild
/bin/sh: arm-linux-gnueabi-objdump: not found  CHK    
include/generated/compile.h  UPD     include/generated/compile.h  CC     
init/version.o/bin/sh: arm-linux-gnueabi-objdump: not found  CC     
init/do_mounts.o/bin/sh: arm-linux-gnueabi-objdump: not found  CC     
init/do_mounts_initrd.o/bin/sh: arm-linux-gnueabi-objdump: not found  LD     
init/mounts.o/bin/sh: arm-linux-gnueabi-ld: not foundmake[2]: ***
[init/mounts.o] Error 127make[1]: *** [init] Error 2make[1]: Leaving directory
`/usr/src/linux-3.7.2'make: *** [debian/stamp/build/kernel] Error
2foobar:/usr/src/linux-3.7.2#
Thanks!


[Non-text portions of this message have been removed]

Yeah, you will still need a tool chain to build anything. This is in Linux
in general, can't build without some basic things. ;)
On Jan 17, 2013 9:04 PM, "Dane Ruyle" <dane_ruyle@...> wrote:

> **
>
>
>
>
> Hello,
> Can someone help me out? I am trying to build the latest kernel (3.7.2) on
> my NSLU2 that is on Debian. The reason is so I can enable and build the
> EM28xx USB video capture modules.The build starts out but winds up with
> file not found errors looking up the file(s) in Google result with a bunch
> of people saying I need toolchain... Do I really need the toolchain when
> building for the same processor?arm-linux-gnueabi-objdump
> Ah I see Debian issues go to a new list now. Sorry for the spam.
> I'm willing to donate if someone does it for me. I've wasted days on this
> reading many outdated howto's and helpguides.
> Using build command - foobar:/usr/src/linux-3.7.2# fakeroot make-kpkg
> --initrd --revision=1.custom.1.0 kernel_image kernel_headers
> build buiild
> /bin/sh: arm-linux-gnueabi-objdump: not found CHK
> include/generated/compile.h UPD include/generated/compile.h CC
> init/version.o/bin/sh: arm-linux-gnueabi-objdump: not found CC
> init/do_mounts.o/bin/sh: arm-linux-gnueabi-objdump: not found CC
> init/do_mounts_initrd.o/bin/sh: arm-linux-gnueabi-objdump: not found LD
> init/mounts.o/bin/sh: arm-linux-gnueabi-ld: not foundmake[2]: ***
> [init/mounts.o] Error 127make[1]: *** [init] Error 2make[1]: Leaving
> directory `/usr/src/linux-3.7.2'make: *** [debian/stamp/build/kernel] Error
> 2foobar:/usr/src/linux-3.7.2#
> Thanks!
>
>
> [Non-text portions of this message have been removed]
>
>
>


[Non-text portions of this message have been removed]

Hi,
Has anyone tried building the (latest) 3.2.7 kernel for the NSLU2?
Maybe I am doing something wrong.  The build starts but eventually errors out
with file not found errors.  It looks like I need a toolchain.  Is this really
necessary if I am building for the same processor?

What is the latest version people have built?

I am looking to enable EM28xx video capture device.

thanks!

Any suggestions on where or how to build the toolchain? I see three options on
the website and went with crosstool but haven't gotten past the homepage.

To: nslu2-general@yahoogroups.com
From: htwiz2002@...
Date: Thu, 17 Jan 2013 21:11:16 -0700
Subject: Re: [nslu2-general] RE: Help building Debian Kernel


























       Yeah, you will still need a tool chain to build anything. This is in Linux

in general, can't build without some basic things. ;)

On Jan 17, 2013 9:04 PM, "Dane Ruyle" dane_ruyle@...> wrote:



> **

>

>

>

>

> Hello,

> Can someone help me out? I am trying to build the latest kernel (3.7.2) on

> my NSLU2 that is on Debian. The reason is so I can enable and build the

> EM28xx USB video capture modules.The build starts out but winds up with

> file not found errors looking up the file(s) in Google result with a bunch

> of people saying I need toolchain... Do I really need the toolchain when

> building for the same processor?arm-linux-gnueabi-objdump

> Ah I see Debian issues go to a new list now. Sorry for the spam.

> I'm willing to donate if someone does it for me. I've wasted days on this

> reading many outdated howto's and helpguides.

> Using build command - foobar:/usr/src/linux-3.7.2# fakeroot make-kpkg

> --initrd --revision=1.custom.1.0 kernel_image kernel_headers

> build buiild

> /bin/sh: arm-linux-gnueabi-objdump: not found CHK

> include/generated/compile.h UPD include/generated/compile.h CC

> init/version.o/bin/sh: arm-linux-gnueabi-objdump: not found CC

> init/do_mounts.o/bin/sh: arm-linux-gnueabi-objdump: not found CC

> init/do_mounts_initrd.o/bin/sh: arm-linux-gnueabi-objdump: not found LD

> init/mounts.o/bin/sh: arm-linux-gnueabi-ld: not foundmake[2]: ***

> [init/mounts.o] Error 127make[1]: *** [init] Error 2make[1]: Leaving

> directory `/usr/src/linux-3.7.2'make: *** [debian/stamp/build/kernel] Error

> 2foobar:/usr/src/linux-3.7.2#

> Thanks!

>

>

> [Non-text portions of this message have been removed]

>

>

>



[Non-text portions of this message have been removed]


















[Non-text portions of this message have been removed]

Hi

I am having trouble starting NFS server on my Pogoplug. I get the following
error messages when I enter /opt/etc/init.d/S56nfsd:

/opt/sbin/rpc.nfsd: error while loading shared libraries: libnsl.so.1: cannot
open shared object file: No such file or directory
/opt/sbin/rpc.mountd: error while loading shared libraries: libnsl.so.1: cannot
open shared object file: No such file or directory

I have installed the package nfs-server. The file libnsl.so.1 is located in
/opt/lib:

-rwxrwxrwx    1 root     root         98394 Feb 14  2012 libnsl-2.5.so
lrwxrwxrwx    1 root     root            13 Jan 18 19:08 libnsl.so.1 ->
libnsl-2.5.so
lrwxrwxrwx    1 root     root            13 Jan 18 19:08 libnsl.so ->
libnsl-2.5.so

Root's PATH is as follows:
PATH=/opt/bin:/opt/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/opt/lib:/usr/local/lib

Do I need to set LD_LIBRARY_PATH for this to work?

Any help much appreciated. By the way I am not an expert in Linux but I am
familiar with some of the basics.

Thanks
Dara

Yes, you need it.  Also make sure you run portmap.  See
http://openpogo.tumblr.com/ .  It shows you what you need to know.

--- In nslu2-general@yahoogroups.com, "dara_mullally"  wrote:
>
> Hi
>
> I am having trouble starting NFS server on my Pogoplug. I get the following
error messages when I enter /opt/etc/init.d/S56nfsd:
>
> /opt/sbin/rpc.nfsd: error while loading shared libraries: libnsl.so.1: cannot
open shared object file: No such file or directory
> /opt/sbin/rpc.mountd: error while loading shared libraries: libnsl.so.1:
cannot open shared object file: No such file or directory
>
> I have installed the package nfs-server. The file libnsl.so.1 is located in
/opt/lib:
>
> -rwxrwxrwx    1 root     root         98394 Feb 14  2012 libnsl-2.5.so
> lrwxrwxrwx    1 root     root            13 Jan 18 19:08 libnsl.so.1 ->
libnsl-2.5.so
> lrwxrwxrwx    1 root     root            13 Jan 18 19:08 libnsl.so ->
libnsl-2.5.so
>
> Root's PATH is as follows:
PATH=/opt/bin:/opt/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/opt/lib:/usr/local/lib
>
> Do I need to set LD_LIBRARY_PATH for this to work?
>
> Any help much appreciated. By the way I am not an expert in Linux but I am
familiar with some of the basics.
>
> Thanks
> Dara
>

Thanks, I will give that a go. I thought I read somewhere that ld_library_path
was not needed for optware.

--- In nslu2-general@yahoogroups.com, "oddballhero"  wrote:
>
> Yes, you need it.  Also make sure you run portmap.  See
http://openpogo.tumblr.com/ .  It shows you what you need to know.
>
> --- In nslu2-general@yahoogroups.com, "dara_mullally"  wrote:
> >
> > Hi
> >
> > I am having trouble starting NFS server on my Pogoplug. I get the following
error messages when I enter /opt/etc/init.d/S56nfsd:
> >
> > /opt/sbin/rpc.nfsd: error while loading shared libraries: libnsl.so.1:
cannot open shared object file: No such file or directory
> > /opt/sbin/rpc.mountd: error while loading shared libraries: libnsl.so.1:
cannot open shared object file: No such file or directory
> >
> > I have installed the package nfs-server. The file libnsl.so.1 is located in
/opt/lib:
> >
> > -rwxrwxrwx    1 root     root         98394 Feb 14  2012 libnsl-2.5.so
> > lrwxrwxrwx    1 root     root            13 Jan 18 19:08 libnsl.so.1 ->
libnsl-2.5.so
> > lrwxrwxrwx    1 root     root            13 Jan 18 19:08 libnsl.so ->
libnsl-2.5.so
> >
> > Root's PATH is as follows:
PATH=/opt/bin:/opt/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/opt/lib:/usr/local/lib
> >
> > Do I need to set LD_LIBRARY_PATH for this to work?
> >
> > Any help much appreciated. By the way I am not an expert in Linux but I am
familiar with some of the basics.
> >
> > Thanks
> > Dara
> >
>

Depends on how the package was built.  If it takes into account /opt/lib.  You
can always put a symbolic link in /usr/lib to the one in /opt/lib.

--- In nslu2-general@yahoogroups.com, "dara_mullally"  wrote:
>
>
> Thanks, I will give that a go. I thought I read somewhere that ld_library_path
was not needed for optware.
>
> --- In nslu2-general@yahoogroups.com, "oddballhero"  wrote:
> >
> > Yes, you need it.  Also make sure you run portmap.  See
http://openpogo.tumblr.com/ .  It shows you what you need to know.
> >
> > --- In nslu2-general@yahoogroups.com, "dara_mullally"  wrote:
> > >
> > > Hi
> > >
> > > I am having trouble starting NFS server on my Pogoplug. I get the
following error messages when I enter /opt/etc/init.d/S56nfsd:
> > >
> > > /opt/sbin/rpc.nfsd: error while loading shared libraries: libnsl.so.1:
cannot open shared object file: No such file or directory
> > > /opt/sbin/rpc.mountd: error while loading shared libraries: libnsl.so.1:
cannot open shared object file: No such file or directory
> > >
> > > I have installed the package nfs-server. The file libnsl.so.1 is located
in /opt/lib:
> > >
> > > -rwxrwxrwx    1 root     root         98394 Feb 14  2012 libnsl-2.5.so
> > > lrwxrwxrwx    1 root     root            13 Jan 18 19:08 libnsl.so.1 ->
libnsl-2.5.so
> > > lrwxrwxrwx    1 root     root            13 Jan 18 19:08 libnsl.so ->
libnsl-2.5.so
> > >
> > > Root's PATH is as follows:
PATH=/opt/bin:/opt/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/opt/lib:/usr/local/lib
> > >
> > > Do I need to set LD_LIBRARY_PATH for this to work?
> > >
> > > Any help much appreciated. By the way I am not an expert in Linux but I am
familiar with some of the basics.
> > >
> > > Thanks
> > > Dara
> > >
> >
>

i tried everything that came to my mind about the ip configuration (with
switch, connecting directly to the NSLU2, with dhcp and without), i tried
pinging 192.168.1.255 and doing arp -a, i downloaded a couple of ip
scanners but both weren't able to find the NSLU2 online.

the device correctly shows up when started in recovery mode but disappears
after the firmware flash...


On Tue, Jan 15, 2013 at 12:55 PM, echo mirage <echomrg@...> wrote:

> I already checked the pages you linked (i knew about the dark leds) but,
> unfortunately, most of the help is about post-flash configurations. the
> only real doubt i have is that i'm using a debian inside a virtualbox on a
> mac to connect and maybe that messed up with my network configuration (but
> upslug worked nicely), i'll double check that before trying to build my own
> image for openwrt with a different default IP.
>
> Thanks for the help!
>
>
> On Tue, Jan 15, 2013 at 12:40 PM, oddballhero <oddballhero@...>wrote:
>
>> The things you mentioned below for your version of OpenWRT actually sound
>> correct.  Make sure you have read
>> http://www.nslu2-linux.org/wiki/OpenWrt/HomePage (especially the section
>> Configuring DHCP and USB ports in OpenWRT Kamikaze 8.09 and Backfire 10.03)
>> and http://wiki.openwrt.org/toh/linksys/nslu2 .  The default
>> installation of 10.03 (unless things have changed in a year, ok,maybe 2) is
>> a static ip setup on 192.168.1.1.  It will not show up on your dhcp table
>> because it is static.  You have to make sure you are on the same subnet as
>> your slug. So make the ip address of you computer something like
>> 192.168.1.254 temporarily until you change the slug network setup.  The LED
>> setup that you see,10.03 has most of the lights turned off (except for
>> Ethernet), is the default and you have to program what you want those LEDs
>> to do.  See the bottom of the above pages.  You can setup the stuff with
>> Luci or the setup files.
>>
>> --- In nslu2-general@yahoogroups.com, "Marcello"  wrote:
>> >
>> > hi all, sorry if this is a noob question but i've been trying to flash
>> openwrt to a NSLU2 for the last couple of days and it's starting to feel
>> like i'm bashing my head on a wall ;)
>> >
>> > i think i managed to flash the openwrt firmware correctly (i'm using
>> 10.3.1) with upslug2 but i can't connect to the device:
>> >
>> > i tried both connecting the NSLU2 to a switch and directly to my
>> computer.
>> > when i try to telnet (or ping) the device on 192.168.1.1 or
>> 192.168.1.77 it doesn't respond and when i connect it to the switch it
>> doesn't show up on the DHCP table.
>> > when i boot the NSLU2 it flashes all the leds and then shows only the
>> ethernet led.
>> >
>> > any help would be REALLY appreciated!
>> > Thanks in advance!
>> > Marcello
>> >
>>
>>
>>
>>
>> ------------------------------------
>>
>> Yahoo! Groups Links
>>
>>
>>
>>
>
>
> --
> Cordiali saluti e ossequi
> - Marcello -
> _______________________________________________________________________
>
>            Numquam ponenda est pluralitas sine necessitate
> _______________________________________________________________________
>



--
Cordiali saluti e ossequi
- Marcello -
_______________________________________________________________________

            Numquam ponenda est pluralitas sine necessitate
_______________________________________________________________________


[Non-text portions of this message have been removed]

Connect the NSLU to a computer that has a static IP configured (do not
connect the NSLU to your network, use a direct ethernet cable between
your PC/laptop and NSLU).
Run ethereal on the specific interface and boot up the NSLU.
Inspect all IP packets and try to figure out the IP of the NSLU.

Regards,
Ovidiu Sas

On Sat, Jan 19, 2013 at 5:30 AM, echo mirage <echomrg@...> wrote:
>
>
>
> i tried everything that came to my mind about the ip configuration (with
> switch, connecting directly to the NSLU2, with dhcp and without), i tried
> pinging 192.168.1.255 and doing arp -a, i downloaded a couple of ip
> scanners but both weren't able to find the NSLU2 online.
>
> the device correctly shows up when started in recovery mode but disappears
> after the firmware flash...
>
> On Tue, Jan 15, 2013 at 12:55 PM, echo mirage echomrg@...> wrote:
>
> > I already checked the pages you linked (i knew about the dark leds) but,
> > unfortunately, most of the help is about post-flash configurations. the
> > only real doubt i have is that i'm using a debian inside a virtualbox on a
> > mac to connect and maybe that messed up with my network configuration (but
> > upslug worked nicely), i'll double check that before trying to build my own
> > image for openwrt with a different default IP.
> >
> > Thanks for the help!
> >
> >
> > On Tue, Jan 15, 2013 at 12:40 PM, oddballhero oddballhero@...>wrote:
>
>
> >
> >> The things you mentioned below for your version of OpenWRT actually sound
> >> correct. Make sure you have read
> >> http://www.nslu2-linux.org/wiki/OpenWrt/HomePage (especially the section
> >> Configuring DHCP and USB ports in OpenWRT Kamikaze 8.09 and Backfire 10.03)
> >> and http://wiki.openwrt.org/toh/linksys/nslu2 . The default
> >> installation of 10.03 (unless things have changed in a year, ok,maybe 2) is
> >> a static ip setup on 192.168.1.1. It will not show up on your dhcp table
> >> because it is static. You have to make sure you are on the same subnet as
> >> your slug. So make the ip address of you computer something like
> >> 192.168.1.254 temporarily until you change the slug network setup. The LED
> >> setup that you see,10.03 has most of the lights turned off (except for
> >> Ethernet), is the default and you have to program what you want those LEDs
> >> to do. See the bottom of the above pages. You can setup the stuff with
> >> Luci or the setup files.
> >>
> >> --- In nslu2-general@yahoogroups.com, "Marcello" wrote:
> >> >
> >> > hi all, sorry if this is a noob question but i've been trying to flash
> >> openwrt to a NSLU2 for the last couple of days and it's starting to feel
> >> like i'm bashing my head on a wall ;)
> >> >
> >> > i think i managed to flash the openwrt firmware correctly (i'm using
> >> 10.3.1) with upslug2 but i can't connect to the device:
> >> >
> >> > i tried both connecting the NSLU2 to a switch and directly to my
> >> computer.
> >> > when i try to telnet (or ping) the device on 192.168.1.1 or
> >> 192.168.1.77 it doesn't respond and when i connect it to the switch it
> >> doesn't show up on the DHCP table.
> >> > when i boot the NSLU2 it flashes all the leds and then shows only the
> >> ethernet led.
> >> >
> >> > any help would be REALLY appreciated!
> >> > Thanks in advance!
> >> > Marcello

Indeed, a google search may help, check out these finds:

http://lists.debian.org/debian-arm/2006/11/msg00045.html
http://old.nabble.com/Cross-compile-toolchain-td30091841.html
http://www.nslu2-linux.org/wiki/Development/MasterMakefile

I'm actually not on Debian myself, but hopefully that should help you
along. ;)


On Fri, Jan 18, 2013 at 2:30 AM, Dane Ruyle <dane_ruyle@...> wrote:

> **
>
>
>
> Any suggestions on where or how to build the toolchain? I see three
> options on the website and went with crosstool but haven't gotten past the
> homepage.
>
> To: nslu2-general@yahoogroups.com
> From: htwiz2002@...
> Date: Thu, 17 Jan 2013 21:11:16 -0700
> Subject: Re: [nslu2-general] RE: Help building Debian Kernel
>
>
> Yeah, you will still need a tool chain to build anything. This is in Linux
>
> in general, can't build without some basic things. ;)
>
> On Jan 17, 2013 9:04 PM, "Dane Ruyle" dane_ruyle@...> wrote:
>
> > **
>
>
> >
>
> >
>
> >
>
> >
>
> > Hello,
>
> > Can someone help me out? I am trying to build the latest kernel (3.7.2)
> on
>
> > my NSLU2 that is on Debian. The reason is so I can enable and build the
>
> > EM28xx USB video capture modules.The build starts out but winds up with
>
> > file not found errors looking up the file(s) in Google result with a
> bunch
>
> > of people saying I need toolchain... Do I really need the toolchain when
>
> > building for the same processor?arm-linux-gnueabi-objdump
>
> > Ah I see Debian issues go to a new list now. Sorry for the spam.
>
> > I'm willing to donate if someone does it for me. I've wasted days on this
>
> > reading many outdated howto's and helpguides.
>
> > Using build command - foobar:/usr/src/linux-3.7.2# fakeroot make-kpkg
>
> > --initrd --revision=1.custom.1.0 kernel_image kernel_headers
>
> > build buiild
>
> > /bin/sh: arm-linux-gnueabi-objdump: not found CHK
>
> > include/generated/compile.h UPD include/generated/compile.h CC
>
> > init/version.o/bin/sh: arm-linux-gnueabi-objdump: not found CC
>
> > init/do_mounts.o/bin/sh: arm-linux-gnueabi-objdump: not found CC
>
> > init/do_mounts_initrd.o/bin/sh: arm-linux-gnueabi-objdump: not found LD
>
> > init/mounts.o/bin/sh: arm-linux-gnueabi-ld: not foundmake[2]: ***
>
> > [init/mounts.o] Error 127make[1]: *** [init] Error 2make[1]: Leaving
>
> > directory `/usr/src/linux-3.7.2'make: *** [debian/stamp/build/kernel]
> Error
>
> > 2foobar:/usr/src/linux-3.7.2#
>
> > Thanks!
>
> >
>
> >
>
> > [Non-text portions of this message have been removed]
>
> >
>
> >
>
> >
>
> [Non-text portions of this message have been removed]
>
>
>
> [Non-text portions of this message have been removed]
>
>
>


[Non-text portions of this message have been removed]