Bug 22628 - Update request: libdrm 2.4.90
Summary: Update request: libdrm 2.4.90
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: mga6-32-ok MGA6-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2018-02-18 19:13 CET by Thomas Backlund
Modified: 2018-03-06 08:56 CET (History)
7 users (show)

See Also:
Source RPM: libdrm
CVE:
Status comment:


Attachments

Description Thomas Backlund 2018-02-18 19:13:08 CET
Advisory:
This libdrm update to 2.4.90 adds more Intel Coffee Lake PCI IDs, various
fixes for amdgpu, and some core libdrm fixes.

Reference:
https://lists.x.org/archives/xorg-announce/2018-February/002838.html



SRPMS:
libdrm-2.4.90-1.mga6.src.rpm



i586:
drm-utils-2.4.90-1.mga6.i586.rpm
libdrm2-2.4.90-1.mga6.i586.rpm
libdrm_amdgpu1-2.4.90-1.mga6.i586.rpm
libdrm-common-2.4.90-1.mga6.i586.rpm
libdrm-devel-2.4.90-1.mga6.i586.rpm
libdrm_intel1-2.4.90-1.mga6.i586.rpm
libdrm_nouveau2-2.4.90-1.mga6.i586.rpm
libdrm_radeon1-2.4.90-1.mga6.i586.rpm
libkms1-2.4.90-1.mga6.i586.rpm



x86_64:
drm-utils-2.4.90-1.mga6.x86_64.rpm
lib64drm2-2.4.90-1.mga6.x86_64.rpm
lib64drm_amdgpu1-2.4.90-1.mga6.x86_64.rpm
lib64drm-devel-2.4.90-1.mga6.x86_64.rpm
lib64drm_intel1-2.4.90-1.mga6.x86_64.rpm
lib64drm_nouveau2-2.4.90-1.mga6.x86_64.rpm
lib64drm_radeon1-2.4.90-1.mga6.x86_64.rpm
lib64kms1-2.4.90-1.mga6.x86_64.rpm
libdrm-common-2.4.90-1.mga6.x86_64.rpm
Comment 1 Thomas Backlund 2018-02-18 19:19:25 CET
As this is somewhat lowlevel, it needs testing on both arches
Comment 2 Len Lawrence 2018-02-20 12:35:26 CET
Installed the updates:
# urpmi lib64kms1
Package lib64kms1-2.4.90-1.mga6.x86_64 is already installed
[root@vega lcl]# rpm -qa | grep drm | sort
drm-utils-2.4.90-1.mga6
lib64drm2-2.4.90-1.mga6
lib64drm_amdgpu1-2.4.90-1.mga6
lib64drm-devel-2.4.90-1.mga6
lib64drm_intel1-2.4.90-1.mga6
lib64drm_nouveau2-2.4.90-1.mga6
lib64drm_radeon1-2.4.90-1.mga6
libdrm-common-2.4.90-1.mga6

As with the mesa packages best to let this run and hope nothing breaks.

CC: (none) => tarazed25

Comment 3 James Kerr 2018-02-23 15:43:40 CET
on mga6-64 plasma 4.14.20-desktop

packages installed cleanly:
- drm-utils-2.4.90-1.mga6.x86_64
- lib64drm-devel-2.4.90-1.mga6.x86_64
- lib64drm2-2.4.90-1.mga6.x86_64
- lib64drm_amdgpu1-2.4.90-1.mga6.x86_64
- lib64drm_intel1-2.4.90-1.mga6.x86_64
- lib64drm_nouveau2-2.4.90-1.mga6.x86_64
- lib64drm_radeon1-2.4.90-1.mga6.x86_64
- lib64kms1-2.4.90-1.mga6.x86_64
- libdrm-common-2.4.90-1.mga6.x86_64

after two days, no rgressions seen

looks OK for mga6-64 on this system:

Machine:   Device: desktop System: Dell product: Precision Tower 3620
           Mobo: Dell model: 09WH54 v: A00 UEFI [Legacy]
CPU:       Quad core Intel Core i7-6700 (-HT-MCP-)
Graphics:  Card: Intel HD Graphics 530
           Display Server: Mageia X.org 119.5 drivers: v4l,intel

CC: (none) => jim

Comment 4 James Kerr 2018-02-23 17:01:44 CET
on mga6-32 xfce 4.14.20-server

packages installed cleanly:
- drm-utils-2.4.90-1.mga6.i586
- libcunit1-2.1.3-1.mga6.i586
- libdrm-common-2.4.90-1.mga6.i586
- libdrm2-2.4.90-1.mga6.i586
- libdrm_amdgpu1-2.4.90-1.mga6.i586
- libdrm_intel1-2.4.90-1.mga6.i586
- libdrm_nouveau2-2.4.90-1.mga6.i586
- libdrm_radeon1-2.4.90-1.mga6.i586

after two days no regressions

looks OK for mga6-32 on this system:

Machine:   Device: desktop Mobo: ECS model: GeForce7050M-M 
CPU:       Quad core AMD Phenom 9500 (-MCP-)
Graphics:  Card: NVIDIA GK208B [GeForce GT 710]
           Display Server: Mageia X.org 119.5 drivers: nvidia,v4l 
           GLX Renderer: GeForce GT 710/PCIe/SSE2/3DNOW! 
	   GLX Version: 4.5.0 NVIDIA 384.111
Comment 5 claire robinson 2018-02-28 23:18:27 CET
Advisory uploaded

Keywords: (none) => advisory

Comment 6 Herman Viaene 2018-03-01 14:49:17 CET
MGA6-32 on Dell Latitude D600 Mate
Pentium M processor with RV250/M9 GL [Mobility FireGL 9000/Radeon 9000], driver ati.
No installation issues.
Does not break current desktop
Tried a few commands:
# drmdevice 
device[0]
	available_nodes 0005
	nodes
		nodes[0] /dev/dri/card0
		nodes[2] /dev/dri/renderD128
	bustype 0000
	businfo
		pci
			domain	0000
			bus	01
			dev	00
			func	0
	deviceinfo
		pci
			vendor_id	1002
			device_id	4c66
			subvendor_id	1028
			subdevice_id	011d
			revision_id	IGNORED
etc....  Looks OK.
# kmstest 
trying to open device 'i915'...failed
trying to open device 'amdgpu'...failed
trying to open device 'radeon'...failed
trying to open device 'nouveau'...failed
trying to open device 'vmwgfx'...failed
trying to open device 'omapdrm'...failed
trying to open device 'exynos'...failed
trying to open device 'tilcdc'...failed
trying to open device 'msm'...failed
trying to open device 'sti'...failed
trying to open device 'tegra'...failed
trying to open device 'imx-drm'...failed
trying to open device 'rockchip'...failed
trying to open device 'atmel-hlcdc'...failed
trying to open device 'fsl-dcu-drm'...failed
trying to open device 'vc4'...failed
trying to open device 'virtio_gpu'...failed
trying to open device 'mediatek'...failed
trying to open device 'meson'...failed
trying to open device 'pl111'...failed
no device found
main: Could not open device (No such device)
In view of the configuration at hand I wonder why it fails on the radeon device.
But that is a sideremark.

CC: (none) => herman.viaene

Comment 7 Herman Viaene 2018-03-01 16:03:49 CET
Just being curious, I tried to force X to use a non-propietary driver, so I selected Xorg - vesa for this setting.
But that resulted - if I did not intervene in an unending loop: boot then a message "A new driver has been selected, you need to reboot", reboot, same message etc... At the message I can "Cancel", go to the prompt, use drakx11 to reinstate the Radeon ati driver, and then start thru with "systemctl default". I suspect this has little to do with the updates.
Comment 8 José Jorge 2018-03-04 11:12:15 CET
Update tested in i586 (laptop Eee PC 901) all ok after reboot.

Whiteboard: (none) => mga6-32-ok
CC: (none) => lists.jjorge

Comment 9 Thomas Andrews 2018-03-04 18:12:35 CET
On an HP Probook 6550b, 64-bit Plasma install.

Both 32-bit and 64-bit packages installed, as 32-bit Google Earth requires the 32-bit packages.

Everything looks good. Google Earth happy, so is vlc and Firefox.

Looks good on this hardware.

CC: (none) => andrewsfarm

Comment 10 Lewis Smith 2018-03-05 12:26:50 CET
M6/64 real EFI hardware with Radeon HD 7310 graphics.

Selecting the following packages for update:
- lib64drm2-2.4.90-1.mga6.x86_64
- lib64drm_amdgpu1-2.4.90-1.mga6.x86_64
- lib64drm_intel1-2.4.90-1.mga6.x86_64
- lib64drm_nouveau2-2.4.90-1.mga6.x86_64
- lib64drm_radeon1-2.4.90-1.mga6.x86_64
- lib64kms1-2.4.90-1.mga6.x86_64
- libdrm-common-2.4.90-1.mga6.x86_64
complained for some (as it did with the Qt update):
"The following must be removed to allow other updates:
task-lxqt-minimal-0.11.0-1.mga6.noarch
because lxqt-panel is missing." I had to say 'yes' to get all 7 drm pkgs updated.
I installed also: drm-utils-2.4.90-1
Have to report back later.

CC: (none) => lewyssmith

Comment 11 Lewis Smith 2018-03-06 07:42:28 CET
M6/64 real EFI hardware with AMD/ATI/Radeon HD 7310 graphics, continued.

drm-utils provides the following programs:
/usr/bin/amdgpu_test
/usr/bin/drmdevice
/usr/bin/kms-steal-crtc
/usr/bin/kmstest
/usr/bin/kms-universal-planes
/usr/bin/modeprint
/usr/bin/modetest
/usr/bin/vbltest

 $ amdgpu_test    
Cannot open AMDGPU device: Success               ???
 $ kmstest
 $ modetest
 $ vbltest
all gave failure output as per Herman's comment 6.
 $ drmdevice
gave the output shown in the same comment.

All this is unhelpful, but in the light of all the no-grief comments - myself included -, OKing for x64 & validating.

Whiteboard: mga6-32-ok => mga6-32-ok MGA6-64-OK
Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

Comment 12 Mageia Robot 2018-03-06 08:56:23 CET
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2018-0043.html

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


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