Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iwd will not start due to kernel config #7

Closed
gearhead opened this issue Jun 19, 2020 · 1 comment
Closed

iwd will not start due to kernel config #7

gearhead opened this issue Jun 19, 2020 · 1 comment

Comments

@gearhead
Copy link

I built this for rpi3 (buildarch=8) and have had reasonable success. Thanks for providing it. Confused as to why it is not available from Arch ARM...
The only thing I found that did not work on my test system was iwd. wpa_supplicant does run, but iwd requires some features to be turned on in the kernel that config8 does not or as set as modules . Once I turned them on and rebuilt the kernel and installed it, iwd now works again. I do not know if all of these are what is required, but I compared the settings to my regular kernel build and these are what I saw as different (updated on left, yours on right) I used this to build the now running image 64 bit kernel 64 bit user space:
$ diff config8 config8.moon

566,567c566,567
< CONFIG_CRYPTO_SHA256_ARM64=y
< CONFIG_CRYPTO_SHA512_ARM64=y
---
> CONFIG_CRYPTO_SHA256_ARM64=m
> CONFIG_CRYPTO_SHA512_ARM64=m
575c575
< CONFIG_CRYPTO_AES_ARM64=y
---
> CONFIG_CRYPTO_AES_ARM64=m
582c582
< CONFIG_CRYPTO_AES_ARM64_BS=y
---
> CONFIG_CRYPTO_AES_ARM64_BS=m
7129c7129
< CONFIG_KEY_DH_OPERATIONS=y
---
> # CONFIG_KEY_DH_OPERATIONS is not set
7311c7311
< CONFIG_CRYPTO_USER_API_HASH=y
---
> # CONFIG_CRYPTO_USER_API_HASH is not set

It may be just these 2, but I have not re-built it to test:

CONFIG_KEY_DH_OPERATIONS=y
CONFIG_CRYPTO_USER_API_HASH=y

Previously, I would get this in the journal when I tried to run iwd:

Jun 18 23:34:02 rune64 systemd[1]: Starting Wireless service...
Jun 18 23:34:03 rune64 iwd[4088]: No HMAC(SHA1) support found
Jun 18 23:34:03 rune64 iwd[4088]: No HMAC(MD5) support found
Jun 18 23:34:03 rune64 iwd[4088]: No CMAC(AES) support found
Jun 18 23:34:03 rune64 iwd[4088]: No HMAC(SHA256) support not found
Jun 18 23:34:03 rune64 iwd[4088]: No HMAC(SHA512) support found, certain TLS connections might fail
Jun 18 23:34:03 rune64 iwd[4088]: No Diffie-Hellman support found, WPS will not be available
Jun 18 23:34:03 rune64 iwd[4088]: The following options are missing in the kernel:
Jun 18 23:34:03 rune64 iwd[4088]:         CONFIG_CRYPTO_USER_API_HASH
Jun 18 23:34:03 rune64 iwd[4088]:         CONFIG_KEY_DH_OPERATIONS
Jun 18 23:34:03 rune64 iwd[4088]:         CONFIG_CRYPTO_MD5
Jun 18 23:34:03 rune64 iwd[4088]:         CONFIG_CRYPTO_SHA256
Jun 18 23:34:03 rune64 iwd[4088]:         CONFIG_CRYPTO_AES
Jun 18 23:34:03 rune64 iwd[4088]:         CONFIG_CRYPTO_CMAC
Jun 18 23:34:03 rune64 iwd[4088]:         CONFIG_CRYPTO_USER_API_HASH
Jun 18 23:34:03 rune64 iwd[4088]:         CONFIG_CRYPTO_USER_API_HASH
Jun 18 23:34:03 rune64 iwd[4088]:         CONFIG_CRYPTO_USER_API_HASH
Jun 18 23:34:03 rune64 iwd[4088]:         CONFIG_CRYPTO_HMAC
Jun 18 23:34:03 rune64 iwd[4088]:         CONFIG_CRYPTO_HMAC
Jun 18 23:34:03 rune64 iwd[4088]:         CONFIG_CRYPTO_HMAC
Jun 18 23:34:03 rune64 iwd[4088]:         CONFIG_CRYPTO_SHA512
Jun 18 23:34:03 rune64 iwd[4088]:         CONFIG_CRYPTO_SHA1
Jun 18 23:34:03 rune64 iwd[4088]: The following optimized implementations might be available:
Jun 18 23:34:03 rune64 iwd[4088]:         CONFIG_CRYPTO_SHA1_SSSE3
Jun 18 23:34:03 rune64 iwd[4088]:         CONFIG_CRYPTO_AES_NI_INTEL
Jun 18 23:34:03 rune64 iwd[4088]:         CONFIG_CRYPTO_SHA512_SSSE3
Jun 18 23:34:03 rune64 iwd[4088]:         CONFIG_CRYPTO_AES_X86_64
Jun 18 23:34:03 rune64 iwd[4088]:         CONFIG_CRYPTO_SHA256_SSSE3
Jun 18 23:34:03 rune64 systemd[1]: iwd.service: Main process exited, code=exited, status=1/FAILURE
Jun 18 23:34:03 rune64 systemd[1]: iwd.service: Failed with result 'exit-code'.
Jun 18 23:34:03 rune64 systemd[1]: Failed to start Wireless service.

Now I get this:

Jun 19 06:50:53 rune64 systemd[1]: iwd.service: Succeeded.
Jun 19 06:50:58 rune64 iwd[2716]: Wireless daemon version 1.7
Jun 19 06:50:58 rune64 iwd[2716]: Loaded configuration from /etc/iwd/main.conf
Jun 19 06:50:58 rune64 iwd[2716]: netconfig: Network configuration is disabled.
Jun 19 06:50:58 rune64 iwd[2716]: Wiphy: 0, Name: phy0
Jun 19 06:50:58 rune64 iwd[2716]:         Permanent Address: b8:27:xx:xx:xx:xx
Jun 19 06:50:58 rune64 iwd[2716]:         Bands: 2.4 GHz 5 GHz
Jun 19 06:50:58 rune64 iwd[2716]:         Ciphers: CCMP TKIP BIP
Jun 19 06:50:58 rune64 iwd[2716]:         Supported iftypes: ad-hoc station ap p2p-client p2p-go p2p-device
Jun 19 06:50:58 rune64 iwd[2716]: Wiphy phy0 will only use the default interface
@moonman
Copy link
Owner

moonman commented Jun 29, 2020

I'll have a look at the config, thanks.

It isn't included in the official repos because (hopefully this is the last time I have to explain this):

  1. It is not officially supported by RaspberryPi foundation
  2. Kevin will not maintain a package (and understandably so) that isn't officially supported by raspberrypi foundation.
  3. I'm not maintaining this regularly enough for it to be in the official repo.

@moonman moonman closed this as completed Jun 29, 2020
JayBeavers pushed a commit to JayBeavers/MyPKGBUILDs that referenced this issue Jul 16, 2020
iwcfg requires various crypto changes
zfs-dkms requires CONFIG_PREEMPT_VOLUNTARY=y due to a mixed GPL license warning

See moonman#7 for a discussion of iwcfg/crypto
See openzfs/zfs#8545 for a discussion of CONFIG_PREEMPT_VOLUNTARY
JayBeavers pushed a commit to JayBeavers/MyPKGBUILDs that referenced this issue Jul 16, 2020
JayBeavers pushed a commit to JayBeavers/MyPKGBUILDs that referenced this issue Jul 16, 2020
iwcfg requires various crypto changes
zfs-dkms requires CONFIG_PREEMPT_VOLUNTARY=y due to a mixed GPL license warning

See moonman#7 for a discussion of iwcfg/crypto
See openzfs/zfs#8545 for a discussion of CONFIG_PREEMPT_VOLUNTARY
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants