insmod is the original low level way to do it and you need the full
path and module filename.

modprobe knows the correct kernel and knows where all modules are
supposed to be install so should just work(assuming a depmod was run
to build the name -> filename mappings).

dmesg | grep -i rt28   and see if it finds a device.

if it does then
"ip link show"

if it does not work do a
lsusb  and return that output.  the ID xxxx:xxxx needs to be shown in
the modinfo as an alias, if not the module does not see the device as
something it is a driver for.


On Mon, Feb 13, 2023 at 3:34 PM Barry Scott <ba...@barrys-emacs.org> wrote:
>
>
>
> On 13 Feb 2023, at 19:12, Bill C <bill.cu1...@gmail.com> wrote:
>
> When I use these tools I get nothing. I ran insmod, that would not install 
> anything. I was thinking there are a bunch of dependencies needed. I must 
> need to install more packages or I will try the live workstation later.
>
>
> I have always used modprobe not insmod. I wondered why and RTFM'ed and found 
> this in the insmod man page.
>
> "insmod is a trivial program to insert a module into the kernel. Most
> users will want to use modprobe(8) instead, which is more clever and
> can handle module dependencies."
>
> Does modprobe get you further?
>
> Barry
>
>
>
> On Mon, Feb 13, 2023, 7:29 AM Ralf Corsépius <rc040...@freenet.de> wrote:
>>
>>
>>
>> Am 13.02.23 um 04:35 schrieb Bill Cunningham:
>> > IDK if anyone is familiar with this series of legacy products/drivers or
>>
>> I am not familiar with these drivers, but AFAIS, they seem to be in
>> Fedora's kernel:
>>
>> # modinfo rt2800usb
>> filename:
>> /lib/modules/6.1.10-200.fc37.x86_64/kernel/drivers/net/wireless/ralink/rt2x00/rt2800usb.ko.xz
>> license:        GPL
>> firmware:       rt2870.bin
>> description:    Ralink RT2800 USB Wireless LAN driver.
>> ...
>>
>> Ralf
>> _______________________________________________
>> users mailing list -- users@lists.fedoraproject.org
>> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: 
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>> Do not reply to spam, report it: 
>> https://pagure.io/fedora-infrastructure/new_issue
>
> _______________________________________________
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
>
>
> _______________________________________________
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to