911795 – x11-libs/libdrm has useflag for video_cards_radeon but not video_cards_radeonsi

Bug 911795 - x11-libs/libdrm has useflag for video_cards_radeon but not video_cards_radeonsi

Summary: x11-libs/libdrm has useflag for video_cards_radeon but not video_cards_radeonsi

Status:	UNCONFIRMED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Gentoo X packagers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2023-08-06 04:42 UTC by Michael Jones
Modified:	2024-01-09 11:58 UTC (History)
CC List:	2 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Michael Jones 2023-08-06 04:42:02 UTC

But x11-base/xorg-drivers supports the useflag video_cards_radeonsi without enabling video_cards_radeon .

if the user sets VIDEO_CARDS="radeonsi amdgpu", as indicated in this wiki page: https://wiki.gentoo.org/wiki/AMDGPU

then xorg-drivers can't be installed, because it depends on 

video_cards_radeon?        ( >=x11-drivers/xf86-video-ati-18.0.1-r1 )
video_cards_radeonsi?      ( >=x11-drivers/xf86-video-ati-18.0.1-r1 )


which depends on

 >=x11-libs/libdrm-2.4.89[video_cards_radeon]



if x11-libs/libdrm has support for video_cards_radeonsi, then users would be able to set VIDEO_CARDS="radeonsi amdgpu" like the wiki says to.


Reproducible: Always

Comment 1 Alexey Zapparov 2023-11-02 23:43:50 UTC

I'm facing the same issue. I have VIDEO_CARDS="amdgpu radeonsi" in my make.conf, thus I had to add to package.use:

  >=x11-libs/libdrm-2.4.116 video_cards_radeon

Comment 2 haukurpj 2024-01-09 11:58:41 UTC

I'm new to Gentoo and I also noticed this inconsistency(?).

First, when installing the system I incorrectly set "amdgpu radeon" as VIDEO_CARDS. Later, I fixed the error and set it correctly as "amdgpu radeonsi". Then I was doing a world update when I encountered this bug.

I am currently using the "package.use" workaround: "x11-libs/libdrm video_cards_radeon" but I find it strange.

To be clear, when this workaround is not present a:

emerge --ask --changed-use --deep --update @world

results in:

x11-libs/libdrm:0

  (x11-libs/libdrm-2.4.118:0/0::gentoo, ebuild scheduled for merge) USE="-valgrind" ABI_X86="(64) -32 (-x32)" VIDEO_CARDS="amdgpu (-exynos) (-freedreno) -intel -nouveau (-omap) -radeon (-tegra) (-vc4) (-vivante) -vmware" conflicts with
    >=x11-libs/libdrm-2.4.110[video_cards_radeon] required by (media-libs/mesa-23.1.9:0/0::gentoo, installed) USE="X gles2 llvm proprietary-codecs vulkan wayland zstd -d3d9 -debug -gles1 -lm-sensors -opencl -osmesa (-selinux) -test -unwind -vaapi -valgrind -vdpau -vulkan-overlay -xa -zink" ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="sse2" VIDEO_CARDS="radeonsi -d3d12 (-freedreno) -intel -lavapipe (-lima) -nouveau (-panfrost) -r300 -r600 -radeon (-v3d) (-vc4) -virgl (-vivante) -vmware"
                              ^^^^^^^^^^^^^^^^^^ 
    >=x11-libs/libdrm-2.4.89[video_cards_radeon] required by (x11-drivers/xf86-video-ati-22.0.0:0/0::gentoo, installed) USE="udev" ABI_X86="(64)"
                             ^^^^^^^^^^^^^^^^^^ 


I've tried to fix this by unmerging "x11-libs/libdrm" and "x11-drivers/xf86-video-ati" and doing a world update, but it results in the same conflict.