Linux Device Hacking - uBoot

Re: Booting Debian on Pogoplug Pro

tb0ne — Fri, 24 May 2013 05:38:52 -0400

Have just setup my pogo with shv's rootfs, also bumped into the resolv.conf problem.
It seems installing the resolvconf package fixed this!

Help! no connect to Pogoplug

bt165 — Wed, 22 May 2013 09:18:58 -0400

Hi!

I have a Pogoplug E02 with Debian runs from a Usbstick. This works great!
But without a Usb-Stick the Pogoplug becomes no IP from the Router.
I can´t connect to the Pogoplug?

My Question is , how can i repair this ?

Can anybody help me?

Thanks!
bt165

Re: How to revert to factory uboot of Goflex Net

bodhi — Fri, 17 May 2013 22:20:47 -0400

> # the next commands could brick the device if
> something is wrong
> cd /root
> flash_erase /dev/mtd0 0 4
> nandwrite /dev/mtd0 uboot-original-mtd0.kwb
> reboot

Yeah :) best to double check the size of this image.

Re: U-Boot w/ MMC/SD-card booting for Pogoplug Series 4

bodhi — Fri, 17 May 2013 17:26:40 -0400

nguyen Wrote:
-------------------------------------------------------
> Have anyone able to boot original Pogoplug Linux
> using this uBoot?

I never really try to do that. But it would be very doable. Just remember to save your orginal uBoot envs to a text file. And then later set them back to boot the correct mtdparts. Installing this uBoot image using Linux command only overwrites mtd0 (so all other mtd parts, where pogo OS is, will remain intact).

Re: U-Boot w/ MMC/SD-card booting for Pogoplug Series 4

halogen — Fri, 17 May 2013 15:58:30 -0400

I successfully attached serial and got ready for netconsole as well.

Even though I see the green light, I'm still experiencing network problem connecting over ssh. It seems like both static and dhcp doesn't work properly.

It's very similar to john3votas' thread on Booting DHCP issues OR sosuke's thread on PogoPlug Mobile SD Boot Troubles

Now I'm researching possible causes that I made a mistake. wish me luck.

How to revert to factory uboot of Goflex Net

shv — Thu, 16 May 2013 13:27:24 -0400

I want to rerevert to the factory uboot of Goflex Net. How can can I read the factory uboot back from flash rootfs partition and write it to flash? Is it necessary to change the uboot environment variables which were changed during installation of new uboot? I don't have any mtdblock devices in /dev.

I found out how to do that after Debian was booted from a USB Stick:

mknod /dev/mtdblock2 b 31 2
mount -t jffs2 -o ro /dev/mtdblock2 /mnt
cp /mnt/uboot-original-mtd0.kwb /root
umount /dev/mtdblock2
apt-get install mtd-utils

# the next commands could brick the device if something is wrong
cd /root
flash_erase /dev/mtd0 0 4
nandwrite /dev/mtd0 uboot-original-mtd0.kwb
reboot

#after reboot ssh-login shall be possible -> activate hbmgr
mount -o remount,rw / # remount rootfs writeable
vi /etc/init.d/rcS
#uncomment the line with "/etc/init.d/hbmgr.sh start"
reboot

Re: PogoPlug Mobile SD Boot Troubles

sosuke — Thu, 16 May 2013 05:58:39 -0400

Thanks Bodhi! I did the mmc stuff but that gave me the same output as letting it run through by itself, but.. adding rootfs stuff and setting a label was what I needed. It works now! Thanks!

Re: PogoPlug Mobile SD Boot Troubles

bodhi — Thu, 16 May 2013 01:20:07 -0400

sosuke,

You could execute uBoot envs in netconsole and see what happen. Execute this mmc boot command in 4 steps:

mmc_bootcmd=mmc init; mmc init; ext2load mmc 0:1 0x00800000 /boot/uImage; if ext2load mmc 0:1 0x01100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi

So stop uBoot at netconsole, and do these 4 commands consecutively. If you have get error with mmc_init, then execute it again to see if you get pass it. Post the errors here if you're not sure how to proceeed.

mmc_init
ext2load mmc 0:1 0x00800000 /boot/uImage
ext2load mmc 0:1 0x01100000 /boot/uInitrd
bootm 0x800000 0x1100000

Update:
I've just noticed that you don't have this in your envs:

usb_init=run usb_scan; setenv usb_root LABEL=rootfs

If you label your rootfs as rootfs, and then have usb_init set to use the label, then you won't need to worry about much. The Initrd will find your rootfs.

Re: iConnect not boots from Stick when DVB-C Stick plugged in

pr0j3ctx — Wed, 15 May 2013 03:05:19 -0400

Hello.

Thanks for this information. I will read the Post and look what I can do.

Greats
pr0

Re: iConnect not boots from Stick when DVB-C Stick plugged in

bodhi — Wed, 15 May 2013 03:02:40 -0400

pr0,

You're running stock uBoot, and this version is very limited in what you can do with uBoot envs. If you are comfortable with flashing new uBoot using a manual procedure (only recommended for more experienced users and with serial console for recovery purpose), then check out this thread, starting here:
http://forum.doozan.com/read.php?2,6624,6959#msg-6959
and instructions here:
http://forum.doozan.com/read.php?2,6624,9123#msg-9123

Newer uBoot will enable you to set the envs to scan and find the USB with rootfs, and hopefully not stuck at a USB device (I don't have this DVB-C stick so can not guarantee that it will handle that device correctly).

Re: PogoPlug Mobile SD Boot Troubles

sosuke — Tue, 14 May 2013 18:49:50 -0400

Thanks for the response bodhi.

That didn't work. I ran

setenv usb_rootfstype 'ext3'
saveenv

Didn't see anything for the SD card so I'm assuming it's the same. But honestly I don't think this would matter. I had my card formatted as ext2. Since you're doing a cp -a I wouldn't think the origins filetype would matter? Just to be sure I reformated as ext3 and recopied everything and still a no go. I also tried another SD card (also 4GB but different maker) and formatted that ext2. It does the same thing (tried it before changing rootfstype).

I would also say that ext2 is fine because it looks like it's loading uImage off disk (at least it says it did) so I would imagine at that point it can read the card? It just seems to be hanging when it actually loads the kernel and I have no clue how to debug that since it drops off my network so no more netconsole at that point.

I also tried a USB thumbdrive but that wouldn't load anything so I either need to try a different USB stick, I have something screwed up for USB drive, or I didn't make that drive correctly. It wouldn't even find uImage.

Any other ideas what might be wrong? Am I going to need a serial cable to debug this?

Update

I tried a different USB stick and this one works (ext2). So I can boot. So now it's trying to figure out what is wrong with the SD card side of things.

Update 2
Got done with work and had more time to play with this. As I said before I got it working with a USB stick (sandisk). I tried various things with my SD cards. Formatted as ext2. Formatted as ext3. Changed the fstab to mount mmcblk0p1 instead of root. Changed fstab to ext2. To ext3. Changed the env to ext2, and ext3. Probably other things I've already forgotten.

Finally I tried a microsd card in a USB reader. That works. So at this point I know I have a working (micro) SD card. So I put it into an SD card converter and tried to boot that. Doesn't work. Hangs at "Starting kernel...".

Does anyone have any ideas?

Thanks

Re: U-Boot w/ MMC/SD-card booting for Pogoplug Series 4

nguyen — Tue, 14 May 2013 13:59:41 -0400

Have anyone able to boot original Pogoplug Linux using this uBoot?

Re: iConnect not boots from Stick when DVB-C Stick plugged in

pr0j3ctx — Tue, 14 May 2013 06:13:27 -0400

Hello.

First the output of fw_printenv:

baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
usbstart=usb start
run_diag=yes
console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)
CASset=min
MALLOC_len=1
bootargs_root=root=/dev/nfs rw
bootargs_end=:::orion: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
eth1addr=00:50:43:5a:1a:1f
eth1mtu=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
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
iomega=123
nandEcc=1bit
ethprime=egiga0
ethact=egiga0
ipaddr=192.168.100.97
serverip=192.168.100.91
arcNumber=1682
uboot_start=0x0
uboot_size=0xc0000
env_start=0xa0000
env_size=0x20000
kernel_start=0x100000
kernel_size=0x300000
initrd_start=0x540000
initrd_size=0x300000
boot_start=0x980000
boot_size=0x1f400000
flash_load=run make_boot_args load1 load2 boot
load1=nand read.e 0x2000000 $(kernel_start) $(kernel_size)
load2=nand read.e 0x4500000 $(initrd_start) $(initrd_size)
boot=bootm 0x2000000 0x4500000
krn=run a b c
rd=run d e f
a=tftp 0x2000000 zImage
b=nand erase $(kernel_start) $(kernel_size)
c=nand write.e 0x2000000 $(kernel_start) $(kernel_size)
d=tftp 0x4500000 initrd
e=nand erase $(initrd_start) $(initrd_size)
f=nand write.e 0x4500000 $(initrd_start) $(initrd_size)
flashall=run krn rd
make_boot_args=setenv bootargs console=ttyS0,115200 mtdparts=orion_nand:;setenv bootargs $(bootargs)$(uboot_size)@$(uboot_start)(uboot),;setenv bootargs $(bootargs)$(env_size)@$(env_start)(env),;setenv bootargs $(bootargs)$(kernel_size)@$(kernel_start)(zImage),;setenv bootargs $(bootargs)$(initrd_size)@$(initrd_start)(initrd),;setenv bootargs $(bootargs)$(boot_size)@$(boot_start)(boot)
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
hddPowerCtrl=no
enaAutoRecovery=yes
pcieTune=no
ethaddr=00:D0:B8:11:F1:C9
make_bootsetenv=make_boot_args setenv bootargs console=ttyS0,115200 mtdparts=orion_nand:;setenv bootargs $(bootargs)$(uboot_size)@$(uboot_start)(uboot),;setenv bootargs $(bootargs)$(env_size)@$(env_start)(env),;setenv bootargs $(bootargs)$(kernel_size)@$(kernel_start)(zImage),;setenv bootargs $(bootargs)$(initrd_size)@$(initrd_start)(initrd),;setenv bootargs
bootargs=setenv bootargs console=ttyS0,115200
boot_starsetenv=boot_start 0x980000
boot_sizesetenv=boot_size 0x1f400000
MAPOWERENV=Ver. 1.1.27 English
usb_scan_1=setenv usb 0:1; setenv dev sda1
usb_scan_2=setenv usb 1:1; setenv dev sdb1
usb_scan_3=setenv usb 2:1; setenv dev sdc1
usb_scan_4=setenv usb 3:1; setenv dev sdd1
usb_scan_5=setenv usb 0:1; setenv dev sda2
usb_scan_6=setenv usb 1:1; setenv dev sdb2
usb_scan_7=setenv usb 2:1; setenv dev sdc2
usb_scan_8=setenv usb 3:1; setenv dev sdd2
bootcmd_usb_1=run usb_scan_1;run make_usb_bootargs;ext2load usb $(usb) 0x00800000 /boot/uImage;bootm 0x00800000
bootcmd_usb_2=run usb_scan_2;run make_usb_bootargs;ext2load usb $(usb) 0x00800000 /boot/uImage;bootm 0x00800000
bootcmd_usb_3=run usb_scan_3;run make_usb_bootargs;ext2load usb $(usb) 0x00800000 /boot/uImage;bootm 0x00800000
bootcmd_usb_4=run usb_scan_4;run make_usb_bootargs;ext2load usb $(usb) 0x00800000 /boot/uImage;bootm 0x00800000
bootcmd_usb_5=run usb_scan_5;run make_usb_bootargs;ext2load usb $(usb) 0x00800000 /uImage;bootm 0x00800000
bootcmd_usb_6=run usb_scan_6;run make_usb_bootargs;ext2load usb $(usb) 0x00800000 /uImage;bootm 0x00800000
bootcmd_usb_7=run usb_scan_7;run make_usb_bootargs;ext2load usb $(usb) 0x00800000 /uImage;bootm 0x00800000
bootcmd_usb_8=run usb_scan_8;run make_usb_bootargs;ext2load usb $(usb) 0x00800000 /uImage;bootm 0x00800000
make_usb_bootargs=run make_boot_args; setenv bootargs $(bootargs) root=/dev/$(dev) rootdelay=10
bootcmd_usb=usb stop;usb start;run bootcmd_usb_1;run bootcmd_usb_2;run bootcmd_usb_3;run bootcmd_usb_4;run bootcmd_usb_5;run bootcmd_usb_6;run bootcmd_usb_7;run bootcmd_usb_8
bootcmd=run bootcmd_usb; run flash_load

The setup is an 4GB USB Stick in the back USB Port of the iconnect. I think it is Port 1.
In the front right Port plugged in an USB DVB-C Stick from Sundtek.

Greets
pr0

Re: iConnect not boots from Stick when DVB-C Stick plugged in

bodhi — Tue, 14 May 2013 01:07:54 -0400

First step, please post your output of fw_printenv from Debian. And also describe your setup a little more: if I understood correctly, the other 2 sticks are USB ? plugged into the front USB ports?

Re: PogoPlug Mobile SD Boot Troubles

bodhi — Tue, 14 May 2013 01:02:46 -0400

sosuke,

Looking back at Davy's thread:

The rootfs is packaged as an ext3 image (kirkwood-debian_image.img) so you'll have to mount with the loop option, and cp -a the contents onto a preformatted sda1 partition.

Did you do this to create the rootfs stick? note that the rootfs image is ext3. So your uBoot env for rootfs type should be ext3. Usually it's OK for booting ext3 even if the env is ext2, but to be sure set your rootfs type to ext3.

iConnect not boots from Stick when DVB-C Stick plugged in

pr0j3ctx — Mon, 13 May 2013 09:49:54 -0400

Hello.

I will try to explain my problem with my bad english. Sorry for this.

I have an iomega iConnect debianized with this Tutorial: http://www.congenio.de/infos/iconnect.html

All runs good. I will use my iomega als tvheadend Server. For this I need two DVB-C Sticks from Sundtek. First I tried only the USB-Stick and configured all. After this I plugged in one DVB-Card for testing. Since testing I had the problem that after reboot a while nothing happens and then the original firmware loaded.

Yesterday i made some tests and after i plugged out my DVB-C Card the iomega booted from my USB-Stick.

The USB-Sticks plugged in at Port 1 at the back of the iconnect.

Now I don`t know what todo next. It isn´t a nice solution to unplug the DVB-C Card each reboot. I often works remotly some miles away on the iconnect.

I´m not a specialistin uBoot etc. so I don´t know what to do. Is there anyone out there who can help me or push me in the right direction.

Sorry if there are to less information. If you need one, tell me and i will bring it.

Thanks for reading till here.

Greats
pr0

PogoPlug Mobile SD Boot Troubles

sosuke — Mon, 13 May 2013 05:43:10 -0400

Hello, I am having some issues getting my Pogoplug mobile to boot from an SD card. I'll say up front that I am no linux expert so if there is anything unclear or additional information needed please let me know.

I followed bodhi's guide for getting this setup (http://forum.doozan.com/read.php?2,11663,page=1)
I've tried 2 different images for the SD card. One from a file called Debian.Wheezy.20130407.Pogoplug.tar (sorry I can't remember where I found this and I can't find it searching) and the other currently on the SD card from Davy's Zyxel thread here (http://forum.doozan.com/read.php?2,7806).

The SD card is fromated ext2 3gb for partition 1 and 1gb swap for partition 2.

I think the uboot install worked out ok because I get feedback from netconsole as follows

** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
SDHC found. Card desciption is:
Manufacturer:       0x1b, OEM "SM"
Product name:       "FBA4B", revision 1.1
Serial number:      171337637
Manufacturing date: 11/2012
CRC:                0x00, b0 = 0
mmc1 is available
SDHC found. Card desciption is:
Manufacturer:       0x1b, OEM "SM"
Product name:       "FBA4B", revision 1.1
Serial number:      171337637
Manufacturing date: 11/2012
CRC:                0x00, b0 = 0
mmc1 is available
Loading file "/boot/uImage" from mmc device 0:1 (xxa1)
2279256 bytes read
Loading file "/boot/uInitrd" from mmc device 0:1 (xxa1)
7004538 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.3.2
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2279192 Bytes = 2.2 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-3.3.2-kirkwood-dg
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7004474 Bytes = 6.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

At this point it seems to hang and drops off my network (no longer in device table on router).

I took a look at the logs on the SD card and they all say

(Nothing has been logged yet.)

Which seems to be the default for them on a fresh install.

Here is my printenv output. Maybe I have a mistake somewhere in here?

Pogov4> printenv
arcNumber=2097
baudrate=115200
bootargs=console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext2 mtdpar
ts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd;
 usb stop; run mmc_bootcmd
bootdelay=10
console=ttyS0,115200
ethact=egiga0
ethaddr=02:50:43:52:d1:04
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /
rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd
; fi
if_netconsole=ping $serverip
ipaddr=192.168.10.46
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mmc_bootcmd=mmc init; mmc init; ext2load mmc 0:1 0x00800000 /boot/uImage; if ext
2load mmc 0:1 0x01100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else boot
m 0x800000; fi
mtddevname=uImage2
mtddevnum=2
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M
(root)
ncip=192.168.10.38
partition=nand0,2
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
preboot=run if_netconsole start_netconsole
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; na
nd read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs
ro rootfstype=ubifs $mtdparts $rescue_custom_params
serverip=192.168.10.38
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; se
tenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && u
bifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm
0x800000 0x1100000; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0
:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext
2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; el
se bootm 0x800000; fi
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_device=0:1
usb_init=run usb_scan
usb_root=/dev/sda1
usb_rootdelay=10
usb_rootfstype=ext2
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if t
est $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_
scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; se
tenv usb_root /dev/$dev; fi; done
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_scan_list=1 2 3 4
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_
rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params

Environment size: 2955/131068 bytes

So is it my SD card? Is it my kernel? Is it my env? I'm not really sure how to proceed to fix this. Any help would be apprciated. Thank you.

Re: U-Boot for Device-Tree Kernel

bodhi — Sun, 12 May 2013 15:13:15 -0400

Of course you're right! I turned on debug for both netconsole and hush parser. Hush parser works with no problem. Netconsole was the problem since it echos back the incompeted command string before hush takes it.

The strange thing is if I turned on netconsole debug option, then the command was echo back OK (no dropped 2nd char). But still it won't boot with netconsole.

Re: U-Boot for Device-Tree Kernel

syong — Sun, 12 May 2013 10:51:21 -0400

If it is hush parser, you should see the problem on the serial console too.

Re: U-Boot for Device-Tree Kernel

bodhi — Sat, 11 May 2013 21:18:33 -0400

@syong,

Re http://forum.doozan.com/read.php?3,12218,12378#msg-12378
Reset_phys does not seems to be the problem. I think it might be a bug in hush parser.

Re: U-Boot w/ MMC/SD-card booting for Pogoplug Series 4

halogen — Sat, 11 May 2013 13:03:19 -0400

Thanks bodhi and dhead,

I'm out of luck this time. I did change /etc/network.d/wired-eth0 as static, however, it seems my bricked PPMobile stocked somewhere before completely booting.

Anyways, I just order serial-USB adapter to bring my PPMobile alive. I will keep up posting my status. Thanks guys. :)

Re: Newer uBoot as workaround to 3.2 kernel problem?

bodhi — Fri, 10 May 2013 18:42:17 -0400

chessplayer,

No, it's not safe to update uBoot for your NSA320 using the offical script. Unless you have assurance from Davy that you can use this standard installation script. But I don't think it will work.

Re: Newer uBoot as workaround to 3.2 kernel problem?

chessplayer — Fri, 10 May 2013 18:16:06 -0400

Hi guys,

I am currently trying to get a Zyxel NSA320 up and running. Using davy's basic setup, I am able to boot from a USB-drive, but the exact same rootfs on the first SATA drive gives:

U-Boot 2011.12 (May 03 2012 - 17:04:23)
ZyXEL NSA320 2-Bay Power Media Server
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot:  0 

Reset IDE: Bus 0: OK Bus 1: OK 
  Device 0: Model: ST3320413AS  Firm: JC45 Ser#: Z2A84WH4
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 305245.3 MB = 298.0 GB (625142448 x 512)
  Device 1: Model: ST3320413AS  Firm: JC66 Ser#: Z2AJ97AK
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 305245.3 MB = 298.0 GB (625142448 x 512)
Loading file "/boot/uImage" from ide device 0:1 (hda1)
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - ide 0:1 **
Loading file "/boot/uInitrd" from ide device 0:1 (hda1)
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - ide 0:1 **
Wrong Image Format for bootm command
Error occured, error code = 108
ERROR: can't get kernel image!

Reset IDE: Bus 0: OK Bus 1: OK 
  Device 0: Model: ST3320413AS  Firm: JC45 Ser#: Z2A84WH4
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 305245.3 MB = 298.0 GB (625142448 x 512)
  Device 1: Model: ST3320413AS  Firm: JC66 Ser#: Z2AJ97AK
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 305245.3 MB = 298.0 GB (625142448 x 512)
** Bad partition 1 **
** Bad partition 1 **
Wrong Image Format for bootm command
Error occured, error code = 108
ERROR: can't get kernel image!

No I am wondering whether I can safely upgrade to the official uBoot. I am somewhat put off by its output:

root@debian-kirkwood-wide:~# ./install_uboot_mtd0.sh 


!!!!!!  DANGER DANGER DANGER DANGER DANGER DANGER  !!!!!!

If you lose power to your device while running this script,
it could be left in an unusable state.

This script will replace the bootloader on /dev/mtd0.

This installer will only work on the following devices:
 Seagate Dockstar
 Seagate GoFlex Net
 Seagate GoFlex Home
 Pogoplug v1
 Pogoplug Pink (v2)
Do not run this installer on any other device.

It would be just great if this listed the Zyxel NSA3xy devices ...

So:

a) Is it safe to update uBoot? (my guess: yes, since otherwise davy's rescue system post would not make much sense, would it?)
b) Will that take care of the SATA boot problem?

Help, as always, greatly appreciated.

Cheers,

chessplayer

Re: U-Boot w/ MMC/SD-card booting for Pogoplug Series 4

dhead666 — Fri, 10 May 2013 16:12:02 -0400

@halogen

nano /etc/network.d/wired-eth0
and reboot

this may change in the future as arch linux (not arm specific) moved from netcfg to netctl

Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB

bodhi — Fri, 10 May 2013 00:44:12 -0400

CP,

Sorry, I don't know much about rescue system! I don't really use it at all, other than installing one on Pogo E02 long ago to try it out. But never booted back into it.

Re: Problems with POGO-E02 (Black)

Ted — Fri, 10 May 2013 00:43:55 -0400

Hi Jeff,
I have this same Black Pogo-E02, and the uboot install error at the same 459cd5082764fc782e204f7de8f4bcca
Looking at previous posts with this version, it looks like users have become semi bricked with forcing no-check. Is there any updated info on this uboot version? Thank you for all that you do.
Regards,
Ted

Re: Booting Debian on Pogoplug Pro

shv — Thu, 09 May 2013 14:53:02 -0400

Could the problem be caused by the following entry in resolv.conf: search fritz.box? But I think this entry should also be overwritten by the dhcpclient.

Re: Booting Debian on Pogoplug Pro

hepi — Thu, 09 May 2013 14:50:15 -0400

@shv: I tested your archive debian-squeeze-pogoplugpro-shv-test.2.1.tar.gz on my Pogoplug V3 after I installed ArchARM today. Thank you for your work! I ran into a problem:

The /etc/resolv.conf contained a wrong nameserver entry and I couldn't ping any external hostnames. I'm checking the config of the dhcpclient now to see what went wrong.

Cheers,
hepi

Re: POGO-E02 Debian installation broken

UncleTom — Thu, 09 May 2013 04:16:00 -0400

Hello,

mine debian wheezy installation is broken to and i dont got a rescue system installed. ive tried a lot of new installtions of debian squeeze, dmesg says me that debian is booting but i dont get a ip or ssh. when im booting without a usb drive on it i can login via ssh on the pogo and see the ip on my router. damn

how can i fix it?

thx

Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB

cpe — Thu, 09 May 2013 03:48:07 -0400

Hi Bodhi,
sorry this may Sound crazy but .. I can boot the rescue USB stick without any Problems. But NOT the wheezy or Lenny or whatever "usual" USB stick also the one made with this dockstar using the actual wheezy-install-script.
Will it help making another rescue System?

Sorry but ...
Greets
CP