From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103678] gdm couldn't start with Vega RX 56 video card
Date: Sun, 12 Nov 2017 18:19:14 +0000 [thread overview]
Message-ID: <bug-103678-502-U1Nsug6CMB@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103678-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1709 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=103678
--- Comment #15 from Christian König <deathsimple@vodafone.de> ---
(In reply to mikhail.v.gavrilov from comment #13)
> a. Intel Graphics Processor -> Enabled
> b. Initial display output -> PCIe 2 slot
> c. A monitor connected to Radeon
> BIOS screenshot: https://bugs.freedesktop.org/attachment.cgi?id=135427
> In this case all BIOS output, boot messages and the console passes through
> the Radeon graphics card.
> But graphics subsusystem couldn't launched.
> The Radeon turbine works silent.
> Demonstration: https://youtu.be/jjGO650EE80
> I think this is bug because even if video card unsupported it must works in
> VESA mode. This behaviour worked in Windows.
Interesting, that indeed that should work. Could be a bug in the VESA BIOS or
the driver touching the hardware even if it decided not to do so.
Please try booting with modprobe.blacklist=amdgpu on the kernel commandline.
> $ glxinfo | grep -i "OpenGL version"
> OpenGL version string: 3.0 Mesa 17.2.4
> Which minimal version is needed?
> I see on Fedora 27 I have Mesa 17.2.4
Not the slightest idea when Vega10 support was added to Mesa, but 17.2.4 is
only a few days old so that could work.
I would try to get X working with only the kernel first. If you have that
working and still no OpenGL you can still compile Mesa on your own.
Alex Kernel branch is here BTW: https://cgit.freedesktop.org/~agd5f/linux/
You can also find a amd-staging-4.13 branch there, but that is a ~month old and
not maintained any more. amd-staging-drm-next is the latest development work.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2863 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
next prev parent reply other threads:[~2017-11-12 18:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 22:08 [Bug 103678] gdm couldn't start with Vega RX 56 video card bugzilla-daemon
2017-11-10 22:08 ` bugzilla-daemon
2017-11-10 22:08 ` bugzilla-daemon
2017-11-10 22:09 ` bugzilla-daemon
2017-11-12 8:49 ` bugzilla-daemon
2017-11-12 8:49 ` bugzilla-daemon
2017-11-12 10:04 ` bugzilla-daemon
2017-11-12 10:06 ` bugzilla-daemon
2017-11-12 10:06 ` bugzilla-daemon
2017-11-12 10:28 ` bugzilla-daemon
2017-11-12 10:29 ` bugzilla-daemon
2017-11-12 10:31 ` bugzilla-daemon
2017-11-12 16:46 ` bugzilla-daemon
2017-11-12 16:48 ` bugzilla-daemon
2017-11-12 16:49 ` bugzilla-daemon
2017-11-12 17:10 ` bugzilla-daemon
2017-11-12 17:55 ` bugzilla-daemon
2017-11-12 18:19 ` bugzilla-daemon [this message]
2017-11-12 21:47 ` bugzilla-daemon
2017-11-13 8:02 ` 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-103678-502-U1Nsug6CMB@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.