All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89405] radeon: *ERROR* invalid ioctl running weston-launch while X is running
Date: Mon, 04 May 2015 16:59:48 +0000	[thread overview]
Message-ID: <bug-89405-502-TxYoSlCinV@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-89405-502@http.bugs.freedesktop.org/>


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

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

--- Comment #1 from fosero@gmail.com ---
Maybe unrelated, but there seems to be issue initializing given gfx chip when
running anything non X.

On a fresh boot trying to run any wayland session (weston directly or current
stable gdm) results in just a black screen. No obvious error in the logs.
Booting with plymouth enabled also just results in a black screen.

However when X is started first any subsequent wayland session shows just fine.

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

[-- Attachment #1.2: Type: text/html, Size: 1353 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-05-04 16:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03  8:56 [Bug 89405] radeon: *ERROR* invalid ioctl running weston-launch while X is running bugzilla-daemon
2015-05-04 16:59 ` bugzilla-daemon [this message]
2015-05-05  6:04 ` bugzilla-daemon
2015-05-05 12:44 ` bugzilla-daemon
2015-05-05 12:45 ` bugzilla-daemon
2015-05-05 12:45 ` bugzilla-daemon
2019-11-19  9: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-89405-502-TxYoSlCinV@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.