antrew Wrote: ------------------------------------------------------- > I know it's not Christmas, but I accidentally > wrote this script after reading this thread. It > will randomly switch on and off random LEDs. > > > #!/bin/bash > > cd /sys/class/leds > > LEDS=(*) > ONOFF=('none' 'default-on') > > while true ;by bodhi - Debian
FrancYescO, > to recover MAC address (fw_printenv ethaddr > returns 00:11:22:33:44:55): > > ip link set dev eth0 address $(dd if=/dev/mtd0 > bs=1 skip=1046528 count=17 2>/dev/null) > > and probably also need to edit in the 8th row of > /root/set_persistent_mac_address That's not as good as getting from ifconfig. MAC address can be changed, and the oneby bodhi - Debian
Miclaud, The envs image from the HDD is not good (or non existent). *** Warning - readenv() failed, using default environment The default envs are set up to boot the USB rootfs. Is that what you wanted to do? or are you trying to boot HDD rootfs? what is on the USB drive? I guess you need to post info about this HDD. What files/partitions are in it? The bottom line is you needby bodhi - uBoot
I saw you've update the post above. Let me take a look.by bodhi - uBoot
Wladislaw, We have moved on to the new u-boot and rootfs/kernel for this box a long time ago. For this NSA325 box, the reboot every 35 seconds is the HW watchdog in action. When the system is stalling for a while, the watchdog kicks in and restart the box. In the new u-boot, I've turned off the watchdog so it will not interfere with the system booting. My suggestion: boot the boby bodhi - uBoot
> I am glad I know where I am:) Be careful now, you don't want to to have to call Tech Support to know where you are (cue Tom Cruise running in the parking lot yelling) :Dby bodhi - uBoot
mervin, > init_sata_power is the smallest issue here, I > would say to get 1st sata running without issues > its the main thing. Not really! I meant the 2nd SATA only (and only if 3.5" HDD is used). The 1st SATA has been working OK for both 2.5" and 3.5" HDDs. And the 2nd SATA has been working fine for 2.5" HDD. If you meant you have issue with a single SAby bodhi - uBoot
Added to the Wiki. QuoteVPN Setup OpenVPNby bodhi - uBoot
Hi mervin, I think I need to modify the DTS to fix this problem once for all. However, as I recall the init_sata_power must be used always. Let me take sometime (in the next few days) and will upload a new DTB for you to test.by bodhi - uBoot
Miclaud, As always, I need to see the complete picture of what's going on. Interrupt serial console at count down printenv and then boot Please post the entire serial boot log, from the u-boot banner.by bodhi - uBoot
jcromero, > Is this working? It should work for boxes that have RTC such as the GoFlex Home, and other Kirkwood boxes. It was a long time ago, but I recalled making it work for boxes that have no RTC, too (I could be remember it wrong, though). When I have some time, I'll reboot my GoFex Net to investigate this.by bodhi - uBoot
fratzicu, Yes. Kirkwood stock u-boot images are usually 4 blocks. The built image is smaller, but we round it up to 512K to make it easier to flash to NAND. As I've mentioned above, I think you should move on to work on the kernel DTS. This has to be done so that you understand the box HW and can run the Kirkwood kernel with the DTS. Don't dwell on the NAND stuff, it is not impoby bodhi - uBoot
fratzicu, > My yoal is maybe put my device in your supported > list of u-boot and kernel and put openwrt on it. Stock u-boot should work fine. Since you have JTAG, as long as you can load u-boot image and run it, you have a rescue path. More important is the new kernel DTS for this Wireless Space version of the Lacie. That would be the same DTS for Debian and OpenWrt. Just gettingby bodhi - uBoot
fratzicu, > So I should find the expected location of the env > in the source code for u-boot used to compile it, > right? Correct. It should be defined in ./include/configs/*lacie*.h (or some similar name header file). Usually the envs location is at one or more blocks after u-boot in the 1st MB. For stock Kirkwood it is usually at the 640K location, my u-boot version uses 76by bodhi - uBoot
mervin, > and otber bit from hdd. Now I got same feeling as > hdd get initialized in debian then linux start > looking for rootfs on hdd instead of usb Not likely, since your bootargs is correct: [ 0.000000][ T0] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:0x100000(uboot),0x80000(uboot_env) The kernel will look for a parby bodhi - uBoot
"RAIDar" That brought back some memory. I use to have a ReadyNAS (SPARC arch) a very long time ago. But forgot all about the details.by bodhi - uBoot
fratzicu, I'll answer number 1, and let joerg look at number 2. > *** Warning - bad CRC, using default environment At this point your u-boot envs are from the internal settings. This u-boot could not find the valid envs where it expected to find. > If I put there the generated uImage and uInitrd it > stops at loading kernel image > > 5316528 bytes read in 387 mby bodhi - uBoot
Miclaud, QuoteI'm afraid that stock u-boot will be booting again he uImage in sector 1290, ignoring your updated kernel first HDD partition (but I could be wrong). Is there a way to configure stock u-boot to look for first HDD partition instead of sector 1290 for uImage kernel? Let me recap what I understood about this box from scanning mai8b, sobir, and your posts again. 1. This bby bodhi - uBoot
AkkJaa,, Cool! so now we know that you can boot with the HDD in the box. But the bootcmd env was reversed to stock rescue. mtdparts=mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) usb_boot=run load_uimage; if run load_uinitrd; then bootm 0x2000000 0x3000000; else bootm 0x2000000; fi usb_bootcmd=runby bodhi - uBoot
mervin, The bootargs mtdparts env was wrong in this boot. mtdparts=orion_nand:0x100000(uboot),0x80000(uboot_env) Power up. Interrupt serial console and setenv mtdparts 'mtdparts=orion_nand:0x100000(uboot),0x80000(uboot_env)' printenv And then bootby bodhi - uBoot
AkkJaa, So this u-boot version is similar to a few others we have seen, that the bootcmd is always reset to bootcmd=usb start;fatload usb 0:1 0x2000000 /uImage-recovery;fatload usb 0:1 0x3000000 /initrd-recovery.gz;nand read 0x1000000 0xD4000 0x6000; bootm 0x2000000 0x3000000 0x1000000 To verify that was because of the HDDs are in the slot, repeat this sequence: 1. With only USB rootfsby bodhi - uBoot
vzhilov, > Just a remark, I don’t have any HDD attached to > the device, only the flash drive which I use to > boot the kernel. Can that be a problem? Of course. There must be a rootfs somewhere on your system to boot into Debian. The kernel has started to boot: Uncompressing Linux... done, booting the kernel. Booting Linux on physical CPU Ox0 Initializing cgroup subsyby bodhi - Debian
echowarrior108, Thanks! I think it's a good example of how to start using OpenVPN. Even though it is too specific to this provider, installation procedure for other providers probably very similar.by bodhi - uBoot
jcromero, That's not how you should do it. dpkg --contents linux-image-5.11.4-kirkwood-tld-1_1.0_armel.deb | grep wireguard The command above does not really tell you anything. Check the kernel config file like this: grep -i wireguard config-5.11.4-kirkwood-tld-1 CONFIG_WIREGUARD=y # CONFIG_WIREGUARD_DEBUG is not set And after you installed and run the box with the kernelby bodhi - Debian
jcromero, > Previously, I have installed manually the > linux-headers-5.2.9-kirkwood-tld-1_1.0_armel.deb > package in /boot, but the wireguard module is not > build > > Am I missing anything? Upgrade the kernel to the latest linux-5.11.4-kirkwood-tld-1-bodhi.tar.bz2 (or at least 5.6.x). It was only available in my kernel builds since 5.6.x-kirkwood-tld-y.by bodhi - Debian
Hybrid_Greg, > So it happened! I bricked my Stora last night, > when tried to flash new U-boot. > It's completely dead, fan is spinning as soon as I > connect power and no serial output at all. > I'm trying to use kwboot, but can't get past > > root@debian:/home/user/Desktop/kwboot-tool# > ./kwboot -t /dev/ttyUSB0 -b > uboot.2017.07-tld-1.neby bodhi - uBoot
echowarrior108, > What is cool is I look back and see that in 2 days > it will 3 years running this sandisk microsd card > and it still works after running nearly 24/7!!! > Was glad you posted about which brand to use and > you called it right. I can't wait to see how long > this runs because I run weekly debian updates as > well and try to check the drive now fby bodhi - uBoot
Hybrid_Greg, > I'm currently flashing uBoot and recieving the > following error: > debian:/boot# nandwrite /dev/mtd0 > uboot.2017.07-tld-1.netgear_ms2110.mtd0.kwb > Input file is not page-aligned. Use the padding > option.-tld-1.netgear_ms2110.mtd0 > nandwrite: error!: Data was only partially written > due to error > error 0 (Success) >by bodhi - Debian
Miclaud, > My question - as a beginner with u-boot related > matters - is: could it be a possibility to > chainload your newer u-boot (installed in a > /dev/sda1 partition) from olderzeus's 1.1.2 > u-boot? If possible maybe I can boot from there > with your latest oxnas kernel and rootfs. Not likely to work. That u-boot is too old. Chainload is tricky and wonby bodhi - uBoot