Ivan, > You have put this in the last post: > Quotebodhi > cat dts/kirkwood-ds112-v10j.dtb >> zImage.fdt > > > That file doesn't exist. I've attached the DTB to this post. Recreate the uImage. cd /media/sdb1/boot cp -a zImage-6.11.6-kirkwood-tld-1 zImage.fdt cat dts/kirkwood-ds112-v10j.dtb >> zImage.fdt mkimage -A arm -O linux -T kernby bodhi - Debian
@Anonymous, > I guess I can't use armhf? Not armhf. This SoC is ARMv5TE (i.e armel). > Here is the new log, with fixed network settings > and new dtb (see uImage built on newer date, while > initrd is old). So you are booting with the new DTB above from kirkwood-promwad.dt.250418.tar. > Bad blocks serial numbers, mac > addresses censored No need to ceby bodhi - Debian
> I managed to boot into original u-boot, but not to > debian: Cool! > Error: invalid dtb and unrecognized/unsupported > machine ID Remember when you boot Debian with stock u-boot you had to append the DTB to uImage? So now all you need to do is to use that uImage, or create a new one. Take your USB rootfs to another Linux box and recreate it. Assuming it's mounted atby bodhi - Debian
Ivan, > Unfortunately, it seems that I would have to > bother you for another u-boot build. It's OK! we still have unknowns to figure out. The rescue u-boot will enable the testing of the 2nd HDD bay too. https://forum.doozan.com/read.php?3,138456 QuoteThis u-boot currently can boot USB rootfs. When booting with USB rootfs, both bays can host large disks (e.g. 3TB or 12TB)by bodhi - Debian
Looks like Synology caused a backlash with their new requirements for hard disks. Probably their executives got greedy. https://arstechnica.com/gadgets/2025/04/synology-confirms-need-for-synology-branded-drives-in-newer-plus-series-nas/ Perhaps we will see more used Synology NAS on eBay :)by bodhi - Off-Topic
BayPanard, Attached here is the new u-boot for Synology DS112. uboot.2024.10-tld-1.ds112.250421.tar md5: 91910852e51c03871c1977f312e2598f sha256: d3dab0b1c6a5cadc75d1f6d2affff56ebf90ab323a32ee102bebe9b7b714bfe9 This tarball includes 5 files uboot.2024.10-tld-1.ds112.kwb uboot.2024.10-tld-1.ds112.environment uboot.2024.10-tld-1.ds112.environment.img uboot.2024.10-tld-1.ds112.boby bodhi - Debian
Ivan, > It seems that i messed up my env. I was trying to > add net console capability, and seems that over > serial console some characters got gobbled up and > I probably messed up my env. Now I can't boot the > uboot. > > I get this in the serial console and it just get's > stuck there: > > U-Boot 2024.10-tld-1 (Dec 02 2024 - 12:37:41 >by bodhi - Debian
Look in the Wiki thread to see if people have benchmarks for Samba file transfer. QuotePerfornance Tuning & Benchmarks Pogo ProV3 vs Pogo E02 Another Pogo Pro V3 benchmarks Network performance - SAMBA - NFS (various protocols) Pogo Pro V3 Network NFS benchmarks Kirkwood vs OXNAS network performance (with flow control) Kirkwood vs OXNAS network performance (flow control turnedby bodhi - Debian
BayPanard, > I face same problem : it seems usb and sata are > not being powered. Not sure yet about USB but it looks like I've missed some configs that might be the cause why SATA does not spin up. Will build another version.by bodhi - Debian
Jan_Grz1, > so the discs now have the file format ext4 and the > system has more ram, but the data is still written > to the usb stick. how do i change that? Like I said. You need to set up Samba properly. - Is the Samba share specified in /etc/samba/smb.conf to point to a mount point? - Is the mount point shown in the system when you run "mount" or "lsblk&quoby bodhi - Debian
MM, I've changed: - The DTS for kirkwood-promwad-thin-client.dtb to use GPO for both 7 and 17. See it it will take 17 this way. - Move the USB hub back to i2c0. See if it will fix the error we saw previously in Anonymous's log. This tarball kirkwood-promwad.dt.250418.tar contains 4 files kirkwood-promwad-thin-client.dtb kirkwood-promwad-thin-client.dts kirkwood-promwaby bodhi - Debian
@ConcentratedCancer, Go ahead copy the fan_control and led binaries to your rootfs /tmp. And try running it cd /tmp ./fan_control ./ledby bodhi - Debian
BayPanard, Here is the updated u-boot. uboot.2024.10-tld-1.ds112.250418.tar md5: 6110c0dea32952a09e598c740d4a1f9e sha256: 01f7fca1c0612b71bbba651e567ea0dd60dd9cb2d78752152cbd86995b587b3f This tarball contain 5 files, only the uboot.2024.10-tld-1.ds112.kwb is new, other files are the same as previous version. uboot.2024.10-tld-1.ds112.kwb uboot.2024.10-tld-1.ds112.environmentby bodhi - Debian
MM, > name pins functions > ================================================================================ > mpp7 7 gpo, spi(cs), lcd(pwm) > > > need change gpio to gpo in DTS? Yes indeed.by bodhi - Debian
@Anonymous, > I have found that problem was with -C gzip while > creating uImage / uInitrd, it started to boot when > I changed to -C none. From what I see in the entire log, your rootfs has some problem. Are you using Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2 or using your own rootfs from somewhere else? When you install Debian kernel, the compression in this file takeby bodhi - Debian
BayPanard, If your rootfs is on HDD, you don't need to use the USB drive. Basically, the boot.scr should be on /boot of whatever system you are running on the DS112. " "Debian rootfs" could be the USB or HDD that you are booting with. Quote2. Prepare the boot script boot.scr in the Debian rootfs Since this is the first time you boot this new u-boot using kwboot,by bodhi - Debian
Anonymous, > Stock U-Boot already has usb support, however > ext2load is fairly slow. I have tried to run > 6.13.8 kernel but apparently load address is > incorrect or something, because I get GZIP error > when trying to uncompress with bootm. Kernel > address is set to 8000 and initramfs to 0, perhaps > that's the problem. No, that's not the problem. Thby bodhi - Debian
BayPanard, Attached here is the new u-boot for Synology DS112. uboot.2024.10-tld-1.ds112.250416.tar md5: d5433ddc12a2a6f12156e2d917f864e4 sha256: c82c1c7bd7b000ecec88bbbc0fb13d0d38e1bad7a507c0a62f55218f68254642 This tarball includes 5 files uboot.2024.10-tld-1.ds112.kwb uboot.2024.10-tld-1.ds112.environment uboot.2024.10-tld-1.ds112.environment.img uboot.2024.10-tld-1.ds112by bodhi - Debian
BayPanard, Please dump u-boot image (from mtd0). cat /proc/mtd You should see the mdts look similar to this (but in a different format) [ 4.590546][ T1] Creating 6 MTD partitions on "spi0.0": [ 4.596111][ T1] 0x000000000000-0x000000080000 : "RedBoot" [ 4.602555][ T1] 0x000000080000-0x000000280000 : "zImage" [ 4.608838][ T1] 0x000by bodhi - Debian
BayPanard, > Do you have some time to build a uboot that I > could try on my box? I will, since this u-boot is seriously deficient in that it does not support USB or IDE command (not possible to boot with USB or SATA storage device). > Do you need me to launch some commands? that I > provide some information? I did get some info previously. Will let you know if I need mby bodhi - Debian
For the new u-boot, 1. UBIFS should be easy. 2 .Graphics is not possible due to lack of driver. 3. USB might be possible, but that will remain to be seen. Currently the power regulator in kernel is not working as we want. There is only enough power to use 1 USB flash drive. If you can, please test the latest DTB in kernel linux-6.13.8-kirkwood-tld-1 https://forum.doozan.com/read.by bodhi - Debian
Jan_Grz1, > Yes, but I want to mount the NAS on Windows. So I > have to switch to ext4 for more speed but then I > can't mount it on Windows anymore? Using Ext4 on the NAS HDDs, and define the Samba or NFS shares on the HDD folders. Samba will export these shares. And then you'd mount the Samba shares on Windows. And it's highly recommended to use Ext4 or Ext3 to hby bodhi - Debian
MM, Could you summarized what is lacking with stock u-boot that you guys want to have? and what is working, i.e SATA, USB, saving envs,...by bodhi - Debian
Jan_Grz1, /dev/sdb1 on /media/Disk1 type fuseblk (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) /dev/sda1 on /media/Disk2 type fuseblk (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) That was likely your problem. You are using NTFS file system on these disks? NTFS performance on Linux is very bad comparing to other filesystby bodhi - Debian
MM, > Quotebodhi > Updated 25 Mar 2025: > Kernel linux-6.13.8-kirkwood-tld-1 package has > been uploaded. The following features were > added/updated: > ... > - Updated PromWad Wtplug and Thin Client DTS > ... > > > Does DTS in the kernel topik have any differences > from the latest version in this thread? Yes, added pcie0 and pcie1, and movedby bodhi - Debian
> Sadly the fan control and led tools are supplied > in their binary form even in the GPL, there are no > other references to led's or fan control anywhere > else in the GPL so that may be a no go > unfortunately. Sometime this happens with a company that intentionally implemented a malicious compliance to GPL. Instead of disclosing how they control a piece of hardwareby bodhi - Debian
> I found two binaries of interest, > /usr/sbin/fan_control and /usr/sbin/led, > "fan_control" controls the fan as you would expect > you can turn it on and off and set speed and get > the fan RPM, "led" allows me to set the power led > status (on, off, blinking, red or blue) as well as > each of the four hard drive LED's (again, red, > blueby bodhi - Debian
> Yep, my mistake, actually there was more than one > mistake, I forgot to copy the kernel before > appending the device tree onto it so the "kernel" > I was trying to load was just the device tree, as > well as I extracted the dts instead of the dtb. I > am still sick so my brain isn't working quite > right haha, :) > regardless that new deviceby bodhi - Debian
@ConcentratedCancer, Bytes transferred = 5776275 (582393 hex) ## Booting image at 00800000 ... Image Name: Linux-6.13.8-kirkwood-tld-1 Created: 2025-04-10 19:34:15 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 706 Bytes = 0.7 kB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK OK Looks like your uImage isby bodhi - Debian