Re: wifi interface not up at boot

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, May 16, 2025 at 06:42:04AM +0200, Marco Moock wrote:
Am 16.05.2025 um 00:31:13 Uhr schrieb Jon LaBadie:

I can get the WiFi interface to connect to my network
but only with manual intervention.  The interface card
is an Intel BE201.  There is no wired ethernet interface.

Describe the steps you do to make it work.

After graphical login, right click NetworkManager applet icon.
From menu select "enable WiFi".

   OR

At command line, Virtual Terminal (no graphics) or terminal
emulator (Mate environment) type "nmcli r{adio} wifi on".

Any suggestions as to how to get the wifi card active and
connecting during boot?

First give system info:

sudo journalctl --dmesg

What, all 1200 lines?  On assumption the interface card messages
are wanted, here is a grep for "iwl" of the output just after boot.
(WiFi is not functioning)

<time> <host> kernel: iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
<time> <host> kernel: iwlwifi 0000:00:14.3: Detected crf-id 0x2001910, cnv-id 0x80930 wfpm id 0x80005b20
<time> <host> kernel: iwlwifi 0000:00:14.3: PCI dev 7740/00e4, rev=0x461, rfid=0x20112200
<time> <host> kernel: iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 7 BE201 320MHz
<time> <host> kernel: iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.4.196
<time> <host> kernel: iwlwifi 0000:00:14.3: loaded firmware version 96.44729d4e.0 bz-b0-fm-c0-96.ucode op_mode iwlmvm
<time> <host> kernel: iwlwifi 0000:00:14.3: Detected RF FM, rfid=0x20112200
<time> <host> kernel: iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
<time> <host> kernel: iwlwifi 0000:00:14.3: loaded PNVM version 752be616
<time> <host> kernel: iwlwifi 0000:00:14.3: base HW address: 88:f4:da:74:44:74
<time> <host> kernel: iwlwifi 0000:00:14.3 wlo1: renamed from wlan0

rfkill list

$ rfkill list
0: asus-wlan: Wireless LAN
	Soft blocked: yes
	Hard blocked: no
1: asus-bluetooth: Bluetooth
	Soft blocked: no
	Hard blocked: no
2: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
3: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

WiFi is functioning but the output is the same before I activated wifi

nmcli

$ nmcli
wlo1: connected to jgLAKEx
        "Intel Wi-Fi"
        wifi (iwlwifi), 86:59:57:78:47:1E, sw disabled, hw, mtu 1500
        ip4 default, ip6 default
        inet4 10.0.0.29/8
        route4 default via 10.0.0.1 metric 600
        route4 10.0.0.0/8 metric 600
        inet6 2601:5cf:8500:dd30::b155/128
        inet6 2601:5cf:8500:dd30:68e4:9496:68e:83d0/64
        inet6 2600:4040:401f:c100:fd0a:83aa:83c9:8eab/64
        inet6 fe80::c0b4:e539:c621:1089/64
        route6 2601:5cf:8500:dd30::b155/128 metric 600
        route6 fe80::/64 metric 1024
        route6 2601:5cf:8500:dd30::/64 metric 600
        route6 default via fe80::8e6a:8dff:fe4e:a32a metric 600
        route6 2600:4040:401f:c100::/64 metric 600
        route6 2600:4040:401f:c100::/56 via fe80::3ebd:c5ff:fe66:d32d metric 600
        route6 default via fe80::3ebd:c5ff:fe66:d32d metric 600

lo: disconnected
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

p2p-dev-wlo1: disconnected
        "p2p-dev-wlo1"
        wifi-p2p, sw disabled, hw

DNS configuration:
        servers: 10.0.0.12 10.0.0.1 8.8.8.8
        domains: labadie.us jgcomp.com jgcomp.org
        interface: wlo1

Obviously this is after WiFi was manually activated.

Here is output immediately after boot from a Virtual Terminal

$ nmcli
lo: disconnected
	"lo"
	loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

wlo1: unavailable
	"Intel Wi-Fi"
	wifi (iwlwifi), CE:F1:7C:61:56:E1, sw disabled, hw, mtu 1500

Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.

Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.


--
Jon H. LaBadie                  jonfu@xxxxxxxxxx
--
_______________________________________________
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, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux