| Bug ID | 110962 |
|---|---|
| Summary | Wrong dependencies cause force dependency on amdgpu-dkms |
| Product | DRI |
| Version | unspecified |
| Hardware | Other |
| OS | All |
| Status | NEW |
| Severity | major |
| Priority | medium |
| Component | DRM/AMDgpu-pro |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | ashark@linuxcomp.ru |
19.20-812932 release for Ubuntu amdgpu-pro(-hwe) and amdgpu-pro-lib32 depend on amdgpu(-hwe), but actually they should depend on amdgpu-lib(-hwe) (just like open variant packages). Because of that even when running installer with --no-dkms, it still is in packages list (because amdgpu(-hwe) depends on it). Is it intentional or just a mistake? I think this is a mistake, because if you want force dependency on amdgpu-dkms with pro stack, you would make all other checks in amdgpu installer script. But because user giver "--no-dkms", such checks are skipped there. Also, I was repacking amdgpu-pro packages (ubuntu archive) to Arch Linux. Am I correct, that amdgpu-dkms package was made with Ubuntu LTS slowness in mind, and is absolutely unneeded for Arch Linux? Am I right that I do not loose any functionality abilities (maybe that allows you to watch gpu's load, like wattman) even for pro stack if I omit amdgpu-dkms?
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
