Tinkerer, I'm looking at the GoFlex Home board picture, inside from the battery looking outward. There are 2 rows of 5 pins. The top row left most 3 pins are: GND TX RX Is that how you determine the pins?by bodhi - uBoot
Tinkrer Wrote: ------------------------------------------------------- > I have two terminal windows open. > > In terminal 1 > kwboot shows spinning. > > In terminal 2 > screen /dev/ttyUSB0 115200 shows garbled > characters. I would check Tx and Rx lines to see they were reversed. Because kwboot handshakes with Boot ROM only, u-boot is not involved. And itby bodhi - uBoot
Tinkrer Wrote: ------------------------------------------------------- > Appreciate your quick reply. > > Yes. I did try with the binary that you posted. > > ./kwboot -t -B 115200 /dev/ttyUSB0 -b > uboot.2014.07.tld-1.goflexhome.mtd0.kwb -p > > I do not have another ARM plug. > > The | character continues to spin :-( > > - Tinkrer Does theby bodhi - uBoot
Hi Looker, Did you install the same u-boot using Arch installation on the other Pogo E02 that still work with Pogo OS?by bodhi - uBoot
Thanks Gray! LouisV did report the typos: http://forum.doozan.com/read.php?2,11663,16696#msg-16696 I've updated the post to indicate that. QuoteAs feedback, I would like to see the "mmc_bootcmd" and "sata_bootcmd" (<devicetype>_bootcmd) as the standard. The reason I use bootcmd_xxx postfix was to follow the same convention that Jeff used originally. It iby bodhi - uBoot
LouisV, Quote> As per my potentially flawed interpretation of > your directions I changed > > mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage) > ,32M(rootfs),-(data) > > back to > > mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage) > ,3M(uImage2),8M(failsafe),112M(root) > This is correct interpretation. Each box potentially has different mtdpaby bodhi - Debian
LouisV, Cool! just what I've suspected, the older MMC driver in davygravy's version might have problem with some SD cards. The kirkwood MMC driver used by ebbes is working much better.by bodhi - Debian
Darn! :) Thanks for testing it! I might have an editing error in that bootcmd.by bodhi - Debian
Tinkrer, Did you download the u-boot I posted? if you did, the command is: ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07.tld-1.goflexhome.mtd0.kwb -p And if you have another ARM plug, then you can use the kwboot binary I uploaded in that same thread.by bodhi - uBoot
@LouisV, Quote> Pogov4> ext2ls mmc 0:1 /boot > ext2ls mmc 0:1 /boot > > > I'm not sure, but shouldn't I see the boot files > listed? > > Pogov4> ext2ls mmc 0:1 / > ext2ls mmc 0:1 / > <DIR> 4096 . > <DIR> 4096 .. > <DIR> 16384 lost+found > <DIR> 98306 proc > <DIR>by bodhi - Debian
agiorgio, Ignore the UBIFS errors, they are expected.by bodhi - Debian
LouisV, > I have been using gparted (which worked fine with > the USB stick). Is the SD card MBR or GPT?by bodhi - Debian
@LouisV, As grayman4hire said, the /boot/uImage and /boot/uInird must be on the SD card. You can interrupt netconsole and run u-boot command ext2ls to see if it can find the boot files mmc init ext2ls mmc 0:1 /boot And by the way, I've uploaded the new U-Boot which should handle MMC a lot better: http://forum.doozan.com/read.php?3,12381by bodhi - Debian
I've uploaded the 2014.07 U-Boot images for GoFlexNet, GoFlex Home, Pogoplug E02, Dockstar, Pogplug V4/Mobile, iConnect, Netgear Stora. Please see 1st post for download link and installation instruction.by bodhi - uBoot
msanad, - Always shutdown before powering off: shutdown -h now - And format the USB as Ext3 (automatically recover from power outage) - See this thread for extending life of USB thumb drives.by bodhi - uBoot
agiorgio, New U-Boot supports large GPT disk, so there is no need to use hybrid MBR. > Number Start (sector) End (sector) Size > Code Name > 1 256 488191 1.9 GiB > 8200 swap > 2 488192 727446527 2.7 TiB > 8300 data > 3 727446528 732566527 19.5 GiB > 8300 root >by bodhi - Debian
@Looker, You can not boot back to Pogo OS after installing ALARM u-boot (part of your Arch installation).by bodhi - uBoot
@grayman4hire, Sorry gray, I need to write some extra flashing instruction for PogoV4/Mobile (same as for iConnect and Netgear Stora). It won't work without it.by bodhi - uBoot
Ah. That's made it simpler with only one USB port. And that link currently the only way to install with a script. Later when you have booted into Arch succesfully, you can come back and install the new U-boot which I will upload today or tomorrow in this thread.by bodhi - uBoot
Does the mmc device appear under /dev/disk? if it does not appear there then the Pogo OS udev (if it uses udev) did not detect the mmc. It might use some hotplug process to do this, though. ls -lR /dev/disk/by bodhi - Debian
jeepster, USB: scanning bus for devices... 2 USB Device(s) found Waiting for storage device(s) to settle before scanning... T Device NOT ready Request Sense returned 00 00 00 1 Storage Device(s) found The problem is the USB was not properly initialized. This problem usually can be solved just by switching to a better brand (such as Sandisk). But first, you can do this: - At serby bodhi - uBoot
jeepster, You have connected serial console, but no need to do UART booting yet. Perhaps the problem is quite simple to see on serial console. - First connect the serial console from your Ubuntu/Windows/Mac box using whatever program you are confortable with. - At serial console, get the entire log of what's going on and post here. Only if the installed u-boot is all messed up, theby bodhi - uBoot
agiorgio, Looks like you are using hybrid MBR, did you create the partitions using the instruction here? http://www.rodsbooks.com/gdisk/hybrid.htmlby bodhi - Debian
Download the GoFlex Home u-boot from this thread: http://forum.doozan.com/read.php?3,12381 And use serial console to boot with UART method (kwboot) as described in this thread: http://forum.doozan.com/read.php?3,7852,7852 Stop at the u-boot countdown, plug in your Arch rootfs USB. And boot! Come back here if you have problem booting into Arch or see errors.by bodhi - uBoot
Have you installed new packages since your last post? perhaps you should reboot after each installation to make sure the system is booting OK. The permission problems we're seeing in the log seems to point to either: - The rootfs was not created by root user. - Some packages installations were not completely successful.by bodhi - uBoot
JohnnyTToxic, That looks totally wrong. If you've followed the instruction, the first and only partition System type should be Linux. And use fdisk -l to list partition, don't use sfdisk. Output of fdisk should be similar to this: Device Boot Start End Blocks Id System /dev/sda1 * 2048 976773166 488385559+ 83 Linuxby bodhi - uBoot
Based on this error: ** ext4fs_devread read error - block ** File not found /boot/uInitrd ** ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-3.14.4-1-ARCH Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3965072 Bytes = 3.8 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... Bad Data CRC I'd guess thby bodhi - uBoot
k3x, > [ 0.000000] Kernel command line: > console=ttyS0,115200 root=/dev/sda1 rootdelay=10 > rootfstype=ext2 > mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(root > fs),-(data) This is correct. > > Why uses the usb boot commandline mtdparts ? Isn't > the usb sebian independent from the internal nand > ? It is just so that the mtdparts are acceby bodhi - Rescue System
k3x, Try these: 1. in serial console, remove the usb_rootfstype, and boot setenv usb_rootfstype boot This will only temporarily remove this env. If it boots OK, you can set it for real in Debian with fw_setenv. 2. If the above does not work, put the rootfs on another USB stick (Sandisk is most reliable brand for booting).by bodhi - Rescue System
JohnnyTToxic, > I have a pogoplug v2 that I've been running > happily as an arch server for about 4 years. The > other day, I lost power to the device and it no > longer boots. Have you taken the USB drive to another Linux box and check for errors with fsck?by bodhi - uBoot