While you're here, please consider supporting GamingOnLinux on:
Reward Tiers: Patreon. Plain Donations: PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers: Patreon. Plain Donations: PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
-
Golf With Your Friends adds a hilarious new Speed Golf …
- Pyretic -
Open source evolution sim Thrive gets upgraded to Godot…
- Pyretic -
Bazzite 3.0 out now with Steam Deck OLED support nearly…
- Pyretic -
Open source evolution sim Thrive gets upgraded to Godot…
- Purple Library Guy -
Zink driver startup time squashed with new patches
- ShabbyX - > See more comments
Latest Forum Posts
- Weekend Players' Club 4/26/2024
- Mezron - Penguins in Gaming
- StoneColdSpider - Nintendo-style gaming, without Nintendo!
- Pengling - Free Steam Keys!
- robvv - Company of Heroes 2 Benchmark
- Vortex_Acherontic - See more posts
View PC info
I think the sweetspot is the 1600 is like the fx6300/50 of the bulldozer. You'll get a 10% percent delta with the 1700, but 1600 can handle, and you can OC'it and you'll be just about on par with single threaded performance. Only if you are running on full 16 threads you'll see a difference, which is rare for now.
View PC info
It drove me nuts my machine was rebooting 3-4 times a day, the technical details are over here https://fujii.github.io/2017/06/23/how-to-reproduce-the-segmentation-faluts-on-ryzen/
AMD is looking into the problem and most likely will release a microcode update soon, for now there is a workraround here https://gist.github.com/satoru-takeuchi/687fb72c65c65e4896cc8836ae24d4c4
Disabling Kernel address space randomization helps ( echo 0 > /proc/sys/kernel/randomize_va_space ) and if bios has an option to disable opcache that also helps.
I don't know if any of you stumbled upon this problem??
View PC info
Ouch! I also have the mce freeze but I thought it was the same bug! the bug happens sometimes when resuming from sleep?? try the patch I said, you'll have to compile the kernel yourself but it improved everything 100 percent for me, not had a crash in 5 days and counting. But yes it does not solve the mce bug. I think it's a different bug, but the cause is the same (the cpu bug). It's like the cores and the threads won't wake up and the kernel tries and tries and the cpu goes yawn!! FY let me sleep. :P
Anyway I'm quite happy with the performance I trust that AMD or the kernel developers will fix this.
View PC info
Not a complete "AMD" build though - We use Nvidia graphics ( GTX 1060 6GB ). I am tempted by the AMD RX 580 8GB graphics cards - for personal use - but I like to play at 4K resolution, and for that I need the performance of Nvidia GTX 1080 Ti 11GB.
It is a relatively tiny build that fits snuggly under my TV making a perfect sofa PC.
I did not go all in with after-market cooling, just added a single 80 mm exhaust fan to the case, in addition to the 200 mm intake that was already present in the case. Setting fans to silent mode in BIOS gives around 40-45 °C for the motherboard and the CPU and around 50-55 °C for the graphics card when relatively idle. Need to do more precise measurements under load, but it does not look like there is any risk of overheating.
I had some problems getting the system to POST the first time, but after some tinkering pulling and re-seating the components I managed to get into the BIOS setup, upgraded the firmware, and it ran fine after that. I also needed to upgrade the firmware on the SSD for it to be detected reliably. Luckily all of that could be done in a platform-independent fashion.
Installation was quite painless. I installed Debian 9, and amdgpu pro drivers, and it worked fine. But Dirt Rally would crash the system whenever shader quality was anything above very low. I was about to panic (does not take much for that to happen apparently), but then I found Vega-ready kernels conveniently pre-built for Debian and Ubuntu (use at your own risk). So I installed it, removed amdgpu pro, and the system worked and recognized the Vega 56 card. Getting Mesa and other related goodies was just a matter of upgrading to Debian Unstable.
The only thing that does not work properly is the only thing that is not AMD. Namely, the Intel Wireless 3168. Even with the latest firmware and kernel WiFi is extremely slow and unstable. It will not allow me to set the proper regulatory domain, and that is probably the root of all problems. Not only does it not work properly, it messes the connection for other WiFi devices. :(
View PC info
I was wondering if this was ever fixed. My new Ryzen build might have this sleep bug. I leave my computer alone and come
back in the morning to find it frozen. I thought it had something to do with the wrong sleep profile.
View PC info
What is your framerate in the Witcher 3 with Vega 56?