[Nouveau] Nvidia GK106GLM (Quadro K2100M) with Nouveau

[Nouveau] Nvidia GK106GLM (Quadro K2100M) with Nouveau

[Martin Knoblauch]

[-- Attachment #1: Type: text/plain, Size: 471 bytes --]

Hi,

 for years I have been running my DELL M4800 Laptop under Linux with the
proprietary drivers from NV. Finally I am kind of sick of recompiling those
drivers every time I upgrade the Kernel.

So, my question is: is there any chance to operate a GK106GLM using
nouveau.ko?

Sorry if this has been asked before.

Cheers
Martin
-- 
------------------------------------------------------
Martin Knoblauch
email: k n o b i AT knobisoft DOT de
www: http://www.knobisoft.de

[-- Attachment #2: Type: text/html, Size: 801 bytes --]

Re: [Nouveau] Nvidia GK106GLM (Quadro K2100M) with Nouveau

[Ilia Mirkin]

Hi Martin,

Depends what your expectations are. Nouveau is missing a number of
features of the blob, the most important of which is probably
stability. Whether you run into instability or not depends a lot on
the software that you use, so you'll just have to find out for
yourself if it works well for you or not. Personally, I have
multi-month uptimes with it. But others struggle to stay up for an
hour.

With GK106, you should have manual reclocking, which should enable you
to achieve ~50-80% of blob performance, if that's a concern for you.
You won't get Vulkan nor H.264 hardware encoding.

Cheers,

  -ilia

On Mon, Mar 14, 2022 at 11:55 AM Martin Knoblauch <knobi@knobisoft.de> wrote:
>
> Hi,
>
>  for years I have been running my DELL M4800 Laptop under Linux with the proprietary drivers from NV. Finally I am kind of sick of recompiling those drivers every time I upgrade the Kernel.
>
> So, my question is: is there any chance to operate a GK106GLM using nouveau.ko?
>
> Sorry if this has been asked before.
>
> Cheers
> Martin
> --
> ------------------------------------------------------
> Martin Knoblauch
> email: k n o b i AT knobisoft DOT de
> www: http://www.knobisoft.de

Re: [Nouveau] Nvidia GK106GLM (Quadro K2100M) with Nouveau

[Martin Knoblauch]

On Mon, Mar 14, 2022 at 7:45 PM Ilia Mirkin <imirkin@alum.mit.edu> wrote:
>
> Hi Martin,
>
> Depends what your expectations are. Nouveau is missing a number of
> features of the blob, the most important of which is probably
> stability. Whether you run into instability or not depends a lot on
> the software that you use, so you'll just have to find out for
> yourself if it works well for you or not. Personally, I have
> multi-month uptimes with it. But others struggle to stay up for an
> hour.
>
> With GK106, you should have manual reclocking, which should enable you
> to achieve ~50-80% of blob performance, if that's a concern for you.
> You won't get Vulkan nor H.264 hardware encoding.
>
> Cheers,
>
>   -ilia
>
Hi Ilia,

 most of my expectations would be met, if I were able to get a decent
resolution from the GK106. As it is the card is not recognized, and it
falls back to VESA with 1280x1024 which is pathetic. I have not much
need or expectation on speed.

Cheers
Martin

> On Mon, Mar 14, 2022 at 11:55 AM Martin Knoblauch <knobi@knobisoft.de> wrote:
> >
> > Hi,
> >
> >  for years I have been running my DELL M4800 Laptop under Linux with the proprietary drivers from NV. Finally I am kind of sick of recompiling those drivers every time I upgrade the Kernel.
> >
> > So, my question is: is there any chance to operate a GK106GLM using nouveau.ko?
> >
> > Sorry if this has been asked before.
> >
> > Cheers
> > Martin
> > --
> > ------------------------------------------------------
> > Martin Knoblauch
> > email: k n o b i AT knobisoft DOT de
> > www: http://www.knobisoft.de



-- 
------------------------------------------------------
Martin Knoblauch
email: k n o b i AT knobisoft DOT de
www: http://www.knobisoft.de

Re: [Nouveau] Nvidia GK106GLM (Quadro K2100M) with Nouveau

[Ilia Mirkin]

On Mon, Mar 14, 2022 at 5:30 PM Martin Knoblauch <knobi@knobisoft.de> wrote:
>
> On Mon, Mar 14, 2022 at 7:45 PM Ilia Mirkin <imirkin@alum.mit.edu> wrote:
> >
> > Hi Martin,
> >
> > Depends what your expectations are. Nouveau is missing a number of
> > features of the blob, the most important of which is probably
> > stability. Whether you run into instability or not depends a lot on
> > the software that you use, so you'll just have to find out for
> > yourself if it works well for you or not. Personally, I have
> > multi-month uptimes with it. But others struggle to stay up for an
> > hour.
> >
> > With GK106, you should have manual reclocking, which should enable you
> > to achieve ~50-80% of blob performance, if that's a concern for you.
> > You won't get Vulkan nor H.264 hardware encoding.
> >
> > Cheers,
> >
> >   -ilia
> >
> Hi Ilia,
>
>  most of my expectations would be met, if I were able to get a decent
> resolution from the GK106. As it is the card is not recognized, and it
> falls back to VESA with 1280x1024 which is pathetic. I have not much
> need or expectation on speed.

That's not normal. Please post logs. Perhaps you have nouveau
blacklisted or something like that? Nouveau should definitely
recognize your card.

  -ilia

Re: [Nouveau] Nvidia GK106GLM (Quadro K2100M) with Nouveau

[Martin Knoblauch]

On Mon, Mar 14, 2022 at 10:42 PM Ilia Mirkin <imirkin@alum.mit.edu> wrote:
>
> On Mon, Mar 14, 2022 at 5:30 PM Martin Knoblauch <knobi@knobisoft.de> wrote:
> >
> > On Mon, Mar 14, 2022 at 7:45 PM Ilia Mirkin <imirkin@alum.mit.edu> wrote:
> > >
> > > Hi Martin,
> > >
> > > Depends what your expectations are. Nouveau is missing a number of
> > > features of the blob, the most important of which is probably
> > > stability. Whether you run into instability or not depends a lot on
> > > the software that you use, so you'll just have to find out for
> > > yourself if it works well for you or not. Personally, I have
> > > multi-month uptimes with it. But others struggle to stay up for an
> > > hour.
> > >
> > > With GK106, you should have manual reclocking, which should enable you
> > > to achieve ~50-80% of blob performance, if that's a concern for you.
> > > You won't get Vulkan nor H.264 hardware encoding.
> > >
> > > Cheers,
> > >
> > >   -ilia
> > >
> > Hi Ilia,
> >
> >  most of my expectations would be met, if I were able to get a decent
> > resolution from the GK106. As it is the card is not recognized, and it
> > falls back to VESA with 1280x1024 which is pathetic. I have not much
> > need or expectation on speed.
>
> That's not normal. Please post logs. Perhaps you have nouveau
> blacklisted or something like that? Nouveau should definitely
> recognize your card.
>
>   -ilia
Hi Ilia,

 thanks for providing the correct clue: "blacklisted". I had removed
one blacklist command from /etc/modprobe.d, but the proprietary
installer had left another at /usr/lib/modprobe.d. Kicked that out and
now I have 1920x1080 and all my stuff is working fine :-)

Btw card is recognized as "NVIDIA NVE6". Does that make sense?

Cheers
Martin

Re: [Nouveau] Nvidia GK106GLM (Quadro K2100M) with Nouveau

[Martin Knoblauch]

On Tue, Mar 15, 2022 at 10:55 AM Martin Knoblauch <knobi@knobisoft.de> wrote:
>
> On Mon, Mar 14, 2022 at 10:42 PM Ilia Mirkin <imirkin@alum.mit.edu> wrote:
> >
> > On Mon, Mar 14, 2022 at 5:30 PM Martin Knoblauch <knobi@knobisoft.de> wrote:
> > >
> > > On Mon, Mar 14, 2022 at 7:45 PM Ilia Mirkin <imirkin@alum.mit.edu> wrote:
> > > >
> > > > Hi Martin,
> > > >
> > > > Depends what your expectations are. Nouveau is missing a number of
> > > > features of the blob, the most important of which is probably
> > > > stability. Whether you run into instability or not depends a lot on
> > > > the software that you use, so you'll just have to find out for
> > > > yourself if it works well for you or not. Personally, I have
> > > > multi-month uptimes with it. But others struggle to stay up for an
> > > > hour.
> > > >
> > > > With GK106, you should have manual reclocking, which should enable you
> > > > to achieve ~50-80% of blob performance, if that's a concern for you.
> > > > You won't get Vulkan nor H.264 hardware encoding.
> > > >
> > > > Cheers,
> > > >
> > > >   -ilia
> > > >
> > > Hi Ilia,
> > >
> > >  most of my expectations would be met, if I were able to get a decent
> > > resolution from the GK106. As it is the card is not recognized, and it
> > > falls back to VESA with 1280x1024 which is pathetic. I have not much
> > > need or expectation on speed.
> >
> > That's not normal. Please post logs. Perhaps you have nouveau
> > blacklisted or something like that? Nouveau should definitely
> > recognize your card.
> >
> >   -ilia
> Hi Ilia,
>
>  thanks for providing the correct clue: "blacklisted". I had removed
> one blacklist command from /etc/modprobe.d, but the proprietary
> installer had left another at /usr/lib/modprobe.d. Kicked that out and
> now I have 1920x1080 and all my stuff is working fine :-)
>
> Btw card is recognized as "NVIDIA NVE6". Does that make sense?
>
> Cheers
> Martin

Just for completeness, here the kernel messages with the exception of
the last four line it looks fine to me:
L2XQJL32:/etc/X11 # dmesg | egrep -i "nouv|drm"
[    0.622266] ata1.00: supports DRM functions and may not be fully accessible
[    0.626716] ata1.00: supports DRM functions and may not be fully accessible
[    2.449847] ACPI: bus type drm_connector registered
[    2.503983] fb0: switching to nouveau from VESA VGA
[    2.504110] nouveau 0000:01:00.0: vgaarb: deactivate vga console
[    2.504203] nouveau 0000:01:00.0: NVIDIA GK106 (0e63c0a1)
[    2.581231] nouveau 0000:01:00.0: bios: version 80.06.7d.00.06
[    2.581548] nouveau 0000:01:00.0: mxm: BIOS version 3.0
[    2.582662] nouveau 0000:01:00.0: fb: 2048 MiB GDDR5
[    2.649210] nouveau 0000:01:00.0: DRM: VRAM: 2048 MiB
[    2.649213] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[    2.649215] nouveau 0000:01:00.0: DRM: TMDS table version 2.0
[    2.649216] nouveau 0000:01:00.0: DRM: DCB version 4.0
[    2.649217] nouveau 0000:01:00.0: DRM: DCB outp 00: 01000f13 00010034
[    2.649218] nouveau 0000:01:00.0: DRM: DCB outp 03: 08015fd6 0f420020
[    2.649219] nouveau 0000:01:00.0: DRM: DCB outp 04: 08015f92 00020020
[    2.649220] nouveau 0000:01:00.0: DRM: DCB outp 05: 08014fc6 0f420010
[    2.649221] nouveau 0000:01:00.0: DRM: DCB outp 06: 08014f82 00020010
[    2.649222] nouveau 0000:01:00.0: DRM: DCB outp 10: 02027fa6 0f420010
[    2.649223] nouveau 0000:01:00.0: DRM: DCB outp 11: 02027f62 00020010
[    2.649224] nouveau 0000:01:00.0: DRM: DCB outp 13: 02049f00 00000000
[    2.649225] nouveau 0000:01:00.0: DRM: DCB conn 00: 00000040
[    2.649226] nouveau 0000:01:00.0: DRM: DCB conn 04: 01000446
[    2.649227] nouveau 0000:01:00.0: DRM: DCB conn 05: 02000546
[    2.649227] nouveau 0000:01:00.0: DRM: DCB conn 07: 00010746
[    2.649228] nouveau 0000:01:00.0: DRM: DCB conn 08: 00020847
[    2.649229] nouveau 0000:01:00.0: DRM: DCB conn 09: 00000900
[    2.650904] nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
[    3.094131] nouveau 0000:01:00.0: DRM: allocated 1920x1080 fb:
0xa0000, bo 00000000f4ade0b2
[    3.094272] fbcon: nouveaudrmfb (fb0) is primary device
[    3.870574] nouveau 0000:01:00.0: [drm] fb0: nouveaudrmfb frame buffer device
[    3.889230] [drm] Initialized nouveau 1.3.1 20120801 for
0000:01:00.0 on minor 0
[    4.568900] systemd[1]: Starting Load Kernel Module drm...
[    4.584059] systemd[1]: modprobe@drm.service: Deactivated successfully.
[    4.584210] systemd[1]: Finished Load Kernel Module drm.
[    5.158821] snd_hda_intel 0000:01:00.1: bound 0000:01:00.0 (ops
nv50_audio_component_bind_ops [nouveau])
[    9.120392] nouveau 0000:01:00.0: Direct firmware load for
nouveau/nve6_fuc084 failed with error -2
[    9.120404] nouveau 0000:01:00.0: Direct firmware load for
nouveau/nve6_fuc084d failed with error -2
[    9.120405] nouveau 0000:01:00.0: msvld: unable to load firmware data
[    9.120409] nouveau 0000:01:00.0: msvld: init failed, -19

Martin

Re: [Nouveau] Nvidia GK106GLM (Quadro K2100M) with Nouveau

[Ilia Mirkin]

On Tue, Mar 15, 2022 at 6:10 AM Martin Knoblauch <knobi@knobisoft.de> wrote:
>
> On Tue, Mar 15, 2022 at 10:55 AM Martin Knoblauch <knobi@knobisoft.de> wrote:
> >
> > On Mon, Mar 14, 2022 at 10:42 PM Ilia Mirkin <imirkin@alum.mit.edu> wrote:
> > >
> > > On Mon, Mar 14, 2022 at 5:30 PM Martin Knoblauch <knobi@knobisoft.de> wrote:
> > > >
> > > > On Mon, Mar 14, 2022 at 7:45 PM Ilia Mirkin <imirkin@alum.mit.edu> wrote:
> > > > >
> > > > > Hi Martin,
> > > > >
> > > > > Depends what your expectations are. Nouveau is missing a number of
> > > > > features of the blob, the most important of which is probably
> > > > > stability. Whether you run into instability or not depends a lot on
> > > > > the software that you use, so you'll just have to find out for
> > > > > yourself if it works well for you or not. Personally, I have
> > > > > multi-month uptimes with it. But others struggle to stay up for an
> > > > > hour.
> > > > >
> > > > > With GK106, you should have manual reclocking, which should enable you
> > > > > to achieve ~50-80% of blob performance, if that's a concern for you.
> > > > > You won't get Vulkan nor H.264 hardware encoding.
> > > > >
> > > > > Cheers,
> > > > >
> > > > >   -ilia
> > > > >
> > > > Hi Ilia,
> > > >
> > > >  most of my expectations would be met, if I were able to get a decent
> > > > resolution from the GK106. As it is the card is not recognized, and it
> > > > falls back to VESA with 1280x1024 which is pathetic. I have not much
> > > > need or expectation on speed.
> > >
> > > That's not normal. Please post logs. Perhaps you have nouveau
> > > blacklisted or something like that? Nouveau should definitely
> > > recognize your card.
> > >
> > >   -ilia
> > Hi Ilia,
> >
> >  thanks for providing the correct clue: "blacklisted". I had removed
> > one blacklist command from /etc/modprobe.d, but the proprietary
> > installer had left another at /usr/lib/modprobe.d. Kicked that out and
> > now I have 1920x1080 and all my stuff is working fine :-)
> >
> > Btw card is recognized as "NVIDIA NVE6". Does that make sense?
> >
> > Cheers
> > Martin
>
> Just for completeness, here the kernel messages with the exception of
> the last four line it looks fine to me:
> L2XQJL32:/etc/X11 # dmesg | egrep -i "nouv|drm"
> [    0.622266] ata1.00: supports DRM functions and may not be fully accessible
> [    0.626716] ata1.00: supports DRM functions and may not be fully accessible
> [    2.449847] ACPI: bus type drm_connector registered
> [    2.503983] fb0: switching to nouveau from VESA VGA
> [    2.504110] nouveau 0000:01:00.0: vgaarb: deactivate vga console
> [    2.504203] nouveau 0000:01:00.0: NVIDIA GK106 (0e63c0a1)
> [    2.581231] nouveau 0000:01:00.0: bios: version 80.06.7d.00.06
> [    2.581548] nouveau 0000:01:00.0: mxm: BIOS version 3.0
> [    2.582662] nouveau 0000:01:00.0: fb: 2048 MiB GDDR5
> [    2.649210] nouveau 0000:01:00.0: DRM: VRAM: 2048 MiB
> [    2.649213] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
> [    2.649215] nouveau 0000:01:00.0: DRM: TMDS table version 2.0
> [    2.649216] nouveau 0000:01:00.0: DRM: DCB version 4.0
> [    2.649217] nouveau 0000:01:00.0: DRM: DCB outp 00: 01000f13 00010034
> [    2.649218] nouveau 0000:01:00.0: DRM: DCB outp 03: 08015fd6 0f420020
> [    2.649219] nouveau 0000:01:00.0: DRM: DCB outp 04: 08015f92 00020020
> [    2.649220] nouveau 0000:01:00.0: DRM: DCB outp 05: 08014fc6 0f420010
> [    2.649221] nouveau 0000:01:00.0: DRM: DCB outp 06: 08014f82 00020010
> [    2.649222] nouveau 0000:01:00.0: DRM: DCB outp 10: 02027fa6 0f420010
> [    2.649223] nouveau 0000:01:00.0: DRM: DCB outp 11: 02027f62 00020010
> [    2.649224] nouveau 0000:01:00.0: DRM: DCB outp 13: 02049f00 00000000
> [    2.649225] nouveau 0000:01:00.0: DRM: DCB conn 00: 00000040
> [    2.649226] nouveau 0000:01:00.0: DRM: DCB conn 04: 01000446
> [    2.649227] nouveau 0000:01:00.0: DRM: DCB conn 05: 02000546
> [    2.649227] nouveau 0000:01:00.0: DRM: DCB conn 07: 00010746
> [    2.649228] nouveau 0000:01:00.0: DRM: DCB conn 08: 00020847
> [    2.649229] nouveau 0000:01:00.0: DRM: DCB conn 09: 00000900
> [    2.650904] nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
> [    3.094131] nouveau 0000:01:00.0: DRM: allocated 1920x1080 fb:
> 0xa0000, bo 00000000f4ade0b2
> [    3.094272] fbcon: nouveaudrmfb (fb0) is primary device
> [    3.870574] nouveau 0000:01:00.0: [drm] fb0: nouveaudrmfb frame buffer device
> [    3.889230] [drm] Initialized nouveau 1.3.1 20120801 for
> 0000:01:00.0 on minor 0
> [    4.568900] systemd[1]: Starting Load Kernel Module drm...
> [    4.584059] systemd[1]: modprobe@drm.service: Deactivated successfully.
> [    4.584210] systemd[1]: Finished Load Kernel Module drm.
> [    5.158821] snd_hda_intel 0000:01:00.1: bound 0000:01:00.0 (ops
> nv50_audio_component_bind_ops [nouveau])
> [    9.120392] nouveau 0000:01:00.0: Direct firmware load for
> nouveau/nve6_fuc084 failed with error -2
> [    9.120404] nouveau 0000:01:00.0: Direct firmware load for
> nouveau/nve6_fuc084d failed with error -2
> [    9.120405] nouveau 0000:01:00.0: msvld: unable to load firmware data
> [    9.120409] nouveau 0000:01:00.0: msvld: init failed, -19

Not a real problem. If you want video decoding acceleration (h264
being the more useful format supported), follow the steps at
https://nouveau.freedesktop.org/VideoAcceleration.html#firmware .

Various Kepler boards can run into hangs which will come out as ctxsw
timeouts. If that becomes a thing, you can replace the nouveau ctxsw
fw with the nvidia one by running the firmware steps above (if you use
the 325.15 firmware) and adding nouveau.config=NvGrUseFW=1 to the boot
line. This has helped a bunch of people with stability.

If you want to switch performance levels, you can do so via
/sys/kernel/debug/dri/0/pstate (cat the file for the list of allowed
levels, and echo the level back in to switch to it). This is mostly
reliable, but we haven't added logic to do it in an automatic way (it
can also lead to a brief flicker).

Good luck.

Cheers,

  -ilia