iwlwifi 0000:03:00.0: No beacon heard and the time event is over already...

[Lyubomir]

I see this error frequently inside logs: iwlwifi 0000:03:00.0: No beacon heard and the time event is over already...

Also, the internet doesn't seem stable, from time to time it disconnects and reconnects on its own, and other times it disconnects and wants me to enter the key again to connect. However, if i hit the X button to close the password modal and try to connect again from the networks list, it does connect without the need to enter the password.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.6
ProcVersionSignature: Ubuntu 5.4.0-58.64-lowlatency 5.4.73
Uname: Linux 5.4.0-58-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: lyubo 14448 F.... pulseaudio
 /dev/snd/pcmC0D0p: lyubo 14448 F...m pulseaudio
CasperMD5CheckResult: skip
Date: Mon Dec 28 21:50:51 2020
Dependencies:

InstallationDate: Installed on 2020-12-27 (0 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam
 Bus 001 Device 003: ID 8087:0aa7 Intel Corp.
 Bus 001 Device 002: ID 275d:0ba6 USB OPTICAL MOUSE
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire A515-51G
PackageArchitecture: all
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-58-lowlatency root=/dev/mapper/vgkubuntu-root ro quiet splash lockdown=confidentiality vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-58-lowlatency N/A
 linux-backports-modules-5.4.0-58-lowlatency N/A
 linux-firmware 1.187.6
SourcePackage: linux-firmware
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/03/2019
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.02
dmi.board.asset.tag: Type2 - Board Serial Number
dmi.board.name: Charmander_KL
dmi.board.vendor: KBL
dmi.board.version: V2.02
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.02
dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02:
dmi.product.family: Aspire 5
dmi.product.name: Aspire A515-51G
dmi.product.sku: 0000000000000000
dmi.product.version: V2.02
dmi.sys.vendor: Acer

[koba (kobako)]

Would you please try this?
#sudo apt update
#sudo apt install linux-image-oem-20.04-edge

[Lyubomir (mystiquewolf)]

Is it okay to have this error?
Error! Your kernel headers for kernel 5.10.0-1008-oem cannot be found.
Please install the linux-headers-5.10.0-1008-oem package

I also installed the recommended package above, but then got this error:
Error! Bad return status for module build on kernel: 5.10.0-1008-oem (x86_64)
Consult /var/lib/dkms/nvidia/450.80.02/build/make.log for more information.
   ...done.

So i purged all linux oem and reinstalled linux-image-oem-20.04-edge only.

[Lyubomir (mystiquewolf)]

Another error:
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125b-2.fw for module r8169
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_08.bin for module i915

[Lyubomir (mystiquewolf)]

Okay so i'm running with the linux-image-oem-20.04-edge kernel now.

Another thing i should mention is that here currently it is morning. in KSystemLog i couldn't see the beacon error with the standard 5.4 kernel this morning, only the entries from yesterday night. Then i installed this kernel you mentioned and rebooted, now can't see even them, so no beacon errors.
Not sure that causes the issues, maybe at night there are more people around with their routers, interference or whatever it is called and the signal might be lower?? I'm not much into drivers and waves so... :-\

[Lyubomir (mystiquewolf)]

I also logout and sleep the PC each night, no reboot except on updates or this morning after installing linux-image-oem-20.04-edge.

[Lyubomir (mystiquewolf)]

So i left the PC on this morning and now i check - i still have this error 3 times even with the oem kernel. I'm not sure if this is the reason for yesterday's frequent disconnecting, but it is the only wifi error with red error i saw, so it's worth fixing it before checking if the issue persists.

[Lyubomir (mystiquewolf)]

And from Network Manager i found this frequent error:
<warn> [1609237790.6890] sup-iface[0x561a7ba0d910,wlp3s0]: connection disconnected (reason -4)

[Lyubomir (mystiquewolf)]

Is this kernel you mentioned supposed to have a fix?

[Lyubomir (mystiquewolf)]

There is also this reason:
<warn> [1609268075.4422] sup-iface[0x561a7ba0daf0,wlp3s0]: connection disconnected (reason 15)

[Lyubomir (mystiquewolf)]

Having issues today connecting with the network with 5.4.0-59-lowlatency. Restarted the PC and not sure if this fixed it. Uploading logs from this point of time.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[uberschizo (uberschizo)]

Just logging in to say I have this too. Any current workarounds?
Interestingly I noticed that this problem only exists in connecting to my wifi router. If I use a 4G wifi hotspot device, the connection is stable.

[Kai-Heng Feng (kaihengfeng)]

Can you please try the -generic kernel instead of -lowlatency?

[Lyubomir (mystiquewolf)]

Since then i've clean reinstalled and i think i don't see this error in my logs. Also don't experience network disruptions.
My curret kernel is 5.11.0-17-lowlatency
Don't know what kernel @uberschizo uses.

[Juerg Haefliger (juergh)]

Apologies for the long delay. Is this still an issue?

[Juerg Haefliger (juergh)]

No response and seems to be resolved at least for some users. Please open a new bug if the problem still persists.