Arch Linux

With the LTS version of the kernel i don't get the error.

I guess it will work if you reboot into 4.9.6 again.

Duplicate of  FS#16702 

Maybe I'm to tired now, but after reading the bug report you sent, i don't really understand how it relates.
Who exactly need to enable the kernel modules and how should be approached.
I see i have the file /lib/modules/4.9.7-1-ARCH/kernel/fs/isofs/isofs.ko.gz. So i should be able to load the modle temporary to test if it works: insmod /lib/modules/4.9.7-1-ARCH/kernel/fs/isofs/isofs.ko.gz

So to load the module permanently i should add an entry to /etc/modprobe.d/ for this module.
But i still don't get it, why after the kernel update i don't have this module loaded anymore.
Could you please elaborate?

Thanks!

You claim to be using and have updated to 4.9.6-1, but *now* you have the modules directory for 4.9.7-1
Either way, you cannot load a module that no longer exists, so kernel updates require you to reboot if you want to load new modules *at all*.
 FS#16702  would solve that problem, by no longer deleting /lib/modules/4.9.6-1-ARCH/ after your kernel update to 4.9.7-1

As for why you don't have this module loaded "anymore", I would consider it far more likely that you never had it loaded to begin with... that is the point of modules, the kernel doesn't load them until and unless you try to use them for the first time.

I wanted to test if the module was loading and if i could manually load it. And after booting back to 4.9.7-1-ARCH kernel, when i run modinfo isofs it appears to be loaded, then i make a test and I can mount now iso files.
I don't understand :(

From the IRC bot:
> When you upgrade the kernel package, it removes all modules for the old version and installs ones for the new version, so module loading doesn't work anymore until you reboot.

Ah ok. I understand now. I didn't realised that i didn't rebooted my laptop since the last kernel upgrade.
Hmm, what if after installing the new kernel, there will be created a simlink for the modules with the name of the new kernel and deleted after the first restart?
Can this be done?

It could be done, but it would be a horrible idea. The reason they have a different name in the first place, is because they aren't guaranteed to be compatible (and for major version bumps, they almost certainly won't be even if you can get away with it on minor version bumps).

OK, thanks for the info. It might be a solution, because the "Kernel Care" from Cloud Linux patches the kernel without a need for reboot, but I don't know how they do it.