View previous topic :: View next topic |
Author |
Message |
TakodaNotDakota n00b
Joined: 12 Oct 2023 Posts: 5
|
Posted: Thu Oct 12, 2023 9:08 pm Post subject: [SOLVED] Wireless interfaces aren't detected at boot |
|
|
Hi,
I'm having a peculiar situation with my setup. Wireless connection is unable to start at boot time but works fine when invoked after.
Code: |
* Setting hostname to Festivity from /etc/hostname ...
...
* Bringing up network interface lo
...
INIT: Entering runlevel: 3
* Starting chronyd ...
* Starting sysklogd ...
* Starting cronie ...
* Could not find a wireless interface
* ERROR: wpa_supplicant failed to start
* Starting DHCP Client Daemon ...
* Mounting network filesystems ...
* Starting seatd ...
* Starting local ...
|
After I log in, there is no connection. However, using the command
Code: | rc-service wpa_supplicant start |
starts it successfully and restores connection. What gives?
Last edited by TakodaNotDakota on Sat Oct 21, 2023 6:56 pm; edited 1 time in total |
|
Back to top |
|
|
CooSee Veteran
Joined: 20 Nov 2004 Posts: 1441 Location: Earth
|
Posted: Thu Oct 12, 2023 9:52 pm Post subject: |
|
|
Welcome to Gentoo,
Code: | rc-update add wpa_supplicant default |
look here https://wiki.gentoo.org/wiki/Wpa_supplicant#Using_OpenRC
have fun with Gentoo.
_________________ " Die Realität ist eine Illusion, die durch Mangel an ehrlicher Kommunikation entsteht "
---
" Der Mensch ist von Natur aus neugierig, was am Ende übrig bleibt ist die Gier " |
|
Back to top |
|
|
TakodaNotDakota n00b
Joined: 12 Oct 2023 Posts: 5
|
Posted: Thu Oct 12, 2023 9:57 pm Post subject: |
|
|
That is already in my config.
But now I just found out about this default value commented in:
Code: | # uncomment this if wpa_supplicant starts up before your network interface
# is ready and it causes issues
# rc_want="dev-settle"
|
That is probably what I want. Thank you for the help |
|
Back to top |
|
|
TakodaNotDakota n00b
Joined: 12 Oct 2023 Posts: 5
|
Posted: Thu Oct 12, 2023 10:19 pm Post subject: |
|
|
I apologize for double posting, but I attempted to implement it but it doesn't seem to work. Same errors still show up, and I still don't get a connection. |
|
Back to top |
|
|
CooSee Veteran
Joined: 20 Nov 2004 Posts: 1441 Location: Earth
|
Posted: Thu Oct 12, 2023 10:40 pm Post subject: |
|
|
TakodaNotDakota wrote: | I apologize for double posting, but I attempted to implement it but it doesn't seem to work. Same errors still show up, and I still don't get a connection. |
no problem
Code: | That is already in my config. |
my bad, i misread it again - this happens sometimes
is there any kind of informational output of dmesg at the end >>> type dmesg in terminal.
i hope someone else has better piece of advice, because last time i used WiFi is 25 years ago - my knowledge is not up to date !
_________________ " Die Realität ist eine Illusion, die durch Mangel an ehrlicher Kommunikation entsteht "
---
" Der Mensch ist von Natur aus neugierig, was am Ende übrig bleibt ist die Gier " |
|
Back to top |
|
|
TakodaNotDakota n00b
Joined: 12 Oct 2023 Posts: 5
|
Posted: Fri Oct 13, 2023 12:09 am Post subject: |
|
|
I try to provide only the relevant information. If I missed anything, I can give the full output, but naturally it's pretty long.
Code: | [ 10.316955] Loading firmware: mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin
[ 10.318087] mt7921e 0000:02:00.0: HW/SW Version: 0x8a108a10, Build Time: 20230526130917a
[ 10.327901] Loading firmware: mediatek/WIFI_RAM_CODE_MT7961_1.bin
[ 10.329535] mt7921e 0000:02:00.0: WM Firmware Version: ____010000, Build Time: 20230526130958
[ 10.353372] Bluetooth: hci0: Device setup in 143025 usecs
[ 10.353375] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[ 10.370895] Loading firmware: mediatek/WIFI_RAM_CODE_MT7961_1.bin |
...
Code: | [ 11.903129] 8021q: 802.1Q VLAN Support v1.8
[ 11.916712] Loading firmware: rtl_nic/rtl8168h-2.fw
[ 11.943796] Generic FE-GE Realtek PHY r8169-0-100:00: attached PHY driver (mii_bus:phy_addr=r8169-0-100:00, irq=MAC)
[ 12.147660] r8169 0000:01:00.0 enp1s0: Link is Down
[ 12.172152] mt7921e 0000:02:00.0 wlo1: renamed from wlan0 |
I type in:
Code: | doas rc-service wpa_supplicant start
doas (takoda@Festivity) password:
* Starting WPA Supplicant Daemon ...
Successfully initialized wpa_supplicant |
output continued
Code: | [ 46.277923] wlo1: authenticate with 1c:64:99:d5:33:0e
[ 46.411431] wlo1: send auth to 1c:64:99:d5:33:0e (try 1/3)
[ 46.416027] wlo1: authenticated
[ 46.420803] wlo1: associate with 1c:64:99:d5:33:0e (try 1/3)
[ 46.427567] wlo1: RX AssocResp from 1c:64:99:d5:33:0e (capab=0x411 status=0 aid=7)
[ 46.457215] wlo1: associated
[ 46.630695] IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready |
|
|
Back to top |
|
|
Logicien Veteran
Joined: 16 Sep 2005 Posts: 1555 Location: Montréal
|
Posted: Fri Oct 13, 2023 3:00 am Post subject: |
|
|
Quote: | * Could not find a wireless interface |
What's that mean is that the wifi have not been detected at the moment that the wpa_supplicant service start or do not have the name expected. In such a situation I put the wireless module needed and it's firmware in an initramfs. In this configuration the wifi is probe earlier in the boot process and can be up and running when wpa_supplicant want to use it.
Configuring the Linux kernel to have the wifi support in hard and not in module can be done too but it need the firmware in the kernel too. So the initramfs would not be needed for the wifi. Be sure that wpa_supplicant and the dhcp client use the right interface name wlo1 or wlan0. You can write a udev rule to force the interface name.
Start the wpa_supplicant service in the default runlevel can help for the interface to be detected before the service start. _________________ Paul |
|
Back to top |
|
|
TakodaNotDakota n00b
Joined: 12 Oct 2023 Posts: 5
|
Posted: Sat Oct 21, 2023 6:56 pm Post subject: |
|
|
I have great news: I solved the problem!
I had to configure https://wiki.gentoo.org/wiki/Netifrc . It started the interface and wpa_supplicant for me. |
|
Back to top |
|
|
|