Bug 25132 - Update request: kernel-linus-5.1.18-1.mga7
Summary: Update request: kernel-linus-5.1.18-1.mga7
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard:
Keywords: feedback
Depends on:
Blocks:
 
Reported: 2019-07-15 17:43 CEST by Thomas Backlund
Modified: 2019-11-07 21:32 CET (History)
2 users (show)

See Also:
Source RPM: kernel-linus
CVE:
Status comment:


Attachments
Xorg log file from previous session (5.87 KB, text/plain)
2019-07-19 13:24 CEST, Len Lawrence
Details

Description Thomas Backlund 2019-07-15 17:43:16 CEST
Bugfixes all over, including fixes for new Intel 802.11ax hw

Advisory will follow...

SRPMS:
kernel-linus-5.1.18-1.mga7.src.rpm

i586:
kernel-linus-5.1.18-1.mga7-1-1.mga7.i586.rpm
kernel-linus-devel-5.1.18-1.mga7-1-1.mga7.i586.rpm
kernel-linus-devel-latest-5.1.18-1.mga7.i586.rpm
kernel-linus-doc-5.1.18-1.mga7.noarch.rpm
kernel-linus-latest-5.1.18-1.mga7.i586.rpm
kernel-linus-source-5.1.18-1.mga7-1-1.mga7.noarch.rpm
kernel-linus-source-latest-5.1.18-1.mga7.noarch.rpm

x86_64:
kernel-linus-5.1.18-1.mga7-1-1.mga7.x86_64.rpm
kernel-linus-devel-5.1.18-1.mga7-1-1.mga7.x86_64.rpm
kernel-linus-devel-latest-5.1.18-1.mga7.x86_64.rpm
kernel-linus-doc-5.1.18-1.mga7.noarch.rpm
kernel-linus-latest-5.1.18-1.mga7.x86_64.rpm
kernel-linus-source-5.1.18-1.mga7-1-1.mga7.noarch.rpm
kernel-linus-source-latest-5.1.18-1.mga7.noarch.rpm
Comment 1 Len Lawrence 2019-07-19 13:24:40 CEST
Created attachment 11201 [details]
Xorg log file from previous session

/var/log/Xorg.0.log.old

CC: (none) => tarazed25

Comment 2 Len Lawrence 2019-07-19 13:26:19 CEST
mga7, x86_64
CPU:      10-Core: Intel Core i9-7900X type: MT MCP
Desktop Mobo: ASUSTeK model: TUF X299 MARK 2 v: Rev 1.xx
NVIDIA GP102 [GeForce GTX 1080 Ti] driver: nvidia v: 430.26

Installed the linus kernel and rebooted.
The boot failed to reach the desktop because there was a mismatch between the nvidia kernel module and the driver X was configured to use.  There was no sign of any attempt to rebuild the nvidia kmod and running drakx11 to install it resulted in a failure, something like "Your screen is too small. .....  Restart the application."  Switched to modesetting driver and attempted to set up the graphical display server from the desktop.  That failed again on reboot.  Went through the loop several times but eventually had to give up because I could not understand what was going on.

# dkms status
nvidia-current, 430.26-1.mga7.nonfree, 5.1.18-desktop-1.mga7, x86_64: installed 
nvidia-current, 430.26-1.mga7.nonfree, 5.1.14-desktop-1.mga7, x86_64: installed 
nvidia-current, 430.26-1.mga7.nonfree, 5.1.18-1.mga7, x86_64: installed 
xtables-addons, 3.3-1.mga7, 5.1.18-desktop-1.mga7, x86_64: installed-binary from 5.1.18-desktop-1.mga7
virtualbox, 6.0.8-1.mga7, 5.1.18-desktop-1.mga7, x86_64: installed-binary from 5.1.18-desktop-1.mga7

I had tried removing dkms-nvidia-current and reinstalling - a simple trick which worked in the past, but not now.
$ rpm -qa | grep nvidia
nvidia-current-utils-430.26-1.mga7.nonfree
x11-driver-video-nvidia-current-430.26-1.mga7.nonfree
dkms-nvidia-current-430.26-1.mga7.nonfree

Extract from /etc/X11/xorg.conf.old
Section "Device"
    Identifier "device1"
    VendorName "NVIDIA Corporation"
    BoardName "NVIDIA GeForce 635 series and later"
    Driver "nvidia"
    Option "DPMS"
    Option "AddARGBGLXVisuals"
    Option "DynamicTwinView" "false"
EndSection

A whole mornings's work. :-/
Comment 3 Len Lawrence 2019-07-19 21:06:56 CEST
Noted this while running drakx11 under the modesetting driver:

failed to link /etc/OpenCL/vendors/nvidia.icd -> /etc/alternatives/nvidia.icd: No such file or directory

No idea if that is significant.  Continued experiments but failed every time to enable the nvidia driver for kernel linus.
Comment 4 Len Lawrence 2019-07-19 22:00:29 CEST
One last ditch attempt on another nvidia machine also failed.  On the first reboot after installing the linus kernel the nvidia driver was built on the fly and installed and then there appeared the message about a conflict between graphics drivers.  There is not much point in my pursuing this any further - none of it makes sense.
Comment 5 James Kerr 2019-07-20 10:27:16 CEST
I experienced the same error when I switched from kernel-desktop to kernel-linus-5.1.14-1.

but the module appears to have been built and installed:

On booting back into kernel-desktop, I have:
# dkms status
nvidia-current, 430.26-1.mga7.nonfree, 5.1.14-1.mga7, x86_64: installed 
nvidia-current, 430.26-1.mga7.nonfree, 5.1.14-desktop-1.mga7, x86_64: installed 
nvidia-current, 430.26-1.mga7.nonfree, 5.1.18-desktop-1.mga7, x86_64: installed

I updated kernel-linus, by installing:
- kernel-linus-5.1.18-1.mga7-1-1.mga7.x86_64
- kernel-linus-devel-5.1.18-1.mga7-1-1.mga7.x86_64
- kernel-linus-devel-latest-5.1.18-1.mga7.x86_64
- kernel-linus-latest-5.1.18-1.mga7.x86_64

and experienced the same error about mismatched kernel module
but again the module appears to have been built and installed:

# dkms status
nvidia-current, 430.26-1.mga7.nonfree, 5.1.14-1.mga7, x86_64: installed 
nvidia-current, 430.26-1.mga7.nonfree, 5.1.14-desktop-1.mga7, x86_64: installed 
nvidia-current, 430.26-1.mga7.nonfree, 5.1.18-1.mga7, x86_64: installed 
nvidia-current, 430.26-1.mga7.nonfree, 5.1.18-desktop-1.mga7, x86_64: installed 

Is there some additional configuration required in order to use 
the nvidia kernel module on kernel-linus?

on kernel-desktop I have:
Desktop Mobo: ECS model: GeForce7050M-M 
CPU:Quad Core model: AMD Phenom 9500
Graphics:
  Device: NVIDIA GK208B [GeForce GT 710] driver: nvidia v: 430.26 
  OpenGL: renderer: GeForce GT 710/PCIe/SSE2 v: 4.6.0 NVIDIA 430.26

CC: (none) => jim

Comment 6 James Kerr 2019-07-20 10:59:01 CEST
on mga7-64  kernel-linus  plasma

on this system:
Mobo: Dell model: 09WH54 v: UEFI [Legacy]: Dell v: 2.13.1 
CPU: Intel Core i7-6700
Graphics: Intel HD Graphics 530 (Skylake GT2)

packages installed cleanly

system re-booted normally:

$ uname -r
5.1.18-1.mga7

# dkms status
virtualbox, 6.0.8-1.mga7, 5.1.18-1.mga7, x86_64: installed 
virtualbox, 6.0.8-1.mga7, 5.1.14-1.mga7, x86_64: installed 
virtualbox, 6.0.8-1.mga7, 5.1.14-desktop-1.mga7, x86_64: installed-binary from 5.1.14-desktop-1.mga7
virtualbox, 6.0.8-1.mga7, 5.1.18-desktop-1.mga7, x86_64: installed-binary from 5.1.18-desktop-1.mga7

which is OK for mga7-64 on this system

It seems that the problem described in the earlier comments relates solely to the nvidia module.
Comment 7 Thomas Backlund 2019-07-20 22:49:22 CEST
(In reply to James Kerr from comment #5)

> 
> Is there some additional configuration required in order to use 
> the nvidia kernel module on kernel-linus?

There should not be ...

I'll try to reproduce it here
Comment 8 Len Lawrence 2019-07-21 17:36:10 CEST
mga7, x86_64

Alienware X51
Intel Core i7-2600 type: MT MCP
NVIDIA GF114 [GeForce GTX 555] driver: nvidia v: 390.116 

The nvidia kmod appeared to be built once the kernel linus updates were complete.
Rebooting failed at the graphics driver stage again, as on other machines but this time there were no virtual consoles available and specifying other drivers with the xdriver kernel option had no effect.  No choice but to revert to the 5.1.14-desktop kernel.  During the boot process the log notes that the dkms autoinstaller is being run at every boot.

$ dkms status
nvidia390, 390.116-3.mga7.nonfree, 5.1.14-desktop-1.mga7, x86_64: installed 
nvidia390, 390.116-3.mga7.nonfree, 5.1.18-1.mga7, x86_64: installed
Comment 9 Len Lawrence 2019-07-21 17:58:34 CEST
Continuing from comment 8.
Tried to boot to runlevel 3, without success, so without a command line there is no way in.  The only other thing to note is that the mouse cursor appeared as a persistent rectangle.
Thomas Backlund 2019-07-27 21:50:53 CEST

Keywords: (none) => feedback

Comment 10 Len Lawrence 2019-09-28 23:53:40 CEST
Tried to find this to resume testing and can no longer find it in the repositories.  Has it been dropped?
Comment 11 Len Lawrence 2019-11-07 21:31:05 CET
Can some kind sysadmin get rid of this?  WONTFIX or something?
Comment 12 Thomas Backlund 2019-11-07 21:32:45 CET
Yeah, I will replace it with a newer update later on...

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.