| 1 |
>> There's an API break between the nouveau driver and the drm in 2.6.3[23] (not |
| 2 |
>> completely sure about the versions) |
| 3 |
>> |
| 4 |
>> Hence the workaround of nouveau-drm |
| 5 |
>> |
| 6 |
>> Hopefully it will be *very* temporary |
| 7 |
> |
| 8 |
> It is. 2.6.34 (which is in ~arch) fixes the API break with the Nouveau |
| 9 |
> driver. |
| 10 |
|
| 11 |
Supposedly it's an API break between the kernel and libdrm: |
| 12 |
|
| 13 |
"Nouveau DRM in kernel 2.6.33 is API incompatible to |
| 14 |
>=x11-libs/libdrm-2.4.18, please use x11-base/nouveau-drm instead." |
| 15 |
|
| 16 |
According to ebuild dependencies and messages, my combination of |
| 17 |
xf86-video-nouveau-0.0.15_pre20100213 and x11-libs/libdrm-2.4.18_pre |
| 18 |
should work. I get this same error no matter what combination of |
| 19 |
libdrm, xf86-video-nouveau, and nouveau-firmware I try, and whether or |
| 20 |
not I have CONFIG_DRM_NOUVEAU=y. This makes me think it's not related |
| 21 |
to the API break: |
| 22 |
|
| 23 |
(EE) Failed to load module "dri" (module does not exist, 0) |
| 24 |
(EE) Failed to load module "dri2" (module does not exist, 0) |
| 25 |
(EE) [drm] No DRICreatePCIBusID symbol |
| 26 |
(EE) No devices detected. |
| 27 |
|
| 28 |
Google says the error can be due to disabling dri in xorg.conf, but I |
| 29 |
don't have anything like that. Should CONFIG_DRM_NOUVEAU=y include |
| 30 |
the dri or dri2 module? |
| 31 |
|
| 32 |
- Grant |
Archives