[Solved] New kernel breaks module loading

Raqua · 2013-06-17 22:32:16

This is what I get when I upgrade to the latest kernel 3.9.6-1. Downgrading to 3.9.5-1 fixes the issue.
Machine will start, boot to login manager, but my mouse does not work, keyboard does not work and I can not ssh to the machine either.

Jun 18 00:08:33 Phenom_LXDE_copy [    5.510604] systemd-modules-load[163]: Failed to lookup alias 'vboxdrv': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [    5.510655] systemd-modules-load[163]: Failed to lookup alias 'vboxnetadp': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [    5.510705] systemd-modules-load[163]: Failed to lookup alias 'vboxnetflt': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [    5.510746] systemd-modules-load[163]: Failed to lookup alias 'loop': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [    5.510786] systemd-modules-load[163]: Failed to lookup alias 'acpi-cpufreq': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [    5.510828] systemd-modules-load[163]: Failed to lookup alias 'tpm_bios': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [    5.510868] systemd-modules-load[163]: Failed to lookup alias 'tpm': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [    5.510907] systemd-modules-load[163]: Failed to lookup alias 'tpm_tis': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [    5.510947] systemd-modules-load[163]: Failed to lookup alias 'pci_hotplug': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [    5.511931] systemd-modules-load[163]: Failed to lookup alias 'shpchp': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [    5.512946] systemd-modules-load[163]: Failed to lookup alias 'ppp_generic': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [    5.513948] systemd-modules-load[163]: Failed to lookup alias 'slhc': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [    5.514961] systemd-modules-load[163]: Failed to lookup alias 'sg': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [    5.904711] systemd[1]: Unit systemd-modules-load.service entered failed state.

Last edited by Raqua (2013-06-20 21:47:43)

WonderWoofy · 2013-06-17 23:05:10

My guess would be that when you upgraded your kernel, your /boot was not mounted. Therefore the version directory in /usr/lib/modules was different from the actual kernel version on disk. But this is not really enough to go on definitively.

Raqua · 2013-06-18 07:52:36

Thanks for your reply.
I do not have separate boot partition, so I am pretty sure it was not unmounted at the time of upgrade.
There were no errors upgrading kernel.

Raqua · 2013-06-20 21:48:11

Ok, I found the problem.

I used to have grub-legacy and switched to syslinux with recent changes with merging /bin /sbin etc. folders.
But I have multiboot and did not noticed that although I had different root I was still booting the same kernel on all 3 partitions. So when I upgraded one partition to 3.9.6, this went fine, but I still booted 3.9.5 kernel from the partition that was not yet upgraded.
Stupid me. I did not realized that syslinux worked differently in this regard.

I tried to make it work with multiple partitions, but specifiing partition with mbr:identifier as wiki says did not work so in the end I switched to grub 2 and now it works.

WonderWoofy · 2013-06-20 22:03:56

Like I said, "the version directory in /usr/lib/modules was different from the actual kernel version on disk".

Raqua · 2013-06-20 22:05:22

Well, not really, version on that disk was exactly the same, just the booted kernel was different.

WonderWoofy · 2013-06-20 22:33:57

I'm surprised that you only just recently started having problems with this. Do you use UEFI with a shared ESP or something? Or a shared /boot?

Raqua · 2013-06-20 22:36:55

I reckon there was no kernel upgrade since I switched from grub-legacy to syslinux, therefore I had everywhere the same kernel, so no problem.
I have none of those you mentioned above.

WonderWoofy · 2013-06-20 22:43:54

Ah, I see, it was the switch (and presumably newly configured bootloader) that messed it all up. That explains it. Thanks for clearing that up in my head.

Raqua · 2013-06-20 22:45:43

Yes.

Arch Linux

#1 2013-06-17 22:32:16

[Solved] New kernel breaks module loading

#2 2013-06-17 23:05:10

Re: [Solved] New kernel breaks module loading

#3 2013-06-18 07:52:36

Re: [Solved] New kernel breaks module loading

#4 2013-06-20 21:48:11

Re: [Solved] New kernel breaks module loading

#5 2013-06-20 22:03:56

Re: [Solved] New kernel breaks module loading

#6 2013-06-20 22:05:22

Re: [Solved] New kernel breaks module loading

#7 2013-06-20 22:33:57

Re: [Solved] New kernel breaks module loading

#8 2013-06-20 22:36:55

Re: [Solved] New kernel breaks module loading

#9 2013-06-20 22:43:54

Re: [Solved] New kernel breaks module loading

#10 2013-06-20 22:45:43

Re: [Solved] New kernel breaks module loading

Board footer