Please show:
ls -la /usr/lib/systemd/system/NetworkManager.service.d
cat /usr/lib/systemd/system/NetworkManager.service.d/*
ls -la /etc/NetworkManager/conf.d/
cat /etc/NetworkManager/conf.d/*
I appreciate your patience and help
`sudo systemctl start dhcpcd ✔
[sudo] password for gianluca:
~ ls -la /usr/lib/systemd/system/NetworkManager.service.d ✔ 8s
total 32
drwxr-xr-x 2 root root 4096 6 dic 23.07 .
drwxr-xr-x 21 root root 20480 13 dic 22.05 ..
-rw-r--r-- 1 root root 43 6 dic 23.07 50-iwd.conf
~ cat /usr/lib/systemd/system/NetworkManager.service.d/* ✔
[Unit]
Wants=iwd.service
After=iwd.service
~ ls -la /etc/NetworkManager/conf.d/ ✔
total 8
drwxr-xr-x 2 root root 4096 11 ago 2022 .
drwxr-xr-x 7 root root 4096 9 nov 00.20 ..
~ cat /etc/NetworkManager/conf.d/* ✔
zsh: no matches found: /etc/NetworkManager/conf.d/*
`
1 Like
Remove that file:
sudo rm -f /usr/lib/systemd/system/NetworkManager.service.d/50-iwd.conf
Restart the service:
sudo systemctl restart NetworkManager
Just to explain: dhcpcd.service, NetworkManager.service and iwd.service are in conflict when running. So only run one of at a time.
Keep sure that dhcpcd.service and iwd.service is not running.
1 Like
Thanks for the clear explanation, I understand.
I tried those commands, it also suggested to restart the daemon, I tried and rebooted, still the same situation. Doesn’t work
Thank you for the unclear description: “Doesn’t work.” Very helpful, really. Did you anything else beside these 2 commands? Show what you did on the terminal for example. That what be much more helpful, since as you said:
I only followed your instructions, I did not do anything else
sudo rm -f /usr/lib/systemd/system/NetworkManager.service.d/50-iwd.conf ✔ 9s
~ sudo systemctl restart NetworkManager ✔
~
no reactions in terminal as you can see.
by “It doesn’t work, same situation” I meant that I need to start dhcpcd to get connected and that networkmanager doesn’t show any connection. also the icon is inactive
Please provide the output of:
systemctl status iwd.service
systemctl status dhcpcd.service
systemctl status NetworkManager.service
If all of these are enabled, disable the first two, like this:
systemctl disable iwd.service
systemctl disable dhcpcd.service
After a reboot NetworkManager should be the only one of these running – now, continue troubleshooting your NetworkManager configuration with the help and advice of forum members.
This assumes you have another computer available to connect to Internet, as needed. That is all.
sudo systemctl status iwd.service ✔
[sudo] password for gianluca:
Sorry, try again.
[sudo] password for gianluca:
● iwd.service - Wireless service
Loaded: loaded (/usr/lib/systemd/system/iwd.service; disabled; preset: disabled)
Drop-In: /usr/lib/systemd/system/iwd.service.d
└─50-networkmanager.conf
Active: active (running) since Sun 2023-12-17 09:44:16 CET; 1min 3s ago
Docs: man:iwd(8)
man:iwd.config(5)
man:iwd.network(5)
man:iwd.ap(5)
Main PID: 530 (iwd)
Tasks: 1 (limit: 18690)
Memory: 2.2M
CPU: 23ms
CGroup: /system.slice/iwd.service
└─530 /usr/lib/iwd/iwd
dic 17 09:44:16 gianluca-latitude5410 iwd[530]: Max HE RX <= 160MHz MCS: 0-11 for NSS: 2
dic 17 09:44:16 gianluca-latitude5410 iwd[530]: Max HE TX <= 160MHz MCS: 0-11 for NSS: 2
dic 17 09:44:16 gianluca-latitude5410 iwd[530]: Interface Types: station
dic 17 09:44:16 gianluca-latitude5410 iwd[530]: Max HE RX <= 80MHz MCS: 0-11 for NSS: 2
dic 17 09:44:16 gianluca-latitude5410 iwd[530]: Max HE TX <= 80MHz MCS: 0-11 for NSS: 2
dic 17 09:44:16 gianluca-latitude5410 iwd[530]: Max HE RX <= 160MHz MCS: 0-11 for NSS: 2
dic 17 09:44:16 gianluca-latitude5410 iwd[530]: Max HE TX <= 160MHz MCS: 0-11 for NSS: 2
dic 17 09:44:16 gianluca-latitude5410 iwd[530]: Ciphers: BIP-GMAC-256 BIP-GMAC-128 GCMP-256 GCMP-128
dic 17 09:44:16 gianluca-latitude5410 iwd[530]: BIP-CMAC-128 CCMP-128 TKIP
dic 17 09:44:16 gianluca-latitude5410 iwd[530]: Supported iftypes: ad-hoc station ap p2p-client p2p-go p2p-device
~ sudo systemctl status dhcpcd.service ✔ 17s
○ dhcpcd.service - DHCP/ IPv4LL/ IPv6RA/ DHCPv6 client on all interfaces
Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; disabled; preset: disabled)
Active: inactive (dead)
~ sudo systemctl status networkmanager.service 3 ✘
Unit networkmanager.service could not be found.
I did disable iwd and dhcpcd after this outcome, rebooted but same situation as seen above with networkmanager inactive and must start dhcpcd to connect
It’s NetworkManager.service.
That’s my fault; I typed the commands hurriedly and led the OP astray.
As @zbe states, it should be NetworkManager.service;
Capitalization is important in Linux, wherever it’s required.
This also raises the importance of examining everything before using copy/paste. It should perhaps have been obvious that all references to NetworkManager.service before and after my typed command, did include the capitals as required.
sudo systemctl status NetworkManager.service ✔
[sudo] password for gianluca:
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: disabled)
Active: active (running) since Sun 2023-12-17 09:44:16 CET; 35min ago
Docs: man:NetworkManager(8)
Main PID: 480 (NetworkManager)
Tasks: 4 (limit: 18690)
Memory: 19.3M
CPU: 644ms
CGroup: /system.slice/NetworkManager.service
└─480 /usr/bin/NetworkManager --no-daemon
dic 17 09:44:16 gianluca-latitude5410 systemd[1]: Started Network Manager.
dic 17 09:44:16 gianluca-latitude5410 NetworkManager[480]: <info> [1702802656.5892] Wi-Fi P2P device added on phy0
dic 17 09:44:16 gianluca-latitude5410 NetworkManager[480]: <info> [1702802656.5895] manager: (/net/connman/iwd/0): new 802.11 Wi-Fi P2P device (/org/freedesktop>
dic 17 09:44:16 gianluca-latitude5410 NetworkManager[480]: <info> [1702802656.5903] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/D>
dic 17 09:44:16 gianluca-latitude5410 NetworkManager[480]: <info> [1702802656.5930] device (wlan0): new IWD device state is disconnected
dic 17 09:44:16 gianluca-latitude5410 NetworkManager[480]: <warn> [1702802656.5939] device (/net/connman/iwd/0): not in expected unavailable state!
dic 17 09:44:16 gianluca-latitude5410 NetworkManager[480]: <info> [1702802656.6777] device (wlan0): new IWD device state is connecting
dic 17 09:44:16 gianluca-latitude5410 NetworkManager[480]: <info> [1702802656.7800] device (wlan0): new IWD device state is connected
dic 17 09:44:30 gianluca-latitude5410 NetworkManager[480]: <info> [1702802670.1230] manager: NetworkManager state is now ASLEEP
dic 17 09:44:30 gianluca-latitude5410 NetworkManager[480]: <info> [1702802670.1280] agent-manager: agent[aa16cd4ebc3cf4df,:1.33/org.kde.plasma.networkmanagement>
lines 1-21/21 (END)
My fault, you guys just nicely helping
sudo systemctl disable iwd.service ✔
[sudo] password for gianluca:
~ sudo systemctl disable dhcpcd.service ✔ 6s
~ sudo systemctl restart NetworkManager.service
after reboot, exactly same situation
Let me ask; how are you connecting to Internet usually? Is it via a WiFi capable Modem/Router connected to your ISP? If you have a network cable you could physically connect to the router in the meantime.
Now, with the capitalization issue solved, here is the difficulty which might be preventing much progress: It is possible; and likely; that running an instance of dhcpcd.service is conflicting with NetworkManager.service – as @megavolt has already indicated – as both should not be active at the same time under normal circumstances. However, NetworkManager.service does appear to be operating as expected.
A few questions that might help:
- Are you using a firewall that might be blocking connection? If so, disable it temporarily, reboot if needed, and test again.
- Which kernel was the
ax201working with previously? - Have you tried reverting to that kernel to see if it still works? If not, try it, and report back with the results.
Have you tried the latest 6.6.7-1 kernel? If not, try it, and report back with the results. - And finally; Never having problems with the
ax201in Manjaro doesn’t mean you never will. It’s possible that it’s taking an early retirement. Can you test the card with another OS, or another computer?
ok, I connect through my phone hotspot. I don’t have a modem or internet at home. I have had the same PC with manjaro, phone and provider for last few years, all was very stable.
It started with last upgrade, I’m using 6.6.7-1, before 6.1.68-1. I try to stick with LTS as both are.
-
I disabled firewall, rebooted… no change
-
I reverted to 6.1, no change
-
as for the card, it’s working when I sudo systemctl restart dhcpcd (like right now)
It’s NetworkManager …when I go on the icon with mouse pointer, it says inactive and when I click wifi is on but no wireless connections show
OK. I’m unable to help with this scenario. I had assumed you were using your phone as a hotspot out of desperation, than much else.
At least now there’s a little more information that might help others.
Good luck.
Aside:- I found another active thread NetworkManager is not running, which might (or might not) be worth monitoring. Cheers.
1 Like
what does your iptables says:
systemctl status iptables
are else the full list:
systemctl list-unit-files|less
sorry about the delay, never got a notification about your message
anyways…
systemctl status iptables ✔
○ iptables.service - IPv4 Packet Filtering Framework
Loaded: loaded (/usr/lib/systemd/system/iptables.service; disabled; preset: disabled)
Active: inactive (dead)
UNIT FILE STATE PRESET
proc-sys-fs-binfmt_misc.automount static -
-.mount generated -
boot-efi.mount generated -
dev-hugepages.mount static -
dev-mqueue.mount static -
proc-fs-nfsd.mount static -
proc-sys-fs-binfmt_misc.mount disabled disabled
sys-fs-fuse-connections.mount static -
sys-kernel-config.mount static -
sys-kernel-debug.mount static -
sys-kernel-tracing.mount static -
tmp.mount generated -
var-lib-machines.mount static -
var-lib-nfs-rpc_pipefs.mount static -
var-lib-snapd-snap-core18-2566.mount enabled disabled
var-lib-snapd-snap-snapd-16778.mount enabled disabled
cups.path enabled disabled
gpm.path static -
ostree-finalize-staged.path disabled disabled
systemd-ask-password-console.path static -
systemd-ask-password-wall.path static -
session-2.scope transient -
accounts-daemon.service disabled disabled
acpid.service disabled disabled
alsa-restore.service static -
alsa-state.service static -
apparmor.service disabled disabled
archlinux-keyring-wkd-sync.service static -
auditd.service disabled disabled
auth-rpcgss-module.service static -
autovt@.service alias -
avahi-daemon.service disabled disabled
avahi-dnsconfd.service disabled disabled
blk-availability.service disabled disabled
bluetooth-mesh.service disabled disabled
bluetooth.service enabled disabled
:
Ya, I guess I’m out as well…
Check back with Official Update News about other Kernel Version [ Stable Update ]
Make sure you can get NetworkManager running through the Wiki config info
The output off systemctl list-unit-files|less should be around 540 lines, but with that you can see what’s running in the background and start / stop programs that mayd be in conflict with your Wireless.
To show the full list, this would work, then you are just have to post back the link:
systemctl list-unit-files | curl -s --data-binary @- 'https://paste.c-net.org/'
My issues were Bluetooth, sometime Portmaster and iptables ones.
A GUI Software for that is pamac build stacer from the AUR
- Service
- only toggle the
Running nowcolumn. - not the
Startup at bootsection, only if you are sure that is really the problem, but maybe then still let us know first.
But all this is more a thinker option.
Otherwise, backup your stuffs, maybe it’s time to restore to a previous point. timeshift
I read your post during the night and didn’t understand a thing
this morning it was easier after coffee and clear mind, well not that I understood much))) but was able to get the info at this link
1 Like
Try
sudo systemctl disable --now systemd-networkd.service
sudo systemctl enable --now NetworkManager