Similar to what I was running into. I haven't looked at it in a while but off the top of my head. The ramfs was too big for the memory. Where it was read into. Or the memory addresses are diffetent from the guruplug and it was overwriting the defaults. On the guruplug, dhcp didn't work, so the second reboot always failed, because it wasn't on the network.. the guruplug failed with a flaky network driver Which I think is fixed on a newer kernel.. hard setting it to 100fdx seemed to work better..
Yum update failed with unsigned packages, and unavailable packages for the guruplug. I haven't tried lately maybe that actually got fixed.
----- Reply message -----
From: "Robert Moskowitz" <rgm@htt-consult.com>
To: "Paul Whalen" <pwhalen@redhat.com>
Cc: <arm@lists.fedoraproject.org>
Subject: [fedora-arm] Bad image/instructions? - Re: Problems with a pogoplug v02
Date: Thu, Apr 18, 2013 4:09 pm
On 04/18/2013 03:11 PM, Paul Whalen wrote:
>
> ----- Original Message -----
>> Per:
>>
>> fedoraproject.org/wiki/Architectures/ARM/F18/GuruPlug
>>
>> I just downloaded the image again from:
>>
>> http://dl.fedoraproject.org/pub/fedora-secondary/releases/18/Images/arm/Fedora-18-kirkwood-arm.img.xz
>>
>> This time I took a 4Gb usb drive I got from MicroCenter that still had a
>> FAT partition. On my F18 notebook as root, I ran:
>>
>> xzcat Fedora-18-kirkwood-arm.img.xz > /dev/sdc1
> Hi Rob,
>
> In your above example your writing to the first partition. Try changing that to:
>
> xzcat Fedora-18-kirkwood-arm.img.xz > /dev/sdc
>
> Hope that works,
ARGH!!!!
That is what fdisk -l told me was how it was seeing the device. Foolish
of me to believe it.
So this time it worked, but strangely. It booted, showed some errors,
did some stuff, then rebooted. The reboot showed some errors, but this
time when the kernel started, nothing else was showing on the
netconsole, so I decided to try to ssh in, and it worked!
I rebooted and it did not come up. I did a power cycle, and the
netconsole came alive showing much the same output as before.
Below is the netconsole output from the second boot.
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: 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 "uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "uImage" from usb device 0:1 (usbda1)
3387008 bytes read
Loading file "uInitrd" from usb device 0:1 (usbda1)
## Booting kernel from Legacy Image at 00800000 ...
Image Name: 3.6.10-8.fc18.armv5tel.kirkwood
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3386944 Bytes = 3.2 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs
Image Type: ARM Linux RAMDisk Image (uncompressed)
Data Size: 14579257 Bytes = 13.9 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
## Booting kernel from Legacy Image at 00800000 ...
Image Name: 3.6.10-8.fc18.armv5tel.kirkwood
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3386944 Bytes = 3.2 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs
Image Type: ARM Linux RAMDisk Image (uncompressed)
Data Size: 14579257 Bytes = 13.9 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
_______________________________________________
arm mailing list
arm@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm