LinuxARM

Hey Guys! I'm not able to get the rsync daemon to run config is 1:1 same as of the first post and no pid "cat: /var/run/rsyncd.pid: No such file or directory" and no connection to rsync server. rsync: failed to connect to XXXXX.local (10.0.0.XX): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(127) [sender=3.1.3] Line was pasted into /etc/inetd.conf after reboot or if I trigger "bash /boot/custom/etc/rc.d/S20-init.rsyncd" # walld/1 dgram rpc/udp wait root /usr/sbin/tcpd rpc.rwalld # # End of inetd.conf. rsync stream tcp nowait root /usr/sbin/tcpd /usr/bin/rsync --daemon Since I'm running newest unraid 6.9.2 was there a change to how inetd works? I want also to add, if i start the daemon manually it's working (/usr/bin/rsync --daemon) which just gets me to the point that something is wrong with inetd.

Thank you @giganode! It looks very similar to my. The config.plist tho is the one that gives you the configuration and settings. You mind to share it with me? You can easy make it generic by searching for "Generic" and remove the content inside the <dict> tags.

Interesting, I'm also running vendor-reset. I'm done reading the whole thread here and my VM is now solid stable beside the reboot issue. I think that it's maybe my EFI configuration. It would be really nice if you could share your current EFI folder, I would like to compere it with my.

My CPU is showing up as Unknown Processor name. I'm running a E5 2680 v4. How to fix this this? Also, if I define topology I can't go higher then 16 with 8 Cores 2 threads otherwise macOS stuck at apple logo. Is this the limit or is there a patch for OpenCore that uppers that limit? Dual socket fixed this issue: <topology sockets='2' dies='1' cores='8' threads='2'/> I'm wondering if it has something to do with the boot sequence, the more cores I add the longer the boot time. Which you can see on this 3 hills the CPU load produces while booting. (first 28, second 16 cores) @Leoyzendid you notice this?

Hey, I just updated OpenCore to 0.6.8 on Big Sur and run into a issue. I'm not able to reset NVRAM over the boot menu. The function just doesn't have any effect no matter how often I tried. I ended up creating a new nvram file in "/etc/libvirt/qemu/nvram/XXXXX_VARS-pure-efi.fd" after which Nvram was reseted and 0.6.8 booted. But doing so produced a few errors and I needed to reboot unraid. Anyone knows why the boot menu "nvram reset" is broken? or another solution without having to reboot unraid like a qemu cli command? SOLVED.

Follow this tutorial to enable sound https://dortania.github.io/OpenCore-Post-Install/universal/audio.html

Hey guys, I just updated OpenCore to 0.6.8 on Big Sur and run into a issue. I'm not able to reset NVRAM over the boot menu. The function just doesn't have any effect no matter how often I tried. I ended up creating a new nvram file in "/etc/libvirt/qemu/nvram/XXXXX_VARS-pure-efi.fd" after which Nvram was reseted and 0.6.8 booted. But doing so produced a few errors and I needed to reboot unraid. Anyone knows why the boot menu "nvram reset" is broken? or another solution without having to reboot unraid like a qemu cli command?