bodhi Wrote: ------------------------------------------------------- > Note that this DTB has not been tested. > > Please test this updated DTB for the ReadyNAS duo > V2 . This needs to be used with kernel > linux-6.10.11-kirkwood-tld-1 or later. The RTC > driver for this box (rs5c372) is quite different > from the Zyxel NSA325 (pcf8563). So don't know if >by AndreaCipcino - Debian
Bodhi, I understand the situation, for now I will fall back on the stock OS and will leave this on stand-by. Once you have again access to your NSA325, and find what's wrong, hopefully that will benefit the resolution of this problem for Readynas Duo v2 too. Thanks again in the meantime.by AndreaCipcino - Debian
Bodhi, I am now returned to work and I have access again to the nas. I have tried the new kirkwood-netgear_readynas_duo_v2.dtb file , and now I think the rs5c372a chip device is running; but the problem still persists. root@nas-backup:/sys/class/rtc# rtcwake -s 30 rtcwake: cannot open /sys/class/rtc/rtc0/device/power/wakeup: No such file or directory rtcwake: /dev/rtc0 not enabled for wby AndreaCipcino - Debian
Mijzelf, as I recall, rtc1is not present. Only rtc0 is inside /sys/class/rtc.by AndreaCipcino - Debian
Bodhi, thank you for answering. I have to wait to the end of August before I can access again the Nas, and starting again to work on this project. I use the Nas in my working environment, and our company is now closed for holidays. I will post the boot log as soon as I can work on it again.by AndreaCipcino - Debian
Whith original netgear firmware, you can set shutdowns and wakeups via web interface: you select in power settings "activate wakeup timer" and then select when the nas should be on, and it works. But as I have checked just now , it has not the wakealarm file, and rtcwake says that rtc0 is not enebled for wakeup events too. So probably netgear has another method to make it wakeup, butby AndreaCipcino - Debian
Hello Bodhi, I would like to use an OMV7 plugin for wakealarm function, but it doesn't work. I have noted that in the realtime clock directory /sys/class/rtc/rtc0 , there is no wakealarm file: root@nas-backup:/sys/class/rtc/rtc0# ls -l total 0 drwxr-xr-x 3 root root 0 Aug 2 16:27 . drwxr-xr-x 3 root root 0 Aug 2 16:27 .. -r--r--r-- 1 root root 4096 Aug 2 16:58 date -r--r-by AndreaCipcino - Debian
Bodhi, I have managed to configure all the leds with systemd method, here I show how I have done it for people who might find useful for resolving similar issues: for configuring leds I have used udev rules: I have created a new rules file in /etc/udev/rules.d and called it 10-local.rules cd /etc/udev/rules.d/ touch 10-local.rules Then I have gained udev info for the leds that I wanteby AndreaCipcino - Debian
Bodhi, all done , now uboot is perfectly set! Thanks for helping me .by AndreaCipcino - uBoot
Bodhi, now both usb rootfs and stock boots fine, thank you! Now for saving this configuration, it is better to use saveenv or use fw_setenv ?by AndreaCipcino - uBoot
Hello, I am writing this here because it has to do with environment variables used by Yuri Minsk in this thread. Basically my netgear ready nas duo v2 has perfectly working original old u-boot, and I would like to set it to first try to load your rootfs from usb and if that failed (i.e. usb storage not present) then proceed to load stock OS. I have set these environment variables: setenv maiby AndreaCipcino - uBoot
Hello bodhi, yes I have used your rootfs of Bookworm with included kernel version 6.5.7. Then creating swap file, done apt-update / upgrade, and set it to boot with systemd. Then installed omv7. Should I update kernel with your latest version? There are 3 LEDs on Nas. "Act" led actually works with hard disks activity. Led "1" and "2" instead are always off. I donby AndreaCipcino - Debian
Hello, I have managed to run a rootfs of Debian 12 + OMV7 on this old NAS. Everything works except hard disk presence LEDs. Those two LEDs remain off, instead they should turn and stay on when an hard disk is connected in the sata port. I know that an user managed to make them work by adjusting an udev rule file, but I am very noob in Linux and I have no idea how to do it. I'm quite stucby AndreaCipcino - Debian