I would like to underline that you basically have various ways of testing the next beta, pick that one you are more comfortable with:

• by reimaging the drive: use a stable official image of your choice, edit firstboot.json selecting "3.1-dev" branch in place of "release", add a new 1bash from the template ont the [urlhttps://github.com/papampi/nvOC_by_fullzero_Community_Release/tree/3.1-dev]github 3.1-dev repo[/url] and go
  
• by firstboot re-run: this will only work on official nvoc images, basically this has the very same effect as the first point here but you won0t need to reimage or detach the drive from the rig, just edit the same files (firstboot.json and 1bash in the FAT partition), switch gnome-terminal profile to "firstboot" (you should have this already on official recent images) and reboot.
  
• by cloning from git: you can get some general instruction about this in the github wiki, this will allow you to quickly switch back to the stable setup where you were running before

I will now report here some hints for 3.1 beta testers I already posted some days ago in the discord channel that will also let you get a preview of what has been worked on in the past few months. Please, don't care any technical detail below if you just love the "easy-to-use" nature of nvOC, you will not be required to know about such things to get nvOC up and running when this becomes stable.

- Foreman monitoring integration: here is just something new, so by definition, no regressions are expected on this

- Selective GPU disable: this is totally new also, but has been worked on for a while and no regressions are expected when you don't select any specific gpu set

- Tempcontrol: its behavior has been changed in order to let it run regularly for other gpus during the grace period of a failed single one. Please note that by its parallel construction if a gpu stops responding for more than an entire loop period you could see more than an alert about the same gpu which is not responding. Just let it go and report if you ever see any patterns like this: thread:1->GPU1->ko | thread:2->GPU1->ko | thread:1->GPU1->ok | thread:2->GPU1-> still ko, reboot

- Pluggable miners: all miners which have been ported to PM has been removed from the legacy places to avoid confusion, there may be some newer versions that have been upgraded in the stable branch and not yet on the beta branch, report if any. You are also invited to try updating on your own meanwhile to see if everything works as expected with the updated/added miner. I'm not sure if you are already familiar wth our new PM approach, but if you ever had the necessity or the wish of adding a new miner for a new algo to nvOC you will be quite happy to see that after "a bit" of rework you should now be able to achieve this with no edits to nvOC scripts of code.