Mageia forum

Since the most recent set of updates, I have been having a strange error on video. My self-built PC is currently using an NVIDIA GT 730 card with the GeForce 630 series and later driver, and a maximum screen resolution of 1920 x 1080.

Upon booting, Plymouth come up as normal but a message comes up in the top left corner: "Building nvidia-current driver..." and shortly thereafter a message:
"Display driver issue
Detected a loaded display driver kernel module which conflicts with the driver the X server is configured to use. Startup of the X server may fail" and indeed it does.

However, if I restart in Recovery Mode, sign in as root and then either "exit" or "systemctl default", the message "building nvidia-current driver" pops up again and I am into Plasma apparently with no difficulty. I am sitting using Plasma right now and the only "issue" seems to be with the nvidia-current driver.

This is an inconvenience and seems strange, and any advice would be appreciated.

Andrew

Could you please post what kernel/nvidia packages you have currently installed?

Code: Select all

rpm -qa|grep -iE "nvidia|kernel"|sort

Well, duh! What did I forget to do???

Code: Select all

dkms-nvidia-current-430.64-8.mga7.nonfree
kernel-desktop-5.4.10-1.mga7-1-1.mga7
kernel-desktop-5.4.12-1.mga7-1-1.mga7
kernel-desktop-5.4.17-1.mga7-1-1.mga7
kernel-desktop-5.4.2-1.mga7-1-1.mga7
kernel-desktop-5.4.6-2.mga7-1-1.mga7
kernel-desktop-5.5.14-1.mga7-1-1.mga7
kernel-desktop-5.5.15-3.mga7-1-1.mga7
kernel-desktop-5.5.4-1.mga7-1-1.mga7
kernel-desktop-5.5.6-2.mga7-1-1.mga7
kernel-desktop-5.5.9-1.mga7-1-1.mga7
kernel-desktop-5.6.6-1.mga7-1-1.mga7
kernel-desktop-devel-5.4.10-1.mga7-1-1.mga7
kernel-desktop-devel-5.4.12-1.mga7-1-1.mga7
kernel-desktop-devel-5.4.17-1.mga7-1-1.mga7
kernel-desktop-devel-5.4.2-1.mga7-1-1.mga7
kernel-desktop-devel-5.4.6-2.mga7-1-1.mga7
kernel-desktop-devel-5.5.14-1.mga7-1-1.mga7
kernel-desktop-devel-5.5.15-3.mga7-1-1.mga7
kernel-desktop-devel-5.5.4-1.mga7-1-1.mga7
kernel-desktop-devel-5.5.6-2.mga7-1-1.mga7
kernel-desktop-devel-5.5.9-1.mga7-1-1.mga7
kernel-desktop-devel-5.6.6-1.mga7-1-1.mga7
kernel-desktop-devel-latest-5.6.6-1.mga7
kernel-desktop-latest-5.6.6-1.mga7
kernel-firmware-20190603-1.mga7
kernel-firmware-nonfree-20200316-1.mga7.nonfree
kernel-userspace-headers-5.6.6-1.mga7
nvidia-current-doc-html-430.64-8.mga7.nonfree
nvidia-current-utils-430.64-8.mga7.nonfree
virtualbox-kernel-5.4.10-desktop-1.mga7-6.0.14-18.mga7
virtualbox-kernel-5.4.12-desktop-1.mga7-6.0.16-1.mga7
virtualbox-kernel-5.4.17-desktop-1.mga7-6.0.16-4.mga7
virtualbox-kernel-5.4.2-desktop-1.mga7-6.0.14-10.mga7
virtualbox-kernel-5.4.6-desktop-2.mga7-6.0.14-16.mga7
virtualbox-kernel-5.5.14-desktop-1.mga7-6.0.18-8.mga7
virtualbox-kernel-5.5.15-desktop-3.mga7-6.0.20-1.mga7
virtualbox-kernel-5.5.4-desktop-1.mga7-6.0.18-1.mga7
virtualbox-kernel-5.5.6-desktop-2.mga7-6.0.18-4.mga7
virtualbox-kernel-5.5.9-desktop-1.mga7-6.0.18-5.mga7
virtualbox-kernel-5.6.6-desktop-1.mga7-6.0.20-2.mga7
virtualbox-kernel-desktop-latest-6.0.20-2.mga7
x11-driver-video-nvidia-current-430.64-8.mga7.nonfree

I'm on it now... thanks for reminding me, doktor!

Can you post the output as root of

Code: Select all

dkms status

The root output of dkms status was:

nvidia-current, 430.64-8.mga7.nonfree, 5.6.6-desktop-1.mga7, x86_64: installed
virtualbox, 6.0.20-1.mga7, 5.6.6-desktop-1.mga7, x86_64: installed-binary from 5.6.6-desktop-1.mga7


However, this is after I corrected the error... unfortunately, whilst removing old kernels, I accidentally removed the current kernel! I had to go back to a netinstall to correct this by an 'upgrade'. Since then, there has been no unusual activity.

This alerted me to the fact that my other (portable) machines had a lot of old kernels which needed to be removed, so I removed them in MCC, then updatedb and update-grub2. All systems now seem to be OK, but in fact, I had no problem with the other systems. The affected system was my main box, in which I had replaced an old 500Gb boot drive with a new 2Gb Seagate, split into three main partitions (mainly /home and another Gb reserved separately for storage).

Anyway, this experience has reminded me of what I should do after updating the kernel!

So the actual problem doesn't persist anymore? Then please mark the thread [DONE], thanks in advance.

andrewholmes wrote:However, this is after I corrected the error... unfortunately, whilst removing old kernels, I accidentally removed the current kernel! I had to go back to a netinstall to correct this by an 'upgrade'. Since then, there has been no unusual activity.

Why run a netinstall then? Simply install back the kernel that you removed, done.

Yes, I can confirm that this thread is done. As a matter of fact, I just updated my main boxen with kernel 5.6.8 and updated as in my previous posting.

Why run a netinstall then? Simply install back the kernel that you removed, done.

Unfortunately, I was unable to reboot into the system. However, each of my systems has a copy of the 7.1 netinstall ISO so I cut a new CD (I'm always losing my CDs) and ran it from that.

doktor5000 wrote:Then please mark the thread [DONE], thanks in advance.

FWIW, to do that, you need to edit the subject of the first post - just saying, for next time.

Got it, thanks.