rkachowski, This indicated that your USB rootfs partition is bad. ** No partition table - usb 0 ** ** No partition table - usb 0 ** ** No partition table - usb 0 ** Redo this USB rootfs. But use fdisk to wipe out partition table first, and create a brand new partition.by bodhi - Debian
raffe, Replace these steps with commands 28. printenv usb start ext2load usb 0:1 0x800000 /boot/uImage 29. ext2load usb 0:1 0x2100000 /boot/uInitrd 30. setenv console 'console=ttyS0,115200 mtdparts=spi_flash:0x78000@0(uboot),0x1000@0x78000(env)' setenv bootargs_usb 'root=/dev/sda1 rootdelay=10 earlyprintk=serial' setenv bootargs '$(consby bodhi - Debian
rkachowski, 1. Regarding serial console > what i've found is that > when all the leds turn on dim and wait there, the > TX connector needs to be removed and immediately > reattached to continue the boot process. from > there i can interrupt the autoboot and get into > the console. Or run kwboot as instructed in the installation post: https://forum.doozan.cby bodhi - Debian
I did not have the privilege to get to know CompuServe. But not because I was too young, I think I was too busy working jobs and trying finish graduate school back in those days :)by bodhi - Off-Topic
kekeke, Please post the entire bootlog, from u-boot banner until it stopped (a snippet of log is never helpful!).by bodhi - Debian
Shogun, I've updated the instruction to include this 2nd part. QuotePart 2 ==== After following the instruction in Part 1, and you still found that you cannot boot into Arch. Follow these steps: 1. Mount the Arch rootfs on another Linux box, and verify whether you have a uInitrd in /boot. Normally Arch does not ship with initrd. 2. If there is no uInitrd in Arch rootfs /bby bodhi - uBoot
Shogun, These errors are OK: Unknown command 'mmc' - try 'help' ## Unknown partition table type 0 ## Unknown partition table type 0 ## Unknown partition table type 0 ## Unknown partition table type 0 ## Unknown partition table type 0 ## Unknown partition table type 0 ## Unknown partition table type 0 loading envs from usb 0 ... ** Bad deviceby bodhi - uBoot
kekeke, > Booting from SATA ... > AHCI init for unit0 > Target spinup took 0 ms. > SATA link 1 timeout. > > Error: SCSI Controller(s) 1B4B:9215 1B4B:9235 not > found > scanning bus for devices... > > Did it hang here?by bodhi - Debian
raffe, > Now I read in > https://forum.doozan.com/read.php?2,12096 that > "Note: all steps below must be done while logging > in as root user (not sudo). If you are not the > root user then don't continue, because the rootfs > will not work.". This I have not done when I > worked on Ubuntu. Could that be the problem? Yes, there will be quite many prby bodhi - Debian
kekeke. Quote> see any output. I tried to change to rx-rx, tx-tx > and got same results. I tried on mac,win,linux > (using kwboot, putty, picocom, screen), tried > different laptop, but everything is useless. > > P.S. When I'm removing jumper that stated as tx on > your schema systems continues to boot normally. > It is expected. NAS326 box behaves this wby bodhi - Debian
Shogun, I'll be back and explain why and what need to be done when you boot Arch rootfs (it is different from booting Debian rootfs). The link I posted is part 1. In your case it needs a part 2.by bodhi - uBoot
Shogun Wrote: ------------------------------------------------------- > I appreciate your response so much bodhi. After a > few days off and some fresh thinking thanks to > your inspiration I got back in! > > > Things I learned: > > I had the public key stored safely in backup after > all (compared public key in authorized_keys with > keys I had backedby bodhi - uBoot
kekeke, HDD post above: https://forum.doozan.com/read.php?2,41874,42084#msg-42084 > My initial printenv output: > https://pastebin.com/DpKnA6Em > Before reboot: https://pastebin.com/j7YWMKDi > After removing HDD and booting to stock os: > https://pastebin.com/BX57SCPh > After applying your recommendations above: > https://pastebin.com/KMmHM114 At this point yby bodhi - Debian
NAS326 serial console Connect only GND, RX, TX (dont connect 3.3V power). +----+----+ | | | +----+----+----+----+----+ |3.3V| TX | RX | | GND| +----+----+----+ +----+by bodhi - Debian
@kekeke, > I tried to debug using netconsole > (https://forum.doozan.com/read.php?3,14), but no > luck either. Just empty output on nc. Stock u-boot does not have netconsole. @all, Serial console is absolutely necessary when you start hacking these embedded Linux boxes. Serial console is not just for trouble shooting purpose, it's also a tool for learning Linux, becausby bodhi - Debian
rkachowski, Try one more time. After logging int the stock OS fw_setenv change_boot_part 1 Sync, and reboot. ----- Note: Your envs look fine. Nothing wrong with them. change_boot_part is reset to 0 each time the stock OS booted successfully, so it is no surprise that it is 0. It could be that this problem has something to do with the USB rootfs itself. But we cannot see tby bodhi - Debian
rkachowski & kekeke, pastebin is quite hard to read. Next time please post here in code tags. Except for the boot log, everything else is easier to troubleshoot if in code tags. Here is rkachowski's output of fw_printenv CASset=max CONTRY_TYPE=FF FEATURE_BIT=00 MALLOC_len=5 MODEL_ID=B303 MPmode=SMP PRODUCT_NAME=STG-328 VENDOR_NAME=MitraStar Technology Corp. autoload=noby bodhi - Debian
balanga, We have a Wiki thread: https://forum.doozan.com/read.php?2,23630 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 tftpby bodhi - uBoot
balanga, No. The commands I posted are to be excuted at serial console prompt (replace xxx and yyy with real number). Not in Linux shell. setenv ipaddr 192.168.0.xxx setenv serverip 192.168.0.yyy tftp 0x800000 uImage tftp 0x1100000 uInitrd tftp 0x1c00000 kirkwood-goflexhome.dtbby bodhi - uBoot
kekeke Wrote: ------------------------------------------------------- > After putting USB stick from rear to the front > port and doing what you said above, I was able to > boot to Debian. Cool! thanks for reporting this kekeke. The rear ports are USB 3.0. So the rootfs need to be attached to the front port.by bodhi - Debian
Ok. Looks like they have not changed the FW in anyway to prevent my env hack. I can confirm this by the look of the u-boot envs listed. Something has prevented you to boot from USB, and the fall back menchanism in the envs has caused it to reset to boot kernel 2 from NAND. Let's reset these to boot from kernel 1 address, so it will boot from USB rootfs. fw_setenv curr_bootfrom 1by bodhi - Debian
By the way, you are running an old rootfs (4.4). But it is an LTS kernel so it's OK. However, then you upgrade this rootfs to the latest kernel, you will need to adjust fstab a little bit to conform to the new rules regarding rootfs device. Your root device should look like this in /etc/fstab: LABEL=rootfs / ext3 noatime,errors=remount-ro 0 1by bodhi - uBoot
balanga, Quote> U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:21:31 > -0700) > Seagate GoFlex Home > Found bootable drive on usb 0 > loading uImage ... > 3154896 bytes read in 1129 ms (2.7 MiB/s) > loading uInitrd ... > 7179935 bytes read in 1169 ms (5.9 MiB/s) > loading DTB /boot/dts/kirkwood-goflexhome.dtb ... > 10605 bytes read in 2721 ms (2.9 KiB/s) &by bodhi - uBoot
raffe, > What do you think about this one? > https://www.ebay.com/itm/1pcs-USB-2-0-to-TTL-UART-6PIN-Module-Serial-Converter-CP2102-STC-PRGMR-Cable-BE-/201709769604?_trksid=p2385738.m4383.l4275.c10 This one is good. It's the right one when you see CP2102 and the pic looks like that.by bodhi - Off-Topic
rkachowski, I need to see how the envs got reset to in stock OS: fw_printenvby bodhi - Debian
Maarten, ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.pogo_v4.mtd0.kwb -p > Sending boot message. Please reboot the > target.../ > Sending boot image... > 0 % [.+.+xmodem: Protocol error This actually looks good. It's the Pogo V4 quirk. You need to recall (up arrow) the kwboot command above and execute it again, repeatedly a few times, until the handshby bodhi - uBoot
balanga, Since you have decided not to use Arch u-boot, don't use Arch definition of 2 mtds. You might as well set it to the traditional definition of 4 mtd partitions: fw_setenv mtdparts 'mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)'by bodhi - uBoot
Shogun, > I have a GoFlexHome that I recall installing > ArchLinuxARM onto years ago. > Is it possible to get this to boot a flash drive > instead of its internal OS? It is definitely possible. 1. "years ago", do you remember which year? it is important to know the time period. Because ALARM has 2 different u-boot version over the years. We do too. At the earby bodhi - uBoot
Thanks for uploading prahal! > On my side I learned that one ought not to run > picocom in parallel to kwboot ... else kwboot > upload has errors "+" instead of "." and ends up > freezing. Indeed! kwboot is a serial console terminal by itself (after loading u-boot image). So running picocom along side would interfere with it, and there is no reason to do sby bodhi - uBoot