From: Ping-Ke Shih <pkshih@realtek.com>
To: James <bjlockie@lockie.ca>, Giulio Paci <giuliopaci@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: Realtek 8822ce connection is very unstable
Date: Wed, 28 Jun 2023 01:29:50 +0000 [thread overview]
Message-ID: <b3c5f2f05d0844dfb4e9f7e943b4cbbd@realtek.com> (raw)
In-Reply-To: <c4b24c16-788b-4f15-ae68-8df44e60a27d@lockie.ca>
> -----Original Message-----
> From: James <bjlockie@lockie.ca>
> Sent: Wednesday, June 28, 2023 2:23 AM
> To: Giulio Paci <giuliopaci@gmail.com>
> Cc: linux-wireless@vger.kernel.org
> Subject: Re: Realtek 8822ce connection is very unstable
>
> Jun. 27, 2023 12:13:48 Giulio Paci <giuliopaci@gmail.com>:
>
> > On Tue, Jun 27, 2023 at 6:04 PM James <bjlockie@lockie.ca> wrote:
> >> I would try a different distro.
> >
> > Any detail about why you would try a different distro and how much
> > should they differ?
> >
> > Actually when I tried Debian Bullseye wifi seemed more stable
> > (although I did not use that system long enough to be sure that it was
> > working without issues), but touchpad was not supported by that
> > system.
> >
> > Do you have any specific suggestion?
> Just something to try.
> I have no ideas.
>
Try below options to see if they can help:
1. try another band (switch from 2GHz to 5GHz or opposite)
2. try another AP
3. disable WiFi power save by
rtw88_core.ko disable_lps_deep=1
or
iw wlan0 set power_save off
By the way, when you try disable_aspm=1 and disable_msi=1, I suggest to
create a file and add them to /etc/modprobe.d/, and then shutdown and turn on
your computer after a while. Because some PCI settings are persistent if only
do rmmod/insmod.
next prev parent reply other threads:[~2023-06-28 1:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 15:12 Realtek 8822ce connection is very unstable Giulio Paci
2023-06-27 16:04 ` James
2023-06-27 16:13 ` Giulio Paci
2023-06-27 18:23 ` James
2023-06-28 1:29 ` Ping-Ke Shih [this message]
2023-06-28 10:35 ` Giulio Paci
2023-06-28 13:28 ` Bitterblue Smith
2023-06-29 0:32 ` Ping-Ke Shih
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=b3c5f2f05d0844dfb4e9f7e943b4cbbd@realtek.com \
--to=pkshih@realtek.com \
--cc=bjlockie@lockie.ca \
--cc=giuliopaci@gmail.com \
--cc=linux-wireless@vger.kernel.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).