You are not logged in.
Pages: 1
Synopsis: Copy the Arch ISO wifi profile located in /etc/netctl to the target and since it will reference the kernel version of the wifi device name I'll hack the target profile to reference the netctl version of the device name.
How do I copy the wifi config used during a new install to the target so that it automatically connects on first boot into the new system?
Last edited by KairiTech (2020-02-06 19:25:56)
Offline
What are you using to control your wifi?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
What are you using to control your wifi?
I connect using wifi-menu.
Offline
wifi-menu is part of netctl and netctl uses profiles to store/setup connection data.
https://wiki.archlinux.org/index.php/Netctl has info where those profiles are located .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Easy enough to copy the wifi profiles created by wifi-menu located in /etc/netctl to the new install then activate the wifi device like so...
systemctl enable netctl-auto@<device>.service
However, my wifi device shows up as wlan0 during the install but changes to wlp6s0 when I boot into the new system.
How do I get both the install wifi device and the new system wifi device to use the same device name?
Offline
The installation iso uses iwd which is configured to use the names provided by the kernel ( eth0 , eth1 , wlan0 etc ) .
On an installed archlinux systemd-udev renames the devices.
https://bbs.archlinux.org/viewtopic.php?id=251713 discusses this, for background info start on https://wiki.archlinux.org/index.php/Pe … ice_naming .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Very interesting reading. This is ugly and I think creating my own device naming rules is a bit extreme so I'll just hack the profile copied to the new install to reference the netctl version of the wifi device name that will show up there.
This in not scalable I know but it will do for now.
Last edited by KairiTech (2020-02-06 19:24:53)
Offline
Pages: 1