Jump to content

raav

Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About raav

  • Rank
    Newbie
  1. Turns out you need to throw more RAM at the VM! After setting Windows to 6GB, the driver worked without error 43 in 4k resolution. It probably would work with less, but I didn't bother testing (2GB was not enough though). Libreelec with Kodi works at 2GB RAM, but not less. There is no automatic switching between resolution or HDR though. When I play 4k HDR content and force my TV HDMI input to PQ however, the image seems pretty much the same as if I play the content on the TV itself, where it switches to HDR. So it seems that 4k HDR does indeed work, but still needs manual adjustment on TV.
  2. So I just tried to get windows 10 running, hoping I could run Kodi there, but windows only shows up in 1024x768 and shows error code: 43 in the display driver. I Already used DUU from guru3d to uninstall drivers and install newest intel drivers 25.20.100.6326. Windows shows the correct card "Intel HD 630" but still error code 43. There is also another driver with error 43 called "Basic Microsoft Display Driver". I have no idea what the problem is here, any thoughts?
  3. I have an ASRock - Z270 Gaming-ITX/ac and Intel G4600 CPU. The motherboard has a MCDP2800 Chip from Megachips which supports HDMI 2.0a and HDCP 2.2. My TV is connected directly to the HDMI output of the board. I followed this guide to install a libreelec vm: With Seabios and i440fx (Q35 and ovmf don't work) the vm runs fine in 3840 × 2160 60Hz and I can use Kodi to play movies up to full HD. When I try to play 4k HDR videos however, the screen turns blank and after some time Kodi restarts. Is 4k output not supported from a VM? Any ideas how to fix that?
  4. Thanks BLKMGK, your approach saved me! I'm new to unraid and suddenly had this issue after starting the array: emhttpd: error: get_filesystem_status, 6477: Operation not supported (95): getxattr: /mnt/user/appdata I could not see any shares and not even create new ones. When I tried to stop the array, the GUI froze and I saw this repeating in the log files: emhttpd: shcmd (140): umount /mnt/user root: umount: /mnt/user: not mounted. emhttpd: shcmd (140): exit status: 32 emhttpd: shcmd (141): rmdir /mnt/user root: rmdir: failed to remove '/mnt/user': Directory not empty emhttpd: shcmd (141): exit status: 1 emhttpd: shcmd (143): /usr/local/sbin/update_cron emhttpd: Retry unmounting user share(s)... There was only this directory and nothing else, so I deleted it from ssh: rm -rf /mnt/user and renamed /boot/config/shares/appdata.cfg before starting the array and everything was back!