All of lore.kernel.org
 help / color / mirror / Atom feed
* [Bug 110478] AMDGPU error(failed to set mode: cannot allocate memory) when hdmi connected
       [not found] <bug-110478-502@http.bugs.freedesktop.org/>
@ 2019-04-23  8:58 ` bugzilla-daemon
  2019-04-23 13:27 ` bugzilla-daemon
  2019-11-19  9:19 ` bugzilla-daemon
  2 siblings, 0 replies; 3+ messages in thread
From: bugzilla-daemon @ 2019-04-23  8:58 UTC (permalink / raw)
  To: dri-devel


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

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

Michel Dänzer <michel@daenzer.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Driver/AMDgpu               |DRM/AMDgpu
         QA Contact|xorg-team@lists.x.org       |
           Assignee|xorg-driver-ati@lists.x.org |dri-devel@lists.freedesktop
                   |                            |.org
            Product|xorg                        |DRI

--- Comment #2 from Michel Dänzer <michel@daenzer.net> ---
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.

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

[-- Attachment #1.2: Type: text/html, Size: 2732 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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug 110478] AMDGPU error(failed to set mode: cannot allocate memory) when hdmi connected
       [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
  2019-11-19  9:19 ` bugzilla-daemon
  2 siblings, 0 replies; 3+ messages in thread
From: bugzilla-daemon @ 2019-04-23 13:27 UTC (permalink / raw)
  To: dri-devel


[-- 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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug 110478] AMDGPU error(failed to set mode: cannot allocate memory) when hdmi connected
       [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
@ 2019-11-19  9:19 ` bugzilla-daemon
  2 siblings, 0 replies; 3+ messages in thread
From: bugzilla-daemon @ 2019-11-19  9:19 UTC (permalink / raw)
  To: dri-devel


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

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

Martin Peres <martin.peres@free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |MOVED
             Status|NEW                         |RESOLVED

--- Comment #4 from Martin Peres <martin.peres@free.fr> ---
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.

You can subscribe and participate further through the new bug through this link
to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/754.

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

[-- Attachment #1.2: Type: text/html, Size: 2452 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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2019-11-19  9:19 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [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
2019-11-19  9:19 ` bugzilla-daemon

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.