fermino, Yours is the odd case. The instruction A and B both show that you should create the USB rootfs and flashing new u-boot at the same time. But you are running stock u-boot with Debian. So there are some adjustment during boot that you need to do. ============= Since you have not successfully flashed u-boot and envs images, you can reboot. Stock u-boot will run. Note that if youby bodhi - uBoot
Ah OK. I'll upload a new version.by bodhi - uBoot
> I don't know if that's a problem but DS411j have > diferent SoC and less DRAM. Find attached file. That's OK. 6281 and 6282 are nearly identical. And less DRAM should be OK. > Also slim has DDR3 and j has DDR2 I did not look at the specs closely. That's most likely the reason it does not work. ======== The NSA325 u-boot can only be used to kwboot, itby bodhi - Debian
FermÃn Olaiz, > Hi! I am following the B guide (using the > 4.12.1-kirkwood-tld-1 rootfs). Note Step B.2 in the installation instruction. QuoteB. Installation from the latest Debian rootfs - If you have installed the latest Debian rootfs, but your u-boot is still stock, then follow all the steps in this section B. - If you are upgrading from uboot.2016.05-tld-1 then you oby bodhi - uBoot
Before we go too far, please try running the same kwboot test again, but this time use this new Synology 411j u-boot: https://forum.doozan.com/read.php?3,135762by bodhi - Debian
Hi Schnee, > Hi, I am trying to add wifi to a pogoplug V4 with > an old USB wifi. It seems it requires zd1211rw.ko > module, but it is not avaialble. > > Is there a "howto" to compile a module? I forgot the add this Wifi module the last time somebody mentioned it! (this module is already in the kernel). I will do that for the next release. If you cannot waiby bodhi - Debian
Reserved.by bodhi - uBoot
It's up in the new thread. https://forum.doozan.com/read.php?3,135762 It'll be a bit rough. I only spent a couple hours to roll it, and have not done any testing. Hopefuly USB and SATA will work.by bodhi - Debian
See here for the new u-boot: https://forum.doozan.com/read.php?3,135762 Please post your kwboot log in the u-boot thread.by bodhi - uBoot
This is the work-in-progress version. Only run kwboot to test (it is not ready to flash to SPI yet). ================= Update 26 Sept 2023 Download at Dropbox uboot.2023.04-tld-1.ds411j.bodhi.tar md5: 53c2f137e946517b2f792c247b300122 sha256: 39f50601260539bc8add2efa896e3565c1f5d44d0b7084cecc466290e2219506 There are 5 files in this tarball. uboot.2023.04-tld-1.ds411j.kwb uboot.2by bodhi - uBoot
Stay tuned, I will upload the new and shiny ds411j u-boot tomorrow!by bodhi - Debian
I see. The GoFlex Home GPIOs would be in conflict with the DS411j Fan GPIO.by bodhi - Debian
Here is the website where I found the GPL source long ago: https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/24922branch/6281-source/ It seems they have moved or removed the GPL source folder somewhere. We need to look for this u-boot (in their latest branch) u-boot-mv-3.5.9by bodhi - Debian
> Not sure what you mean, is there anything you want > me to do regarding this? thanks. Not sure yet what you can do on your side. It might be that the kernel DTS is wrong. Does any of the fans run upon power up? does it stop at some point during boot and start again?by bodhi - Debian
There are 2 errors in this boot. By default, the new u-boot expects the uImage be the original one without the DTB embedded. The real fix is a 2 step process (u-boot and rootfs). So try this quick fix in 1 step first, and later we'll do the real fix. Run kwboot, with the USB rootfs attached, power up, and interrupt u-boot at count down and setenv dtb_file Also get the current lisby bodhi - Debian
Nefarious19, > So far, I tried few u-boot's from bodhi, > and one for NSA235 seems to work. I even booted > kernel, however, It panicked. Can someone help me > to get my box work again? If you want to boot Debian with th NSA325 u-boot, post the entire serial console boot log (from the kwboot command to the kernel panic). If it booted then the panic is most likely notby bodhi - Debian
> Yepp, there are 2 fans, both are sharing the > voltage somehow because when I remove one, the > second is running even faster I think so. Since there is only one gpio fan node in the DTS. And it failed to initialize [ 35.947234] gpio-fan: probe of gpio-fan-150-15-18 failed with error -524 This is where it should be investigated first.by bodhi - Debian
There are 2 fans, so are they both running at full speed? Let's do this first: QuoteInstall fancontrol to see if it will help.by bodhi - Debian
Install fancontrol to see if it will help. Hold on, I missed that error in your boot log [ 35.947234] gpio-fan: probe of gpio-fan-150-15-18 failed with error -524by bodhi - Debian
I remember now. This SoC does not have kirkwood-thermal. How about hwmon? ls -l /sys/class/hwmon/by bodhi - Debian
Try To see the exact path and name of the leds: ls -l /sys/class/leds/ and then see what is the current trigger: cat /sys/class/leds/ix4-300d:hdd:blue/trigger cat /sys/class/leds/ix4-300d:hddfail:red/trigger And then try to turn it off: echo none > /sys/class/leds/ix4-300d:hdd:blue/trigger echo none > /sys/class/leds/ix4-300d:hddfail:red/trigger And then try to turn itby bodhi - Debian
Also please change the Subject of the 1st post of this thread to Debian on Synology DS411j. And add a reference to the original u-boot thread. I will move this thread to the Debian subforum.by bodhi - Debian
Check the sysclass for thermal. ls -l /sys/class/thermal/cooling_device* ls -l /sys/class/hwmon/ And see what are they. cat /sys/class/thermal/cooling_device0/cur_state cat /sys/class/thermal/cooling_device0/max_state cat /sys/class/thermal/cooling_device0/typeby bodhi - Debian
> I recompiled the mainline kernel with > > > CONFIG_GPIO_74X164=m > > > and now I have 5 leds on /sys/class/leds Cool! > > > ix4-300d:hdd:blue ix4-300d:hddfail:red > ix4-300d:power:white ix4-300d:sys:blue > ix4-300d:sysfail:red > > > They are working pretty well except > ix4-300d:hddfail:red that it is always on. Letby bodhi - Debian
LeggoMyEggo, > Looking at some of the other legacy type hardware, > maybe 32 bit i386 could share the same fate? Saw > that the availability of hardware to grind out the > code and test is becoming an issue as well as > finding people interested in maintaining. I'm afraid so. Definitely 32 bit i386 is already on the way out. I think when things are running OK, old aby bodhi - Debian
dmb4312, > Did some tests and can confirm that dreamplug and > hp t5235 dont boot and hang at DRAM OK. > back to the goflexhome boot with devices=usb > it sees all the drives as earlier, attached > console output and dmesg below. > I have 2x120G and 2x240G SSDs inserted Cool! > Another thing I noticed is that fans are running > at 100 percent speed.by bodhi - Debian
dmb4312, > now that the system has been testet and working ok > with bodhi kernel(5.13.6-kirkwood-tld-1)and stock > uboot(ancient) > > Im willing to try to use new uboot to make this > box permanent auto-boot > what is the a proper way to boot bodhi kernel with > new uboot? Good works! As you found out, just ignore the SATA drives during boot will get iby bodhi - Debian
alf45tar, > http://lists.infradead.org/pipermail/barebox/2015-April/023137.html Yes, that's a very good find! even though it is specific to barebox bootloader. It makes a lot of sense that it got to mainline Linux kernel eventually. Because the GPIO LEDs were deferred probe but the kernel never tried to probe it later, that made me think there must be dependency not met somewherby bodhi - Debian
dmb4312, > > root@debian:/# cd /boot/ > root@debian:/boot# cat dts/kirkwood-ds411j.dtb >> > zImage.fdt > root@debian:/boot# mv uImage uImage.orig > root@debian:/boot# mkimage -A arm -O linux -T > kernel -C none -a 0x00008000 -e 0x00008000 -n > Linux-5.13.6-kirkwood-tld-1 -d zImage.fdt uImage > Image Name: Linux-5.13.6-kirkwood-tld-1 > Created:by bodhi - uBoot