Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 25 May 2023 21:31:13 +0200
From:      Mario Marietto <marietto2008@gmail.com>
To:        Theron <theron.tarigo@gmail.com>
Cc:        freebsd-hackers <freebsd-hackers@freebsd.org>
Subject:   Re: How to blacklist the nouveau driver on FreeBSD....
Message-ID:  <CA%2B1FSijWw5nAUHU9LpbzdBMjy6RAkTNndwSCeFAL33KR5GLmKw@mail.gmail.com>
In-Reply-To: <CA%2B1FSijh33rXXihOyzZp5wO=HEEwpHF0UT-bG1FjEs59=GhnyQ@mail.gmail.com>
References:  <CA%2B1FSii7cX_pdvi_mioAist1tps-mOCyRPw-Gy-mZ-u-8YH1pQ@mail.gmail.com> <46f1653a-89ba-6df3-6e3a-bd4a6c692be1@gmail.com> <CA%2B1FSihEwaq2jDsrPrd-65-44gMB_6YLhQBFw3AtMBp7ebKusQ@mail.gmail.com> <CA%2B1FSijh33rXXihOyzZp5wO=HEEwpHF0UT-bG1FjEs59=GhnyQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

[-- Attachment #1 --]
Hello.

I've asked for some clarifications on the Blender forum about the reason
why a part of the nouveau userland is called within the linuxulator,instead
of the nVidia one. You can read here :

https://devtalk.blender.org/t/why-blender-cycles-is-not-able-to-detect-my-gpu-s-and-cuda-within-the-ubuntu-linuxulator/27777


this is what he said :


I can’t give you full help with this, but I will share some information
based on what I can gather from this post and resources online.

   -

   Linuxulator appears to be some kind of compatibility layer. It’s not
   guaranteed to work with all applications, and CUDA is likely to be one of
   the application types it will have issues with. Maybe try verifying that
   applications that use the GPU work, then CUDA applications, then look into
   getting Cycles rendering working with CUDA. This may not be a Blender
   issue, but a Linuxulator issue.
   -

   Depending on how you installed your GPU drivers on “Linux”, you might
   not have all the packages required to run CUDA applications. For example,
   on some Linux distributions I had to install packages like libcuda1 and
   libnvoptix1 to use CUDA and OptiX on Linux.
   -

   As you pointed out, the error libGL error: failed to load driver: nouveau
   suggests Blender is trying to load the nouveau driver. Typically when
   installing the Nvidia proprietary driver, the loading of the nouveau
   drivers gets disabled. Maybe the Nvidia GPU drivers weren’t installed
   properly? Or do you need to disable nouveau manually? Or is this just some
   issue with the Linuxulator?
   -

   You also have errors related to “opening a display” (opening the Blender
   GUI). This could be related to the GPU driver issue discussed before, or
   maybe you need to do a bit of extra setup to get GUI applications working
   in Linuxulator. Such as setting up a desktop environment within your
   Linuxulator?
   It also might be easier to test Blender with CUDA rendering if you
   started with command line rendering rather than GUI render.
   -

   Command Line Rendering — Blender Manual 3
   <https://docs.blender.org/manual/en/latest/advanced/command_line/render.html>;

Sorry if I’m unable to help much with this.

On Thu, May 25, 2023 at 11:47 AM Mario Marietto <marietto2008@gmail.com>
wrote:

> Can you figure out a method to do what I want to do ? If we are able to
> "connect" the nVidia driver to the CG / graphic tool instead of the nouveau
> one,a lot of cool features will be unfrozen. For example we could try to
> run Unreal Engine 5 within the linuxulator,Davinci Resolve,Maya 3d,a lot of
> cool stuff will use the nvidia driver and it will work great.
>
> On Thu, May 25, 2023 at 11:10 AM Mario Marietto <marietto2008@gmail.com>
> wrote:
>
>> Smplayer behaves the same as blender. I think this is a general behavior.
>> Check below what happens when I run it within the linuxulator :
>>
>> root@marietto:/mnt/zroot2/zroot2 # chroot /compat/ubuntulunar /bin/bash
>>
>> root@marietto:/# smplayer
>>
>> QStandardPaths: error creating runtime directory '/var/run/user/1001' (No
>> such file or directory)
>> This is SMPlayer v. 22.7.0 (revision 10091) running on Linux
>> libGL error: glx: failed to create dri2 screen
>> *libGL error: failed to load driver: nouveau*
>>
>>
>>
>> On Thu, May 25, 2023 at 2:56 AM Theron <theron.tarigo@gmail.com> wrote:
>>
>>> On 5/24/23 04:43, Mario Marietto wrote:
>>> > since the nouveau driver can't be blacklisted within the Linuxulator
>>> > because it's impossible to run "sudo update-initramfs -u" inside of
>>> > it. For this reason,I would ask if in your opinion the nouveau driver
>>> > can be blacklisted directly in FreeBSD or in some other way. Thanks.
>>> >
>>> FreeBSD does not contain the nouveau kernel module so there is nothing
>>> to blacklist.
>>>
>>> > He says that he created a Python script for updating Nvidia drivers on
>>> > CentOS 7 and Ubuntu. That's nice,but it can't work. Why ? please give
>>> > a look to an old post created by me some time ago and you will see :
>>> >
>>> >
>>> https://www.reddit.com/r/freebsd/comments/11431bi/how_to_blacklist_the_nouveau_driver_within_the/
>>> >
>>> These libGL errors are from Mesa libGL, which is trying to use the
>>> userspace part of nouveau (which is part of the Mesa project),
>>> presumably based on Nvidia GPU's PCI ID being known to Mesa, despite
>>> there being no nouveau kernel interface available.
>>>
>>> Since you are trying to use Nvidia's binary driver (the only one which
>>> works on FreeBSD), Blender should have never loaded Mesa's libGL in the
>>> first place - there is most likely a configuration problem here with
>>> libglvnd, the component responsible for choosing the correct libGL
>>> implementation.
>>>
>>> When Blender fails to detect CUDA this has nothing to do with libGL and
>>> absolutely nothing to do with nouveau - have you found any other CUDA
>>> program to work in linux compat?
>>>
>>> Theron
>>>
>>
>>
>> --
>> Mario.
>>
>
>
> --
> Mario.
>


-- 
Mario.

[-- Attachment #2 --]
<div dir="ltr"><div>Hello.</div><div><br></div><div>I&#39;ve asked for some clarifications on the Blender forum about the reason why a part of the nouveau userland is called within the linuxulator,instead of the nVidia one. You can read here :</div><div><br></div><div><a href="https://devtalk.blender.org/t/why-blender-cycles-is-not-able-to-detect-my-gpu-s-and-cuda-within-the-ubuntu-linuxulator/27777">https://devtalk.blender.org/t/why-blender-cycles-is-not-able-to-detect-my-gpu-s-and-cuda-within-the-ubuntu-linuxulator/27777</a></div><div><br></div><div><br></div><div>this is what he said :</div><div> <br></div><div></div><div><div class="gmail-cooked"><p>I can’t give you full help with this, but I will 
share some information based on what I can gather from this post and 
resources online.</p>
<ul><li>
<p>Linuxulator appears to be some kind of compatibility layer. It’s not 
guaranteed to work with all applications, and CUDA is likely to be one 
of the application types it will have issues with. Maybe try verifying 
that applications that use the GPU work, then CUDA applications, then 
look into getting Cycles rendering working with CUDA. This may not be a 
Blender issue, but a Linuxulator issue.</p>
</li><li>
<p>Depending on how you installed your GPU drivers on “Linux”, you might
 not have all the packages required to run CUDA applications. For 
example, on some Linux distributions I had to install packages like <code>libcuda1</code> and <code>libnvoptix1</code> to use CUDA and OptiX on Linux.</p>
</li><li>
<p>As you pointed out, the error <code>libGL error: failed to load driver: nouveau</code>
 suggests Blender is trying to load the nouveau driver. Typically when 
installing the Nvidia proprietary driver, the loading of the nouveau 
drivers gets disabled. Maybe the Nvidia GPU drivers weren’t installed 
properly? Or do you need to disable nouveau manually? Or is this just some 
issue with the Linuxulator?</p>
</li><li>
<p>You also have errors related to “opening a display” (opening the 
Blender GUI). This could be related to the GPU driver issue discussed 
before, or maybe you need to do a bit of extra setup to get GUI 
applications working in Linuxulator. Such as setting up a desktop environment
 within your Linuxulator?<br>
It also might be easier to test Blender with CUDA rendering if you started with command line rendering rather than GUI render. <br></p></li><li><p><a href="https://docs.blender.org/manual/en/latest/advanced/command_line/render.html" class="gmail-inline-onebox" rel="noopener nofollow ugc">Command Line Rendering — Blender Manual <span class="gmail-badge gmail-badge-notification gmail-clicks" title="3 clicks">3</span></a></p>
</li></ul>
<p>Sorry if I’m unable to help much with this.</p></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 25, 2023 at 11:47 AM Mario Marietto &lt;<a href="mailto:marietto2008@gmail.com">marietto2008@gmail.com</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Can you figure out a method to do what I want to do ? If we are able to &quot;connect&quot; the nVidia driver to the CG / graphic tool instead of the nouveau one,a lot of cool features will be unfrozen. For example we could try to run Unreal Engine 5 within the linuxulator,Davinci Resolve,Maya 3d,a lot of cool stuff will use the nvidia driver and it will work great. <br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 25, 2023 at 11:10 AM Mario Marietto &lt;<a href="mailto:marietto2008@gmail.com" target="_blank">marietto2008@gmail.com</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Smplayer behaves the same as blender. I think this is a general behavior. Check below what happens when I run it within the linuxulator :<br></div><div><br></div><div><span style="color:rgb(0,0,0);background-color:rgb(255,255,255);font-family:arial,sans-serif">root@marietto:/mnt/zroot2/zroot2 # chroot /compat/ubuntulunar /bin/bash</span></div><div><span style="font-family:arial,sans-serif"><br>root@marietto:/# smplayer </span></div><div><span style="font-family:arial,sans-serif"><br></span></div><div><span style="font-family:arial,sans-serif">QStandardPaths: error creating runtime directory &#39;/var/run/user/1001&#39; (No such file or directory)
<br>This is SMPlayer v. 22.7.0 (revision 10091) running on Linux
<br>libGL error: glx: failed to create dri2 screen
<br><b>libGL error: failed to load driver: nouveau</b></span><span style="font-family:monospace"><br></span></div><div><span style="font-family:monospace"><br></span></div><div><span style="font-family:monospace"><br></span></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 25, 2023 at 2:56 AM Theron &lt;<a href="mailto:theron.tarigo@gmail.com" target="_blank">theron.tarigo@gmail.com</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 5/24/23 04:43, Mario Marietto wrote:<br>
&gt; since the nouveau driver can&#39;t be blacklisted within the Linuxulator <br>
&gt; because it&#39;s impossible to run &quot;sudo update-initramfs -u&quot; inside of <br>
&gt; it. For this reason,I would ask if in your opinion the nouveau driver <br>
&gt; can be blacklisted directly in FreeBSD or in some other way. Thanks.<br>
&gt;<br>
FreeBSD does not contain the nouveau kernel module so there is nothing <br>
to blacklist.<br>
<br>
&gt; He says that he created a Python script for updating Nvidia drivers on <br>
&gt; CentOS 7 and Ubuntu. That&#39;s nice,but it can&#39;t work. Why ? please give <br>
&gt; a look to an old post created by me some time ago and you will see :<br>
&gt;<br>
&gt; <a href="https://www.reddit.com/r/freebsd/comments/11431bi/how_to_blacklist_the_nouveau_driver_within_the/" rel="noreferrer" target="_blank">https://www.reddit.com/r/freebsd/comments/11431bi/how_to_blacklist_the_nouveau_driver_within_the/</a><br>;
&gt;<br>
These libGL errors are from Mesa libGL, which is trying to use the <br>
userspace part of nouveau (which is part of the Mesa project), <br>
presumably based on Nvidia GPU&#39;s PCI ID being known to Mesa, despite <br>
there being no nouveau kernel interface available.<br>
<br>
Since you are trying to use Nvidia&#39;s binary driver (the only one which <br>
works on FreeBSD), Blender should have never loaded Mesa&#39;s libGL in the <br>
first place - there is most likely a configuration problem here with <br>
libglvnd, the component responsible for choosing the correct libGL <br>
implementation.<br>
<br>
When Blender fails to detect CUDA this has nothing to do with libGL and <br>
absolutely nothing to do with nouveau - have you found any other CUDA <br>
program to work in linux compat?<br>
<br>
Theron<br>
</blockquote></div><br clear="all"><br><span>-- </span><br><div dir="ltr">Mario.<br></div>
</blockquote></div><br clear="all"><br><span>-- </span><br><div dir="ltr">Mario.<br></div>
</blockquote></div><br clear="all"><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature">Mario.<br></div>

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2B1FSijWw5nAUHU9LpbzdBMjy6RAkTNndwSCeFAL33KR5GLmKw>