You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to use a patched kernel version 6.0.12 to fix undetected sound module. I did make -j$(nproc) && sudo make module_install && sudo make install.
These are the files inside the /boot after several sudo make install:
After a restart, I saw that the uname -a is updated to 6.0.12+, but not the kernel and initrd image paths from kernelstub -p, which still shows as above paths..
$ uname -a
Linux pop-os 6.0.12+ #2 SMP PREEMPT_DYNAMIC Mon May 1 20:44:44 CEST 2023 x86_64 x86_64 x86_64 GNU/Linux
At the end, I can't see any expected improvement after the reboot.
Since there is no grub-update in PopOS, I'm so confused and unsure how to switch the Linux kernel. There is no official documentation about this. The documentation https://support.system76.com/articles/kernelstub/ is still confusing since the kernel image path doesn't change after executing the command.
The text was updated successfully, but these errors were encountered:
ywiyogo
changed the title
Can't update to previous kernel
Can't update to a previous kernel
May 1, 2023
I tried to use a patched kernel version 6.0.12 to fix undetected sound module. I did
make -j$(nproc) && sudo make module_install && sudo make install
.These are the files inside the /boot after several
sudo make install
:I did run
However, afterwards I saw that the kernel path from
sudo kernelstub -p
doesn't change:After a restart, I saw that the
uname -a
is updated to 6.0.12+, but not the kernel and initrd image paths fromkernelstub -p
, which still shows as above paths..At the end, I can't see any expected improvement after the reboot.
Since there is no grub-update in PopOS, I'm so confused and unsure how to switch the Linux kernel. There is no official documentation about this. The documentation https://support.system76.com/articles/kernelstub/ is still confusing since the kernel image path doesn't change after executing the command.
The text was updated successfully, but these errors were encountered: