https://bugs.kde.org/show_bug.cgi?id=503082
RM <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #14 from RM <[email protected]> --- I've been fighting with something similar. Per my research this cannot be fixed via udev rule as it all takes place prior to udev activation. My workaround -- and apparently this hack works on only *some* kernels -- is `initcall_blacklist=simpledrm_platform_driver_init` on the kernel commandline to blacklist `simpledrm` and prevent it from taking over any of the `/dev/dri/card*` objects. You lose early boot spew visibility until drm takes over. On my system `/dev/dri/card0` is now the same as `/dev/dri/renderD128`, `card1` is `D129`, and `card2` is `D130`. Annoyingly they're out of alignment with PCI address ordering (`/dev/dri/by-path`) but at least `card0` and `renderD128` now point to my intended "main" GPU. Regarding `DRI_PRIME`, it may be helpful to reference a PCI address instead of an ordinal 0/1/2, e.g. `DRI_PRIME=pci-0000_01_00_0`. Of course, PCI addresses can be shuffled around as well just from adding or removing hardware. My iGPU gets bumped from 0000_0b to 000_0c when dGPU #2 is present. There's no winning at this, IMHO. Not yet. -- You are receiving this mail because: You are watching all bug changes.
