dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104854] smu7_populate_single_firmware_entry fails to load powerplay firmware.
Date: Sat, 23 Jun 2018 21:19:51 +0000	[thread overview]
Message-ID: <bug-104854-502-M4iQkuPL42@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104854-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 3207 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=104854

--- Comment #10 from José Pekkarinen <koalinux@gmail.com> ---
Created attachment 140293
  --> https://bugs.freedesktop.org/attachment.cgi?id=140293&action=edit
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é.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4187 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-06-23 21:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-30  8:32 [Bug 104854] smu7_populate_single_firmware_entry fails to load powerplay firmware bugzilla-daemon
2018-03-07  9:39 ` bugzilla-daemon
2018-03-08 20:22 ` bugzilla-daemon
2018-03-08 20:36 ` bugzilla-daemon
2018-03-09  7:36 ` bugzilla-daemon
2018-03-30 16:12 ` bugzilla-daemon
2018-03-31 17:51 ` bugzilla-daemon
2018-03-31 19:10 ` bugzilla-daemon
2018-06-15 15:33 ` bugzilla-daemon
2018-06-19  9:06 ` bugzilla-daemon
2018-06-19  9:15 ` bugzilla-daemon
2018-06-23 21:19 ` bugzilla-daemon [this message]
2018-06-23 21:22 ` bugzilla-daemon
2019-11-19  8:29 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-104854-502-M4iQkuPL42@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox