Solved Still can't get Wayland working with NVidia.

To resurrect this thread from July, I did a little more work on it. And.. of course, I'd erred. dandelion told me to check that I had
Code: 
hw.nvidiadrm.modeset: 1
set and I thought I had. Only today, did I realize I'd mistyped it, and so it the sysctl was set to 0, not 1.
So, I fixed that, and got a bit further. Now I don't get the errors about cannot create backend.

It's still not working though. I type labwc, or dwl, and the screen then goes to a blotch of colors. I can't enter anything, I can't even remote in and kill wayland, labwc, or dwl. The only fix is to reboot the machine. /var/log/messages has things like
opened client 1 on seat0 No clients on seat0 to activate CLosed client 1 on seat0
I haven't yet looked more deeply into this, but I figure I'm at least making a little progress.
 
hi mate, here's how i start labwc and dwl

labwc

Code: 
exec dbus-launch --exit-with-session labwc

dwl

Code: 
exec dbus-launch --exit-with-session dwl -s 'dwlb -font "monospace:size=16"' 2>/dev/null

Code: 
/etc/rc.conf

Code: 
seatd_enable="YES"
dbus_enable="YES"
 
Thanks, I forgot to try with exec dbus-launch. I'll have to try that later today and report back (in the midst of work now, so won't have time for a while.
 
Unfortunately, no luck there, either. It might be the Nvidia card, I find that I get this same splotches of color screen if I quit X. Though, in that case, I can type startx and get back to an X session.
 
whats in your kld_list

Code: 
/etc/rc.conf

Code: 
kld_list="nvidia-modeset nvidia-drm linux linux64 i915kms ext2fs mac_priority fusefs"

as you say maybe its an issue with your Nvidia card

for me setting up Wayland wasnt too bad

enable seat and dbus
install drivers and add to your kld_list
the XDG_RUNTIME_DIR is created and exported on Freebsd 14.1 so you dont need to do anyting
use dbus-launch to start the wayland compositor

1 - seat
2 - dbus
3 - kld_list
4 - XDG_RUNTIME_DIR
5 - dbus-launch

do you have these packages installed

Code: 
wlroots
xdg-desktop-portal-wlr
qt5-wayland
qt5ct
qt6-wayland
wayland
wayland-protocols
wayland-utils
 
Right, I remember we went through that, probably on page one of this thread. After input from you, and some others, I just have nvidia-drm in the kldlist , seatd and dbus are running, the only thing I'd left out is the dbus-launch. And, I just fixed the typo in loader.conf, I'd had nvidai instead of nvidia. I think it might be the card, but I don't have any of the qt packages you mention nor the wayland-utils. I have linux enabled, but missing several of the others, I'll have to go back and try adding to kld_list and the packages you suggest that I have not installed.
 
hi mate

you dont need ext2fs mac_priority fusefs

extfs is for mounting linux ext4 drivers
mac_priority is for the realtime audio
and i forget what fusefs is for, but its not need not wayland

the following is what i have on my dell xps with nvidia and intel

Code: 
kld_list="nvidia-modeset nvidia-drm linux linux64 i915kms"
 
Ok thanks. Tried with the others though, and still getting that splash of color. I'm getting more convinced it's a problem with my card, since, as I said, if I run startx, then close X, I get that instead of the terminal. I'm going to try to reseat the card at some point this week. Thanks for all your efforts, they are appreciated.

And, if nothing else, at some point (was it this thread?), you turned me on to alacritty, as well as a friend of mine who has some beef with the urxvt people so he'd been looking for a new terminal. And fuse, by the way, is used for some filesystems, for example, on my laptop which multiboots with Linux, I use it to mount Linux partitions.
 
I feel as if I should write a "How NOT TO" to see if I could possibly save some people the stuff I went through. For example, after I added
Code: 
hw.nvidiadrm.modset=1
I began getting artifacts if I left X or went to ctl+alt+fnx. Fixed by either changing it to sc, or by just putting
Code: 
hw.vga.textmode=1
in /boot/loader.conf. Ah well, I'll keep trying when I see wayland or nvidia updates.
 
scottro said:
Ah well, I'll keep trying when I see wayland or nvidia updates.
Click to expand...
If you want, you can try the latest Production Branch of driver (550.107.02) with the patch on PR 280772 if it supports your GPU.
And the patch also allow you to test the latest New Feature Branch of driver (560.35.03). See the posts on the PR for details.
Currently, the latest Beta Branch of driver is older than 560.35.03, so ignore it.

Note that the patch does nothing with legacy drivers. So if your GPU is supported only on legacy drivers (I suppose no, as you are testing nvidia-drm.ko), ignore this post.
 
Thanks, but at this point, I'll just wait till it's in latest packages. It's not important for this workstation to have Wayland, it's more a matter of it being irritating that it doesn't work.
 
Ok, well, the latest NVidia updates seem to have fixed the issue. I can now use Wayland on my main workstation.
The nvidia-driver, nvidia-drm-kmod and linux-nvidia driver updates to 550.120 seem to have solved the issue.

Thanks to everyone, who helped and encouraged on this thread. If I start naming people, I'll leave someone out, so thanks to all.

Of course, on my main workstation, I'll probably keep using X, but it was frustrating to not be able to get Wayland working, and if something does turn out to be better on Wayland on this workstation, I'll have it available (for example, the way videos on the laptop run better on Wayland).
 
You must log in or register to reply here.
Back
Top