From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] pinebookpro-kernel: missing options to get iwd running
Date: Thu, 21 Jan 2021 21:50:37 +0100 [thread overview]
Message-ID: <20210121205037.ceuotdsVG-EUaXrZXhNaqG7FlMtKC72E0INeB37E-l8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27346@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
Closed issue by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/issues/27346
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
*output of ``xuname`` (part of xtools)*
* package:
*affected package(s) including the version*: ``pinebook-pro-kernel-5.9.12_1 iwd-1.10_1``
### Expected behavior
Iwd starts
### Actual behavior
Uppon starting iwd, I do get this message and iwd returns.
```
DES support not found
No CBC(DES3_EDE) support found, certain TLS connections might fail
No Diffie-Hellman support found, WPS will not be available
The following options are missing in the kernel:
CONFIG_CRYPTO_USER_API_SKCIPHER
CONFIG_KEY_DH_OPERATIONS
CONFIG_CRYPTO_ECB
CONFIG_CRYPTO_CBC
CONFIG_CRYPTO_DES
The following optimized implementations might be available:
CONFIG_CRYPTO_DES3_EDE_X86_64
```
### Steps to reproduce the behavior
prev parent reply other threads:[~2021-01-21 20:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 8:23 [ISSUE] " Johnnynator
2020-12-22 16:47 ` CameronNemo
2020-12-23 2:06 ` CameronNemo
2020-12-23 2:07 ` CameronNemo
2020-12-31 21:06 ` ericonr
2020-12-31 21:11 ` CameronNemo
2021-01-21 14:28 ` ericonr
2021-01-21 20:46 ` CameronNemo
2021-01-21 20:50 ` ericonr [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210121205037.ceuotdsVG-EUaXrZXhNaqG7FlMtKC72E0INeB37E-l8@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).