[SOLVED] net.wlp2s0 has started, but is inactive

[Torpus]

Hello,

When I turn on Gentoo on hardware, the wpa_supplicant daemon starts, but says:

Code: Select all

 * WARNING: net.wlp2s0 has started, but is inactive

Now when I try connecting to some Wi-Fi network, it says this:

Code: Select all

# wpa_supplicant -B -i wlp2s0 -c /etc/wpa_supplicant/wpa_supplicant-wlp2s0.conf
Successfully initialized wpa_supplicant
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
ctrl_iface exists and seems to be in use - cannot override it
Delete '/run/wpa_supplicant/wlp2s0' manually if it is not used anymore
Failed to initialize control interface '/run/wpa_supplicant/'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.

wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0

I can't ping, whether if I put a domain or the IP address directly

I'll be glad to give you any additional info if needed

Please help me with this, I'm struggling to fix it for days and I'm still stuck.

[kimchi_sg]

Code: Select all

ctrl_iface exists and seems to be in use - cannot override it
Delete '/run/wpa_supplicant/wlp2s0' manually if it is not used anymore

What happens when you try to follow the above instruction?

Code: Select all

rm -rf /run/wpa_supplicant/wlp2s0
ls -l /run/wpa_supplicant

[Torpus]

It got some error removed, but apparently there's still another:

Code: Select all

# rm -rf /run/wpa_supplicant/wlp2s0
# ls -l /run/wpa_supplicant
total 0
# wpa_supplicant -B -i wlp2s0 -c /etc/wpa_supplicant/wpa_supplicant-wlp2s0.conf
Successfully initialized wpa_supplicant
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured

I still can't ping:

Code: Select all

# ping 209.51.188.116
PING 209.51.188.116 (209.51.188.116) 56(84) bytes of data.
From 192.168.0.10 icmp_seq=1 Destination Host Unreachable
From 192.168.0.10 icmp_seq=2 Destination Host Unreachable
From 192.168.0.10 icmp_seq=3 Destination Host Unreachable
From 192.168.0.10 icmp_seq=4 Destination Host Unreachable
From 192.168.0.10 icmp_seq=5 Destination Host Unreachable
From 192.168.0.10 icmp_seq=6 Destination Host Unreachable
^C
--- 209.51.188.116 ping statistics ---
7 packets transmitted, 0 received, +6 errors, 100% packet loss, time 6128ms
pipe 4
# ping gnu.org
ping: gnu.org: Temporary failure in name resolution

Am I still using two wpa_supplicant's or something?

[grknight]

Why are you trying to rerun wpa_supplicant when netifrc (net.wlp2s0) already has apparently done so?

To see when this connects, look into dmesg. Perhaps it is misconfigured in /etc/wpa_supplicant/wpa_supplicant-wlp2s0.conf.

What is in /etc/conf.d/net?

[Torpus]

I tried rerunning it because this is how I believed connecting to a Wi-Fi on the terminal is like. But you're right it automatically connects once it boots up (my phone says that) but I still can't ping or anything.
I think the issue is that there're dhcpcd and wpa_supplicant daemons that start on boot before net.wlp2s0 itself which causes the conflict, what is weird is that despite I did

Code: Select all

rc-update del dhcpcd default
rc-update del wpa_supplicant default

I'm still notified that these daemons start AGAIN before net.wlp2s0 whenever I boot up my Gentoo:

Code: Select all

 * Starting DHCP Client Daemon ...
 * Loading module amdgpu ...
insmod /lib/modules/6.4.11-gentoo/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko
modprobe: ERROR: could not insert 'amdgpu': Invalid argument
 * Setting system clock using the hardware clock [UTC] ...
 * Mounting misc binary format filesystem ...
 * Loading custom binary format handlers ...
 * Updating /etc/fstab: parse error at line 2 -- ignored
 * Configuring kernel parameters ...
 * Creating user login records ...
 * Wiping /tmp directory ...
 * Setting hostname to genbox from /etc/conf.d/hostname ...
 * Setting terminal encoding [UTF-8] ...
 * Loading key mappings [us] ...
 * Bringing up network interface lo ...
 * Saving key mapping ...
 * Saving terminal encoding ...
 * Seeding random number generator ...
 * Seeding 256 bits and crediting ...
 * Saving 256 bits of creditable seed for next boot ...
 * Create Volatile Files and Directories ...
INIT: Entering runlevel: 3
 * Starting dbus ...
 * Bringing up interface wlp2s0
 *   Caching network module dependencies
 *   Starting wpa_supplicant on wlp2s0 ...
Successfully initialized wpa_supplicant
 *   Starting wpa_cli on wlp2s0 ...
 *   Backgrounding ... ...
 * WARNING: net.wlp2s0 has started, but is inactive
 * WARNING: netmount will start when net.wlp2s0 has started
 * Starting local ...

I just can't get it.

Also, I have no idea how can I look into dmesg.

Here's my /etc/conf.d/net:

Code: Select all

modules="wpa_supplicant"
config_wlp2s0="dhcp"

Looks pretty simple, that's literally all of it. It might have something missing.

[grknight]

Please show the output of rc-status -a.

I ask to see this as it looks like dhcpcd in staring in the boot runlevel which is rather unexpected.

[Torpus]

Ah thanks!! dhcpcd was on sysinit instead of default while wpa_supplicant said it's inactive, I killed them both with rc-update and now net.wlp2s0 doesn't complain and connects to my Wi-Fi once it boots.

But my Gentoo still can't reach the internet for some reason:

Code: Select all

~ # ping 209.51.188.116
ping: connect: Network is unreachable
~ # ping gnu.org
ping: gnu.org: Temporary failure in name resolution

The internet will work normally if I just chrooted into Gentoo from a Linux Mint Live USB connected to Wi-Fi, but I want Wi-Fi to work on hardware

[mrbassie]

Ah thanks!! dhcpcd was on sysinit instead of default while wpa_supplicant said it's inactive, I killed them both with rc-update and now net.wlp2s0 doesn't complain and connects to my Wi-Fi once it boots.

But my Gentoo still can't reach the internet for some reason:

Code: Select all

~ # ping 209.51.188.116
ping: connect: Network is unreachable
~ # ping gnu.org
ping: gnu.org: Temporary failure in name resolution

The internet will work normally if I just chrooted into Gentoo from a Linux Mint Live USB connected to Wi-Fi, but I want Wi-Fi to work on hardware

What's your dns source?

[NeddySeagoon]

Torpus,

You don't start dhcpcd or wpa_supplicant in any runlevel at all.
Your net file

Code: Select all

modules="wpa_supplicant"
config_wlp2s0="dhcp"

does that when wlp2s0 starts.

To see dmesg, try

Code: Select all

dmesg --color=always | less

Run

Code: Select all

dmesg > /dmesg.txt

Get a working network connection and post that file onto a pastebin site.

[Torpus]

It's weird but my resolv.conf is empty!!

At first I used to have this only:

Code: Select all

nameserver 127.0.0.53

But when I had these Wi-Fi issues before asking what to do I simply went through my Mint Live USB and copy-pasted what was in its own resolv.conf:

Code: Select all

nameserver 127.0.0.53
options edns0 trust-ad
search .

Yet as I said for some reasons all these lines got deleted by themselves.

Here's my dmesg.txt

[NeddySeagoon]

Torpus,

iwlwifi looks good as far as

Code: Select all

[    2.807673] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0

but then nothing tries to start it.

What does

Code: Select all

/etc/init.d/net.wlp2s0 start

If its already running, use restart.

dmesg should add lines mentioning associated and authenticated. It may even JustWork :)

[Torpus]

I fixed the DNS issue once again in resolv.conf, now the internet can work by chrooting through a Live USB.

But Wi-Fi still doesn't work on hardware.

When I

Code: Select all

/etc/init.d/net.wlp2s0 start

I get this:

Code: Select all

 * Bringing up interface wlp2s0
 *   Starting wpa_supplicant on wlp2s0 ...
Successfully initialized wpa_supplicant
 *   Starting wpa_cli on wlp2s0 ...
 *   Backgrounding ...
 * WARNING: net.wlp2s0 has started, but is inactive

Now in this time the laptop doesn't even connect to my Wi-Fi hotspot which is the phone (it says that) even though that Wi-Fi is already in wpa_supplicant/wpa_supplicant-wlp2s0.conf where the SSID and passphrase are stored.

I'm trying to struggle with this for almost an entire week and this issue still seems too ambiguous to me as I have no clue what can be the problem(s)

I believe that there are many issues as we've seen at the beginning with the dhcpcd daemon since I'm a n00b

[NeddySeagoon]

Torpus,

That's all good.

After

Code: Select all

/etc/init.d/net.wlp2s0 start

what is added to the end of dmesg?

There should be signs of wlp2s0 at least trying to start and maybe error messages explaining why not.

Pastebin all of dmesg if you like.

/etc/resolv.conf will be populated by dhcpcd, so it will sort itself out before you need it.

[Torpus]

Here you go https://pastebin.com/5trcXKkQ :)

[NeddySeagoon]

Torpus,

Code: Select all

[   51.401936] warning: `iwconfig' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[   55.136693] wlp2s0: authenticate with 14:a3:64:d5:5d:7d
[   55.136712] wlp2s0: 80 MHz not supported, disabling VHT
[   55.142570] wlp2s0: send auth to 14:a3:64:d5:5d:7d (try 1/3)
[   55.148729] wlp2s0: authenticated
[   55.149636] wlp2s0: associate with 14:a3:64:d5:5d:7d (try 1/3)
[   55.153715] wlp2s0: RX AssocResp from 14:a3:64:d5:5d:7d (capab=0x411 status=0 aid=1)
[   55.163930] wlp2s0: associated
[   55.213191] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready

That's the hard bit done. The kernel is correct.

Code: Select all

[   55.148729] wlp2s0: authenticated
[   55.163930] wlp2s0: associated
[   55.213191] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready

The radio link is working but it didn't ask for any configuration ... so it didn't get any.

Do that bit again, then do

Code: Select all

dhcpcd  wlp2s0

and it should work until the dhcp lease expires.

That's what

Code: Select all

config_wlp2s0="dhcp"

in the net file should do

[pietinger]

Torpus,

I see you have configured your kernel self and you are missing the package: net-wireless/wireless-regdb, because of:

Code: Select all

[    0.840039] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    0.841504] cfg80211: failed to load regulatory.db

Because this is done before your dracut initrmafs starts at timestamp:

Code: Select all

[    1.395100] Run /init as init process
[    1.396604]   with arguments:
[    1.396608]     /init
[    1.396612]   with environment:
[    1.396615]     HOME=/
[    1.396619]     TERM=linux
[    1.396622]     BOOT_IMAGE=/vmlinuz-6.4.11-gentoo

[    1.573218] dracut: Gentoo-2.14

this means: You have configured it static into your kernel, So you must add it also into CONFIG_EXTRA_FIRMWARE.
See here: https://wiki.gentoo.org/wiki/Wi-Fi#Kernel (in IMPORTANT box)


P.S.: Of course it is easier to change it to <M>odule (but you must emerge wireless-regdb also):

Code: Select all

[*] Networking support  --->
    [*] Wireless  --->
        <M>   cfg80211 - wireless configuration API

        <M>   Generic IEEE 802.11 Networking Stack (mac80211)

[Torpus]

I just turned both of these options to modules and recompiled my kernel and installed that package, but I still see no difference on hardware when I try connecting:

Code: Select all

~ # /etc/init.d/net.wlp2s0 start
 * Bringing up interface wlp2s0
 *   Caching network module dependencies # this just came out and wasn't there
 *   Starting wpa_supplicant on wlp2s0 ...
Successfully initialized wpa_supplicant
 *   Starting wpa_cli on wlp2s0 ...
 *   Backgrounding ...
 * WARNING: net.wlp2s0 has started, but is inactive # my hotspot says that the laptop's connected
~ # dhcpcd wlp2s0
sending commands to dhcpcd process
~ # ping gentoo.org
ping: gentoo.org: Temporary failure in name resolution
~ # ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 192.168.0.10 icmp_seq=1 Destination Host Unreachable # same errors here
From 192.168.0.10 icmp_seq=2 Destination Host Unreachable
From 192.168.0.10 icmp_seq=3 Destination Host Unreachable
^C
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4105ms
pipe 4

Here's a new dmesg

This is more complicated than I've ever thought

[pietinger]

In your kernel is now everything (for WiFi) okay:

Code: Select all

[    2.926183] cfg80211: Loading compiled-in X.509 certificates for regulatory database

[    2.954730] Loading firmware: regulatory.db
[    2.955624] Loading firmware: regulatory.db.p7s

[    2.971722] Intel(R) Wireless WiFi driver for Linux
[    2.971846] iwlwifi 0000:02:00.0: enabling device (0000 -> 0002)
[    2.972975] iwlwifi 0000:02:00.0: Detected crf-id 0xbadcafe, cnv-id 0x10 wfpm id 0x80000000
[    2.972994] iwlwifi 0000:02:00.0: PCI dev 24fd/0110, rev=0x230, rfid=0xd55555d5
[    2.973053] Loading firmware: iwlwifi-8265-36.ucode
[    2.979122] iwlwifi 0000:02:00.0: loaded firmware version 36.ca7b901d.0 8265-36.ucode op_mode iwlmvm
[    3.036529] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230

[    3.095596] iwlwifi 0000:02:00.0: base HW address: b8:9a:2a:33:98:89, OTP minor version: 0x0
[    3.170885] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[    3.174909] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0

[    5.307128] iwlwifi 0000:02:00.0: Registered PHC clock: iwlwifi-PTP, with index: 0

But later there is a problem (or not?) in userspace:

Code: Select all

[   37.663093] warning: `iwconfig' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[   41.406052] wlp2s0: authenticate with 14:a3:64:d5:5d:7d
[   41.406078] wlp2s0: 80 MHz not supported, disabling VHT
[   41.412129] wlp2s0: send auth to 14:a3:64:d5:5d:7d (try 1/3)
[   41.418451] wlp2s0: authenticated
[   41.419476] wlp2s0: associate with 14:a3:64:d5:5d:7d (try 1/3)
[   41.423627] wlp2s0: RX AssocResp from 14:a3:64:d5:5d:7d (capab=0x411 status=0 aid=1)
[   41.426278] wlp2s0: associated
[   41.477661] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready

Here I must give over to our expert Neddy ... or grknight ... or ...

[Torpus]

After re-configuring and re-emerging the kernel as you suggested, I still get the same errors.

Code: Select all

/etc/init.d/net.wlp2s0 start
dhcpcd  wlp2s0

Say exactly the same thing as before (and I wonder why net.wlp2s0 doesn't start as a daemon anymore)

At first after the kernel re-emerge, WLAN were disabled by rfkill, I just enabled all but later net.wlp2s0 says the same thing.

My WiFi hotspot this time doesn't say I'm connected to it or anything, weird.

It's for you to solve, Neddy :)

Here's my most recent dmesg

[pietinger]

hmm ... no progress here ...

Let me see what I can do. First let me say you can have only netifrc OR networkmanager active. So, please show us what you have activated at system start with:

Code: Select all

# rc-update

Maybe you want read: https://wiki.gentoo.org/wiki/Network_management
Next question: Do you use iwd OR wpa_supplicant ? (I recommend iwd)
Please show us all

Code: Select all

# ls -al /etc/init.d/net*

and its content.

[Torpus]

I used to have both netifrc and networkmanager, I removed netifrc and configured network manager following the Wiki, I did also add dnsmasq for more security but I'm afraid this would result to possible more issues.

I was jumping from Network Management to dnsmasq and iwd guides on the Wiki... I felt like I messed up things even more (hopefully not). It was just confusing and took some time.

wpa_supplicant was the default one which I removed it for iwd as suggested, the Wiki suggested also to remove dhcpc for configuring networkmanager

Here you get these:

Code: Select all

/ # rc-update   
       NetworkManager |      default                           
               binfmt | boot                                   
             bootmisc | boot                                   
              cgroups |                                 sysinit
                 dbus |      default                           
                devfs |                                 sysinit
                dmesg |                                 sysinit
              dnsmasq |      default                           
              elogind | boot                                   
                 fsck | boot                                   
                  gpm |      default                           
             hostname | boot                                   
              hwclock | boot                                   
                  iwd |      default                           
              keymaps | boot                                   
            killprocs |                        shutdown        
    kmod-static-nodes |                                 sysinit
                local |      default nonetwork                 
           localmount | boot                                   
             loopback | boot                                   
              modules | boot                                   
             mount-ro |                        shutdown        
                 mtab | boot                                   
             netmount |      default                           
               procfs | boot                                   
                 root | boot                                   
         save-keymaps | boot                                   
    save-termencoding | boot                                   
            savecache |                        shutdown        
              seedrng | boot                                   
                 swap | boot                                   
               sysctl | boot                                   
                sysfs |                                 sysinit
 systemd-tmpfiles-setup | boot                                   
 systemd-tmpfiles-setup-dev |                                 sysinit
         termencoding | boot                                   
                 udev |                                 sysinit
         udev-trigger |                                 sysinit

Code: Select all

/ # ls -al /etc/init.d/net*     
-rwxr-xr-x 1 root root 2285 Aug 23 18:25 /etc/init.d/net-online
lrwxrwxrwx 1 root root    6 Aug 23 22:09 /etc/init.d/net.wlp2s0 -> net.lo # this one is red with a white text that turns on and off for some reason
-rwxr-xr-x 1 root root 2067 Aug 23 18:25 /etc/init.d/netmount

edit: When I turn on Gentoo on hardware it says that NetworkManager has started but is inactive. Here's my dmesg

[NeddySeagoon]

Torpus,

You newest dmesg does not show any sign of WiFi trying to associate or authenticate.
It's not like it tried and failed - it didn't try.

Its worse than than that iwlwifi appears to be as ready as a coiled spring but wlan0 does not exist.
It won't appear in

Code: Select all

ifconfig -a

udev will rename that to something unpredictable like wlp2s0 but not until it exists.

That has to be kernel. How are you configuring building and installing your kernel?

Code: Select all

[    0.000000] Linux version 6.4.11-gentoo (root@mintbox) (gcc (Gentoo Hardened 12.3.1_p20230526 p2) 12.3.1 20230526, GNU ld (Gentoo 2.40 p5) 2.40.0) #13 SMP PREEMPT_DYNAMIC Sat Sep  2 13:55:39 +01 2023

That's your 13th kernel build of 6.4.11-gentoo from Sat Sep 2 13:55:39 +01 2023.

dmesg does not have any missing or duplicate symbol errors either - they indicate mixing and matching several kernel builds, which is normally a bad idea

Pastebin your entire kernel config file and describe your kernel build process from the start until the reboot.
Dan't skip the boot loader update.

[pietinger]

Neddy,

the strange thing is that kernel was already right before !?

@Torpus

may I suggest two things:

1. Work without dnsmasq until your wifi connection works correct.
2. Always listen to Neddy

(Because I am a netifrc man I cannot help with networkmanager; but you surely will get help from our experts)

[NeddySeagoon]

pietinger,

Until the interface appears, nothing else matters.
Yes - the kernel was OK but its not now :)

I don't use NetworkManager either - I still rub two sticks together.

[pietinger]

Until the interface appears, nothing else matters.

Yes - of course !

I don't use NetworkManager either - I still rub two sticks together.

And: Thanks a lot for takeover !