**SOLVED** Sheevaplug out the box won't boot, gets stuck

[tommed]

Hi Guys,

1. Got my NewIT Sheevaplug out of the box
2. Plugged the SD card in
3. Plugged it into my Windows Vista laptop via miniUSB, and ethernet port into my home router (DHCP enabled)
4. Powered on the plug
5. Installed the 2 drivers at the download site (Windows TerraTermUSBDriver)
6. Powered down the plug
7. Launched PuTTY, set the COM6 (the USB serial port), switched off hardware flow control, set baudrate to 115200
8. Powered up the plug
9. Clicked open on PuTTY

Got:

SDHC found. Card desciption is:
Manufacturer:       0x1b, OEM "SM"
Product name:       "00000", revision 1.0
Serial number:      2375
Manufacturing date: 6/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.
Linux version 2.6.32.7 (newit@gemini) (gcc version 4.4.1 (Sourcery G++ Lite 2009q3-68) ) #5 PREEMPT Wed Feb 10 21:09:39 GMT 2010
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Marvell SheevaPlug Reference Board
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttyS0,115200 root=/dev/mmcblk0p2 rootdelay=5
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 256MB 256MB = 512MB total
Memory: 513152KB available (5104K code, 1034K data, 140K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:114
Console: colour dummy device 80x30
Calibrating delay loop... 1058.40 BogoMIPS (lpj=5292032)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Kirkwood: MV88F6281-A1, TCLK=200000000.
Feroceon L2: Enabling L2
Feroceon L2: Cache support initialised.
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: US
   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
   (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
   (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
   (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
   (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
   (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
   (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
cfg80211: Calling CRDA for country: US
Switching to clocksource orion_clocksource
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
JFS: nTxBlock = 4010, nTxLock = 32083
msgmni has been set to 1002
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
sata_mv sata_mv.0: version 1.28

Then nothing (left it for 30 mins). PuTTY doesn't become inactive (offline) it just doesn't do anything else.
I checked the logs on my router, but no request for an IP address or anything. Debian (Squeeze) simply isn't booting.



Anyone know what's going on..? I'm new to this, so please be gentle!

[peter a]

This is what comes after , so would think it`s some think to do with the esata controller.

sata_mv sata_mv.0: slots 32 ports 2
scsi0 : sata_mv
scsi1 : sata_mv
ata1: SATA max UDMA/133 irq 21
ata2: SATA max UDMA/133 irq 21
NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 667 at 0x000005360000
Creating 3 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000500000 : "uImage"
0x000000500000-0x000020000000 : "root"
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address 00:50:43:01:52:80
libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
mice: PS/2 mouse device common for all mice
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
i2c /dev entries driver
cpuidle: using governor ladder
cpuidle: using governor menu
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
Registered led device: plug:green:health
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
ata1: SATA link down (SStatus 0 SControl F300)
mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
Gating clock of unused units
before: 0x00dfc3dd
 after: 0x00c7c1d9
rtc-mv rtc-mv: setting system clock to 2010-12-20 19:12:24 UTC (1292872344)
Waiting 10sec before mounting root device...
usb 1-1: new high speed USB device using orion-ehci and address 2
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 7 ports detected
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
usb 1-1.3: new full speed USB device using orion-ehci and address 3
ata2.00: ATA-7: SAMSUNG HD154UI, 1AG01118, max UDMA7
ata2.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata2.00: configured for UDMA/133
scsi 1:0:0:0: Direct-Access     ATA      SAMSUNG HD154UI  1AG0 PQ: 0 ANSI: 5
sd 1:0:0:0: [sda] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
sd 1:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3 sda4
sd 1:0:0:0: [sda] Attached SCSI disk


etc etc etc

[tommed]

Thanks peter,
are you suggesting the plug is faulty? Or could this be a software problem?

[peter a]

Either  !!!!!
But, the only one you can do something about is software.
If it a multi boot plug I would let it boot from NAND "and or" make a new SD card.

[tommed]

Ok thanks; can you please send me a link to a guide as to how to do this (and links to the uimage and debian system) please, as there was no cd or manual provided with the plug.

[NewIT_James]

Hi,

Looks rather like it's getting the kernel from the Nand and Rootfs from the SD card.

Does it boot ok without the SD card in?

NewIT Technical

[tommed]

Hi,

Looks rather like it's getting the kernel from the Nand and Rootfs from the SD card.

Does it boot ok without the SD card in?

NewIT Technical

Hi, yes it does! Great sign!!! So how can I get it booting now with the sd card? Do I need to change the boot opts? Can you provide some instructions please?

[NewIT_Marcus]

Looks to me like you're trying to boot a non-eSATA plug with an eSATA SD card.

If I'm wrong, and you have an eSATA Sheevaplug, perhaps there is a problem with the eSATA port.

But you didn't state whether you have an eSATA plug or not.

[tommed]

No it isn't an eSata plug.
the sdcard came with the plug and I havent done anything but plug it in and turn it on

[NewIT_Marcus]

No it isn't an eSata plug.

But your SD card tries to execute eSATA checks.

You have an SD card that is designed for an eSATA plug. Download a non-eSATA image here

[tommed]

Can you please confirm the dd command for writing the .img file please?

dd if=transcend-8G-8...-NewIT-v1.4-debian-squeeze.img of=/dev/sda bs=512 count=1

does that look correct?

[NewIT_Marcus]

Can you please confirm the dd command for writing the .img file please?

dd if=transcend-8G-8...-NewIT-v1.4-debian-squeeze.img of=/dev/sda bs=512 count=1

does that look correct?

No. You will write it to an SD card, so the output is /dev/mmcblk0. And you want to copy all of it, not just part.

dd if=/path/to/image-file.img of=/dev/mmcblk0 bs=1M

[peter a]

Well I was right that it can`t find the esata controller !!!!

So that`s why you have to make a esata and non-esata images !!!

[tommed]

Doh! Thanks, nearly wiped the HD on my laptop then?! Thanks guys!
Quite right peter! Someone must have popped the wrong SD card in my box!!

[tommed]

Brill! That image boots perfectly, many thanks to all!