[Closed] Nvidia 390.143 and kernel 5.13 in Mageia 8

[Closed] Nvidia 390.143 and kernel 5.13 in Mageia 8

Postby stan » Aug 7th, '21, 01:24

Unable to boot into Magia 8 with kernel 5.13.4 and Nvidia driver 390.143 (64-bit on i7). Reports Light Display Manager could not start.

Tries to start several times...
Code: Select all
Aug 06 23:45:55 localhost systemd[1]: Finished Shorewall IPv6 firewall.
Aug 06 23:45:55 localhost systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Aug 06 23:45:55 localhost systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug 06 23:45:55 localhost systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 1.
Aug 06 23:45:55 localhost systemd[1]: Stopped Light Display Manager.
Aug 06 23:45:55 localhost systemd[1]: Starting Light Display Manager...
Aug 06 23:45:55 localhost systemd[1]: Started Light Display Manager.
Aug 06 23:45:55 localhost acpid[1002]: client 1744[0:0] has disconnected
Aug 06 23:45:55 localhost acpid[1002]: client connected from 2067[0:0]
Aug 06 23:45:55 localhost acpid[1002]: 1 client rule loaded
Aug 06 23:45:55 localhost systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Aug 06 23:45:55 localhost systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug 06 23:45:56 localhost systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 2.
Aug 06 23:45:56 localhost systemd[1]: Stopped Light Display Manager.
Aug 06 23:45:56 localhost systemd[1]: Starting Light Display Manager...
Aug 06 23:45:56 localhost systemd[1]: Started Light Display Manager.
Aug 06 23:45:56 localhost acpid[1002]: client 2067[0:0] has disconnected
Aug 06 23:45:56 localhost acpid[1002]: client connected from 2083[0:0]
Aug 06 23:45:56 localhost acpid[1002]: 1 client rule loaded
Aug 06 23:45:56 localhost systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Aug 06 23:45:56 localhost systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug 06 23:45:56 localhost systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 3.
Aug 06 23:45:56 localhost systemd[1]: Stopped Light Display Manager.
Aug 06 23:45:56 localhost systemd[1]: Starting Light Display Manager...
Aug 06 23:45:56 localhost systemd[1]: Started Light Display Manager.
Aug 06 23:45:56 localhost acpid[1002]: client 2083[0:0] has disconnected
Aug 06 23:45:56 localhost acpid[1002]: client connected from 2092[0:0]
Aug 06 23:45:56 localhost acpid[1002]: 1 client rule loaded
Aug 06 23:45:56 localhost systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Aug 06 23:45:56 localhost systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug 06 23:45:56 localhost systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 4.
Aug 06 23:45:56 localhost systemd[1]: Stopped Light Display Manager.
Aug 06 23:45:56 localhost systemd[1]: Starting Light Display Manager...
Aug 06 23:45:56 localhost systemd[1]: Started Light Display Manager.
Aug 06 23:45:56 localhost acpid[1002]: client 2092[0:0] has disconnected
Aug 06 23:45:56 localhost acpid[1002]: client connected from 2101[0:0]
Aug 06 23:45:56 localhost acpid[1002]: 1 client rule loaded
Aug 06 23:45:56 localhost systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Aug 06 23:45:56 localhost systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug 06 23:45:56 localhost systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
Aug 06 23:45:56 localhost systemd[1]: Stopped Light Display Manager.
Aug 06 23:45:56 localhost systemd[1]: lightdm.service: Start request repeated too quickly.
Aug 06 23:45:56 localhost systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug 06 23:45:56 localhost systemd[1]: Failed to start Light Display Manager.


Nouveau X driver not working reliably either. Internet search reports issues with Nvidia 390 and kernel 5.13.

Switched to kernel 5.10.52 and everything is fine.
Last edited by stan on Nov 26th, '21, 01:37, edited 2 times in total.
stan
 
Posts: 4
Joined: Sep 3rd, '11, 19:31

Re: Nvidia 390.143 and kernel 5.13 in Mageia 8

Postby doktor5000 » Aug 7th, '21, 21:41

Can you please post the output as root of
Code: Select all
rpm -qa|grep -iE "kernel|nvidia"|sort
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: 17630
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Nvidia 390.143 and kernel 5.13 in Mageia 8

Postby stan » Nov 26th, '21, 01:35

I can report that this problem is not present in kernel 5.15.4 (and Mageia 8, Nvidia 390.144).

I stuck with kernel 5.10 up to 5.10.78 but latest kernel update to 5.15.4 is working fine with Nvidia graphics and this can be closed.
Thank you.
stan
 
Posts: 4
Joined: Sep 3rd, '11, 19:31

Re: [Closed] Nvidia 390.143 and kernel 5.13 in Mageia 8

Postby morgano » Nov 26th, '21, 10:40

That is great!
Thank you for the confirmation.
Mandriva since 2006, Mageia 2011 at home & work. Thinkpad T40, T43, T400, T510, Dell M4400, M6300, Acer Aspire 7. Workstation using LVM, LUKS, VirtualBox, BOINC
morgano
 
Posts: 1306
Joined: Jun 15th, '11, 17:51
Location: Kivik, Sweden


Return to Video

Who is online

Users browsing this forum: No registered users and 1 guest

cron