Problems with booting shevaplug / installing debian

[tylernt]

Your console= and bootargs= variables look munged. I suggest you make your console variable say simply

console=ttyS0,115200

I'm not entirely sure, but to fix your bootargs variable, I think it needs to look something like this instead:

bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw

The "mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)" section might possibly even need to be removed entirely.

[js4]

Thanks! I'll give it a shot.

[js4]

Tried it today - no luck 

[tylernt]

What does 'printenv' give you now?

[js4]

Marvell>> printenv
baudrate=115200
loads_echo=0
ipaddr=10.4.50.165
serverip=10.4.50.5
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethact=egiga0
bootargs_root=ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs
mtdpartitions=mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)
ethaddr=00:50:43:01:66:16
real_bootcmd=setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
bootargs_console=console=ttyS0,115200
recover1=setenv mainlineLinux yes; setenv arcNumber 2097; setenv bootcmd run recover2; saveenv; reset
recover2=run recover3; setenv bootcmd $(real_bootcmd); saveenv; setenv bootargs $(bootargs_console) $(mtdpartitions) root=/dev/ram0 rw ramdisk=0x01100000,8M install_type=nand; bootm 0x00800000 0x01100000
recover3=run recover4; nand erase clean 0x00100000 0x00400000; nand write.e 0x00800000 0x00100000 0x00400000
recover4=usb start; fatload usb 0 0x00800000 uImage; fatload usb 0 0x01100000 initrd
arcNumber=2097
filesize=32D62A
bootcmd=setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
console=ttyS0,115200
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=yes
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes
pcieTune=no


I changed console to what you suggested. I tried to change bootcmd to your suggestion, but it wouldn't load. I think I need the nand read.e part and for the mtdpartitions to be set to orion_nand instead of nand_mtd.

Below is what happened when I took out $(bootargs_root). It tried to load the kernel and then just a black screen:

Marvell>> setenv bootcmd setenv bootargs $(bootargs_console) $(mtdpartitions); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000

NAND read: device 0 offset 0x100000, size 0x400000

Reading data from 0x4ff800 -- 100% complete.
 4194304 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.30.2
   Created:      2009-07-23   1:53:36 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2620440 Bytes =  2.5 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

[marcus]

I'm having the same issue. My rootfs worked fine on the older models, but I got 12 new sheevaplugs and now I have this issue with al of them. I contacted globalscale about the issue and they said the CPU has changed. I'm thinking I need to use a differen't kernal now.

Do you have the problem still, and did you check your plugs to determine the cpu revision?

I have been working on flashing the new cpu versions and although I have made significant progress by creating a suitable kernel and tinkering with the installer process, I'm not quite there yet.

[Lemming]

I'm also seeing this problem. I'm trying to install Debian on my SheevaPlug, and everything works fine until I get to the installer - until the kernel image boots, basically. Any help resolving this would be greatly appreciated.

[Lemming]

I got this working on my machine, it seems to be a problem with terminal emulation. I downloaded a new terminal emulator (Zoc for OSX) and it works fine now. It seems that the installer emits some characters that screen doesn't like when it switches pages.

[guidol]

## Booting image at 00800000 ...
   Image Name:   Linux-2.6.30.2
   Created:      2009-07-23   1:53:36 UTC
Starting kernel ...
Uncompressing Linux... done, booting the kernel.

seems like a to be an to old Kernel...try >=2.6.32.2

[kjell]

I encountered this problem when installing Debian Squeeze. Switching terminal emulator did not solve it for me, I tried Zoc with different settings, xterm for both Mac OS X and Ubuntu and GTerm (on Ubuntu).

What did solve it however was resetting the terminal when the Debian installer started showing garbage, by selecting "send hard reset" from "shell" menu in Mac OS X's terminal.app. After this, it worked fine with no need to reattach the USB cable after each page refresh by installer. It's definitely possible to reset other terminal emulators as well.

[pablog]

I have just registered myself in this forum to let you know that I solved this same issue installing the 2.6.36.2 kernel instead of 2.6.30.2 (which was giving me this error).

I took it from http://sheeva.with-linux.com/sheeva