Here's the sequence of commands.
This time, I used depmod and modprobe, but the results are the same as with insmod.


# find /lib -name "*.ko" | grep iw

/lib/modules/4.19.48/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko

/lib/modules/4.19.48/kernel/drivers/net/wireless/intel/iwlwifi/dvm/iwldvm.ko

/lib/modules/4.19.48/kernel/drivers/net/wireless/intel/iwlwifi/mvm/iwlmvm.ko


# depmod -a

# modprobe iwlwifi

# modprobe iwldvm

# modprobe iwlmvm


# lsmod | grep iw

iwlmvm                286720  0

iwldvm                147456  0

iwlwifi               217088  2 iwldvm,iwlmvm

led_class              16384  3 iwldvm,input_leds,iwlmvm


# lspci -v | grep -i iw

<nothing returned>


# dmesg | tail -3

[    9.567663] random: 7 urandom warning(s) missed due to ratelimiting

[  211.991313] Intel(R) Wireless WiFi driver for Linux

[  211.991313] Copyright(c) 2003- 2015 Intel Corporation



Best regards,
Dave

On Saturday, July 4, 2020, 02:08:45 PM CDT, Hans Bezemer <hbezemer@kliksafe.nl> wrote:


What's the output of 'lsmod | grep iw'?


On 20/07/03 06:04PM, david mccooey wrote:
>  I configured the kernel with iwlwifi, iwldvm, and iwlmvm as modules,and installed them using insmod.
> However, "lspci -v" does not show these lines:
> Kernel driver in use: iwlwifiKernel modules: iwlwifi
> It's as if the modules aren't really installed.
> Based on various online sources, I think I need a utility called "iw" to get thesemodules to be used by the kernel.
> I have other computers here (MacOS) that can use the WiFi network, butthere is no "prt-get" there, so how would I retrieve the "iw" package?If I can get it on the Mac, then I can load it onto a USB drive, and thenread that USB drive from CRUX.
> Best regards,Dave
>    On Wednesday, July 1, 2020, 9:53:38 PM CDT, david mccooey <dmccooey@att.net> wrote: 
> 
>  Thank you.
> I am doing this installation on a computer at work, and there is a firewall.
> The WiFi network does not have a firewall, so I am configuring a kernelwith the appropriate driver -- for the Intel Wi-Fi 6 AX200.
> Best regards,Dave    On Wednesday, July 1, 2020, 02:03:44 AM CDT, Fredrik <fredrik@rinnestam.se> wrote: 
> 
>  On 2020-07-01 04:22, david mccooey wrote:
> > Hello,
> >
> > rsync: failed to connect to crux.nu (213.132.101.140): Connection timed
> > out (110)
> > rsync error: error in socket IO (code 10) at clientserver.c(127)
> > [Receiver=3.1.3]
> > Error: Running rsync failed ()
> > Updating failed
> >
> > It then tries to get "opt" and "xorg", but they time out as well with
> > the same messages.
> >
> >
> > From the bash prompt, I can ping 213.132.101.140 or crux.nu without any
> > problem, so it does not appear to be a network issue.
>
> Yes it is. I'd bet your firewall doesn't allow rsync traffic
>
> > Any help would be appreciated.
> >
> > Thank you,
> >
> > Dave
>
>
> _______________________________________________
> CRUX mailing list
> CRUX@lists.crux.nu
> https://lists.crux.nu/mailman/listinfo/crux
>   

> _______________________________________________
> CRUX mailing list
> CRUX@lists.crux.nu
> https://lists.crux.nu/mailman/listinfo/crux


_______________________________________________
CRUX mailing list
CRUX@lists.crux.nu
https://lists.crux.nu/mailman/listinfo/crux