Hey, new computer, had old fedora 25 install, decided to wipe it because it’s a new system, and after nvidia driver installation, i was getting freezes after a day of usage, after 2 or 3 days these freezes became more frequent, 10 or 15 minutes after booting up the system freezes almost completely (if i have a music playing, sometimes the music will continue playing, then freeze, then play, the cursor will also slowly move like a in slideshow).
Switched to an older kernel, with nouveau drivers and so far, everything seems normal. Any idea on how to debug this? Drivers were installed using npm repo (dnf install xorg-x11-drv-nvidia akmod-nvidia). System info below, gpu is gtx 760 not sure why it’s not showing up.
Both .15 and .14 give me problems, on .13 i don’t have access to anything but nouveau, so it works.
And yeah, weird that i don’t have that on my terminal history, the kmod-nvidia drivers. I don’t remember installing anything in batch or by script.
Either way i’m about to reinstall fedora 27 to see if it works this time. If it doesn’t, i’ll try 26.
I would suggest, update fully.
Then use the negativo17 repo for nvidia drivers, ive had good luck with these in the past (i dont use nvidia cards anymore).
You may need to run dracut -f after installing the drivers. I recommend going the dkms-nvidia route. It seems to build them nicer and more consistantly.
Welp, just got another freeze. I got one on the first day, but i was asleep when it froze so i wasn’t sure, now it happened again during normal usage (no games or any heavy processing). Any idea on how to debug this?
bump ;_; anyone got any idea on what’s going on? I’m not even sure if it’s the driver’s fault anymore, since it takes so long to freeze and there doesn’t seem to be any trigger to it.
Yeah, there are some bugs but they’re not anything you wouldn’t always find (there’s always a few people with system freezes on F25, 26, 27…).
I just noticed there’s a kernel update, so i’ll try it out and see what’s up. I was going to change the OS but i’m not sure if that will solve anything.
@wendell ever had this happen to you/any idea how to debug it? (tl;dr fedora 27 randomly freezes, can take 10 hours or 10 minutes, no apparent trigger, new pc, fresh install, didn’t happen on old f25 installation)
I’m not sure if this would fall into your issue but I have been having issues with the nvidia 390.25 driver on kernel 4.15.3-2. I’ve been dealing with lagging and tearing for over a week now. Here is the nvidia forum post.
My ole nvidia based laptop, has a 9800mgs, freezes in linux for seemingly no reason on 340. Been hearing the same problem go around lately,o you’re not the only one with weild issues
Hi, I just built a system with a Ryzen R7 1700 myself, and I have similar problems. I think that the problem might be the Linux + Ryzen combo (on certain Ryzen chips, not all). I found a bug report on kernel.org about an issue similar to this. There was also a thread on this forum that I found to be less relevant to our respective issues as the OP claimed to have solved it by removing a dodgy WiFi card.
Specifications of the desktop:
AMD R7 1700
ASUS Prime X370-PRO Motherboard
MSI RX 560 2GB
2x8GB 2666MHz Ballistix DDR4 RAM
Seasonic FOCUS Plus Series SSR-750FX 750W 80+ Gold PSU
What I’ve done to troubleshoot so far:
Replaced old janky Radeon HD 7950 w/ RX 560
Needs more testing (I installed it yesterday); I got a single lockup so far
Tried disabling “Global C-state Control” in BIOS (suggested in the kernel.org bug report i linked to)
Got 17 hours uptime; needs more testing
This is why I liked @wendell’s comment about trying this
I have a Thinkpad P51 with a Maxwell-based Quadro M1200M and an Intel i7 7700HQ; Fedora 27 runs well enough. Very rarely do I get lockups. Because my laptop’s GPU is similar to yours, I’d say that Nvidia is not the prime suspect here.
More about the P51:
It runs Fedora 27
It uses the RPMFusion Nvidia drivers (version 390.XX)
It has 3x8GB 2400MHz DDR4 RAM (1x stock Samsung DIMM, 2x Crucial DIMM)
Essentially, it seems like there is a problem with Ryzen chips entering and/or exiting deep-sleep states (C6). It is uncertain whether or not an issue is present at the software level, or the hardware level. Not every chip seems to be affected. There is heresay that Windows has disabled C6 on Ryzen as a workaround (or actually implemented some other fix). This is, to best of my knowledge, the latest on the issue. I’ll be doing more testing on my end. If you have read through this, then please, join me in testing this and post any news about this.
