module list under 13.2

English Hardware
#1

Simple question: how do I get a list of loaded modules with 13.2? modprobe
-l now tells me that -l is an invalid option and man doesn’t seem to show
anything useful for listing what’s loaded.

I’m trying to get a wierd Actiontec usb wireless (AR9170+AR9101) working but
I can’t even figure out if the kernel module is installing.

–
Will Honea

#2

run “lsmod” in the cli
to get a text file, type lsmod >loadedmodules.txt
to see if a mod is loaded, type lsmod | grep “module name”

#3

rwishart wrote:

> run “lsmod” in the cli
> to get a text file, type lsmod >loadedmodules.txt
> to see if a mod is loaded, type lsmod | grep “module name”
>

Thank you. Seems to be a convoluted route to replace a simple option…

Will Honea

#4

This is w hat the lsmod man page in 13.1 (and probably many version before that) says:

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

And lsmod already exists for ages :wink:

#5

hcvv wrote:

> And lsmod already exists for ages :wink:
>

Good point. I plead guilty to being a grumpy old man :slight_smile: Found modprobe -l
and quit looking years back so it’s my problem.

Thanks for all the support, folks - really!

–
Will Honea

#6

I’m trying to get a wierd Actiontec usb wireless (AR9170+AR9101) working but
I can’t even figure out if the kernel module is installing.

Hi Will

A quick way to see if any driver is bound to your USB wireless hardware can be done with

usb-devices

Look for the output block pertaining to your wireless hardware.

#7

deano ferrari wrote:

> A quick way to see if any driver is bound to your USB wireless hardware
> can be done with
>
> Code:
> --------------------
> usb-devices
> --------------------
>
> Look for the output block pertaining to your wireless hardware.
>

Much better info for what I was looking for. Turned out to be an early
“combo” device that needs a driver to handle the specific mode settings they
used. Source for the driver is available with a bit of searching but it was
easier to just dig out another (supported) device from the junk box in this
case.

–
Will Honea

#8

Much better info for what I was looking for. Turned out to be an early
“combo” device that needs a driver to handle the specific mode settings they
used. Source for the driver is available with a bit of searching but it was
easier to just dig out another (supported) device from the junk box in this
case.

–
Will Honea

Yes, sometimes it is just better to take the pragmatic approach and go with hardware that is supported out of the box. :slight_smile:

#9

deano ferrari wrote:

> Yes, sometimes it is just better to take the pragmatic approach and go
> with hardware that is supported out of the box. :slight_smile:
>

Especially with a junk box the size and age of mine :wink:

–
Will Honea