Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have noticed several cases where, if I use lsmod to find a module and then use modinfo for that module, it comes out with a ERROR: Module not found message. For example with the Nvidia module (When using the proprietary drivers).

So in what cases would a module appear on lsmod but give an ERROR like the one I mentioned above with modinfo.

share|improve this question
up vote 7 down vote accepted

It's being aliased. In my example (similar to yours perhaps):

lsmod | grep nvidia
nvidia               9171294  51

modinfo nvidia
ERROR: modinfo: could not find module nvidia

modprobe --resolve-alias nvidia

grep -r nvidia /etc/modprobe.d/
/etc/modprobe.d/nvidia-graphics-drivers.conf:alias nvidia nvidia_current

modinfo nvidia_current
filename:       /lib/modules/3.7.5-030705-generic/updates/dkms/nvidia_current.ko
alias:          char-major-195-*
version:        313.09

Above should speak for itself, doesn't it?

share|improve this answer
Above speaks for itself ^^. Is there any other case where this could also happen. – Luis Alvarado Feb 5 '13 at 22:31
@LuisAlvarado Perhaps, but this is the only one I know of. – gertvdijk Feb 5 '13 at 22:33
So if I have alias myModuleAlias someModule, does modinfo myModuleAlias not work? I would have expected this to be part of the point of an alias? – fpghost Jan 14 '14 at 14:19

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.