View previous topic :: View next topic |
Author |
Message |
hjkl Apprentice
Joined: 22 Apr 2021 Posts: 198 Location: Somewhere in Europe
|
|
Back to top |
|
|
CPlusPanda n00b
Joined: 24 Jul 2021 Posts: 1
|
Posted: Sat Jul 24, 2021 12:02 pm Post subject: |
|
|
Same problem here, although on a fresh install instead |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6098 Location: Dallas area
|
Posted: Sat Jul 24, 2021 12:51 pm Post subject: |
|
|
Code: | emerge -pv mesa libdrm |
What is returned _________________ PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
Ionen Developer
Joined: 06 Dec 2018 Posts: 2719
|
Posted: Sat Jul 24, 2021 1:04 pm Post subject: |
|
|
This typically mean it's running in software-only mode without hardware acceleration (nearly unusable last I tried).
Would imply missing drivers or bad settings (such as on mesa, so the above post may be of interest).
Unlike nvidia-drivers, nouveau should technically work as expected assuming set VIDEO_CARDS=nouveau (notably for mesa), and the kernel module is working. Not that nouveau is that great performance-wise (albeit shouldn't be _that_ bad), and mileage may vary depending on the card. |
|
Back to top |
|
|
hjkl Apprentice
Joined: 22 Apr 2021 Posts: 198 Location: Somewhere in Europe
|
Posted: Sat Jul 24, 2021 1:14 pm Post subject: |
|
|
This was the case because nouveau was built in.
It has to be built as module in the kernel. _________________ Having problems compiling since 2021 |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21633
|
Posted: Sat Jul 24, 2021 4:06 pm Post subject: |
|
|
Nouveau built-in should work fine. If changing to a module fixed it, my first guess would be that you need firmware for the card, that the firmware is not available early enough when you use a built-in, but that the firmware is available by the time modules load. If you want to use a built-in driver, you need to build into the kernel the required firmware too. dmesg should tell you what firmware was used. CONFIG_EXTRA_FIRMWARE + CONFIG_EXTRA_FIRMWARE_DIR will let you put the firmware into the kernel. Note that each firmware blob mentioned in dmesg must be mentioned verbatim in CONFIG_EXTRA_FIRMWARE. If extra path qualifiers are used, the kernel will fail to recognize at load time that it has the blob it needs, because the name does not match exactly. |
|
Back to top |
|
|
Ionen Developer
Joined: 06 Dec 2018 Posts: 2719
|
Posted: Sat Jul 24, 2021 4:10 pm Post subject: |
|
|
Hu wrote: | Nouveau built-in should work fine. If changing to a module fixed it, my first guess would be that you need firmware for the card, | That sound unlikely, nouveau doesn't use firmwares (the cards have a builtin firmware). Or at most only optionally for video decoding acceleration and that only works on a few cards (it wouldn't affect wayland).
Not that I see why builtin nouveau wouldn't work, maybe just happened to fix something while changing things around. Maybe it actually was neither builtin nor a module. |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6098 Location: Dallas area
|
Posted: Sat Jul 24, 2021 4:54 pm Post subject: |
|
|
Ionen wrote: | Hu wrote: | Nouveau built-in should work fine. If changing to a module fixed it, my first guess would be that you need firmware for the card, | That sound unlikely, nouveau doesn't use firmwares (the cards have a builtin firmware). Or at most only optionally for video decoding acceleration and that only works on a few cards (it wouldn't affect wayland).
Not that I see why builtin nouveau wouldn't work, maybe just happened to fix something while changing things around. Maybe it actually was neither builtin nor a module. |
Some of the cards do use firmware, depends on model. The firmware isn't distributed the normal way though, it's pulled in by nvidia-firmware.
Having said that, I always used nouveau (when I had nvidia cards installed) as a module. _________________ PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
Ionen Developer
Joined: 06 Dec 2018 Posts: 2719
|
Posted: Sat Jul 24, 2021 5:19 pm Post subject: |
|
|
Anon-E-moose wrote: | Ionen wrote: | [...] Or at most only optionally for video decoding acceleration and that only works on a few cards (it wouldn't affect wayland). | Some of the cards do use firmware, depends on model. The firmware isn't distributed the normal way though, it's pulled in by nvidia-firmware.. |
This is what I was referring to for video decoding acceleration, and it's not actually needed for anything else. |
|
Back to top |
|
|
hjkl Apprentice
Joined: 22 Apr 2021 Posts: 198 Location: Somewhere in Europe
|
Posted: Sat Jul 24, 2021 5:44 pm Post subject: |
|
|
Hu wrote: | Nouveau built-in should work fine. If changing to a module fixed it, my first guess would be that you need firmware for the card, that the firmware is not available early enough when you use a built-in, but that the firmware is available by the time modules load. If you want to use a built-in driver, you need to build into the kernel the required firmware too. dmesg should tell you what firmware was used. CONFIG_EXTRA_FIRMWARE + CONFIG_EXTRA_FIRMWARE_DIR will let you put the firmware into the kernel. Note that each firmware blob mentioned in dmesg must be mentioned verbatim in CONFIG_EXTRA_FIRMWARE. If extra path qualifiers are used, the kernel will fail to recognize at load time that it has the blob it needs, because the name does not match exactly. |
I will try to do that and what I noticed in my dmesg was this:
Code: |
❯ dmesg | grep -i firm
[ 2.972023] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 2.981464] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-7f] only partially covers this bridge
[ 3.204297] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 6.323488] nouveau 0000:08:00.0: pmu: firmware unavailable
|
Should i emerge sys-firmware/nvidia-firmware? I have a GTX 1060 _________________ Having problems compiling since 2021 |
|
Back to top |
|
|
Ionen Developer
Joined: 06 Dec 2018 Posts: 2719
|
Posted: Sat Jul 24, 2021 5:58 pm Post subject: |
|
|
hjkl wrote: | Should i emerge sys-firmware/nvidia-firmware? I have a GTX 1060 | nvidia-firmware package is rather old (based on 340.xx branch drivers which is gone from the tree), doubt you can use that... not that I looked at its extraction script.
Either way, cases where you can use the external nvidia-firmware with nouveau is entries with "EXTFW" in this:
https://nouveau.freedesktop.org/FeatureMatrix.html
And your 1060 falls under "NV130".
I am not aware of nouveau using other firmware blobs, but I'm not the most familiar with it so I could be wrong.
Last edited by Ionen on Sat Jul 24, 2021 6:02 pm; edited 1 time in total |
|
Back to top |
|
|
hjkl Apprentice
Joined: 22 Apr 2021 Posts: 198 Location: Somewhere in Europe
|
Posted: Sat Jul 24, 2021 6:01 pm Post subject: |
|
|
Ionen wrote: | hjkl wrote: | Should i emerge sys-firmware/nvidia-firmware? I have a GTX 1060 | nvidia-firmware package is rather old (based on 340.xx branch drivers which is gone from the tree), doubt you can use that... not that I looked at its extraction script.
Either way, cases where you can use an external firmware with nouveau is entries with "EXTFW" in this:
https://nouveau.freedesktop.org/FeatureMatrix.html
And your 1060 is a "NV130".
I am not aware of nouveau using other firmware blobs, but I'm not the most familiar with it so I could be wrong. |
Looking at that, it does indeed that nothing needs any other firmware blobs .
As far as I know, I'm pretty much stuck with nouveau as module instead of built in. _________________ Having problems compiling since 2021 |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6098 Location: Dallas area
|
Posted: Sat Jul 24, 2021 6:46 pm Post subject: |
|
|
Anon-E-moose wrote: | Code: | emerge -pv mesa libdrm |
What is returned |
along with the above info, what nvidia card do you have? _________________ PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
hjkl Apprentice
Joined: 22 Apr 2021 Posts: 198 Location: Somewhere in Europe
|
Posted: Sat Jul 24, 2021 6:49 pm Post subject: |
|
|
Anon-E-moose wrote: | Anon-E-moose wrote: | Code: | emerge -pv mesa libdrm |
What is returned |
along with the above info, what nvidia card do you have? |
Code: |
❯ emerge -pv mesa libdrm
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] x11-libs/libdrm-2.4.106::gentoo USE="-libkms -valgrind" ABI_X86="32 (64) (-x32)" VIDEO_CARDS="nouveau -amdgpu (-exynos) (-freedreno) -intel (-omap) -radeon (-tegra) (-vc4) (-vivante) -vmware" 0 KiB
[ebuild R ] media-libs/mesa-21.1.4::gentoo USE="X classic dri3 egl gallium gbm gles2 llvm wayland zstd -d3d9 -debug -gles1 -lm-sensors -opencl -osmesa (-selinux) -test -unwind -vaapi -valgrind -vdpau -vulkan -vulkan-overlay -xa -xvmc -zink" ABI_X86="32 (64) (-x32)" VIDEO_CARDS="nouveau (-freedreno) -i915 -i965 -intel -iris (-lima) (-panfrost) -r100 -r200 -r300 -r600 -radeon -radeonsi (-v3d) (-vc4) -virgl (-vivante) -vmware" 0 KiB
Total: 2 packages (2 reinstalls), Size of downloads: 0 KiB
* IMPORTANT: 12 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
|
I have a GTX 1060 _________________ Having problems compiling since 2021 |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6098 Location: Dallas area
|
Posted: Sat Jul 24, 2021 7:18 pm Post subject: |
|
|
Too bad, it's not one of those cards that Nouveau has working for power management (clock speed among other things)
Is it still slow as a module?
If so then the only real alternative is nvidia drivers which should work if running the latest wayland/wlroots/xwayland/etc. _________________ PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
hjkl Apprentice
Joined: 22 Apr 2021 Posts: 198 Location: Somewhere in Europe
|
Posted: Sat Jul 24, 2021 7:36 pm Post subject: |
|
|
Anon-E-moose wrote: | Too bad, it's not one of those cards that Nouveau has working for power management (clock speed among other things)
Is it still slow as a module?
If so then the only real alternative is nvidia drivers which should work if running the latest wayland/wlroots/xwayland/etc. |
It was the other way around.
When it was built in, it was very slow.
As module, it's performance is well, nouveau as it's intended.
Here's the dmesg from it as built in though:
Code: |
[ 3.022234] fb0: switching to nouveaufb from EFI VGA
[ 3.022291] nouveau 0000:08:00.0: vgaarb: deactivate vga console
[ 3.022318] nouveau 0000:08:00.0: NVIDIA GP106 (136000a1)
[ 3.150155] nouveau 0000:08:00.0: bios: version 86.06.63.00.aa
[ 3.150274] nouveau 0000:08:00.0: acr: firmware unavailable
[ 3.150277] nouveau 0000:08:00.0: pmu: firmware unavailable
[ 3.150308] nouveau 0000:08:00.0: gr: firmware unavailable
[ 3.150314] nouveau 0000:08:00.0: sec2: firmware unavailable
[ 3.150622] nouveau 0000:08:00.0: fb: 6144 MiB GDDR5
[ 3.169897] nouveau 0000:08:00.0: fb: VPR locked, but no scrubber binary!
[ 3.177259] nouveau 0000:08:00.0: DRM: VRAM: 6144 MiB
[ 3.177260] nouveau 0000:08:00.0: DRM: GART: 536870912 MiB
[ 3.177262] nouveau 0000:08:00.0: DRM: BIT table 'A' not found
[ 3.177264] nouveau 0000:08:00.0: DRM: BIT table 'L' not found
[ 3.177266] nouveau 0000:08:00.0: DRM: TMDS table version 2.0
[ 3.177267] nouveau 0000:08:00.0: DRM: DCB version 4.1
[ 3.177269] nouveau 0000:08:00.0: DRM: DCB outp 00: 01000f42 04620030
[ 3.177271] nouveau 0000:08:00.0: DRM: DCB outp 01: 04811f96 04600020
[ 3.177273] nouveau 0000:08:00.0: DRM: DCB outp 02: 04011f92 04620020
[ 3.177274] nouveau 0000:08:00.0: DRM: DCB outp 03: 04822f86 04600010
[ 3.177276] nouveau 0000:08:00.0: DRM: DCB outp 04: 04022f82 04620010
[ 3.177277] nouveau 0000:08:00.0: DRM: DCB outp 06: 02033f62 00020010
[ 3.177279] nouveau 0000:08:00.0: DRM: DCB outp 08: 02044f72 00020020
[ 3.177280] nouveau 0000:08:00.0: DRM: DCB conn 00: 00001031
[ 3.177282] nouveau 0000:08:00.0: DRM: DCB conn 01: 02000146
[ 3.177283] nouveau 0000:08:00.0: DRM: DCB conn 02: 01000246
[ 3.177285] nouveau 0000:08:00.0: DRM: DCB conn 03: 00010361
[ 3.177286] nouveau 0000:08:00.0: DRM: DCB conn 04: 00020461
[ 3.177569] nouveau 0000:08:00.0: DRM: failed to create kernel channel, -22
[ 3.177736] nouveau 0000:08:00.0: DRM: MM: using COPY for buffer copies
[ 3.496283] nouveau 0000:08:00.0: DRM: allocated 1920x1080 fb: 0x200000, bo 000000005d1457e6
[ 3.497032] fbcon: nouveaudrmfb (fb0) is primary device
[ 4.076757] nouveau 0000:08:00.0: [drm] fb0: nouveaudrmfb frame buffer device
[ 4.076878] [drm] Initialized nouveau 1.3.1 20120801 for 0000:08:00.0 on minor 0
|
_________________ Having problems compiling since 2021 |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6098 Location: Dallas area
|
Posted: Sat Jul 24, 2021 7:43 pm Post subject: |
|
|
hjkl wrote: | Anon-E-moose wrote: | Too bad, it's not one of those cards that Nouveau has working for power management (clock speed among other things)
Is it still slow as a module?
If so then the only real alternative is nvidia drivers which should work if running the latest wayland/wlroots/xwayland/etc. |
It was the other way around.
When it was built in, it was very slow.
As module, it's performance is well, nouveau as it's intended.
Here's the dmesg from it as built in though: |
What do the messsages look like with it as a module?
The builtin was looking for firmware it didn't find, plus another message about a channel. _________________ PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
hjkl Apprentice
Joined: 22 Apr 2021 Posts: 198 Location: Somewhere in Europe
|
Posted: Sat Jul 24, 2021 7:47 pm Post subject: |
|
|
Anon-E-moose wrote: | hjkl wrote: | Anon-E-moose wrote: | Too bad, it's not one of those cards that Nouveau has working for power management (clock speed among other things)
Is it still slow as a module?
If so then the only real alternative is nvidia drivers which should work if running the latest wayland/wlroots/xwayland/etc. |
It was the other way around.
When it was built in, it was very slow.
As module, it's performance is well, nouveau as it's intended.
Here's the dmesg from it as built in though: |
What do the messsages look like with it as a module?
The builtin was looking for firmware it didn't find, plus another message about a channel. |
Code: |
[ 6.156009] fb0: switching to nouveaufb from EFI VGA
[ 6.156091] nouveau 0000:08:00.0: vgaarb: deactivate vga console
[ 6.156126] nouveau 0000:08:00.0: NVIDIA GP106 (136000a1)
[ 6.281585] nouveau 0000:08:00.0: bios: version 86.06.63.00.aa
[ 6.291252] nouveau 0000:08:00.0: pmu: firmware unavailable
[ 6.298479] nouveau 0000:08:00.0: fb: 6144 MiB GDDR5
[ 6.329863] nouveau 0000:08:00.0: DRM: VRAM: 6144 MiB
[ 6.329863] nouveau 0000:08:00.0: DRM: GART: 536870912 MiB
[ 6.329864] nouveau 0000:08:00.0: DRM: BIT table 'A' not found
[ 6.329865] nouveau 0000:08:00.0: DRM: BIT table 'L' not found
[ 6.329866] nouveau 0000:08:00.0: DRM: TMDS table version 2.0
[ 6.329867] nouveau 0000:08:00.0: DRM: DCB version 4.1
[ 6.329868] nouveau 0000:08:00.0: DRM: DCB outp 00: 01000f42 04620030
[ 6.329868] nouveau 0000:08:00.0: DRM: DCB outp 01: 04811f96 04600020
[ 6.329869] nouveau 0000:08:00.0: DRM: DCB outp 02: 04011f92 04620020
[ 6.329870] nouveau 0000:08:00.0: DRM: DCB outp 03: 04822f86 04600010
[ 6.329870] nouveau 0000:08:00.0: DRM: DCB outp 04: 04022f82 04620010
[ 6.329871] nouveau 0000:08:00.0: DRM: DCB outp 06: 02033f62 00020010
[ 6.329872] nouveau 0000:08:00.0: DRM: DCB outp 08: 02044f72 00020020
[ 6.329872] nouveau 0000:08:00.0: DRM: DCB conn 00: 00001031
[ 6.329873] nouveau 0000:08:00.0: DRM: DCB conn 01: 02000146
[ 6.329873] nouveau 0000:08:00.0: DRM: DCB conn 02: 01000246
[ 6.329874] nouveau 0000:08:00.0: DRM: DCB conn 03: 00010361
[ 6.329875] nouveau 0000:08:00.0: DRM: DCB conn 04: 00020461
[ 6.330225] nouveau 0000:08:00.0: DRM: MM: using COPY for buffer copies
[ 6.821646] nouveau 0000:08:00.0: DRM: allocated 1920x1080 fb: 0x200000, bo 000000008e50ac91
[ 6.822279] fbcon: nouveaudrmfb (fb0) is primary device
[ 7.369999] nouveau 0000:08:00.0: [drm] fb0: nouveaudrmfb frame buffer device
[ 7.370146] [drm] Initialized nouveau 1.3.1 20120801 for 0000:08:00.0 on minor 0
|
I don't know what to do about the firmware it didn't find. _________________ Having problems compiling since 2021 |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6098 Location: Dallas area
|
Posted: Sat Jul 24, 2021 8:31 pm Post subject: |
|
|
Code: | [ 3.150274] nouveau 0000:08:00.0: acr: firmware unavailable
...
[ 3.150308] nouveau 0000:08:00.0: gr: firmware unavailable
[ 3.150314] nouveau 0000:08:00.0: sec2: firmware unavailable
...
[ 3.177569] nouveau 0000:08:00.0: DRM: failed to create kernel channel, -22 |
These are the diffference between builtin and module, and the last one is probably related to one of the firmwares above.
The firmware would have to be included in the kernel build for builtin and if I'm not mistaken you get the firmware from nvidia-firmware.
One of the firmwares controls hardware acceleration, thus the slowness. _________________ PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
hjkl Apprentice
Joined: 22 Apr 2021 Posts: 198 Location: Somewhere in Europe
|
Posted: Sun Jul 25, 2021 9:51 am Post subject: |
|
|
Anon-E-moose wrote: | Code: | [ 3.150274] nouveau 0000:08:00.0: acr: firmware unavailable
...
[ 3.150308] nouveau 0000:08:00.0: gr: firmware unavailable
[ 3.150314] nouveau 0000:08:00.0: sec2: firmware unavailable
...
[ 3.177569] nouveau 0000:08:00.0: DRM: failed to create kernel channel, -22 |
These are the diffference between builtin and module, and the last one is probably related to one of the firmwares above.
The firmware would have to be included in the kernel build for builtin and if I'm not mistaken you get the firmware from nvidia-firmware.
One of the firmwares controls hardware acceleration, thus the slowness. |
I'll try to emerge it then.
I'll let you know how it goes! _________________ Having problems compiling since 2021 |
|
Back to top |
|
|
hjkl Apprentice
Joined: 22 Apr 2021 Posts: 198 Location: Somewhere in Europe
|
Posted: Sun Jul 25, 2021 9:55 am Post subject: |
|
|
hjkl wrote: | Anon-E-moose wrote: | Code: | [ 3.150274] nouveau 0000:08:00.0: acr: firmware unavailable
...
[ 3.150308] nouveau 0000:08:00.0: gr: firmware unavailable
[ 3.150314] nouveau 0000:08:00.0: sec2: firmware unavailable
...
[ 3.177569] nouveau 0000:08:00.0: DRM: failed to create kernel channel, -22 |
These are the diffference between builtin and module, and the last one is probably related to one of the firmwares above.
The firmware would have to be included in the kernel build for builtin and if I'm not mistaken you get the firmware from nvidia-firmware.
One of the firmwares controls hardware acceleration, thus the slowness. |
I'll try to emerge it then.
I'll let you know how it goes! |
Hold up, the version for them is 340 and the driver for that is no longer even in the repos so i'm pretty sure that wouldn't do anything. _________________ Having problems compiling since 2021 |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6098 Location: Dallas area
|
Posted: Sun Jul 25, 2021 10:17 am Post subject: |
|
|
I hadn't looked, it seems that the firmware for the later nvidia cards is provided by sys-kernel/linux-firmware
your card should be a gp106, /lib/firmware/nvidia/gp106 _________________ PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
|