Yeah! Jobs that bros can reciprocate! There should be a word for that...
checks notes Shareholders?!
What an unfortunate family name in the internet age
It would have cost you nothing to just not post this
Only financially. Put 2 and 2 together again...
why tho. money?
Se bullet 4. It takes a non-zero amount of effort. Keep showing up with only 1 effort just out of spite if you have to. But don't let it be zero.
How tiny? Inside earth tiny?
Meanwhile, in the engineering dungeon
You'll never gues what I put off for a month because it locked up the device every time it performed one. Some karmic god is being a real Bitch today. Imaging a new sd card while I spin up rtl_433 on another pi to keep my dopamine levels up
Just attempted adding the mqtt addon to hass since migrating to a raspberry pi. Will only bootloop without ever providing a gui. observer shows all green when it is alive. Logs are unhelpful. I just wana sleep man.
Zwave is superior for not clogging up the 2.4GHz airspace, both are darling to use with hass. Wifi is a close third for usability but suffers from bogging local wifi/airspace without interoperability without a controller of some kind being online. Zigbee/Zwave both can function somewhat even with the local server offline
Asrock has done me well for budget builds, asus is what I happened to upgrade to for midrange. Honestly being dramatic, just haven't cared for GB historically.
Good detective work! Adding liquefying thermal pads as a reason to avoid Gigabyte.
Portainer helped me finally get a wrangle on it with a webui to manage everything from with a proper UI. You can still deploy with terminal commands and dockerfiles and such, or through Portainer with app templates or stacks. But you're not limited to the terminal when it comes to managing everything.
The pattern says liquid but the colors say heat damage. Both?
Should I struggle through constant crashes to get my 7900gre with 16gb of vram working, possibly through the headache of ONNX? Can anyone report their own success or offer advice? AMD on linux is generally lovely, SD with AMD on linux, not so much. It was much better with my RTX2080 on linux but gaming was horrible with NVIDIA drivers. I feel I could do more with the 16GB AMD card if stability wasn't so bad. I currently have both cards running to the horror of my PSU. A1111 does NOT want to see the NVIDIA card, only the AMD. Something about the version of pytorch? More work to be done there.
- Having a much better time back on Cinnamon default instead of Wayland. Oops!
** It heard me. Crashed again on an x/y plot but due to being away from Wayland I was able to see the terminal dump: amdgpu thermal overload! shutdown initiated! That'll do it! Finally something easy to fix. Wonder why thermal throttling isn't kicking in to control runaway? Will stress it once more and clock the temps this time.
Temps were exceeding 115C, phew! No idea why the default amdgpu driver has no fan control but they're ripping like they should now. Monitoring temps has restored system stability. Using multiple amd/nvidia dedicated venv folders and careful driver choice/installation were the keys to multigpu success.
So NVIDIA just doesn't cut it on Linux/proton I've come to learn. Looking at the best bang//buck, it this the AMD card people are flocking to? 7800 XT maybe?