You need to run "ifconfig -a" to show all interfaces including "down" network hardware, otherwise it defaults to only show up interfaces. On Wed, Feb 17, 2021 at 4:54 PM Paolo Galtieri <pgaltieri@xxxxxxxxx> wrote: > > I have a Dell XPS 15 9500 laptop. I've already listed other issues with > this laptop running Fedora 33. Here's a new one :( > > lspic -k shows the following: > > 0:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi > Subsystem: Rivet Networks Device 1651 > Kernel modules: iwlwifi > > lsmod shows the following: > > lsmod | grep iwl > iwlwifi 344064 0 > cfg80211 954368 1 iwlwifi > > So the appropriate wireless driver is loaded, however ifconfig shows the > following devices: > > enp0s20f0u1u4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > inet 192.168.10.2 netmask 255.255.255.0 broadcast 192.168.10.255 > inet6 fe80::7484:4652:d8fb:2914 prefixlen 64 scopeid 0x20<link> > ether 00:e0:4c:68:0b:68 txqueuelen 1000 (Ethernet) > RX packets 22169 bytes 20677661 (19.7 MiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 20374 bytes 7329505 (6.9 MiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 > inet 127.0.0.1 netmask 255.0.0.0 > inet6 ::1 prefixlen 128 scopeid 0x10<host> > loop txqueuelen 1000 (Local Loopback) > RX packets 25 bytes 3400 (3.3 KiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 25 bytes 3400 (3.3 KiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 > inet 192.168.122.1 netmask 255.255.255.0 broadcast > 192.168.122.255 > ether 52:54:00:d9:35:63 txqueuelen 1000 (Ethernet) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 0 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > vmnet1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > inet 192.168.203.1 netmask 255.255.255.0 broadcast > 192.168.203.255 > inet6 fe80::250:56ff:fec0:1 prefixlen 64 scopeid 0x20<link> > ether 00:50:56:c0:00:01 txqueuelen 1000 (Ethernet) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 142 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > vmnet8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > inet 172.16.96.1 netmask 255.255.255.0 broadcast 172.16.96.255 > inet6 fe80::250:56ff:fec0:8 prefixlen 64 scopeid 0x20<link> > ether 00:50:56:c0:00:08 txqueuelen 1000 (Ethernet) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 142 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > Note there is no wireless device listed. > > So what do I need to do to get wireless working on this laptop under Fedora? > > Paolo > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > 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@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
