All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: "Dominik Förderer" <dominik.foerderer@posteo.de>
To: ath11k@lists.infradead.org
Subject: Re: Re: Have the QCA6390 patches for XPS 9310 landed yet?
Date: Mon, 02 Aug 2021 07:20:29 +0000	[thread overview]
Message-ID: <408a86cfc4dfd5a2054651f36033222e917a5f5c.camel@posteo.de> (raw)
In-Reply-To: <f5648123-c612-bb5a-dce4-1022aedc28c8@gecius.de>


[-- Attachment #1.1: Type: text/plain, Size: 3778 bytes --]

Am 30.07.21 um 23:52 schrieb Justin Mazzola Paluska:
>> On 7/30/21 4:08 PM, wi nk wrote:
>>>> On Fri, Jul 30, 2021 at 10:01 PM Kalle Valo <kvalo at codeaurora.org>> 
>>>> wrote:
>>>>>> Mitchell Nordine <mail at mitchellnordine.com>> writes:
>>>>>>
>>>>>>>> Hi kvalo and wink!
>>>>>>>>
>>>>>>>> It's been a while since I've had a chance to check in on this - have I
>>>>>>>> missed any QCA6390 progress?
>>>>>>>>
>>>>>>>> Currently the nixos-hardware repo is fixed to 5.10.18 along with most
>>>>>>>> of the patches on ath11k-qca6390-bringup, apart from two commits that
>>>>>>>> I'm sure were merged a while ago.
>>>>>>>>
>>>>>>>>
https://github.com/NixOS/nixos-hardware/blob/31f61b90ddb9257b94888ee17ccf96236e180c76/dell/xps/13-9310/default.nix#L14
>>>>>>>>
>>>>>>>>
>>>>>>>> Just wondering if the rest of the patches or some alternative fixes
>>>>>>>> have landed in a more recent version of the kernel yet, and whether
>>>>>>>> it's worth diving in and updating our nix expr yet?
>>>>>> Basically all you need is a BIOS update for XPS 9310 (to get 32 MSI
>>>>>> vectors working) and a recent Linux release. I don't remember the exact
>>>>>> kernel release, and can't check it now, but something like v5.12 or
>>>>>> v5.13 should work without extra patches.
>>>>>>
>>>>>> -- 
>>>>>> https://patchwork.kernel.org/project/linux-wireless/list/
>>>>>>
>>>>>>
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches 
>>>>>>
>>>>>>
>>>>>> -- 
>>>>>> ath11k mailing list
>>>>>> ath11k at lists.infradead.org
>>>>>> http://lists.infradead.org/mailman/listinfo/ath11k
>>>>
>>>> Hey Mitchell!
>>>>
>>>>    Just to add a little, Dell released a BIOS update that now allows
>>>> the driver to obtain all 32 MSI vectors (I posted around the time that
>>>> happened if you need the earliest version, otherwise just grab the
>>>> latest version).  I've been running 5.12 and 5.13 without WIFI issues.
>>>> Occasionally I still have bluetooth problems and the i915 drivers are
>>>> causing video artifacts randomly, but the wireless connection seems
>>>> pretty solid at this point.
>>
>> Which BIOS do you have?  I have 1.2.5.

>Just to add my experience - WiFi and BT are working. I'm on BIOS 3.0.4 
>(upgraded today via fwupdmgr / lvfs) with 5.13.5 / fedora 34 / xps 9310 
>32G dev edition. BT works since BIOS 2.something and kernel 5.12

>No memmap kernel parameter needed.

>>
>> I'm currently running 5.13 with a patch that reverted 
>> 3579994476b65cb5e272ff0f720a1fd31322e53f.  I needed to do that or the 
>> 5.13 kernel wouldn't connect to my access point because the firmware 
>> crashed.  (I got that pointer from 
>> https://bugzilla.kernel.org/show_bug.cgi?id=212059.)  With 357999 
>> reverted, everything works well.
>>
>> I still have the memmap=20M$12M kernel argument set from the old qca 
>> bringup branch days.  Do you also use that?
>>      --Justin
>>

I have the exact same issue as Justin described. I am on Bios 3.0.4 and Kernel
5.13.7 on Manjaro. I also have to revert
3579994476b65cb5e272ff0f720a1fd31322e53f to prevent the firmware from crashing
while connecting to my AP.
I figured out that the Problem is, that my router (Fritzbox), which is very
common in germany provide a (not changable) 160MHZ 5GhZ network. With 80MhZ or
lower there are no problems and ath11k is very stable.
Wen Gong released a patch e6ed929b4140d293bf8523f0376ed9bbdce29c47 for 5.14 to
address this Problem, but this patch caused a very unstable and randomly
crashing wifi on every channel width (20, 40, 80, 160 MhZ). On 5.14 i have now
to revert both mentioned patches to have a stable wifi. I posted this problem to
this list on june, but no one might mentioned it.

Dominik 

[-- 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

  reply	other threads:[~2021-08-04 19:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 16:30 Have the QCA6390 patches for XPS 9310 landed yet? Mitchell Nordine
2021-07-30 20:00 ` Kalle Valo
2021-07-30 20:08   ` wi nk
2021-07-30 21:52     ` Justin Mazzola Paluska
2021-07-30 21:57       ` wi nk
2021-07-30 22:11       ` Jens Gecius
2021-08-02  7:20         ` Dominik Förderer [this message]
2021-08-02 14:06     ` Kalle Valo
2021-08-04 13:06     ` Mitchell Nordine
2021-08-26 14:40       ` Kalle Valo

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=408a86cfc4dfd5a2054651f36033222e917a5f5c.camel@posteo.de \
    --to=dominik.foerderer@posteo.de \
    --cc=ath11k@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.