After startup my wifi works fine. But after some minutes the networks manager starts showing Limited connectivity and the internet wont work. Please Help. I tried updating with garuda-update but i didn’t work. I tried going back into snapshots but i didn’t work either. I turned off dns and firewall but the error still persists. Please help
Please follow the template and post that garuda-inxi.
Also, explain where/how you “turned off dns and firewall”, and when the issue first happened (or did it never work?)
Note however that the issue is not necessarily on the computer side, it may be the access point (modem/router usually) you are connecting to, or too much distance between them, or radio interference.
If possible, also check with other devices (another computer, smartphone, something).
5 Likes
garuda-inxi
System:
Kernel: 6.7.7-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc avail: acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=9cddb97d-84e2-4fda-9a50-27e9c51e4c4e rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
ibt=off
Desktop: KDE Plasma v: 5.27.10 tk: Qt v: 5.15.12 info: frameworks
v: 5.115.0 wm: kwin_x11 vt: 2 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Laptop System: Dell product: Latitude 14 Rugged (5404) v: 00
serial: <superuser required> Chassis: type: 9 serial: <superuser required>
Mobo: Dell model: 07RKHG v: A00 serial: <superuser required> part-nu: 062F
uuid: <superuser required> BIOS: Dell v: A15 date: 01/24/2018
CPU:
Info: model: Intel Core i5-4310U bits: 64 type: MT MCP arch: Haswell
gen: core 4 level: v3 note: check built: 2013-15 process: Intel 22nm
family: 6 model-id: 0x45 (69) stepping: 1 microcode: 0x26
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
L3: 3 MiB desc: 1x3 MiB
Speed (MHz): avg: 798 min/max: 800/3000 scaling: driver: intel_cpufreq
governor: schedutil cores: 1: 798 2: 798 3: 798 4: 798 bogomips: 20752
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Haswell-ULT Integrated Graphics vendor: Dell driver: i915
v: kernel arch: Gen-7.5 process: Intel 22nm built: 2013 ports: active: eDP-1
empty: DP-1,HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:0a16
class-ID: 0300
Device-2: Sunplus Innovation Laptop Integrated Webcam HD driver: uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 2-7.2:5
chip-ID: 1bcf:28ae class-ID: 0e02
Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.4
compositor: kwin_x11 driver: X: loaded: modesetting
alternate: fbdev,intel,vesa dri: crocus gpu: i915 display-ID: :0
screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99")reflection and transmission of waves
s-diag: 414mm (16.31")
Monitor-1: eDP-1 model: AU Optronics 0x333c built: 2013 res: 1366x768
hz: 60 dpi: 112 gamma: 1.2 size: 309x173mm (12.17x6.81") diag: 354mm (13.9")
ratio: 16:9 modes: 1366x768
API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus
device: 1 drv: swrast surfaceless: drv: crocus x11: drv: crocus
inactive: gbm,wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.0.2-arch1.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 4400 (HSW
GT2) device-ID: 8086:0a16 memory: 1.46 GiB unified: yes
API: Vulkan v: 1.3.276 layers: 3 device: 0 type: integrated-gpu name: Intel
HD Graphics 4400 (HSW GT2) driver: mesa intel v: 24.0.2-arch1.1
device-ID: 8086:0a16 surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe
(LLVM 16.0.6 256 bits) driver: mesa llvmpipe v: 24.0.2-arch1.1 (LLVM
16.0.6) device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: Intel Haswell-ULT HD Audio vendor: Dell driver: snd_hda_intel
v: kernel bus-ID: 00:03.0 chip-ID: 8086:0a0c class-ID: 0403
Device-2: Intel 8 Series HD Audio vendor: Dell 8 driver: snd_hda_intel
v: kernel bus-ID: 00:1b.0 chip-ID: 8086:9c20 class-ID: 0403
API: ALSA v: k6.7.7-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: PipeWire v: 1.0.3 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Ethernet I218-LM vendor: Dell driver: e1000e v: kernel
port: f080 bus-ID: 00:19.0 chip-ID: 8086:155a class-ID: 0200
IF: eno1 state: down mac: <filter>
Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 8086:08b1 class-ID: 0280
IF: wlp2s0 state: up mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
RAID:
Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
v: 3.0 port: f060 bus-ID: 00:1f.2 chip-ID: 8086:282a rev: N/A class-ID: 0104
Drives:
Local Storage: total: 119.24 GiB used: 36.7 GiB (30.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 model: SATA SSD size: 119.24 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter>
fw-rev: 0A0 scheme: MBR
Partition:
ID-1: / raw-size: 119.24 GiB size: 119.24 GiB (100.00%)
used: 36.7 GiB (30.8%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-2: /home raw-size: 119.24 GiB size: 119.24 GiB (100.00%)
used: 36.7 GiB (30.8%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-3: /var/log raw-size: 119.24 GiB size: 119.24 GiB (100.00%)
used: 36.7 GiB (30.8%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-4: /var/tmp raw-size: 119.24 GiB size: 119.24 GiB (100.00%)
used: 36.7 GiB (30.8%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 7.66 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 4 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 42.0 C mobo: 25.0 C sodimm: SODIMM C
Fan Speeds (rpm): cpu: 0
Info:
Memory: total: 8 GiB available: 7.66 GiB used: 2.47 GiB (32.3%)
Processes: 234 Power: uptime: 0m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 3.05 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1662 libs: 438 tools: octopi,pamac,paru
Compilers: clang: 16.0.6 gcc: 13.2.1 Shell: garuda-inxi default: fish
v: 3.7.0 running-in: warp inxi: 3.3.33
Garuda (2.6.23-1):
System install date: 2023-07-29
Last full system update: 2024-03-03
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut
Windows dual boot: <superuser required>
Failed units:
- The error is not related to my Network as the wifi works fine on my android.
- I changed the dns to default through Garuda Assistant.
1 Like
Did it ever work reliably?
Any errors from journalctl -fu NetworkManager?
Keep it running until the connection drops.
“Limited connectivity”, now that I think of it again, does not indicate complete radio connection drop, rather inability to reach out to the internet. (derp)
Since you confirm the issue is not with other devices, I think it’s indeed more likely a computer issue rather than on the access point and ISP side.
Still, I’d double check the DNS settings on the access point (in case you ever changed them).
4 Likes
Maybe your WiFi card is going is some kind of sleep state. Try the pci_aspm=off kernel boot parameter. Manually or like here (even if for a different card)
If not helping, make sure to check also a few other kernels.
Edit: for the iwlwifi driver probably these instructions are applicable. Especially those on power save:
4 Likes
It worked well before i tried to restore a snapshot which i did on purpose of finding some lost files. After this i got this connectivity error. I have checked the dns settings on Access Point but it is set to deafult(provided by isp). I think that recovering a snapshot might have caused the problem.
1 Like
I tried the first solution but it didnt help. The network just disconnectes without any alerts i wonder whats the issue. Like it works for 5-10 minutes and then suddenly stops working. Browser says that DNS address could not be found.
The final log of the command journalctl -fu NetworkManager is following after the wifi stops working:
Network Manager state is now CONNECTED_SITE
there are no logs after this.
To confirm it’s a DNS problem, when it drops try
ping 8.8.8.8
1 Like
It does ping 8.8.8.8 and shows 64 bytes from 8.8.8.8 after wifi shows limited connectivity
I don’t know if this will help but Xfinity had us down most of the day on Friday to upgrade service in the area and on Saturday when it was back up my system connected just fine, but my roommates had a very slow connection. I went through everything and could find nothing wrong. I rolled his system back to the 29th and same issue after reboot. I then proceeded to just delete and recreate the connection, same issue til I did a reboot. Then all was good.
Have you tried different kernels?
I’d start from
sudo pacman -S linux-lts linux-lts-headers
Reboot and select it at GRUB in the advanced options.
I believe this is a DNS problem, and you could test other servers, but sometimes a kernel regression can occur. E.g. (just a quick search, but it’s on 6.7):
https://bugzilla.kernel.org/show_bug.cgi?id=218359
Finally, a couple of routinary steps:
Disable IPv6 in Network Manager, disable mac address randomization in Garuda Network Assistant and reboot your PC and the router.
recovering a snapshot might have caused the problem
Is the automatic backup snapshot still around by chance? (not the usual pre/post ones, the kind that have “_backup_” in their name and record the state before restoring)
Perhaps comparing network related configuration files can give a clue (assuming this is indeed the cause). The dnsmasq ones specifically. I hereby confess my head exploded last time I tried to make sense of all the interactions between networking components.
cat /etc/resolv* ?
Maybe deleting and recreating the wifi connection?
Also worth trying the wifi.powersave = 0 thing from this thread
Realtek RTL8822CE Wifi - limited connectivity - #5 by tbg
Here are some suggestions you can try:
Test assigning your computer a static IP address either via your router or Network Manager.
Test older versions of the Intel iwlwifi firmware, see:
There are also numerous iwlwifi driver options that often help improve performance with this Intel wifi adapter.
To test alternate iwlwifi driver options try selectively running each of the following commands once your connection is lost.
Execute the first command below, and then test if your connection is restored and remains stable afterwards.
bash -c "nmcli networking off; sudo systemctl stop NetworkManager; sudo ip link set wlp2s0 down; sleep 1; sudo lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs sudo rmmod; sleep 3; sudo modprobe iwlwifi 11n_disable=1; sleep 1; sudo ip link set wlp2s0 up; sleep 1; sudo systemctl start NetworkManager; nmcli networking on; sleep 1; nmcli r wifi off; sleep 1; nmcli r wifi on"
If executing the first command didn’t help, then run the second command below. Test if your connection is restored and remains stable after running the next command.
bash -c "nmcli networking off; sudo systemctl stop NetworkManager; sudo ip link set wlp2s0 down; sleep 1; sudo lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs sudo rmmod; sleep 3; sudo modprobe iwlwifi 11n_disable=8; sleep 1; sudo ip link set wlp2s0 up; sleep 1; sudo systemctl start NetworkManager; nmcli networking on; sleep 1; nmcli r wifi off; sleep 1; nmcli r wifi on"
If executing the second command didn’t help, then run the following command below. Test if your connection is restored and remains stable after running the final command below.
bash -c "nmcli networking off; sudo systemctl stop NetworkManager; sudo ip link set wlp2s0 down; sleep 1; sudo lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs sudo rmmod; sleep 3; sudo modprobe iwlwifi 11n_disable=8 bt_coex_active=0; sleep 1; sudo ip link set wlp2s0 up; sleep 1; sudo systemctl start NetworkManager; nmcli networking on; sleep 1; nmcli r wifi off; sleep 1; nmcli r wifi on"
The iwlwifi driver option modifications implemented with the above commands will only remain in effect during the current session. Rebooting will nullify changes that executing any of the above commands instituted. If the driver options I suggested above improve your wifi’s performance, then an ilwifi driver configuration file will need to be createdd in /etc/modprobe.d for the changes to be made persistent.
If any of the temporary modprobe commands you tested earlier correct your connectivity issue, then follow the instructions below to create a lasting fix.
The following commands below will auto-generate the required /etc/modprobe.d/iwlwifi.conf Intel wifi driver configuation file.
If during testing the first command improved your connectivity, then execute the following in the terminal:
echo "options iwlwifi 11n_disable=1 " | sudo tee /etc/modprobe.d/iwlwifi.conf
If during testing the second command improved your connectivity, then execute the following in the terminal:
echo "options iwlwifi 11n_disable=8 " | sudo tee /etc/modprobe.d/iwlwifi.conf
If during testing the third command improved your connectivity, then execute the following in the terminal:
echo "options iwlwifi 11n_disable=8 bt_coex_active=0 " | sudo tee /etc/modprobe.d/iwlwifi.conf
You can also try further modifying your Intel wifi’s power saving options by adding extra parameters to the /etc/modprobe.d/iwlwifi.conf file.
Run the following command(s) to add experimental power saving options to the Intel wifi configuration file that sometimes improve reliability:
echo -e "options iwlwifi power_save=0\noptions iwlmvm power_scheme=1" | sudo tee -a /etc/modprobe.d/iwlwifi.conf
If the above command does not improve your wifi performance significantly, then run the following command to again ammend /etc/modprobe.d/iwlwificonf to add further power saving options:
echo 'options iwlwifi power_save=0 d0i3_disable=0 uapsd_disable=0' | sudo tee -a /etc/modprobe.d/iwlwifi.conf
Reboot after creatiing or making any changes to the /etc/modprobe.d/iwlwifi.conf Intel wifi configuration file, then test for improvements.
Edit:
I corrected a typo in one of my modprobe commands above, so be sure to run the first group of commands again if you already tested my original unedited commands.
As well, I have added the further steps required to make any driver modifications persistent in my recent edit(s).
2 Likes
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.