Wi-Fi works from time to time.

After start of PC Wi-Fi not gonna work, after reboot it will. So every time I want to use Wi-Fi I have to reboot.
KDE.
With Xfce there was problem with Wi-Fi too: it was always starting automatically and after turning Wi-Fi off I couldn't start it again, only after reboot.

$ inxi -Fxxxza --no-host
System: Kernel: 5.4.2-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.4-x86_64
root=UUID=9b674b36-81d3-4405-9f19-780914d751a2 rw quiet apparmor=1
security=apparmor resume=UUID=8f42e9b9-86b5-4be9-bf7c-26d8019260b2
udev.log_priority=3
Desktop: KDE Plasma 5.17.4 tk: Qt 5.13.2 wm: kwin_x11 dm: SDDM
Distro: Manjaro Linux
Machine: Type: Laptop System: Dell product: Inspiron 15-3573 v: 1.7.0 serial:
Chassis: type: 10 serial:
Mobo: Dell model: 0XT9M4 v: A00 serial: UEFI: Dell v: 1.7.0
date: 05/02/2019
Battery: ID-1: BAT0 charge: 37.2 Wh condition: 37.2/41.4 Wh (90%) volts: 16.3/14.8
model: SMP-LG2.8C DELL GR43778 type: Unknown serial: status: Full
CPU: Topology: Dual Core model: Intel Celeron N4000 bits: 64 type: MCP
arch: Goldmont Plus family: 6 model-id: 7A (122) stepping: 1 microcode: 32
L2 cache: 4096 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 4378
Speed: 796 MHz min/max: 800/2600 MHz Core speeds (MHz): 1: 796 2: 796
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel UHD Graphics 605 vendor: Dell driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:3185
Display: x11 server: [X.Org](http://X.Org) 1.20.6 driver: intel unloaded: modesetting
alternate: fbdev,vesa compositor: kwin_x11 resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel UHD Graphics 600 (Geminilake 2x6)
v: 4.5 Mesa 19.2.7 compat-v: 3.0 direct render: Yes
Audio: Device-1: Intel vendor: Dell driver: snd_hda_intel v: kernel bus ID: 00:0e.0
chip ID: 8086:3198
Device-2: Logitech Headset H390 type: USB
driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-2.4:11 chip ID: 046d:0a44
Sound Server: ALSA v: k5.4.2-1-MANJARO
Network: Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell
driver: ath10k_pci v: kernel port: f040 bus ID: 01:00.0 chip ID: 168c:0042
IF: wlp1s0 state: down mac:
Device-2: TP-Link USB 10/100 LAN type: USB driver: cdc_ether bus ID: 1-1:2
chip ID: 2357:0602 serial:
IF: enp0s21f0u1c2 state: unknown speed: N/A duplex: N/A mac:
Device-3: Action Star Enterprise USB 10/100 LAN type: USB
driver: hid-generic,usbhid bus ID: 1-2.1:5 chip ID: 0835:8501
Device-4: Action Star Enterprise USB 10/100 LAN type: USB
driver: hid-generic,usbhid bus ID: 1-2.5.1:13 chip ID: 0835:8502
Device-5: Qualcomm Atheros type: USB driver: btusb bus ID: 1-7:10
chip ID: 0cf3:e009
IF-ID-1: ppp0 state: unknown speed: N/A duplex: N/A mac: N/A
Drives: Local Storage: total: 763.85 GiB used: 357.23 GiB (46.8%)
ID-1: /dev/sda vendor: Western Digital model: WD3200LPVX-00V0TT0 size: 298.09 GiB
block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 5400 rpm
serial: rev: 1A01 scheme: GPT
Partition: ID-1: / raw size: 20.00 GiB size: 19.56 GiB (97.81%) used: 10.54 GiB (53.9%)
fs: ext4 dev: /dev/sda3
ID-2: /home raw size: 176.84 GiB size: 173.06 GiB (97.86%)
used: 85.42 GiB (49.4%) fs: ext4 dev: /dev/sda5
ID-3: swap-1 size: 1024.0 MiB used: 0 KiB (0.0%) fs: swap
swappiness: 60 (default) cache pressure: 100 (default) dev: /dev/sda2
Sensors: System Temperatures: cpu: 53.0 C mobo: 49.0 C sodimm: 37.0 C
Fan Speeds (RPM): N/A
Info: Processes: 168 Uptime: 1h 28m Memory: 7.59 GiB used: 1.06 GiB (14.0%)
Init: systemd v: 242 Compilers: gcc: 9.2.0 Shell: bash v: 5.0.11
running in: konsole inxi: 3.0.37

Have you tested different kernels yet?

I would suggest testing 4.19, 5.5 and one real time kernel.

1 Like

Okay.

1 Like

Tried them, all the same. Whatever.

There are countless posts about issues with your adapter. You can script a full network restart without requiring a reboot. A service can also be written to auto restart your wifi connection at boot or after suspend.

You have many ways you could try to correct this issue, but with your attitude I don't know how many volunteers you'll find to help you.

Do some searches and you will find no shortage of posts about your adapter.

Ok, thanks.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by