squeeze install fails on Dockstar, no uImage?
February 02, 2013 07:42AM
I have a feeling I'm not the only one with this problem, but I searched and couldn't find what I'm looking for.

I'm using Jeff's script to install Debian Squeeze on my Dockstar, so I'm following these directions:

http://projects.doozan.com/debian/

I'm watching the console on a serial termal from another Dockstar which is running NetBSD.

Linux is not that familiar to me, so please take it easy on me :)

The intsall seems to work, although I get this error:

# Starting debootstrap installation
I: Retrieving InRelease
I: Failed to retrieve InRelease

The uBoot firmware can't find /boot/uImage:

UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
** File not found /boot/uImage
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
** File not found /boot/uImage
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
** File not found /boot/uInitrd
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..

And Debian never boots. It goes back to the Dockstar version of Linux.

Am I doing something wrong? Maybe the installer isn't getting everything it needs?

Thanks!
Re: squeeze install fails on Dockstar, no uImage?
February 02, 2013 07:54AM
Sorry, I posted too soon... I forgot to put this in there:

I mounted the USB disk and found that, in fact, there is no uImage:

-sh-3.2# fdisk -l

Disk /dev/sda: 8076 MB, 8076132352 bytes
249 heads, 62 sectors/track, 1021 cylinders
Units = cylinders of 15438 * 512 = 7904256 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1   *           1         990     7641779  83 Linux
/dev/sda2             991        1021      239289  82 Linux swap
-sh-3.2# mount /dev/sda1 /mnt
[   34.120000] EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
-sh-3.2# ls -1 /mnt/boot
System.map-2.6.32-5-kirkwood
config-2.6.32-5-kirkwood
initrd.img-2.6.32-5-kirkwood
vmlinuz-2.6.32-5-kirkwood

Thanks!
Re: squeeze install fails on Dockstar, no uImage?
February 02, 2013 12:13PM
Pls post your output of /usr/sbin/fw_printenv
Re: squeeze install fails on Dockstar, no uImage?
February 02, 2013 05:24PM
I did restore the firmware back to original from the bottom of the uBoot page on Jeff's site, then let the squeeze install script do whatever it does with the firmware from there. This machine was previously running NetBSD and I had changed the uBoot environment to boot it, but I was hoping it went back to "original" when I re-install the original bootloader.

Here it is:

-sh-3.2# fw_printenv
ethact=egiga0
bootdelay=3
baudrate=115200
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
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
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $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; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
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_init=run usb_scan
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
ethaddr=00:10:75:1A:5E:FE
arcNumber=2097
-sh-3.2#
Re: squeeze install fails on Dockstar, no uImage?
February 03, 2013 07:01AM
Your uBoot envs look good, and you booted back to Pogo linux. So you can just rerun the Squeeze installation from scratch. The installer will detect new uBoot and skip that part. Also, remmeber to keep the entire log of the installation.
Re: squeeze install fails on Dockstar, no uImage?
February 03, 2013 12:23PM
I've tried many times unfortunately. I attached a screen log from one of those times.

Thanks.
Attachments:
open | download - screenlog.0.squeeze_install_fail.gz (15.6 KB)
Re: squeeze install fails on Dockstar, no uImage?
February 05, 2013 02:47PM
I could not tell why either! did not see any error other than the mounting of sda1 failed at one point (however it seems to mount OK later). It is a little bit hard to read the log from a serial console.

You could try to boot with Davy's rootfs:
http://forum.doozan.com/read.php?2,7806
Eddiie
Re: squeeze install fails on Dockstar, no uImage?
February 06, 2013 12:20AM
acruhl Wrote:
-------------------------------------------------------
> I've tried many times unfortunately. I attached a
> screen log from one of those times.
>
> Thanks.


I am having the same problem...

InRelease failed.

Can't install.

Please fix!
Re: squeeze install fails on Dockstar, no uImage?
February 07, 2013 05:09PM
uBoot file needs to be created from vmlinuz, which is not happening for what ever reason.

The following seems to correct the problem:

cd /tmp/debian/usr/bin #adjust based on the location of usb stick mount point
./mkimage -A arm -O linux -T kernel  -C none -a 0x00008000 -e 0x00008000 -n Linux-2.6.32-5-kirkwood -d ../../boot/vmlinuz-2.6.32-5-kirkwood ../../boot/uImage
./mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-2.6.32-5-kirkwood -d ../../boot/initrd.img-2.6.32-5-kirkwood ../../boot/uInitrd



Edited 1 time(s). Last edit at 02/07/2013 09:51PM by okigan.
Re: squeeze install fails on Dockstar, no uImage?
February 07, 2013 10:41PM
Do we know why InRelease fails and if it's a problem? I think it's not in the Debian repository for whatever reason. I'm not a Debian expert, so I don't know what's going on.

I will try the manual mkimage commands. I was looking for these a bit but didn't find them, so thanks for that.

I did try the DavyGravy rootfs, to the point where I might want to get one of those NAS boxes that he built it for.

So I have a running Dockstar with that rootfs, but it's VERY tiny so you have a lot of stuff to add if you want to use it.

It would be really nice to figure out why the squeeze install script fails...
Eddiie
Re: squeeze install fails on Dockstar, no uImage?
February 08, 2013 03:51AM
I tried the steps left by Okigan,


debian:/usr/bin# ./mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-2.6.32-5-kirkwood -d ../../boot/vmlinuz-2.6.32-5-kirkwood ../../boot/uImage
Image Name: Linux-2.6.32-5-kirkwood
Created: Fri Feb 8 10:46:09 2013
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1435344 Bytes = 1401.70 kB = 1.37 MB
Load Address: 0x00008000
Entry Point: 0x00008000
debian:/usr/bin# ./mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-2.6.32-5-kirkwood -d ../../boot/initrd.img-2.6.32-5-kirkwood ../../boot/uInitrd
Image Name: initramfs-2.6.32-5-kirkwood
Created: Fri Feb 8 10:46:26 2013
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 6000049 Bytes = 5859.42 kB = 5.72 MB
Load Address: 0x00000000
Entry Point: 0x00000000


reboot,
debian:~# uname -a
Linux debian 2.6.32-5-kirkwood #1 Sun Sep 23 22:53:30 UTC 2012 armv5tel GNU/Linux

Maybe I am not doing this correctly. I am expecting it to be Kernel 3.7.x or something newer than 2.6.

How do I do this?

Thank you!
Re: squeeze install fails on Dockstar, no uImage?
February 09, 2013 12:12AM
acruhl Wrote:
-------------------------------------------------------
> Do we know why InRelease fails and if it's a
> problem? I think it's not in the Debian repository
> for whatever reason. I'm not a Debian expert, so I
> don't know what's going on.
> squeeze install script fails...

I saw a thread discussing the InRelease issue.
Per which InRelease was replaced with Release, and failure to download InRelease
should be only an info message not warning/error.

My guess is that squeeze used to have a package similar to kernel-flash in wheezy,
but with recent updates it's no longer included in the packages that Jeff specifies.
Re: squeeze install fails on Dockstar, no uImage?
February 09, 2013 12:15AM
Eddiie Wrote:
-------------------------------------------------------
> debian:/usr/bin# ./mkimage -A arm -O linux -T
> kernel -C none -a 0x00008000 -e 0x00008000 -n
> Linux-2.6.32-5-kirkwood -d

> reboot,
> debian:~# uname -a
> Linux debian 2.6.32-5-kirkwood #1 Sun Sep 23
> 22:53:30 UTC 2012 armv5tel GNU/Linux
>
> Maybe I am not doing this correctly. I am
> expecting it to be Kernel 3.7.x or something
> newer than 2.6.

you made uboot image from Linux-2.6.32-5-kirkwood,
so what you got on reboot is corresponding to that.

Check out other threads on this board, how to get to newer kernels
(although it's not clear if they give any benefit)
Jens
Re: squeeze install fails on Dockstar, no uImage?
February 09, 2013 04:02PM
Hi,

same problem with fresh isntall, using the commands from okigan helped out:

./mkimage -A arm -O linux -T kernel  -C none -a 0x00008000 -e 0x00008000 -n Linux-2.6.32-5-kirkwood -d ../../boot/vmlinuz-2.6.32-5-kirkwood ../../boot/uImage
Image Name:   Linux-2.6.32-5-kirkwood
Created:      Sat Jan  1 01:01:50 2000
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    1435344 Bytes = 1401.70 kB = 1.37 MB
Load Address: 0x00008000
Entry Point:  0x00008000
./mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-2.6.32-5-kirkwood -d ../../boot/initrd.img-2.6.32-5-kirkwood ../../boot/uInitrd
kirkwood ../../boot/uInitrd
Image Name:   initramfs-2.6.32-5-kirkwood
Created:      Sat Jan  1 01:02:00 2000
Image Type:   ARM Linux RAMDisk Image (gzip compressed)
Data Size:    4529754 Bytes = 4423.59 kB = 4.32 MB
Load Address: 0x00000000
Entry Point:  0x00000000

The files where missing before and the uBoot runs into an error:
U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02
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
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000008000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=3"
UBI: MTD device size:            91 MiB
UBI: number of good PEBs:        727
UBI: number of bad PEBs:         1
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     0
UBI: available PEBs:             716
UBI: total number of reserved PEBs: 11
UBI: number of PEBs reserved for bad PEB handling: 7
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
** File not found /boot/uImage
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
** File not found /boot/uImage
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
** File not found /boot/uInitrd
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: ........ done.
### JFFS2 load complete: 524288 bytes loaded to 0x800000
## Starting application at 0x00800200 ...

After fixing this:
U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02
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
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000008000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=3"
UBI: MTD device size:            91 MiB
UBI: number of good PEBs:        727
UBI: number of bad PEBs:         1
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     0
UBI: available PEBs:             716
UBI: total number of reserved PEBs: 11
UBI: number of PEBs reserved for bad PEB handling: 7
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1435408 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
4529818 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.32-5-kirkwood
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1435344 Bytes = 1.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-2.6.32-5-kirkwood
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4529754 Bytes = 4.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

It looks like the installer must be fixed!
andrzej_k2
Re: squeeze install fails on Dockstar, no uImage?
February 12, 2013 01:34AM
Hi all,

I have this problem too


Pogoplug:~$ /usr/sbin/fw_printenv
ethact=egiga0
bootdelay=3
baudrate=115200
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs
ro rootfstype=ubifs $mtdparts $rescue_custom_params
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
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
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
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0
:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
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
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_list=1 2 3 4
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_init=run usb_scan
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_
rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
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
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd;
 usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
ethaddr=00:25:31:04:6D:E5
arcNumber=2097
serverip=192.168.0.110
ipaddr=192.168.0.113
if_netconsole=ping $serverip
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; se
tenv stdout nc; setenv stderr nc; version;
preboot=run if_netconsole start_netconsole


U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02
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 
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000008000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=3"
UBI: MTD device size:            91 MiB
UBI: number of good PEBs:        727
UBI: number of bad PEBs:         1
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     0
UBI: available PEBs:             716
UBI: total number of reserved PEBs: 11
UBI: number of PEBs reserved for bad PEB handling: 7
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
** File not found /boot/uImage
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
** File not found /boot/uImage
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
** File not found /boot/uInitrd
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: ......... done.
### JFFS2 load complete: 524288 bytes loaded to 0x800000
## Starting application at 0x00800200 ...




How to fix? On box POGO-P24 and on device Pogo E02.
Who can help?
tungsten2k
Re: squeeze install fails on Dockstar, no uImage?
July 04, 2013 01:18PM
Same here on Pogo E02.

Can't seem to find any solution other than building a Linux box (that I don't have) then rebuilding the boot image on the target USB drive?
Re: squeeze install fails on Dockstar, no uImage?
July 04, 2013 06:25PM
I don't know if this has anything to do with your problem, but on my Pogo E02, which was built initially from a very old version of squeeze, I had to run the command "flash-kernel" after an "apt-get upgrade" in order to permit a new kernel download to take effect. If I didn't do this, it just booted on the old kernel and sometimes complained about bad modules which were no longer compatible with that kernel. If I were not running on NAND, it did not "flash" anything -- it just built a new uInitrd and uImage. You might give that a try.

(I find no longer have to do this once I upgraded to wheezy.)
Re: squeeze install fails on Dockstar, no uImage?
August 21, 2013 12:37AM
well, "good" to find my own post that solves my problem or at least almost solves it:

Installing squeeze/wheeze from rescue system fails to uBoot files and calling mkimage does not work.

So the work around to chroot into newly create system.

* Run Jeff's script as usual
* Say NO to reboot
* Then:

mount /dev/sda1 /tmp/debian
chroot /tmp/debian /bin/bash 

mkimage -A arm -O linux -T kernel  -C none -a 0x00008000 -e 0x00008000 -n Linux-2.6.32-5-kirkwood -d /boot/vmlinuz-2.6.32-5-kirkwood /boot/uImage

mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-2.6.32-5-kirkwood -d /boot/initrd.img-2.6.32-5-kirkwood /boot/uInitrd
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: