It’s pretty hard to brick a Kirkwood box, connect a serial console and watch it boot. Post the serial log and I will have a look. Though this forum is about replacing stock , not fixing it.by jdwl101 - Debian
Hi, You haven't appended the dtb to the image, make sure you follow all steps of '4b' in Bodhi's instructions. Here are the commands; cd /boot mv uImage uImage.orig cp -a zImage-5.1.11-kirkwood-tld-2 zImage.fdt cat dts/kirkwood-lenovo-iomega-ez.dtb >> zImage.fdt mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-5.1.11-kirkwooby jdwl101 - Debian
To boot from USB, create a 4.12 rootfs (using Bodhi's instructions in the Kernel / Rootfs thread), label it rootfs and enter these commands into the uboot prompt; setenv bootargs 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=spi_flash:0x7e000@0(u-boot),0x1000@0x7f000(env),0x1000@0x7e000(env2) earlyprintk=serial' setenv bootcmd_usb 'usb reset; run usb_scanby jdwl101 - Debian
Hi, Load the uImage and uInitrd from the hard disk sectors is possible, but it does make updates more complex, as a change in image size can stop the system booting. Boot with the serial console connected and when you see this prompt; Hit any key to stop autoboot: Hit a key to get to the uboot prompt. Then enter printenv and paste the output here, so we can see how it's booting nby jdwl101 - Debian
Hi, That guide you used loads the uinitrd and uimage from raw drive sectors. To update them you have write the new images to the drive in the same way, or change your boot parameters to load from USB or a partition. Updating the kernel in Debian alone won’t load it through uboot. Boot to uboot and printenv, post the output for us to see.by jdwl101 - Debian
Hi, kwboot needs to be run from a Linux pc connected to the ex4100’s serial port. If your pc is a windows box you could use a virtual machine or Linux livecd.by jdwl101 - Debian
Plug your USB drive into a usb2 port and try again. The kernel log doesn’t show the drive being assigned an sd id.by jdwl101 - Debian
congrats! This one was a real bugger, very surprising that Synology hamstrings their boxes uboot!by jdwl101 - Debian
Ok, sorry about that, I'm following the thread but didn't see that. Even if imi fails still try to boot the uImage. Would be interesting to see what it does.by jdwl101 - Debian
I agree, the 0x2000 might be cutting the image off. Try; scsi read $load_image_addr 0x5000 0x2F00by jdwl101 - Debian
If you want to have another 'crack' at loading from sda here are the commands from my howto (changed to use SCSI instead); /kernels# dd if=uImage of=/dev/sda bs=1MiB seek=10 3+1 records in 3+1 records out 4171272 bytes (4.2 MB, 4.0 MiB) copied, 3.1455 s, 1.3 MB/s /kernels# dd if=uInitrd of=/dev/sda bs=1MiB seek=20 9+1 records in 9+1 records out 9762728 bytes (9.8 MB, 9.3 Mby jdwl101 - Debian
That’s good news! Annoying that the drive needed to be hot swapped though. After doing the scsi read check if ‘im’ is available to test the loaded image. If it’s good you should be able to use bootm to execute it (and boot).by jdwl101 - Debian
Hi Rich, Try selecting the ide device before trying to read, eg; ide device 1 command. If that doesn’t help give us the output of help ide to see if the ide command has been neutered. Jby jdwl101 - Debian
Check your MTD parts definition. If you have a copy of the stock uboot variables they should give an idea of whether yours are right. I've not seen an updated uboot for the Iomega \ Lenovo boxes, mostly due to the lack of UART booting making testing very risky. If you find one and it works let us know!by jdwl101 - Debian
Hey, There's nothing in your uboot envs that would try to mount an NFS root. To me it looks like the init scripts on your rootfs have NFS entries in them that are being read as starting NFS root. If this is a new build just recreate the rootfs. Make sure you only have 1 partition with the 'rootfs' label and no other drives with a copy of the rootfs or anything. If it'by jdwl101 - Debian
Hey, the variables for the new uboot are not configured to boot stock from Flash. If there's no rootfs partition on any device your box will not boot.by jdwl101 - Debian
Ha! Sorry, I should have checked the age of their wiki guide.by jdwl101 - uBoot
Well done on resurrecting your GoFlex, they're great little boxes.by jdwl101 - Debian
Hi, have you tried tftp booting the kernel directly? On the FreeBSD marvel page their example doesn't use the loader; Booting FreeBSD on Marvell Marvell>> tftpboot 900000 mv5281/kernel.bin Using egiga0 device TFTP from server 10.0.0.204; our IP address is 10.0.2.2 Filename 'mv5281/kernel.bin'. Load address: 0x900000 Loading: ########################################by jdwl101 - uBoot
You will be fine to still boot from usb if you want to. Good catch with the dtb file (8f), the kernel won't boot without it. With that set you will be good to boot. Still get the netconsole running and capture the uboot log.by jdwl101 - Debian
Alternatively, you could set a fixed IP address on the usb rootfs and boot it knowing what IP it should come up as. Could also be a faulty usb port on the box, maybe try a sata rootfs and see if it comes up.by jdwl101 - uBoot
Hi jj, One question, which uboot image did you flash? Your extract says 'uboot.kwb', was it this one? nandwrite /dev/mtd0 uboot.2017.07-tld-1.goflexnet.mtd0.kwb From your envs I take it your wanting to load from sata as well? Everything else looks accurate to me. Though Bodhi may see something that I've missed. Take a look at the netconsole setup, you will want to coby jdwl101 - Debian
Ok, that's odd as well. how about the usb stick you tried? Can you show us the partition table, file structure and contents of /boot? For the u-boot install instructions are here; U-boot download and install thread it should be straightforward as you've shown fw_printenv is present in the rescue system and there's no bad block in the dmesg. Be sure to flash the defaultby jdwl101 - Debian
From the rescue prompt can you see the sata drive? It would be good to see what is in the /boot directory. Though Bodhi's sure to be right about appending the dtb, it's odd to me that the box isn't just crashing when loading the kernel and instead is loading the rescue system from the flash. If you can give us an fdisk -l output and then mount the sata drive and show the diskby jdwl101 - Debian
Hi, Bodhi provides instructions and a root filesystem to boot from usb here; Kernel and rootfs Scroll down to the rootfs instructions at: Updated 24 Jul 2017: Basic Debian stretch Kirkwood rootfs for most Kirwood plugs You will need to follow the 'append dtb to uImage' instructions, then change the u-boot parameters via a serial console to boot from usb.by jdwl101 - Debian
Hi, your Go Flex is booting from the UBI flash partition, not from Bohdi's 4.12 rootfs. To figure out why that is happening you need to print the u-boot variables. If fw_printenv is available from the rescue prompt you maybe able to get it from there, otherwise you will need a serial console and share the serial bootlog. You could also try creating a new boot usb and see if that works.by jdwl101 - Debian
The power usage is that low that WOL is really a headache you don't need. Just set the hard disk to spin down and leave it running.by jdwl101 - Debian
Hi, mine run systemd, generally without issue, except that there can be issues restarting services if /var/run isn't large enough. Not a major problem but can mean more reboots after package upgrades. If I was starting again I'd stick with sysV init. I went with systemd as I know how to write systemd service files and tend to stuff up sysV init scripts.by jdwl101 - Debian
Hi, you haven’t left enough space for the kernel. Load the initrd to 2100000 and it should boot.by jdwl101 - Debian