Re: operation not supported Wayland
- Reply: Леонид Гнездилов : "Re: operation not supported Wayland"
- In reply to: Леонид Гнездилов : "Re: operation not supported Wayland"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 10 Dec 2025 15:08:39 UTC
On 12/10/25 06:26, Леонид Гнездилов wrote: > Well, everything fell into place - hardware acceleration in wayland > stopped working on cores built after about November 24. Alacritty > definitely uses hardware acceleration (most likely OpenGL) of Firefox > too. Now the cool specialists have to get involved and fix everything) > I found and installed the FreeBSD-kernel-generic-16 > package.snap20251110100118 and everything worked as before. Now it > must be frozen so that it is not updated. Thanks for identifying the solution so succinctly. Did you only downgrade the kernel? Is the rest of your base newer? I have a custom kernel so I will need FreeBSD-set-src, although I might have a backup in this case. > Special thanks to Ross, apparently only the two of us will use Wayland > on FreeBSD)) > By the way, Ross, could you try installing alacritty? To repeat the bug. > Let me remind you that I was able to repeat this error on two > motherboards with intel early generations (i915kms), with an external > graphics card (radeonkms) and on a motherboard with Ryzen 3(amdgpu) > ---------------- > To whom: freebsd-current@freebsd.org (freebsd-current@freebsd.org ); > Subject: operation not supported by Wayland; > 09.12.2025, 19:05, "S. Ross Gohlke" <ross@bisd.ro>: > > On 12/9/25 05:04, Leonid Gnezdilov wrote: > > So! I have done research and investigation)) I found out that > the system installed from the image (date 20251110) runs all > applications in wayland. I checked on 4 motherboards with > i915kms (kaby lake and some other lake))) radeonkms and > amdgpu. Starting from 20251124 - "operation not supported". on > any hardware! You just update the working system and get a > non-working firefox, for example. (In general, most of the > software does not work, but the composers themselves do). > It's the same in 15-Stable. > S. Ross Gohlke - could you upgrade the system and give it a try? > > I upgraded from 20251106 to 20251204 and I did run into a problem > -- I was going to try 20251205 before I reported anything, but not > there yet. > > After upgrade, Firefox (and Thunderbird) refused to launch from > the menu. In a panic, I compiled Firefox from ports and got the > same result, but this time I tried running it a second time > directly from the terminal and it gave me a dialog window offering > to launch in Safe Mode, which worked. Safe Mode disables all > extensions, hardware acceleration and something else. > > My extensions were fine, but I had to disable hardware > acceleration to get Firefox to launch normally: > > Settings > General > Performance > > Uncheck "Use recommended performance settings" > > Uncheck "Use hardware acceleration when available" > > I have never seen this setting, I have never used this setting, I > don't know if this is due to a change in FreeBSD or Firefox or both. > > It was the same story with Thunderbird, but Thunderbird did not > preemptively provide a Safe Mode dialog when run from the > terminal. I had to run "thunderbird --safe-mode" to open it so I > could disable hardware acceleration. > > Some background on my system: Lenovo ThinkPad E14, Intel Core > i5-1135G7 > > vgapci0@pci0:0:2:0: class=0x030000 rev=0x01 hdr=0x00 > vendor=0x8086 device=0x9a49 subvendor=0x17aa subdevice=0x5088 > vendor = 'Intel Corporation' > device = 'TigerLake-LP GT2 [Iris Xe Graphics]' > class = display > subclass = VGA > > According to Lenovo, here: > > https://psref.lenovo.com/syspool/Sys/PDF/ThinkPad/ThinkPad_E14_Gen_2_Intel/ThinkPad_E14_Gen_2_Intel_Spec.pdf > > Intel Iris Xe Graphics capability requires system to be > configured with dual-channel memory. On the system with > single-channel memory, Intel Iris Xe Graphics will function as > Intel UHD Graphics > > Since E14 only has one memory slot, I must be consigned to UHD > Graphics, but I have no clue as to the implications. > > The final important detail is that I recently upgraded from 16GB > to 32GB (used) RAM, after upgrade to 20251106 but before upgrade > to 20251204. > > Regards, > > Ross > > ---------------- > To whom: freebsd-current@freebsd.org > (freebsd-current@freebsd.org ); > Subject: operation not supported by Wayland; > 04.12.2025, 16:51, "S. Ross Gohlke" <ross@bisd.ro> > <mailto:ross@bisd.ro>: > > On 12/4/25 07:26, S. Ross Gohlke wrote: > > On 12/3/25 07:23, Leonid Gnezdilov wrote: > > You won't believe it - I installed 15.0-STABLE and > the same thing happened again. I'm already > starting to think it's the computer hardware. > Although it worked until 11/24/2025. > GPU-firmware-intel-kmod-geminilake and i915_kms > are used (different versions, latest, 61, 515) > ---------------- > To: S. Ross Gohlke (ross@bisd.ro ), > freebsd-current@freebsd.org > (freebsd-current@freebsd.org ); > Subject: operation not supported by Wayland; > 02.12.2025, 17:05, "Leonid Gnezdilov" > <comdir@infonix.info > <mailto:comdir@infonix.info>: > > I installed the system again today, on a > different disk. And it doesn't work! > Everything is exactly the same, "operation not > supported". So it wasn't me who broke the > system, but the update.Can this already be > considered a bug? > During the installation, I selected the > installation from the packages (tech preview), > maybe this will help in the diagnosis? The > drm-latest module, I tried drm-515, but it > doesn't help. > ---------------- > To: S. Ross Gohlke (ross@bisd.ro ), > freebsd-current@freebsd.org > (freebsd-current@freebsd.org ); > Subject: operation not supported by Wayland; > 12/01/2025, 17:15 p.m., "Leonid Gnezdilov" > <comdir@infonix.info >: > > Today I tried to remove most of the > packages, but I was almost left without > pkg)) The result was a system with fewer > packages than with the new installation. > Reinstalled wayland. And what do you > think? Everything is the same, most > applications swear on "operation not > supported" Installed foot and wayfire. By > the way, they work. But firefox is not. I > discovered that applications that do not > run use libm.so.5, but do not seem to use > running applications. No other differences > are visible yet. I’ll try to compare on > github foot and alacritty this evening, > maybe I’ll find some kind of pattern. > Tomorrow it’s time to try to reinstall the > system)) > ---------------- > To whom: freebsd-current@freebsd.org > (freebsd-current@freebsd.org ); > Subject: operation not supported by Wayland; > 27.11.2025, 19:44, "S. Ross Gohlke" > <ross@bisd.ro>: > > On 11/26/25 10:11, Leonid Gnezdilov wrote: > > Hi! > FreeBSD 16.0-CURRENT, Wayland. > After the one of upgrade (or after > some of my experiments with the > system), many applications stopped > running. Most applications. Old, > probably XWayland, applications > work. Telegram-desktop, a > rox-terminal, browser was able to > run - net-surf. > > Errors during launch vary, but > almost everything is united by > "operation not supported (os error > 45)" > Well, yes, Wayland compositors > start and work without problems > (hyprland, labwc, hikari), errors > occur when launching compositors > clients - applications. > > I am running a Wayland session on > FreeBSD 16.0-CURRENT pkgbase from a > couple of weeks ago and have not seen > these errors. > > Wayfire is the compositor, and my > regular app rotation -- foot, Firefox, > Thunderbird -- is as stable as it has > been. I am not using XWayland. > > If there are specific apps you would > like me to check let me know. > > Regards, > > Ross > > % pkg info -x gpu > gpu-firmware-intel-kmod-tigerlake-20230625.1600003 > > % pkg info -x drm | grep kmod > drm-latest-kmod-6.9.1600003 > > Also, here is my relevant environment, excluding XDG. > > SAL_USE_VCLPLUGIN=gtk3 > QT_WAYLAND_DISABLE_WINDOWDECORATION=1 > GDK_BACKEND=wayland > SDL_VIDEODRIVER=wayland > QT_AUTO_SCREEN_SCALE_FACTOR=1 > MOZ_ENABLE_WAYLAND=1 > QT_QPA_PLATFORM=wayland-egl > CLUTTER_BACKEND=wayland > QT_QPA_PLATFORMTHEME=qt5ct > > TMPDIR is mounted tmpfs since default /tmp size might be > too small for programs like Firefox to do anything useful. > > -- > Sincerely, > Leonid Gnezdilov > INFONICS LLC > +7(4712)770-365 > +7(919)210-97-73 > > -- > Sincerely, > Leonid Gnezdilov > INFONICS LLC > +7(4712)770-365 > +7(919)210-97-73