balanga , > What's the most straightforward way of getting a > new uBoot onto it? > > I don't really want to follow the Arch Linux > instructions here :- > > https://archlinuxarm.org/platforms/armv5/seagate-goflex-home That instruction is pretty good. But if you don't want to proceed to far into Arch Linux installation then try to gain SSH as instby bodhi - uBoot
Looker, See the instruction for "Migrating from Arch to Debian" in the Wiki thread QuoteBooting Debian on Pogoplug How to set up U-Boot for booting in multiple drives configuration Backup and Restore NAND mtds UART Booting HowTo for Selected Kirkwood Devices Migrating from Arch to Debian? How to boot new Debian rootfs using stock u-boot tftp - Pogo E02 How to boot neby bodhi - Debian
Tom, The rootfs /boot looks OK. But the label is not. Become root, and then set the label to rootfs: su - tune2fs -L rootfs /dev/sdb1 sync And then take it to the Dockstar and power up. The LED color amber indicated that the kernel has failed to run. But on the slight chance that the LED is wrong, and the problem is actually rootfs mounting, setting the correct label will enable tby bodhi - Debian
balanga Wrote: ------------------------------------------------------- > bodhi Wrote: > ------------------------------------------------------- > > balanga, > > > > > In my tests so far it seems that I need an > > image > > > that supports bootelf, but I'm not sure which > > > image is available and whether I can use it > >by bodhi - uBoot
Power up, interrupt serial console and setenv set_bootargs_usb 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial' boot And post the entire serial console log here.by bodhi - Debian
wired, > U-Boot 2011.12 (Apr 18 2012 - 23:08:20) > Seagate GoFlexNet This old u-boot does not support FDT. So did you append the DTB to uImage as instructed in the kernel release thread? Quote4. Create uImage with embedded DTB for booting with older u-boots (2012 or earlier). Skip this step if you have installed the latest U-Boot for Kirkwood (or are installing this u-boot at theby bodhi - Debian
> U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:21:31 > -0700) > Seagate GoFlex Home > gcc (Debian 6.3.0-18) 6.3.0 20170516 > GNU ld (GNU Binutils for Debian) 2.28 > > > This one does include bootelf.... No, it does not have full functionality to boot BSD. See my explanation above.by bodhi - uBoot
Tom, You should always post the log in context. That means including the command themselve (and importantly the mount command). This time do these: e2label /dev/sdb1 mount df -h cd /media/sdb1 ls -lart boot Please copy/paste the whole terrminal session log for the above commands here.by bodhi - Debian
Tom, > The LED is still amber and did not change to > green. Ah. The kernel has not even finish starting. Double check your rootfs kernel files (and also rootfs partition while we are at it). Mount it on another Linux box and assuming it is mountd at /media/sdb1 e2label /dev/sdb1 mount cd /media/sdb1 ls -lart /boot Look at the kernel files in /boot. Do they look correct?by bodhi - Debian
Tom, It is a classic problem with having multiple partitions in the system. The new u-boot will take care of that with the envs. You are runing old u-boot so you need to change a few envs to ensure the booting is correct. Interupt netconsole at count down and run setenv usb_set_bootargs 'setenv bootargs console=$console root=LABEL=rootfs rootdelay=$usb_rootdelay $mtdparts $usb_cusby bodhi - Debian
Tom, Interrupt netconsole at countdown > Hit any key to stop autoboot: 0 And printenv Please post the entire log here.by bodhi - Debian
balanga, > In my tests so far it seems that I need an image > that supports bootelf, but I'm not sure which > image is available and whether I can use it > without kwboot. Use the one that I've built specifically for this purpose and attached to a post here a while back in your old FreeBSD thread. It is not one of the relased GF Home u-boot images. This u-boot has bby bodhi - uBoot
balanga, > I was going to try and flash the unit but I can't > find the USB stick I had so tried to rebuild it. > Unfortunately there's something missing since the > unit starts flashing green for several minutes > before it starts flashing orange. The rootfs was not created correctly, so the kernel did not finish booting. > > Is it possible to diagnoby bodhi - uBoot
SiliCAT, I think you should use the rw option in u-boot env for now. In the future, if you have another Pogo, you can try to put the NFS rootfs on it and see if you will get the same result as I did. This issue is minor, but I like the server to determine the access mode and avoid changing u-boot env.by bodhi - uBoot
Perhaps it's a different version of NFS server. Here is mine. dpkg -l | grep nfs ii libnfsidmap2:armel 0.25-5.1 armel NFS idmapping library ii nfs-common 1:1.3.4-2.1 armel NFS support files common to client and server ii nfs-kernel-server 1:1.3.4-2.1by bodhi - uBoot
SiliCAT On the server, what is the permission of ls -l /srv ls -l /srv/nfs-export And also verify with exportfs -sby bodhi - uBoot
z0rg, > > > U-Boot SPL 2013.10 (Apr 27 2014 - 19:08:27) > > Boot device: NAND > > Attempting to set PLLA to 800 MHz ... > > plla_ctrl0 : 0000030a > > plla_ctrl1 : 00400000by bodhi - uBoot
lille, > this box did not run 3 weeks in total, you could > call it new :( wtf You could obmit that part of NAND in mtd definition like I do. If you don't plan to go back to stock, then no worry. Just define it like this. Note that the second partition is not used either, I included it for illustration purpose. fw_setenv mtdparts 'mtdparts=orion_nand:0x100000(uboot),0xby bodhi - Debian
Spammer strikes again %^%&* :) Still waiting for Jeff to remove this account.by bodhi - Off-Topic
lille, Ah. I was expected to see undefined mtd block devices, where blkid would spit out errors no matter what. However, this kernel version has mtd block device built in. So the other mtds are OK, but not mtd5. That's not very good, it is a real problem. Which box is this? please post the entire log of dmesg cat /proc/mtdby bodhi - Debian
lille, > What's wrong here? Is this EMC troubles maybe? There is nothing wrong. blkid always spits out error like that if the mtdblock devices are not defined. If you do fdisk, you will see that they are not. Which kernel are you running? uname -aby bodhi - Debian
balanga, > > Would I be able to update my uBoot without access > via serial port? Of course, you can. The flashing typically done in Debian. However, there is always a risk in flashing uboot (eg. typo, wrong image...) that you you will not to be able to recover without serial console. And then JTAG becomes the last resort to unbrick.by bodhi - uBoot
balanga Wrote: ------------------------------------------------------- > I gave up on one of my GoFlex Home docks a few > months ago because nothing was being output to the > serial connection... Now after revisiting it, I > see that the green LED has stopped flashing and > become steady. My DHCP server indicated it was > online, and I've just managed to ssh in. &gby bodhi - uBoot
SiliCAT Wrote: ------------------------------------------------------- > Hi bodhi, > > Looks like there is no root user in > asuswrt-merlin. > admin is Asuswrt's UID 1. It's root, but with a > different name. and admin will be replaced by a > login ID which is chosen by the user. > There is a root group. I meant in the Debian stretch rootfs.by bodhi - uBoot
SiliCAT, > drwxr-xr-x 21 SiliCAT root 4096 Jan 24 13:00 PogoplugV4 Try root root. > drwxr-xr-x 21 root root 4096 Jan 24 13:00 PogoplugV4by bodhi - uBoot
Last post moved here: Compile cryptodev module on Linux Kernel 4.14.1 Kirkwood https://forum.doozan.com/read.php?2,48489by bodhi - Debian
SiliCAT, > There might be a mistake in the Wiki. > > root=/dev/nfs rw > > without the rw, the filesystem is mounted > as read-only. That's odd. I did not have to specify rw. What is the permission of your top level? does it look like this: drwxr-xr-x 25 root root 4096 Feb 24 2015 tldDebian2 Note: that tldDebian2 folder is specified in my bootcmd_nfs:by bodhi - uBoot
SiliCAT, That's probably a different problem. I'm using U-Boot 2017.07-tld-1 on 2 Pogo V4 boxes, and both NFS rootfs are on a Debian stretch server (with no V2 enabled).by bodhi - uBoot
Buck, > At present I am trying to bring up the most recent > FDT version on that system's SSD since its > firmware has already been flashed to the 2017.07 > version. That would hopefully solve the boot > problems without doctoring up the non-FDT system > drive. Good call. It will be easier to maintain the system from now on.by bodhi - Debian
SiliCAT., As I recalled, with Debian stretch, you need to set the NFS version in the rootfs to enable NFS V2 to make it work with old u-boot. The new u-boot (2017.07-tld-1) has NFS V3 so it would work right away. See: https://forum.doozan.com/read.php?3,12261,35307#msg-35307by bodhi - uBoot