[SOLVED]Kernel cannot use the graphics drivers after update.

This forum is dedicated to testing early releases and cauldron : Howtos, tips, tricks and user global feedback and thoughts...

Helpful tip :
For bugs tracking we use : https://bugs.mageia.org = The Mageia Bug Tracker
In this bug tracker you'll find already reported bugs and you'll be able to report those you have found....

[SOLVED]Kernel cannot use the graphics drivers after update.

Postby banjo » Feb 26th, '19, 04:38

I am running Mageia 7 Beta 1.

After the latest updates, which installed kernel 1.20.12-desktop-2.mga7, my computer can no longer use the Nvidia drivers that it was using before. I have not changed the drivers. I simply ran the recent updates.

During the boot process, it displays the following error.

driver-error-IMG_2775.jpg
Kernel error during the boot.
driver-error-IMG_2775.jpg (85.39 KiB) Viewed 2872 times


After that, the boot hangs at the following messages.

driver-error-IMG_2773.jpg
The last messages during the boot.
driver-error-IMG_2773.jpg (141.1 KiB) Viewed 2872 times


I booted using the previous kernel, 4.20.11-desktop-1.mga7, and it throws the same error.

Is it trying to use the default driver again? Do I need to re-install the Nvidia drivers? Did the Nvidia drivers fail to build properly?

I booted into recovery mode and got to a command line, so at least I can log in as root. I am at a loss about what to do next.

How do I synch up the kernel and the graphics drivers from the command line?

How would I install the next updates to see if that will fix it?

Any help about where to start fixing this would be much appreciated.

Thanks,
Banjo
(_)=='=~
Last edited by banjo on Feb 28th, '19, 17:24, edited 1 time in total.
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 445
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Kernel cannot use the graphics drivers after update.

Postby benmc » Feb 26th, '19, 05:51

hi,

seems your display manager is running,
open a tty a (alt + ctrl + F2) and login as usual user

then
Code: Select all
startx startkde
(for plasma or startlxde for LXDE... etc)
if desktop does not display, then the following from the the same tty, otherwise from the desktop.

open a terminal as root:
Code: Select all
urpmi --auto-update

it may be that the newer kernel had arrived at your localest mirror, but the associated dkms package had not.
reboot and see if the dkms module rebuilds your nvidia driver and installs it.
(should indicate this during the plymouth splash screen)

if not then as root:
Code: Select all
drakx11

choose the correct driver. do not need to run the" test" function.
reboot, choose the latest kernel and it should run the dkms module and build the driver for your kernel.

if it does not indicate that the kernel module is being built and installed, you may need to reinstall your dkms-nvidia module
as root:
Code: Select all
urpme dkms-nvidia
and if you press tab here, it will auto-fill or at least give you some nvidia option ie: dkms-nvidia304, dkms-nvidia340... etc.

then
Code: Select all
urpmi dkms-nvidia****
what ever you have just removed.

advise if still problems.

p.s. note that nvidia304 driver is no longer supported, so remove it and install the nouveau driver.
benmc
 
Posts: 1175
Joined: Sep 2nd, '11, 12:45
Location: Pirongia, New Zealand

Re: Kernel cannot use the graphics drivers after update.

Postby banjo » Feb 26th, '19, 18:46

Thank you for the suggestions. I tried all of them, and none of them helped the problem. It still reports that the loaded display driver kernel module conflicts with the driver that the X server is configured to use.

I did all of the updates using urpmi --auto-update.

I uninstalled and then reinstalled dkms-nvidia340, which should be the proper driver for my card.

I ran drakx11 and it indicated that the driver was the nvidia driver. I confirmed the nvidia driver as the correct driver and told it to save the config. That apparently worked partly because xorg.conf is calling for the nvidia driver.

I dumped out /etc/X11/xorg.conf to see what the xserver is looking for.

driver-error-IMG_2796.jpg
xorg.conf display information
driver-error-IMG_2796.jpg (72.26 KiB) Viewed 2856 times


I then dumped out the inxi info.

driver-error-IMG_2797.jpg
Inxi information
driver-error-IMG_2797.jpg (65.8 KiB) Viewed 2856 times


Apparently, whatever is telling inxi its information appears to be calling for the nouveau driver.

Where does inxi get its information?

I don't know how to put the nouveau driver back into xorg.

I installed the nvidia driver because the nouveau driver was doing a very bad job with unpainted damage areas and tearing etc. so I don't know how far the nouveau driver will take me.
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 445
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Kernel cannot use the graphics drivers after update.

Postby doktor5000 » Feb 26th, '19, 19:02

banjo wrote:Where does inxi get its information?

Probably from lspci -k which shows the currently loaded kernel module for each device.

Can you post the output of
Code: Select all
rpm -qa|grep -iE "kernel|nvidia"|sort

and please check whether you have nomodeset in the kernel options for the kernel that you're trying to boot.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Kernel cannot use the graphics drivers after update.

Postby banjo » Feb 26th, '19, 19:46

Here is the command line for the boot.

Code: Select all
[poobah@localhost /proc]$ cat cmdline
BOOT_IMAGE=/boot/vmlinuz-4.20.12-desktop-2.mga7 root=UUID=35487fac-29f4-4fc1-a385-81c09a642f44 ro splash quiet noiswmd nokmsboot resume=UUID=77aed617-be09-48c7-a04f-605c6dc76456 audit=0 vga=788


I do not see nomodeset in the list of arguments.

Here is the list of packages.

Code: Select all
[poobah@localhost ~]$ rpm -qa | grep -iE "kernel|nvidia|sort"
kernel-desktop-4.20.2-1.mga7-1-1.mga7
kernel-desktop-devel-4.19.12-3.mga7-1-1.mga7
kernel-desktop-devel-latest-4.20.12-2.mga7
kernel-desktop-4.19.9-2.mga7-1-1.mga7
kernel-desktop-devel-4.20.2-2.mga7-1-1.mga7
kernel-desktop-4.19.12-1.mga7-1-1.mga7
kernel-desktop-devel-4.19.13-1.mga7-1-1.mga7
kernel-desktop-devel-4.20.7-2.mga7-1-1.mga7
kernel-desktop-4.20.3-2.mga7-1-1.mga7
kernel-firmware-20190114-1.mga7
kernel-desktop-4.19.12-3.mga7-1-1.mga7
kernel-desktop-4.20.7-1.mga7-1-1.mga7
kernel-desktop-4.20.6-2.mga7-1-1.mga7
kernel-desktop-devel-4.19.14-1.mga7-1-1.mga7
kernel-desktop-devel-4.20.12-2.mga7-1-1.mga7
dkms-nvidia340-340.107-4.mga7.nonfree
kernel-desktop-4.20.1-1.mga7-1-1.mga7
kernel-desktop-devel-4.20.3-2.mga7-1-1.mga7
kernel-desktop-4.19.12-2.mga7-1-1.mga7
kernel-desktop-devel-4.20.3-1.mga7-1-1.mga7
kernel-desktop-4.19.6-3.mga7-1-1.mga7
kernel-desktop-4.19.14-1.mga7-1-1.mga7
kernel-firmware-nonfree-20190221-1.mga7.nonfree
kernel-desktop-devel-4.20.4-1.mga7-1-1.mga7
kernel-desktop-devel-4.20.1-1.mga7-1-1.mga7
kernel-desktop-devel-4.20.2-1.mga7-1-1.mga7
kernel-desktop-4.19.13-1.mga7-1-1.mga7
kernel-desktop-devel-4.20.8-2.mga7-1-1.mga7
kernel-desktop-4.20.4-1.mga7-1-1.mga7
kernel-desktop-4.19.10-1.mga7-1-1.mga7
kernel-desktop-devel-4.19.12-1.mga7-1-1.mga7
kernel-desktop-4.20.6-3.mga7-1-1.mga7
kernel-desktop-4.20.9-1.mga7-1-1.mga7
kernel-desktop-4.19.10-2.mga7-1-1.mga7
kernel-desktop-devel-4.20.6-3.mga7-1-1.mga7
kernel-desktop-4.20.7-2.mga7-1-1.mga7
kernel-desktop-4.20.11-2.mga7-1-1.mga7
kernel-userspace-headers-4.20.12-2.mga7
kernel-desktop-4.20.2-2.mga7-1-1.mga7
kernel-desktop-devel-4.20.2-3.mga7-1-1.mga7
kernel-desktop-devel-4.20.11-2.mga7-1-1.mga7
kernel-desktop-4.20.8-2.mga7-1-1.mga7
kernel-desktop-devel-4.20.7-3.mga7-1-1.mga7
kernel-desktop-4.20.3-1.mga7-1-1.mga7
kernel-desktop-devel-4.20.7-1.mga7-1-1.mga7
kernel-desktop-devel-4.20.9-1.mga7-1-1.mga7
kernel-desktop-4.20.2-3.mga7-1-1.mga7
kernel-desktop-devel-4.19.12-2.mga7-1-1.mga7
kernel-desktop-4.20.7-3.mga7-1-1.mga7
kernel-desktop-4.20.12-2.mga7-1-1.mga7
kernel-desktop-4.19.9-1.mga7-1-1.mga7
kernel-desktop-devel-4.20.6-2.mga7-1-1.mga7
kernel-desktop-latest-4.20.12-2.mga7


I have managed to get the graphics to boot up by editing /etc/X11/xorg.conf and changing the driver in the Section "Device" from "nvidia" to "nouveau". So it appears that the kernel is stuck on loading nouveau regardless of which driver I installed with drakx11. Once the kernel and xorg agree on the driver, it works.

Even though it boots now, I want to understand what is going on and why it gets stuck on nouveau.

What does "nomodeset" do, and how do I get it in the list?
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 445
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Kernel cannot use the graphics drivers after update.

Postby banjo » Feb 26th, '19, 20:48

I looked up "nomodeset", and apparently I do not need that switch in the argument list since the graphics do work using the nouveau driver. So the missing "nomodeset" should not be an issue with running the nvidia drivers.

By the way, the plymouth splash screen changed between the most recent kernel and the previous one. The latest one fits the screen better. The aspect ratio of the splash screen was incorrect until this latest update. I don't know if that is relevant or not.
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 445
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Kernel cannot use the graphics drivers after update.

Postby doktor5000 » Feb 26th, '19, 21:16

banjo wrote:I do not see nomodeset in the list of arguments.


banjo wrote:I looked up "nomodeset", and apparently I do not need that switch in the argument list since the graphics do work using the nouveau driver. So the missing "nomodeset" should not be an issue with running the nvidia drivers.


nokmsboot is an alias for nomodeset, so if you have either one you're OK. And it's required for the proprietary drivers, as otherwise you end up with a different driver being loaded, those that come with the kernel and which are being already loaded in initrd (nouveau in this case) and hence later other drivers cannot be loaded anymore.

So currently you should be fine regarding kernel boot options.

Can you please also add the output as root of
Code: Select all
dkms status
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Kernel cannot use the graphics drivers after update.

Postby banjo » Feb 27th, '19, 00:56

Here is the output.

Code: Select all
[root@localhost poobah]# dkms status
nvidia340, 340.107-4.mga7.nonfree, 4.20.12-desktop-2.mga7, x86_64: installed
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 445
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Kernel cannot use the graphics drivers after update.

Postby doktor5000 » Feb 27th, '19, 20:00

Looks fine to me.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Kernel cannot use the graphics drivers after update.

Postby benmc » Feb 27th, '19, 20:11

have a look at => https://bugs.mageia.org/show_bug.cgi?id=24436

(NVidia driver not functioning since Kernel 4.20.12-1 )
benmc
 
Posts: 1175
Joined: Sep 2nd, '11, 12:45
Location: Pirongia, New Zealand

Re: Kernel cannot use the graphics drivers after update.

Postby marydou » Feb 27th, '19, 23:52

benmc wrote:have a look at => https://bugs.mageia.org/show_bug.cgi?id=24436

(NVidia driver not functioning since Kernel 4.20.12-1 )


All these problems with NVidia could they be just a bad update that will be fixed or does it mean it's better to invest in an AMD card?
marydou
 
Posts: 6
Joined: Feb 17th, '19, 21:19

Re: Kernel cannot use the graphics drivers after update.

Postby banjo » Feb 28th, '19, 00:32

All these problems with NVidia could they be just a bad update that will be fixed or does it mean it's better to invest in an AMD card?


This is cauldron, after all. :lol: I suspect that halt-and-catch-fire is expected on occasion.

Banjo
(_)=='=~
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 445
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Kernel cannot use the graphics drivers after update.

Postby banjo » Feb 28th, '19, 15:31

I just added "nomodeset" to the grub command line and reset the system to use the nvidia drivers. It boots into nvidia graphics fine now using nvidia340.

So now I have both "nokmsboot" and "nomodeset" in the kernel switches and it works.

Perhaps something has changed in the kernel in the handling of those switches.

I have posted this same information on Bugzilla

https://bugs.mageia.org/show_bug.cgi?id=24436

Banjo
(_)=='=~
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 445
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: [SOLVED]Kernel cannot use the graphics drivers after upd

Postby banjo » Feb 28th, '19, 17:33

I have marked this SOLVED because the change to adding nomodeset to the boot parameters fixed my problem. Whatever change was made to the kernel still needs to be fixed or documented, but several people on bugzilla have reported that using nomodeset makes their computer bootable again. So for now it is working.
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 445
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts


Return to Testing : Alpha, Beta, RC and Cauldron

Who is online

Users browsing this forum: No registered users and 1 guest

cron