http://bugzilla.opensuse.org/show_bug.cgi?id=1207558 Bug ID: 1207558 Summary: Mesa 22.x has got a serious bug Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Critical Priority: P5 - None Component: X.Org Assignee: gfx-bugs@suse.de Reporter: m.nomiya@gmail.com QA Contact: gfx-bugs@suse.de Found By: --- Blocker: --- I installed Mesa 22.3.3 on openSUSE 15.4 on a laptop (Intel CPU and GPU) and when I rebooted, I got a black screen and could not operate it at all. I think this is the reason why it was marked as WONTFIX. However, if a file with the contents of blacklist nvidia is placed in /etc/modprobe.d, X starts without any problems. However, when I execute $ vdpauinfo here, the following strange error message appears. ������cannot find libvdpau_nvidia.so is not found In other words, Mesa does not cause problems on nvidia, amd gpu pc's, but on Intel GPU pc's it also pulls in nvidia modules etc., causing strange behaviour. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1207558 http://bugzilla.opensuse.org/show_bug.cgi?id=1207558#c1 --- Comment #1 from Masaru Nomiya <m.nomiya@gmail.com> --- I built Mesa and Mesa-drivers with ths src.rpm on Timbleweed repository. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1207558 http://bugzilla.opensuse.org/show_bug.cgi?id=1207558#c2 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |IN_PROGRESS CC| |m.nomiya@gmail.com Flags| |needinfo?(m.nomiya@gmail.co | |m) --- Comment #2 from Stefan Dirsch <sndirsch@suse.com> --- Not sure what you did. We don't provide Mesa 22.3.3 packages for Leap 15.4. Not even in X11:XOrg project of our buildservice. You cannot simply expect Tumbleweed packages working on Leap 15.4. I suggest going back to original Mesa of Leap 15.4. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1207558 http://bugzilla.opensuse.org/show_bug.cgi?id=1207558#c3 --- Comment #3 from Masaru Nomiya <m.nomiya@gmail.com> --- Make sure you read it correctly! I have also written the following;
I built Mesa and Mesa-drivers with ths src.rpm on Timbleweed repository.
Again��� I did not install the Mesa, Mesa-drivers binary for Tumbleweed, but compiled & installed their src.rpms within Leap 15.4. I've posted a bugreport on its behaviour. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1207558 http://bugzilla.opensuse.org/show_bug.cgi?id=1207558#c4 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |INVALID --- Comment #4 from Stefan Dirsch <sndirsch@suse.com> --- As said. Still unsupported. I won't spend hours now to try to fix your messed up system. I can only recommend replacing these obviously non-working Mesa packages with the official Mesa packages from Leap 15.4. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1207558 http://bugzilla.opensuse.org/show_bug.cgi?id=1207558#c5 --- Comment #5 from Masaru Nomiya <m.nomiya@gmail.com> --- I am a Tumbleweed user. Packman ML informed me that Mesa 22.x or later is WonfFIX (https://bugzilla.opensuse.org/show_bug.cgi?id=1207425) with Leap 15.x, so I installed Leap 15.4 on my laptop & built Mesa, Mea-drivers on my laptop and checked it out. I then informed you that this might be the cause of WONTFIX. First of all, it's not very likely that it won't boot unless nvidia is blacklisted! Or do you just leave WONTFIX alone? If so, please let me know. I'll report it to ML. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1207558 http://bugzilla.opensuse.org/show_bug.cgi?id=1207558#c6 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(m.nomiya@gmail.co | |m) | --- Comment #6 from Stefan Dirsch <sndirsch@suse.com> --- I've set this to WONTFIX for Leap 15.4 because of ninja failed at some point of building. See https://bugzilla.opensuse.org/show_bug.cgi?id=1207425#c1 I don't know what kind of problem you have on your Intel GPU only machine with nvidia drivers, that you need to disable them. There should not be any nvidia drivers installed on your machine if you don't have any NVIDIA GPU. I can try to figure out what's wrong on your kind of messed up system, but it will take hours of my time I would like to spend my time on more important tasks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1207558 http://bugzilla.opensuse.org/show_bug.cgi?id=1207558#c7 --- Comment #7 from Stefan Dirsch <sndirsch@suse.com> --- Oh. And if you have a fix for building Mesa 22.3 on Leap 15.4, just let me know. Very much appreciated. https://build.opensuse.org/package/show/X11:XOrg/Mesa But I need a fix for the package above. Telling me, that build works on your 15.4 based laptop with all kind of unoffical updates from a number of developer projects unfortunately doesn't help me at all. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1207558 http://bugzilla.opensuse.org/show_bug.cgi?id=1207558#c8 --- Comment #8 from Masaru Nomiya <m.nomiya@gmail.com> ---
I've set this to WONTFIX for Leap 15.4 because of ninja failed at some point of > building. See https://bugzilla.opensuse.org/show_bug.cgi?id=1207425#c1
I was reading this. So when compiling, I watched carefully but the compile went through without any ninja errors. Incidentally, before compiling, I updated leap 15.4 to the latest state of the repositories at the time of installation. So I am wondering why there is a difference in the presence or absence of ninja error. I myself have never experienced a ninja error that prevented me from building at all. I sometimes get a stop with a ninja error when I try to build with gcc9, but these have all been solved by upgrading to gcc12. One more question. Are there other distros with similar reports of Mesa that I haven't been able to find? If so, please inform me of them. It's late here in Japan, so I'm going to bed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1207558 http://bugzilla.opensuse.org/show_bug.cgi?id=1207558#c9 --- Comment #9 from Stefan Dirsch <sndirsch@suse.com> --- There is no gcc12-c++ package available when building against openSUSE_Leap_15.4. It is when building against openSUSE_Leap_15.5 though. So I simply can't verify whether using gcc12 would help. # osc meta prj X11:XOrg <repository name="openSUSE_Leap_15.5"> <path project="openSUSE:Leap:15.5" repository="standard"/> <arch>x86_64</arch> <arch>i586</arch> <arch>aarch64</arch> </repository> <repository name="openSUSE_Leap_15.4"> <path project="openSUSE:Leap:15.4" repository="standard"/> <arch>x86_64</arch> <arch>i586</arch> <arch>aarch64</arch> </repository> -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1207558 http://bugzilla.opensuse.org/show_bug.cgi?id=1207558#c10 --- Comment #10 from Masaru Nomiya <m.nomiya@gmail.com> --- Are you REALLY a maintainer? As a maintainer, it is a given that you know exactly what is in the Leap 15.4 package. As I mentioned earlier, I am talking based on a clean install of Leap 15.4. The Leap 15.4 installer even creates an update repository, which contains a set of gcc12-related files. I didn't know that, and when I began to compile Mesa-22.3.3, etc., I got a message saying to use gcc-12, so I started YaST2, searched for gcc12, and found it, so I just put those in. Now then, you don't understand the meaning of why gcc12 is provided, do you? Anyway, when compiling Mesa and Mesa-drivers, I was told to use libdrm 2.4.110 or higher, even though the system has 2.4.107. I got the src.rpm from the Tumbleweed repo, compiole & install. FYI. I removed libdrm_nouveau2 installed with libdrm, and nvidia blacklisting is no longer necessary. However, vdpauinfo still gives a strange message that libvdpau_nvidia.so is not found, but vainfo works fine. Of course, with the following settings; export LIBVA_DRIVERS_PATH=/usr/lib64/dri export LIBVA_DRIVER_NAME=iHD -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1207558 http://bugzilla.opensuse.org/show_bug.cgi?id=1207558#c11 --- Comment #11 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to Masaru Nomiya from comment #10)
Are you REALLY a maintainer?
Well, I would guess so. After adding X11:XOrg project to obs in 2001 and maintaining it with more than 300 packages since more than 20 years now.
The Leap 15.4 installer even creates an update repository, which contains a set of gcc12-related files.
Seems after changing the build project for 15.4 to openSUSE:Leap:15.4:Update gcc12 packages are found now ... Mesa 22.3.3 now also building against Leap 15.4.
I didn't know that, and when I began to compile Mesa-22.3.3, etc., I got a message saying to use gcc-12, so I started YaST2, searched for gcc12, and found it, so I just put those in.
You stumbled across the buildrequires to gcc12. Easy for you. My collegue figured it out the hard way. But long after Mesa 22.3 had been released. It's still nowhere documented that now gcc12 is needed for building. :-( ------------------------------------------------------------------- Mon Jan 16 11:27:13 UTC 2023 - Hans-Peter Jansen <hp@urpla.net> - Compile with gcc12 on Leaps: building drivers fails with: /usr/include/dxguids/dxguids.h:70:1: internal compiler error: in cxx_eval_bit_field_ref, at cp/constexpr.c:2578
I removed libdrm_nouveau2 installed with libdrm, and nvidia blacklisting is no longer necessary.
No idea why this is needed on a Intel-only GPU system. Maybe you have a Intel/nVidia combination and didn't notice it yet? Running 'inix -aG' would help to figure it out.
However, vdpauinfo still gives a strange message that libvdpau_nvidia.so is not found, but vainfo works fine.
There is no VDPAU driver available for Intel. So apparently you're using the VDPAU wrapper library, which then uses VA-API as backend. package: libvdpau-va-gl check /etc/profile.d/libvdpau-va-gl.sh Maybe VDPAU_DRIVER is set to 'nvidia' for some reason. It should be set to 'va_gl'.
Of course, with the following settings;
export LIBVA_DRIVERS_PATH=/usr/lib64/dri export LIBVA_DRIVER_NAME=iHD
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1207558 http://bugzilla.opensuse.org/show_bug.cgi?id=1207558#c12 --- Comment #12 from Masaru Nomiya <m.nomiya@gmail.com> --- I could build Mesa, Mesa-dedrivers of 22.3.4 on Leap 15.4., and it works fine. vdpauinfo also works fine, as well, Regards. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com