New IT forum Follow us on Twitter
21 May 2012, 04:00:29 pm *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: TonidoPlug2 - Now in stock!
 
   Home   SHOP Help Search Login Register  
Pages: [1]
  Print  
Author Topic: Preparing Debian squeeze SD card, won't boot. Wrong disk image?  (Read 950 times)
Zorael
Newbie
*
Posts: 3


« on: 16 April 2011, 01:50:08 pm »

I just received my black eSata Multiboot Sheevaplug which I ordered with an 8Gb SD card preinstalled with Ubuntu jaunty. After it dawned on me that jaunty support has ended, I now want to reflash the SD card (not the nand) with a squeeze image.

I found the NewIT disk images (assuming the eSata ones are also for multiboot plugs), but I'm unsure of which to pick. It's not apparent anywhere, and the only mention I could find on these forums were regarding to SD card sizes. The provided SD card was not a Transcend nor an Ultima, but an Integral. On a hunch I picked the "ultima-8G-NewIT-v1.2-debian-squeeze-eSATA" image. No problems encountered when dd'ing it onto the card.

But when I try to boot it, it doesn't go past loading the kernel.

Code:
         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (Jul 14 2009 - 06:46:57) Marvell version: 3.4.16

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

[...]

SDHC found. Card desciption is:
Manufacturer:       0x02, OEM "TM"
Product name:       "SD08G", revision 6.2
Serial number:      3250326552
Manufacturing date: 4/2010
CRC:                0x00, b0 = 0

2822228 bytes read
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.32.7
   Created:      2010-02-10  21:21:03 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2822164 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

<endless pause>

The Ubuntu jaunty installation that came prepared onto the card had the 2.6.36 kernel, and as listed in that output the one on the image is 2.6.32. Are the images available from the NewIT page outdated? Did I pick the wrong one?

Alternatively; my nand partition (which seems to be running squeeze and 2.6.36) still works. Can I just clone it onto the SD card?

Mounting the rootfs partition on my normal machine, the contents look fine.
Code:
Disk /dev/sdb: 8254 MB, 8254390272 bytes
4 heads, 16 sectors/track, 251904 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1         123        3928   83  Linux
/dev/sdb2             124      245632     7856288   83  Linux

printenv output is as follows, if at all relevant;
Code:
baudrate=115200
loads_echo=0
ipaddr=10.4.50.165
serverip=10.4.50.5
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)
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:herpderp
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=F0:AD:4E:herpderp
bootargs_console=console=ttyS0,115200
recover1=setenv mainlineLinux yes; setenv arcNumber 2678; 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
bootargs_root_nand=ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs
bootcmd_nand=setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root_nand); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
bootargs_root_mmc=root=/dev/mmcblk0p2 rootdelay=5
bootcmd_mmc=setenv bootargs $(bootargs_console) $(bootargs_root_mmc); mmcinit; ext2load mmc 0:1 0x800000 /uImage; bootm 0x00800000
real_bootcmd=run bootcmd_mmc; run bootcmd_nand
arcNumber=2678
filesize=37B8DF
bootcmd=run bootcmd_mmc; run bootcmd_nand
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

Environment size: 2230/131068 bytes

Help and pointers appreciated.
Logged
NewIT_Marcus
Administrator
Hero Member
*****
Posts: 960


« Reply #1 on: 16 April 2011, 03:28:43 pm »

Sorry, I forgot to move over the new images. I have done so now:

http://www.downloadsnewit.co.uk/SD-images/Sheevaplug/all/

The "all" images have a kernel that loads eSATA modules if arcNumber is 2678, but doesn't if arcNumber is 2097.  ie they are suitable for all Sheevaplugs. They also are more up-to-date in terms of package updates - the date that each image was updated is encoded in the image name.

You should be able to get your SD card running by changing arcNumber to 2097 - the kernel on the old images works for eSATA with arcNumber 2097, but probably barfs on your 2678. You could update just the kernel if you wish, or use a complete image from the directory above.
« Last Edit: 14 September 2011, 01:59:47 pm by NewIT_Tayler » Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.16 | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!