[SOLVED] 3.17.* do not load usb related modules

root · 2014-11-03 04:09:45

Today I realized that I couldn't mount any USB device. They weren't even detected according to the dmesg output.
As I haven't mounted any of these as of late I couldn't tell when this behaviour may have started.
It appears though that, at least in my case, 3.17.* kernels do not load the necessary modules once the USB device is connected.
I have tried with both 3.17.1 and 3.17.2 being the latter the one I updated to as of today.

Luckily I had still the 3.16.4 kernel around and, after downgrading, those modules (usb_storage, sd_mod and usbcore) were loaded correctly after connecting the memory stick.

All of them are the stock kernels and this only happens with the 3.17 ones.

EDiT: Working again without any known reason in 3.17.3 kernel.

Last edited by root (2014-11-20 01:53:29)

ewaller · 2014-11-03 04:17:54

When you had the problem, did you think to verify that the running kernel was indeed 3.17? Any chance the kernel you were actually running was really still 3.16, but the installed modules had been upgraded to 3.17? Note, this is not an idle question, the problem is very common.

root · 2014-11-03 04:50:50

Thanks for your reply ewaller.

Do you refer to running

uname -r

?

When I first encountered the problem I was still running the 3.16 kernel and hadn't yet rebooted after doing the daily pacman update. Do you mean that despite not having had rebooted the 3.17 modules were already "live"?

If so, as far as I understand it, it should have all worked correctly after the downgrades when I restarted right after them, shouldn't it?

Scimmia · 2014-11-03 04:53:57

When you update the kernel, you reboot.

ewaller · 2014-11-03 05:22:45

Yeah, what happens is the kernel in memory cannot find its modules because a new kernel has been installed and the old modules on disk removed. If one upgrades the kernel, and for whatever reason (there are at least a half dozen) the new kernel does not fond its way to the boot partition, then, even after a reboot, the kernel (which is loaded at boot) that kernel will not be able to locate its modules. So yes, if you've trouble, ensure that the versions from uname -r and pacman -Qi linux are the same.

root · 2014-11-03 06:00:58

@ewaller

I see.
Though, as far as I understand it, it doesn't explain why until I downgrade to the 3.16.4 kernel those modules are not loaded by either of the 3.17 ones.

I just checked and uname -r and pacman -Qi linux are the same but still the modules are not loaded.

I followed the steps suggested by the wiki for adding the modules manually and dmesg tells me the following:

[ 6463.126925] usbcore: registered new interface driver usb-storage
[ 6579.109027] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 6579.109940] sr 1:0:0:0: Attached scsi generic sg1 type 5

Not what I expected (the drives are usually sdb) and lsusb still doesn't show the drive:

Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

karol · 2014-11-03 14:02:58

https://bugs.archlinux.org/task/42664

raymondcal · 2014-11-09 16:01:06

Same thing here with my USB mouse.
3.16 broke my intel xserver driver
3.17 is breaking USB.
What's happening to Arch ?

karol · 2014-11-09 16:49:46

I'm using an intel GPU and it works fine.
https://bbs.archlinux.org/viewtopic.php … 9#p1459309

tsh · 2014-11-09 18:38:17

raymondcal wrote:

Same thing here with my USB mouse.
3.16 broke my intel xserver driver
3.17 is breaking USB.

I am coming from a similar problem -- my USB keyboard and mouse were not detected until they were plugged out and plugged in again.

The problem seems to be depending upon when the new kernel is installed or when mkinitcpio is run. I upgraded the kernel when the USB keyboard and mouse were not connected. However, after connecting them both and then running

mkinitcpio -p linux

they were working correctly. I then compared the older initramfs and the one after running mkinitcpio and the older one did not have the logitech module needed by my USB mouse. Could it be that mkinitcpio hooks only include the currently in-use modules for USB devices?

Lone_Wolf · 2014-11-10 12:00:19

tsh wrote:

Could it be that mkinitcpio hooks only include the currently in-use modules for USB devices?

Not exactly , any modules required for specific hardware that's not connected when mkinitcpio is run with autodetect won't be added.

$ mkinitcpio --hookhelp autodetect
==> Help for hook 'autodetect':
This hook shrinks your initramfs to a smaller size by autodetecting the needed
modules. Be sure to verify included modules are correct and none are missing.
This hook must be run before other subsystem hooks in order to take advantage
of auto-detection.  Any hooks placed before 'autodetect' will be installed in
full.
$

To verify which modules are detected, you can use mkinitcpio --automods .

root · 2014-11-16 02:37:35

On my behalf I don't use autodetect as, if I remember correctly, it didn't work quite well with resume on this laptop (leading to a black screen).

A fix for this situation might be available once the 3.18 kernel is available,

https://bugzilla.kernel.org/show_bug.cgi?id=84381

cfr · 2014-11-17 00:57:57

tsh wrote:

I am coming from a similar problem -- my USB keyboard and mouse were not detected until they were plugged out and plugged in again.

This may be a different problem. If I understood the OP, the USB modules were not loaded even when things were newly connected. On the other hand, they are loaded in your case when things are connected. (I have a similar problem although it is not specific to 3.17.* and may be a different problem again.)

root · 2014-11-18 00:59:23

cfr wrote:

This may be a different problem. If I understood the OP, the USB modules were not loaded even when things were newly connected.

You understood correctly.

Even though as of 3.17.3 the usb related modules are back but, in "exchange", both suspend and hibernate crash.

Considering to mark this as 'Solved' as the issue has changed its category so to speak.

Arch Linux

#1 2014-11-03 04:09:45

[SOLVED] 3.17.* do not load usb related modules

#2 2014-11-03 04:17:54

Re: [SOLVED] 3.17.* do not load usb related modules

#3 2014-11-03 04:50:50

Re: [SOLVED] 3.17.* do not load usb related modules

#4 2014-11-03 04:53:57

Re: [SOLVED] 3.17.* do not load usb related modules

#5 2014-11-03 05:22:45

Re: [SOLVED] 3.17.* do not load usb related modules

#6 2014-11-03 06:00:58

Re: [SOLVED] 3.17.* do not load usb related modules

#7 2014-11-03 14:02:58

Re: [SOLVED] 3.17.* do not load usb related modules

#8 2014-11-09 16:01:06

Re: [SOLVED] 3.17.* do not load usb related modules

#9 2014-11-09 16:49:46

Re: [SOLVED] 3.17.* do not load usb related modules

#10 2014-11-09 18:38:17

Re: [SOLVED] 3.17.* do not load usb related modules

#11 2014-11-10 12:00:19

Re: [SOLVED] 3.17.* do not load usb related modules

#12 2014-11-16 02:37:35

Re: [SOLVED] 3.17.* do not load usb related modules

#13 2014-11-17 00:57:57

Re: [SOLVED] 3.17.* do not load usb related modules

#14 2014-11-18 00:59:23

Re: [SOLVED] 3.17.* do not load usb related modules

Board footer