Sorry. It was not my intention to go against any rule in the forum. For house keeping. You can delete that post and even this one. I only have thanks from what I have learn from you guys. And from what I am hopping to learn new.by fcopurico - uBoot
rayknight Thanks for your concern. Regards security issues, updates, new vulnerabilities etc. I am one of those guys that do not believe the way all that updated STUFF is been handle. It is ironic how Doors are left open on purpose. Just to tell others they have the latest in updates. A never ending updates that may be the real cause of all. It is easy if you are concern on securitby fcopurico - uBoot
The why in general? I am new to doozan.com and Debian on Arm device. My installation went relative easy, because a friend help. And that I follow Wiki and a few other links here. Openwrt version Why? I do not intent to use Openwrt. Nor to run from NAND. So any version is good enough to be used as a Rescue System. Why exactly 18.06.2 ? Because it was posted here: https://forum.doozby fcopurico - uBoot
If I remove USB I can still boot from OpenWrt in NAND. U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:21:31 -0700) 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 egiga0 Using egiga0 device host 192.168.0.104 is alive [ 0.000000] Booting Linux on physiby fcopurico - uBoot
This is the log running my own Debian Buster with Kernel 4.19.0-18-marvell from USB. Yes the two simple enviroment corrections did the trick. Now it is booting with original bodhi environments. It can still multiboot USB and NAND. I have not tested HDD but It should not be a problem. GoFlexHome> setenv dtb_file GoFlexHome> setenv load_initrd_addr 0x2100000 GoFlexHome> saveenv Goby fcopurico - uBoot
I try to read a little before I posted. But to be honest what you ask was so simple that I did not need to read. I started by restoring my original environment. So I 1) 1rst deleted new items I added setenv usb_boot setenv usb_bootcmd setenv usb_load_uimage setenv usb_load_uinitrd setenv usb_set_bootargs 2) Restore some I did change setenv bootargs 'console=ttyS0,115200 root=Lby fcopurico - uBoot
Can you explain or correct me. fw_setenv dtb_file I guess this in fact clear or delete "dtb_file" variable? Why it is important? Is the same file any way. Well one I did attached at the end of new uImage. The original option I guess points to \boot\dts\kirkwood-goflexhome.dtb But both are the same file kirkwood-goflexhome.dtb? setenv load_initrd_addr 0x2100000 Interestingby fcopurico - uBoot
here is the original env root@OpenWrt:~# fw_printenv arcNumber=2097 bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi) bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_lede bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_by fcopurico - uBoot
So this time I used the alternate method cd /boot cp -a vmlinuz-4.19.0-18-marvell zImage.fdt cat dts/kirkwood-goflexhome.dtb >> zImage.fdt mv uImage uImage.orig mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.19.0-18-marvell -d zImage.fdt uImage mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs--4.19.0-18-marvell -d inby fcopurico - uBoot
So I went to run in an more manual way: cd /boot mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.19.0-18-marvell -d vmlinuz-4.19.0-18-marvell uImage mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs--4.19.0-18-marvell -d initrd.img--4.19.0-18-marvell uInitrd I stop uBoot and used usb reset setenv usb_set_bootargs 'seteby fcopurico - uBoot
I am new here. I own a GoflexHome. I follow your wiki and had success in general. With your latest files I can boot Debian from USB and HDD. So your multiboot environment do work nicely. Even when most of the stuff in the enviroment are strange to me. I have a project in mind where I need to build my owm kernel and OS. The OS is not an issue. But I have trouble with the kernel. It seemsby fcopurico - uBoot