1

Been going crazy with this since yesterday. I'm running a Geforce 710 using the nvidia-440 driver which I downloaded from the Ubuntu reps, and suddenly after about 3 hours of gaming yesterday, system froze, rebooted, then driver wouldn't load. Purged, reinstalled, nada. Then tried purging, checking gcc version for building .run file directly from nvidia, won't build. Purged all that work, reinstalled 440 again through ubuntu-drivers autoinstall, worked then rebooted and gone again. Tried various drivers none work. Then suddenly 440 worked again. Then rebooted, didn't work, then rebooted again and now working. I really have no clue what is happening but was inches away from putting Windows 10 on this machine. I've read hundreds of forums at this point and all recommend troubleshooting the way I have, but the problem is I'm not getting any kind of consistent results. Does anyone know what is going on here?

Improve this question

3 Answers 3

Reset to default
1

Ooooh! I might have just figured something out. I think this has something to do with LightDM starting before the nvidia driver loads. If I do not login, and first drop to command line using ctrl alt f1, then sudo service lightdm stop, then start it up again, it seems to work correctly. At least it did a couple times in a row for me now. I'll post here again if any new developments.

Improve this answer
1
  • Confirmed this workaround works. Kind of annoying, but at least the card is functioning.
    – Justin Wierbonski
    Feb 17, 2020 at 17:22
1

I had the same issue today, you should just use the appcenter to install 390 or even 430, the performance difference shouldn't be noticable. Were just going to have to wait a little while while the kernel team sorts all the issues around 5.3 Hope you stay with us!

Improve this answer
1
  • Well, 440 has been working for me now, I just have restart lightdm. I think if there were a way to delay it from starting a few seconds, the issue would be resolved.
    – Justin Wierbonski
    Feb 14, 2020 at 23:15
1

Seems like today's update to 5.3.0.4 and xserver updates fixed the issue!

Improve this answer
1
  • Just letting others know that it still does happen sometimes, but restarting lightdm always fixes it.
    – Justin Wierbonski
    Feb 26, 2020 at 12:33

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.