Arch Linux

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: Loading Modules [FAIL] after updating to kernel 2.6.39

Should I use modprobe after upgrading the kernel each time to avoid a potential hang from a problematic module at boot?

That question doesn't make sense to me. If you identify any "problematic modules", you should look for a way to fix them. the modprobe command loads modules, so running it after each kernel upgrade is not a valid operation.

karol

Archivist

Registered: 2009-05-06

Posts: 25,440

Re: Loading Modules [FAIL] after updating to kernel 2.6.39

Not sure what your point is, Karol. MOD_AUTOLOAD= has inded been removed from rc.conf - module autoloading continues to function exactly as before, as I stated above.

Exactly that was my point :-)
Maybe OP saw that MOD_AUTOLOAD was deprecated and thought it meant module autoloading is gone.

subtleflow

Member

Registered: 2011-06-13

Posts: 9

Re: Loading Modules [FAIL] after updating to kernel 2.6.39

How can I identify a module that gives trouble? Which log file should I look or which commands can help? I am just learning about the kernel and modules so any help is appreciated.

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: Loading Modules [FAIL] after updating to kernel 2.6.39

Just one more thing:

I did not saw the LOADING MODULES that I used to see before editing /etc/rc.conf.

You will only see that message if you have modules in rc.conf's MODULES array. You now have none, therefore no message. The message "Triggering Udev uevents" indicates that udev is loading modules for you.

dmesg and/or /var/log/kernel.log will give you information realted to the kernel, including the loading/unloading of modules.

Last edited by tomk (2011-06-13 15:44:54)

subtleflow

Member

Registered: 2011-06-13

Posts: 9

Re: Loading Modules [FAIL] after updating to kernel 2.6.39

Thanks for the info. How can I filter the output from kernel.log or dmesg to get the most relevant information? I tried switching the dmesg level  to 

 dmesg -n 1 

and got nothing from it. Does this mean that my system is free from kernel errors?