From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110478] AMDGPU error(failed to set mode: cannot allocate memory) when hdmi connected
Date: Tue, 23 Apr 2019 13:27:20 +0000 [thread overview]
Message-ID: <bug-110478-502-7YuVNeXmRB@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110478-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 777 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110478
--- Comment #3 from cmdrrdo@gmail.com ---
(In reply to Michel Dänzer from comment #2)
> Yeah, this is a kernel issue. There's only a small amount of VRAM available,
> so the 5760x2160 framebuffer can't fit, and the kernel driver doesn't
> support scanout from system memory with Raven Ridge yet.
>
> Meanwhile, if the amount of VRAM can be increased in the BIOS setup, try
> that.
Thank you very much for the explanation and workaround suggestion. My choices
on this laptop are "128M" or "Auto". I think I have to poke Asus about this,
but: With Auto I do get 2048 as per dmesg and it's working.
So again, thank you. :)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1696 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-04-23 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-110478-502@http.bugs.freedesktop.org/>
2019-04-23 8:58 ` [Bug 110478] AMDGPU error(failed to set mode: cannot allocate memory) when hdmi connected bugzilla-daemon
2019-04-23 13:27 ` bugzilla-daemon [this message]
2019-11-19 9:19 ` 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-110478-502-7YuVNeXmRB@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.