Hello, I upgraded my pink Pogoplug to Wheezy, which didn't cause any major problems, but ...
After "apt-get upgrade" reboot was fine, but after "apt-get dist-upgrade" it didn't come up after the reboot. Then a vague memory came up my mind ... http://www.cyrius.com/journal/debian/wheezy-upgrade.tbm -- may this be the problem? U-boot says (netconsole): -------------------------------------- U-Boot 2010.09 (Oct 23 2010 - 11:51:16) Marvell-PinkPogo by Jeff Doozan 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: 728 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: 717 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) 1613336 bytes read Loading file "/boot/uInitrd" from usb device 0:1 (usbda1) 7207731 bytes read ## Booting kernel from Legacy Image at 00800000 ... Image Name: kernel 3.2.0-4-kirkwood Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1613272 Bytes = 1.5 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 01100000 ... Image Name: ramdisk 3.2.0-4-kirkwood Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 7207667 Bytes = 6.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... ---------------------------------------------- ... but I can't even ping it. It starts correctly when I start from the image I took before upgrading. Unfortunately I forgot the root-password of the pogoplug-firmware (which still has ssh running), so I'm not sure if simply running http://projects.doozan.com/uboot/ in the wrong environment (debian instead of original pogoplug firmware) is a good idea. What is the recommended way for upgrading u-boot (if this is likely to be the reason for the failure)? I can't find Pogoplug on http://cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade/ . Thanks in advance Rainer Rauschenberg -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/alpine.LFD.2.00.1501061602420.17923@much-magic
