Exciting! Thank you so much for your help mate, it's very much appreciated.
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.
Either way, this did it! Thank you so much!
I believe that the issue might be that the amdgpu driver is too new, judging by this string of errors:
Dec 20 21:30:54 minion xserver-wrapper[1080]: (II) AMDGPU(0): [KMS] Kernel modesetting enabled.
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
Dec 20 21:30:54 minion xserver-wrapper[1080]: (II) AMDGPU(1): [KMS] Kernel modesetting enabled.
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
Dec 20 21:30:54 minion xserver-wrapper[1080]: (EE) Screen 0 deleted because of no matching config section.
Dec 20 21:30:54 minion xserver-wrapper[1080]: (II) UnloadModule: "amdgpu"
Dec 20 21:30:54 minion xserver-wrapper[1080]: (EE) Screen 0 deleted because of no matching config section.
Dec 20 21:30:54 minion xserver-wrapper[1080]: (II) UnloadModule: "amdgpu"
Dec 20 21:30:54 minion xserver-wrapper[1080]: (EE) Device(s) detected, but none match those in the config file.
Dec 20 21:30:54 minion xserver-wrapper[1080]: (EE)
Dec 20 21:30:54 minion xserver-wrapper[1080]: Fatal server error:
Dec 20 21:30:54 minion xserver-wrapper[1080]: (EE) no screens found(EE)
So if this doesn't end up working, I'll definitely look into the pinning thing, because 5.10 seems like my best shot.
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:
boot.kernelPatches = [{
name = "acpi quirk";
patch = pkgs.writeText "acpi.patch" ''
diff --git a/drivers/acpi/resource.c b/drivers/acpi/resource.c
index 297a88587031..655332f3a5da 100644
--- a/drivers/acpi/resource.c
+++ b/drivers/acpi/resource.c
@@ -524,6 +524,12 @@ static const struct dmi_system_id pcspecialist_laptop[] = {
DMI_MATCH(DMI_BOARD_NAME, "GM6BG0Q"),
},
},
+ {
+ /* Infinity E15-5A165-BM */
+ .matches = {
+ DMI_MATCH(DMI_BOARD_NAME, "GM5RG1E0009COM"),
+ },
+ },
{ }
};
'';
}];
I'll report back with the results when I'm able.
I picked up a laptop a couple of months ago for the purpose of setting up Linux on (I chose NixOS for stability) to go with my existing desktop. It's an Infinity E15-5A165-BM (Infinity being an Australian local manufacturer of gaming laptops) which features a Ryzen 5 6600H CPU and a GeForce 1650 GTX.
The keyboard uses a generic driver (i8042), which works great on Windows and when booting (including Grub/systemd-boot). However, once booted, I've found that the keyboard no longer responds to input - and in fact no longer shows up as an input device. Now, I've done a fair bit of debugging so far (for someone who's not had to patch anything manually but knows how to do a proper search) and I've worked out the following:
- The latest available kernel in which the keyboard is recognised is 5.10 LTS - but setting this as the kernel to use in NixOS results in me no longer being able to boot into a graphical interface.
- I managed to find this lore.kernel thread in which I believe my issue is discussed. This tells me that it's known and being worked on and that I can maybe wait for a future kernel version, and that theoretically I might just be able to patch the kernel myself, if I learn how to do that and use the right settings?
I've done a couple of commands and pulled some logs from the laptop, and detailed info - lshw, lspci, dmidecode, acpidump, etc - can be found in this folder on my web server.
To my understanding my options are to use the older kernel for now and figure out why the display manager is not working, or learn to patch the current kernel and hope that that works. What's my best option, and is there anything else I might be missing ?
If you block spam SMSes or assholes and spambots on chat services, it's basically that. No matter how much the other person tries, they can no longer get through to you on that service. In most cases, it's as if they no longer exist.