I installed 17 on my system and once logged into the installed system I tried to install the fglrx-updates package and then apply all updates from apt-get. There was 400 + meg since the base install is around 4 months old. When I reboot the boot splash appears and then disappears after what I would call a typical boot period and goes to a black screen and stays there. I tried to reinstall again and install the proprietary driver and run the update from Muon. I noticed this time that it asked if I wanted to keep an old or use a new version of Xsession. I am sorry I did make great notes on this. This time though I opted to say keep the old thinking the update may have caused X corruption since the system appeared to freeze at the point that X would be loading. Note at this point I could not even get to TTY1 in either of my installs. This second time with the old Xsession loaded a very corrupted Xsession with a lot of collored lines but nothing you could make out or navigate from. I reinstalled again and loaded the proprietary driver and left well enough alone except I would think I should be able to run updates for security reasons. Netrunner is Kubuntu based and I have installed version 15.10 and installed AMD driver and updated and never had an issue. Any ideas?

I seem to be having a similar issue as the OP. I have experienced the black screen with just a pointer on it on both virtual and metal installations. I have also tried re-installation on both with the same result. I also tried keeping the old Xsession on each with no difference.
I did see a thread with similar symptoms, but it appears to be related to sddm's issues with encrypted home directories and I didn't encrypt on my virtual installations.
Any help would be appreciated, I really like what I have seen of the distro, and am hoping to make it my primary distro, but this issue is making it difficult.

Thank you for the replies people. I am currently running Netrunner 17 without any updates and with the fglrx base driver installed. It appears to be running fine at this time. I am pretty certain if I run Muon Update, it would be at the black screen again. I have an awesome video card, why not take full advantage of it. I like the idea of open source software and drivers but if they can't take full advantage of the hardware I spent good money on, I will take advantage of the proprietary drivers. I started with computers for the awesome gaming experience so I want the full abilities of my hardware. That being said. Netrunner appears to have some regression with the base Kubuntu. I can install Kubuntu 15.10 and install fglrx drivers from the additional drivers utility. Then install all the available updates from Muon and have a boot-able system. I cannot get the same outcome with the install of Netrunner 17 and following the same logical post install path. Ideas

(20th March 2016, 4:32)bobbblll Wrote: Thank you for the replies people. I am currently running Netrunner 17 without any updates and with the fglrx base driver installed. It appears to be running fine at this time. I am pretty certain if I run Muon Update, it would be at the black screen again. I have an awesome video card, why not take full advantage of it. I like the idea of open source software and drivers but if they can't take full advantage of the hardware I spent good money on, I will take advantage of the proprietary drivers. I started with computers for the awesome gaming experience so I want the full abilities of my hardware. That being said. Netrunner appears to have some regression with the base Kubuntu. I can install Kubuntu 15.10 and install fglrx drivers from the additional drivers utility. Then install all the available updates from Muon and have a boot-able system. I cannot get the same outcome with the install of Netrunner 17 and following the same logical post install path. Ideas

the problem is that I have installed Netrunner again, have performed an update, only the latest Linux kernel have 4.5 installed, then the latest Mesa driver.

started computer and now I land in console mode and must always enter startx, so that the desktop starts.

The problem of Netrunner is SDDM ... the worst problems! And if you google, you will find extremely many problems with SDDM. Extremely many users can not log in after updating to 5.5.3 Plasma, but will have to type startx.

Unfortunately Netrunner has not paid attention to something. I do wonder how it will look like with the quality of Netrunner, the looks are not everything.

So Netrunner .... where are the solutions?

Because Netrunner I have about 6 hours of my life consumed by your botch to get down again.

but not surprised you, if this is not there sddm.config, I am surprised at some Netrunner so no longer.

it should not be there, You must you 24 hours around the clock are pleased that a new update is available, nähmlich that unstable, catastrophic SSDM 0.13. This please do not install, but as long as do not install until a correct, working version is available!

That should have known Netrunner, is well known since January and still cheer you this broken part via update below. Irresponsible something!

20th March 2016, 8:36 Edited(This post was last modified: 20th March 2016, 8:37 by strykenKN.)

and even a hint, only changes nothing in sddm, otherwise after starting the computer, the screen white and her whatâ press anything else. Netrunner is afflicted absolutely immature and extremely many errors, therefore usually hands off of it and prefer yum original Ubuntu!

it is quite clear to sddm 0.13 and if you google for sddm 0.13, you can find hundreds of pages of that there are problems with it since August.

Since August is promised that you want to fix the error to the release 0.14, but now we have almost April and it has done nothing.

The problem is, if the old version retains 0.13 and e.g want you can log in without password, it can happen that the computer again does not go to desktop mode and the screen simply remains white.

KDE 5.5.3 is fraught with extremely many errors. Something may be published in any way as Final.

A new customer like me who does not know that and Netrunner or Kubuntu installed is so driven to madness. For 12 hours I'm around with your Netrunner and I Eaves my hair, because there are only problems.

Something may not be easy if you want to use an OS productive and with such an error may sowas called Final, especially when since August you know sddm caused 0.13 big mistakes.

20th March 2016, 21:46 Edited(This post was last modified: 20th March 2016, 22:00 by strykenKN.)

but exact sddm 0.13 causes immense problems and if you google after that teem in the forums only way of errors and problems with the sddm 0.13 and with sddm 0.14 to allegedly provide a fix, but that was promised by the KDE team in August and soon we of April.
I installed sddm 0:13 and already the problems begin, I land at boot back into the console and must "startx, so that the desktop loads at all.
Here is my log:

I see your system is using prime-switch to switch between the Intel chip and the NVIDIA chip.
This means that your running your hybrid system using nvidia-prime instead of bumblebee, would this be correct?