Hi there -

I have been trying to setup a cross compile toolchain but no luck with Ubuntu
10.10 - the main issue is that the Wiki suggests gcc 3.3 but it's way too way
for the news Linux dist. I even setup another VM with Ubuntu 7.10 but apt-get
fails miserably because the packages 7.10 looks for just aren't available
anymore!

http://www.nslu2-linux.org/wiki/Optware/AddAPackageToOptware

Any folks with any luck out there? Appreciate any pointers,

Gilbert

redir_handle = open (redir, O_WRONLY | O_TRUNC | O_CREAT,);

 

On Sat, Mar 05, 2011 at 02:59:28PM +0200, vasanag wrote:
> On 03/05/2011 12:17 AM, nslu@... wrote:
>
> So, if the flash disk is damaged, is there any way to clone it to a
> new one? Can I use a tool like dd or gddrescue to make the cloning?
> Or, a full system installation is needed?

Definitely not saying it is damaged (just a possibility). but if it is
cp should be fine and the way i would do it as any file that is corrupt
should generate an error when its blocks are read. dd or gddrescue may
also work but damaged blocks are just going to be zeroed when copy
leaving you with damaged files, if its the root fs or a system
critical fs starting from scratch would be best and just tar up your
config dir

keep in mind this isnt a nslu specific problem, you may want to try
asking on some generic linux forums as well

I have re-flashed my formerly "unslung" slug with SlugOS/BE and set up my
desired partitioning structure

But when I came to install the various optware packages including coreutils,
rsync, samba, python etc.
I found that there were no packages for librsync and rdiff-backup

Are these (librsync and rdiff-backup) available for SlugOS/BE
or should I go for a Debian-based slug firmware/Debian install to obtain
access to Debian's larger package collection?

Thanks
Ian W.

On Wed, Mar 09, 2011 at 08:55:16PM +0200, vasanag wrote:
> After contacting some other linux forums, I made a backup of the
> flash disk, using ddrescue, and then I checked the filesystem, using
> fsck.  The fsck fixed a lot of problems and the system is working
> perfectly, at the moment.
>
> BUT, how can I be sure that everything is working correctly?  Can I
> trust my system after this repair?  Or, should I install everything
> from scratch?

Hi

cant give you a definate yes or no. me "best practices" would say back
up the configs and start again just to be sure. but if its a non vital
system you are probably fine to let it run till something breaks (eg a
daemon not running)


just boot it up, confirm everything working and let it run if you feel
safe doing it

if you had non system files (pictures/moives) on that flash disk this
may be a good time to look at how you do backups. a 6 month old file
an be better than no file at all

Hello

I've the unslung working on my NSLU2 which is connected to one USB Harddisk. I'd
like to install debian now. I tried the debian installer and the installer asks
to partition USB harddisk. I do not want to lose any data on the harddisk. My
question is this. How do I safely install debian on a HD that was previously
used for Unslung? I would like to retain all the original data on the HD (which
was 60% full).

Thanks in Advance.
MP

I would propose to:
+ remove the HDD
+ install Lenny to an USB stick
+ bring up Lenny setup to whatever you want
+ reattach the HDD
+ finally, add HDD to 'fstab', f.i. to become '/media/data'

This will make you able to anytime change the disk without loosing the
OS and vvs.
Once you need to raplace the HDD, just add an USB hub between SLUG and HDD1,
Attach HDD2, cp all you need from HDD1 to HDD2, edit fstab, remove USB
hub + HDD1 - done

nslu2-linux@yahoogroups.com schrieb:
> There is 1 message in this issue.
>
> Topics in this digest:
>
> 1. Moving from Unslung to Debian
>     From: mp3sub
>
>
> Message
> ________________________________________________________________________
> 1. Moving from Unslung to Debian
>     Posted by: "mp3sub" mp3sub@... mp3sub
>     Date: Mon Mar 21, 2011 11:47 pm ((PDT))
>
> Hello
>
> I've the unslung working on my NSLU2 which is connected to one USB Harddisk.
I'd like to install debian now. I tried the debian installer and the installer
asks to partition USB harddisk. I do not want to lose any data on the harddisk.
My question is this. How do I safely install debian on a HD that was previously
used for Unslung? I would like to retain all the original data on the HD (which
was 60% full).
>
> Thanks in Advance.
> MP
>
>
>
>
>
>
> Messages in this topic (1)
>
>
>
>
>
> ------------------------------------------------------------------------
> Yahoo! Groups Links
>
>
>
> ------------------------------------------------------------------------
>
>
>

--- In nslu2-linux@yahoogroups.com, Robert Hammond <rob.hammond@...> wrote:
>
> In message <idhfr6+coj8@...>, 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

Thank you Robert.  I had to tie up my work on this project before the relatives
arrived for the holidays, so I haven't been able to take advantage of this yet. 
I hope to get back to it in another 6 weeks or so though, so I'm really happy to
see that this was done.

mp3sub <mp3sub@...> writes:

>
> Hello
>
> I've the unslung working on my NSLU2 which is connected to one USB Harddisk.
I'd like to install debian now. I
> tried the debian installer and the installer asks to partition USB harddisk. I
do not want to lose any data
> on the harddisk. My question is this. How do I safely install debian on a HD
that was previously used for
> Unslung? I would like to retain all the original data on the HD (which was 60%
full).

I managed to achieve this by partitioning the disk how I wanted it using gparted
on another Linux machine then selecting manual partitioning when setting up
Debian but it was non trivial. I think it was necessary to make sure /dev/sda3
was a small partition that could be used as /boot

For sale is a NSLU2 with serial port console mod.  I purchased this new a few
years ago and never used it.  It still has Linksys software. Includes: Orginal
Box, Power supply, Linksys CDROM, Stand, Network Cable. Installed the serial
console mod using a 3.5mm plug on the front just above the power switch tested
with teraterm (115200, 8,N,1).   Requires FTDI TTL-232R-3V3-AJ cable, NOT
INCLUDED. Make offer + $10.00 for USPS Flat rate prority shipping.

NO INTERNATIONAL SHIPPING

Thank You,
w5tuh@...

Hello,

I'm using optware on a usb drive with a Cisco e3000. I'm trying to compile my
own package, and had two problems. The first is I noticed /opt/bin/aclocal is a
symlink to /opt/bin/aclocal-1.10, but aclocal-1.11 is what is installed.

root@rom:/opt# ls -la /opt/bin/aclocal*
lrwxrwxrwx    1 root     root           12 Apr  5 02:46 /opt/bin/aclocal ->
aclocal-1.10
-rwxr-xr-x    1 root     root        31181 Dec 21 06:17 /opt/bin/aclocal-1.11

The other problem is that after symlinking correctly, aclocal fails on perl not
being built with ithreads.

root@rom:/opt# ln -sf /opt/bin/aclocal-1.11 /opt/bin/aclocal
root@rom:/opt# aclocal
/opt/share/automake-1.11/Automake/ChannelDefs.pm line 23:

This Perl hasn't been configured and built properly for the threads
module to work.  (The 'useithreads' configuration option hasn't been used.)

Having threads support requires all of Perl and all of the XS modules in
the Perl installation to be rebuilt, it is not just a question of adding
the threads module.  (In other words, threaded and non-threaded Perls
are binary incompatible.)

If you want to the use the threads module, please contact the people
who built your Perl.

Cannot continue, aborting.
BEGIN failed--compilation aborted at
/opt/lib/perl5/5.8.8/mipsel-linux/threads.pm line 28.
Compilation failed in require at
/opt/share/automake-1.11/Automake/ChannelDefs.pm line 23.
BEGIN failed--compilation aborted at
/opt/share/automake-1.11/Automake/ChannelDefs.pm line 26.
Compilation failed in require at
/opt/share/automake-1.11/Automake/Configure_ac.pm line 26.
BEGIN failed--compilation aborted at
/opt/share/automake-1.11/Automake/Configure_ac.pm line 26.
Compilation failed in require at /opt/bin/aclocal line 39.
BEGIN failed--compilation aborted at /opt/bin/aclocal line 39.


I'm new to this list and this development effort. I apologize in advance if this
is the incorrect forum.

Thanks.

I can offer you $50.



----- Original Message ----
From: krisov <w5tuh@...>
To: nslu2-linux@yahoogroups.com
Sent: Thursday, March 31, 2011 14:28:40
Subject: [nslu2-linux] FS NSLU2 with serial port console mod

For sale is a NSLU2 with serial port console mod.  I purchased this new a few
years ago and never used it.  It still has Linksys software. Includes: Orginal
Box, Power supply, Linksys CDROM, Stand, Network Cable. Installed the serial
console mod using a 3.5mm plug on the front just above the power switch tested
with teraterm (115200, 8,N,1).   Requires FTDI TTL-232R-3V3-AJ cable, NOT
INCLUDED. Make offer + $10.00 for USPS Flat rate prority shipping.

NO INTERNATIONAL SHIPPING

Thank You,
w5tuh@...



------------------------------------

Yahoo! Groups Links

Sorry, I have to withdraw my offer as I found one cheaper.



----- Original Message ----
From: Adrian Irimescu <adrian_irimescu@...>
To: nslu2-linux@yahoogroups.com
Sent: Sunday, April 10, 2011 12:06:22
Subject: Re: [nslu2-linux] FS NSLU2 with serial port console mod

I can offer you $50.



----- Original Message ----
From: krisov <w5tuh@...>
To: nslu2-linux@yahoogroups.com
Sent: Thursday, March 31, 2011 14:28:40
Subject: [nslu2-linux] FS NSLU2 with serial port console mod

For sale is a NSLU2 with serial port console mod.  I purchased this new a few
years ago and never used it.  It still has Linksys software. Includes: Orginal
Box, Power supply, Linksys CDROM, Stand, Network Cable. Installed the serial
console mod using a 3.5mm plug on the front just above the power switch tested
with teraterm (115200, 8,N,1).   Requires FTDI TTL-232R-3V3-AJ cable, NOT
INCLUDED. Make offer + $10.00 for USPS Flat rate prority shipping.

NO INTERNATIONAL SHIPPING

Thank You,
w5tuh@...



------------------------------------

Yahoo! Groups Links






------------------------------------

Yahoo! Groups Links

Hello everyone!

I've been using my 1th slug (Unslung 5.5) for more than 3 years now without a
single problem (installed web server, CUPS, MusicBrowser, etc).

Here's the situation.
Recently I got a brand new 2d slug, upgraded from the original V23R25 to V23R29,
then to V23R63, tested with 2 Ext. Disks (Lacie and Memup - 1 Tb cap. each);
finally, since everything appeared to be working properly, upgraded to unslung
6.10.

I was unsure about the slug's behaviour with the 2 large hard disks attached,
but my first tests after the unslung/unsling process went smoothly: it
recognized, mounted and formatted both disks to EXT3 without any trouble; I was
also able to access the web interface and perform the basic download/uploading
of large files -- all worked well.

Then, in my ignorance (being an average windows user lacking the proper
knowledge of Linux), I made what I thought it was a trivial change, but that
turned out to be a total disaster: at the slug's web interface I decided to
delete a user I had created before upgrading to unslung 6.10 (having admin.
privileges) and then, changed my mind, and, in that same windows session,
recreated the same user back again. Immediately after that, windows (Vista Home
Prem. 32b) started denying me access into the admin folder; but much worse than
that: after  restarting the slug in an attempt to fix things, I realized that
the slug wasn't booting anymore: since then, in all my attempts to reboot
properly (with no disks attached), it starts as usual by flashing the 1th led
(amber => green) and then the 1th and the 2d led, but it never ends the boot
process with the final little beep... Both leds remain steady green (the 2d
flashing sometimes indicating some ethernet activity) but no way of reaching the
slug using telnet/http/ftp with Putty/WinScp, etc

I'll list below the attempts that I made so far trying to fix the situation,
hoping that someone among the more experienced users at the forum (or someone
having been through the same trouble) may give me some hint to put me on the
right track so I could get my slug back into business:
1) Of course I started by trying those basic solutions like booting without any
disks attached, press for 30 secs the reset button at the back of the device and
then restart... no joy.

2) Thanks to the wonderful how~tos available at the forum's site, I was able to
get into the slug's redboot prompt(from a linux session using a Knoppix 6.4.4 CD
and then following the method of telneting to 192.168.0.1, port 9000, using
iputils/arping commands).

3) At redboot prompt, first, I only issued the command 'reset', closed the linux
session, restarted windows, rebooted the slug and tried to access the web
interface - no success!

4) Then, I thought the trouble probably was due to some malfunction at the
non-volatile SysConf area of flash; so I got again into redboot prompt and
issued the command 'fis erase -f 0x50040000 -l 0x20000' and then 'restart' to
put the slug in upgrade mode, closed that telnet session at redboot and upgraded
the slug back to linksys V23R63 firmware; although the upgrade process finished
successfully according to Sercomm's utility final message - the slug doesn't
finish the boot process!

5) After that I reflashed several times (using the same method) - sequentially
from V23R63 back to V23R25 and then again conversely up to unslung 6.10 - still
no joy!

The list of the available commands produced by 'help' at the redboot command
intimidates someone lacking the specific knowledge like me, so I didn't dare to
use them (except for the command 'boot' related to Sercomm's utility, which
anyway didn't produced any visible change).

So I'm running here out of ways to try to fix things. I recognize at this stage
I feel tempted to try the infamous linksys EraseAll utility (since, despite the
risk, it apparently erases all the slug's flash prior to reflashing a fresh
image and, thus, maybe, the offended part will be reseted as well. In fact, the
choice seems to be: throwing the little fellow into garbage or try that last
attempt. But before I do that, I want to see if there's some another possible
solution to try and would be very grateful if someone could help me to get into
the right track.

Greetings to all (and sorry for being so long in my post)
Joao Miranda (Lisbon)

I recommend to flash SlugOS 5.x LE, before killing the device with
EraseAll. Just need to note 2 things:
     1) google "NSLU2 turnup" and follow this instructions
     2) replace defective setup-optware.sh with the repaired version below

A lot of things are going different with SlugOS, so misconfiguration of
the unslung stuff my be bypassed. It is _not_ to hard for an experienced
windows user to use this "bit more linux than unslung" system. Be
courageous. Be cool. Learn a lot.

Or you can try the more impressive way ... Martin Michlmayr's prepared
"Debian for NSLU2" <http://www.cyrius.com/debian/nslu2/>. Personally, I
was a bit angry to use Debian on the Slug and the Plug. After 22 years
of experience with CP/M, DOS, WIN, but only some hours Knoppix and some
days of SlugOS 5.3/LE - I asked if this is the right experience to
switch to a real Linux. ... then I used Debian for the 1st time ... Now
I'm switching all my PCs, Laptops, Servers to Debian (except one Gaming
PC). You can't get more dumb by trying it.


fixed setup-optware.sh (you can copy&paste it to joe or nano or vi, but
may need fix CR/LF to LF then):
___________________________
#!/bin/sh

if test 0 != `id -u`; then
     echo 'Please run as root'
     exit 1
fi

if test `uname -m` = armv5teb ; then
     optware_target=slugos5be
else
     optware_target=slugos5le
fi

feed=http://ipkg.nslu2-linux.org/feeds/optware/${optware_target}/cross/unstable
latest_xsh=`wget -q -O- ${feed} | grep '\.xsh' | sed -e 's/.*xsh">//' -e
's/<.*//'`

if test -n "${latest_xsh}"; then
     cd /tmp
     rm -f ${latest_xsh}
     wget ${feed}/${latest_xsh}
     sh ${latest_xsh}
fi
___________________________

> 1. Another Slug dead (itr doesn't boot..) -- any hint/suggestion very w
>     From: jmir_po
>
> [...]
> So I'm running here out of ways to try to fix things. I recognize at this
stage I feel tempted to try the infamous linksys EraseAll utility

Hi,

I have a NSLU2 running DD-WRT v24-sp2, ackfire 10.03.1-rc3,r22796 with attached
a USB drive Samsung HD103UL.
My problem is it doesn't get into sleepmode, and read
http://www.nslu2-linux.org/wiki/FAQ/SpinDownUSBHarddisks
I tried all available tools for that (hdparm, sdparm, sg_start, scsi-stop) and
even tried to change powermodes but without luck.
I've put the drive into a PC and I could get it into sleep there so physically
it should be able to handle it.

For me having a NSLU2 and storage that doesn't go into sleepmode is useless, I
wanted this setup just to save power and saving HD from wearing out.

Please help me, I'm desperate.
PS: Switching firmware is not really an option to me since this firmware has all
I want fitting in default memory.

PLEASE HELP!
Thanks in advance.

Hi Mai!
Many thanks for your feedback and the information! You're right: my troubles
with the slug are an opportunity to try out something new and more solid then
unslung. I'll follow your suggestion about trying SlugOs and maybe later the
Debian version (looked the link you sent about Martin Michlmayr's site and it
sounds interesting, lot's of information for beginners like me...

Still, I don't want to give up (yet) the idea of restoring the slug, specially
because I am not totally sure about the mistake that caused the problem... So,
if you have a spare moment, please, look at the list of the attempts I made to
restore it and tell me is there any other method I could try?

For some silly reason I wasn't able to reproduce successfully the how-to
'UpSlug2' (http://www.nslu2-linux.org/wiki/Main/UpSlug2) and manually reflash
the slug: I manage to install upslug2 (on a linux session using Knoppix) and
then it recognizes the slug (which is in upgrade mode); yet, when I issue the
command:

upslug2 --target="xx:xx:xx:xx:xx:xx" --image="NSLU2_V23R63.bin"

I get an error message from linux stating that system doesn't recognize that
file or folder; obviously I need to find out how to tell linux where the
firmware is... Is there a command for that?
(the slug is connected to my laptop through an ethernet cable; the laptop is
connected to my router (Thomson TG784) using a network cable as well)

Once again, thank you for your feedback!
Joao Miranda




--- In nslu2-linux@yahoogroups.com, Mai Kee Reis <maik_nospam_reiss@...> wrote:
>
> I recommend to flash SlugOS 5.x LE, before killing the device with
> EraseAll. Just need to note 2 things:
>     1) google "NSLU2 turnup" and follow this instructions
>     2) replace defective setup-optware.sh with the repaired version below
>
> A lot of things are going different with SlugOS, so misconfiguration of
> the unslung stuff my be bypassed. It is _not_ to hard for an experienced
> windows user to use this "bit more linux than unslung" system. Be
> courageous. Be cool. Learn a lot.
>
> Or you can try the more impressive way ... Martin Michlmayr's prepared
> "Debian for NSLU2" <http://www.cyrius.com/debian/nslu2/>. Personally, I
> was a bit angry to use Debian on the Slug and the Plug. After 22 years
> of experience with CP/M, DOS, WIN, but only some hours Knoppix and some
> days of SlugOS 5.3/LE - I asked if this is the right experience to
> switch to a real Linux. ... then I used Debian for the 1st time ... Now
> I'm switching all my PCs, Laptops, Servers to Debian (except one Gaming
> PC). You can't get more dumb by trying it.
>
>
> fixed setup-optware.sh (you can copy&paste it to joe or nano or vi, but
> may need fix CR/LF to LF then):
> ___________________________
> #!/bin/sh
>
> if test 0 != `id -u`; then
>     echo 'Please run as root'
>     exit 1
> fi
>
> if test `uname -m` = armv5teb ; then
>     optware_target=slugos5be
> else
>     optware_target=slugos5le
> fi
>
>
feed=http://ipkg.nslu2-linux.org/feeds/optware/${optware_target}/cross/unstable
> latest_xsh=`wget -q -O- ${feed} | grep '\.xsh' | sed -e 's/.*xsh">//' -e
> 's/<.*//'`
>
> if test -n "${latest_xsh}"; then
>     cd /tmp
>     rm -f ${latest_xsh}
>     wget ${feed}/${latest_xsh}
>     sh ${latest_xsh}
> fi
> ___________________________
>
> > 1. Another Slug dead (itr doesn't boot..) -- any hint/suggestion very w
> >     From: jmir_po
> >
> > [...]
> > So I'm running here out of ways to try to fix things. I recognize at this
stage I feel tempted to try the infamous linksys EraseAll utility

Hi,

There are only a few USB bridge controllers within an USB drive enclosure (the
controller chop converts the USB protocol/signals to SATA or IDE for the
harddrive) that pass the sleep command through.

Some bridge controllers from JMicron or Cypress work.

Also some USB enclosures (WD My Passport) do it automatically.

Ernst

--- In nslu2-linux@yahoogroups.com, "ZakHooi" <combegt@...> wrote:
>
> Hi,
>
> I have a NSLU2 running DD-WRT v24-sp2, ackfire 10.03.1-rc3,r22796 with
attached a USB drive Samsung HD103UL.
> My problem is it doesn't get into sleepmode, and read
http://www.nslu2-linux.org/wiki/FAQ/SpinDownUSBHarddisks
> I tried all available tools for that (hdparm, sdparm, sg_start, scsi-stop) and
even tried to change powermodes but without luck.
> I've put the drive into a PC and I could get it into sleep there so physically
it should be able to handle it.
>
> For me having a NSLU2 and storage that doesn't go into sleepmode is useless, I
wanted this setup just to save power and saving HD from wearing out.
>
> Please help me, I'm desperate.
> PS: Switching firmware is not really an option to me since this firmware has
all I want fitting in default memory.
>
> PLEASE HELP!
> Thanks in advance.
>

jmir_po <j-mir@...> writes:
...

> But before I do that, I
> want to see if there's some another possible solution to try and would be very
> grateful if someone could help me to get into the right track.
>

If you have access to a multimeter it would be worthwhile checking what voltage
is on the slug's power supply when it is running (often the 5V pin on the USB
connector is the easiest point to measure it). When the PSU is failing it can
often manage to run redboot but not boot the complete system.

Adam

Hi,
requesting update of bitlbee 3.0.1 -> 3.0.2
and bip 0.8.4 -> 0.8.8
in optware.
~K

Thank you, Brian.  You all made the process very no-mess, no-fuss.

Making a few commits now, prolly just updates to (more) current versions, for
some basic packages.

****I think I've spotted a minor problem w/ the "make directories" makefile...
it doesn't create the required directory called "bin" at : 
optware/staging/opt/bin  .  I've seen this I think everytime I've built libpcap
on a fresh/virgin toolchain setup.   My manual fix for this is just to go in and
create the dir by hand via command line or via Nautilus.

Since this is a toolchain question I thought I'd pass it by you, on the minor
chance that it could be some quirky 32 vs 64 bit difference...  Maybe no one
else sees it?

again, thanks,

davy

Hi ZakHooi,

does the scsi-start and scsi-stop command work, if manually executed on
you OS?

With my OS (SlugOS/LE 5.3) + ICY-BOX + WD10EACS, it does it's job, if
manually executed.
It is not invoking scsi-stop automatically, until I installed a cron
triggered perl or bash script which is analyzing /proc/hdparm (or such)
statistics.
But it is still not usable because kernel never invokes scsi-start (need
kernel patch). I don't know how to apply such kernel patch to SlugOS 5.3.
The source for my inspiration was the NSLU wiki, but finally, I was not
able to solve this an my own. My 4th box is a Sheeva, running Debian.
This baby is doing the spinup / spindown perfectly from scratch! With
the same model of ICY-BOX and WD10. So, now  I'm planning to bring my
spare NSLU2 to Debian (Martin Michlmayr's "Squeeze" adoption). If this
runs well with spinup/down, I'll move my older NSLU2 boxes step by step
to Debian.

As a conclusion:
1) you'll need to check, if the basics are running (manual invocation).
Then you know if your hardware is supporting scsi spindown.
2) if _yes_, you'll next need to check, if the kernel and/or some pseudo
deamon (cron'ed perl script) is trying to do its job
3) if _no_ and you are not able to fix the shit, think about Debian.
Debian 5 is completely ready to run on NSLU2 from official Debian setup
CD. Debian 6 is avail at Martin.

Sorry for no better help, I'm also a bloody newbie since 3 years ;-)
Mai Kee

> ________________________________________________________________________
> 1. HELP:spindown usbdrive doesn't work (DD-WRT v24-sp2, ackfire 10.03.1
>     Posted by: "ZakHooi" combegt@... combegt
>     Date: Fri Apr 15, 2011 9:58 am ((PDT))
>
> [...]
> I have a NSLU2 running DD-WRT v24-sp2, ackfire 10.03.1-rc3,r22796 with
attached a USB drive Samsung HD103UL.
> My problem is it doesn't get into sleepmode
> [...]
> scsi-stop
> [...]
>

Hi Joao,

sorry for being late - I tried to find your posting on my hard disk, but
missed it multiple times because the not so wisely choosen "Subj:" line ;-)

> ________________________________________________________________________
> 2a. Re: Digest Number 2665
>     Posted by: "jmir_po" j-mir@... jmir_po
>     Date: Fri Apr 15, 2011 3:08 pm ((PDT))
>
>
> [...]
> Still, I don't want to give up (yet) the idea of restoring the slug, specially
because I am not totally sure about the mistake that caused the problem...
> [...]
>
Okay, that's the prefered way, all Linux users shall think!
;-)

> [...]
> So, if you have a spare moment, please, look at the list of the attempts I
made to restore it and tell me is there any other method I could try?
> [...]
>
I'm afraid, the problem on my side is not only the lack of spare time.
It's more the lack of knowledge :-(
My spare time is also my rare time.
> [...]
> upslug2 --target="xx:xx:xx:xx:xx:xx" --image="NSLU2_V23R63.bin"
>
> I get an error message from linux stating that system doesn't recognize that
file or folder; obviously I need to find out how to tell linux where the
firmware is... Is there a command for that?
> [...]
>
Did you mentioned to give a full path to --image ?
upslug2 --target="xx:xx:xx:xx:xx:xx" --image="/home/joao/NSLU2_V23R63.bin"
I don't know upsulg from Linux, so I't only *guessed*.
I always used the hard-to-find Windows tool
"SercommFirmwareUpdater_Upgrade_207_XP.zip" or "Upgrade_207_XP.exe"- at
least this are the names it has recently on my hard disk.
> [...]
> (the slug is connected to my laptop through an ethernet cable; the laptop is
connected to my router (Thomson TG784) using a network cable as well)
> [...]
>
I prefered to use a crossover cable and temporarily manually assigned IP
addresses an the PC. In times one can't find the crossover cable (lent
to brother or classmate? Or dropped behind the bookshelf?), such
adaptors are handy:
<http://www.angledcables.com/ethernet-crossover-adapter--rj.html>.
Bought mine at Pearl.de, but it's common Chinese scrap, so it should be
easy to get one. (Sorry to any Chinese people! Ranting about your low
budget electric products is a genetic defect on my side. I can't
withstand this).

HTH,
Mai Kee

Hi Mai!
Thank you for your reply and support! I did managed to solve the problem thanks
to your previous suggestion! I'll make here a small description of the steps I
took so someone else falling in the same situation could try the same solution.

As I said in my previous post, after several attempts to solve the problem
(re-flashed my slug several times from NSLU2_V23R25.bin to NSLU2_V23R63.bin and
Unslung 6.10 using upslug2 from a Linux session using a Knoppix CD, as well as
the Windows Sercomm's utility), I decided to try your suggestion and flashed the
slug with the Debian firmware (di-nslu2.bin). After the flash process finished,
It didn't allowed me to log in using ssh and proceed with the Debian
installation (I guess because of ip conflict and dhcp); after that, I
immediately re-flashed again with Lynksys V23R63 and... bingo! my slug came back
to live again, i.e., it finished the boot process normally with the usual little
final beep.

The funny part of the story is that during this mini-drama, searching for a
solution, I realized how much you're right about the advantages of going debian
(well, compared with Unslung); so I re-flashed once again the slug with the
debian firmware and I'm now a brand-new-linux-newbie trying furiously to setup
my webserver, cups, etc.

Once again - thanks for your support and hints!
Joao




--- In nslu2-linux@yahoogroups.com, Mai Kee Reis <maik_nospam_reiss@...> wrote:
>
> Hi Joao,
>
> sorry for being late - I tried to find your posting on my hard disk, but
> missed it multiple times because the not so wisely choosen "Subj:" line ;-)
>
> > ________________________________________________________________________
> > 2a. Re: Digest Number 2665
> >     Posted by: "jmir_po" j-mir@... jmir_po
> >     Date: Fri Apr 15, 2011 3:08 pm ((PDT))
> >
> >
> > [...]
> > Still, I don't want to give up (yet) the idea of restoring the slug,
specially because I am not totally sure about the mistake that caused the
problem...
> > [...]
> >
> Okay, that's the prefered way, all Linux users shall think!
> ;-)
>
> > [...]
> > So, if you have a spare moment, please, look at the list of the attempts I
made to restore it and tell me is there any other method I could try?
> > [...]
> >
> I'm afraid, the problem on my side is not only the lack of spare time.
> It's more the lack of knowledge :-(
> My spare time is also my rare time.
> > [...]
> > upslug2 --target="xx:xx:xx:xx:xx:xx" --image="NSLU2_V23R63.bin"
> >
> > I get an error message from linux stating that system doesn't recognize that
file or folder; obviously I need to find out how to tell linux where the
firmware is... Is there a command for that?
> > [...]
> >
> Did you mentioned to give a full path to --image ?
> upslug2 --target="xx:xx:xx:xx:xx:xx" --image="/home/joao/NSLU2_V23R63.bin"
> I don't know upsulg from Linux, so I't only *guessed*.
> I always used the hard-to-find Windows tool
> "SercommFirmwareUpdater_Upgrade_207_XP.zip" or "Upgrade_207_XP.exe"- at
> least this are the names it has recently on my hard disk.
> > [...]
> > (the slug is connected to my laptop through an ethernet cable; the laptop is
connected to my router (Thomson TG784) using a network cable as well)
> > [...]
> >
> I prefered to use a crossover cable and temporarily manually assigned IP
> addresses an the PC. In times one can't find the crossover cable (lent
> to brother or classmate? Or dropped behind the bookshelf?), such
> adaptors are handy:
> <http://www.angledcables.com/ethernet-crossover-adapter--rj.html>.
> Bought mine at Pearl.de, but it's common Chinese scrap, so it should be
> easy to get one. (Sorry to any Chinese people! Ranting about your low
> budget electric products is a genetic defect on my side. I can't
> withstand this).
>
> HTH,
> Mai Kee
>