Ext2ls and the usb start commands are built into uboot. You need to be at the uboot prompt to use them.
----- 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:19 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/Fedo...
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,
OK. I kind of figured out part of this. That is, I had more to do after the 1st boot, per:
fedoraproject.org/wiki/Architectures/ARM/F18/GuruPlug
Problem is with the instructions:
# NOTE: substitute "usb 1:1" with "usb 0:1" on non-Plus model devices, or try: usb start ext2ls usb x:1 #where x can be any integer but usually 0-3, the right number will show a directory listing including the files uInitrd and uImage
Well no usb or ext2ls commands. I searched all over the image. I ran updatedb, the tried locate. Nothing. Now what?
_______________________________________________ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
"omalley_s@rocketmail.com" omalley_s@rocketmail.com writes:
Ext2ls and the usb start commands are built into uboot. You need to be at the uboot prompt to use them.
Just FTR, the default version of uboot shipped on the Guruplug Server (at least on the two non-Plus version I have) did not include ext support. I had to reflash uboot to a newer version.
-derek
On 04/23/2013 09:03 AM, Derek Atkins wrote:
"omalley_s@rocketmail.com" omalley_s@rocketmail.com writes:
Ext2ls and the usb start commands are built into uboot. You need to be at the uboot prompt to use them.
Just FTR, the default version of uboot shipped on the Guruplug Server (at least on the two non-Plus version I have) did not include ext support. I had to reflash uboot to a newer version.
I posted this in an earlier part of this thread. Here is what I see in the nc session for the netconsole.
You tell me if it is supporting ext. I did make the documented changes to uboot for f18 (which I don't have that link in front of me, but Scott's.
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) Failed to mount ext2 filesystem... ** Bad ext2 partition or disk - usb 0:1 ** 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) Failed to mount ext2 filesystem... ** Bad ext2 partition or disk - usb 0:1 ** ** Block device usb 1 not supported ** Block device usb 2 not supported ** Block device usb 3 not supported Loading file "uImage" from usb device 0:1 (usbda1) Failed to mount ext2 filesystem... ** Bad ext2 partition or disk - usb 0:1 ** Loading file "uInitrd" from usb device 0:1 (usbda1) Failed to mount ext2 filesystem... ** Bad ext2 partition or disk - usb 0:1 ** 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 ...