On Tue, 1 Sep 2020 at 18:59, Ilia Mirkin <imirkin at alum.mit.edu> wrote:> On Tue, Sep 1, 2020 at 9:10 AM Analabha Roy <hariseldon99 at gmail.com> > wrote: > > Any suggestions on how to trace the config issues? Do I have to debug > the va_openDriver() function? > > My guess, without reading any code, is that DRI_PRIME isn't doing what > you want it to, and the nouveau driver is being handed an intel > device. This does not work well. Fixing this will require tracing > through the va winsys code which to figure out how it invokes the > loader. > > > https://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/frontends/va/context.c#n111 > > For the DRM/rendernodes "platform", it will just take whatever fd it > is given. vainfo appears to give it a fixed device: > > > https://github.com/intel/libva-utils/blob/master/common/va_display_drm.c#L39 > > However it looks like you can pass in --device /dev/dri/renderD129 or > whatever the right one is, which should pass in the right render node, > as seen here: > > https://github.com/intel/libva-utils/blob/master/common/va_display.c#L80 > > Note that I've never tried this, just did a few google searches to > find this stuff. > >Brilliant googling. get_drm_device_name() does seem to do a crude argparse of "--device" So I ran $ DRI_PRIME=1 LIBVA_DRIVER_NAME=nouveau vainfo --device /dev/dri/renderD128 *vainfo: unrecognized option '--device'*Show information from VA-API driver Usage: vainfo --help --help print this message Usage: vainfo [options] Display options: --display display | help Show information for the specified display, or the available display list * --device device Set device name, only available under drm display* What does this mean? Note that I also ran $ nm -Dn -o /usr/lib/x86_64-linux-gnu/libva*|grep get_drm_device_name Didn't get anything... Cheers,> > -ilia >-- Analabha Roy Assistant Professor Department of Physics <http://www.buruniv.ac.in/academics/department/physics> The University of Burdwan <http://www.buruniv.ac.in/> Golapbag Campus, Barddhaman 713104 West Bengal, India Emails: daneel at utexas.edu, aroy at phys.buruniv.ac.in, hariseldon99 at gmail.com Webpage: http://www.ph.utexas.edu/~daneel/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20200901/9bf947ab/attachment.htm>
Hi, Try: DRI_PRIME=1 LIBVA_DRIVER_NAME=nouveau vainfo --display drm --device /dev/dri/renderD129 Also try with and without the --device option, the important one is --display drm Cheers Julien On Tue, Sep 1, 2020 at 10:49 AM Analabha Roy <hariseldon99 at gmail.com> wrote:> > > On Tue, 1 Sep 2020 at 18:59, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > >> On Tue, Sep 1, 2020 at 9:10 AM Analabha Roy <hariseldon99 at gmail.com> >> wrote: >> > Any suggestions on how to trace the config issues? Do I have to debug >> the va_openDriver() function? >> >> My guess, without reading any code, is that DRI_PRIME isn't doing what >> you want it to, and the nouveau driver is being handed an intel >> device. This does not work well. Fixing this will require tracing >> through the va winsys code which to figure out how it invokes the >> loader. >> >> >> https://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/frontends/va/context.c#n111 >> >> For the DRM/rendernodes "platform", it will just take whatever fd it >> is given. vainfo appears to give it a fixed device: >> >> >> https://github.com/intel/libva-utils/blob/master/common/va_display_drm.c#L39 >> >> However it looks like you can pass in --device /dev/dri/renderD129 or >> whatever the right one is, which should pass in the right render node, >> as seen here: >> >> https://github.com/intel/libva-utils/blob/master/common/va_display.c#L80 >> >> Note that I've never tried this, just did a few google searches to >> find this stuff. >> >> > Brilliant googling. get_drm_device_name() does seem to do a crude argparse > of "--device" > > So I ran > > $ DRI_PRIME=1 LIBVA_DRIVER_NAME=nouveau vainfo --device /dev/dri/renderD128 > > *vainfo: unrecognized option '--device'*Show information from VA-API > driver > Usage: vainfo --help > --help print this message > > Usage: vainfo [options] > Display options: > --display display | help Show information for the > specified display, or the available display list > > * --device device Set device name, only available > under drm display* > > > What does this mean? > > Note that I also ran > > > $ nm -Dn -o /usr/lib/x86_64-linux-gnu/libva*|grep get_drm_device_name > > Didn't get anything... > > Cheers, >> >> -ilia >> > > > -- > Analabha Roy > Assistant Professor > Department of Physics > <http://www.buruniv.ac.in/academics/department/physics> > The University of Burdwan <http://www.buruniv.ac.in/> > Golapbag Campus, Barddhaman 713104 > West Bengal, India > Emails: daneel at utexas.edu, aroy at phys.buruniv.ac.in, hariseldon99 at gmail.com > Webpage: http://www.ph.utexas.edu/~daneel/ > _______________________________________________ > Nouveau mailing list > Nouveau at lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/nouveau >-------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20200901/1d5d369a/attachment-0001.htm>
On Tue, Sep 1, 2020, 23:28 Julien Isorce <julien.isorce at gmail.com> wrote:> Hi, > > Try: DRI_PRIME=1 LIBVA_DRIVER_NAME=nouveau vainfo --display drm --device > /dev/dri/renderD129 > > Also try with and without the --device option, the important one is > --display drm >Nada, and nada. Exact same error as before, both cases. waah!> Cheers > Julien > > On Tue, Sep 1, 2020 at 10:49 AM Analabha Roy <hariseldon99 at gmail.com> > wrote: > >> >> >> On Tue, 1 Sep 2020 at 18:59, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >> >>> On Tue, Sep 1, 2020 at 9:10 AM Analabha Roy <hariseldon99 at gmail.com> >>> wrote: >>> > Any suggestions on how to trace the config issues? Do I have to debug >>> the va_openDriver() function? >>> >>> My guess, without reading any code, is that DRI_PRIME isn't doing what >>> you want it to, and the nouveau driver is being handed an intel >>> device. This does not work well. Fixing this will require tracing >>> through the va winsys code which to figure out how it invokes the >>> loader. >>> >>> >>> https://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/frontends/va/context.c#n111 >>> >>> For the DRM/rendernodes "platform", it will just take whatever fd it >>> is given. vainfo appears to give it a fixed device: >>> >>> >>> https://github.com/intel/libva-utils/blob/master/common/va_display_drm.c#L39 >>> >>> However it looks like you can pass in --device /dev/dri/renderD129 or >>> whatever the right one is, which should pass in the right render node, >>> as seen here: >>> >>> https://github.com/intel/libva-utils/blob/master/common/va_display.c#L80 >>> >>> Note that I've never tried this, just did a few google searches to >>> find this stuff. >>> >>> >> Brilliant googling. get_drm_device_name() does seem to do a crude >> argparse of "--device" >> >> So I ran >> >> $ DRI_PRIME=1 LIBVA_DRIVER_NAME=nouveau vainfo --device >> /dev/dri/renderD128 >> >> *vainfo: unrecognized option '--device'*Show information from VA-API >> driver >> Usage: vainfo --help >> --help print this message >> >> Usage: vainfo [options] >> Display options: >> --display display | help Show information for the >> specified display, or the available display list >> >> * --device device Set device name, only available >> under drm display* >> >> >> What does this mean? >> >> Note that I also ran >> >> >> $ nm -Dn -o /usr/lib/x86_64-linux-gnu/libva*|grep get_drm_device_name >> >> Didn't get anything... >> >> Cheers, >>> >>> -ilia >>> >> >> >> -- >> Analabha Roy >> Assistant Professor >> Department of Physics >> <http://www.buruniv.ac.in/academics/department/physics> >> The University of Burdwan <http://www.buruniv.ac.in/> >> Golapbag Campus, Barddhaman 713104 >> West Bengal, India >> Emails: daneel at utexas.edu, aroy at phys.buruniv.ac.in, >> hariseldon99 at gmail.com >> Webpage: http://www.ph.utexas.edu/~daneel/ >> _______________________________________________ >> Nouveau mailing list >> Nouveau at lists.freedesktop.org >> https://lists.freedesktop.org/mailman/listinfo/nouveau >> >-------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20200902/af42fb29/attachment.htm>