> 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
Multivan, Looks normal. Now shutdown, power up and let it boot without interruption. And post entire the serial boot log here.by bodhi - uBoot
Multivan, > after I send the reset command from terminal > windows uboot continues and openwrt is up. > Do you have and Idea why the start process stops ? Powerup, interrupt serial consle and, printenv boot And post the entire serial console log here (copy/paste everything on the terminal).by bodhi - uBoot
dmb4312, > I guess there are missing NIC modules in both > kernels. Most probably not that reason. But we'll see more info after you tried again with the correction below. Here something you need to correct first. During rootf creation, you've missed the bold part . Quote4. (Stock u-boot only) Create uImage with embedded DTB for booting with older u-boots (2012 or earby bodhi - uBoot
See section 2 in the updated instruction. https://forum.doozan.com/read.php?2,102054,105374#msg-105374by bodhi - uBoot
Cool! let me revise that post.by bodhi - uBoot
Is the curtain call for Debian armel coming? Currently, there is Debian discussion going on about droping armel architecture altogether in trixie (Debian 13). armel includes Kirkwood, and many other old Marvell SoCs without floating point. I hope it will be at least maintained in trixie and planned for obsolescence afterward. That will give us a few more years!by bodhi - Debian
dmb4312, OK so this stock u-boot does not have boot, run, saveenv, and ext2load commands. The only way that you can boot with the USB rootfs is using tftp to load the kernel and then use bootm to boot. So I need to revise this post to add more instruction about tftp. https://forum.doozan.com/read.php?2,102054,105374#msg-105374 1. The problem is we don't have new u-boot for it. Soby bodhi - uBoot
I suspect this problem is systemd related. [ 16.557200][ T1] systemd[1]: systemd 247.3-7+deb11u4 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified) [ 16.582478][ T1] systemd[1]: Detected architecture arm. Welcome to [1by bodhi - Debian
> Power up, interrupt u-boot count down, and then. > > setenv usb_set_bootargs 'setenv bootargs > console=ttyS0,115200 root=LABEL=rootfs > rootdelay=10 earlyprintk=serial' > setenv load_uimage 'ext2load usb 0:1 0x800000 > /boot/uImage' > setenv load_uinitrd 'ext2load usb 0:1 0x2100000 > /boot/uInitrd' > setenv usb_boot 'mwby bodhi - uBoot
> 2. Installed bodhi kernel on mainline Debian 11 -> > no leds Strange! do you have serial console log? is there any error during boot?by bodhi - Debian
All, > Where did you get the kernel you are booting? It > appears to be an actual Debian built kernel, not > one that bodhi supplied on this forum. Debian > does not officially support the Lenovo device, so > they may not have included necessary drivers when > building their kernel. You should try using the > kernel supplied by bodhi. > > Ray Ray is prby bodhi - Debian
Do you have serial console? It might show some errors that we cannot see in dmesg.by bodhi - Debian
alf45tar, I did not see anything strange in dmesg. FWIW, my Marvell Armada 385 boxes (with kernel linux-6.4.11-mvebu-tld-1) and Marvel Kirwood boxes (with kernel linux-6.4.11-kirkwood-tld-1) are showing /sys/class/leds/ content in both Debian 11 and 12.by bodhi - Debian