<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - smu7_populate_single_firmware_entry fails to load powerplay firmware." href="https://bugs.freedesktop.org/show_bug.cgi?id=104854#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - smu7_populate_single_firmware_entry fails to load powerplay firmware." href="https://bugs.freedesktop.org/show_bug.cgi?id=104854">bug 104854</a> from <a class="email" href="mailto:koalinux@gmail.com" title="José Pekkarinen <koalinux@gmail.com>"> José Pekkarinen</a> <pre>Created <a href="attachment.cgi?id=140293" name="attach_140293" title="dri config to work it around.">attachment 140293</a> <a href="attachment.cgi?id=140293&action=edit" title="dri config to work it around.">[details]</a> dri config to work it around. I spent some more time toying this around and I found that, building the drm inside the kernel like in this extract of the config, and provided that you still blacklist the amdgpu module: BOOT_IMAGE=/kernel-genkernel-x86_64-4.17.2+ root=/dev/mapper/bee-root ro dolvm crypt_root=/dev/sda3 real_root=/dev/bee/root resume=/dev/bee/swap iommu=pt intel_iommu=on kvm-intel.nested=1 apparmor=1 zswap.enabled=1 security=apparmor crashkernel=256M modprobe.blacklist=amdgpu The kernel booting will ignore my evil purposes: # dmesg|grep amdgpu [ 0.000000] Command line: BOOT_IMAGE=/kernel-genkernel-x86_64-4.17.2+ root=/dev/mapper/bee-root ro dolvm crypt_root=/dev/sda3 real_root=/dev/bee/root resume=/dev/bee/swap iommu=pt intel_iommu=on kvm-intel.nested=1 apparmor=1 zswap.enabled=1 security=apparmor crashkernel=256M modprobe.blacklist=amdgpu [ 0.000000] Kernel command line: BOOT_IMAGE=/kernel-genkernel-x86_64-4.17.2+ root=/dev/mapper/bee-root ro dolvm crypt_root=/dev/sda3 real_root=/dev/bee/root resume=/dev/bee/swap iommu=pt intel_iommu=on kvm-intel.nested=1 apparmor=1 zswap.enabled=1 security=apparmor crashkernel=256M modprobe.blacklist=amdgpu [ 0.755913] [drm] amdgpu kernel modesetting enabled. [ 0.756304] amdgpu 0000:01:00.0: enabling device (0400 -> 0403) [ 0.772792] amdgpu 0000:01:00.0: VRAM: 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used) [ 0.773338] amdgpu 0000:01:00.0: GTT: 256M 0x0000000000000000 - 0x000000000FFFFFFF [ 0.777463] [drm] amdgpu: 2048M of VRAM memory ready [ 0.778060] [drm] amdgpu: 3072M of GTT memory ready. [ 0.798170] amdgpu: [powerplay] can't get the mac of 5 [ 0.809732] [drm] Initialized amdgpu 3.25.0 20150101 for 0000:01:00.0 on minor 0 [ 6.112759] amdgpu: [powerplay] VI should always have 2 performance levels [ 6.144432] amdgpu 0000:01:00.0: GPU pci config reset [ 22.024297] amdgpu: [powerplay] can't get the mac of 5 resulting in a properly booted machine that is able to use the amd gpu: $ DRI_PRIME=1 glxinfo |grep OpenGL OpenGL vendor string: X.Org OpenGL renderer string: AMD Radeon (TM) R7 M360 (ICELAND, DRM 3.25.0, 4.17.2+, LLVM 6.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.1.2 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 18.1.2 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.1 Mesa 18.1.2 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10 OpenGL ES profile extensions: Technically it seems to be a weird workaround and I don't know if that may light your bulbs in any way, but hey, I hope it helps. José.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>