Bug 1046646

Hi Ignacio,

with 3.12.X the module does exist:
find /lib/modules/3.12.6-300.fc20.x86_64/ -iname "rt61*"
/lib/modules/3.12.6-300.fc20.x86_64/kernel/drivers/net/wireless/rt2x00/rt61pci.ko

So it might be that it is not correctly loaded on F20. 
If you 'modprobe rt61pci' by hand does it work correctly? Do you get any errors
in /var/log/messages?

Thanks,
Michele

Hi Michele,

the module seems to be there:
[silvia@kasa ~]$ find /lib/modules/3.12.5-302.fc20.x86_64/ -iname "rt61*"
/lib/modules/3.12.5-302.fc20.x86_64/kernel/drivers/net/wireless/rt2x00/rt61pci.ko

Although it does not get loaded for some reason with modprobe. I cannot see anything interesting either in /var/log/messages

Created attachment 842072 [details]
log messages

Here you have the log of the last boot.

[silvia@kasa ~]$ uname -r
3.11.10-301.fc20.x86_64


-------------
menuentry 'Fedora, with Linux 3.12.5-302.fc20.x86_64' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.12.5-302.fc20.x86_64-advanced-300025cb-3b7f-4a9a-a4dd-2784670f254c' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos2'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2  300025cb-3b7f-4a9a-a4dd-2784670f254c
		else
		  search --no-floppy --fs-uuid --set=root 300025cb-3b7f-4a9a-a4dd-2784670f254c
		fi
		linux	/boot/vmlinuz-3.12.5-302.fc20.x86_64 root=/dev/sda2 ro quiet rhgb 
	}
-------------


It should show clearly 3.12.5-302.fc20.x86_64 instead

Is it possible that the update messed up the system? and now it tries to load a kernel that does not have any modules installed. Do you have a suggestion to fix this?

As pointed above no folder for that specific kernel O_o. And the right one is not loaded...

[silvia@kasa ~]$ ls /lib/modules/
3.11.10-200.fc19.x86_64  3.11.6-200.fc19.x86_64  3.3.2-1.fc17.x86_64
3.11.1-200.fc19.x86_64   3.12.5-302.fc20.x86_64

Hi Ignacio,

I am not 100% sure I follow comment 4. Can you upload the full /boot/grub2/grub.cfg file?

From c#4 it is at least odd that there is not initrd file. But in general without
that the system won't boot at all.

thanks,
Michele

Created attachment 842472 [details]
grub.cfg

Since the grub was not updated automatically on the system upgrade I did the next:
grub2-mkconfig -o /boot/grub2/grub.cfg
grub2-install /dev/sda

Clearly I have something messed up on the system since the initrd line was not added you pointed out before.

Should we close this as "Messed up during upgrade kind of bug"? Or do you want some more information to see what actually failed?

[silvia@kasa ~]$ ls /boot/initr*
/boot/initramfs-0-rescue-f6bd7478243382f240fc43fd6bbc94b1.img
/boot/initramfs-3.11.10-200.fc19.x86_64.img
/boot/initramfs-3.11.1-200.fc19.x86_64.img
/boot/initramfs-3.11.6-200.fc19.x86_64.img
/boot/initramfs-fedup.img
/boot/initrd-plymouth.img

So the initramfs file for the new kernel is actually missing...

I guess the kernel package ended up in some inconsistency state. Reinstalling the package fixed the issue. Thanks for the help.