From: Sven Eckelmann <sven@narfation.org>
To: walde <waldemar.stroh@uni-siegen.de>
Cc: Mariusz <enebeo@gmail.com>,
"ath11k@lists.infradead.org" <ath11k@lists.infradead.org>
Subject: Re: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
Date: Fri, 18 Nov 2022 12:26:54 +0100 [thread overview]
Message-ID: <4660647.LvFx2qVVIh@sven-l14> (raw)
In-Reply-To: <28dd9e69-a2f6-2e5e-90d7-c44611d700a5@uni-siegen.de>
[-- Attachment #1.1: Type: text/plain, Size: 924 bytes --]
On Tuesday, 15 November 2022 19:29:13 CET walde wrote:
> we probably have the same problem.
> We have two Pinapple 6 Wifi 6 cards from the manufacturer 8devices that
> we want to operate at 6 GHz. The modules have the QCN 9074 chipset and
> are also certified for the 6E standard. The modules work very well at 5
> GHZ. However the option to transmit on 6 GHz is not available. The board
> ID is also defined as 0xff. If there is any information you could share
> to enable the modules for 6 GHz, we would appreciate it.
You have to return it to them via their RMA procedure [1]. I already did that
in (mid) January 2022 and they replaced our cards with properly working
versions in (mid) February 2022.
Maybe you got a card from their first batch(es) (which had this problem) - or
the problem was reintroduced for some reason.
Kind regards,
Sven
[1] https://shop.8devices.com/index.php?route=account/return/add
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 102 bytes --]
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2022-11-18 11:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.7.1667674802.1691884.ath11k@lists.infradead.org>
2022-11-07 16:07 ` Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band Nagarajan Maran (QUIC)
2022-11-07 18:57 ` Mariusz
2022-11-08 21:03 ` Mariusz
[not found] ` <CAJrE-q73Jt8MfGn4bbyPs_VEb5DcjLMb7BWBp5MjMDjhZ2g5Wg@mail.gmail.com>
[not found] ` <MW2PR02MB38992059ED67678172D6604DED059@MW2PR02MB3899.namprd02.prod.outlook.com>
2022-11-15 10:02 ` Mariusz
2022-11-15 18:29 ` walde
2022-11-15 19:18 ` Mariusz
2022-11-18 11:26 ` Sven Eckelmann [this message]
2022-11-18 12:48 ` Mariusz
2022-11-18 14:05 ` Sven Eckelmann
2022-11-19 13:39 ` Mariusz
2022-11-19 15:16 ` Robert Marko
2022-11-19 16:09 ` Mariusz
2022-11-20 8:13 ` Mariusz
2022-11-22 15:14 ` Mariusz
2022-12-06 8:56 ` Sven Eckelmann
2022-11-17 16:51 ` Mariusz
2022-11-05 11:23 Mariusz
2022-12-17 10:31 ` Sven Eckelmann
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=4660647.LvFx2qVVIh@sven-l14 \
--to=sven@narfation.org \
--cc=ath11k@lists.infradead.org \
--cc=enebeo@gmail.com \
--cc=waldemar.stroh@uni-siegen.de \
/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