From: Chris Wilson <chris@chris-wilson.co.uk>
To: Christian Gmeiner <christian.gmeiner@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: xf86-video-intel 2.20.5 does not detect PCI_CHIP_SANDYBRIDGE_M_GT1
Date: Thu, 30 Aug 2012 11:51:24 +0100 [thread overview]
Message-ID: <84c8a8$5idipv@orsmga001.jf.intel.com> (raw)
In-Reply-To: <CAH9NwWfaFbTALwpD18zQr3TNhSBg+xB_8JRZ0G7+1TzDUeeUJQ@mail.gmail.com>
On Thu, 30 Aug 2012 10:24:17 +0200, Christian Gmeiner <christian.gmeiner@gmail.com> wrote:
> [ 13.840] drmOpenDevice: node name is /dev/dri/card0
> [ 13.840] drmOpenDevice: open result is 7, (OK)
> [ 13.840] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
> [ 13.840] drmOpenDevice: node name is /dev/dri/card0
> [ 13.840] drmOpenDevice: open result is 7, (OK)
> [ 13.840] drmOpenByBusid: drmOpenMinor returns 7
> [ 13.840] drmOpenByBusid: Interface 1.4 failed, trying 1.1
> [ 13.840] drmOpenByBusid: drmGetBusid reports
This is the reason why we fail to detect the device. The device node
exists but the drmSetVersion call fails, which is, of course,
completely impossible. Both Fedora and Ubuntu are tracking a race
condition in the early setup with afaict exactly this symptom.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-08-30 10:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 7:43 xf86-video-intel 2.20.5 does not detect PCI_CHIP_SANDYBRIDGE_M_GT1 Christian Gmeiner
2012-08-30 7:50 ` Daniel Vetter
2012-08-30 8:12 ` Zhang, Xiong Y
2012-08-30 8:17 ` Daniel Vetter
2012-08-30 8:24 ` Christian Gmeiner
2012-08-30 10:51 ` Chris Wilson [this message]
2012-08-30 11:24 ` Christian Gmeiner
2012-08-30 11:29 ` Christian Gmeiner
2012-08-31 21:57 ` Christian Gmeiner
2012-08-30 8:23 ` Christian Gmeiner
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='84c8a8$5idipv@orsmga001.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=christian.gmeiner@gmail.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@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.