wayfire not running automatically?

T

tyoc213

I installed wayfire via desktop-installer (which only works after reebooting, not from the installation from usb as it will say that it cant fin auto-ask) then I rebooted and could install with desktop-installer, however it did not start in graphical mode, and if I try to run it from my user I get this


1789785470006.png


My computer has 2 nvidia cards

1789785546045.png


Also this freebsd version 15.1 release-p3 generic amd64
pkfinfo | egrep "nvidia|drm"
libdrm-2.4.134,1 direct rendering manager library and headers
nvidia-driver-595.99.02 nvidia graphics driver userland
nvidia-kmod-595.99.02.1500068 nvidia dgraphis driver kernel module
Click to expand...
and this
1789811793222.png
 
I made this tutorial a couple of years ago
before the desktop-installer existed

NapoleonWils0n

Thread 'Freebsd 14 Wayland and Wayfire using Nvidia on Dell XPS 15'

Freebsd 14 Wayland running the Wayfire compositor on a Dell XPS 15 2019 using a Nvidia graphics card


All the hardware works but you need to use wifibox for the wifi drivers,
and nvidia on freebsd doesnt yet support nvenc and cuda

the packages needed are nvidia-driver nvidia-settings nvidia-drm-515-kmod libva-intel-driver libva-utils

and the kld_list looks like this
kld_list="i915kms nvidia-modeset nvidia-drm linux linux64"

In this video i also cover tofi a wayland dmenu rofi clone
github.com

GitHub - philj56/tofi: Tiny dynamic menu for Wayland

Tiny dynamic menu for Wayland. Contribute to philj56/tofi development by creating an account on GitHub.
github.com github.com

Setting up mpv to open videos on the second...
  • Thanks
  • Like
 
One person on discord told me that the first error I got was because I got drivers for 15.0 instead of 15.1, then I made
/usr/ports/graphics/nvidia-drm-kmod/$ make reinstall and after setting export XDG_RUNTIME_DIR=/var/run/user/`id -u` and creating the folder for my 1001 user with 777 permissions I got this errors

By the way, I have 2 cards which I can see with nvidia-smi and two monitors... should I try removing and leaving one?

Should I reinstall all from scratch and not use desktop-installer (which installed incorrect drivers??? where I report that bug for that software?)

1789961269271.png


1789961301437.png



Should I try reinstalling again from scratchs??
 
Hi I helped the OP on discord to install the Nvidia Drivers for FreeBSD 15.1 on his Dual-GPU workstation.
the machine has one Proffesional and one Consumer ADA generation GPU. Error messages seems to originate from the
Consumer 4080 GPU.

He is getting errors with Extended Open GL (EGL) that i don have any experience on.

T-AOKI ? any insight here ?

//Regards.
 
For SLI (I guess Op wants it), NVIDIA has a document below in their readme (the URL is for 595.99.02). But not for Wayland.
Chapter 23. Configuring SLI MosaicREADME/sli.html

And unfortunately, I don't have SLI-capable computer in hand to try.

Note that the documented procedure uses x11/nvidia-xconfig, but it supports old-school monolithic /etc/X11/xorg.conf only (no supports for recent "modularlized" configs).

Text version of NVIDIA's readme should be installed as /usr/local/share/doc/NVIDIA_GLX-1.0/README for your installed version (and HTML version is in html subdirectory there).
 
And for Wayfire, I'm not actually using (installed just to confirm it startup or not before submitting upgraded driver ports), but I have a script to startup Wayfire like below (not exactly the same, maybe-excessive configurations for HiDPI and some others including commented out ones are dropped here).
Possibly you'll additionally need output configuration in ~/.config/wayfire/wayfire.ini, though, if not automatically detected properly.

Code: 
#!/bin/sh
export XDG_RUNTIME_DIR=/tmp/`id -u`-xdg-runtime
export XDG_CONFIG_HOME=${HOME}/.config
export XDG_CACHE_HOME=${HOME}/.cache
export XDG_DATA_HOME=${HOME}/.local/share

export WLR_BACKENDS=libinput,drm

if [ ! -d ${XDG_RUNTIME_DIR} ] ; then mkdir -p ${XDG_RUNTIME_DIR} ; fi

chown -R ${USER}:`id -g` ${XDG_RUNTIME_DIR}
chmod 700 ${XDG_RUNTIME_DIR}

ck-launch-session dbus-run-session wayfire
 
You dont need to manually create the XDG_RUNTIME_DIR anymore
or export it in your shell, its done automatically

Code: 
printenv

And the location is

Code: 
XDG_RUNTIME_DIR=/var/run/xdg/username

where username is your username
 
In the /var/run/xdg/username directory

You should see the wayland-0 socket

Code: 
[i] Yes Master ? doas ls -l /var/run/xdg/djwilcox
total 7
srwxr-xr-x  1 djwilcox djwilcox 0 21 Sep 12:27 Alacritty-wayland-0-12598.sock
drwx------  2 djwilcox djwilcox 3 21 Sep 12:28 at-spi
drwx------  3 djwilcox djwilcox 3 21 Sep 12:27 dbus-1
drwx------  2 djwilcox djwilcox 3 21 Sep 12:28 dconf
drwx------  2 djwilcox djwilcox 2 21 Sep 12:28 doc
drwx------  2 djwilcox djwilcox 3 21 Sep 12:27 dwlb
drwx------  2 djwilcox djwilcox 3 21 Sep 12:28 emacs
drwx------  2 djwilcox djwilcox 4 21 Sep 12:30 pulse
drwx------  4 djwilcox djwilcox 5 21 Sep 12:30 speech-dispatcher
srw-------  1 djwilcox djwilcox 0 21 Sep 12:27 ssh-agent.socket
-rw-------  1 djwilcox djwilcox 0 21 Sep 12:28 tofi.lock
srwxr-xr-x  1 djwilcox djwilcox 0 21 Sep 12:27 wayland-0
-rw-r-----  1 djwilcox djwilcox 0 21 Sep 12:27 wayland-0.lock
-rwx------  1 root     djwilcox 0 21 Sep 12:27 xdg_session.0

You may need to add the following to your ~/.zshenv
or whatever shell you use

Code: 
export XDG_CURRENT_DESKTOP=wlroots
 
Things to check

1) remove export XDG_RUNTIME_DIR if its set in your shell

2) make sure you have seatd and dbus enabled

Code: 
sudo sysrc seatd_enable="YES"
sudo sysrc dbus_enable="YES"

3) make sure you are in the video group

where username is your username

Code: 
sudo pw groupmod video -m username

4) reboot to make sure it picks up the default

5) try starting wayfire with something like this

Code: 
exec dbus-run-session wayfire
 
NapoleonWils0n said:
Things to check

1) remove export XDG_RUNTIME_DIR if its set in your shell

2) make sure you have seatd and dbus enabled

Code: 
sudo sysrc seatd_enable="YES"
sudo sysrc dbus_enable="YES"

3) make sure you are in the video group

where username is your username

Code: 
sudo pw groupmod video -m username

4) reboot to make sure it picks up the default

5) try starting wayfire with something like this

Code: 
exec dbus-run-session wayfire
Click to expand...
And for NVIDIA GPUs specific for Wayland (in general):
  • Not having neither nvidia_load, nvidia-modeset_load nor nvidia-drm_load to be "YES" in /boot/loader.conf (blocklisted by default in recent releases, though). If any, nvidia.ko is mandatorily loaded as a dependency but too large to be loaded in /boot/loader.conf.
  • Having hw.nvidiadrm.modeset=1 (recently default, but for in cases somehow needed to install older versions by overriding version, it would be needed)in /boot/loader.conf.
  • Having nvidia-drm included in kld_list variable in /etc/rc.conf.
Shoudn't be relevant for Op (RTX 4000 series), but for RTX 5000 (blackwell) series and maybe later, too, having:
  • hw.nvidia.registry.EnableGpuFirmware=1 in /boot/loader.conf.
This tunable should be 17 instead of 1 in cases for multi GPU and mixing up RTX 5000 series and GPUs in older generation of architectures.
 
ok, thanks for all the info, the only thing I see clearly is I only have `-rwx------ 1 root djwilcox 0 21 Sep 12:27 xdg_session.0` isnie the xdg of my user.

On the other side I did make reinstall on all of the referenced graphics packages and got this launch_st an launch_err as stin an stout for the command. The error I see is A connection to the bus can't be made (which I guess makes sense from only having sdg session and not the other files from doas ls -l /var/run/xdg/tyoc213.

In loader I have

  • hw.nvidiadrm.modeset="1"
  • hw.nvidia.registry.EnableGpuFirmware=1


In rc.conf I have

  • kl_lis="nvidia-rm nvidia-modeset coretemp cuse"

IIRC I have tried also without nvidia-modeset there...


So, wdyt? is fixable? should I try with only the 4080 which is my "main" gpu?


By the way, https://download.nvidia.com/XFree86/FreeBSD-x86_64/455.38/README/sli.html that nvidia-xconfig doesnt have multigpu option, I attach also the output of nvidia-xconfig --advanced-help
 

Attachments

Not sure on Wayland, but on X11, multi GPU configurations need to:
  • have per-GPU device section within configurations having definition for BusID
  • specify only one primary GPU by putting Option "PrimaryGPU" "yes" line in any of device or OutputClass section
If multiple Option "PrimaryGPU" "yes" line exists, would likely to fail to start X11. If none, likely to go into "undefined behavior" that maybe first detected one dictates.

I consider Wayland to have fatal design issue that (at least clearly) compositor-independent system configs cannot be specified as part of Wayland specs. FATAL. Need to have human-readable text configurations like in X11. Of course, having frontend to configure them on compositors or something running on specific compositor (or generic) is OK, but having such tools doesn't mean it's sufficient.
 
My d key is failing on my laptop along w and s, but on my pc I think it is written correctly as is other keyboar.

Here is the /etc/X11/xorg.conf that was generated, didnt pass any extra arg as multi GPU from the documentation is missing as you can see in the nvidia.txt help log above.
 

Attachments

You must log in or register to reply here.
Back
Top