Bug 1046646 - REGRESSION: rt2x00/rt61pci module not loaded
Summary: REGRESSION: rt2x00/rt61pci module not loaded
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-26 12:34 UTC by Ignacio Casal Quinteiro (nacho)
Modified: 2013-12-27 19:39 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-12-27 19:39:22 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
log messages (47.49 KB, text/plain)
2013-12-26 20:21 UTC, Ignacio Casal Quinteiro (nacho)
no flags Details
grub.cfg (7.74 KB, text/plain)
2013-12-27 19:26 UTC, Ignacio Casal Quinteiro (nacho)
no flags Details

Description Ignacio Casal Quinteiro (nacho) 2013-12-26 12:34:43 UTC
The network is not working after upgrading to fedora 20.

lspci output:
05:01.0 Network controller: Ralink corp. RT2561/RT61 rev B 802.11g


With the f19 kernel it loads and works correctly:
lsmod |grep rt
rt61pci                32326  0 
rt2x00pci              13083  1 rt61pci
rt2x00mmio             13322  1 rt61pci
rt2x00lib              67095  3 rt61pci,rt2x00pci,rt2x00mmio
eeprom_93cx6           13130  1 rt61pci
mac80211              564847  2 rt2x00lib,rt2x00pci
iTCO_vendor_support    13419  1 iTCO_wdt
cfg80211              460310  2 mac80211,rt2x00lib
crc_itu_t              12613  1 rt61pci


Doing the same under the new kernel it does not show any rt module loaded.

Comment 1 Michele Baldessari 2013-12-26 19:39:44 UTC
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

Comment 2 Ignacio Casal Quinteiro (nacho) 2013-12-26 20:18:59 UTC
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

Comment 3 Ignacio Casal Quinteiro (nacho) 2013-12-26 20:21:09 UTC
Created attachment 842072 [details]
log messages

Here you have the log of the last boot.

Comment 4 Ignacio Casal Quinteiro (nacho) 2013-12-26 20:35:48 UTC
[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?

Comment 5 Ignacio Casal Quinteiro (nacho) 2013-12-26 20:37:29 UTC
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

Comment 6 Michele Baldessari 2013-12-26 21:22:57 UTC
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

Comment 7 Ignacio Casal Quinteiro (nacho) 2013-12-27 19:26:00 UTC
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?

Comment 8 Ignacio Casal Quinteiro (nacho) 2013-12-27 19:28:21 UTC
[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...

Comment 9 Ignacio Casal Quinteiro (nacho) 2013-12-27 19:39:22 UTC
I guess the kernel package ended up in some inconsistency state. Reinstalling the package fixed the issue. Thanks for the help.


Note You need to log in before you can comment on or make changes to this bug.