Bad USB drive, I built it with xzcat on a F18 notebook. See below
On 04/17/2013 10:24 PM, Scott Sullivan wrote:
On 04/17/2013 09:11 PM, Robert Moskowitz wrote:
Any advise on what to do next? I really think it has to do with which usb port I am using.
So I do recall from back when the Pogoplug was new there were many folks having issues with some USB drive just not being recognized during uboot.
Since it looks you got the new uboot installed, I would now try using a netconsole to see if you can get any extra information about why it's booting into the Pogoplug linux.
http://forum.doozan.com/read.php?3,14,14
This thread mentions the dockstar, which is just the same basic hardware in a different configuration. Same principle applies.
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 ...
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
I removed the drive, put it in a different usb port, and my notebook (which is running gnome on f18) would not open it in Nautilus. I kind of assumed that this was suppose to be a readable partition. So I brought up Disk Manager, and it showed the drive still having a MSDOS FAT partition with unknown content. My previous attempt was with a 8Gb usb drive that had a ext3 partition, and now still has that partition with unknown content. Note below that the pogoplug boot things it is seeing an ext2 partition on the drive.
So what now? Is the image bad? Is that the wrong command on F18 (note that the nc options on http://forum.doozan.com/read.php?3,14,14 are wrong for F18)? Is the image totally non-workable on the plug and I should instead use the f17 image at:
http://fedoraproject.org/wiki/Architectures/ARM/Kirkwood#Writing_the_Image
?
Help?
On 04/18/2013 10:51 AM, Robert Moskowitz wrote:
Bad USB drive, I built it with xzcat on a F18 notebook. See below
On 04/17/2013 10:24 PM, Scott Sullivan wrote:
On 04/17/2013 09:11 PM, Robert Moskowitz wrote:
Any advise on what to do next? I really think it has to do with which usb port I am using.
So I do recall from back when the Pogoplug was new there were many folks having issues with some USB drive just not being recognized during uboot.
Since it looks you got the new uboot installed, I would now try using a netconsole to see if you can get any extra information about why it's booting into the Pogoplug linux.
http://forum.doozan.com/read.php?3,14,14
This thread mentions the dockstar, which is just the same basic hardware in a different configuration. Same principle applies.
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 ...
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
----- 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,
Paul
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,
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 ...
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?
You should run `sync` after doing that kind of i/o. I bet half the bits were still in the buffer flushing out by the time you yanked the usb. On Apr 18, 2013 1:49 PM, "Robert Moskowitz" rgm@htt-consult.com wrote:
Per:
fedoraproject.org/wiki/**Architectures/ARM/F18/GuruPlughttp://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.xzhttp://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
I removed the drive, put it in a different usb port, and my notebook (which is running gnome on f18) would not open it in Nautilus. I kind of assumed that this was suppose to be a readable partition. So I brought up Disk Manager, and it showed the drive still having a MSDOS FAT partition with unknown content. My previous attempt was with a 8Gb usb drive that had a ext3 partition, and now still has that partition with unknown content. Note below that the pogoplug boot things it is seeing an ext2 partition on the drive.
So what now? Is the image bad? Is that the wrong command on F18 (note that the nc options on http://forum.doozan.com/read.**php?3,14,14http://forum.doozan.com/read.php?3,14,14are wrong for F18)? Is the image totally non-workable on the plug and I should instead use the f17 image at:
http://fedoraproject.org/wiki/**Architectures/ARM/Kirkwood#** Writing_the_Imagehttp://fedoraproject.org/wiki/Architectures/ARM/Kirkwood#Writing_the_Image
?
Help?
On 04/18/2013 10:51 AM, Robert Moskowitz wrote:
Bad USB drive, I built it with xzcat on a F18 notebook. See below
On 04/17/2013 10:24 PM, Scott Sullivan wrote:
On 04/17/2013 09:11 PM, Robert Moskowitz wrote:
Any advise on what to do next? I really think it has to do with which usb port I am using.
So I do recall from back when the Pogoplug was new there were many folks having issues with some USB drive just not being recognized during uboot.
Since it looks you got the new uboot installed, I would now try using a netconsole to see if you can get any extra information about why it's booting into the Pogoplug linux.
http://forum.doozan.com/read.**php?3,14,14http://forum.doozan.com/read.php?3,14,14
This thread mentions the dockstar, which is just the same basic hardware in a different configuration. Same principle applies.
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 ...
______________________________**_________________ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.**org/mailman/listinfo/armhttps://admin.fedoraproject.org/mailman/listinfo/arm
______________________________**_________________ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.**org/mailman/listinfo/armhttps://admin.fedoraproject.org/mailman/listinfo/arm
On 04/21/2013 10:08 PM, Jon wrote:
You should run `sync` after doing that kind of i/o. I bet half the bits were still in the buffer flushing out by the time you yanked the usb.
No. I followed instructions and ran sync.
On Apr 18, 2013 1:49 PM, "Robert Moskowitz" <rgm@htt-consult.com mailto:rgm@htt-consult.com> wrote:
Per: fedoraproject.org/wiki/Architectures/ARM/F18/GuruPlug <http://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 I removed the drive, put it in a different usb port, and my notebook (which is running gnome on f18) would not open it in Nautilus. I kind of assumed that this was suppose to be a readable partition. So I brought up Disk Manager, and it showed the drive still having a MSDOS FAT partition with unknown content. My previous attempt was with a 8Gb usb drive that had a ext3 partition, and now still has that partition with unknown content. Note below that the pogoplug boot things it is seeing an ext2 partition on the drive. So what now? Is the image bad? Is that the wrong command on F18 (note that the nc options on http://forum.doozan.com/read.php?3,14,14 are wrong for F18)? Is the image totally non-workable on the plug and I should instead use the f17 image at: http://fedoraproject.org/wiki/Architectures/ARM/Kirkwood#Writing_the_Image ? Help? On 04/18/2013 10:51 AM, Robert Moskowitz wrote: Bad USB drive, I built it with xzcat on a F18 notebook. See below On 04/17/2013 10:24 PM, Scott Sullivan wrote: On 04/17/2013 09:11 PM, Robert Moskowitz wrote: Any advise on what to do next? I really think it has to do with which usb port I am using. So I do recall from back when the Pogoplug was new there were many folks having issues with some USB drive just not being recognized during uboot. Since it looks you got the new uboot installed, I would now try using a netconsole to see if you can get any extra information about why it's booting into the Pogoplug linux. http://forum.doozan.com/read.php?3,14,14 This thread mentions the dockstar, which is just the same basic hardware in a different configuration. Same principle applies. 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 ... _______________________________________________ arm mailing list arm@lists.fedoraproject.org <mailto:arm@lists.fedoraproject.org> https://admin.fedoraproject.org/mailman/listinfo/arm _______________________________________________ arm mailing list arm@lists.fedoraproject.org <mailto:arm@lists.fedoraproject.org> https://admin.fedoraproject.org/mailman/listinfo/arm
-
Jon -
Paul Whalen -
Robert Moskowitz