Package: linux-image-3.2.0-1-kirkwood Version: 3.2.2-1
Problem: This kernel package, when installed on many Kirkwood machines, including the Dockstar, does not boot. Various users have noticed this, and it seems likely that it could be related to compression of the kernel image into the uImage file. Notably, an uncompressed vmlinux.bin (from the same build/source) relabeled as uImage will boot correctly. Unfortunately, the default for this package is a compressed image. http://packages.debian.org/unstable/kernel/linux-image-3.2.0-1-kirkwood Steps to reproduce, with output shown: On my Dockstar: ============================== ================================ cd / wget http://ftp.us.debian.org/debian/pool/main/l/linux-2.6/linux-image-3.2.0-1-kirkwood_3.2.2-1_armel.deb dpkg -i linux-image-3.2.0-1-kirkwood_3.2.2-1_armel.deb mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.2.0-1-kirkwood -d /boot/vmlinuz-3.2.0-1-kirkwood /boot/uImage mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-3.2.0-1-kirkwood -d /boot/initrd.img-3.2.0-1-kirkwood /boot/uInitrd ================================================================== >From serial connection: ============================================================== U-Boot 2010.09 (Oct 23 2010 - 11:49:22) Marvell-Dockstar/Pogoplug by Jeff Doozan SoC: Kirkwood 88F6281_A0 DRAM: 128 MiB NAND: 256 MiB In: serial Out: serial Err: serial Net: egiga0 88E1116 Initialized on egiga0 Hit any key to stop autoboot: 0 (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 4 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-0x000010000000 : "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: 219 MiB UBI: number of good PEBs: 1752 UBI: number of bad PEBs: 0 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: 1731 UBI: total number of reserved PEBs: 21 UBI: number of PEBs reserved for bad PEB handling: 17 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) 1570456 bytes read Loading file "/boot/uInitrd" from usb device 0:1 (usbda1) 6621782 bytes read ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-3.2.0-1-kirkwood Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1570392 Bytes = 1.5 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 01100000 ... Image Name: initramfs-3.2.0-1-kirkwood Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 6621718 Bytes = 6.3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. ================================================================= No further output is seen. I am using Debian GNU/Linux 6/Wheezy. The same behavior shows up with Squeeze.
