What happened to "modprobe -l" ?

[old486whizz]

modprobe -l has always been very useful to list out what modules are available for your currently running kernel.

I've just upgraded from F15 to F17, and modprobe no longer has the "-l" parameter available!?
And no explanation of where it's vanished to, nor any replacement.

Can anyone possibly give me a clue as to what's going on, as I can't see why this has happened anywhere.

--
old486whizz

[smr54]

Probably worth a search on bugzilla and filing a request. A quick look at bugzilla didn't find that, though there were a few other modprobe complaints.

As to why--quite possibly an oversight.

[marko]

I've never used modprobe -l since I never even heard of that option but "lsmod" works for what you want

[PabloTwo]

old486whizz]I've just upgraded from F15 to F17, and modprobe no longer has the "-l" parameter available!?
And no explanation of where it's vanished to, nor any replacement.

From "man modprobe" on F16 with module-init-tools-3.16-5.fc16.x86_64 (the package that provides the modprobe command).

-l --list
List all modules matching the given wildcard (or "*" if no wildcard is given). This option is provided for backwards com‐
patibility and may go away in future: see find(1) and basename(1) for a more flexible alternative.

[marko]

Originally Posted by marko

I've never used modprobe -l since I never even heard of that option but "lsmod" works for what you want

UPDATE:
Sorry, now I see you mean available module list and not the list of the modules loaded in the kernel. lsmod will only show the modules the kernel has loaded.

All I can think of would be to make a script that takes the output of:

find /lib/modules/`uname -r` -type f -name "*.ko" -exec basename {} \;

and then strips off the .ko extension and then runs each one of those names into 'modinfo'
or if you'd be happy with just the name, then the find command would be enough

[vallimar]

module-init-tools was replaced with kmod.
They don't seem to have replicated that functionality in the new package.

[hadrons123]

This gives the same funtionality as modprobe -l

ls -R /lib/modules/$( uname -r )/kernel

[guzenkov]

Its a pity that such a useful option is gone. Now we have to waste time making up the find expressions.
Speaking of the former I use:

 find  /lib/modules/`uname -r`/kernel -type f -printf '%f\n'