From: Dennis Schridde <dennis.schridde-axtXthT+lymYbFdUjOg7S7NAH6kLmebB@public.gmane.org>
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Cc: "Deucher,
Alexander" <Alexander.Deucher-5C7GfCeVMHo@public.gmane.org>,
"Yu, Qiang" <Qiang.Yu-5C7GfCeVMHo@public.gmane.org>
Subject: Re: AMDGPU without display output
Date: Tue, 18 Apr 2017 14:25:18 +0200 [thread overview]
Message-ID: <2000813.UM9hCpDLC0@c07060> (raw)
In-Reply-To: <DM5PR12MB1739D59ACC914AE04D4A35E38F050-2J9CzHegvk/RSyQDjr89dQdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 512 bytes --]
On Freitag, 14. April 2017 03:50:30 CEST Yu, Qiang wrote:
> PS. If you want to use X11/OGL on this no display output card, just add an
> option to the amdgpu kernel module "virtual_display=all" which will fake a
> display output so that the xserver can start with amdgpu DDX successfully.
> You can use remote desktop apps like VNC to view the X screen.
Thanks a lot for that information! This will likely simplify several things,
once we solve the "Fatal error during GPU init" (see my other email).
--Dennis
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 681 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2017-04-18 12:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 14:31 AMDGPU without display output Dennis Schridde
2017-04-13 15:15 ` Deucher, Alexander
[not found] ` <BN6PR12MB165282CADA64ADF35AD09EF4F7020-/b2+HYfkarQqUD6E6FAiowdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-04-13 15:20 ` Dennis Schridde
2017-04-14 1:50 ` Yu, Qiang
[not found] ` <DM5PR12MB1739D59ACC914AE04D4A35E38F050-2J9CzHegvk/RSyQDjr89dQdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-04-18 12:25 ` Dennis Schridde [this message]
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=2000813.UM9hCpDLC0@c07060 \
--to=dennis.schridde-axtxtht+lymybfdujog7s7nah6klmebb@public.gmane.org \
--cc=Alexander.Deucher-5C7GfCeVMHo@public.gmane.org \
--cc=Qiang.Yu-5C7GfCeVMHo@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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