bennytheben, This should be easy to solve since you have serial console. With serial console connected, and both the USB rootfs and the HDD attached, power up. Interrupt serial console, and printenv boot Please post the entire serial console log here.by bodhi - uBoot
Carlo, See here: https://forum.doozan.com/read.php?2,56989,57049#msg-57049by bodhi - uBoot
Try setenv bootdev usb setenv device 0:1 setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial' setenv load_dtb_addr 0x1c00000 setenv load_initrd_addr 0x1100000 setenv load_uimage_addr 0x800000 setenv dtb_file '/boot/dts/kirkwood-dockstar.dtb' setenv load_dtb 'echo loading DTB $dtb_file ...; load $bootdev $by bodhi - Rescue System
Carlo, > if i give ... > > /usr/sbin # /usr/sbin/flash_erase /dev/mtd0 > 0xc0000 1 > -/bin/sh: /usr/sbin/flash_erase: not found > > > should i use flash_erase from > this > tar? Yes. > or use the default flash_eraseall? No. You are not erasing all of mtd0, only 1 block inside it.by bodhi - uBoot
Kernel linux-4.16.1-kirkwood-tld-1 package has been uploaded. Please see 1st post for download link. From this kernel and future releases, to check CPU vulnerabilities: grep . /sys/devices/system/cpu/vulnerabilities/* /sys/devices/system/cpu/vulnerabilities/meltdown:Not affected /sys/devices/system/cpu/vulnerabilities/spectre_v1:Not affected /sys/devices/system/cpu/vulnerabilities/spby bodhi - Debian
Bennytheben, > You say blocks 0 - 7 are the ones to watch out > for. I'm not sure if you're referring to the first > number (in decimal) or the hex number (which I > don't know how to read), but I assumed you meant > the decimal number and went ahead to the next > step. Maybe you could make the instructions > slightly clearer for people who are newbiesby bodhi - uBoot
Carlo Wrote: ------------------------------------------------------- > hi, > i've followed your instructions, put the debian > system (i didn't get the linux file) where it > should be, i've gone one with the uboot procedure, > but as i checked w_env.config i noticed that's not > mtd0 > > > / # cat /etc/fw_env.config > # Configurationby bodhi - uBoot
habibie, A couple things to do/look at: 1. Log in with serial console if you have one, and regenerate SSH keys. Or mount this drive on another Linux box and chroot into it to do that. 2. Look at the sshd rules in its config file for allowing root log in. If it is indeed set up to disallow root login, you could try log in with alarm user instead of root. And then change this rule.by bodhi - uBoot
Geah Heh, > Now the box appears totally up. I am going to > further venture in apt upgrades and update to your > latest kernel as well. Thanks again for your great > contribution to the community! Cool! The mtdparts syntax is a little bit confusing. But that was the established precedent in u-boot env and Linux kernel so I did not want to use a better variable name for u-bby bodhi - Debian
rynax, https://forum.doozan.com/read.php?4,54044,57009#msg-57009by bodhi - Rescue System
Geah Heh, Ah! I forgot. 1. With the new kernel, the mtd driver must be orion_nand 2. The env needs an extra mtdparts fw_setenv mtdparts 'mtdparts=orion_nand:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2)'by bodhi - Debian
Geah Heh, Cool! You should set them permanently using fw_setenv.by bodhi - Debian
alexinc, Let see if you can boot with RAM version and then you decide how to go from there. Download this file to the top folder of a USB drive (formatted as Ext3): lede-17.01.4-oxnas-stg212-u-boot-initramfs.bin Power up, interrupt serial console at the 1st stage u-boot (I think the 2nd stage is also work). And then setenv to boot. usb start setenv mtdparts 'mtdparts=41000by bodhi - Rescue System
Geah Heh, Your bootargs env was set incorrectly. It got concated with old info: [ 0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/nfs rwby bodhi - Debian
Last post moved here: https://forum.doozan.com/read.php?2,56989by bodhi - Debian
Carlo, > or straiglt follow instructions in uboot and > kernel/rootfs post? This.by bodhi - uBoot
echowarrior, > this way if a sd card were to > fail I could open up the case to change it out > without unscrewing the board and disturbing the > power wires and all that, it may be overkill > though, lol. :) Sounds good! not overkill at all. It is true that SD card will need to be replaced at some point if writing too much to it.by bodhi - uBoot
Carlo, They look OK. 512 -rwxrwxrwx 1 nobody root 512.0K Apr 13 2018 mtd0 1024 -rwxrwxrwx 1 nobody root 1.0M Apr 13 18:42 mtd0-originalby bodhi - uBoot
habibie, devices=usb ide disks=0 1 2 3 4 5 6 7 dtb_file= The above is correct, to remove the dtb_file env so that the boot commands will not try to use it. > I would like my Seagate GoFLEX Home to boot > and/or run ALARM (Arch Linux ARM) OS. So, I > downloaded and extracted the > ArchLinuxARM-2018.04-kirkwood-rootfs.tar.gz > on a USB memory stick and notice its /bootby bodhi - uBoot
habibie Wrote: ------------------------------------------------------- > Boshi, > > I am not asking for help on how to build and/or > compile any versions of Linux kernel which I > already know how to do that. All I asked is the > scripting file used on the debian buildroot tree > to package the compiled binary kernel files as a > package. This kernel packageby bodhi - Debian
echowarrior108, That configuration would defeat the purpose of having an internal storage drive contained inside the box. If you need to add SD card reader/writer to this box and access it outside, then why don't you just plug in an external USB SD card reader/writer? There are 4 USB ports available, which you can also plug in more USB hubs. The mods you did is nice because it woby bodhi - uBoot
joerg_999 Wrote: ------------------------------------------------------- > no, i dont think so, the dtb file seems also > correct: > 10106 Feb 10 00:14 kirkwood-pogo_e02.dtb > > curios?!? > > SOLVED! > maybe you was right Bodhi, i created a new > filesystem and generate a new uImage / uInitrd > with kernel 4.15.2 took the new dts files for Pogo > andby bodhi - Debian
Gravelrash Wrote: ------------------------------------------------------- > i reckon bodhi has the most,,,, cornered the > market comes to mind :))) :))) I have too many :) I also got a HP Thin Client still in box. This Marvell one was reported by Ray. It is as cheap but more powerful than the T5325 (with 1GB RAM). I need to look at the model and let you know.by bodhi - Off-Topic
Dieter, > Probably, because the uboot is too old to handle > so many arguments per command? True. > PS: I still have it running, can I switch it off? Sure, you did not save anything. Let me write a few envs. I was hoping I can use the script, but it is too new for this u-boot.by bodhi - Rescue System
joerg, Quote> > root@debian:~# cat /etc/fw_env.config > # MTD device name Device offset Env. size > Flash sector size Number of sectors > /dev/mtd0 0xc0000 0x20000 0x20000 > seems to be OK. Yes. That's the correct address. Is the memory error about something "too few addresses within range"? If that was, look at your /boot/dts/kiby bodhi - Debian
Manuel, I'll think of some other way for you to try. If I have a chance to open my box this weekend (doubt it :). I will play with it some more.by bodhi - Debian
Carlo, > > / # ls -lh mtd0.nsa325 > -rw-r--r-- 1 root root 1.0M Apr 12 14:52 mtd0.nsa325 > The nanddump was OK. Note the size is 1M even. It means there is no OOB. Stock OS did not recognize -noecc option. It is OK. However, you could have used the NAND dump binary I provided in the u-boot installation thread. https://forum.doozan.com/read.php?3,12381 Quoteby bodhi - uBoot
habibie, The Makefile is always in the kernel source tree. Basically, I have no customization on top of the kernel tree, other than the code patches, and the config file. Building kernel packages instruction can be found on the net, litterally hundreds of hits when you search for it. Just to clarify, as a matter of policy, I don't discuss building kernel or u-boot, because it will addby bodhi - Debian
Nice :) So now we can file it as a kwboot success story. It is safe to save envs now. We should proceed working on booting the kernel with uInitrd. There is plenty of memory so move it to setenv mtdparts 'mtdparts=armada-nand:-(ubifs);spi1.0:0x00100000(uboot),0x00010000@0x00100000(uboot_env)' setenv load_dtb_addr 0x1000000 setenv load_initrd_addr 0x3900000 setenv load_iby bodhi - Debian
On another Linux box, mount the Debian rootfs that you meant to run on this Dockstar and put the attached u-boot script in the /boot folder (if it was mounted at /media/sdb1): cp -a uboot.2016.05-tld-1.environment.scr /media/sdb1/boot/ Power up this box and interrupt serial console, run the script loading commands: usb start ext2load usb 0:1 0x800000 /boot/uboot.2016.05-tld-1.environby bodhi - Rescue System