From: znavko@disroot.org
To: help-guix@gnu.org
Subject: Re: Why 'iw dev' does not show wireless device?
Date: Wed, 09 Oct 2019 17:38:44 +0000 [thread overview]
Message-ID: <bed537574ba67f3c4c75986ac58a2d55@disroot.org> (raw)
In-Reply-To: <87a7adloxr.fsf@nckx>
(Double). Yes, Tobias, I've dug this finally. This wifi card is not supported by LinuxLibre.
Please, would you give me advice, what to choose from mass-market ( in Russia dns-shop.ru )
for LinuxLibre and Guix in price under 540 euro ( 40.000 Roubles ) ???
I found this https://certification.ubuntu.com/desktop
But not sure it will exactly work with LinuxLibre. Also h-node lack some contemporary models.
October 6, 2019 6:17 PM, "Tobias Geerinckx-Rice" <me@tobias.gr> wrote:
> Znavko,
>
> znavko@disroot.org 写道：
>
>> # lspci -vvnn > wifi
>> # nano wifi
>> ...
>> Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless
>> Network Adapter
>> ...
>> Kernel driver in use: ath10k_pci
>> Kernel modules: ath10k_pci
>> Please, what to do? I cannot get the name of the network device.
>
> All ath10k devices of which I'm aware require proprietary firmware
> blobs that Guix won't ship and Linux-Libre won't load. Even
> though the kernel driver is loaded, I suspect you'll find some
> firmware-related errors in dmesg.
>
> I'm sorry,
>
> T G-R
next prev parent reply other threads:[~2019-10-09 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-06 17:00 Why 'iw dev' does not show wireless device? znavko
2019-10-06 18:16 ` Tobias Geerinckx-Rice
2019-10-09 17:38 ` znavko [this message]
2019-10-14 18:36 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bed537574ba67f3c4c75986ac58a2d55@disroot.org \
--to=znavko@disroot.org \
--cc=help-guix@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).