Hello everyone,
Because of some wi-fi problems I'm having with the latest 5.12 rc4 kernel in rawhide, I'd like to switch back to 5.12 rc3, because I recall that wi-fi worked.
The command, credits to Ed, I tried, was
sudo grub2-editenv - set "saved_entry=133a2487cda040dbbe9609f0ab827def-5.12.0-0.rc3.20210319git8b12a62a4e3e.172.fc35.x86_64
but it didn't work, so I'm wondering if that entry thing needs to be changed.
If so, how? what should I do?
Thanks for any answer.
Best regards.
Francisco.
On 27/03/2021 18:35, Francisco Tissera wrote:
Because of some wi-fi problems I'm having with the latest 5.12 rc4 kernel in rawhide, I'd like to switch back to 5.12 rc3, because I recall that wi-fi worked.
The command, credits to Ed, I tried, was
sudo grub2-editenv - set "saved_entry=133a2487cda040dbbe9609f0ab827def-5.12.0-0.rc3.20210319git8b12a62a4e3e.172.fc35.x86_64
but it didn't work, so I'm wondering if that entry thing needs to be changed.
If so, how? what should I do?
Thanks for any answer.
Well, I did something like that on an F33 system. Switching from 5.11.9-200.fc33 to 5.11.7-200.fc33 with no problem.
After doing the "set" command did you verify that it took by doing the "list" command?
I don't know if it is an email issue, but the command you showed didn't have a closing quote mark.
Francisco Tissera writes:
Hello everyone,
Because of some wi-fi problems I'm having with the latest 5.12 rc4 kernel in rawhide, I'd like to switch back to 5.12 rc3, because I recall that wi-fi worked.
The command, credits to Ed, I tried, was
sudo grub2-editenv - set "saved_entry=133a2487cda040dbbe9609f0ab827def-5.12.0-0.rc3.20210319git8b12a62a4e3e. 172.fc35.x86_64
but it didn't work, so I'm wondering if that entry thing needs to be changed.
If so, how? what should I do?
grubby --set-default=/boot/vmlinuz-??????.fc33.x86_64
Fill in the path to the kernel version you want to boot by default.
I did this for a few months while the noveau kernel driver has been utterly fubared, until it got fixed.
Althought it's unclear whether this would work now that your grub2 config has been fiddled with, first. But, that would've been what does the trick.