• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: Big problems trying to update my original Sheevaplug.  (Read 6647 times)
Full Member

Karma: 8
Posts: 239

View Profile
« on: January 12, 2012, 05:32:07 AM »

I had some problems with Debian, so I decided to wipe and start again, and whilst at it, load the new DENX u-boot.  I am installing to internal NAND for performance reasons.

After a whole evening wasted because ESIA was copying zero byte instimg and initrd...   Sorted that by copying the files manually, and I can get the provided Debian ESIA image loaded and it booting.

However, there is something badly wrong with it, as CXBikers kernel update scripts fail to work for numerous reasons.

I then used my Debian rootfs again using ESIA, and it loaded the old kernel that ships with it, but with the updated rootfs (after changing the MD5 checksum in the manifest).

CXBikers kernel then flashes correctly, however it does not boot, it hangs on "Uncompressing Linux... done, booting the kernel.".

Can someone take a look here at my uboot enviroment and see if it looks sensible?

Marvell>> reset
resetting ...

U-Boot 2011.12 (Jan 08 2012 - 21:53:47)
Marvell-Sheevaplug - eSATA - SD/MMC

SoC:   Kirkwood 88F6281_A0
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  512 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x100000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.2.0
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2911752 Bytes = 2.8 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Marvell>> printenv
app_summary=Debian Stable (Squeeze) ARM5 SheevaPlug Distribution
bootargs_root=ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs
bootcmd=setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
install_options=backup= url=Debian_Squeeze kernel=uImage rootfs=root.tar.gz modules=modules.tar.gz apptype= access=c2hlZXZhOnBsdWcK
real_bootcmd=setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
rec33=setenv bootargs $(bootargs_console) $(mtdpartitions) root=/dev/ram0 rw ramdisk=0x01100000,8M install_type=nand $(install_options); bootm 0x00800000 0x01100000
recover1=setenv mainlineLinux yes; setenv arcNumber 2097; setenv bootcmd run recover2; saveenv; reset
recover2=run recover3; setenv bootcmd $(real_bootcmd); saveenv; run rec33
recover3=run recover4
recover4=usb start; fatload usb 0 0x00800000 instImg; fatload usb 0 0x01100000 initrd
x_bootargs=console=ttyS0,115200 mtdparts=orion_nand:512k(uboot),4m@1m(kernel),507m@5m(rootfs) rw
x_bootargs_root=ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs
x_bootcmd_kernel=nand read 0x6400000 0x100000 0x400000
x_bootcmd_sata=ide reset;
x_bootcmd_usb=usb start;

Environment size: 1684/131068 bytes

Really keen to get this back online, as it's my mailserver amonst other things, and my ISP will soon start bouncing messages.

Full Member

Karma: 8
Posts: 167

View Profile WWW
« Reply #1 on: January 12, 2012, 06:59:17 AM »

The env looks OK to me. I had the same problem with 3.2
A wild guess try bikers 3.1.8 kernel instead.

Full Member

Karma: 8
Posts: 239

View Profile
« Reply #2 on: January 12, 2012, 09:45:58 AM »

I'll give it  ago in the next couple of hours.

What's interesting, I usually keep ontop of kernels, and the plug WAS running 3.2 totally fine until I started tinkering.  So if it's not happy now, it's something specific in what I have done, as it's CAPABLE of running 3.2.

Full Member

Karma: 8
Posts: 239

View Profile
« Reply #3 on: January 12, 2012, 12:02:18 PM »

3.1.8 brought things back to life!

Just as a sanity check, flashed 3.2 again from a fresh download, and it was borked again.  Flashed 3.1.8 and it was fine again...

Something REALLY fishy going on, as like I said before I decided to tinker, I did have 3.2 running on this same plug. (the only different I can think could be partition layout or the fact I was using an old Marvell uboot rather than the new uboot).

Either way, going to stay on 3.1.8 for the moment until someone smarter than me can work out what's wrong...

Pages: [1]
Jump to: