[SOLVED]Kernel 5.1.0 will not boot

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 5.1.0 will not boot

Postby banjo » Apr 23rd, '19, 01:04

I just updated the kernel to 5.1.0-desktop-0.rc6.1.mga7 on my Mageia 7 Beta machine, and the computer now boots to a black screen. It goes through the boot sequence showing the splash screen until about the time that it usually switches to the Nvidia drivers, then it stops at the black screen. So I am guessing that it is the Nvidia drivers that are broken or are incompatible with the new kernel.

The computer will boot if I go back to 5.0.9-desktop-1.mga7

A couple of updates ago I saw an update to the Nvidia drivers saying that a bug was fixed to work with kernel 5.1... I think. I'm not sure how to back that information out. Anyway, apparently it does not work.

What does "rc6" mean in the kernel package name?

Here is the inxi info

Code: Select all
$ inxi -b
System:    Host: Mageia7 Kernel: 5.0.9-desktop-1.mga7 x86_64 bits: 64 Desktop: KDE Plasma 5.15.4
           Distro: Mageia 7 mga7
Machine:   Type: Desktop Mobo: ASUSTeK model: P5G41T-M LX PLUS v: Rev X.0x serial: <root required>
           BIOS: American Megatrends v: 0502 date: 10/21/2011
CPU:       Dual Core: Intel Core2 Duo E7300 type: MCP speed: 1893 MHz
Graphics:  Device-1: NVIDIA G94 [GeForce 9600 GT] driver: nvidia v: 340.107
           Display: x11 server: Mageia X.org 1.20.4 driver: nvidia,v4l resolution: 1680x1050~60Hz
           OpenGL: renderer: GeForce 9600 GT/PCIe/SSE2 v: 3.3.0 NVIDIA 340.107
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
           Device-2: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter driver: 8139too
           Device-3: Qualcomm Atheros AR9271 802.11n type: USB driver: ath9k_htc
Drives:    Local Storage: total: 465.76 GiB used: 26.31 GiB (5.6%)
Info:      Processes: 191 Uptime: 2m Memory: 3.85 GiB used: 1.69 GiB (43.8%) Shell: bash inxi: 3.0.33


Thanks,
Banjo
(_)=='=~
Last edited by banjo on May 11th, '19, 14:40, 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 5.1.0 will not boot

Postby benmc » Apr 23rd, '19, 03:05

banjo wrote:What does "rc6" mean in the kernel package name?


rc is deemed release candidate.
(Un)fortunately this likely refers to the kernel, so unlikely the kernel that will be used in the Mageia7 final release.

as with the nature of Cauldron, I would suspect that an updated Nvidia module has yet to reach your nearest and dearest mirror.
I did an M7-B3 install yesterday, and afterwards, updated upwards of 800 packages, so it looks like the devs are hard at work.
benmc
 
Posts: 1175
Joined: Sep 2nd, '11, 12:45
Location: Pirongia, New Zealand

Re: Kernel 5.1.0 will not boot

Postby banjo » Apr 23rd, '19, 03:53

Thanks for the info. I thought that it might be "Release Candidate", but Mageia is still in Beta 3 (as far as I know) so that is confusing.

The Nvidia driver was updated earlier this morning.

Code: Select all
$ rpm -q dkms-nvidia340-340.107-6.mga7.nonfree --last
dkms-nvidia340-340.107-6.mga7.nonfree.x86_64  Mon 22 Apr 2019 07:57:59 AM EDT


I thought that the change log said that it was to fix a compatibility bug with 5.1. I do not know how to uncover the change logs, so I cannot confirm.

After the kernel was updated this afternoon, it stopped working.

Code: Select all
$ rpm -q kernel-desktop-5.1.0-0.rc6.1.mga7-1-1.mga7 --last
kernel-desktop-5.1.0-0.rc6.1.mga7-1-1.mga7.x86_64 Mon 22 Apr 2019 04:47:35 PM EDT


I have not seen a huge 800 package update yet, so maybe the fix is still in the pipeline. I will give it some time and see what happens.

Thanks for the help. I am new to running Cauldron and it is a bit.... um... dynamic compared to what I am used to. :o
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 5.1.0 will not boot

Postby doktor5000 » Apr 23rd, '19, 10:49

banjo wrote:I thought that it might be "Release Candidate", but Mageia is still in Beta 3 (as far as I know) so that is confusing.

There's no relation between the version of some software components and the version of Mageia.
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 5.1.0 will not boot

Postby banjo » Apr 23rd, '19, 13:31

Thanks for the info. I am still learning the ropes.

I installed yum-plugin-changelog so I can now view the changes. Here are the relevant logs from the two package updates yesterday.

Code: Select all
$ rpm -q --changelog dkms-nvidia340-340.107-6.mga7.nonfree | less

* Mon Apr 22 2019 tmb <tmb> 340.107-6.mga7
+ Revision: 1394660
- fix build with 5.1 series kernels

* Wed Mar 06 2019 tmb <tmb> 340.107-5.mga7.nonfree
+ Revision: 1372025
- fix build with 5.0 series kernels (arch)

     etc


$ rpm -q --changelog kernel-desktop-5.1.0-0.rc6.1.mga7-1-1.mga7 | less

* Mon Apr 22 2019 tmb <tmb> 5.1.0-0.rc6.1.mga7
+ Revision: 1394608
- update defconfigs
- add 5.1 buildfixes for rtl8723de, rtl8812au
- fix 3rdparty, vboxsf, shuttle-wmi, tools patches to apply cleanly
- rebase aufs patches
- update filelists
- drop merged/obsolete patches
- update to 5.1-rc6
- drop obsolete kgit patch support

* Sat Apr 20 2019 tmb <tmb> 5.0.9-1.mga7
+ Revision: 1393804
- add current -stable -net queue
- update to 5.0.9 final

     etc


It looks like there were supposed to be fixes in the Nvidia driver update for the 5.1 kernel.

I will try booting 5.1 again and see if anything useful shows up in the logs.
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 5.1.0 will not boot

Postby banjo » Apr 23rd, '19, 14:09

I rebooted kernel 5.1.0 without the splash screen, and the boot hung with the messages:

Code: Select all
[ OK ] Started Permit User Sessions.
[ OK ] Started Permit User Sessions.
[ OK ] Started Command Scheduler
[ OK ] Started Command Scheduler
       Starting Terminate Plymouth Boot Screen...
       Starting Hold until boot process finishes up...
       Starting Terminate Plymouth Boot Screen...
       Starting Hold until boot process finishes up...


After the last message, it just hangs. The messages are duplicated on the screen like that.... two identical messages in a row.

The boot into 5.1.0 was done at around 7:40 a.m. and there appears to be no journal entry for that boot.

Code: Select all
$ journalctl --list-boots
   -----     lots of stuff ------
  -4 e53849315b784b2a9698800bbadc9d80 Mon 2019-04-22 08:11:33 EDT—Mon 2019-04-22 17:40:49 EDT
  -3 69d117b3667a45c38b943bdf866b78cc Mon 2019-04-22 18:23:21 EDT—Mon 2019-04-22 18:31:44 EDT
  -2 5a69ae61b00c4b3bbbae7c01e37f2321 Mon 2019-04-22 18:37:36 EDT—Mon 2019-04-22 22:13:06 EDT
  -1 25dcf9d40790447ba77d98e39d02eb14 Tue 2019-04-23 06:54:37 EDT—Tue 2019-04-23 07:41:03 EDT
   0 94995aef09b6466896f7f24ee88d6622 Tue 2019-04-23 07:47:23 EDT—Tue 2019-04-23 07:52:46 EDT


The boot at 7:47 is a normal boot into kernel 5.0.9, as was the boot at 6:54.
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 5.1.0 will not boot

Postby doktor5000 » Apr 23rd, '19, 15:49

banjo wrote:I installed yum-plugin-changelog so I can now view the changes.
Code: Select all
$ rpm -q --changelog dkms-nvidia340-340.107-6.mga7.nonfree | less


FWIW, you don't need to install anything to view rpm changelogs, and you didn't even use that yum plugin ;)
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 5.1.0 will not boot

Postby banjo » Apr 23rd, '19, 15:53

Hmm. I tried it before, and it gave me an error saying that changelog was not installed. Then it worked after I installed the yum package.

Is root required for that feature? Maybe I wasn't logged in as root the first time.
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 5.1.0 will not boot

Postby doktor5000 » Apr 23rd, '19, 19:23

banjo wrote:Is root required for that feature? Maybe I wasn't logged in as root the first time.

No, the rpm database can also be queried as regular user, root is only required if you want to verify all files in a package.
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 5.1.0 will not boot

Postby adhefe » Apr 24th, '19, 03:48

I'm using kernel 5.1.0.

This is a hybrid graphics computer with intel (integrated) and nvidia (dedicated) video cards.

This boots fine with intel's video card and nvidia's support is also working fine with mageia prime.
adhefe
 
Posts: 188
Joined: Mar 11th, '19, 02:08

Re: Kernel 5.1.0 will not boot

Postby banjo » Apr 24th, '19, 13:47

I assume that if the latest update is now unbootable in general there would be a lot of chatter about it, and I am not seeing that. So it might be something local to my computer. But it does work with 5.0.9. Just not with 5.1.0.

I am going to keep updating to see if the problem fixes itself. Other than that, I'm not sure what to do.

Thanks for the info.
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 5.1.0 will not boot

Postby banjo » Apr 25th, '19, 16:03

I just installed an updated kernel, kernel-desktop-latest-5.1.0-0.rc6.2.mga7, which came through with the following change log

Code: Select all
* Wed Apr 24 2019 tmb <tmb> 5.1.0-0.rc6.2.mga7
+ Revision: 1395106
- add post -rc6 fixes from git
- update microcode conflict
- update dkms conflicts
- update firmware conflicts

* Mon Apr 22 2019 tmb <tmb> 5.1.0-0.rc6.1.mga7
+ Revision: 1394608
- update defconfigs
- add 5.1 buildfixes for rtl8723de, rtl8812au
- fix 3rdparty, vboxsf, shuttle-wmi, tools patches to apply cleanly
- rebase aufs patches
- update filelists
- drop merged/obsolete patches
- update to 5.1-rc6
- drop obsolete kgit patch support

* Sat Apr 20 2019 tmb <tmb> 5.0.9-1.mga7
+ Revision: 1393804
- add current -stable -net queue
- update to 5.0.9 final



Since it appears that I am having dkms problems, and the changelog says that dkms issues have been addressed, I thought that the boot problem might be fixed. So I tried to boot the new kernel. The result was that it failed again. To see if I could gather more information, I logged in and ran "startx".

X11 failed to load the nvidia340 module. I have captured, the best I can from a photograph of the screen, the errors below.

Code: Select all
Current version of pixman: 0.38.4
    Before reporting problens. check https://bugs.mageia.org
    to make sure that you have the latest version.
Markers: (--) probed. (**) from conflg file, (==) default setting,
    (++) from command line. (!!) notice. (II) informational,
    (WW) warning, (EE) error. (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Apr 25 07:59:49 2019
(==) Using conflg file: "/etc/X11/xorg.conf"
(==) Uslng conflg directory: "/etc/X11/xorg.con£.d"
(==) Uslng system config directory "/usr/share/X11/xorg.conf.d"
modprobe: ERROR could not insert 'nvidia340': Operation not pernitted
modprobe: ERROR: install command for nvidia

(EE)
(EE) Server terminated with error (1). Closing log file Xorg.0.log
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error


I found the Xorg.0.log from the boot time of 07:59:49. The contents are below:

Code: Select all
[   125.998]
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[   125.998] Build Operating System: ecosse 4.14.110-server-1.mga6
[   125.999] Current Operating System: Linux Mageia7 5.1.0-desktop-0.rc6.2.mga7 #1 SMP Wed Apr 24 08:08:41 UTC 2019 x86_64
[   125.999] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.1.0-desktop-0.rc6.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
[   125.999] Build Date: 22 April 2019  09:44:56PM
[   125.999] Build ID: x11-server 1.20.4-7.mga7
[   125.999] Current version of pixman: 0.38.4
[   126.000]    Before reporting problems, check https://bugs.mageia.org
   to make sure that you have the latest version.
[   126.000] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   126.000] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Apr 25 07:59:49 2019
[   126.001] (==) Using config file: "/etc/X11/xorg.conf"
[   126.001] (==) Using config directory: "/etc/X11/xorg.conf.d"
[   126.001] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   126.001] (==) ServerLayout "layout1"
[   126.001] (**) |-->Screen "screen1" (0)
[   126.001] (**) |   |-->Monitor "monitor1"
[   126.002] (**) |   |-->Device "device1"
[   126.002] (**) Option "DontZap" "False"
[   126.002] (**) Option "AllowMouseOpenFail"
[   126.002] (==) Automatically adding devices
[   126.002] (==) Automatically enabling devices
[   126.002] (==) Automatically adding GPU devices
[   126.002] (==) Automatically binding GPU devices
[   126.002] (==) Max clients allowed: 256, resource mask: 0x1fffff
[   126.002] (==) FontPath set to:
   catalogue:/etc/X11/fontpath.d,
   built-ins
[   126.002] (**) ModulePath set to "/usr/lib64/xorg/extra-modules,/usr/lib64/xorg/modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules"
[   126.002] (II) The server relies on udev to provide the list of input devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
[   126.002] (II) Loader magic: 0x616d40
[   126.002] (II) Module ABI versions:
[   126.002]    X.Org ANSI C Emulation: 0.4
[   126.002]    X.Org Video Driver: 24.0
[   126.002]    X.Org XInput driver : 24.1
[   126.002]    X.Org Server Extension : 10.0
[   126.003] (++) using VT number 5

[   126.004] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[   126.007] (--) PCI:*(1@0:0:0) 10de:0622:196e:0545 rev 161, Mem @ 0xfd000000/16777216, 0xe0000000/268435456, 0xfa000000/33554432, I/O @ 0x0000cc00/128, BIOS @ 0x????????/131072
[   126.007] (II) Open ACPI successful (/var/run/acpid.socket)
[   126.007] (II) "glx" will be loaded by default.
[   126.007] (II) LoadModule: "v4l"
[   126.008] (II) Loading /usr/lib64/xorg/modules/drivers/v4l_drv.so
[   126.008] (II) Module v4l: vendor="X.Org Foundation"
[   126.008]    compiled for 1.20.1, module version = 0.1.1
[   126.008]    ABI class: X.Org Video Driver, version 24.0
[   126.008] (II) LoadModule: "glx"
[   126.008] (II) Loading /usr/lib64/xorg/extra-modules/libglx.so
[   126.024] (II) Module glx: vendor="NVIDIA Corporation"
[   126.024]    compiled for 4.0.2, module version = 1.0.0
[   126.024]    Module class: X.Org Server Extension
[   126.024] (II) NVIDIA GLX Module  340.107  Thu May 24 21:40:32 PDT 2018
[   126.024] (II) LoadModule: "nvidia"
[   126.025] (II) Loading /usr/lib64/xorg/extra-modules/nvidia_drv.so
[   126.025] (II) Module nvidia: vendor="NVIDIA Corporation"
[   126.025]    compiled for 4.0.2, module version = 1.0.0
[   126.025]    Module class: X.Org Video Driver
[   126.025] (II) v4l driver for Video4Linux overlay mode (V4L2)
[   126.025] (II) NVIDIA dlloader X Driver  340.107  Thu May 24 21:18:05 PDT 2018
[   126.025] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[   126.025] (WW) Falling back to old probe method for v4l
[   126.025] (II) Loading sub module "fb"
[   126.025] (II) LoadModule: "fb"
[   126.025] (II) Loading /usr/lib64/xorg/modules/libfb.so
[   126.026] (II) Module fb: vendor="X.Org Foundation"
[   126.026]    compiled for 1.20.4, module version = 1.0.0
[   126.026]    ABI class: X.Org ANSI C Emulation, version 0.4
[   126.026] (WW) Unresolved symbol: fbGetGCPrivateKey
[   126.026] (II) Loading sub module "wfb"
[   126.026] (II) LoadModule: "wfb"
[   126.026] (II) Loading /usr/lib64/xorg/modules/libwfb.so
[   126.026] (II) Module wfb: vendor="X.Org Foundation"
[   126.026]    compiled for 1.20.4, module version = 1.0.0
[   126.026]    ABI class: X.Org ANSI C Emulation, version 0.4
[   126.026] (II) Loading sub module "ramdac"
[   126.026] (II) LoadModule: "ramdac"
[   126.026] (II) Module "ramdac" already built-in
[   126.375] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[   126.375] (EE) NVIDIA:     system's kernel log for additional error messages and
[   126.375] (EE) NVIDIA:     consult the NVIDIA README for details.
[   126.375] (WW) Falling back to old probe method for v4l
[   126.375] (EE) No devices detected.
[   126.375] (EE)
Fatal server error:
[   126.375] (EE) no screens found(EE)
[   126.375] (EE)
Please consult the Mageia support
    at https://bugs.mageia.org
 for help.
[   126.375] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[   126.375] (EE)
[   126.383] (EE) Server terminated with error (1). Closing log file.


I do not know enough about the software to understand the details of this, but it appears that the new kernel is not able to load the Nvidia module for some reason.

What does "(WW) Falling back to old probe method for v4l" mean?

The old kernel, kernel-desktop-devel-5.0.9-1.mga7-1-1.mga7, loads the same Nvidia module OK.

Where is the "system's kernel log"? I still cannot find a journalctl log for that failed boot.

Thanks for looking,
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 5.1.0 will not boot

Postby doktor5000 » Apr 25th, '19, 16:55

banjo wrote:What does "(WW) Falling back to old probe method for v4l" mean?

You can ignore that, it's displayed for every X start. It's about video for linux or in short, v4l.

banjo wrote:Where is the "system's kernel log"? I still cannot find a journalctl log for that failed boot.

You can display the kernel log with journalctl -k and older logs with journalctl -k -b-1 (for previous boot) or in general -b-N for the Nth previous boot.

It would help if you could add the output as root of
Code: Select all
dkms status

and
Code: Select all
rpm -qa|grep -iE "nvidia|dkms"|sort
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 5.1.0 will not boot

Postby banjo » Apr 25th, '19, 19:35

Dkms status

Code: Select all
# dkms status
nvidia340, 340.107-6.mga7.nonfree, 5.1.0-desktop-0.rc6.2.mga7, x86_64: installed
nvidia340, 340.107-6.mga7.nonfree, 5.0.9-desktop-1.mga7, x86_64: installed
nvidia340, 340.107-6.mga7.nonfree, 5.1.0-desktop-0.rc6.1.mga7, x86_64: installed


Package info

Code: Select all
# rpm -qa | grep -iE "nvidia|dkms"|sort
dkms-2.0.19-39.mga6
dkms-minimal-2.0.19-39.mga6
dkms-nvidia340-340.107-6.mga7.nonfree
nvidia340-doc-html-340.107-6.mga7.nonfree
x11-driver-video-nvidia340-340.107-6.mga7.nonfree
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 5.1.0 will not boot

Postby benmc » Apr 25th, '19, 22:33

Bug 24719 - updating to nvidia340/340.107-6.mga7 results in no desktop presented

https://bugs.mageia.org/show_bug.cgi?id=24719
Last edited by isadora on Apr 26th, '19, 08:16, edited 1 time in total.
Reason: Link added
benmc
 
Posts: 1175
Joined: Sep 2nd, '11, 12:45
Location: Pirongia, New Zealand

Re: Kernel 5.1.0 will not boot

Postby banjo » Apr 25th, '19, 22:41

Thanks for posting that. I wasn't sure if this is an actual bug or something specific to my system.
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 5.1.0 will not boot

Postby benmc » Apr 26th, '19, 00:05

banjo wrote:Thanks for posting that. I wasn't sure if this is an actual bug or something specific to my system.


I have one nvidia laptop that I sometimes use for testing .isos.
your post gave me a reason to check the issue.
so, after install of Mga7b3(32), ran the 800+ updates - reboot to no desktop :(
redid the install for 64bit deselected the appropriate rpm packages, updated another 800+ packages, reboot to working desktop.
reran the updater to capture the previously de-selected updates, captured the output of the update, and rebooted to no desktop.,

so thanks for the heads up.
benmc
 
Posts: 1175
Joined: Sep 2nd, '11, 12:45
Location: Pirongia, New Zealand

Re: Kernel 5.1.0 will not boot

Postby banjo » Apr 29th, '19, 02:21

I just installed the latest update to dkms-nvidia340-340.107-8.mga7.nonfree with high hopes that the problem would be solved. The system rebuilt the driver, but it still will not boot the nvidia graphics using the 5.1.0 kernel.

The changelog from the update:

Code: Select all
* Sun Apr 28 2019 tmb <tmb> 340.107-8.mga7
+ Revision: 1395814
- fix up dkms.conf for uvm removal

* Sun Apr 28 2019 tmb <tmb> 340.107-7.mga7.nonfree
+ Revision: 1395810
- stop installing the uvm module, its not supported with newer kernels

* Mon Apr 22 2019 tmb <tmb> 340.107-6.mga7.nonfree
+ Revision: 1394660
- fix build with 5.1 series kernels

* Wed Mar 06 2019 tmb <tmb> 340.107-5.mga7.nonfree
+ Revision: 1372025
- fix build with 5.0 series kernels (arch)
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 5.1.0 will not boot

Postby benmc » Apr 29th, '19, 05:31

best to post onto the bug report your findings.
benmc
 
Posts: 1175
Joined: Sep 2nd, '11, 12:45
Location: Pirongia, New Zealand

Re: Kernel 5.1.0 will not boot

Postby banjo » Apr 29th, '19, 13:46

OK. Did that.
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 5.1.0 will not boot

Postby banjo » May 11th, '19, 14:40

An update to the nvidia driver, nvidia340-340.107-9.mga7, appears to have fixed this issue on my system.

Info posted on bugzilla at https://bugs.mageia.org/show_bug.cgi?id=24719.

Here is my latest inxi info.

Code: Select all
$ inxi -b
System:    Host: localhost Kernel: 5.1.0-desktop-2.mga7 x86_64 bits: 64 Desktop: KDE Plasma 5.15.4
           Distro: Mageia 7 mga7
Machine:   Type: Desktop Mobo: ASUSTeK model: P5G41T-M LX PLUS v: Rev X.0x serial: <root required>
           BIOS: American Megatrends v: 0502 date: 10/21/2011
CPU:       Dual Core: Intel Core2 Duo E7300 type: MCP speed: 1622 MHz
Graphics:  Device-1: NVIDIA G94 [GeForce 9600 GT] driver: nvidia v: 340.107
           Display: x11 server: Mageia X.org 1.20.4 driver: nvidia,v4l resolution: 1680x1050~60Hz
           OpenGL: renderer: GeForce 9600 GT/PCIe/SSE2 v: 3.3.0 NVIDIA 340.107
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
           Device-2: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter driver: 8139too
           Device-3: Qualcomm Atheros AR9271 802.11n type: USB driver: ath9k_htc
Drives:    Local Storage: total: 465.76 GiB used: 27.54 GiB (5.9%)
Info:      Processes: 184 Uptime: 2m Memory: 3.85 GiB used: 1.59 GiB (41.2%) Shell: bash inxi: 3.0.33
$ rpm -qa | grep nvidia
x11-driver-video-nvidia340-340.107-9.mga7.nonfree
dkms-nvidia340-340.107-9.mga7.nonfree
nvidia340-doc-html-340.107-9.mga7.nonfree


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 5.1.0 will not boot

Postby banjo » May 11th, '19, 14:51

BTW, I figured out how I got confused about needing a plugin to view the changelog. When I typed in the command, I inadvertently put a space between the the -- and the switch 'changelog', so rpm thought that I was asking about a package named 'changelog'. Like this:

Code: Select all
$ rpm -q -- changelog dkms-nvidia340-340.107-9.mga7.nonfree
package changelog is not installed
dkms-nvidia340-340.107-9.mga7.nonfree


Hence, I assumed that I had to install a package to view the log. :oops: And so I went down that rabbit hole.

Back on track.

Thanks to all the hard working devs, testers, packagers and others who make this distro happen.

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


Return to Testing : Alpha, Beta, RC and Cauldron

Who is online

Users browsing this forum: No registered users and 1 guest

cron