Thanks for the tip for watchdog, my transfes speeds are better than with the old kernel (about 50 MB/s because i´m using it over WIFI, but before i manage only 40), I already using zram instead of zswap with a little hack that I manage, but now i´m thinking changing to zswap (in theory is better???, don´t know if it´s truth), the only think i need to test is the HW video acceleration, now we have the codecs included in the sources, hope i manged to get it working in the following days.
Yes, the Kernel for MCH single bay seems working in MCHD but as you said the fans and another drive can not be found. I used a mixed combine with MCH kernel and MCHD rootfs (from forth32) to boot my device previously, and it works fine but only docker not work.
Awesome, thanks for the “systemd.unified_cgroup_hierarchy=0” info. That was my hold up on using the new kernel with Docker. 
1 Like
I found where they hid the 184MB + 12MB memory reserve for GPU (where else 60MB remains a mystery)
linux-4.9.266/include/soc/realtek/memory.h
line 209:
/* legacy : 184 M */
#ifndef CONFIG_RTK_TRANSCODE
#define ION_MEDIA_HEAP_PHYS1 (MEM_SLOT(0, PHYS, 0x00000400))
#define ION_MEDIA_HEAP_SIZE1 (MEM_SLOT(0, SIZE, 0x00000400))
#define ION_MEDIA_HEAP_FLAG1 (MEM_SLOT(0, FLAG, 0x00000400))
#else
#define ION_MEDIA_HEAP_PHYS1 (MEM_SLOT(0, PHYS, 0x00000400))
#define ION_MEDIA_HEAP_SIZE1 (MEM_SLOT(0, SIZE, 0x00000400))
#define ION_MEDIA_HEAP_FLAG1 (MEM_SLOT(0, FLAG, 0x00000400))
#endif
/* legacy : 12 M */
#ifndef CONFIG_RTK_TRANSCODE
#define ION_AUDIO_HEAP_PHYS (MEM_SLOT(1, PHYS, 0x00000400))
#define ION_AUDIO_HEAP_SIZE (MEM_SLOT(1, SIZE, 0x00000400))
#define ION_AUDIO_HEAP_FLAG (MEM_SLOT(1, FLAG, 0x00000400))
#else
#define ION_AUDIO_HEAP_PHYS (MEM_SLOT(1, PHYS, 0x00000400))
#define ION_AUDIO_HEAP_SIZE (MEM_SLOT(1, SIZE, 0x00000400))
#define ION_AUDIO_HEAP_FLAG (MEM_SLOT(1, FLAG, 0x00000400))
#endif
1 Like
Good find on the extra memory, I compiled linux-4.9.266 and it works great.
I tried the new zip - Install_usb_disk_Debian11(OMV6)(GPL_MCH_Monarch_8.7.0-107_20220623) and the makepartshdd.sh is using the old /dev/sataa and with your new USB Boot should be sda. Also, for some reason the new install will not recognize eth0 . No network initialization.
How did you get sda to work?
Thanks
This installation flash drive is only for the version of WD MCH (Monarch/1HDD), probably the separation GPL from the DUO went deeper
overlooked …
fixed errors on the installation flash drive in makepartshdd.sh and etc/network/interfases
redownload install drive
in system now ver.kernels 4.1.17 and 4.9.266, for change ver. command:
/boot/bootA #ver.4.9.266 +GPU (RAM ~750MB)
/boot/bootB #ver.4.9.266 -GPU (RAM ~1GB)
/boot/bootG #ver.4.1.17 -GPU (RAM ~1GB)
boot branch A
boot branch B (Rescue)
boot branch G/Gold (“Factory”)
All kernels boot one system.
Getting closer. It creates partitions and does pickup an IP address.
Issues
The watchdog timer is active and rebooting every 2 minutes.
I have console access for Root but can’t connect to the IP address with ssh.
Thanks for all the work!
Regarding some of the left over memory. I decreased the ION_MEDIA_HEAP_SIZE2 from 60MB to 16MB. (trying 12MB still gave an error):
/* legacy : 60 M */
#define ION_MEDIA_HEAP_PHYS2 (MEM_SLOT(2, PHYS, 0x01000000))
#define ION_MEDIA_HEAP_SIZE2 (MEM_SLOT(2, SIZE, 0x01000000))
#define ION_MEDIA_HEAP_FLAG2 (MEM_SLOT(2, FLAG, 0x01000000))
@JohnsonEW regarding the watchdog; you have to use /dev/watchdog now. I use the Debian provided watchdog package, please see my config above.
1 Like
boot from usb, mount sda19 and edit /etc/ssh/sshd_config:
“PermitRootLogin prohibit-password” → “PermitRootLogin yes”
or
sed -i ‘s/PermitRootLogin\ prohibit-password/PermitRootLogin\ yes/g’ [Path]/etc/ssh/sshd_config
I fixed the errors, try downloading again and installing clean (link in the post above)
Yes, I downloaded the new zip and it works well. I haven’t installed OMV, have to figure out the disabling watchdog Alex-N posted info on.
and where is it?
I enabled this setting:
cat /etc/default/watchdog
Setting the boot mode to 5 in the bootConfig should trigger the BOOT_GOLD_MODE
(bootloader/uboot/common/cmd_boot.c)
1 Like
sorry originally it reads
/* legacy : 146 M */
(same file you used)
1 Like
I can’t figure out how to stop the watchdog / reboot with the 4.9.266 kernel. If it’s compiled in the kernel is it possible to disable it through settings / software? The Debian watchdog software package doesn’t have an effect on the reboot.
The 4.1.17 kernel works great - no issues.
This is how I have it running (I forgot to mention the config of the watchdog service)
/etc/watchdog.conf
watchdog-device = /dev/watchdog
/etc/default/watchdog
# Start watchdog at boot time? 0 or 1
run_watchdog=1
# Start wd_keepalive after stopping watchdog? 0 or 1
run_wd_keepalive=0
# Load module before starting watchdog
watchdog_module="rtk-wdt"
The last line is optional if kernel doesn’t use modules.
Looks like you’re using the systemd-Watchdog feature in
/etc/systemd/system.conf
[Manager]
RuntimeWatchdogSec=45
That works for me as well.
1 Like
That was it. I am using RAH-66 (4.9.266) kernel from the USB Install. Once I set this no more reboots.
Thanks!
WD deleted all versions GPL Monarch? 
I suppose this is just an oversight…
Besides, the new version (8.8.0-112) didn’t change anything in the kernel.
