toyanucci

In the same position and need your feedback. So you used the new bootloader and selected 64561 and the same settings as before. Did you have to manually do the update or were you able to boot into 7.1 and do the update from the gui?

Just taking the time to say thank yo to the OP and all who's work he built upon. Got this working easily with my Asrock J4105 baremetal build. I run it headless and always found it annoying to hook it up to a monitor and connect a keyboard to update the bootloader but all I did was check my router to see what new device connected (after booting up). I got the ip address that way and simply used the port listed in the instructions to be able to access the bootloader config and get it set up. I had one small hickup and it was that my serial number was said to be invalid. I added it anyway but couldn't log into my synology account to setup ddns but realized it was because I didn't enter the MAC1 that corresponded to the serial number. I entered it in the config file on the usb stick I have the bootloader on and it now works perfectly. Thanks again!

You applied the update from within DSM without redoing redpill? Wondering if it's safe to just apply the update 🤷🏾‍♂️ Sorry for the duplicate posts, not sure why it did that. Can someone please delete them?

Many others have helped to get this up and running so we're all standing on their shoulders. The process I followed is based on the above edited quoted posts. I'm running 7.0.1-42218 baremetal on a Asrock J4105 ITX board with no modifications. I had 6.2.3 working with Jun's loader before. I haven't seen this posted so I hope this part helps someone but I have a M1 Macbook Air which uses an arm processor and I was unable to compile an image with the docker on this machine or using docker in a Ubuntu virtual machine on the M1 Macbook Air as there were always errors relating to docker. I created a Ubuntu VM on the 6.2.3 build and used the info above to to compile the image. I tested by booting from the usb with the drives unplugged and installed to a different drive to verify it was working ok. I have attached the edited global_config.json file which has apollolake-7.0.1-42218 added so you can use that in the commands from above instead of apollolake-7.0.1-42214. Thanks @Tango38317for your help with that. The machine gets an ip address in about 45 seconds after boot and everything works perfectly. I have several things running in docker including plex which works without issue but I had to add the following as a scheduled task that runs at boot to get hw transcoding to work for plex if you have a plex pass and a real SN and MAC: chmod 777 /dev/dri/* Again, I hope this helps someone. global_config.json

Mine says it's idling in the 60's too which immediately looked strange to me so I figured it had to wrong as well.

Thankfully the internal nic works so I won't need to make an additional purchase. If anyone wants the H360T I have though let me know. I'll sell it at cost

Ok. So I tried to update from within DSM 6.2 and it tried but hung at updating programs for over an hour so I hard reset. I put the redpill usb in and it loaded up and said it needed to be reinstalled. I reinstalled and kept settings and it updated and updated programs and now I'm on 7.0 baremetal. Docker and everything is running great. Thanks to everyone who helped me figure all this out and especially to everyone who contributed to redpill. I know all this takes a LOT of time to figure out, time that could be spent doing so many other things but the dedication to the community is what keeps the progress going here. Thanks again!

I let the usb boot up then I hot plugged the sata drive and hit refresh at the setup page and it came up. Installing currently. Everything is working with the test drive I'm using. After installing it works perfectly on reboot as well and takes just about a minute from power on to when the DSM can be accessed. Now to try to update my normal setup

It seems the onboard nic is working after all! All along I had a sata drive connected when I tried to boot up and it would't boot at all. I unplugged the drive just now and could access the setup page within 2 minutes. Now it's to figure out how to get the sata drive to work 😀

Can someone recommend a compatible nic? I waited all week for a HP NC360T to be delivered only to realize it's a pcie x4 and my j4105 motherboard only has a pcie x1 slot 😑 The onboard realtek nic should be compatible but for some reason it isn't working for me so I want to try using another nic.

Man it was weird! After 3 to 4 day's it would stop working...Thinking about it now maybe that coincided with when watchtower updated plex 🤔 And yes, maybe native plex sets the permission during setup as well which is why docker plex would work afterwards.

Just restarted and checked and /dev/dri/ is populated...maybe it's a permission thing as you said. about to try what you said: chmod 777 /dev/dri/* So that fixed it!! I am so thankful as this has been a MAJOR annoyance for many months. I didn't want to bother anyone with the problem but so glad I finally just asked. Thank you so much for you help!! I can finally stop running those daily scripts lol.

I do but it's like if a native app doesn't attempt to use it it's not enabled so docker can't access it until it is.

docker run -d \ --name=plex \ --net=host \ -e PUID=1026 \ -e PGID=100 \ -e TZ=America/Chicago \ -e VERSION=latest \ -v /volume1/docker/plex/config:/config \ -v /volume1/docker/multimedia:/Multimedia \ --restart unless-stopped \ --device=/dev/dri:/dev/dri \ linuxserver/plex:latest That's what I used to create the docker plex. The issue is at boot nothing is in /dev/dri/ unless I run run native plex first.

I can get hw transcoding to work for plex in docker but to make it work I have to run plex from package center first or /dev/dri/ is empty. Rebooting (manually or from losing power) results in no /dev/dri/ being empty again and I have to stop docker plex and run package center plex then stop it and start docker plex for hw transcoding to start working again in docker. /dev/dri/ also magically goes empty after a few days even if there's no power loss. Currently I have some scheduled scripts that run at 5am that stops docker plex, installs package center plex, stops package center plex, then starts docker plex to ensure hw transcoding will be available at least daily if there's a power loss or something that happens without me being aware of it. I know, it's all weird and confusing but my question is if there's another way to get /dev/dri/ to populate without having to run package center plex. Also, because of the default unchangeable port number of plex I can't have both plex's running.