From: zlice <zlice@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: hostapd: 2.10 breaks ap functionality
Date: Mon, 14 Feb 2022 06:29:53 +0100 [thread overview]
Message-ID: <20220214052953.RInUv583syXW8zKGnas5Gtw-bzR9FACWT4j8eHzN8Hg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35420@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
New comment by zlice on void-packages repository
https://github.com/void-linux/void-packages/issues/35420#issuecomment-1038661491
Comment:
more precise `-dd`
```
Allowed channel: mode=0 chan=10 freq=2457 MHz max_tx_power=30 dBm
Allowed channel: mode=0 chan=11 freq=2462 MHz max_tx_power=30 dBm
ACS: Automatic channel selection started, this may take a bit
ACS: No available channels found
wifi0: IEEE 802.11 Configured channel (0) or frequency (0) (secondary_channel=1) not found from the channel list of the current mode (2) IEEE 802.11a
wifi0: IEEE 802.11 Hardware does not support configured channel
Could not select hw_mode and channel. (-3)
wifi0: interface state UNINITIALIZED->DISABLED
wifi0: AP-DISABLED
```
Pretty sure this is a hostapd, firmware or kernel bug (or a combination or all three? i can't keep up with wifi on linux, swear something changes every time a dev sneezes thinking of wifi). But I have tried everything at this point, hostapd-2.10 is broken.
next prev parent reply other threads:[~2022-02-14 5:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 18:06 [ISSUE] " zlice
2022-02-14 5:29 ` zlice [this message]
2022-02-14 20:25 ` [ISSUE] [CLOSED] " zlice
2022-02-14 20:25 ` zlice
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=20220214052953.RInUv583syXW8zKGnas5Gtw-bzR9FACWT4j8eHzN8Hg@z \
--to=zlice@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).