• Home
  • Help
  • Search
  • Login
  • Register
Pages: 1 2 [3] 4 5
Author Topic: Debian installer for SheevaPlug available now  (Read 35655 times)
tbm
Full Member
***

Karma: 7
Posts: 121



View Profile WWW
« Reply #30 on: October 28, 2009, 05:17:05 AM »

one more question: is it possible to update the kernel with an image from http://sheeva.with-linux.com/sheeva/? originally these are for the shipped ubuntu version.
or do you have a better location to get new kernels from?

No idea about that kernel but you can get newer Debian kernels from Debian unstable.
Logged

Billy
Newbie
*

Karma: 0
Posts: 12


View Profile
« Reply #31 on: October 28, 2009, 06:13:02 AM »

Hi jimjack,
have a lock to post 7, the installer also dies on installing busybox and there was also an
uncorrect date.
This was also my second Plug ant it was from NewIt too.
At least I sended it back due to the brocken USB.
Could it be that there is something wrong with those NewIt Plugs?

I'll get a new one in the next days and will test it then.
Logged

tbm
Full Member
***

Karma: 7
Posts: 121



View Profile WWW
« Reply #32 on: October 28, 2009, 08:40:58 AM »

jimjack: I'm really curious why you have such a bad time setting.  Also, the installer runs rdate to set the date, so I'm curious why that didn't work.  Can you look for rdate in /var/log/syslog?

And yes, you can run rdate from the installer shell.  Try:

Code:
rdate -o 123 -nvv 0.debian.pool.ntp.org

Does this work?
Logged

jimjack
Newbie
*

Karma: 0
Posts: 12


View Profile
« Reply #33 on: October 28, 2009, 11:25:33 AM »

No, thats not possible  Sad

Code:
# rdate -o 123 -nvv 0.debian.pool.ntp.org
.
rdate: Could not set time of day: Invalid argument

On my second SeevaPlug rdate is correctly running. Hmm...

And here the output from running rdate without arguments

Code:
~ # rdate -v 0.debian.pool.ntp.org
rdate: 0.debian.pool.ntp.org: Servname not supported for ai_socktype


Here is a snipped from /var/log/syslog for rdate

Code:
...
Dec  3 00:26:56 clock-setup: rdate: Could not set time of day: Invalid argument
...


And here a snippet from dmesg (booting the debian installer).

Code:
...
rtc-mv rtc-mv: setting system clock to 2068-01-08 06:52:46 UTC (3093231166)
...

I think there is something wrong with the rtc on the Marvel board.


The complete syslog is attached.


Steffen

* syslog.txt (614.99 KB - downloaded 403 times.)
« Last Edit: October 28, 2009, 11:51:03 AM by jimjack » Logged

mgillespie
Full Member
***

Karma: 7
Posts: 239



View Profile
« Reply #34 on: October 28, 2009, 03:48:57 PM »

one more question: is it possible to update the kernel with an image from http://sheeva.with-linux.com/sheeva/? originally these are for the shipped ubuntu version.
or do you have a better location to get new kernels from?

No idea about that kernel but you can get newer Debian kernels from Debian unstable.


I'm running sheeva.with-linux.com kernels.  But I used my "Alternative Debian Install Method".

http://plugcomputer.org/plugforum/index.php?topic=878.0
Logged

darkscout
Newbie
*

Karma: 0
Posts: 26


View Profile
« Reply #35 on: October 28, 2009, 10:21:02 PM »

No, thats not possible  Sad
Code:
# rdate -o 123 -nvv 0.debian.pool.ntp.org
.
rdate: Could not set time of day: Invalid argument

It's debian bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502336

I installed ntpdate and it worked fine.

I got it from emdebian, but it shouldn't matter.
http://www.emdebian.org/grip/search.php?package=ntpdate&arch=&distro=sid

Download the .deb. You also have to download ALL the debs of the dependencies. (And I did dependencies of dependencies to be safe.)

This has to be done at root (/)
wget the .deb file.
Then: ar vx [the deb file]
This will create a data.tar.gz.
Then: tar xzvf data.tar.gz
This will extract all of the files where they should be.
Delete the files that ar extracted and do it again for all the debs.

Then:
Code:
~ # ntpdate 0.debian.pool.ntp.org
29 Oct 04:59:43 ntpdate[18617]: step time server 72.52.190.26 offset 2043603676.731723 sec
~ # rdate -o 123 -nvv 0.debian.pool.ntp.org
.
.
Thu Oct 29 04:59:50 UTC 2009
rdate: adjust local clock by 0.015412 seconds
~ #

And.... drum roll....

It worked!

As more people start getting these with the date being farther and father in the past, I imagine that this will be a growing problem. Another thing that might work is an ntpdate in ubuntu before you attempt the debian install, if the rtc maintains over reboots (which it should) then this should work.

Just shy of 12:30 am. Who needs sleep when you have toys.
Logged

jimjack
Newbie
*

Karma: 0
Posts: 12


View Profile
« Reply #36 on: October 28, 2009, 11:32:18 PM »

Thanks darkscout for your help. I will try this the next days.

I think there is an problem with new SheevaPlugs. The rtc time is not correctly set and the
debian installer rdate fails.

Yesterday i used the old method to install debian on an SD card (Lenny 5.0). The SheevaPlug
works fine and the date/time ist now correct. At this point with the correct date/time on the
rtc I will try a new installation with the debian installer.

Steffen
Logged

darkscout
Newbie
*

Karma: 0
Posts: 26


View Profile
« Reply #37 on: October 29, 2009, 12:00:45 AM »

I wonder if our internal battery is dead. I just restarted installation and I got the same error. I'd think that once you set the rtc it should be 'permanent'.

But since I got to do it all over again might as well write a how to...

All that is required is ntpdate.
All of it's dependencies + libattr which is a dependency of libcap2.

This should copy and paste directly into a terminal window and continue the rest of the the install.

Code:
cd /
wget http://www.emdebian.org/grip/pool/main/n/ntp/ntpdate_4.2.4p6+dfsg-2em1_armel.deb
wget http://www.emdebian.org/grip/pool/main/n/netbase/netbase_4.37em1_all.deb
wget http://www.emdebian.org/grip/pool/main/e/eglibc/libc6_2.10.1-2em1_armel.deb
wget http://www.emdebian.org/grip/pool/main/libc/libcap2/libcap2_2.17-2em1_armel.deb
wget http://www.emdebian.org/grip/pool/main/o/openssl/libssl0.9.8_0.9.8k-5em1_armel.deb
wget http://www.emdebian.org/grip/pool/main/a/attr/libattr1_2.4.44-1em1_armel.deb
ar xv ntpdate_4.2.4p6+dfsg-2em1_armel.deb
tar -xzvf data.tar.gz
rm -rf control.tar.gz data.tar.gz debian-binary
ar xv netbase_4.37em1_all.deb
tar -xzvf data.tar.gz
rm -rf control.tar.gz data.tar.gz debian-binary
ar xv libc6_2.10.1-2em1_armel.deb
tar -xzvf data.tar.gz
rm -rf control.tar.gz data.tar.gz debian-binary
ar xv libcap2_2.17-2em1_armel.deb
tar -xzvf data.tar.gz
rm -rf control.tar.gz data.tar.gz debian-binary
ar xv libssl0.9.8_0.9.8k-5em1_armel.deb
tar -xzvf data.tar.gz
rm -rf control.tar.gz data.tar.gz debian-binary
ar xv libattr1_2.4.44-1em1_armel.deb
tar -xzvf data.tar.gz
rm -rf control.tar.gz data.tar.gz debian-binary
/usr/sbin/ntpdate
/usr/sbin/ntpdate 0.debian.pool.ntp.org
rdate -o 123 -nvv 0.debian.pool.ntp.org
exit
Logged

jimjack
Newbie
*

Karma: 0
Posts: 12


View Profile
« Reply #38 on: October 29, 2009, 12:20:27 AM »

You are right, I think also the battery is dead. There is an warrenty sticker on the NewIt SheevaPlug.
I cannot look inside to check and change the battery without loosing warrenty.

Thats not an big problme for me. The SheevaPlugs hangs on the network an when the installation is
okay the SheevaPlug can get the right date/time on each start.

Thanks for your code. I will try this and give an feedback.

Steffen
Logged

darkscout
Newbie
*

Karma: 0
Posts: 26


View Profile
« Reply #39 on: October 29, 2009, 12:56:58 AM »

You are right, I think also the battery is dead. There is an warrenty sticker on the NewIt SheevaPlug.
I cannot look inside to check and change the battery without losing warrenty.

Indeed, I just want to know what else is kept alive by that battery. I wish there was some definitive way. Set X = 5 before, pull power. See if X is still 5.
[/quote]

Ok, Now I'm locking up here:
Code:
  lqqqqqqqqqqqqqqqqqqqqqu Finishing the installation tqqqqqqqqqqqqqqqqqqqqqqk
  x                                                                         x
  x                                   22%                                   x
  x                                                                         x
  x Setting users and passwords...                                          x
  x                                                                         x
  mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj

Anyone have any idea? Or any idea how to to get back to syslog so I can see what is going on?
Logged

tbm
Full Member
***

Karma: 7
Posts: 121



View Profile WWW
« Reply #40 on: October 29, 2009, 09:47:10 AM »

Can someone with the time problem please start the installer and do the following:

Code:
wget http://ftp.uk.debian.org/debian/pool/main/s/strace/strace-udeb_4.5.17+cvs080723-2_armel.udeb
udpkg -i strace-udeb_4.5.17+cvs080723-2_armel.udeb
strace rdate -o 123 -nvv 0.debian.pool.ntp.org
Logged

tbm
Full Member
***

Karma: 7
Posts: 121



View Profile WWW
« Reply #41 on: October 29, 2009, 11:55:22 AM »

Never mind, I got the info I need.
Logged

darkscout
Newbie
*

Karma: 0
Posts: 26


View Profile
« Reply #42 on: October 29, 2009, 04:16:41 PM »

So I installed coreutils just to see what date my plug thought it was:

Fri Jan 26 03:29:08 UTC 1945

-

But now I'm wondering if my hardware clock is even installed:

~ # /sbin/hwclock --show
The Hardware Clock registers contain values that are either invalid (e.g. 50th day of month) or beyond the range we can handle (e.g. Year 2095).


Someone that doesn't get this error, could you please install util-linux and run 'sudo hwclock --show'

Edit: Buried somewhere I found that supposedly the HW clock can't be read until it's written to once (makes sense). So the FIRST thing anyone should do after they get ssh running and login for the first time is a 'hwclock -w'. That should fix almost all of the problems we're seeing.

I still can't get the installer to work completely. It likes to hang in random spots. Before it was the 22% while setting up users, now it was setting up the kernel.

I did the alternative Debian Install method and I'm up and running.
« Last Edit: October 30, 2009, 07:17:39 AM by darkscout » Logged

Billy
Newbie
*

Karma: 0
Posts: 12


View Profile
« Reply #43 on: October 30, 2009, 08:14:53 AM »

Today I got a replaced new Plug from NewIT.
And again the same issue, uncorrect date and time!
Thats why I installed firstly Ubuntu to my 4GB SD-Card with sheevaplug-installer-v1.0 and setup Date with ntpdate pool.ntp.org and hwclock --systohc.
Afterwards I started the Debian queeze installation with the debian installer according
http://www.cyrius.com/debian/kirkwood/sheevaplug/install.html

And as expected, the installer was running perfectly   ! Smiley

There was only the known problem that sheeva was not booting from power on.
I solved this by inserting a second mmcinit in -->
setenv bootcmd_mmc 'mmcinit; mmcinit; ext2load mmc 0 0x0800000 /uInitrd; ext2load mmc 0 0x400000 /uImage'

Thanks all for your help and good ideas!
« Last Edit: October 30, 2009, 09:09:08 AM by Billy » Logged

j0n3s
Newbie
*

Karma: 2
Posts: 13


View Profile
« Reply #44 on: November 01, 2009, 04:47:11 AM »

You can now use the Debian installer to install Debian on the Marvell SheevaPlug.  This routine will install Debian testing (squeeze), which is
currently under development.  The installer itself is also under development, so there may be problems from time to time but it should
generally work pretty well.  The Debian installer doesn't support installations to flash, but you can use it to install to a USB stick or disk as well as to an SD card.

Instructions: http://www.cyrius.com/debian/kirkwood/sheevaplug/


Everything run smoothly on NewIT device with SD card.
Thanks.
Logged

Pages: 1 2 [3] 4 5
Print
Jump to: