starting wayland (wayfire) fails using nvidia card [Found 0 GPUS]

I just had hours over several days trying to get my dvorak keymap working on Wayfire.
I had:
xkb_layout = us
xkb_model = macintosh
xkb_options =
xkb_rules = evdev
xkb_variant = dvorak

This did not work until I changed "macintosh" to "apple". I also added xkb_options but I don't think that had anything to do with it. It didn't recognize my 2011 Macbook Pro 8, 1 keyboard as macintosh. I've tested changing between macintosh and apple and it does change it between painful qwerty and comfortable dvorak. This is with FreeBSD 14.0 in it with the default keyboard layout always set as us.dvorak. Somehow Wayfire uses standard Qwerty despite that fact. Glad it was resolved. So just in case you guys have the same problem.
 
Thank you to everyone on this thread. This has been very useful to me for the last 24 hours. Special thanks to NapoleonWils0n and ZioMario 🙏. Thanks for the videos NapoleonWils0n.🙏

I used to use FreeBSD in the wayback so bear with me if I say or do something stupid. It has been a hot minute.
Started this project on Friday night and the most progress has been the last 24 hours due largely to this thread. Again thanks you for all the good info.

I have a fully functional system so far 🙏. However, when I run the bash scrip I created start-wayfire I see red errors scrolling by at lighting speeds with the cool blue text so I can't read them.

Would anyone be able to tell me what log it would be in? Wayland log? Seatd log? nvidia log? System log? I am guessing seat but again it goes so fast I can't tell. Again I know someone is going to point me at something obvious in /var/log that I missed. It was 1:30 in the morning lol I haven't slept.
 
hi mate

this is a script i used to start wayfire

Code: 
#!/bin/sh

exec dbus-launch --exit-with-session wayfire

you can start any wlroots compositor on Freebsd using the same method
like dwl, labwc, wayfire etc

you could try sending stderror to a text file
i havent tried but it should work

Code: 
#!/bin/sh

exec dbus-launch --exit-with-session wayfire 2> wayfire-output.txt
 
NapoleonWils0n
Since you got some window compositors running, I am curious, could you also manage to get XWayland working with nvidias proprietary drivers ?
If so, which version worked best for XWayland ?
 
i have got XWayland working on Wayfire, Labwc and dwl
with nvidias proprietary drivers

i use XWayland to run X11 apps like Davinci Resolve in a linux jail
and forward the display from the jail to the Freebsd host

i have been using Wayland on Freebsd for the last 16 months
and have tired wayfire, labwc, hikari, dwl and a few others

wayfire = comes with a panel and a has a gui to configure the settings rather bloated with lots of effects
doesnt have independent workspace per display, you have to pin applications to a display

labwc = doesnt have a panel, so you need to install one
doesnt have independent workspace per display, you have to pin applications to a display

hikari = not going to be updated to the latest version of wlroots by the looks of things
so pretty much abandonware

dwl = built in panel, so you dont have to install one
the best wlroots compositor on Freebsd by far
independent workspace per display, without having to pin applications to a monitor

dwl is the only compositor on Freebsd with independent workspace per display
so it you have a multi monitor set up then dwl is by far the best

you have to enable XWayland in dwl but i cover that in the guide

i dont really tile windows that often, i just keep them on separate workspaces
so even if you arent a tiling window user i would still recommend dwl

heres the top 3

1 - dwl
2 - labwc
3 - wayfire

github.com

cerberus/dwl/dwl-freebsd.org at master · NapoleonWils0n/cerberus

cerberus code library. Contribute to NapoleonWils0n/cerberus development by creating an account on GitHub.
github.com github.com

nvidia-smi

Code: 
Yes Master ? nv-sglrun nvidia-smi
shim init
Wed Mar 12 15:27:36 2025
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 550.127.05             Driver Version: 550.127.05     CUDA Version: 12.4     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce GTX 1650        Off |   00000000:01:00.0 Off |                  N/A |
| N/A   48C    P8              2W /   50W |       1MiB /   4096MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+

+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI        PID   Type   Process name                              GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|  No running processes found                                                             |
+-----------------------------------------------------------------------------------------+

i have written several guides in the how to section

1- freebsd dwl wayland tiling window manager install

NapoleonWils0n

Thread 'freebsd dwl wayland tiling window manager install'

freebsd dwl wayland tiling window manager install with patches in a separate git branch.


the reason why you need to build dwl on freebsd rather than using the port or packages
is because the dwl package lets you set an variable called DWL_HOME_CONFIG that points to a dwl config.h file
which is used to customize dwl

the problem is that a lot of the dwl patches like movestack have changes in other files like dwl.c
and since the dwl package only uses the config.h file most of the patches wont work with the dwl package or port

in this video i cover install dwl on freebsd...
  • Thanks
  • Like

2- labwc a stacking wayland window manager inspired by openbox

NapoleonWils0n

Thread 'labwc a stacking wayland window manager inspired by openbox'

Labwc is a wlroots-based window-stacking compositor for wayland,
inspired by openbox.


In this video i cover window placement , setting the theme, creating keyboard shortcuts to switch workspaces and move windows to different workspaces and monitors

How to warp your cursor between monitors, create keyboard shortcuts to increase, decrease and mute the volume

labwc doesnt have independant workspaces per monitor,
but you can set windows to be dsplayed on all workspaces using a keyboard shortcut

you can also create rules for particular windows like chromium, mpv and...
  • Thanks

3 - Freebsd 14 Wayland and Wayfire using Nvidia on Dell XPS 15

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
 
NapoleonWils0n doesn't dwl require dwlb for a bar/panel? If I just run dwl with no other arguments, I don't get a panel. On FreeBSD, I run it with arguments I got from you,
Code: 
exec dbus-launch --exit-with-session dwl -s 'dwlb -font "Liberation:size=12"'  2>/dev/null
If using it on Linux, I just use waybar, which at least gives me a clock though it doesn't show what is running (that is, no window saying alacritty, etc.) (For Linux I usually use Fedora, which doesn't offer a version of dwlb).
 
hi mate

your right i just checked my notes and i did install the dwlb package

Code: 
sudo pkg install dwlb

and then build dwl from source
so more accurate to say there is a bar that works with dwl

scottro said:
NapoleonWils0n doesn't dwl require dwlb for a bar/panel? If I just run dwl with no other arguments, I don't get a panel. On FreeBSD, I run it with arguments I got from you,
Code: 
exec dbus-launch --exit-with-session dwl -s 'dwlb -font "Liberation:size=12"'  2>/dev/null
If using it on Linux, I just use waybar, which at least gives me a clock though it doesn't show what is running (that is, no window saying alacritty, etc.) (For Linux I usually use Fedora, which doesn't offer a version of dwlb).
Click to expand...
 
LillieNB said:
DWL would be my first choice, as I use mostly tiling windows only.


Linuxulator also, I see.
How is the native XWayland performance under FreeBSD in DWL ?
Click to expand...

XWayland apps even run from a Jail like Davinci Resolve work absolutely fine
no issues at all, you cant tell them apart from native apps

dwl and labwc work great with Xwayland

when i was using wayfire 16 months ago there was an Xwayland bug that crashed the compositor
when you opened an X11 XWayland app but that has now been fixed

the one issue with Xwayland is that at the moment it only supports a single window

for example Davinci resolve by default has a single window but you can set it to use 2 windows,
like having the editor on one display and the preview window on another display

however thats not possible with XWayland at the moment
 
🤣You are spot on! I am 100% using wayfire for the bloated effects and eye candy! I figure what the heck. I am getting off Windows for good so let's have some fun. A little eye candy for fun to start. You have convinced me to look into dwl for sure. Nvidia though... never again!!! It's a 6 year old card and it was all I had. If I had any AMD card at this point I would use it lol. I have been looooooooong waiting for the day FreeBSD felt ready for a desktop user like me. I think it's here. I like the eye candy. 😁
 
NapoleonWils0n said:
hi mate

this is a script i used to start wayfire

Code: 
#!/bin/sh

exec dbus-launch --exit-with-session wayfire

you can start any wlroots compositor on Freebsd using the same method
like dwl, labwc, wayfire etc

you could try sending stderror to a text file
i havent tried but it should work

Code: 
#!/bin/sh

exec dbus-launch --exit-with-session wayfire 2> wayfire-output.txt
Click to expand...

This worked. Appreciate it. I can view the errors that were too fast to read now.
 
I prefer to have KDE 6.0 + Wayland instead of Wayland + wayfire, labwc, hikari, dwl and so on. I was able to have it only choosing my Intel GPU as primary GPU. Didn't work with my nVidia RTX 2080ti GPU. But 1 year is passed until I tried. Maybe at today they have fixed the bugs ? What do you think NapoleonWils0n ?
 
ZioMario said:
I prefer to have KDE 6.0 + Wayland instead of Wayland + wayfire, labwc, hikari, dwl and so on. I was able to have it only choosing my Intel GPU as primary GPU. Didn't work with my nVidia RTX 2080ti GPU. But 1 year is passed until I tried. Maybe at today they have fixed the bugs ? What do you think NapoleonWils0n ?
Click to expand...
I am using a 2080 founders card. :mad:.

I think its the DRM modules that I am not getting right. I had it working the other day. I was running everything on FreeBSD 15. Then I came to the realization that I do want to run some old games for fun. I am not a gamer but like to occasionally waste some time on an old game. Since FreeBSD 15 has removed 32 bit libraries I can see old games becoming a hassle. So reformatted and installed 14.2

Now I am back at square one. Sigh.

I really do like KDE Plasma 6. Other than integration with pacman in Arch (my other windows/mac alternative). But that is probably on me. I did not try to figure out how to integrate the KDE store and pacman. I just didn't care enough and used pacman.

Since this is six year old hardware. Designaire Z390 + intel i9 and nvidia 2080 I thought I would go with something lighter then KDE but I still want a fun experience. This is also not work related and just a fun thing for me to tinker with and have fun. Just wasting time and having fun. Getting to know this old gal FreeBSD again. It's been a looooong time.
 
When I install the nvidia-driver it has xorg as a dependancy.

Is there a way to install with no xorg at all? Is there some kind of install option to use wayland and no xorg code at all?

I am trying to keep this as lean as possible. I am sure there will be libraries installed for that and that. Just trying to keep them to a minimum.
 
wk002 said:
When I install the nvidia-driver it has xorg as a dependancy.

Is there a way to install with no xorg at all? Is there some kind of install option to use wayland and no xorg code at all?

I am trying to keep this as lean as possible. I am sure there will be libraries installed for that and that. Just trying to keep them to a minimum.
Click to expand...
I believe some apps run in XWayland so xorg is part of it , also i dont know if xorg-server contains xwayland.
 
wk002 said:
Since this is six year old hardware. Designaire Z390 + intel i9 and nvidia 2080 I thought I would go with something lighter then KDE but I still want a fun experience. This is also not work related and just a fun thing for me to tinker with and have fun. Just wasting time and having fun. Getting to know this old gal FreeBSD again. It's been a looooong time.
Click to expand...

I have your same hardware components. I think they are powerful enough for running KDE 6.0. If you want to play good games directly on FreeBSD and not only old games,you can try learning how to compile them from source. You can give a look at this video tutorial :


View: https://www.youtube.com/watch?v=kJRjPs2CKQM

in this way you can use 14.2 and play good and relatively recent 3D games.
 
ZioMario said:
I have your same hardware components. I think they are powerful enough for running KDE 6.0. If you want to play good games directly on FreeBSD and not only old games,you can try learning how to compile them from source. You can give a look at this video tutorial :
Click to expand...
I had a 1080TI before, and I could use wine without problems for decent games 2 years ago.
KDE is pretty lightweight I believe.
Well, atleast anything would be lighter here than Windows 7+.
 
ZioMario said:
I have your same hardware components. I think they are powerful enough for running KDE 6.0. If you want to play good games directly on FreeBSD and not only old games,you can try learning how to compile them from source. You can give a look at this video tutorial :


View: https://www.youtube.com/watch?v=kJRjPs2CKQM

in this way you can use 14.2 and play good and relatively recent 3D games.
Click to expand...

That is the current plan. Once I see all the pkgs and options I need then I will probably start all over and compile all the components from source. I just need to rember that option to answer all the prompts before the compile.

I tried to compile the nvidia driver a few nights ago thinking I could install from ports and walk away. NOPE! Every 2 minutes was another window popping up asking me to select options. I vaguely recall from my youth there being a switch which did all the prompts up front and then you could walk away...
 
I couldn't tell you why, but adding "hw.nvidia.fbdev=1" (obviously without the quotes) to my loader.conf file made everything all better. 🩹

It enables the framebuffer? Are there other options available I should be aware of? I would like to look into additional hw.nvidia.xyz options if they exist.

I kind of got the impression that was a linux setting? I have linux and linux64 in my kld_list. Am I doing something in a round about way?
 
wk002 said:
I couldn't tell you why, but adding "hw.nvidia.fbdev=1" (obviously without the quotes) to my loader.conf file made everything all better. 🩹

It enables the framebuffer? Are there other options available I should be aware of? I would like to look into additional hw.nvidia.xyz options if they exist.

I kind of got the impression that was a linux setting? I have linux and linux64 in my kld_list. Am I doing something in a round about way?
Click to expand...
It would be because you're using Wayland instead of X11.

In official tarball from nvidia, it is the default for 570 series of driver, causing X11 to error out (cannot acquire modesetiing permission). So it would be set to 0 on upcoming upgrading on ports with PR 285139 and corresponding review D49245 until required simpledrm for X11 is implemented on base LinuxKPI and/or graphics/drm-*-kmod ports.

If you're fine for it set to 1, you can set it via /boot/loader.conf. (As it is defined as RDTUN, needed to be set BEFORE nvidia-drm.ko is loaded.)

Note that at this moment the patches there cannot be applicable due to updated distfiles of graphics/drm-*-kmod. Would upload updated patch today or tomorrow. (Take some more time to see non-upgraded graphics/drm-510-kmod is upgraded or not.)
 
You must log in or register to reply here.
Back
Top