Controllers and Sleeping - Getting into the Linux Mindset

I have recently converted my personal computer to 100% Linux duty. I have dabbled in Linux before, but have always found myself back on Windows due to requiring proprietary software for college.

I am having my best Linux experience so far using Fedora 25. But I have a few issues. I want to figure out these problems by myself, but I find that I cannot help myself because my approach method to troubleshooting problems is wrong.

There are 2 issues I am experiencing:
1) my onboard sound cuts out after I resume from hibernation (more of annoyance)
2) my PS4 controller is recognized by the system (shows up in lsusb command) but will not work in any games

I don't expect to get the first one fixed, nor do I consider it a "deal breaker". However, I would like to get my controller working in games. From the forum trolling I have done it seems to be a permissions issue. Why would this be the case? My keyboard and mouse are USB peripherals but work in game, why would a controller not work in game?

If you can help me answer these questions, I am positive I can find the answer in how to get my controller working in games if I understand the why.

I don't know if I have the answer to your problem and I am new to Linux, but have you tried a different distortion of Linux. I had trouble seting up Plex Media Server on Fedora 25, so I setup a virtual machine on Fedora 25 and installed Ubuntu, I didn't have any problems installing Plex on Ubuntu. I my opinion there isn't a perfect Linux distro you might have to run different Linux distro's for different tasks. At least that has been my expereance.

I had a problem with a usb gamepad once in linux; the problem was that a different gamepad was assigned to js0 in /dev/input. Unplugging that one and restarting was as close as I came to a solution. You can figure out what physical device a dev file corresponds to by using cat on the file, then mashing the buttons. If it's the same controller, you'll see a bunch of crap get typed out. That's all I know, happy troubleshooting!