Announcement

Collapse
No announcement yet.

XWayland Rootful HiDPI Support Under Review

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #11
    Originally posted by Hibbelharry View Post

    I tend to agree, but the very definition of X isn't clear at all, at least not in discussions here. Do we talk Xservers here or X.org X11 or generally the X11 protocol?

    A Xserver directly running on hardware will be gone in the foreseeable future. Knowing that we can assume a lot of the current x.org x11 codebase is going into disrepair. Removing some of the very underused and superseeded parts of x.org X11 has already happend in the past when things like Xprint were removed. When will be the time to say this isn't X anymore?
    It'll be when

    X don' give it to ya (what)
    Fuck waiting for you to get Wayland on your own, X don' deliver to ya (uh)
    Click Click, launch it in Rootful, it's real
    With the non-stop, pop-pop of XWayland steel​

    Comment


    • #12
      Originally posted by milo_hoffman View Post
      This may become the safer way forward for those who want to run legacy window managers, given that the X11 server code is basically abandoned and a security ticking time bomb at this point.
      This should have been the way forward from day one.

      But no, we had to repeat the IPv6 experience.

      Comment


      • #13
        Naive question from someone who hasn't researched it and is still getting used to the wayland thing -- would this help running nvidia-settings (which apparently somehow strangely needs X to access the control / monitoring settings for the GPU) under an environment using wayland without X (wherein it'd just crash)?

        Comment


        • #14
          Originally posted by pong View Post
          Naive question from someone who hasn't researched it and is still getting used to the wayland thing -- would this help running nvidia-settings (which apparently somehow strangely needs X to access the control / monitoring settings for the GPU) under an environment using wayland without X (wherein it'd just crash)?
          Unless something changed recently nvidia-settings needs to communicate with the Xorg nvidia video driver so that won't work.

          EDIT: I think a workaround might be starting a separate Xorg instance with the nvidia driver, running nvidia-settings there and do your over clocking. If you're lucky you can load profiles with nvidia-settings on Wayland using the command line interface, but probably not. What should work in any case is nvidia-smi, FWIW. That also works on the console without GUI.
          Last edited by binarybanana; 14 November 2023, 06:15 AM.

          Comment


          • #15
            Originally posted by s_j_newbury View Post
            Code:
            Xwayland -fullscreen -retro :11 -glamor gl -hidpi -once &​
            [...] The dynamic resizing of the root window doesn't seem to be working for me under Sway, [...]
            The automatic resizing happens only with -decorate, not with -fullscreen.

            Comment


            • #16
              Originally posted by milo_hoffman View Post
              This may become the safer way forward for those who want to run legacy window managers, given that the X11 server code is basically abandoned and a security ticking time bomb at this point.
              Recently there was a security advisory involving x.org but they responded quickly with a resolution if memory serves, no?

              Comment


              • #17
                Thanks I'll try the separate Xorg instance thing and see what settings I can apply there that "stick" and remain applied to the overall wayland etc. case when I switch back to it in the other console or something.

                nvidia-smi should work for some controls but sadly I don't think one can control the fans there for instance so some things so far seem only to be possible in nvidia-settings with the more full thermal / clocking etc. controls or run a guest and pass through the GPU and control it there but of course that's only when you don't want to share that one with the host desktop.

                Originally posted by binarybanana View Post

                Unless something changed recently nvidia-settings needs to communicate with the Xorg nvidia video driver so that won't work.

                EDIT: I think a workaround might be starting a separate Xorg instance with the nvidia driver, running nvidia-settings there and do your over clocking. If you're lucky you can load profiles with nvidia-settings on Wayland using the command line interface, but probably not. What should work in any case is nvidia-smi, FWIW. That also works on the console without GUI.

                Comment


                • #18
                  Originally posted by pong View Post
                  or run a guest and pass through the GPU and control it there but of course that's only when you don't want to share that one with the host desktop.
                  That's what I ended up with. The iGPU does all the desktop stuff and the dGPU goes to a VM (for games). Luckily most CPUs have iGPUs now and mobos come with a few video outputs. wine/proton is great, but for me it's always been too hit and miss. Compute can still be done on the host (when not running a VM).

                  Comment

                  Working...
                  X