GSHumphreys wrote:
> I love my slug, but it has started living up to its name, it takes over
> an hour to boot..... when it has finished it works fine until the next
> reboot. This takes more than an hour too.

I sometimes have a similar problem. When I power on the slug, it
usually boots up normally, but sometimes it seems to get stuck in the
bootloader. When I recognize that the slug did not boot properly
(cannot reach it after a few minutes) I usually connect to the serial
console, and if I type enter, the boot timeout appears, counts down
some seconds, and then boots up properly.

My machine is de-underclocked, has a auto-power-on with attiny13, and
a serial console using an old siemens mobile phone cable. I don't know
if the bootloader gets stuck because the serial console sent some
garbage that caused the bootloader to stop and wait for input. Does
anyone have an idea?

@GSHumphrey: Maybe your filesystem is bad and requires a filesystem
check at bootup? That would explain the delay. Is there heavy disk
activity during boot-up? Did you install many services/daemons that
use too much memory? That would cause the slug to swap, which could be
incredibly slow.

Thomas

Your serial port is getting interference and stopping the boot.  See the wiki
page for ideas about how to fix this (it needs a resistor added).
-- Rod

-----Original Message-----
From: Thomas Boehne <tobox@...>
Date: Thursday, Feb 1, 2007 7:01 pm
Subject: Re: [nslu2-linux] 1+ hour boot up

GSHumphreys wrote:
  I love my slug, but it has started living up to its name, it takes over
  an hour to boot..... when it has finished it works fine until the next
  reboot. This takes more than an hour too.

I sometimes have a similar problem. When I power on the slug, it
usually boots up normally, but sometimes it seems to get stuck in the
bootloader. When I recognize that the slug did not boot properly
(cannot reach it after a few minutes) I usually connect to the serial console,
and if I type enter, the boot timeout appears, counts down
some seconds, and then boots up properly.

My machine is de-underclocked, has a auto-power-on with attiny13, and a serial
console using an old siemens mobile phone cable. I don't know if the bootloader
gets stuck because the serial console sent some
garbage that caused the bootloader to stop and wait for input. Does
anyone have an idea?

@GSHumphrey: Maybe your filesystem is bad and requires a filesystem check at
bootup? That would explain the delay. Is there heavy disk
activity during boot-up? Did you install many services/daemons that
use too much memory? That would cause the slug to swap, which could be
incredibly slow.

Thomas



Yahoo! Groups Links

On Thu, Feb 01, 2007 at 12:31:42AM -0000, swissreporter wrote:
> ntfs on the disk, which i tried to symlink to a www-dir on ext3-
> partition on HDD2.

The ntfs driver doesn't support chown. There is only a mount time
option to set the owner for all files at mount time.

--
marceln

On Thu, 2007-02-01 at 00:19 +0000, swissreporter wrote:

> I would, however, like to access the system partition on HD2
> (unslung), which I can see if I open "my Network" in Win XP - but
> can't access whatever user/PW-comibnation I use.

You need a account which is in the administrator list of the slugs
administrator list.

The normal "admin" account should work.

--
marceln

On Thu, 2007-02-01 at 00:24 +0000, swissreporter wrote:

> However, I just don't get the "mount -o bind" to write-protect this
> directory.
>

>From the manpage:
        Note that the filesystem mount options will remain the same as
        those on the  original  mount  point,  and  cannot  be changed by
        passing the -o option along with --bind/--rbind.


> What am I doing wrong?

Trying something that can't work.

--
marceln

This morning I have realized that 2.6.18-4 finally made it into unstable
in Debian. All the problems that I used to have with 2.6.18-3 seem to be
gone, including the endianess problems with tcpdump. So if you are having
trouble with stalling network connections, capturing packets or network
timeouts, I suggest you upgrade to the new kernel.

Greetings,
Thomas

Thomas Böhne wrote:
> This morning I have realized that 2.6.18-4 finally made it into unstable
> in Debian. All the problems that I used to have with 2.6.18-3 seem to be
> gone, including the endianess problems with tcpdump. So if you are having
> trouble with stalling network connections, capturing packets or network
> timeouts, I suggest you upgrade to the new kernel.

And there lies the reason why we chose to go early with the open source
driver - if there are problems, then they get fixed :-)

-- Rod

What is the best way to install the new kernel?  Where can I get it?
Can it be done with apt-get?

--Tom


Thomas Böhne wrote:
>
>
> This morning I have realized that 2.6.18-4 finally made it into unstable
> in Debian. All the problems that I used to have with 2.6.18-3 seem to be
> gone, including the endianess problems with tcpdump. So if you are having
> trouble with stalling network connections, capturing packets or network
> timeouts, I suggest you upgrade to the new kernel.
>
> Greetings,
> Thomas
>
>

Hi,
    Just out of curiosity, has anyone managed to set up a bootable RAIDed root
filing system on OpenDebianSlug (or OpenSlug, which IIRC is used to boot ODS)?

    I guess what I need to do is modify /initrd/linuxrc to start up the RAID,
then pivot root to /dev/md1 (or whatever), but it would be nice if someone
who's already done this could explain how they did it, seeing as the wiki only
seems to cover Unslung.

    Would I be better off reflashing to Debian-arm proper (instead of
OpenDebianSlug, aka debian-armeb) and then reconfiguring everything on the new
drive? I guess the hard part is going to be moving the Samba PDC config, SMB
IDs and user accounts over without breaking anything...

    Has anyone solved the "RAID marked as dirty" issue reported on the wiki -
the one where if you power down the 'slug, the RAID rootfs is not unmounted
and thus marked as 'dirty', forcing md to resync it (copy from drive 0 to
drive 1) on the next cold boot and crippling the RAID until the resync
completes?

    Is it possible to RAID the swap too? I was thinking about having a RAID0'ed
swap partition (which provides speed but not redundancy), and a RAID1 for data
storage (which offers redundancy but not necessarily speed).

Thanks.
--
Phil.                         |  (\_/)  This is Bunny. Copy and paste Bunny
ygroups@...         | (='.'=) into your signature to help him gain
http://www.philpem.me.uk/     | (")_(") world domination.

* Tom Curran <narrucmot@...> [2007-02-01 19:09]:
> What is the best way to install the new kernel?  Where can I get it?
> Can it be done with apt-get?

You could do:

wget
http://ftp.uk.debian.org/debian/pool/main/l/linux-2.6/linux-image-2.6.18-4-ixp4x\
x_2.6.18.dfsg.1-9_arm.deb
sudo dpkg -i linux-image-2.6.18-4-ixp4xx_2.6.18.dfsg.1-9_arm.deb

--
Martin Michlmayr
http://www.cyrius.com/

THX, marceln. It doesn't . I get: "Multiple Connections to a server
or shared ressource by the same user, using more than one user name,
are not allowed. Disconnect all previous connections to the server
  ... and try again".

I did. still the same.


--- In nslu2-linux@yahoogroups.com, Marcel Nijenhof <nslu2@...> wrote:
>
> On Thu, 2007-02-01 at 00:19 +0000, swissreporter wrote:
>
> > I would, however, like to access the system partition on HD2
> > (unslung), which I can see if I open "my Network" in Win XP - but
> > can't access whatever user/PW-comibnation I use.
>
> You need a account which is in the administrator list of the slugs
> administrator list.
>
> The normal "admin" account should work.
>
> --
> marceln
>

I have had problems with power when plugging a disk into a running
slug. It appears that the startup current causes the voltage to drop
enough to 'glitch' the it. A way around this is to power the disk
externally for the unslung(ing?) process. Once the system is working,
you can remove the external power. Also, when running the disk powered
from the slug, the power surge is at startup and does not cause a
later problem.

sdm485

--- In nslu2-linux@yahoogroups.com, David Walstra <walstrad@...> wrote:
>
> Hi,
>
> I tried, but unfortunately it didn't work.
>
> I also tried this:
>
> ---
> boot the NSLU2 without a disk
>
> login as root (root/uNSLUng if you use the standard password)
> check if there are two processes running with the name USB_Detect
> if USB_Detect is running this will probably not help. If you
encounter that and find a solution, please mention it here.
> if not, go to /var/run
> in this dir there is a file called usb_det.pid; it probably has
an older date than the other files in the dir
> remove this file. do the same in /var.state/run/ if it has a
usb_det.pid
> reboot
> ---
>
> Indeed, USB_Detect was not running and it is now, each time I
reboot with no disk attached.
> But at the very moment I plugin a new (unformatted) disk, the slug
hangs. The leds go flashing and it doesn't respond to requests to the
internal webserver anymore. Also, my telnet session is killed at that
moment.
>
> I think the only thing I can do now, is reflash and hope that is
isn't a hardware issue...
>
> Shall I try the original Linksys firmware or maybe try unslung 5.5
again?
>
> Kind regards!
>
> Marcel Nijenhof <nslu2@...> wrote:
> Hi,
>
> >
> >
> > Well, maybe you read my previous message. In the meanwhile, I tried
> > backing up my pendrive. I now have two image files that I think are
> > fine.
>
> You have to know for sure that they are fine.
>
> > When I boot Knoppix with the pen drive attached, Knoppix sees
> > only two partitions. However, When I insert it under Windows (write
> > protection enabled, just to be sure), the disk manager sees three
> > partitions. I have not been able to backup the third partition (which
> > is 62 Mb in size. the first one is 312 Mb and the second one is 125
> > Mb). Is this a problem?
>
> No.
>
> The third partition is the swap and doesn't contain information that
> is interesting to save.
>
> > I asked about how to partition the new pen drive I bought. I suddenly
> > recalled that I just let the web interface of the slug format the old
> > pen drive when I used it for the first time. So I thought that when
> > I'd do the same with the new pen drive (which is also 512 Mb in
> > size), the slug will use the same partition sizes. However, here
> > comes the next problem: I can only boot the slug when I have no
> > devices attached.
>
> Please remove the file "/.sd<a|b>root" from the internal flash
> first.
>
> --
> marceln
>
>
>
>
>
>
> ---------------------------------
> Now that's room service! Choose from over 150,000 hotels
> in 45,000 destinations on Yahoo! Travel to find your fit.
>

The Daylight Saving TIme rules have changed and this year in the US (for the
most part) DST will change on March 11. Many OSes as well as firmware devices
will be effected by this change. Are there any updates for the NSLU2 regarding
this?

Doug



________________________________________________________________________________\
____
Have a burning question?
Go to www.Answers.yahoo.com and get answers from real people who know.

Thank you!  That was about 10 times and easy and painless as I thought
it would be!

Martin Michlmayr wrote:
>
>
> * Tom Curran <narrucmot@... <mailto:narrucmot%40gmail.com>>
> [2007-02-01 19:09]:
>  > What is the best way to install the new kernel? Where can I get it?
>  > Can it be done with apt-get?
>
> You could do:
>
> wget
>
http://ftp.uk.debian.org/debian/pool/main/l/linux-2.6/linux-image-2.6.18-4-ixp4x\
x_2.6.18.dfsg.1-9_arm.deb
>
<http://ftp.uk.debian.org/debian/pool/main/l/linux-2.6/linux-image-2.6.18-4-ixp4\
xx_2.6.18.dfsg.1-9_arm.deb>
> sudo dpkg -i linux-image-2.6.18-4-ixp4xx_2.6.18.dfsg.1-9_arm.deb
>
> --
> Martin Michlmayr
> http://www.cyrius.com/ <http://www.cyrius.com/>
>
>

On Fri, 2007-02-02 at 10:21 +0000, swissreporter wrote:
> THX, marceln. It doesn't . I get: "Multiple Connections to a server
> or shared ressource by the same user, using more than one user name,
> are not allowed. Disconnect all previous connections to the server
>  ... and try again".

This seems a error on the client side.

>
> I did. still the same.

Did you really check that all the connections are dropped (including
the connection to the ipc service). Please check this with the
net command.

--
marceln

I am running debian sid, installed about a year ago (uptime 329 days!).

To install the latest timezone data, this seems to have done the trick:
# apt-get update
# apt-get install tzdata

Cheers,
Steve

On 03/02/2007, at 5:29 AM, Brian Wood wrote:

>
>
> On Feb 2, 2007, at 9:58 AM, Mr Doug - wrote:
>
>> The Daylight Saving TIme rules have changed and this year in the
>> US (for the
>> most part) DST will change on March 11. Many OSes as well as
>> firmware devices
>> will be effected by this change. Are there any updates for the
>> NSLU2 regarding
>> this?
>
>
>>
>
>
> You didn't mention what firmware you were running, but I can give
> you some general info. I'm running Debian on a test slug and have
> discovered the following:
>
> The first thing to do is figure out if your tzdata is up to date, run:
>
> date --date="Mar 11 15:00:00 UTC 2007"
>
> Your system will respond with what it thinks the date/time should
> be then. If the response indicates daylight savings time (ie: EDT,
> CDT, MDT etc.) then your timezone data is up to date and reflects
> the latest screwing around by the US government.
>
> If the response is a standard time indication (EST, CST, MST etc.)
> then your timezone data needs to be updated to account for the
> recent changes, by updating your "tzdata" or whatever your
> particular system is using to determine the time offset from GMT
> (UCT). For OpenSlug this is /usr/share/zoneinfo/America/<city
> name>. It's the "tzdata" for Debian systems.
>
> I'm not sure how UnSlung deals with this as I don't run it.
>
> Wish I could me more help but that's what I know at this point.
>
>
>
>
>
>

No Package by that name exists for the ipkg method under unslung.
Could one be created? Or is there another way to update for the unslung?

Doug

--- Steve Bennett <steveb+nslu2@...> wrote:

> I am running debian sid, installed about a year ago (uptime 329 days!).
>
> To install the latest timezone data, this seems to have done the trick:
> # apt-get update
> # apt-get install tzdata
>
> Cheers,
> Steve
>
> On 03/02/2007, at 5:29 AM, Brian Wood wrote:
>
> >
> >
> > On Feb 2, 2007, at 9:58 AM, Mr Doug - wrote:
> >
> >> The Daylight Saving TIme rules have changed and this year in the
> >> US (for the
> >> most part) DST will change on March 11. Many OSes as well as
> >> firmware devices
> >> will be effected by this change. Are there any updates for the
> >> NSLU2 regarding
> >> this?
> >
> >
> >>
> >
> >
> > You didn't mention what firmware you were running, but I can give
> > you some general info. I'm running Debian on a test slug and have
> > discovered the following:
> >
> > The first thing to do is figure out if your tzdata is up to date, run:
> >
> > date --date="Mar 11 15:00:00 UTC 2007"
> >
> > Your system will respond with what it thinks the date/time should
> > be then. If the response indicates daylight savings time (ie: EDT,
> > CDT, MDT etc.) then your timezone data is up to date and reflects
> > the latest screwing around by the US government.
> >
> > If the response is a standard time indication (EST, CST, MST etc.)
> > then your timezone data needs to be updated to account for the
> > recent changes, by updating your "tzdata" or whatever your
> > particular system is using to determine the time offset from GMT
> > (UCT). For OpenSlug this is /usr/share/zoneinfo/America/<city
> > name>. It's the "tzdata" for Debian systems.
> >
> > I'm not sure how UnSlung deals with this as I don't run it.
> >
> > Wish I could me more help but that's what I know at this point.
> >
> >
> >
> >
> >
> >
>
>




________________________________________________________________________________\
____
Need a quick answer? Get one in minutes from people who know.
Ask your question on www.Answers.yahoo.com

Always something... and if it isn't technology or new functionality, it's
the government trying to "improve" our lives...

Off the top of my head I don't know where/how Unslung manages the DST change
data.  I'll add this as an item for investigation, and, um -- submit it to
one of the Unslung developers for further examination ;)

(I don't suppose anyone can claim a tax credit for the effort involved in
fixing something that's only broken because of the meddling of the US
Government, can they?  Good grief, you'd think the politicians have better
things to do than mess up the clocks for thousands upon thousands of
otherwise perfectly functional embedded devices and computers...)

**mutter*mutter**grumble*grumble**

Mike (mwester)

----- Original Message -----
From: "Mr Doug -" <dsc3507@...>
To: <nslu2-linux@yahoogroups.com>
Sent: Friday, February 02, 2007 10:20 PM
Subject: Re: [nslu2-linux] DST change


> No Package by that name exists for the ipkg method under unslung.
> Could one be created? Or is there another way to update for the unslung?
>
> Doug

Mike (mwester <mwester@...> writes:

> Off the top of my head I don't know where/how Unslung manages the DST change
> data.  I'll add this as an item for investigation, and, um -- submit it to
> one of the Unslung developers for further examination ;)
>

Unslung keeps the timezone data in /usr/zoneinfo/ That data is generated by the
firmware build process when it builds glibc-2.2.5 The zoneinfo data is endian
dependent so you can't just copy the files from another machine. If you have
built the unslung firmware source there is a copy of the zomeinfo compiler at

unslung/tmp/work/glibc-2.2.5-r5/build-armeb-linux/timezone/zic

which you could use to compile a fixed copy of the zone data.

Because this is part of the firmware it can't easily be fixed with ipkg.

Hi,
my slug is oopsing under heavy cpu load and different circumstances,
in a non repeatable way. I suspect of bad RAM, but can't find something
like memtest86 for ARM. Is there such a thing out there?

Thanks
Ramiro

Well this obviously is going to be a problem. There probably should be a WIKI
on the procedure or maybe a IPKG that would download the required files,
compiler, etc., do the compile, and install the resulting zone file. If that is
feasible.

This is another reason the pundits could use to put down Lionux. This obviously
is not as big a problem in Windows. Why does this have to be so buried in the
OS? It could be a simple text file that is read.

  On August 8, 2005, President George W. Bush signed the Energy Policy Act of
2005. This Act changed the time change dates for Daylight Saving Time in the
U.S. Beginning in 2007, DST will begin on the second Sunday in March and end
the first Sunday in November. The Secretary of Energy will report the impact of
this change to Congress. Congress retains the right to resume the 2005 Daylight
Saving Time schedule once the Department of Energy study is complet

Doug


--- Adam Baker <slug@...> wrote:

>
> Unslung keeps the timezone data in /usr/zoneinfo/ That data is generated by
> the
> firmware build process when it builds glibc-2.2.5 The zoneinfo data is endian
> dependent so you can't just copy the files from another machine. If you have
> built the unslung firmware source there is a copy of the zomeinfo compiler at
>
> unslung/tmp/work/glibc-2.2.5-r5/build-armeb-linux/timezone/zic
>
> which you could use to compile a fixed copy of the zone data.
>
> Because this is part of the firmware it can't easily be fixed with ipkg.
>
>




________________________________________________________________________________\
____
Yahoo! Music Unlimited
Access over 1 million songs.
http://music.yahoo.com/unlimited

Hi, I am using V2.3R63-uNSLUng-6.8-beta, unslung to a 160Gb drive in
port 1 (with another drive in port 2).

Unfortunately I had a problem with drive 1 and had to replace it with
one I got from a friend.  The new drive had the exact same drive
geometry as the old one and I had no problem in creating the partitions
using another Linux box and copying everything over.  However I didn't
realise until I got it, that this drive has a built-in USB hub - it has
a card reader attached, and this causes a problem when starting up the
slug because the drive is probably a different device than the old one
was.

OK, I thought, I can boot up without the drive attached, telnet in and
change the unslung device (will this work in principle?)

BUT, when I do that I can't log in - my password is always rejected.  I
thought the root password would go back to the default of uNSLUng, but
that doesn't work.  I may have changed it when I unslung the thing
originally but none of my likely passwords work either.

What's my best course of action?  Re-flash?

Thanks for any advice.

Dave

Hi Brian, thanks for replying.

> Couldn't you just remove the new drive from its hub-equipped case and
> put it in the old case?

I'm looking at the new drive now but there is no visible means of opening it.
I'm sure I can find a way though!  The old drive was an S-ATA and I bet the new
one is P-ATA though.

Dave
--