Re: How to blacklist the nouveau driver on FreeBSD....

I've fixed some errors found in the tutorial that I wrote,this :

https://www.reddit.com/r/freebsd/comments/13qfz3t/comment/jlncmxh/?context=3

adding these command lines :


cp -r /compat/ubuntu/usr/lib/x86_64-linux-gnu /lib

cp -r /compat/ubuntu/etc/alternatives /etc

cp -r /compat/ubuntu/usr/lib/x86_64-linux-gnu /usr/lib


and boom. The error is changed. Now I think that we are getting closer to
the real error to fix :

https://pastebin.ubuntu.com/p/BSGYsWH2Hf/

The real error now is : CUDA cuInit: Unknown error.

This seems to be a more interesting error to talk about.

On Thu, May 25, 2023 at 9:31 PM Mario Marietto <marietto2008@gmail.com>
wrote:

> 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.
>


-- 
Mario.