Xorg development effort slowing in favour of Wayland
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
its only a thing for vlc or mplayer , but when you are watching youtube in a browser thats different ..
Firefox for linux has no proper hardware decoding yet. It usually gives you a cisco binary, which uses processor to decode youtube's drm infested video.
There is a thing called vaapi for AMD chips, but nvidia's implementation of that thing (vdpau) was still unsupported by mozilla last time I checked.
This is why you can see a lot of internet drama about windows streaming all 60fps videos on 0.5% cpu, while linux streaming same videos on 20% cpu.
Also why a lot of folks just use youtube-dl or similar tools to pipe online video into ffmpeg. It can decode video directly on GPU.
If you want more about tearing, does it happen in glxgears? Is it the same when running glxgears on xfce4 and glxgears on plasma?
Did you force triple buffering in xorg.conf? Did you use cvt tool to generate a modeline for your monitor? Did you enable vsync in nvidia-settings?
I get that it's all a lot of hassle, but there are sometimes simple ways to fix stuff. Unless it's apple, then you get a canned response to recycle it
Firefox for linux has no proper hardware decoding yet.
I thought Firefox use ffmpeg for some/alot of its decoding of video. But then I heard it's not really ffmpeg on the computer, but Firefox having turned into a media player as well, shipping with its own custom version of ffmpeg. How is that even possible? Isn't that incredibly bad if the user actually has ffmpeg installed? Is there any technical reason it can't send output through ffmpeg directly?
X.Org is quite mature. Wayland is still under development at a rapid pace. I see no reason for a distribution like Slackware, LFS, Gentoo, that is source based to be quick to jump onto Wayland
They aren't really. Slackware is shipping with Xorg as default, but it ALSO ships Wayland, which is great. I'm using Wayland.
Perhaps you could consider it "testing", but mature. This works out perfectly well actually. People can chose and both are available. KDE6 will use Wayland as default, and I suspect Slackware will do the same if/when moving to KDE6, but I would think Slackware will keep Xorg around for a long time also.
Firefox for linux has no proper hardware decoding yet. It usually gives you a cisco binary, which uses processor to decode youtube's drm infested video.
There is a thing called vaapi for AMD chips, but nvidia's implementation of that thing (vdpau) was still unsupported by mozilla last time I checked.
This is why you can see a lot of internet drama about windows streaming all 60fps videos on 0.5% cpu, while linux streaming same videos on 20% cpu.
Also why a lot of folks just use youtube-dl or similar tools to pipe online video into ffmpeg. It can decode video directly on GPU.
If you want more about tearing, does it happen in glxgears? Is it the same when running glxgears on xfce4 and glxgears on plasma?
Did you force triple buffering in xorg.conf? Did you use cvt tool to generate a modeline for your monitor? Did you enable vsync in nvidia-settings?
I get that it's all a lot of hassle, but there are sometimes simple ways to fix stuff. Unless it's apple, then you get a canned response to recycle it
I don't know why youtube in their infinite wisdom switched to vp9, when I thought it was always using AV1, or maybe just a standard mp4 format, but my bluray player doesn't like VP9, at least not through my dlna server, because it says it cannot play the format, so I always have to use clipgrab to not only download the video and convert it thus degrading the quality. I tend to watch youtube videos offline when they are longform anyhow - I just find it weird that if I use the youtube app on the bluray, I can watch videos but I can't playback the videos offline through minidlna it hates the VP9 format yet it plays videos just fine from the app, so I don't know, again though this is just another tangent.
As for the playback, I notice in vlc or youtube on firefox or brave that there is some horizontal tearing, depending on if there is a lot of motion on the video in question; I know it also sounds anecdotal but thats all I have.
Okay, I just discovered another reason to move to wayland. In AUR (and I presume elsewhere) there is a set of packages for a Wayfire desktop. Wayfire is the Wayland compositor and it RIPS! IT also takes very little resource! With the rest of the desktop modules and settings it gives Fluxbox a run for the money, as my new lean and fast desktop that gets out of my way and lets me work. Cube animation, animated windows, wobbly windows, the whole set of special stuff without the overhead! (Except blur. Forget blur, it is a dog.)
Wayfire is implemented as a bare-bones Wayland compositor that allows for plug-in modules and it comes with all the modules I need to go crazy. I gotta play with this a while! I feel like a kid with a new toy!
@Jeebizz
The glxgears output is not so relevant, I asked about whether or not you see the same tearing in both plasma and xfce.
Try expanding glxgears to fullscreen in both those environments and see if it tears.
If it only tears in plasma, complain to kwin developer. If it tears in all environments, you can probably assume it's the driver fault or your X configuration.
Also, a (cvt generated) Modeline goes into Monitor section, this one's mine, for example:
Pipeline should probably go into Device section, but I don't use it/not sure, see the README provided with the driver.
Wayland should at least support a configuration file for these options, before being taken seriously as a replacement for Xorg.
@zeebra
Firefox is funded by google, not by ffmpeg. And long ago in the past, flash player used to support vdpau hardware decoding.
@Jeebizz
The glxgears output is not so relevant, I asked about whether or not you see the same tearing in both plasma and xfce.
Try expanding glxgears to fullscreen in both those environments and see if it tears.
If it only tears in plasma, complain to kwin developer. If it tears in all environments, you can probably assume it's the driver fault or your X configuration.
Also, a (cvt generated) Modeline goes into Monitor section, this one's mine, for example:
Pipeline should probably go into Device section, but I don't use it/not sure, see the README provided with the driver.
Wayland should at least support a configuration file for these options, before being taken seriously as a replacement for Xorg.
@zeebra
Firefox is funded by google, not by ffmpeg. And long ago in the past, flash player used to support vdpau hardware decoding.
I'll append that when I have time, but it is just confusing and maybe im reading too much into it - why is CRT even mentioned when nobody is using a crt these days, oh well. I haven't been in xfce either, just plasma5 and before that mate, but i removed MATE and just stuck with plasma5.
why is CRT even mentioned when nobody is using a crt these days, oh well.
Don't worry about it, I only posted my ModeLine as an example, you should make yours with 'cvt' and use "DFP-0" in there.
I use "CRT-0" because the driver identified the connector as CRT-0, as it's connected with plain old VGA cable.
Do not use my ModeLine, cause the numbers are certainly all wrong for your monitor. Read 'man cvt' for more info.
And it might be a good time to update your driver, because you have 470.161.03 and the latest in 470 series is 470.239.06.
Edit:
And you probably don't need a custom EDID binary at all. since DFP connected modern monitors expose the EDID information automatically.
The EDID line is intended only for old monitors, those old school fat VGA cables with ferrite cores, and monitors behind KVM switches as @dhalliwe explained on previous page.
why is CRT even mentioned when nobody is using a crt these days
As elcore mentions, this is just a naming convention for the port on the video card.
In my xorg.conf file, I have two lines that refer to settings on my dual-monitor setup.
Quote:
Option "CustomEDID" "CRT:/etc/X11/LG2261_edid.bin" #Only for the CRT that is blocked by the KVM
Option "metamodes" "DVI-I-1: 1920x1080 +0+0, VGA-0: 1920x1080 +1920+0"
The CustonEDID specification is labelled CRT, but I am using an LED monitor on that VGA output. (As previously mentioned,it passes through a VGA Keyboard-Video-Mouse device, Also known as a KVM.)
The second line mentions a DVI port and a VGA port, and provides me with a single screen across the two monitors (3840x1080 resolution). The labels/names for the two ports on the video card are DVI-I-1 and VGA-0. These names match what I see from the NVIDIA X Server Settings - maybe because it uses what I specified in xorg.conf. I don't remember exactly how I figured out these names,but they need to have some meaning to the driver. The CRT and VGA-0 names are the same port on the video card. As mentioned earlier, I use Nvidia's 390.x driver.
To make a Swedish or a Finnish angry it takes, a lot, it is not in the culture of Linus Torvald to make dramas, just look where the problem comes from....
To make a Swedish or a Finnish angry it takes, a lot, it is not in the culture of Linus Torvald to make dramas, just look where the problem comes from....
Oh well, I might mess with it later but I just don't feel like it right now. I'm also going to be a bit generous and blame the driver perhaps.
Wayfire is implemented as a bare-bones Wayland compositor that allows for plug-in modules and it comes with all the modules I need to go crazy. I gotta play with this a while! I feel like a kid with a new toy!
Slackware as far as I remember has always shipped with a nice selection of Xorg window managers and/or desktop alternatives alongside major one(s). I hope this tradition continues with Wayland (also).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
