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 105883] booting with kernel using amd-staging-drm-next on 2400G hangs
Date: Thu, 05 Apr 2018 20:15:28 +0000	[thread overview]
Message-ID: <bug-105883-502-uH6FcOQzXw@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105883-502@http.bugs.freedesktop.org/>


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

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

--- Comment #6 from Harry Wentland <harry.wentland@amd.com> ---
On Ubuntu the kernel log keeps appending to /var/log/kern.log, but that might
look different on different distros.

If you have a luxury of a second system you might be able to ssh into the Ryzen
system and run dmesg that way.

As for the options Edward mentioned, you can pass them to the kernel command
line. If you use grub for your bootloader you'd press 'e' on the selected
kernel and append " amdgpu.dpm=0 amdgpu.dc=1" at the end of the line that
starts with "linux". Alternatively you can append those to GRUB_CMDLINE_LINUX
in /etc/default/grub and run "sudo update-grub"

Keep in mind that this is how I'd do it on Ubuntu. There' might be a way to
pass these through /etc/modconf.d as well.

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

[-- Attachment #1.2: Type: text/html, Size: 1753 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-04-05 20:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-04 11:36 [Bug 105883] booting with kernel using amd-staging-drm-next on 2400G hangs bugzilla-daemon
2018-04-04 17:02 ` bugzilla-daemon
2018-04-04 17:17 ` bugzilla-daemon
2018-04-04 17:19 ` bugzilla-daemon
2018-04-05  5:19 ` bugzilla-daemon
2018-04-05  8:01 ` bugzilla-daemon
2018-04-05 20:15 ` bugzilla-daemon [this message]
2018-04-08  2:59 ` bugzilla-daemon
2018-04-09  8:10 ` bugzilla-daemon
2018-04-16 13:01 ` bugzilla-daemon
2018-04-16 13:01 ` bugzilla-daemon
2018-04-16 13:02 ` bugzilla-daemon
2018-04-16 13:04 ` bugzilla-daemon
2018-04-22 14:55 ` bugzilla-daemon
2018-04-22 14:57 ` bugzilla-daemon
2019-11-19  8:34 ` 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-105883-502-uH6FcOQzXw@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