From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: nouveau-drm compile failure
Date: Thu, 20 May 2010 16:06:59 -0700 [thread overview]
Message-ID: <AANLkTik7thIFwNtu8V8D9NARc9-MjsNArwYV5OQjOg9F@mail.gmail.com> (raw)
In-Reply-To: <87ljbepefc.fsf@newton.gmurray.org.uk>
>> There's an API break between the nouveau driver and the drm in 2.6.3[23] (not
>> completely sure about the versions)
>>
>> Hence the workaround of nouveau-drm
>>
>> Hopefully it will be *very* temporary
>
> It is. 2.6.34 (which is in ~arch) fixes the API break with the Nouveau
> driver.
Supposedly it's an API break between the kernel and libdrm:
"Nouveau DRM in kernel 2.6.33 is API incompatible to
>=x11-libs/libdrm-2.4.18, please use x11-base/nouveau-drm instead."
According to ebuild dependencies and messages, my combination of
xf86-video-nouveau-0.0.15_pre20100213 and x11-libs/libdrm-2.4.18_pre
should work. I get this same error no matter what combination of
libdrm, xf86-video-nouveau, and nouveau-firmware I try, and whether or
not I have CONFIG_DRM_NOUVEAU=y. This makes me think it's not related
to the API break:
(EE) Failed to load module "dri" (module does not exist, 0)
(EE) Failed to load module "dri2" (module does not exist, 0)
(EE) [drm] No DRICreatePCIBusID symbol
(EE) No devices detected.
Google says the error can be due to disabling dri in xorg.conf, but I
don't have anything like that. Should CONFIG_DRM_NOUVEAU=y include
the dri or dri2 module?
- Grant
next prev parent reply other threads:[~2010-05-20 18:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 16:56 [gentoo-user] nouveau-drm compile failure Grant
2010-05-20 17:32 ` [gentoo-user] " Nikos Chantziaras
2010-05-20 17:54 ` Nikos Chantziaras
2010-05-20 18:59 ` Alan McKinnon
2010-05-20 19:14 ` Grant
2010-05-20 19:21 ` Graham Murray
2010-05-20 19:26 ` Alan McKinnon
2010-05-20 23:06 ` Grant [this message]
2010-05-21 5:25 ` Graham Murray
2010-05-21 17:26 ` Grant
2010-05-21 21:10 ` walt
2010-05-21 23:42 ` Grant
2010-05-22 15:58 ` walt
2010-05-22 20:42 ` Grant
2010-05-20 19:05 ` Grant
2010-05-20 19:09 ` Grant
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=AANLkTik7thIFwNtu8V8D9NARc9-MjsNArwYV5OQjOg9F@mail.gmail.com \
--to=emailgrant@gmail.com \
--cc=gentoo-user@lists.gentoo.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