My bad.  The led was flashing amber/green which was the problem.

After a few goes, I got the led to flash red/green which was really
the upgrade mode.  All is good now.  Thanks.

--- In nslu2-linux@yahoogroups.com, "Jonathon Smith"
<bruceleetokyo@...> wrote:
>
> Hello,
>
> I currently have debian installed on a 1gig usb stick.  I would like
> to reinstall to a 160gig usb hard disk.
>
> I disconnected the usb stick and reboot the nslu2 to upgrade mode but
> I could not ping the IP, therefore cannot load the new installer.
>
> Is their anything special which needs to be done for a reinstall?
>

--- In nslu2-linux@yahoogroups.com, "reuter.rudolf" <reuterru@...> wrote:
>
> --- In nslu2-linux@yahoogroups.com, "Mike (mwester)" <mwester@> wrote:
> >
> > reuter.rudolf wrote:
> > ...
> > > What I get now, after deleting
> > > linux-ixp4xx-2.6.27.8+svnr1085-r2.do_compile and "make
> slugosbe-image" is:
> > >
> > > make[1]: Entering directory
> > >
>
`/home/rudi/slug/slugos/tmp/work/nslu2be-linux-gnueabi/linux-ixp4xx-2.6.27.8+svn\
r1085-r2/linux-2.6.27'
> > >   CC      init/main.o
> > > armeb-linux-gnueabi-ld: init/.tmp_main.o: compiled for a little
endian
> > > system and target is big endian
> > > armeb-linux-gnueabi-ld: failed to merge target specific data of file
> > > init/.tmp_main.o
> > > make[1]: *** [init/main.o] Error 1
> > >
> > > Then I deleted init/.tmp_main.o and started again, with the same
> > > results. Is it now the best to delete the whole /slug/slugos/tmp
> folder?
> >
> > Wow!  I have no idea what happened, but it looks like you have part of
> > your environment built with little-endian, and part with big-endian --
> > that's one of those things that I suspect the OE experts would "that
> > can't happen".
> >
> > Yes, delete the entire tmp directory, and start fresh.  Make sure that
> > you take care to make "slugosbe-image", and never "slugosle-image"
(or,
> > for those that prefer little-endian, the other way around - it makes
> > little difference as long as its all consistent).
> >
> > Again, that can't happen.  But clearly it did, somehow.
> >
> > Mike (mwester)
> >
> >
> > BTW, if you can just provide the complete list of modules you need
> > enabled, we can add them to the SlugOS 5 feeds as soon as I get the
> > release done, and the feeds building -- hopefully a matter of one
final
> > opkg patch to do, and then the mechanics of the release process to
> execute.
> >
> Thank you for your help Mike, and for the offer to include the modules
> in the feed.
> I like to have uvcvideo.ko (probably CONFIG_USB_VIDEO_CLASS=m) for my
> webcam and pwc.ko (probably CONFIG_USB_PWC=m) which is for Philips
> webcams, just in case. They use the V4L2 (Video for Linux version 2)
> support, which is already enabled in the feed, but I could not test
> that yet, because of the missing uvcvideo.ko driver.
>
> I tried to compile with a new "tmp" folder, with the following result:
> 2009-02-28 23:13 slug/slugos/tmp deleted and make slugosbe-image:
> NOTE: Tasks Summary: Attempted 732 tasks of which 0 didn't need to be
> rerun and 1 failed.
> ERROR:
> '/home/rudi/slug/slugos/openembedded/packages/glibc/glibc_2.6.1.bb'
failed
> NOTE: build 200902282313: completed
> make[1]: *** [image] Fehler 1
> make[1]: Verlasse Verzeichnis '/home/rudi/slug/slugos'
> make: *** [slugosbe-image] Fehler 2
>
> In my next try I will delete slug/slugos and start again.
>
> Regards, Rudolf
>
Hello Mike,
The kernel module uvcvideo.ko is now working. I renamed slug/slugos
and started again.
First to my special problem:
After a resizing of the Linux partition of my development computer the
swap partition was not enabled. Therefore I got sometimes an "out of
memory error" - fixed.

A detailed explanation of the build process ------------------
In order to compile "uvcvideo.ko" (webcam driver) you first type:
"make ARCH=arm menuconfig" in path
slug/slugos/tmp/work/nslu2be-linux-gnueabi/linux-ixp4xx-2.6.27.8+svnr1085-r2/lin\
ux-2.6.27
and set flag:
/Device Drivers/Multimedia Devices/Video capture adapters/V4L USB
devices/USB Video Class (UVC) <M>
and save the file ".config".
If the phase "config" is not run, it is useful to also edit
config-2.6.27.8 in path:
slug/slugos/tmp/staging/nslu2be-linux-gnueabi/kernel
Insert after "# CONFIG_USB_VIDEO_CLASS is not set"
CONFIG_USB_VIDEO_CLASS=m

In order to enable compilation you should delete the file:
linux-ixp4xx-2.6.27.8+svnr1085-r2.do_compile
in path: slug/slugos/tmp/stamps/nslu2be-linux-gnueabi
Maybe deleting .do_config will avoid editing config-2.6.27.8.

Next run from path slug "make slugosbe-image".
The file kernel-module-uvcvideo_2.6.27.8+svnr1085-r2_nslu2be.ipk
is found in path: slug/slugos/tmp/deploy/ipk/nslu2be

My next action will be to compile the source code for uvccapture, a
video camera capture tool, which works for me under slugOS4.8.
Do you please have a hint, how to do that in accordance with the rules?

Thanks for the big help Mike.
Regards, Rudolf

i'm trying to run hellanzb on my slug runnng debian lenny 5.0

On giganews i'm only getting 4kbp/s. Is there any config change i can
make to speed up performance?

Can I use nzbget on debian if not?

Thanks a lot,

Joe

Thanks for the pointer. I'd like to buy a replacement that won't
involve me doing any cable mods. I don't really trust my electronics
:)

What's the plug size on the NSLU2?

Thanks

On Thu, Feb 26, 2009 at 4:21 PM, Ian White <iandavidwhite@...> wrote:
> And from another source, a replacement (UK) power supply at a more sensible
> price
>
>
>
http://www.poweradaptorsuk.co.uk/index.php?cat=5_volt_adaptors&ActinicSID=467440\
c8ab5b6a28e4a3b3a84aa51ba8
>
> First PSU on the page is capable of 2.5 amps at 5 volts DC
> which, subject to current carrying capacity of the slug circuit board power
> tracks easily should be able to power a couple of bus-powered devices
>
> And if you are only going to power the nslu2, the last PSU on this same page
> is even cheaper
> but note 1000ma is probably not really enough to power the slug and any bus
> powered USB devices
> at least not without running the PSU at near full capacity which might cause
> reliablilty problems
>
>
>
> ----- Original Message -----
> From: Ian White
> To: nslu2-linux@yahoogroups.com
> Sent: Thursday, February 26, 2009 11:35 AM
> Subject: Re: [nslu2-linux] Re: Bricked by Lenny?
> I am successfully using http://www.maplin.co.uk/Module.aspx?ModuleNo=48517
> (which I bought when it was on a better discount than it currently is)
>
> But http://www.maplin.co.uk/Module.aspx?ModuleNo=48484 ought to do as an
> alternative
>
> I'm sure that there must be a number of other sources of 230 volt AC -to- 5
> volt DC (at circa 1.5 amp) power supplies
> at better prices than Maplin
>
> Especially if you are prepared to do some cable mods on the DC side of a PSU
> to achieve correct DC power plug
>
>
> ----- Original Message -----
> From: Nick Boyle
> To: nslu2-linux@yahoogroups.com
> Sent: Thursday, February 26, 2009 10:30 AM
> Subject: Re: [nslu2-linux] Re: Bricked by Lenny?
>
> Can anyone recommend a replacement adaptor from Maplins in the UK?
>
> On Thu, Feb 26, 2009 at 12:07 AM, Harsh <harshbaste@...> wrote:
>> I had a similar behavior when I got my slug over from the US and plugged
>> it
>> into a wall point in Singapore. Didn't realize I was plugging a
>> non-adjustable 110V US adaptor into a 230V socket. The behavior was
>> exactly
>> as you described - a quick flash of the green (ready) light every time I
>> pressed the power button but the device refused to switch on.
>>
>> A few more attempts and the green flash also disappeared so I'm guessing
>> there was a capacitor in the adaptor discharging whatever power it had
>> stored in it and when it got maxed out that was the end of it.
>>
>> Got a new adaptor and it all worked fine.
>>
>> I think I heard elsewhere on this newsgroup that the stock Linksys adaptor
>> is also of slightly poor quality and prone to fail.
>>
>>
>> ________________________________
>> From: sdm485 <steve@...>
>> To: nslu2-linux@yahoogroups.com
>> Sent: Wednesday, 25 February, 2009 8:53:04 PM
>> Subject: [nslu2-linux] Re: Bricked by Lenny?
>>
>> It sounds like the power supply since it can't even get to the Reboot
>> loader. Probably a
>> capacitor inside has failed. It is probably a coincidence that it happened
>> during the upgrade.
>> USB hub power supplies work as a replacement but you have to change the
>> plug
>> on the end.
>> Steve
>>
>> --- In nslu2-linux@ yahoogroups. com, Nick Boyle <nick@...> wrote:
>>>
>>> It was all working fine, then I updated the distro to Lenny.
>>>
>>> It was off last night when I got in, and repeatedly tried to switch it
>>> on. Got a quick flash of the green light on the power switch, but that
>>> was it. The USB drive is fine and is currently plugged into my Ubuntu
>>> server.
>>>
>>> Any ideas?
>>>
>>
>>
>> ________________________________
>> Bollywood news, movie reviews, film trailers and more! Click here.
>>
>>
>
>

One of the things I'm sure new users find confusing about SlugOS is
the fact that there is never a release called "Release" or "Final".
Version 3.10 is labelled Beta, version 4.10 is labelled Beta, and I
wager version 5 will be labelled Beta beyond its Beta too.

What are we, Google? (o:

Another problem is that 3.10 is still mentioned at
http://www.nslu2-linux.org as the version to download, until the user
reaches this page:
http://www.slug-firmware.net/s-dls.php

I'm willing to clean up the documentation if there's support for my
doing so.

Hi Jay,

I'm having the same problem. Tried with the supplied binary but also
compiled it myself with no success.

- michael

Jay schrieb:
> Hi all,
>
> Tonight I downloaded and flashed my fatslug with Kamikaze 8.09 via
> UpSlug2. Flash process worked without issues, slug rebooted itself,
> all the lights flashed, then after what seemed to me to be an
> uncomfortable length of time the Ethernet light turns green - all
> other lights including Ready light are not illuminated.
>
> I look in my router's dhcp leases and see the slug requested
> 192.168.1.130 which is the same address is had before the flash attempt.
>
> Attempts to ping, telnet, and ssh are all met with failure.
>
> In desperation I re-flashed back to v 7.09 with success but I'm left
> frustrated and wondering what with wrong with the flash attempt.
>
> Unfortunately creating a serial connector is beyond my expertise.
>
> Any thoughts and/or advice is much appreciated!
>
>
>
>
>
> ------------------------------------
>

Jay-127 wrote:
>
>
> Attempts to ping, telnet, and ssh are all met with failure.
>
>

I have the same problem, though I used the 8mb 'non-fat' image.  Hopefully
there is a quick fix for this!

--
View this message in context:
http://www.nabble.com/nslu2-and-kamikaze-8.09-tp22269826p22289808.html
Sent from the Nslu2 - Linux mailing list archive at Nabble.com.

dystopianrebel wrote:
> One of the things I'm sure new users find confusing about SlugOS is
> the fact that there is never a release called "Release" or "Final".
> Version 3.10 is labelled Beta, version 4.10 is labelled Beta, and I
> wager version 5 will be labelled Beta beyond its Beta too.
>
> What are we, Google? (o:

I shall respond to this by quoting an email I sent out to another user
who ventured a different theory on why we don't do "release" or "final":

----------------------------
(10-Feb-2007)

>> Presumably 6.8 is beta because of this kind of undiscovered problem!

> Actually, I prefer to think that the "-beta" nomenclature is less
"problem-oriented" as it is "expectation-oriented".  It certainly is
true that the community does not have the test equipment and formal
procedures associated with many commercial release processes, but on the
other hand, this community has a diversity and breadth of environments
that would be the envy of well-run QA labs.  IMO, the "-beta" is an
indicator of what is expected -- users should not expect a problem-free
experience, but like a well-run Beta program, users can expect the
involvement by the developers and contributors to help them solve the
problem.  On the flip side, users also need to expect that just as in a
formal Beta program, they are required to take an active role in helping
to diagnose and solve any problems they encounter.

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


> Another problem is that 3.10 is still mentioned at
> http://www.nslu2-linux.org as the version to download, until the user
> reaches this page:
> http://www.slug-firmware.net/s-dls.php
>
> I'm willing to clean up the documentation if there's support for my
> doing so.

Excellent timing!  Your application has been accepted.  :-D

SlugOS 5.3-beta is almost done; it awaits a README file, a couple of
final tests, an MD5 sum, and it then will move to the slug-firmware.net
site for downloads.

No documentation exists on the wiki at this time for that release.  The
wiki is huge, and the collective knowledge stored there is considerable.
  But the other side of that coin is that it's often like rummaging
through an old warehouse -- it's hard to know what is outdated versus
what is current.

We're going to fix that with a new convention for SlugOS 5.3 (and
beyond) -- you can go peek at the DSM-G600 pages to get an idea of how
we will be marking pages going forward.  So folks perusing the wiki will
be clearly able to see pages specific to SlugOS 5.3 based on the words
and color-coding at the top of the page.  We'll also be asking users to
"certify" pages that are still useful -- a different bit of test will be
added to existing pages that are still pertinent to SlugOS 5.3.

The idea is that the user has a clear visual cue on each page that will
tell them when they have wandered away from the known-good docs for a
specific distro, or distro version (if it's specific to a version).

Stay tuned -- I'm travelling yet again this week, so I really can't say
when this will actually get done (depends on how much "quality" time I
end up with in airports, I suspect).  But it should be Real Soon Now(tm).

-Mike (mwester)

I'm sort of at the end of my rope on this one, and could really use
help from some of the seasoned experts...

I've picked up a USB audio dongle (although I attempted to secure one
with a C-Media chip, I ended up with "3D SOUND" dongle with a JMTek
chip in it)... I've managed to configure the dongle with my NSLU2
running Unslung 6.10 Beta.  I abandoned getting it to work with a USB
2.0 hub, but have met with success using a Texas Instruments
TUSB2040/2070 USB 1.1 hub.  I also have a Western Digital .5 Tb MyBook
sharing the USB hub, which has all my MP3s on it.

When I use madplay (0.15.2) to playback an MP3, sound comes out of the
USB dongle (although it does sound like the MP3 is either downsampled,
or over-driven) and is delivered to my speakers.

However, when I attempt to use MPD (0.14.2) with the wymypy web-based
front-end for playback, the playback is badly stuttered (like, a
half-second of audio is heard, then a second of silence, then another
half-second of audio, etc.).  Top reveals MPD's CPU utilization is
pegged at 97%, leading me to believe the stuttering is a side affect
of the excessive utilization.

I could go about getting another server-side playback utility running,
but I was hoping to avoid setting up PHP and/or a web server.  Madplay
reports only using between 5% and 15% CPU utilization, so what's up
with MPD?  Is it using some floating point calculation that can be
supressed through mpd.conf possibly?

Also, any ideas on improving the fidelity of the sound sample coming
out of the USB dongle?  I know the dongle is capable of much higher
quality, having used it with another system...

Hello!
If I remember correctly, the NSLU2 processor is one of those unlucky ones to
be created without a FPU as part of its design.

Technically the processor it uses is ideal for file management, and of
course as it happens working in some routers, and of course the NSLU2.
Because it does not have this FPU, Linux on it needs to emulate (some how)
the floating point functions that we take for granted on desktops and full
size servers, except for IBM's Z Series. So it spends its time physically
doing that and causes the MP3 players such as that one to produce choppy
sound. (And the other one to bollix the sampling actions.)

If you have access to another system running Linux, (your choice of
distributions), try your MP3s on the same player there.

Next up: Is this a powered hub? I certainly hope so. You have your disk
drive there that holds your collection, and the sound device dongle.

The other issue is why did you abandon using the USB 2.0 hub? Supposedly the
NSLU2 contains USB 2.0 connectors, so the hub should agree with them.

The other thing that comes to mind is perhaps your choice of installed
release, but I don't think it is at fault here.

--
Gregg C Levine hansolofalcon@...
"The Force will be with you always." Obi-Wan Kenobi
 


> -----Original Message-----
> From: nslu2-linux@yahoogroups.com [mailto:nslu2-linux@yahoogroups.com] On
Behalf
> Of threeeyedtoad
> Sent: Monday, March 02, 2009 10:47 PM
> To: nslu2-linux@yahoogroups.com
> Subject: [nslu2-linux] HELP - MP3 playback using MPD on unslung 6.10
>
> I'm sort of at the end of my rope on this one, and could really use
> help from some of the seasoned experts...
>
> I've picked up a USB audio dongle (although I attempted to secure one
> with a C-Media chip, I ended up with "3D SOUND" dongle with a JMTek
> chip in it)... I've managed to configure the dongle with my NSLU2
> running Unslung 6.10 Beta.  I abandoned getting it to work with a USB
> 2.0 hub, but have met with success using a Texas Instruments
> TUSB2040/2070 USB 1.1 hub.  I also have a Western Digital .5 Tb MyBook
> sharing the USB hub, which has all my MP3s on it.
>
> When I use madplay (0.15.2) to playback an MP3, sound comes out of the
> USB dongle (although it does sound like the MP3 is either downsampled,
> or over-driven) and is delivered to my speakers.
>
> However, when I attempt to use MPD (0.14.2) with the wymypy web-based
> front-end for playback, the playback is badly stuttered (like, a
> half-second of audio is heard, then a second of silence, then another
> half-second of audio, etc.).  Top reveals MPD's CPU utilization is
> pegged at 97%, leading me to believe the stuttering is a side affect
> of the excessive utilization.
>
> I could go about getting another server-side playback utility running,
> but I was hoping to avoid setting up PHP and/or a web server.  Madplay
> reports only using between 5% and 15% CPU utilization, so what's up
> with MPD?  Is it using some floating point calculation that can be
> supressed through mpd.conf possibly?
>
> Also, any ideas on improving the fidelity of the sound sample coming
> out of the USB dongle?  I know the dongle is capable of much higher
> quality, having used it with another system...
>
>

HowTo block IP number ranges from input with iptables.
Unfortunately kernel-module-ipt-iprange is missing in the slugOS5 feed.

My NSLU2 web server (moinmoin Python standalone server) was yesterday
attacked by chinese cmputers (use Reverse DNS), so my web site was no
longer available to the public. The IP numbers in the access log of
the web server showed in most cases at "reverse DNS" that they come
from China. So what to do?
Google was my friend and I found under http://www.okean.com a list
(china.txt) of IP number ranges (530) from China. Most of the
attackers IP numbers could be found in those number ranges. But how to
exclude them from web server access?
A search in the internet recommended the use of iptables. Up to now I
have seen only to exclude single IP numbers from access. Fortunately
there is an extension to iptables available "iprange" (kernel-module).
What has to be installed:
ipkg install iptables
ipkg install iptables-utils
ipkg install iptables-doc
ipkg install kernel-module-ip-tables
ipkg install kernel-module-ipt-iprange # fehlt in SlugOS5
depmode -a
modprobe ip_tables
modprobe ipt-iprange
Test:
root@LKG95AC9E:~$ lsmod
Module                  Size  Used by
ipt_iprange              832  529
iptable_filter          1472  1
ip_tables               9832  1 iptable_filter
x_tables                8548  2 ipt_iprange,ip_tables

How to define ranges in iptables, example:
iptables -A INPUT -m iprange --src-range 58.14.0.0-58.25.255.255 -j DROP

You can imagin, that it is not very convenient to type 530 lines like
the above. So I wrote a little Python script to do the work:
#!/usr/bin/env python
# use: script to setup iptables with blacklist iprange
# 2009-03-02 iptables_blacklist.py, RR

blacklist = "china_blacklist.txt"
blacklist_sh = "china_blacklist.sh"

sline = ""
sline2 = ""
sline3 = ""

try:
     fbl = file(blacklist, 'r')
     fbls = file(blacklist_sh, 'w')
     fbls.write("#!/bin/sh \n")
     for sline in fbl:
         if sline.find("#"):       # filter comments
             sline2 = sline.replace(' - ', '-')
             sline2 = sline2.replace(' China', '')
             sline2 = sline2.replace('\n', '') # remove EOL
             #print sline2  # append "," for no EOL
             sline3 = "iptables -I INPUT -m iprange --src-range "
             sline3 = sline3 + sline2 + " -j DROP"
             fbls.write(sline3 + "\n")
     fbl.close()
     fbls.close()
except:
     print 'File not found: ' + blacklist

After editing the file iptables_blacklist.py either set the execute
bits, or call "python iptables_blacklist.py".
Then either set the execute bits of "china_blacklist.sh", or call "sh
china_blacklist.sh". Test it with:
root@LKG95AC9E:~/iptables$ iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
DROP       all  --  anywhere             anywhere            source IP
range 222.240.0.0-222.249.249.255
...

In order to save the iptables settings use "iptables-save
>iptables.sav". After that you can restore the parameters with
"iptables-restore iptables.sav".
What I have not done up to now is to provide a startup script in
/etc/init.d.

I hope it will help people who are in the same situation like me.
Regards, Rudolf

p.s. Unfortunately kernel-module-ipt-iprange is missing in the slugOS5
feed.

--
http://www.knecht-ruprecht.info

Hello Mario,

as a fist thing, I forgot to mention I am using slugOS 4.8 on my NSLU2.

Fail2Ban is an interesting program. But it is mainly for SSH use. See
the docu:
First of all, remember that Fail2ban is a log parser. It cannot do
anything before something is written in the log files.
... and is mainly looking for password abuse.

Therefore it would not help in my case.

Regards, Rudolf

--- In nslu2-linux@yahoogroups.com, "Mario Ruprecht" <mario@...> wrote:
>
> Maybe Fail2Ban could be an alternative to control iptables?
> http://www.fail2ban.org/wiki/index.php/Main_Page
>
> Not sure if it's available for Unslung, though.
>
> Cheers, Mario
>
> --
>  <http://www.knecht-ruprecht.info/> http://www.knecht-ruprecht.info
>
>
>
>
>   _____
>
> From: nslu2-linux@yahoogroups.com [mailto:nslu2-linux@yahoogroups.com]
> On Behalf Of reuter.rudolf
> Sent: Tuesday, March 03, 2009 8:05 AM
> To: nslu2-linux@yahoogroups.com
> Subject: [nslu2-linux] NSLU2 web server was attacked by chinese
> computers, use of iptables
>
>
>
> HowTo block IP number ranges from input with iptables.
> Unfortunately kernel-module-ipt-iprange is missing in the slugOS5 feed.
>
> My NSLU2 web server (moinmoin Python standalone server) was yesterday
> attacked by chinese cmputers (use Reverse DNS), so my web site was no
> longer available to the public. The IP numbers in the access log of
> the web server showed in most cases at "reverse DNS" that they come
> from China. So what to do?
> Google was my friend and I found under http://www.okean.
> <http://www.okean.com> com a list
> (china.txt) of IP number ranges (530) from China. Most of the
> attackers IP numbers could be found in those number ranges. But how to
> exclude them from web server access?
> A search in the internet recommended the use of iptables. Up to now I
> have seen only to exclude single IP numbers from access. Fortunately
> there is an extension to iptables available "iprange" (kernel-module).
> What has to be installed:
> ipkg install iptables
> ipkg install iptables-utils
> ipkg install iptables-doc
> ipkg install kernel-module-ip-tables
> ipkg install kernel-module-ipt-iprange # fehlt in SlugOS5
> depmode -a
> modprobe ip_tables
> modprobe ipt-iprange
> Test:
> root@LKG95AC9E:~$ lsmod
> Module Size Used by
> ipt_iprange 832 529
> iptable_filter 1472 1
> ip_tables 9832 1 iptable_filter
> x_tables 8548 2 ipt_iprange,ip_tables
>
> How to define ranges in iptables, example:
> iptables -A INPUT -m iprange --src-range 58.14.0.0-58.25.255.255 -j DROP
>
> You can imagin, that it is not very convenient to type 530 lines like
> the above. So I wrote a little Python script to do the work:
> #!/usr/bin/env python
> # use: script to setup iptables with blacklist iprange
> # 2009-03-02 iptables_blacklist.py, RR
>
> blacklist = "china_blacklist.txt"
> blacklist_sh = "china_blacklist.sh"
>
> sline = ""
> sline2 = ""
> sline3 = ""
>
> try:
> fbl = file(blacklist, 'r')
> fbls = file(blacklist_sh, 'w')
> fbls.write("#!/bin/sh \n")
> for sline in fbl:
> if sline.find("#"): # filter comments
> sline2 = sline.replace(' - ', '-')
> sline2 = sline2.replace(' China', '')
> sline2 = sline2.replace('\n', '') # remove EOL
> #print sline2 # append "," for no EOL
> sline3 = "iptables -I INPUT -m iprange --src-range "
> sline3 = sline3 + sline2 + " -j DROP"
> fbls.write(sline3 + "\n")
> fbl.close()
> fbls.close()
> except:
> print 'File not found: ' + blacklist
>
> After editing the file iptables_blacklist.py either set the execute
> bits, or call "python iptables_blacklist.py".
> Then either set the execute bits of "china_blacklist.sh", or call "sh
> china_blacklist.sh". Test it with:
> root@LKG95AC9E:~/iptables$ iptables -L
> Chain INPUT (policy ACCEPT)
> target prot opt source destination
> DROP all -- anywhere anywhere source IP
> range 222.240.0.0-222.249.249.255
> ...
>
> In order to save the iptables settings use "iptables-save
> >iptables.sav". After that you can restore the parameters with
> "iptables-restore iptables.sav".
> What I have not done up to now is to provide a startup script in
> /etc/init.d.
>
> I hope it will help people who are in the same situation like me.
> Regards, Rudolf
>
> p.s. Unfortunately kernel-module-ipt-iprange is missing in the slugOS5
> feed.
>

--
http://www.knecht-ruprecht.info

Thanks for the quick response.

I'm fully aware that the NSLU2 does not have a FPU.  This is well
documented in the wiki pages.  Also well documented are the MP3
players that only use integer math.  Both madplay and MPD are both
included in the list of supported MP3 players that use integer math.
As I described, madplay works fine, but (to my knowledge) does not
support remote server play via a web interface.  MPD has many clients
that support remote play via the web.

I've read in several places online that replaygain (and possibly
software volume control - whatever that is) MAY use FP math.  My
question for those who have gotten MPD successfully running on a Slug
- is there a configuration that can be made in mpd.conf that would
suppress any functionality that utilizes FPU?

As for the hub - yes, I'm using a powered USB 1.1 hub.  Again, using
maadplay, everything is hunky dory playing MP3s off a HD plugged into
the same 1.1 hub.  I bailed on a USB 2.0 hub after reading multiple
places that the USB audio dongle may not play nice with a 2.0 hub - at
least, not using an unslung distro.  The USB 2.0 hub is fine with the
unslung NSLU to hang HD drives off, but not for the audio.

So - thoughts on how to get MPD working without FPU math under unslung?


--- In nslu2-linux@yahoogroups.com, "Gregg C Levine"
<hansolofalcon@...> wrote:
>
> Hello!
> If I remember correctly, the NSLU2 processor is one of those unlucky
ones to
> be created without a FPU as part of its design.
>
> Technically the processor it uses is ideal for file management, and of
> course as it happens working in some routers, and of course the NSLU2.
> Because it does not have this FPU, Linux on it needs to emulate
(some how)
> the floating point functions that we take for granted on desktops
and full
> size servers, except for IBM's Z Series. So it spends its time
physically
> doing that and causes the MP3 players such as that one to produce choppy
> sound. (And the other one to bollix the sampling actions.)
>
> If you have access to another system running Linux, (your choice of
> distributions), try your MP3s on the same player there.
>
> Next up: Is this a powered hub? I certainly hope so. You have your disk
> drive there that holds your collection, and the sound device dongle.
>
> The other issue is why did you abandon using the USB 2.0 hub?
Supposedly the
> NSLU2 contains USB 2.0 connectors, so the hub should agree with them.
>
> The other thing that comes to mind is perhaps your choice of installed
> release, but I don't think it is at fault here.
>
> --
> Gregg C Levine hansolofalcon@...
> "The Force will be with you always." Obi-Wan Kenobi
>
>
>
> > -----Original Message-----
> > From: nslu2-linux@yahoogroups.com
[mailto:nslu2-linux@yahoogroups.com] On
> Behalf
> > Of threeeyedtoad
> > Sent: Monday, March 02, 2009 10:47 PM
> > To: nslu2-linux@yahoogroups.com
> > Subject: [nslu2-linux] HELP - MP3 playback using MPD on unslung 6.10
> >
> > I'm sort of at the end of my rope on this one, and could really use
> > help from some of the seasoned experts...
> >
> > I've picked up a USB audio dongle (although I attempted to secure one
> > with a C-Media chip, I ended up with "3D SOUND" dongle with a JMTek
> > chip in it)... I've managed to configure the dongle with my NSLU2
> > running Unslung 6.10 Beta.  I abandoned getting it to work with a USB
> > 2.0 hub, but have met with success using a Texas Instruments
> > TUSB2040/2070 USB 1.1 hub.  I also have a Western Digital .5 Tb MyBook
> > sharing the USB hub, which has all my MP3s on it.
> >
> > When I use madplay (0.15.2) to playback an MP3, sound comes out of the
> > USB dongle (although it does sound like the MP3 is either downsampled,
> > or over-driven) and is delivered to my speakers.
> >
> > However, when I attempt to use MPD (0.14.2) with the wymypy web-based
> > front-end for playback, the playback is badly stuttered (like, a
> > half-second of audio is heard, then a second of silence, then another
> > half-second of audio, etc.).  Top reveals MPD's CPU utilization is
> > pegged at 97%, leading me to believe the stuttering is a side affect
> > of the excessive utilization.
> >
> > I could go about getting another server-side playback utility running,
> > but I was hoping to avoid setting up PHP and/or a web server.  Madplay
> > reports only using between 5% and 15% CPU utilization, so what's up
> > with MPD?  Is it using some floating point calculation that can be
> > supressed through mpd.conf possibly?
> >
> > Also, any ideas on improving the fidelity of the sound sample coming
> > out of the USB dongle?  I know the dongle is capable of much higher
> > quality, having used it with another system...
> >
> >
>

Just put kamikaze 8.09 on my 128M fatslug; it has a serial port. It  booted up
with a static
IP of 192.168.1.1. I changed that to my network in the /etc/config/network file
and
rebooted. It now works fine via the webpage. It sees all the RAM too.
Steve



--- In nslu2-linux@yahoogroups.com, Jay Johnson <jej_94107@...> wrote:
>
> Thanks much for this Michael - makes me feel a bit better.
>
> For now I'm gonna leave it at 7.09 but I sure would like to know what's up :).
>
> Good luck with your slug!
>
> Cheers,
>
> Jay
>
> --- On Mon, 3/2/09, Michael Stucki <mundaun@...> wrote:
> From: Michael Stucki <mundaun@...>
> Subject: [nslu2-linux] Re: nslu2 and kamikaze 8.09
> To: nslu2-linux@yahoogroups.com
> Date: Monday, March 2, 2009, 3:18 AM
>
>
>
>
>
>
>
>
>
>
>
>
>             Hi Jay,
>
>
>
> I'm having the same problem. Tried with the supplied binary but also
>
> compiled it myself with no success.
>
>
>
> - michael
>
>
>
> Jay schrieb:
>
> > Hi all,
>
> >
>
> > Tonight I downloaded and flashed my fatslug with Kamikaze 8.09 via
>
> > UpSlug2. Flash process worked without issues, slug rebooted itself,
>
> > all the lights flashed, then after what seemed to me to be an
>
> > uncomfortable length of time the Ethernet light turns green - all
>
> > other lights including Ready light are not illuminated.
>
> >
>
> > I look in my router's dhcp leases and see the slug requested
>
> > 192.168.1.130 which is the same address is had before the flash attempt.
>
> >
>
> > Attempts to ping, telnet, and ssh are all met with failure.
>
> >
>
> > In desperation I re-flashed back to v 7.09 with success but I'm left
>
> > frustrated and wondering what with wrong with the flash attempt.
>
> >
>
> > Unfortunately creating a serial connector is beyond my expertise.
>
> >
>
> > Any thoughts and/or advice is much appreciated!
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > ------------ --------- --------- ------
>
> >
>

I also had to change the root password from the webpage before I could log in
via ssh. I
didn't know the default password and this worked...:) Looks like 4M+ of jffs for
additional
programs. Cool.
S


--- In nslu2-linux@yahoogroups.com, Jay Johnson <jej_94107@...> wrote:
>
> Thanks much for this Michael - makes me feel a bit better.
>
> For now I'm gonna leave it at 7.09 but I sure would like to know what's up :).
>
> Good luck with your slug!
>
> Cheers,
>
> Jay
>
> --- On Mon, 3/2/09, Michael Stucki <mundaun@...> wrote:
> From: Michael Stucki <mundaun@...>
> Subject: [nslu2-linux] Re: nslu2 and kamikaze 8.09
> To: nslu2-linux@yahoogroups.com
> Date: Monday, March 2, 2009, 3:18 AM
>
>
>
>
>
>
>
>
>
>
>
>
>             Hi Jay,
>
>
>
> I'm having the same problem. Tried with the supplied binary but also
>
> compiled it myself with no success.
>
>
>
> - michael
>
>
>
> Jay schrieb:
>
> > Hi all,
>
> >
>
> > Tonight I downloaded and flashed my fatslug with Kamikaze 8.09 via
>
> > UpSlug2. Flash process worked without issues, slug rebooted itself,
>
> > all the lights flashed, then after what seemed to me to be an
>
> > uncomfortable length of time the Ethernet light turns green - all
>
> > other lights including Ready light are not illuminated.
>
> >
>
> > I look in my router's dhcp leases and see the slug requested
>
> > 192.168.1.130 which is the same address is had before the flash attempt.
>
> >
>
> > Attempts to ping, telnet, and ssh are all met with failure.
>
> >
>
> > In desperation I re-flashed back to v 7.09 with success but I'm left
>
> > frustrated and wondering what with wrong with the flash attempt.
>
> >
>
> > Unfortunately creating a serial connector is beyond my expertise.
>
> >
>
> > Any thoughts and/or advice is much appreciated!
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > ------------ --------- --------- ------
>
> >
>

sdm485 wrote:
>
> It  booted up with a static
> IP of 192.168.1.1.
>

Thanks so much for finding 'the problem' i.e. that the OS was booting with
an unexpected (?) IP address.  With a bit of temporary ethernet cable
swapping, I was able to connect and 'fix' the network settings back to what
I wanted them to be :)

As well, I had not been aware of the 'web' interface that was available.
Pretty nifty!

Now, hopefully, I will be able to install all the packages that I could not
before with the 'hybrid' webcam-only version of Kamikaze that I had
previously!

--
View this message in context:
http://www.nabble.com/nslu2-and-kamikaze-8.09-tp22269826p22312437.html
Sent from the Nslu2 - Linux mailing list archive at Nabble.com.

I've just installed Debian Lenny on my nslu2 and went to install
Dovecot.  It wasn't found, but a search produced dovecot-common,
which I then installed.

I made a couple of mistakes in editing dovecot.conf, corrected them,
but then got :-
"
# 1.0.15: /etc/dovecot/dovecot.conf
Error: Can't use mail executable /usr/lib/dovecot/imap: No such file or
directory
Fatal: Invalid configuration in /etc/dovecot/dovecot.conf "

The folder /usr/lib/dovecot/ does exist with various files, but not imap.

I decided to play safe (I thought) and, to get a fresh .conf, removed
  dovecot and reinstalled it.  However, it said it wasn't restoring
the deleted file(s).  I then tried the old unslung dovecot.conf which
  I still had, but got the same error as above.

So, a couple of questions.
a) Should there be a dovecot, or is dovecot-common OK?
b) Where is /usr/lib/dovecot/imap?
b+1) How can I get a fresh dovecot.conf (plus the other files from /etc/dovecot
which I deleted)?

Thanks

Allan

I just disabled libsamplerate in mpd configure except on x86 optware target.
When libsamplerate is enabled, it does quite a lot of FP calculation. Please
give mpd_0.14.2-3 a try and see if it makes any difference.

-Brian Zhou

--- In nslu2-linux@yahoogroups.com, "threeeyedtoad" <threeeyedtoad@...> wrote:
>
> I'm sort of at the end of my rope on this one, and could really use
> help from some of the seasoned experts...
>
> I've picked up a USB audio dongle (although I attempted to secure one
> with a C-Media chip, I ended up with "3D SOUND" dongle with a JMTek
> chip in it)... I've managed to configure the dongle with my NSLU2
> running Unslung 6.10 Beta.  I abandoned getting it to work with a USB
> 2.0 hub, but have met with success using a Texas Instruments
> TUSB2040/2070 USB 1.1 hub.  I also have a Western Digital .5 Tb MyBook
> sharing the USB hub, which has all my MP3s on it.
>
> When I use madplay (0.15.2) to playback an MP3, sound comes out of the
> USB dongle (although it does sound like the MP3 is either downsampled,
> or over-driven) and is delivered to my speakers.
>
> However, when I attempt to use MPD (0.14.2) with the wymypy web-based
> front-end for playback, the playback is badly stuttered (like, a
> half-second of audio is heard, then a second of silence, then another
> half-second of audio, etc.).  Top reveals MPD's CPU utilization is
> pegged at 97%, leading me to believe the stuttering is a side affect
> of the excessive utilization.
>
> I could go about getting another server-side playback utility running,
> but I was hoping to avoid setting up PHP and/or a web server.  Madplay
> reports only using between 5% and 15% CPU utilization, so what's up
> with MPD?  Is it using some floating point calculation that can be
> supressed through mpd.conf possibly?
>
> Also, any ideas on improving the fidelity of the sound sample coming
> out of the USB dongle?  I know the dongle is capable of much higher
> quality, having used it with another system...
>

* allanganderson <aganderson@...> [2009-03-04 01:23]:
> I've just installed Debian Lenny on my nslu2 and went to install
> Dovecot.  It wasn't found, but a search produced dovecot-common,
> which I then installed.

I don't know anything about dovecot, but installing the -common
package itself is most certainly not enough.  You'll also need
dovecot-imapd

Note that your question is better asked on the
debian-user@... list since it is not NSLU2 specific.
--
Martin Michlmayr
http://www.cyrius.com/

> I made a couple of mistakes in editing dovecot.conf, corrected them,
> but then got :-
> "
> # 1.0.15: /etc/dovecot/dovecot.conf
> Error: Can't use mail executable /usr/lib/dovecot/imap: No such file or
directory
> Fatal: Invalid configuration in /etc/dovecot/dovecot.conf "
>
> The folder /usr/lib/dovecot/ does exist with various files, but not imap.
>
> I decided to play safe (I thought) and, to get a fresh .conf, removed
>  dovecot and reinstalled it.  However, it said it wasn't restoring
> the deleted file(s).  I then tried the old unslung dovecot.conf which
>  I still had, but got the same error as above.
>
> So, a couple of questions.
> a) Should there be a dovecot, or is dovecot-common OK?
> b) Where is /usr/lib/dovecot/imap?
> b+1) How can I get a fresh dovecot.conf (plus the other files from
/etc/dovecot which I deleted)?
Dovecot is split into several packages. All of them require
dovecot-common. Depending on our needs you want to install either or
both of:

dovecot-imapd - secure IMAP server that supports mbox and maildir mailboxes
dovecot-pop3d - secure POP3 server that supports mbox and maildir mailboxes

I think that apt-get purge dovecot-common should remove all files and
allow the conf file to be re-installed.

Ian.

Rock on.  Disabling libsamplerate did the trick for me in mpd_0.14.2-3.  Now
that I know what to search for, there are some threads that have recently spun
up on the linux.debian.bugs.dist Google Group (specifically Bug#517976),
complaining about libsamplerate as a CPU hog for machines without FPU.  I guess
there have been changes to MPD recently that changed how this was implemented.

    Brian, thanks for the quick response and attention in this matter.  I'm
amazed and grateful for how well the *nix community continues to support the
little Slug, five years after it was first introduced to the market.  Amazing.


--- In nslu2-linux@yahoogroups.com, "Brian Zhou" <b88zhou@...> wrote:
>
> I just disabled libsamplerate in mpd configure except on x86 optware target.
When libsamplerate is enabled, it does quite a lot of FP calculation. Please
give mpd_0.14.2-3 a try and see if it makes any difference.
>
> -Brian Zhou
>
> --- In nslu2-linux@yahoogroups.com, "threeeyedtoad" <threeeyedtoad@> wrote:
> >
> > I'm sort of at the end of my rope on this one, and could really use
> > help from some of the seasoned experts...
> >
> > I've picked up a USB audio dongle (although I attempted to secure one
> > with a C-Media chip, I ended up with "3D SOUND" dongle with a JMTek
> > chip in it)... I've managed to configure the dongle with my NSLU2
> > running Unslung 6.10 Beta.  I abandoned getting it to work with a USB
> > 2.0 hub, but have met with success using a Texas Instruments
> > TUSB2040/2070 USB 1.1 hub.  I also have a Western Digital .5 Tb MyBook
> > sharing the USB hub, which has all my MP3s on it.
> >
> > When I use madplay (0.15.2) to playback an MP3, sound comes out of the
> > USB dongle (although it does sound like the MP3 is either downsampled,
> > or over-driven) and is delivered to my speakers.
> >
> > However, when I attempt to use MPD (0.14.2) with the wymypy web-based
> > front-end for playback, the playback is badly stuttered (like, a
> > half-second of audio is heard, then a second of silence, then another
> > half-second of audio, etc.).  Top reveals MPD's CPU utilization is
> > pegged at 97%, leading me to believe the stuttering is a side affect
> > of the excessive utilization.
> >
> > I could go about getting another server-side playback utility running,
> > but I was hoping to avoid setting up PHP and/or a web server.  Madplay
> > reports only using between 5% and 15% CPU utilization, so what's up
> > with MPD?  Is it using some floating point calculation that can be
> > supressed through mpd.conf possibly?
> >
> > Also, any ideas on improving the fidelity of the sound sample coming
> > out of the USB dongle?  I know the dongle is capable of much higher
> > quality, having used it with another system...
> >
>

Hi,

I tried to compile nslu2 according to the information found on the wiki page:

$ svn co http://svn.nslu2-linux.org/svnroot/optware/trunk optware
$ cd optware
$ make wl500g-target
$ cd wl500g
$ make

in the very first steps:

...
checking for
mipsel-linux-gcc... /opt/brcm/hndtools-mipsel-uclibc/bin/mipsel-uclibc-gcc
checking for C compiler default output file name... configure: error: C
compiler cannot create executables
...

It seems that the configure scripts found the mipsel-uclibc-gcc, but it is (of
course) completely missing from my machine, so it is unusable. Other targets
(e.g. nslu2-target) seem good: they compile the cross-compiler first.
I don't know what can be wrong.

Thanx in advance
K. Gy.

--- In nslu2-linux@yahoogroups.com, Martin Michlmayr <tbm@...> wrote:
>
> * allanganderson <aganderson@...> [2009-03-04 01:23]:
> > I've just installed Debian Lenny on my nslu2 and went to install
> > Dovecot.  It wasn't found, but a search produced dovecot-common,
> > which I then installed.
>
> I don't know anything about dovecot, but installing the -common
> package itself is most certainly not enough.  You'll also need
> dovecot-imapd
>
> Note that your question is better asked on the
> debian-user@... list since it is not NSLU2 specific.
> --
> Martin Michlmayr
> http://www.cyrius.com/
>

Hi Martin

Yes, eventually, I found that, when I installed dovecot* instead of
dovecot-common.

I don't understand though, why after I'd deleted the .conf file,
apt-get wouldn't re-install it.  Good job I had an old one.
Perhaps ask this on debian@ ?

Thanks for your reply, and great work on the Debian front!

Allan

--- In nslu2-linux@yahoogroups.com, Ian Barton <lists@...> wrote:
>
> > I made a couple of mistakes in editing dovecot.conf, corrected them,
> > but then got :-
> > "
> > # 1.0.15: /etc/dovecot/dovecot.conf
> > Error: Can't use mail executable /usr/lib/dovecot/imap: No such file or
directory
> > Fatal: Invalid configuration in /etc/dovecot/dovecot.conf "
> >
> > The folder /usr/lib/dovecot/ does exist with various files, but not imap.
> >
> > I decided to play safe (I thought) and, to get a fresh .conf, removed
> >  dovecot and reinstalled it.  However, it said it wasn't restoring
> > the deleted file(s).  I then tried the old unslung dovecot.conf which
> >  I still had, but got the same error as above.
> >
> > So, a couple of questions.
> > a) Should there be a dovecot, or is dovecot-common OK?
> > b) Where is /usr/lib/dovecot/imap?
> > b+1) How can I get a fresh dovecot.conf (plus the other files from
/etc/dovecot which I deleted)?
> Dovecot is split into several packages. All of them require
> dovecot-common. Depending on our needs you want to install either or
> both of:
>
> dovecot-imapd - secure IMAP server that supports mbox and maildir mailboxes
> dovecot-pop3d - secure POP3 server that supports mbox and maildir mailboxes
>
> I think that apt-get purge dovecot-common should remove all files and
> allow the conf file to be re-installed.
>
> Ian.
>

Hi Ian

I'd found that install dovecot* instead of dovecot-common got me the missing
pieces!

Thanks for the tip on purge.  I'm new to apt.

Allan

--- In nslu2-linux@yahoogroups.com, "Mike (mwester)" <mwester@...> wrote:
> I shall respond to this by quoting an email I sent out to another user
> ----------------------------
> IMO, the "-beta" is an
> indicator of what is expected -- users should not expect a problem-free
> experience, but like a well-run Beta program, users can expect the
> involvement by the developers and contributors to help them solve the
> problem.

Has development ceased for 3.10 and 4.10? If so, I do believe it would be
clearer to users if we declared the ancestor "final" when the descendant is
approved for all new installations.

An alternative is to adopt the convention of distinguishing among the "latest,
stable" release, the "development, unstable" release, and the "old, stable"
release.

> Excellent timing!  Your application has been accepted.  :-D
> SlugOS 5.3-beta is almost done; it awaits a README file, a couple of
> final tests, an MD5 sum, and it then will move to the slug-firmware.net
> site for downloads.

Let me know when I can be of assistance.

Hi,
I just installed SlugOS/BE 4.8 Beta on my NSLU2, with samba and ntpclient using
ipkg.

I installed ez-ipupdate, but figured out it doesn't work for my network, as
NSLU2 is connected to a router and ez-ipupdate only gets my eth0 local address
and not my public address (the only way to make it work is by applying a patch
to ez-ipupdate).

So I decided to use ddclient, but ddclient did not appear in my ipkg list. I was
wondering if I could add more repositories to my ipkg configuration. I added the
new source "http://ipkg.nslu2-linux.org/feeds/unslung/cross/" into my ipkg
configuration directory, did an ipkg update and then ddclient appeared in my
ipkg list. I did an ipkg install ddclient, and it worked: ddclient was installed
into /opt/sbin, and also perl was downloaded...

... but it doesn't work. I configured ddclient in /opt/etc/ddclient.conf, but
when i start ddclient from command line, there are some error in compiling perl
script. Am I doing the right thing? In fact any SlugOS/BE package ends with
-armv5teb, while unslung packages ends with -armeb. Are those architectures
compatible? Is there any other option to set up?

Thanks