It happens rarely after updates. Mostly when there are video driver updates but today I got a black screen after updating systemd and one or two x11 files. Don’t know how to get error messages or any other kind of clue to what happened.
The solution is always get the recovery mode and run XFdrake.
Does it happens to anybody else? (It is not an whole installation problem, only updating)
Thanks
You are right.
I had the same problem after updates.
[mila@localhost ~]$ journalctl --since=2017-03-24 | grep “rpm.*installed”
bře 24 13:52:45 localhost.localdomain drakrpm-update[18377]: [RPM] lib64gcc1-6.3.1_2017.02-1-omv2015.0.x86_64 installed
bře 24 13:52:45 localhost.localdomain drakrpm-update[18377]: [RPM] lib64udev1-233-1-omv2015.0.x86_64 installed
bře 24 13:52:45 localhost.localdomain drakrpm-update[18377]: [RPM] lib64gomp1-6.3.1_2017.02-1-omv2015.0.x86_64 installed
bře 24 13:52:45 localhost.localdomain drakrpm-update[18377]: [RPM] lib64quadmath0-6.3.1_2017.02-1-omv2015.0.x86_64 installed
bře 24 13:52:45 localhost.localdomain drakrpm-update[18377]: [RPM] lib64gdbm4-1.13-1-omv2015.0.x86_64 installed
bře 24 13:52:45 localhost.localdomain drakrpm-update[18377]: [RPM] lib64sodium18-1.0.12-1-omv2015.0.x86_64 installed
bře 24 13:52:46 localhost.localdomain drakrpm-update[18377]: [RPM] hdparm-9.51-1-omv2015.0.x86_64 installed
bře 24 13:52:46 localhost.localdomain drakrpm-update[18377]: [RPM] lib64atomic1-6.3.1_2017.02-1-omv2015.0.x86_64 installed
bře 24 13:52:46 localhost.localdomain drakrpm-update[18377]: [RPM] bash-completion-2.5-1-omv2015.0.noarch installed
bře 24 13:52:46 localhost.localdomain drakrpm-update[18377]: [RPM] libgcc1-6.3.1_2017.02-1-omv2015.0.x86_64 installed
bře 24 13:52:46 localhost.localdomain drakrpm-update[18377]: [RPM] libsystemd0-233-1-omv2015.0.i586 installed
bře 24 13:52:46 localhost.localdomain drakrpm-update[18377]: [RPM] libudev1-233-1-omv2015.0.i586 installed
bře 24 13:52:46 localhost.localdomain drakrpm-update[18377]: [RPM] lib64stdc++6-6.3.1_2017.02-1-omv2015.0.x86_64 installed
bře 24 13:52:47 localhost.localdomain drakrpm-update[18377]: [RPM] x11-server-common-1.19.3-1-omv2015.0.x86_64 installed
bře 24 13:52:47 localhost.localdomain drakrpm-update[18377]: [RPM] lib64gfortran3-6.3.1_2017.02-1-omv2015.0.x86_64 installed
bře 24 13:52:47 localhost.localdomain drakrpm-update[18377]: [RPM] lib64gdbm_compat4-1.13-1-omv2015.0.x86_64 installed
bře 24 13:52:47 localhost.localdomain drakrpm-update[18377]: [RPM] libstdc++6-6.3.1_2017.02-1-omv2015.0.x86_64 installed
bře 24 13:52:48 localhost.localdomain drakrpm-update[18377]: [RPM] lib64QupZilla2-2.1.2-1-omv2015.0.x86_64 installed
bře 24 13:52:49 localhost.localdomain drakrpm-update[18377]: [RPM] binutils-2.28-2-omv2015.0.x86_64 installed
bře 24 13:52:49 localhost.localdomain drakrpm-update[18377]: [RPM] lib64cc1_0-6.3.1_2017.02-1-omv2015.0.x86_64 installed
bře 24 13:52:49 localhost.localdomain drakrpm-update[18377]: [RPM] x11-server-xwayland-1.19.3-1-omv2015.0.x86_64 installed
bře 24 13:52:50 localhost.localdomain drakrpm-update[18377]: [RPM] qupzilla-core-2.1.2-1-omv2015.0.x86_64 installed
bře 24 13:52:50 localhost.localdomain drakrpm-update[18377]: [RPM] lib64input10-1.6.3-1-omv2015.0.x86_64 installed
bře 24 13:52:51 localhost.localdomain drakrpm-update[18377]: [RPM] qupzilla-plugins-2.1.2-1-omv2015.0.x86_64 installed
bře 24 13:52:53 localhost.localdomain drakrpm-update[18377]: [RPM] gcc-6.3.1_2017.02-1-omv2015.0.x86_64 installed
bře 24 13:52:53 localhost.localdomain drakrpm-update[18377]: [RPM] gcc-cpp-6.3.1_2017.02-1-omv2015.0.x86_64 installed
bře 24 13:52:53 localhost.localdomain drakrpm-update[18377]: [RPM] qupzilla-2.1.2-1-omv2015.0.x86_64 installed
bře 24 13:52:53 localhost.localdomain drakrpm-update[18377]: [RPM] x11-driver-input-libinput-0.25.0-1-omv2015.0.x86_64 installed
bře 24 13:52:54 localhost.localdomain drakrpm-update[18377]: [RPM] libinput-1.6.3-1-omv2015.0.x86_64 installed
bře 24 13:52:54 localhost.localdomain drakrpm-update[18377]: [RPM] x11-server-xorg-1.19.3-1-omv2015.0.x86_64 installed
I needed to run the drakx11 program and again set the nouveau driver.
Bug report?
Don’t know but this could be because OM Lx 3 is now designed to NOT use traditional drivers like nouveau and instead use that xorg/mesa thingy.
In other words to test remove/uninstall any such drivers and move ‘/etc/X11/xorg.conf’ and any file pointing to video driver in ‘/etc/X11/xorg.conf.d/’ somewhere safe and reboot and see what happens.
Don’t know what to do. In my case, the driver is intel graphics. Why would OMV not use what XFdrake offers to be used?
The basic reason is that video driver manufactures haven’t done a good job of keeping up with everything else in Linux development. The process is the same remove the Intel driver package, move ‘/etc/X11/xorg.conf’ and any file pointing to video driver in ‘/etc/X11/xorg.conf.d’ to somewhere safe and reboot. What happens when you reboot is your computer is then forced to use xorg and mesa packages to achieve graphics/video. It is working well for a lot of users. And simplifies things a lot obviously.
As a way of explaining this have any of you seen the videos (they’re on you tube) where Linus Torvals complains about nVidia developers, complains some more and in some instances cusses them out. One comment was “nNidia you suck”. And Intel and AMD/Radeon/whateverhowmanynamesdotheyhave come in for their fair share of abuse as well. What he’s complaining about is how hard and sometimes impossible it is to get their code to work well and properly with the code on other parts of Linux systems.
Ben79 your starting to rant. STOP! 
Ok! I will test this Xorg/Mesa support for 3D acceleration applications.
But I also have to run hardwired applications that demand nvidia API’s that probably won’t work without proprietary support.
Asap, I’ll post the results here.
Not tested xorg support yet! But I just couldn’t test cuda programs because bumblebee does not work without proper support to nvidia drivers. To be able to do it, I have to boot kernel 4.9.10, the last one to have nvidia drivers properly builded.
I think I have the same problem with my Radeon RX 460. I did a new installation today, it booted up fine, I ran rpmi --auto-update and after a reboot I got a black screen. I tried removing xorg.conf and running XFdrake to no avail.
First: When posting about an update breaking graphic driver it is important to note if there was a kernel update or graphics hardware update. In this case I’m guessing there was a kernel update.
FWIW: The current idea is to remove xorg.conf and not use XFdrake simply reboot. This results in using only Xorg/Mesa packages for graphics so when you run 'inxi ‘G’ you’ll see no driver listed:
$ inxi -G
Graphics: Card: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
Display Server: OpenMandriva X.org 119.3 drivers: (unloaded: fbdev,vesa)
Resolution: 1920x1080@60.00hz
GLX Renderer: Mesa DRI Intel Haswell Desktop GLX Version: 3.0 Mesa 17.0.3
granted I’m using Intel and you are Radeon RX 460 but it may be worth a try to see if it works for you. Does work for a lot of users. Another way of saying is that OM Lx 3 is now designed to not use traditional graphic drivers if at all possible. If doesn’t work then likely Radeon driver kernel modules probably needs to be built for new kernel. Which needs a developer. Best way to bring to attention of developers is with a bug report.
Edit: What driver does Radeon use? What OMV package?
Oh, was about to forget. Welcome jaro. 
Is this still true?
The list of upgraded packages was quite long because like I said I did urpmi --auto-update on a fresh installation of OMV 3.01 which was released five months ago. I didn’t install any extra packages myself. Kernel was upgraded to 4.10. I’ve copied the whole list of upgraded packages here:
I was also prompted to accept removal of lib64keffects9, lib64kpmcore3, lib64kwinglutils9 and lib64kwinxrenderutils9 in order to proceed with the update.
In the meantime I’ve reinstalled the system and followed the advice from the wiki to add xorg.blacklist=ati to GRUB options which made the xorg.conf file disappear from /etc/X11/xorg.conf.d. Unfortunately after a reboot following urpmi --auto-update I got a black screen again 
My output of inxi -G:
Graphics: Card: Advanced Micro Devices [AMD/ATI] Baffin [Radeon RX 460]
Display Server: OpenMandriva X.org 119 drivers: (unloaded: fbdev,vesa) Resolution: 3840x2160@60.00hz
GLX Renderer: Gallium 0.4 on AMD POLARIS11 (DRM 3.8.0 / 4.9.0-desktop-1omv, LLVM 3.9.0)
GLX Version: 3.0 Mesa 13.0.2Ben79,
No, It is no longer true. The last two kernel versions (4.10.10 and 4.10.11) and nvidia 378.13.1 do work fine.
When the write window is open look on top line for the < /> icon.
Sorry wasn’t able to help your problem, at least yet. There was a kernel update:
kernel-release-desktop-4.10.11-1omv
but do know I’m speculating that is possible cause of problem. Could you one time try removing ‘xorg.conf’ and ‘xorg.blacklist=ati’ and rebooting?
Edit: If that doesn’t work it’s time for bug report.
Wow, that is good to know.
You were right about the kernel update being the culprit. I did another clean install, went to the Control Center to update the system, selected all packages except for the kernel-* packages. After the update finished I rebooted the system and could log in fine. So just to be sure I updated the kernel-* packages. After a reboot I got a black screen again. So now I have to select in GRUB to boot with 4.9 kernel which is working just fine.
Should I report a bug?
Great, thanks. If you do get it resolved please also let everyone know here and mark as solved.
Jaro will you please try adding the following options to the grub boot line before booting.
These lines will prevent one or both of the available ATI graphics drivers from loading.