Description of problem: Blender show no text in menus and dialogues, nouveau errors in journal (wanted to learn it a bit but got no further...) Version-Release number of selected component (if applicable): blender-3.3.8-1.mga9.src.rpm Cauldron near Megeia 9 release How reproducible: Always on this system, a Thinkpad T510; $ inxi -G Graphics: Device-1: NVIDIA GT218M [NVS 3100M] driver: nouveau v: kernel Device-2: Lenovo Integrated Webcam [R5U877] type: USB driver: uvcvideo Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X: loaded: modesetting,v4l dri: nouveau gpu: nouveau resolution: 1920x1080~60Hz API: OpenGL v: 3.3 Mesa 23.1.5 renderer: NVA8 I have tried with both plain nouveau, and with modeseting, same result. nvidia470 is not compatible. Steps to Reproduce: 1. Up to date Cauldron / mga9 near release. Plasma, sddm, x86_64 2. Install Blender 3. Launch Blender; 4. It looks OK except there is no text in menus or dialogues $ blender --factory-startup --debug-all Reveals several identical errors like this: Received X11 Error: error code: 167 request code: 152 minor code: 0 error text: GLXBadFBConfig No error nor warning in /var/log/Xorg.0.log In journal: aug 19 00:52:59 localhost kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 00000004 [INVALID_VALUE] aug 19 00:52:59 localhost kernel: nouveau 0000:01:00.0: gr: 00100000 [] ch 37 [001cb60000 blender[225155]] subc 4 class 502d mthd 0838 data 000121b0 aug 19 00:52:59 localhost kernel: nouveau 0000:01:00.0: gr: TRAP_MP_EXEC - TP 0 MP 0: 00000010 [INVALID_OPCODE] at 06e68c warp 28, opcode fff0f0f0 fff4f4f4 aug 19 00:52:59 localhost kernel: nouveau 0000:01:00.0: gr: TRAP_MP_EXEC - TP 0 MP 1: 00000010 [INVALID_OPCODE] at 06e68c warp 27, opcode fff0f0f0 fff4f4f4 aug 19 00:52:59 localhost kernel: nouveau 0000:01:00.0: gr: 00200000 [] ch 37 [001cb60000 blender[225155]] subc 3 class 8597 mthd 0d78 data 00000004 aug 19 00:52:59 localhost kernel: nouveau 0000:01:00.0: gr: TRAP_MP_EXEC - TP 0 MP 0: 00000010 [INVALID_OPCODE] at 06e68c warp 28, opcode fff0f0f0 fff4f4f4 aug 19 00:52:59 localhost kernel: nouveau 0000:01:00.0: gr: TRAP_MP_EXEC - TP 0 MP 1: 00000010 [INVALID_OPCODE] at 06e68c warp 27, opcode fff0f0f0 fff4f4f4 Last three lines repeated many times
Created attachment 13944 [details] Screenshot
CC blender packager, and driver maintainers
CC: (none) => ghibomgx, kernel
WORKAROUND: disabling hardware acceleration "works" meaning menues etc appear correctly but with the drawback it is really painfully slow.... (only tested with modesetting) "Mageia Control Center" -> "Set up the graphical server" -> "Options" -> Checkmark "Disable Hardware Acceleration", and reboot.
Pretty weird it happens on nvidia470 as the GL levels there should be complete. Does the same occurs in nvidia-current-535.xx (at least for the time it stays up before kernel resuming crashes)? Does the same occurs using blender-3.3.11, e.g. here: https://copr-be.cloud.fedoraproject.org/results/ghibo/mageia9-bonus/mageia-cauldron-x86_64/06318015-blender/
(In reply to Giuseppe Ghibò from comment #4) > Pretty weird it happens on nvidia470 as the GL levels there should be > complete. > > Does the same occurs in nvidia-current-535.xx (at least for the time it > stays up before kernel resuming crashes)? Morgan is using nouveau as this card is so old that it is no longer supported by any driver (needs 340)…
(In reply to sturmvogel from comment #5) > (In reply to Giuseppe Ghibò from comment #4) > > Pretty weird it happens on nvidia470 as the GL levels there should be > > complete. > > > > Does the same occurs in nvidia-current-535.xx (at least for the time it > > stays up before kernel resuming crashes)? > Morgan is using nouveau as this card is so old that it is no longer > supported by any driver (needs 340)… Ah, I missed the newer card report that changed, so the card is not the GTX 750Ti anymore...
Yes this is another machine than I normally report on. This is my newest laptop. As said in description i also tried nvidia470 but as expected it is not compatible. On my machine with GTX 750Ti, Blender works now currently on modesetting OK (for less suspend-resume problems than the nvidia driver, and Giuseppe's lowlatency kernel.)
(In reply to Morgan Leijström from comment #7) > Yes this is another machine than I normally report on. This is my newest > laptop. As said in description i also tried nvidia470 but as expected it is > not compatible. > > On my machine with GTX 750Ti, Blender works now currently on modesetting OK > (for less suspend-resume problems than the nvidia driver, and Giuseppe's > lowlatency kernel.) I think this is not a bug of blender, but rather of nouveau (or to be precise modesetting+nouvau). Probably it has some flaw on some opengl level. We might check it's compatibility with 'piglit': https://gitlab.freedesktop.org/mesa/piglit but we don't have it yet packaged for mga. As for your old laptop and blender, I think you can still "squeeze" something from it using the nvidia340.xx proprietary drivers (of course unsupported for security). You should have received the instructions on how to use it.
(In reply to Giuseppe Ghibò from comment #8) > (In reply to Morgan Leijström from comment #7) > > > > On my machine with GTX 750Ti, Blender works now currently on modesetting > I think this is not a bug of blender, but rather of nouveau (or to be > precise modesetting+nouvau). Plus it depends on GPU capability i presume, as it works on my workstation with GTX 750Ti --- > As for your old laptop and blender, I think you can still "squeeze" > something from it using the nvidia340.xx proprietary drivers (of course > unsupported for security). You should have received the instructions on how > to use it. Thank you i got that mail. Might try that. However easiest is dual boot it to Windows 10, and blender works correctly there.
I guess we probably have more software with similar issues, (using higher level OpenGL than provided by modesetting+nouveau with actual GPU)... We have to keep eyes open for reports.
Just trying blender on my system: $ inxi -G Graphics: Device-1: Intel GeminiLake [UHD Graphics 600] driver: i915 v: kernel Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X: loaded: intel,v4l dri: iris gpu: i915 resolution: 1366x768~60Hz API: OpenGL v: 4.6 Mesa 23.1.5 renderer: Mesa Intel UHD Graphics 600 (GLK 2) and as expected it does not show Morgan's problem. This looks good for ERRATA. @Morgan, you say comment 3 how to disable h/w acceleration, which fixes the issue at a price. I was unsure whether 'modesetting' helped; and if so, how to do that.
Keywords: (none) => FOR_ERRATA9CC: (none) => lewyssmith
Added in https://wiki.mageia.org/en/Mageia_9_Errata#Graphics
Source RPM: blender-3.3.8-1.mga9.src.rpm => blender-3.3.8-1.mga9.src.rpm, xorg modesetting, kernel...Keywords: FOR_ERRATA9 => IN_ERRATA9Summary: Blender show no text in menus and dialogues, nouveau [INVALID_OPCODE] in journal => Incomplete OpenGL support with old GPUs, i.e Blender show no text in menus and dialogues, nouveau [INVALID_OPCODE] in journal
Is this option in Comment #3 depending on the grafic card or desktop environment? I dont have this checkbox.
CC: (none) => linux
(In reply to psyca from comment #13) > Is this option in Comment #3 depending on the grafic card or desktop > environment? I dont have this checkbox. Yes, it's depending on graphic card driver. Available only for intel, amdgpu, nvidia proprietary, nouveau and modesetting.
Thanks, added to Errata.