You are not logged in.
I am following the arch Wayland wiki to configure weston.
Currently I made the following configuration under ~/.config/weston.ini to make sure that the configuration is working:
[output]
name=LVDS1
mode=1920x1080
transform=flipped
scale=2I run weston using weston-launch.
But nothing changes, namely, weston launches normally without applying the configurations because there is no scale and no flipping.
When I close weston and read its output I find the following line:
Using config file './weston.ini'So it seems like it is reading the file (note I am in .config directory), but why am I not seeing the changes?
Last edited by bazalia (2017-12-11 15:15:11)
Offline
The main option I want for now is scale=2 because I have a HiDPI display.
I tried running
weston --backend=drm-backend.so --scale=2But that crashed (I don't know how to copy the stdout to here as the machine I am trying to get wayland to work in doesn't have a gui)
I noticed that --scale seems to be an option for the wayland and x11 backends only and not for drm backend. So I tried running
weston --backend=wayland-backend.soand
weston --backend=x11-backend.soAnd they returned
Loading module '/usr/lib/libweston-3/wayland-backend.so'
failed to create display: No such file or directory
fatal: failed to create compositor backendand
Loading module '/usr/lib/libweston-3/x11-backend.so'
fatal: failed to create compositor backendNote /usr/lib/libweston-3 directory does include both of these files, and that I am running as root, and that I am using nvidia drivers
Offline
Re-read the wiki page,
then decide whether you prefer to change compositor or videocard manufacturer.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Ok I think I understand this a bit more. But correct me if I'm wrong.
There are multiple compositors that implement the Wayland protocol.
These compositors include Weston, GNOME, Sway and Grefsen.
Weston does not support NVIDIA GPU drivers but other three mentioned above do.
Hence I need to change to another compositor.
Offline
Close, but not entirely correct.
The official wayland protocol only mentions GBM as Buffer API.
All linux drivers support GBM except the nvidia driver.
Nvidia proposed an alternative called EGLStreams, but they are the only ones that use it and it was rejected for becoming part of the official wayland protocol.
Nvidia started work on a new buffer API that is intended to be supported/usable by all drivers, but no one knows when that will be ready.
The developers of some wayland compositors decided they didn't want to wait for that and implemented EGLStreams support in their compositor.
If you want to combine wayland with the nvidia driver you can only choose between the compositors that include EGLStreams support.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Ok thanks for the answer, I'm always happy to learn something new.
I ended up installing GNOME and everything is fine now.
Offline
When I close weston and read its output I find the following line:
Using config file './weston.ini'So it seems like it is reading the file (note I am in .config directory), but why am I not seeing the changes?
Maybe no longer interesting fo you, but this meens that the config file needs to be in ~, not in ~/.config.
Offline
bazalia wrote:When I close weston and read its output I find the following line:
Using config file './weston.ini'So it seems like it is reading the file (note I am in .config directory), but why am I not seeing the changes?
Maybe no longer interesting fo you, but this meens that the config file needs to be in ~, not in ~/.config.
No. That means it should be loading the configuration file from "{CURRENT_WORKING_DIRECTORY}/weston.ini". bazalia said he was running it after "cd ~/.config", so it should be right.
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
bazalia wrote:When I close weston and read its output I find the following line:
Using config file './weston.ini'So it seems like it is reading the file (note I am in .config directory), but why am I not seeing the changes?
Maybe no longer interesting fo you, but this meens that the config file needs to be in ~, not in ~/.config.
No it doesn't. It means that it is looking for weston.ini in the current directory.
Offline