All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: Andy Lutomirski <luto@amacapital.net>
Cc: DRI <dri-devel@lists.freedesktop.org>
Subject: Re: X using radeon is refusing to start
Date: Fri, 06 Feb 2015 11:51:55 +0900	[thread overview]
Message-ID: <54D42C4B.200@daenzer.net> (raw)
In-Reply-To: <CALCETrWYmVC7OFHLwerWJXbyt1Ek2TvQ2PV7wCvtRKBqWwf+Hw@mail.gmail.com>

On 06.02.2015 09:10, Andy Lutomirski wrote:
> I just started getting X failures that say:
> 
> [   739.208] (EE) RADEON(0): [drm] failed to set drm interface version.
> 
> I'm not sure what triggered it.
> 
> dmesg says:
> 
> [  740.156499] [drm:drm_stub_open]
> [  740.156502] [drm:drm_open_helper] pid = 2170, minor = 0
> [  740.156541] [drm:drm_ioctl] pid=2170, dev=0xe200, auth=1,
> DRM_IOCTL_MODE_GETRESOURCES
> [  740.156557] [drm:drm_ioctl] pid=2170, dev=0xe200, auth=1,
> DRM_IOCTL_MODE_GETRESOURCES
> [  740.156575] [drm:drm_release] open_count = 2
> [  740.156577] [drm:drm_release] pid = 2170, device = 0xe200, open_count = 2
> [  740.158548] [drm:drm_ioctl] pid=2170, dev=0xe200, auth=1,
> DRM_IOCTL_SET_VERSION
> [  740.158549] [drm:drm_ioctl] ret = -13
> [  740.159612] [drm:drm_framebuffer_reference] ffff8804457110a0: FB ID: 83 (3)
> 
> -13 means -EACCES.

We'd need to see dmesg from the beginning to be sure, but it looks like
something (maybe plymouth or whatever boot splash you're using?) is
keeping the DRM device open, so Xorg doesn't become DRM master.


-- 
Earthling Michel Dänzer               |               http://www.amd.com
Libre software enthusiast             |             Mesa and X developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-02-06  2:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06  0:10 X using radeon is refusing to start Andy Lutomirski
2015-02-06  2:51 ` Michel Dänzer [this message]
2015-02-06  8:29   ` Chris Wilson
2015-02-06  8:37     ` Michel Dänzer

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=54D42C4B.200@daenzer.net \
    --to=michel@daenzer.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=luto@amacapital.net \
    /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.