Tag: fedora

Linux Game Troubleshooting: Unable to find a supported OpenGL core profile.

Continued adventures in application troubleshooting aka using strace in the most brute force sort of way.

Have you ever had one of those problems where you know the payoff isn’t worth the work, but you can’t step away because you have to solve it? That is where I am at right now. If you read my earlier post on troubleshooting, you know that I am working on getting a itch.io game to work in Linux. In that post, I fixed a few missing libraries, but then I hit a dead end. Something in my setup still wasn’t quite right.

As I also noted in that post, this is not the only way to approach solving this issue. It may not even be the best, but it is a way. My real goal here is to convince you that you shouldn’t fear the potential complexity of these tools or even your own lack of knowledge. Get in there and play around. It is the best way to learn.

So, to start, let’s set the system context. I am running run Fedora 28 on an AMD Ryzen 1700X with an Nvidia GTX 10801.

The logs …


Why Won’t it Start? Troubleshooting Missing Shared Libraries in Linux

I like the puzzles posed by troubleshooting. Whenever we troubleshoot something, whether an application, a classroom exercise or assignment, a research project, or something more mundane, there are always clues as to why something didn’t go quite right. If we can uncover those clues, we have a chance to make things work better the next time we attempt the task.

What follows is an example of troubleshooting in Linux. It is not the only way, it may not even be the best way, but it is one way. Note, too, that the solution is less important than the procedure. You may have a different issue, but this process can help you discover the clues to a workable solution. One of the great strengths of Linux is the power it gives it users, but that power requires a willingness to dive in and explore. While not always easy, I have found those explorations have given me a far greater appreciation for the power and potential of the modern PC.

The Problem Game

I’ve been shopping around on different gaming platforms. I’ve always liked itch.io. Their approach to indie gaming and to the broader open source community is …


Ryzen Issues on Fedora 27

I’ve been experiencing periodic lockups on my Ryzen-based, Fedora Workstation. It’s been a constant puzzle so I went looking for a resolution. Apparently, I’m not the only one with this problem: (Kernel Bug 196683).

As a workaround, I’ve opted to set the kernel boot parameter: rcu_nocbs=0-15. Some have reported success with this, others have had to disable c6 states directly in the BIOS. I am opting for the former, for now, and hoping for the best. If I continue to have issues, I will update this accordingly.

These notes were written to remind me what I did, but they may be of use to others.

  1. Confirm that CONFIG_RCU_NOCB_CPU is set and compiled into the kernel. This is required for the rcu_nocbs setting to work. Luckily, It is compiled into the stock Fedora 27 kernel (source: Kernel Bug 196683: Comment 87).


$ fgrep CONFIG_RCU_NOCB_CPU /boot/config-$(uname -r)




If you’re using Ubuntu, you can check out Programster’s Ubuntu 16.04 - Compile Custom Kernel For Ryzen for help on compiling a custom kernel or just disable c6 states.

  1. Add rcu_nocbs=0-15 to the boot parameters. This setting is for the Ryzen 1700X which has …

© Geoffrey Gimse (Opinions expressed here are my own and are not neccessarily shared by employers, friends, or colleagues.). Built using Pelican. Except where noted, all photos are my own. Other images used on this site are in the Public Domain and available from Openclipart, or have been purchased for use via The Noun Project.