You are not logged in.
Pages: 1
My wayland system is running fine.
In an effort to remove all xorg packages I have run into an issue.
It appears if I want to use nvidia graphic drivers it has a dependency of xorg-server as shown below.
What are my options to use nvidia and remove xorg-server?
[demo@archlinux ~]$ sudo pacman -R xorg-server
[sudo] password for demo:
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing xorg-server breaks dependency 'xorg-server' required by nvidia-utils[demo@archlinux ~]$ sudo pacman -R nvidia-utils
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing nvidia-utils breaks dependency 'nvidia-utils=535.98' required by nvidia
:: removing nvidia-utils breaks dependency 'nvidia-utils' required by nvidia-settingsI assume (and I don't like using that word) that if I want to use nvidia I am stuck with xorg-server?
I look to the experts here for advice.
Thanks
Let me know if you need any more info?
Last edited by MAYBL8 (2023-08-22 16:04:50)
Online
How is this a "Wayland update" and why put the date in the title - we can see the date of the post. Please edit the title to represent your actual question.
The nvidia package is the xorg driver, isn't it? If you don't use xorg, why would you need the xorg driver?
EDIT: Actually I'm not sure about this - so it is really a question (not a rhetorical one). I've never really used nvidia - other GPUs have different kernel drivers (e.g., for KMS) and for xorg DDX. I'm now not entirely sure if these are distinct with nvidia and they may all be packaged together.
Last edited by Trilby (2023-08-22 14:38:46)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
The nvidia package is the xorg driver, isn't it?
nvidia is the kernel module built for the linux package. nvidia-utils is all of userspace (including X OpenGL Vulkan e.t.c.) and firmware. https://gitlab.archlinux.org/archlinux/ … n/PKGBUILD
Offline
You could create a dummy package to provide the dependency and see what parts of nvidia-utils actually fail because of that.
Offline
I removed xorg-server and all the nvidia packages that were dependencies of it.
Online
What means you're now using nouveau.
Offline
Graphics:
Device-1: Intel CometLake-U GT2 [UHD Graphics] vendor: Hewlett-Packard
driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
ports: active: eDP-1 empty: DP-1,DP-2 bus-ID: 00:02.0 chip-ID: 8086:9b41
class-ID: 0300
Device-2: NVIDIA GP108M [GeForce MX250] vendor: Hewlett-Packard
driver: nvidia v: 535.98 alternate: nouveau non-free: 535.xx+
status: current (as of 2023-08) arch: Pascal code: GP10x process: TSMC 16nm
built: 2016-21 pcie: gen: 3 speed: 8 GT/s lanes: 4 bus-ID: 3b:00.0
chip-ID: 10de:1d13 class-ID: 0302
Display: wayland server: Xwayland v: 23.2.0 compositor: kwin_wayland
driver: X: loaded: modesetting,nvidia alternate: fbdev,intel,nouveau,nv,vesa
dri: iris gpu: i915 display-ID: 0
Monitor-1: eDP-1 model: AU Optronics 0x30eb built: 2017 res: 3840x2160
dpi: 284 gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5")
ratio: 16:9 modes: 3840x2160
API: OpenGL v: 4.6 Mesa 23.1.6 renderer: Mesa Intel UHD Graphics (CML GT2)
direct-render: YesOnline
Did you reboot after removing the package?
You cannot use the nvidia chip w/o nvidia-utils and it's also what blacklists nouveau.
Edit:
pacman -Qs nvidia
DRI_PRIME=1 eglinfo -BLast edited by seth (2023-08-22 16:30:21)
Offline
Yes rebooted
[demo@archlinux ~]$ pacman -Qs nvidia
local/egl-wayland 2:1.1.11-4
EGLStream-based Wayland external platform
local/libvdpau 1.5-1
Nvidia VDPAU library
local/libxnvctrl 535.98-1
NVIDIA NV-CONTROL X extension
local/sway-nvidia 1.0.7-1
Helper files to make sway a better experience for us poor NVIDIA users.
[demo@archlinux ~]$ DRI_PRIME=1 eglinfo -B
GBM platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: Intel
OpenGL core profile renderer: Mesa Intel(R) UHD Graphics (CML GT2)
OpenGL core profile version: 4.6 (Core Profile) Mesa 23.1.6
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Intel
OpenGL compatibility profile renderer: Mesa Intel(R) UHD Graphics (CML GT2)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 23.1.6
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Intel
OpenGL ES profile renderer: Mesa Intel(R) UHD Graphics (CML GT2)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 23.1.6
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20
Wayland platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: Intel
OpenGL core profile renderer: Mesa Intel(R) UHD Graphics (CML GT2)
OpenGL core profile version: 4.6 (Core Profile) Mesa 23.1.6
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Intel
OpenGL compatibility profile renderer: Mesa Intel(R) UHD Graphics (CML GT2)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 23.1.6
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Intel
OpenGL ES profile renderer: Mesa Intel(R) UHD Graphics (CML GT2)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 23.1.6
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20
X11 platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: Intel
OpenGL core profile renderer: Mesa Intel(R) UHD Graphics (CML GT2)
OpenGL core profile version: 4.6 (Core Profile) Mesa 23.1.6
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Intel
OpenGL compatibility profile renderer: Mesa Intel(R) UHD Graphics (CML GT2)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 23.1.6
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Intel
OpenGL ES profile renderer: Mesa Intel(R) UHD Graphics (CML GT2)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 23.1.6
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20
Surfaceless platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: Intel
OpenGL core profile renderer: Mesa Intel(R) UHD Graphics (CML GT2)
OpenGL core profile version: 4.6 (Core Profile) Mesa 23.1.6
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Intel
OpenGL compatibility profile renderer: Mesa Intel(R) UHD Graphics (CML GT2)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 23.1.6
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Intel
OpenGL ES profile renderer: Mesa Intel(R) UHD Graphics (CML GT2)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 23.1.6
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20
Device platform:
Device #0:
Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: Intel
OpenGL core profile renderer: Mesa Intel(R) UHD Graphics (CML GT2)
OpenGL core profile version: 4.6 (Core Profile) Mesa 23.1.6
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Intel
OpenGL compatibility profile renderer: Mesa Intel(R) UHD Graphics (CML GT2)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 23.1.6
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Intel
OpenGL ES profile renderer: Mesa Intel(R) UHD Graphics (CML GT2)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 23.1.6
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20
Device #1:
Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 15.0.7, 256 bits)
OpenGL core profile version: 4.5 (Core Profile) Mesa 23.1.6
OpenGL core profile shading language version: 4.50
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: llvmpipe (LLVM 15.0.7, 256 bits)
OpenGL compatibility profile version: 4.5 (Compatibility Profile) Mesa 23.1.6
OpenGL compatibility profile shading language version: 4.50
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: llvmpipe (LLVM 15.0.7, 256 bits)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 23.1.6
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20Last edited by MAYBL8 (2023-08-22 16:42:33)
Online
If you want to reinstall nvidia without xorg-server to test what works you can fake the package being installed for one transaction with:
pacman -S --assume-installed=xorg-server=21.1.8-2 nvidiaOffline
Ok I ran the above command.
I have never used the assume switch. That is pretty cool.
Online
This will not sustain, the next "pacman -Syu" will draw in xorg-server again (at least when updating nvidia-utils)
You'll have to use a dummy package to keep the dependency met, see eg. https://aur.archlinux.org/cgit/aur.git/ … form-dummy for an example.
Offline
Please consider opening an issue on the Arch bug tracker asking for the nvidia-utils package to switch xorg-server from depends to optdepends.
Offline
Online
Here is a link to my bug report. They marked it low priority:
https://bugs.archlinux.org/?do=index&op … ed%5B0%5D=
Online
Should I start another post for this one?
I noticed I had xorg-xwayland and went to remove it:
[demo@archlinux ~]$ sudo pacman -Rcns xorg-xwayland
checking dependencies...
:: cage optionally requires xorg-server-xwayland: X11 support
:: sway optionally requires xorg-xwayland: X11 support
:: wlroots optionally requires xorg-xwayland: Xwayland support
Packages (8) kwayland-integration-5.27.7-1 libfontenc-1.1.7-1 libxfont2-2.0.6-2 plasma-wayland-session-5.27.7-2
xorg-server-common-21.1.8-2 xorg-setxkbmap-1.3.4-1 xorg-xkbcomp-1.4.6-1 xorg-xwayland-23.2.0-1It wants to remove plasma-wayland-session
Is this another bug report?
Thanks
Online
https://wiki.archlinux.org/title/KDE#Starting_Plasma
There's a lot of stuff that has no native wayland support (yet) - if you want to use/install that, you'll need xwayland to run a nested X11 and apparently plasma relies on that (no surprise, given its sheer size)
Offline
So if I understand it correctly.
For now under kde-plasma I won't be able to have a pure wayland system (without and xorg packages)?
From my research I don't see that the devs are trying to make a plasma without xorg packages.
Do you know if sway is pure wayland?
I think I broke my sway install. I will try to investigate it next.
Online
Which "devs" are you referring to? There's the upstream KDE/Plasma devs then there's the archlinux devs/packagers. A "pure wayland plasma" might be challenging based on what the first group of devs is doing, but I suspect it is possible if you rebuild / repackage some components. A "pure wayland" set of KDE/Plasma packages in the arch repos is a completely different story - and while it's really up to the packagers in question, arch linux tends to enable most optional compilation bits resulting in large packages with lots of dependencies: it would be a break from this pattern to package a "pure wayland" plasma in the arch repos.
There's a similar distinction for Sway. Sway itself can use xwayland but does not require it in any way. The sway package lists xorg-xwayland as an optional dependency. So yes, it is very easy to run sway as a "pure wayland" compositor.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Thanks for that answer.
Maybe I am asking for something that is not on the list of things to do (having a pure wayland system) . I am ok with just seeing the progress happening and learning as I go.
I will keep learning and researching and looking forward to new developments as they arise.
Thanks everyone for the help so far.
Online
Pages: 1