I'm trying to compile nouveau-drm for my Nvidia 8400GS video card, but
compilation fails:
/var/tmp/portage/x11-base/nouveau-drm-20100316/work/master/drivers/gpu/drm/nouveau/nouveau_drv.c:
In function 'nouveau_pci_suspend':
/var/tmp/portage/x11-base/nouveau-drm-20100316/work/master/drivers/gpu/drm/nouveau/nouveau_drv.c:232:
error: implicit declaration of function 'acquire_console_sem'
/var/tmp/portage/x11-base/nouveau-drm-20100316/work/master/drivers/gpu/drm/nouveau/nouveau_drv.c:234:
error: implicit declaration of function 'release_console_sem'
I get kernel config warnings:
* CONFIG_FB_CFB_FILLRECT: is not set when it should be.
* CONFIG_FB_CFB_COPYAREA: is not set when it should be.
* CONFIG_FB_CFB_IMAGEBLIT: is not set when it should be.
But those kernel options are required to be automatically selected by
a list of dependant options which is very long and very ridiculous.
Are those options the reason for the compile failure?
- Grant
05-20-2010, 05:32 PM
Nikos Chantziaras
nouveau-drm compile failure
On 05/20/2010 07:56 PM, Grant wrote:
I'm trying to compile nouveau-drm for my Nvidia 8400GS video card, but
compilation fails:
I don't think you should be using nouveau-drm in the first place. This
driver is now in the kernel itself. nouveau-drm was used before that
driver moved into the Linux kernel together with the other DRM drivers.
Also, as a consequence, trying to use nouveau-drm means you're getting
an outdated driver, since AFAIK the updates happen in-kernel now.
05-20-2010, 05:54 PM
Nikos Chantziaras
nouveau-drm compile failure
On 05/20/2010 08:32 PM, Nikos Chantziaras wrote:
On 05/20/2010 07:56 PM, Grant wrote:
I'm trying to compile nouveau-drm for my Nvidia 8400GS video card, but
compilation fails:
I don't think you should be using nouveau-drm in the first place. This
driver is now in the kernel itself. nouveau-drm was used before that
driver moved into the Linux kernel together with the other DRM drivers.
Also, as a consequence, trying to use nouveau-drm means you're getting
an outdated driver, since AFAIK the updates happen in-kernel now.
I forgot to mention *where* in the kernel configuration you can enable
nouveau. It's in Device Drivers->Staging drivers
05-20-2010, 06:59 PM
Alan McKinnon
nouveau-drm compile failure
On Thursday 20 May 2010 19:32:33 Nikos Chantziaras wrote:
> On 05/20/2010 07:56 PM, Grant wrote:
> > I'm trying to compile nouveau-drm for my Nvidia 8400GS video card, but
>
> > compilation fails:
> I don't think you should be using nouveau-drm in the first place. This
> driver is now in the kernel itself. nouveau-drm was used before that
> driver moved into the Linux kernel together with the other DRM drivers.
>
> Also, as a consequence, trying to use nouveau-drm means you're getting
> an outdated driver, since AFAIK the updates happen in-kernel now.
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
--
alan dot mckinnon at gmail dot com
05-20-2010, 07:05 PM
Grant
nouveau-drm compile failure
>> I'm trying to compile nouveau-drm for my Nvidia 8400GS video card, but
>> compilation fails:
>
> I don't think you should be using nouveau-drm in the first place. *This
> driver is now in the kernel itself. *nouveau-drm was used before that driver
> moved into the Linux kernel together with the other DRM drivers.
Well, the xf86-video-nouveau-0.0.16_pre20100510 ebuild says:
Nouveau DRM not detected. If you want any kind of
acceleration with nouveau, emerge x11-base/nouveau-drm or
enable CONFIG_DRM_NOUVEAU in the kernel.
Nouveau DRM in kernel 2.6.33 is API incompatible to
>=x11-libs/libdrm-2.4.18, please use x11-base/nouveau-drm
instead.
Unfortunately, the same ebuild depends on >=x11-libs/libdrm-2.4.19. I
tried to ignore the warning but X fails with:
(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.
The xf86-video-nouveau-0.0.15_pre20100213 ebuild only depends on
>=x11-libs/libdrm-2.4.18_pre so I installed those but I still get the
errors above when trying to start X.
Any ideas? Do you have nouveau working?
- Grant
05-20-2010, 07:09 PM
Grant
nouveau-drm compile failure
>>> I'm trying to compile nouveau-drm for my Nvidia 8400GS video card, but
>>> compilation fails:
>>
>> I don't think you should be using nouveau-drm in the first place. *This
>> driver is now in the kernel itself. *nouveau-drm was used before that driver
>> moved into the Linux kernel together with the other DRM drivers.
>
> Well, the xf86-video-nouveau-0.0.16_pre20100510 ebuild says:
>
> Nouveau DRM not detected. If you want any kind of
> acceleration with nouveau, emerge x11-base/nouveau-drm or
> enable CONFIG_DRM_NOUVEAU in the kernel.
> Nouveau DRM in kernel 2.6.33 is API incompatible to
>>=x11-libs/libdrm-2.4.18, please use x11-base/nouveau-drm
> instead.
>
> Unfortunately, the same ebuild depends on >=x11-libs/libdrm-2.4.19. *I
> tried to ignore the warning but X fails with:
>
> (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.
>
> The xf86-video-nouveau-0.0.15_pre20100213 ebuild only depends on
>>=x11-libs/libdrm-2.4.18_pre so I installed those but I still get the
> errors above when trying to start X.
>
> Any ideas? *Do you have nouveau working?
>
> - Grant
I forgot to mention that I have CONFIG_DRM_NOUVEAU enabled in my
2.6.33 kernel and nouveau-firmware is loading successfully.
- Grant
05-20-2010, 07:14 PM
Grant
nouveau-drm compile failure
>> > I'm trying to compile nouveau-drm for my Nvidia 8400GS video card, but
>>
>> > compilation fails:
>> I don't think you should be using nouveau-drm in the first place. *This
>> driver is now in the kernel itself. *nouveau-drm was used before that
>> driver moved into the Linux kernel together with the other DRM drivers.
>>
>> Also, as a consequence, trying to use nouveau-drm means you're getting
>> an outdated driver, since AFAIK the updates happen in-kernel now.
>
> 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
Have you installed nouveau-drm? If so, do you get kernel config
warnings during the emerge?
- Grant
05-20-2010, 07:21 PM
Graham Murray
nouveau-drm compile failure
Alan McKinnon <alan.mckinnon@gmail.com> writes:
> 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.
05-20-2010, 07:26 PM
Alan McKinnon
nouveau-drm compile failure
On Thursday 20 May 2010 21:21:27 Graham Murray wrote:
> Alan McKinnon <alan.mckinnon@gmail.com> writes:
> > 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.
That's good news.
The next question is the horrible one: does nouveau actually work* yet?
I had to switch back to nvidia proprietary as mouveau had every imaginable
feature I want (especially how to deal with two monitors in a sane way) and
the features functioned correctly, excep that the whole package did not work.
*work: By this I mean work to be synonymous with "perform at adequate speed".
500ms lag on getting a 2D desktop to do something is not defined as "perform"
The engineer in me says this is really just a matter of finding the correct 4
bits to flip in the right register at the right time, so I have high hope for
nouveau.
--
alan dot mckinnon at gmail dot com
05-20-2010, 11:06 PM
Grant
nouveau-drm compile failure
>> 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?