linux

This magazine is from a federated server and may be incomplete. Browse more on the original instance.

Gork, in Could 2024 be the year of the diagonal linux desktop?

I would constantly be turning my head, even though I wouldn’t need to, if my monitor were rotated at a weird angle like that.

BeardedBlaze, in Could 2024 be the year of the diagonal linux desktop?
@BeardedBlaze@lemmy.world avatar

This doesn’t work on Wayland lol

kugmo,
@kugmo@sh.itjust.works avatar

Based, X forever staying relevant.

fruitycoder,

Time to update “Are we Wayland yet?” With this breaking lack of feature support.

waigl,

Have you tried it? There is wlrandr, and at least according to how the command line looks, it could be supported.

BeardedBlaze,
@BeardedBlaze@lemmy.world avatar

Have you?

GermainRobitaille, (edited )

Are you talking about wlr-randr? Because its –transform argument only accepts normal|90|180|270|flipped|flipped-90|flipped-180|flipped-270, not any transformation matrix. Maybe its just a limitation of the command line tool and it could be modified, I don’t know, I haven’t been too deep in the code or the protocol specifications. It also looks like it only works with wlroots based compositor.

dinckelman, in Does Wayland really break everything? (Nate Graham's OG post ref'd in the Phoronix article)

I’ve been using Wayland sessions as default since plasma 5.22 came around, and with other window managers before that too. Everything that has ever been broken for me, was broken because of X11 or XWayland. I’d rather take a considerably better experience with an occasional issue, that an experience that is held together by candy wrappers and hot glue, and is widely considered obsolete

PseudoSpock,
@PseudoSpock@lemmy.dbzer0.com avatar

Pics or it didn’t happen.

semperverus, (edited )
@semperverus@lemmy.world avatar

Im in the same boat. Been using wayland since around that version or a little later and it has only been uphill (except for right now since i am on the development build and Qt broke itself causing the system config menu to fail to load 80% of KCMs, but this is my fault for switching to alpha software lol)

possiblylinux127, in What is the point of dbus?

Its so that your system can hold passengers

bus

maryjayjay,

*can hold dpassengers

norgur,
@norgur@discuss.tchncs.de avatar

Get into de bus?

taanegl, in Gentoo goes Binary (packages)

Wait, didn’t Gentoo have a binary cache? I seem to remember many years ago that I used one…

LogicalDrivel, in Could 2024 be the year of the diagonal linux desktop?
@LogicalDrivel@sopuli.xyz avatar

I’m just going to leave this here …m.wikipedia.org/…/Betteridge's_law_of_headlines

Quazatron, in Gentoo goes Binary (packages)
@Quazatron@lemmy.world avatar

Good, I might try it now.

When you have more life behind you than ahead of you, time suddenly becomes precious.

kerrigan778, in Could 2024 be the year of the diagonal linux desktop?

No.

Corngood, (edited ) in Laptop keyboard unresponsive - I think my (unknown) laptop is affected by the kernel Zen IRQ regressions - how do I work around this?

Could you do:

Please share the output of grep -v /sys/class/dmi/id/* as a normal user (not root)

It looks like all the patches from that thread are in linux 6.6, so your board may still need quirks added.

Once you know the board name you try something like this:


<span style="color:#323232;">  boot.kernelPatches = [{
</span><span style="color:#323232;">      name = "acpi quirk";
</span><span style="color:#323232;">      patch = pkgs.writeText "acpi.patch" ''
</span><span style="color:#323232;">diff --git a/drivers/acpi/resource.c b/drivers/acpi/resource.c
</span><span style="color:#323232;">index 297a88587031..655332f3a5da 100644
</span><span style="color:#323232;">--- a/drivers/acpi/resource.c
</span><span style="color:#323232;">+++ b/drivers/acpi/resource.c
</span><span style="color:#323232;">@@ -524,6 +524,12 @@ static const struct dmi_system_id pcspecialist_laptop[] = {
</span><span style="color:#323232;"> 			DMI_MATCH(DMI_BOARD_NAME, "GM6BG0Q"),
</span><span style="color:#323232;"> 		},
</span><span style="color:#323232;"> 	},
</span><span style="color:#323232;">+	{
</span><span style="color:#323232;">+		/* [COMPUTER DESCRIPTION] */
</span><span style="color:#323232;">+		.matches = {
</span><span style="color:#323232;">+			DMI_MATCH(DMI_BOARD_NAME, "[BOARD_NAME]"),
</span><span style="color:#323232;">+		},
</span><span style="color:#323232;">+	},
</span><span style="color:#323232;"> 	{ }
</span><span style="color:#323232;"> };
</span><span style="color:#323232;">'';
</span><span style="color:#323232;">  }];
</span>

Just be careful that the indentation of the patch part doesn’t get changed.

Splatsune,
@Splatsune@beehaw.org avatar

Figured I’d do the pre-setup before I went to bed, so I’ve run the grep command and put the board_name from that output such that the patch now reads thus:


<span style="color:#323232;">  boot.kernelPatches = [{
</span><span style="color:#323232;">      name = "acpi quirk";
</span><span style="color:#323232;">      patch = pkgs.writeText "acpi.patch" '' 
</span><span style="color:#323232;">diff --git a/drivers/acpi/resource.c b/drivers/acpi/resource.c 
</span><span style="color:#323232;">index 297a88587031..655332f3a5da 100644 
</span><span style="color:#323232;">--- a/drivers/acpi/resource.c 
</span><span style="color:#323232;">+++ b/drivers/acpi/resource.c 
</span><span style="color:#323232;">@@ -524,6 +524,12 @@ static const struct dmi_system_id pcspecialist_laptop[] = {
</span><span style="color:#323232;">                        DMI_MATCH(DMI_BOARD_NAME, "GM6BG0Q"), 
</span><span style="color:#323232;">                }, 
</span><span style="color:#323232;">        }, 
</span><span style="color:#323232;">+       { 
</span><span style="color:#323232;">+               /* Infinity E15-5A165-BM */ 
</span><span style="color:#323232;">+               .matches = { 
</span><span style="color:#323232;">+                       DMI_MATCH(DMI_BOARD_NAME, "GM5RG1E0009COM"), 
</span><span style="color:#323232;">+               }, 
</span><span style="color:#323232;">+       }, 
</span><span style="color:#323232;">        { } 
</span><span style="color:#323232;"> }; 
</span><span style="color:#323232;">'';
</span><span style="color:#323232;">  }];
</span>

I’ll report back with the results when I’m able.

Corngood, (edited )

Nice. Also it occurred to me that there might be a way to set that quirk through the kernel command line instead of having to compile a patched kernel. I haven’t had a chance to look it up though.

Edit: I couldn’t find anything obvious. This behaviour is buried pretty deep.

Splatsune,
@Splatsune@beehaw.org avatar
Corngood, (edited )

That’s great. If you get a chance, would you be able to test this patch?


<span style="color:#323232;">diff --git a/drivers/acpi/resource.c b/drivers/acpi/resource.c
</span><span style="color:#323232;">index 297a88587031..3204bed08b3c 100644
</span><span style="color:#323232;">--- a/drivers/acpi/resource.c
</span><span style="color:#323232;">+++ b/drivers/acpi/resource.c
</span><span style="color:#323232;">@@ -484,6 +484,18 @@ static const struct dmi_system_id tongfang_gm_rg[] = {
</span><span style="color:#323232;"> 			DMI_MATCH(DMI_BOARD_NAME, "GMxRGxx"),
</span><span style="color:#323232;"> 		},
</span><span style="color:#323232;"> 	},
</span><span style="color:#323232;">+	{
</span><span style="color:#323232;">+		.ident = "Infinity E15-5A165-BM"
</span><span style="color:#323232;">+		.matches = {
</span><span style="color:#323232;">+			DMI_MATCH(DMI_BOARD_NAME, "GM5RG1E0009COM"),
</span><span style="color:#323232;">+		},
</span><span style="color:#323232;">+	},
</span><span style="color:#323232;">+	{
</span><span style="color:#323232;">+		.ident = "Infinity E15-5A305-1M"
</span><span style="color:#323232;">+		.matches = {
</span><span style="color:#323232;">+			DMI_MATCH(DMI_BOARD_NAME, "GM5RGEE0016COM"),
</span><span style="color:#323232;">+		},
</span><span style="color:#323232;">+	},
</span><span style="color:#323232;"> 	{ }
</span><span style="color:#323232;"> };
</span><span style="color:#323232;"> 
</span>

I’d like to try to get it upstream, and that seems like the sanest way to do it.

You might need to be on linux 6.5+ for this patch to apply, and if you could verify that it’s still broken on 6.6 without the patch, that would be nice.

Splatsune,
@Splatsune@beehaw.org avatar

I did try kernel 6.6 without either patch before installing the new one, and I can confirm that the issue was still present on that version.

With the new patch though (after adding a comma to the end of each .ident string), everything is working as expected.

Corngood,

That’s great. Thanks!

Corngood,

git.kernel.org/pub/scm/linux/kernel/…/commit/?h=b…

FYI, I think the fix will make it into 6.8.

Splatsune,
@Splatsune@beehaw.org avatar

Exciting! Thank you so much for your help mate, it’s very much appreciated.

Chewy7324, in Does Wayland really break everything? (Nate Graham's OG post ref'd in the Phoronix article)

Same topic, original article linked in post description. lemmy.ndlug.org/post/523560

GustavoM, in Does Wayland really break everything? (Nate Graham's OG post ref'd in the Phoronix article)
@GustavoM@lemmy.world avatar

Been using Wayland since 3’ish years ago and my desktop experience has been really smooth – no crashes, errors or anything of the sort. Everything “just werks” just as if I were on Xorg instead. Even on a completely obscure/zero linux support single board computer (Orange pi zero 3).

cogman,

Graphics drivers are what matters. Your orange pi uses a mali GPU which is well supported by Linux (thanks ARM).

nVidia is just barely at the point where their most recent gpu drivers aren’t terrible under Wayland. It’s taken a while to get there.

GPUs with good open source drivers will fare fine.

umbrella,
@umbrella@lemmy.ml avatar

maxwell users are fucked tho

cogman,

Not as bad as you might think. The nouveau drivers have come a long way for maxwell. You should give it a shot if you haven’t. But, unfortunately, if you are using anything new then nouveau sucks. It’s a fun game where you get to wait until nvidia no longer wants to support your GPU and hope by that point that nouveau has progressed far enough that you won’t be looking at noman’s land.

umbrella, (edited )
@umbrella@lemmy.ml avatar

I meant the GTX900 series. I’m aware the 700s have decent support in nouveau, but the 900s has already been dropped by nvidia so we are on older drivers not capable of the latest vulkan extensions required by modern Proton.

For nouveau it needs GSP firmware that wasnt released as part of that release they did a while ago. I think pascal users are on the same situation, they just havent been dropped by the proprietary drivers yet. I wonder if we are gonna be stuck on xorg forever.

The newer cards got the important bits released by nvidia so the community can at least have a path forward…

cogman,

I wasn’t fully aware of NVK and where it’s at. It’s actually pretty exciting. I wouldn’t mind dropping my current nvidia binary blob for fully open source drivers.

umbrella,
@umbrella@lemmy.ml avatar

it didnt work ootb for me on ubuntu so i dropped it, but i hear it can already be made to work well with the desktop and basic stuff. performance in games is still bad but they are running.

cevn,

It still sucks for me at least. Doesnt respect scaling, or work after suspend, also discord streaming still broken for years. Also push to talk.

Chewy7324,

I’ve switched away from Xorg a few years ago because of its terrible multi monitor support and bad experiences with picom. Sway and now hyprland are imo a better tiling wm experience then their Xorg equivalent.

isotope, in I've started building a TUI for Lemmy

Looks good! You might want to join forces with github.com/LunaticHacker/lemmy-terminal-viewer

chaorace, (edited ) in Laptop keyboard unresponsive - I think my (unknown) laptop is affected by the kernel Zen IRQ regressions - how do I work around this?
@chaorace@lemmy.sdf.org avatar

Your best bet is probably figuring out why the graphical session isn’t working and then going from there. Since you’re on NixOS odds are all the logs you need are right there in journald.

Worst case scenario: you might need to pin your system nixpkgs to ~January 2021 until the issue sorts itself out. You can still install newer userland packages if you separately manage them as a flake (this is a common and well-supported pattern in home-manager)

EDIT: found a discussion with good configuration.nix examples for pinning the system nixpkgs. Once you find a workable pin you could also try inching it up to get a better idea of what broke (January 2021 is a good starting point because it’s the last month before 5.11 released, a newer pin is very likely possible)

Splatsune,
@Splatsune@beehaw.org avatar

I believe that the issue might be that the amdgpu driver is too new, judging by this string of errors:


<span style="color:#323232;">Dec 20 21:30:54 minion xserver-wrapper[1080]: (II) AMDGPU(0): [KMS] Kernel modesetting enabled.
</span><span style="color:#323232;">Dec 20 21:30:54 minion xserver-wrapper[1080]: (EE) AMDGPU(0): [drm] Failed to open DRM device for pci:0000:05:00.0: Invalid argument
</span><span style="color:#323232;">Dec 20 21:30:54 minion xserver-wrapper[1080]: (II) AMDGPU(1): [KMS] Kernel modesetting enabled.
</span><span style="color:#323232;">Dec 20 21:30:54 minion xserver-wrapper[1080]: (EE) AMDGPU(1): [drm] Failed to open DRM device for pci:0000:05:00.0: Invalid argument
</span><span style="color:#323232;">Dec 20 21:30:54 minion xserver-wrapper[1080]: (EE) Screen 0 deleted because of no matching config section.
</span><span style="color:#323232;">Dec 20 21:30:54 minion xserver-wrapper[1080]: (II) UnloadModule: "amdgpu"
</span><span style="color:#323232;">Dec 20 21:30:54 minion xserver-wrapper[1080]: (EE) Screen 0 deleted because of no matching config section.
</span><span style="color:#323232;">Dec 20 21:30:54 minion xserver-wrapper[1080]: (II) UnloadModule: "amdgpu"
</span><span style="color:#323232;">Dec 20 21:30:54 minion xserver-wrapper[1080]: (EE) Device(s) detected, but none match those in the config file.
</span><span style="color:#323232;">Dec 20 21:30:54 minion xserver-wrapper[1080]: (EE)
</span><span style="color:#323232;">Dec 20 21:30:54 minion xserver-wrapper[1080]: Fatal server error:
</span><span style="color:#323232;">Dec 20 21:30:54 minion xserver-wrapper[1080]: (EE) no screens found(EE)
</span>

So if this doesn’t end up working, I’ll definitely look into the pinning thing, because 5.10 seems like my best shot.

chaorace,
@chaorace@lemmy.sdf.org avatar

Hmm… what’s the purpose of loading amdgpu at all if you’re using an NVIDIA card? Optimus?

GustavoM, in Gentoo goes Binary (packages)
@GustavoM@lemmy.world avatar

Gentoo “purist”: “Welp, Gentoo is now officially dead.”

Non-gentoo user: “Welp, Gentoo is now just another Arch fork LMAO!”

Ramin_HAL9001, (edited )

Non-gentoo user: “Welp, Gentoo is now just another Arch fork LMAO!”

To be fair, you can still build packages and fine-tune the builds with the Emerge system flags, which is sort-of Gentoo’s killer feature. It is just that they have recognized that most people will install probably 99% of all software without changing the default flags, and so why not give them those packages pre-built.

So I guess this make Gentoo more similar to Nix OS or Guix OS but without the high-tech package manager and dependency resolution.

thecookingsenpai, in Gentoo goes Binary (packages)
@thecookingsenpai@lemmy.world avatar

When Arch switching to brew as one and only package manager

  • All
  • Subscribed
  • Moderated
  • Favorites
  • linux@lemmy.ml
  • localhost
  • All magazines
  • Loading…
    Loading the web debug toolbar…
    Attempt #