ChuckPa
February 15, 2023, 6:06am
42
Yes.
You set / remove any conf changes.
Example: This is how to make the Apple Magic Keyboard function keys work.
[chuck@lizum ~.2001]$ cd /etc/modprobe.d
[chuck@lizum modprobe.d.2002]$ ls
alsa-base.conf blacklist-firewire.conf blacklist-rare-network.conf mdadm.conf
amd64-microcode-blacklist.conf blacklist-framebuffer.conf hid_apple.conf vmware-fuse.conf
blacklist-ath_pci.conf blacklist-modem.conf intel-microcode-blacklist.conf
blacklist.conf blacklist-oss.conf@ iwlwifi.conf
[chuck@lizum modprobe.d.2003]$ cat hid_apple.conf
options hid_apple fnmode=2
[chuck@lizum modprobe.d.2004]$
Next I update-initramfs and reboot.
So even if I don’t have the latest firmware that dmesg is complaining about ( tgl_guc_70.1.1.bin), if I do an update-initramfs, it will update the kernel to use the existing one that I have (older version)?
ChuckPa
February 15, 2023, 6:10am
44
Are you using the default kernel or did you upgrade that manually?
That was upgraded manually through the Bullseye backports repo:
root@mediaserver:~# uname -r
6.0.0-0.deb11.6-amd64
ChuckPa
February 15, 2023, 6:11am
46
I can’t help with that stuff. Keeping up with current distribution is challenging enough.
You’ve created a custom kernel config. You NEED to get the right kernel drivers in it for it to work.
This is why I never recommend messing with the kernel unless you know what you’re doing.
I see, ok. There was another problem (which I forgot what it was) that a kernel upgrade fixed. So that’s why for all my Debian servers, I upgrade the kernel always.
However, all these GuC stuff didn’t really fix the issue in this thread. I don’t know what did.
ChuckPa
February 15, 2023, 6:16am
48
First get all the drivers in that it’s complaining about.
Once that’s done (and initramfs rebuilt) – retest
system
Closed
May 16, 2023, 6:17am
49
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.