Ask Your Question
1

Cannot log in to graphical desktop Fedora 23, kernel 4.4.8-300

asked 2016-05-09 07:02:42 -0500

this post is marked as community wiki

This post is a wiki. Anyone with karma >750 is welcome to improve it.

All working fine until this morning. Small update yesterday to x-org, which I suspect has something to do with this. been happily using nvidia driver 316.xx for a couple of months.

I've just got the "aw snap, something went wrong" screen of death!

Yeah I know we're supposed to now digest hundreds and hundreds of pages of densely written instructions on journalctl and systemd and how wonderfully efficient it all is at logging... To be frank I don't have all day to sit banging my head or taking a computer science class. Am able to follow clearly written instructions though ;0)

Can somebody please tell me where to start?? I simply need to get back to where I was yesterday when everything was working fine. If Fedora/Linux really is this unstable and able to break in an instant, to be honest I'm not sure it's really fit for purpose for a daily use machine, but my offloading aside, can somebody please tell me what to look for, in which log, in which terminal, in order to fix/remove/update the offending item?? I can't believe I'd consider going back to Windows after my brief but frustrating love affair with Fedora!

edit retag flag offensive close merge delete

Comments

rather than attempt to wade through the endless documentation (which I don't fully understand) on a hunch I simply uninstalled the nvidia drivers and restored everything. It now works perfectly - so clearly the problem is related to support or installation of the official nvidia driver. Note that I am NOT using a repo for this but have followed instructions elsewhere to install the driver from the nvidia site. If my video replay remains flicker free, I may simply keep things like this - the video replay and screen flicker/tear being the ONLY reason I went down the nvidia route

thingummybob gravatar imagethingummybob ( 2016-05-09 12:16:53 -0500 )edit

2 Answers

Sort by » oldest newest most voted
0

answered 2016-05-11 09:54:28 -0500

genodeftest gravatar image

What did you do last before this happened? Did you update nvidia or your kernel, or any other package? dnf history list and dnf history info [history ID] should give you details. If you prefer graphical applications, try yumex-dnf instead.

This issue might be related to Wayland. You may want to edit /etc/gdm/custom.conf as root and add the line WaylandEnable=true in section [daemon], then restart your computer.

Also, please have a look at this wiki answer and follow the steps described there.

edit flag offensive delete link more
0

answered 2016-05-12 03:16:57 -0500

thingummybob gravatar image

To try to be clearer: I had been happily running under nvidia drivers for a month or more, following the in-depth guide to install the official (and newly updated) nvidia drivers, all very well documented here:

https://www.if-not-true-then-false.co...

Everything ran exactly as described on that page - got all the same results etc. and all seemed to fine. No problems or crashes. A few little niggles later but nothing serious. Further to other help/advice received here, a routine "dnf --refresh upgrade" found a few recent upgrades to x-org (which shouldn't be running under nvidia right?) but which I agreed to install as there were no warnings about dependencies or such. Computer continued to run fine afterwards, so thought nothing of it. Next morning when I went to boot up, suddenly I'm in trouble.

If this does constitute "an answer" it's simply because on a hunch I uninstalled the nvidia drivers (basically the reverse procedure, also well documented at same site) and noted that everything was immediately restored to a working state. Perhaps importantly, I changed something which I might have otherwise completely overlooked. I'd bought an hdmi cable to connect the graphics card and monitor - partly to test the inbuilt speakers and also to see how Pulse handled the audio. I'd left everything like that until the other day. When the difficulties showed up, part of my testing was to remove the hdmi cable and go back to dvi and desktop speakers. Funnily enough (or not) the little niggles I'd been having, such as the plymouth boot screen being completely the wrong resolution, plus things like desktop recovery after screen timeout (functional but a bit slow) all suddenly sprang into full function.

So, much as I don't really understand either what the specific problem was or exactly why I fixed it, I tend to feel that however well written the above guide is, there's some important difference between installing those drivers under hdmi than dvi, and that the hdmi just doesn't work properly. I further noted that the SINGLE reason I'd even bothered with the nvidia drivers, which was to enable full glx rendering under vlc to avoid the 'dreaded' screen tears and flickering, have also completely disappeared now, so I've no need to go anywhere near the nvidia drivers again, particularly as Wayland is being improved daily. I'm actually logged in under gnome, where it says

"Gallium 0.4 on NVC8" whatever that is exactly, but it works fine. And besides, Wayland still has this unbelievably irritating issue where it will insist on keep opening new windows (i.e. terminal) not at the last used location but always at top left. Can't believe how tiresome it is to have to keep moving those.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2016-05-09 07:02:42 -0500

Seen: 611 times

Last updated: May 12 '16