So years ago when the name Docker started circulating I thought it was stupid... such BS.
Did I give it 2 minutes? Nope. A real head in sand moment if I must say. FF to today.. I am accessing a full Team license to Pluralsight via $boss at $work and I stumble across the Docker course.
Ok.. fine.
So I plow through the intro and my ears are perked. If I were a dog, my tail would be at 12 o'clock.
So I have this Mac Mini at home that un recently was my Plex media server, well the thunderbolt nas I used as my BE storage up and died. So I loaded docker-ce and went to town.
Right now I've got containers for Pi-hole and Portainer. I've always wondered how much of an impact pi-hole would make in a house with 5 internet users so it's up and going. Then portainer because it was recommended by an acquaintance in IRC and a mention from the Googs.
So far pi-hole is eating an impressive 44mb of ram and portainer 7.54mb. <Borat "very niice"> I'm impressed, honestly. I'm now searching for other legit container uses here at home.. I want more.
Technology tidbits and things related to small farming including Powershell, AD, Exchange, Security, Chickens, Dogs, General Construction and the like.
Friday, December 28, 2018
Tuesday, December 18, 2018
AMD Radeon Adrenalin drivers, Code 43 in Device Manager. -SOLVED
So I'm setting up a new rig for my oldest daughter, she bought herself an Oculus Rift (Lucky ass!) Not like I haven't been wanting VR since it was a pipe dream! lol.
Anyway so she needs a new rig to power her new toy, she's running on an I7-3770, 8gigs of ram, a 500gb SSD and a GeForce 570Ti. It's served her well so far however it's not good enough.
So anyway I'm setting her up with an HP Z620 workstation, powered by a Xeon E5-2520 6 core, 16gigs of RDDR3, another 500 gig SSD and an RX 570.
So this is a fresh Win10 Pro install right? I get it home and it's fully updated and go to install the most recent Radeon drivers. I download 18.21.x, the installer routine completes fine, I reboot only to find a Code 43 in Device Manager.
What the hell.
I won't bore you with the details because chances are in your found my site you've already tried numerous things on the Googles.
I installed the atikmdag-patcher.. originally intended to remove the resolution and refresh limitations from older Crimson drivers. Located here: atikmdag-patcher
I don't know why.
I don't understand how.
It makes zero sense to me but This. Shit. Worked.
Ran this .exe, it says it patched a few things and a reboot later and BOOM! Windows is happy.. 3DMARK11 is happy... I'm happy.
Anyway so she needs a new rig to power her new toy, she's running on an I7-3770, 8gigs of ram, a 500gb SSD and a GeForce 570Ti. It's served her well so far however it's not good enough.
So anyway I'm setting her up with an HP Z620 workstation, powered by a Xeon E5-2520 6 core, 16gigs of RDDR3, another 500 gig SSD and an RX 570.
So this is a fresh Win10 Pro install right? I get it home and it's fully updated and go to install the most recent Radeon drivers. I download 18.21.x, the installer routine completes fine, I reboot only to find a Code 43 in Device Manager.
What the hell.
I won't bore you with the details because chances are in your found my site you've already tried numerous things on the Googles.
I installed the atikmdag-patcher.. originally intended to remove the resolution and refresh limitations from older Crimson drivers. Located here: atikmdag-patcher
I don't know why.
I don't understand how.
It makes zero sense to me but This. Shit. Worked.
Ran this .exe, it says it patched a few things and a reboot later and BOOM! Windows is happy.. 3DMARK11 is happy... I'm happy.
Subscribe to:
Posts (Atom)