Arch Linux

KuriyamaMirai

Member

Registered: 2017-11-23

Posts: 12

[SOLVED] Problem with systemd-networkd on auto connecting wifi network

I think this is Networking problem but since I just used Arch about 3 weeks so it will be better to post on Newbie corner
I'm switching from netctl to wpa_supplicant and able to use wifi through wpa by configed it according to wiki
But using systemd-networkd to auto connect on boot is not working, it also makes 90s timeout on boot and I need use wpa_supplicant by hand
This is what I did:

# Connect wifi by using wpa_supplicant after created wpa_supplicant.conf file
wpa_supplicant -B -i wlp3s0 -c<(wpa_passphrase My_wifi My_wifi_password)
dhcpcd wlp3s0
# Confige systemd-networkd
systemctl enable systemd-networkd # I use google dns so I'm not enable systemd-resolved
systemctl enable wpa_supplicant@.service
# Create /etc/systemd/network/wlp3s0.network
[Match]
Name=wlp3s0

[Network]
DHCP=ipv4

Also try WonderWoofy solution but not work, since I did't use systemd-resolved so I did not create link to /etc/resolv.conf
with 90s timeout, I found this thread: https://bbs.archlinux.org/viewtopic.php?id=166607 and https://bbs.archlinux.org/viewtopic.php?id=224001, but it's not helped because I already disabled my netctl profile, there are also other threads about this issue but it's mainly because systemd version.
More details:

# List of enabled service:

UNIT FILE                             STATE  
autovt@.service                       enabled
dbus-org.freedesktop.network1.service enabled
display-manager.service               enabled
getty@.service                        enabled
lightdm.service                       enabled
nftables.service                      enabled
ntpd.service                          enabled
systemd-networkd-wait-online.service  enabled
systemd-networkd.service              enabled
wpa_supplicant@.service               enabled
systemd-networkd.socket               enabled
remote-fs.target                      enabled

12 unit files listed.

# Output of journalctl -xf
Dec 10 19:30:46 Mashiro kernel: ACPI Error: Needed type [Reference], found [Integer] ffff8a9b250ef2d0 (20170728/exresop-103)
Dec 10 19:30:46 Mashiro kernel: ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20170728/dswexec-461)
Dec 10 19:30:46 Mashiro kernel: ACPI Error: Method parse/execution failed \_PR.CPU0._PDC, AE_AML_OPERAND_TYPE (20170728/psparse-550)
Dec 10 19:30:49 Mashiro kernel: ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x000000003) is beyond end of object (length 0x0) (20170728/exoparg2-430)
Dec 10 19:30:49 Mashiro kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.GFX0._DSM, AE_AML_PACKAGE_LIMIT (20170728/psparse-550)
Dec 10 19:30:49 Mashiro kernel: ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x000000003) is beyond end of object (length 0x0) (20170728/exoparg2-430)
Dec 10 19:30:49 Mashiro kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.GFX0._DSM, AE_AML_PACKAGE_LIMIT (20170728/psparse-550)
Dec 10 19:30:49 Mashiro kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.PEG0.PEGP._DSM, AE_AML_PACKAGE_LIMIT (20170728/psparse-550)
Dec 10 19:32:16 Mashiro systemd[1]: Timed out waiting for device sys-subsystem-net-devices-wlp3s0.conf.device.

# uname -a
Linux Mashiro 4.14.4-1-ARCH #1 SMP PREEMPT Tue Dec 5 19:10:06 UTC 2017 x86_64 GNU/Linux

Last edited by KuriyamaMirai (2017-12-10 13:51:08)

Slithery

Administrator

From: Norfolk, UK

Registered: 2013-12-01

Posts: 5,776

Re: [SOLVED] Problem with systemd-networkd on auto connecting wifi network

You have the wrong services enabled and the wrong filename for your wpa_supplicant.conf file. Please read...

https://wiki.archlinux.org/index.php/WP … systemd.29

---

No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

KuriyamaMirai

Member

Registered: 2017-11-23

Posts: 12

Re: [SOLVED] Problem with systemd-networkd on auto connecting wifi network

You have the wrong services enabled and the wrong filename for your wpa_supplicant.conf file. Please read...

https://wiki.archlinux.org/index.php/WP … systemd.29

Thank you, it worked
I think I did it but now I remembered,  I started wpa_supplicant@wlp3s0 when there are none wpa_supplicant-wlp3s0.conf, and when I created that file, I run wpa_supplicant@.service @_@

Last edited by KuriyamaMirai (2017-12-10 13:49:38)