The kernel-5.6.6 keeps appearing on the boot menu but I removed it yesterday.
Would be interesting to see what happens when you select/boot that second kernel.
Can you share the output of these two commands?
ls -l /boot/*/5.6.6-300.fc32.x86_64
dnf list --installed kernel\*5.6.6\*
ls -l /boot/*/5.6.6-300.fc32.x86_64 = ls: cannot access ‘/boot/*/5.6.6-300.fc32.x86_64’: No such file or directory
dnf list --installed kernel\*5.6.6\* = Error: No matching Packages to list
So…there kernel is gone but it still shows up on the grub menu even after rebuilding it?
That is odd.
That’s what I think.
Is there a conf file for it in /boot/loader/entries/
This is odd. But I can boot from the second kernel, and it doesn’t have a wifi option neither a bluetooth option. Take a look:
https://drive.google.com/file/d/1ht37auqDur4hcCJs9KaqhF6nuZH-vmik/view?usp=sharing
No, just this:
ee02659f1f65446fb9510d7711281441-0-rescue.conf
ee02659f1f65446fb9510d7711281441-5.6.19-300.fc32.x86_64.conf
My computer has a Optane Memory. Maybe this memory is causing this?
Do you have more than one Fedora installed?
Can we see:
lsblk -o NAME,FSTYPE,SIZE,TYPE,MOUNTPOINT,PTTYPE,LABEL,PARTLABEL
2 Likes
sudo rpm -qa kernel*
Looks fine. That kernel must be there somewhere. You can’t boot off a kernel that doesn’t exist.
Lets find it.
sudo find / -type f -name vmlinuz-5.6.6-300.fc32.x86_64
3 Likes
Why not search for any installed kernel packages with sudo dnf list kernel* ?
Or look for kernel images in /boot/ ?
2 Likes
It’s a lost case, I already tried everything. But thanks to all of you for trying to help me.
This just means a file with the specified name wasn’t found. (forget about /run/user/1000/gvfs)
Just leave the settings as they are, the distribution creators and maintainers usually design the system in a way that makes sense for the end-user. Just get used to see three kernels in the boot menu and all is good. (Are you dual booting? Because if not, you should not even see the Grub menu)
1 Like
Yes, I’m dual booting. Fedora - Windows.
1 Like