That's great. Many thanks.by spindles7 - Debian
The SATA partition 1 is the rootfs (newly created), formatted as ext4 (as I am using the latest uBoot) but now has additional software installed etc. Partition 2 is for data eg where samba shares will reside, as I intend to run it as a fileserver. You will recall in an earlier post I asked if it was OK to create additional partitions on the SATA drive. It doesn't seem to have changed aby spindles7 - Debian
OK, here's the session capture log: 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 Hit any key to stop autoboot: 0 GoFlexHome> setenv devices ide GoFlexHome> setenv bootdev ide GoFlexHome> printenv arcNumber=3338 bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs;by spindles7 - Debian
oops, sorry didn't realise the first one had gone onto a 2nd page so sent it again in error.by spindles7 - Debian
Alright, here we go again: 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 Hit any key to stop autoboot: 0 GoFlexHome> setenv devices ide GoFlexHome> setenv bootdev ide GoFlexHome> boot Reset IDE: Bus 0: OK Bus 1: not available Device 0: Model: ST1000DM000-9TS15E Firm: CC92by spindles7 - Debian
Alright, here we go again... 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 Hit any key to stop autoboot: 0 GoFlexHome> setenv devices ide GoFlexHome> setenv bootdev ide GoFlexHome> boot Reset IDE: Bus 0: OK Bus 1: not available Device 0: Model: ST1000DM000-9TS15E Firm: CCby spindles7 - Debian
Ok, here's the log: 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 Hit any key to stop autoboot: 0 GoFlexHome> setenv devices 'ide usb' GoFlexHome> setenv bootdev ide GoFlexHome> boot Reset IDE: Bus 0: OK Bus 1: not available Device 0: Model: ST1000DM000-9TSby spindles7 - Debian
OK, here goes: 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 Hit any key to stop autoboot: 5 4 printenv boot ^C [1]+ Stopped nc -l -u -p 6666 root@raspberrypi:/var/log # fg nc -l -u -p 6666by spindles7 - Debian
Thanks for that, but when I add that to /boot.uEnv.txt and reboot it doesn't work - ie the /proc/cmdline doesn't show the extra parameters and ipv 6 is still active and systemd not running. My environment includes the setting: set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params but custom_params doesn't seem to be gettinby spindles7 - Debian
So, all is booting fine form the rootfs installed on the SATA drive now. I now want to add the boot arguments to /boot/uEnv.txt such as: custom_params=init=/bin/systemd ipv6.disable=1 to enable systemd and disable IP v6 but it ignores anything I enter in that file. What am I doing wrong? Let me know what extra info you need. Once again many thanks for your help. spindles7by spindles7 - Debian
I spoke too soon! It seems that uBoot is ignoring the /boot/uEnv.txt file: root@debian:~# cat /boot/uEnv.txt custom_params=init=/bin/systemd After rebooting the /proc/cmdline entry shows just: root@debian:~# cat /proc/cmdline console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts orion_nand:1M(u-boot),-(rootfs) So I had to add the 'init=/bin/systemd' to the set_bby spindles7 - Debian
Thanks for that. Tried kwboot - the only other arm-based device I have is a Raspberry pi - which seemed to run kwboot, but just hung on the following: ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.goflexhome.mtd0.kwb -p Sending boot message. Please reboot the target.../ I then switched on the GFH and the led on the unit never comes on. The serial port shows the pi sending stby spindles7 - Debian
Ok, adapter has arrived and I've hooked it up. This is what I get with just the rescue memory stick in the usb port: U-Boot 2016.09.01-1 (Oct 10 2016 - 23:11:39 -0600) Arch Linux ARM Seagate GoFlex Home SoC: Kirkwood 88F6281_A1 DRAM: 128 MiB WARNING: Caches not enabled NAND: 256 MiB In: serial Out: serial Err: serial Net: egiga0 88E1116 Initialized on egiga0by spindles7 - Debian
Thanks for that. I now realise that it's not booting into the Arch system, because it boots without any storage attached at all!! Instead it is booting into a rescue partition in the NAND which I had installed earlier; unfortunately the rescue system is not connecting to the LAN, so I can't access it. So I have ordered the serial/USB adapter and will have to wait for that to arriby spindles7 - Debian
bodhi Wrote: ------------------------------------------------------- > > Bad move :) this made it harder for me to help > you. Because now I don't know what's in your > installed u-boot until you can boot Arch again. > Yes, indeed, silly thing to do! > > and now whilst it still boots OK into > ArchLinux, > > (led flashes briefly green then solby spindles7 - Debian
OK that was my fault - in order to show the contents of the uEnv.txt file in the terminal session I used cat > uEnv.txt << EOF. This meant that the environment variables were evaluated, and of course they were not set so the file was wrong. Sorry about that. So I have deleted the swap partition and corrected the uEnv.txt file and tried again. This time, the led flashes green andby spindles7 - Debian
No it's a SATA drive in place of the stock drive that comes with the GFH. There's one ext3 partition and a swap partition and yes, I was logged in as root the whole time. I've re-done the rootfs on the drive - I attach the session text. I used the new uEnv.txt you sent earlier. Now the led flashes green for a few seconds then flashes red and stays that way, so obviouslyby spindles7 - Debian
Many thanks for that. I have tried the new uEnv.txt but the unit still refuses to boot properly. The led just continues to flash green and never stops blinking. Have left it for several minutes with no change. Have set the boot flag on the partition, and tried again, but still no joy. spindles7by spindles7 - Debian
Yes, I can still boot into the Arch system as I am doing the testing on a separate disc. I installed Arch a couple of days ago, so all is recent. Anyway I show below the output of those two commands as requested. cat /proc/mtd: ========== dev: size erasesize name mtd0: 00100000 00020000 "u-boot" mtd1: 0ff00000 00020000 "rootfs" fw_printenv: ========by spindles7 - Debian
Thanks for that. I have tried to get this working but it will not boot. These are the steps I've taken: 1. On a separate disc in the first ext3 partition on the disc, I have created the rootfs using the tarball Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 and labelled it as rootfs. 2. I left the uImage as it came with the tarball. 3. Downloaded and edited the uEnv_arch_uboot_booby spindles7 - Debian
Hi, Came across your website after installing ArchLinuxARM on my GoFlexHome device. I would prefer to use Debian Stretch, so looking for help to get this up and running. I assume I have to replace the Uboot code with the version on this website and then install the latest kirkwood package. However before I start, would appreciate any tips, pitfalls and pointing me to the correct instructioby spindles7 - Debian