paperblankets

General feedback: I'm happy with the (small) number of bugs, and the gottchas that come with releasing via docker tags/in lockstep with plex-pass releases. I could see this issue not happening if the binhex-* version was semver, and a patch release was made after the plex team rolled their update. That way all users of this container would have been sent a new version. I'm sure this way is very simple though, and allows you to maintain many containers at once without getting bogged down. But yeah, keep up the good work/thanks! This issue feedback: This resolution was done over a beer from my phone, instead of by rebuilding my own docker container, or pulling the latest Plex version from a shell script in a VM and debugging everything that changed since the last time. Tldr feedback: Thanks for making my life easier!

> Yup. Looks like it was a Plex specific issue and not a docker build issue. Remove the tag for the specific version and apply (if you rolled back to the previous version) and then check for updates (those who have not rolled back to the previous version just need to do this). Latest version fixes the issue I'm running binhex-plexpass, I don't see any updates, but I have the symptoms listed above. Has a new release happened? Or is the fix still rolling back or removing tags? How do I remove tags? Edit: trying a force update to start with Edit edit: That seems to have worked.

It is supposed to, my results have been hit or miss though. In the past windows 10 audio over hdmi worked as expected, in ubuntu hdmi audio tries to work, and fails or plays loud, distorted audio. At this exact moment hdmi audio is not working in my vms, and I assumed that way unique to my setup. I am not sure if it is an update to nvidia drivers, or windows that caused it. Steam streaming drivers exacerbate the issue. Edit: Yes audio over hdmi should work. People are still referencing this post, so I am going to mention that if you get past the mmap error mentioned in this post, you will then likely run into an error where your nvidia/amd/etc drivers are not msi enabled. The fix for that is mentioned around the forums but here is a link to the msi utility. You run that (as admin) after driver install/restart, and check the msi checkbox next to the device that needs msi support.

Hi @kalfun, One of these paths does not exist for me as well: /tmp/user.scripts/tmpScripts/Fix mmap/script: line 3: /sys/class/vtconsole/vtcon1/bind: No such file or directory /tmp/user.scripts/tmpScripts/Fix mmap/script: line 4: echo: write error: No such device `vtcon1` in my case does not exist. I have just left the script as is though since the error does not cause damage, and if a configuration change occurs and that console is used I want the script to fix that bind. Things to note about this configuration that made it work in my case: The script is set up for "At start of Array" The script did _not_ work for me the first time when I ran it from the terminal. I had to spin down the array, restart, and let the user script run. Other thoughts: Make sure one of those directories exists, /sys/devices/virtual/vtconsole/vtcon1/bind or /sys/devices/virtual/vtconsole/vtcon0/bind. If one or both exist but you are still getting not found/permissions issues you might need to do something to make your user script run with higher permissions (But I don't have advice on that, and the thought is unsettling to me) Others might now if there are more vtcon directories that _could_ be in use on your system. I am not sure.

I am not sure if I needed to restart the server, or have the array stopped, but one of those let me run two of the 3 commands: echo 0 > /sys/class/vtconsole/vtcon0/bind echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind Which resulted in a boot without mmap errors, which allowed me to install drivers. @bigjme I added a user script to fix mmap, it sounds like this fix does not persist on a restart for you right? Thank you for the debugging steps and suggestions!

Thanks for the info Jamie! I indeed get a different result when ssh'ed as root. I am still running into issues though. Last login: Thu Aug 9 19:06:02 2018 from 192.168.1.125 Linux 4.14.49-unRAID. root@HuananTheHydra:~# echo 0 > /sys/class/vtconsole/vtcon0/bind -bash: /sys/class/vtconsole/vtcon0/bind: No such file or directory root@HuananTheHydra:~# echo 0 > /sys/class/vtconsole/vtcon1/bind -bash: /sys/class/vtconsole/vtcon1/bind: No such file or directory root@HuananTheHydra:~# echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind -bash: /sys/bus/platform/drivers/efi-framebuffer/unbind: No such file or directory My vtcon* directories do not contain a bind folder. root@HuananTheHydra:~# /sys/class/vtconsole/vtcon0/ power/ subsystem/ root@HuananTheHydra:~# /sys/class/vtconsole/vtcon1/ power/ subsystem/

I get similar mmap errors to what you describe, and have the same issues on driver install. When I run the following in the webterminal: echo 0 > /sys/class/vtconsole/vtcon1/bind I get -bash: echo: command not found When I run: sudo echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind  I get: /sys/bus/platform/drivers/efi-framebuffer/unbind: Permission denied Any thoughts? I made a post here: but have not gotten any feedback thus far.