Solved How to switch from X.org to Xlibre?

T-Aoki said:
Anyway, NVIDIA doesn't state support for XLibre.
But the message related with NVIDIA are all warnings (WW). And maybe works OK if xlibre-server doesn't actually use any features introduced / modified at ABI version 26. This would be why XLibre guys added xlibre flavor to x11/nvidia-driver/Makefile.
Click to expand...
Actually I haven't noticed any instabilities and the NVIDIA control panel didn't show any issues. Also I am not using any intensive GPU related task, so far so good... 🤷‍♂️
 
freezr said:
Suspend/Resume worked out... 🤔
Click to expand...
Currently, there is very little difference between Xlibre and Xorg so things (for now), should work the same.

As they diverge, Xlibre will likely contain more features, improvements and bug fixes compared to Xorg. But at the same time, may also see more regressions as development is more active.
 
eternal_noob said:
Nobody insulted you.
Click to expand...
I disagree. I was insulted. It was said that I was being obtuse. That is an insult. It's basically the same as saying that someone is stupid.

Anyway, this is my last post about this topic because one more and the scary admin will appear and admonish us, which is also painful to me, so I also try to avoid it.
 
I already said, it would have been more properly phrased as "deliberately obtuse", in the sense that you were pretending to misunderstand what was said. I also apologized for the the misunderstanding. However, if you wish to feel that I insulted you, that's your choice. It was not what was meant, but honestly, I feel that my original elaboration was sufficient.
 
Hi
I'm posting here just to share an experience. I used Xlibre for several months without any problems.

I have a machine with an Nvidia driver.

pkg nvidia-driver-595.80


I encountered no problems, but a blocking bug: My USB keyboard and mouse stopped working at login, and I couldn't connect. Console mode was fine, no hardware issues.
Clearly, xlibre-xf86-input-libinput is the culprit.
I tried another BE zfs with Xlibre, and it worked, but after running an upgrade pkg, the bug reappeared. I'm back to Xorg while waiting for better support or a fix for libinput.
 
  • Thanks
Reactions: mro
fjdlr said:
Hi
I'm posting here just to share an experience. I used Xlibre for several months without any problems.

I have a machine with an Nvidia driver.

pkg nvidia-driver-595.80


I encountered no problems, but a blocking bug: My USB keyboard and mouse stopped working at login, and I couldn't connect. Console mode was fine, no hardware issues.
Clearly, xlibre-xf86-input-libinput is the culprit.
I tried another BE zfs with Xlibre, and it worked, but after running an upgrade pkg, the bug reappeared. I'm back to Xorg while waiting for better support or a fix for libinput.
Click to expand...
After further testing, I cannot say with certainty that xlibre-xf86-input-libinput is the direct cause.


What I observed is:
XLibre environments consistently showed the issue (graphical login displayed, but USB keyboard and mouse inactive).
Xorg environments worked normally.
Replacing the XLibre stack with Xorg fixed the problem.

Therefore, the issue appears to be related to the XLibre input stack or its interaction with my hardware, but I have not identified the exact component yet.
 
fjdlr said:
After further testing, I cannot say with certainty that xlibre-xf86-input-libinput is the direct cause.


What I observed is:
XLibre environments consistently showed the issue (graphical login displayed, but USB keyboard and mouse inactive).
Xorg environments worked normally.
Replacing the XLibre stack with Xorg fixed the problem.

Therefore, the issue appears to be related to the XLibre input stack or its interaction with my hardware, but I have not identified the exact component yet.
Click to expand...
Does adding below in your /etc/sysctl.conf and try-and-erro which one to uncomment helps? Default should be 12 now.

Note that for testing, invoking sysctl kern.evdev.rcpt_mask=(your choice) as root (whichever su to root, sudo or doas would be OK as you like) is OK and having worked one alone in your /etc/sysctl.conf is sufficient for rearest future.

To be honest, you actually don't need below. But having it would help something related happenes again.

If none works, switching from libinput to evdev could help.

Code: 
# kern.evdev.rcpt_mask=1    # bit0 (1<<0), via sysmouse
# kern.evdev.rcpt_mask=2    # bit1 (1<<1), via kbdmux
# kern.evdev.rcpt_mask=4    # bit2 (1<<2), direct USB mouse (ums)
# kern.evdev.rcpt_mask=8    # bit3 (1<<3), direct keyboard (atkbd and ukbd)
# kern.evdev.rcpt_mask=5    # Both bit2 and 0 (sysmouse and ums, no kbd)
# kern.evdev.rcpt_mask=6    # Both bit2 and 1 (ums and kbdmux)
# kern.evdev.rcpt_mask=7    # Bits2, 1, and 0 (ums, kbdmux and sysmouse)
# kern.evdev.rcpt_mask=9    # Bits3 and 0 (direct keyboard and sysmouse)
# kern.evdev.rcpt_mask=10    # Both bit3 and 1 (direct kbd and kbdmux)
# kern.evdev.rcpt_mask=11    # Bits3, 1, and 0 (HW kbd, kbdmux, sysmouse)
# kern.evdev.rcpt_mask=12    # Both bit3 and 2 (direct kbd and ums) default
# kern.evdev.rcpt_mask=13    # Bits 3, 2 and 0 (HW kbd, ums and sysmouse)
# kern.evdev.rcpt_mask=14    # Bits 3, 2 and 1 (HW kbd, ums and kbdmux)
# kern.evdev.rcpt_mask=15    # All 4 bits
 
@ T-Aoki
Hi
Thanks, I'll do a test in a dedicated BE, install Xlibre for try, (I went back to Xorg)

I may try kern.evdev.rcpt_mask later for testing.

What makes me think the issue is not purely an evdev configuration problem is that several Xorg boot environments work correctly on the same machine, while several XLibre boot environments show the issue.

For now I have switched back to Xorg and the problem is gone.
Freebsd 15-1-rc2 and Xorg BE

%> sysctl kern.evdev.rcpt_mask


kern.evdev.rcpt_mask: 12
 
Note that, for example, my Elecom HUGE Plus trackball doesn't work on xorg (xlibre is untested) with kern.evdev.rcpt_mask=12, while works with kern.evdev.rcpt_mask=13 (additionally enable bit0 to enable sysmouse events to be picked).
Most trackballs / mice / trackpoint work fine with kern.evdev.rcpt_mask=12, though.
 
T-Aoki

Okay, I'll test it in a while; I eventually want to switch to Xlibre.

Note that I used Xlibre for several months without encountering any problems. It all started yesterday with an upgrade package; I saw some Xlibre components. This updated build system didn't allow the login/password entry, as mentioned (but I had the graphical login manager, no problem driver Nvidia). When testing other build system snapshots with Xlibre, the problem disappeared. I've gone back to Xorg for the time being, not without regret... "I'll be back."
 
You must log in or register to reply here.
Back
Top