Splatsune

Splatsune, 1 year ago

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.

Splatsune, 1 year ago

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.

Splatsune, 1 year ago

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.

Splatsune, 1 year ago

Either way, this did it! Thank you so much!

https://beehaw.org/pictrs/image/f4b3f47f-495f-40e1-b9b9-3e12cc91926d.webp

Splatsune, 1 year ago

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