Package Details: mkinitcpio-wifi 0.3-1

Git Clone URL: https://aur.archlinux.org/mkinitcpio-wifi.git (read-only, click to copy)
Package Base: mkinitcpio-wifi
Description: mkinitcpio hook to enable wifi remote access
Upstream URL: https://aur.archlinux.org/packages/mkinitcpio-wifi/
Licenses: GPL
Submitter: tequa
Maintainer: tequa
Last Packager: tequa
Votes: 1
Popularity: 0.000000
First Submitted: 2019-07-24 18:01 (UTC)
Last Updated: 2020-03-30 17:15 (UTC)

Latest Comments

sam_vde commented on 2023-11-04 18:46 (UTC)

Hi

Many, many thanks for your work on this! I run this hook on my laptop and I really enjoy being able to remotely reboot and unlock the fully encrypted device as needed.

Now, I have the rare case where my kernel wifi device name is actually mlan0 instead of wlan0 (https://github.com/torvalds/linux/blob/master/drivers/net/wireless/marvell/mwifiex/README). So I had to adapt the wifi hook file manually to make this work.

Perhaps it is a good thing to support the netconf syntax and allow dynamically selecting the device name? I was following https://wiki.archlinux.org/title/Dm-crypt/Specialties and kind of expected step "Add ip=:::::wlan0:dhcp to the kernel parameters" to work with mlan0 instead of wlan0. The syntax is 'ip=192.168.1.1::192.168.1.254:255.255.255.0::eth0:none'

Looking at https://github.com/grazzolini/mkinitcpio-netconf/blob/master/netconf_hook it should be doable although I am far from a developer myself :)

I also ran into the problem mentioned below that my initial tests blocked the adapter because of missing firmware in the initcpio until a module removal and reload.

If I can help test, I'd be more than happy to do so on my device.

DocMAX commented on 2021-08-11 01:52 (UTC)

on initramfs iwlwifi is crashing, anyone else? https://bugzilla.kernel.org/show_bug.cgi?id=214031

tequa commented on 2020-03-30 17:33 (UTC)

A few things that I still could not fix (so if somebody has a solution, please post), but that might help in case of problems:

Once wifi is broken during boot (e.g. missing firmware) it is usually also broken after boot (because it will not be re-enabled?) without manual intervention, and from then on mkinitcpio autodetection will not include the modules properly.

In some (at least my) cases firmware is not detected correctly by mkinitcpio (also not listed properly by modinfo <module>). In these cases it seems to be necessary to somehow find out via dmesg and manually add the file needed via mkinitcpio.conf.

tequa commented on 2020-03-30 17:32 (UTC) (edited on 2020-03-30 17:33 (UTC) by tequa)

Hello, the -D <driver> option seems not necessary (probably I just copied it somewhere and did not think about it any more), so I removed it. ccm module was already in my cpios, so I'm not sure if I was just lucky here - now it is added.

zertyz commented on 2020-03-28 10:51 (UTC)

Thanks for the package.

A dependency on the crypto module ccm.ko is needed -- at least in my case -- when authenticating via WPA/WPA2 -- otherwise I keep seeing messages like "wlan0: deauthenticating from xx.xx.xx.xx.xx.xx by local choice (Reason: 1=UNSPECIFIED)"

Also, is the -D on wpa_supplicant really needed?