The alternative Debian install method.

[hungarianhc]

There is a issue with the speed that the system boots from nand (too fast), and the system is up and ready before your HDD has spun up.

I have this issue, and used the wait4usbdisks tip which works perfectly.

http://plugcomputer.org/plugforum/index.php?topic=485.msg2858#msg2858

I don't think it's distro specific, it seems to affect all Linux distros, including the stock Ubuntu one.  I am tempted to include it in the build process.

As for the Lenny problem, sorry, I don't know, I only have the one plug, running Squeeze, and can't test the Lenny ones.  I have to rely on the fact it's Debian Stable, that it works...

Fantastic! Once i'm more awake, I'll go ahead and give this a shot. If my fstab issues can be fixed, then I'll be a happy camper. I am guessing this will work. In the other thread that I linked to, I noticed that if I did "mount -a" after bootup, it would mount everything in /etc/fstab so it's quite believable that it just got to the file before things were ready. Thanks, much!

[portnawak]

Tried to download the archive from mediafire several times today, from different computers, the archive (http://www.mediafire.com/download.php?g2dmzzcmy0z) seems to be corrupted, am I the only one with the problem ?

[mgillespie]

Use these ones:

http://www.mediafire.com/?mxzzmymzyjk  (Lenny)

Or

http://www.mediafire.com/?z2ljmnukmdc (Squeeze)

Or use the script to build your own (and more uptodate) rootfs.

[portnawak]

Use these ones:

http://www.mediafire.com/?z2ljmnukmdc (Squeeze)

Thanks a lot for your prompt response, it worked like a charm, now running Squeeze apt-get updated/upgraded with the latest kernel from sheeva.with-linux.com

Still have to get eSata PM support in this kernel ... don't know yet where to start, but I'll try to learn cross-compilation :-D

Thanks again.

[Herman]

The delay can be accomplished by adding the rootdelay parm:
setenv bootargs_console console=ttyS0,115200 rootdelay=10

A message shows up when Squeeze boot stalls at attaching the USB hdd. You have to wait several minutes for it to appear. The messages recommends some possible causes and parms to change. The message was not very clear where they were to be added or the bootargs syntax.

Tried both warm boot and cold boot with no problem after adding the parm.

Herman

[truehl]

Hi,
I've dowloaded the squeeze prebuild image and use this with the sheevaplug installer. So far everything works fine. After the process is finished, the plug boots an shows :

Code:

| |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (Nov  4 2009 - 12:58:36) Marvell version: 3.4.23

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0
SDHC found. Card desciption is:
Manufacturer:       0x03, OEM "SD"
Product name:       "SD04G", revision 8.0
Serial number:      1886447911
Manufacturing date: 4/2009
CRC:                0x00, b0 = 0

** Invalid partition type "" (expect "U-Boot")
## Booting image at 00800000 ...
Bad Magic Number
Marvell>>

Witch boot varibles do I need to boot from sd-card?

Greetings,
Thomas

[truehl]

Hi,
the readme file states:"At the end of the build process (which should only take about 10 minutes), you will be left with a rootfs.tar.gz that can be used to overwrite the one in the sheeva installer 1.0 download." I've ran the script an was left with a folder "Debian" and not with a "rootfs.tar.gz". Did I get something wrong?

Please help
Thx, Thomas

[meldini@ngi.it]

Hi, this is my first message.
i don't understand this passage:
"At the end of the build process (which should only take about 10 minutes), you will be left with a rootfs.tar.gz that can be used to overwrite the one in the sheeva installer 1.0 download."
I have downloaded a prebuilt rootfs.tar.gz
I have downloaded sheevaplug-installer-v1.0.tar.gz
and now?
Sorry for my english 

[mgillespie]

Hi, this is my first message.
i don't understand this passage:
"At the end of the build process (which should only take about 10 minutes), you will be left with a rootfs.tar.gz that can be used to overwrite the one in the sheeva installer 1.0 download."
I have downloaded a prebuilt rootfs.tar.gz
I have downloaded sheevaplug-installer-v1.0.tar.gz
and now?
Sorry for my english 

You don't need to use the "build process", this is if you want to use the script to build your OWN rootfs.tar.gz  You have opted to download a pre-built one.

You need to untar the sheevaplug-installer-v1.0.tar.gz, replace the Ubuntu rootfs.tar.gz with the debian one you have download.  Then follow the instructions for SheevaInstaller.

[Deviant0ne]

This looks great; I've created an image and plan on trying Debian tonight. One question though: which kernel will this new rootfs be using? The kernel shipped in the SheevaPlug installer? Is it possible to update the kernel using the Ubuntu update method (./README... etc.)? Thanks again for this tool!

[mgillespie]

The kernel that gets loaded is the one in the SheevaInster 1.0 (2.6.30 I recall).  But yes, once you are up and running, you can simply update it to the latest from sheeva-with-linux.

This is exactly what I do, it works without issue.

[Deviant0ne]

Fantastic! Thank you very much

[Deviant0ne]

I tried installing a new kernel and the script can't find mtd0 to write the kernel. I am assuming I have to alter the script to make it write to the correct location, but I don't know said correct location... Any ideas?

[Deviant0ne]

Used --rootkernel instead of --nandkernel and got a little farther... Plug will boot but only sees the original kernel, not the updated one. I created a symlink to the new kernel, but still no dice. Ideas?

[Deviant0ne]

Your script worked beautifully. However, would you mind explaining how you went about updating your kernel from the sheeva-with-linux website? As I mentioned, I tried using the ./README... --rootkernel option and creating a symlink to the new kernel, but to no avail. The plug boots, but when I do a uname -a, the plug still reads 2.6.30.2 instead of 2.6.32.9. Any advice you can provide would be greatly appreciated. Thank you in advance.