Wi-Fi connection keeps dropping out . MX 23.1 [Solved]

[bogos]

Code: Select all

System:
  Kernel: 6.1.0-13-amd64 [6.1.55-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-13-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.1_x64 Libretto October 15  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Laptop System: insyde product: i101 v: V1.00.01 serial: <superuser required>
  Mobo: N/A model: Type2 - Board Product Name v: Type2 - Board Version
    serial: <superuser required> UEFI: INSYDE v: MRTRIX.F.W101HFBNTAA03 date: 12/19/2015
Battery:
  ID-1: axp288_fuel_gauge charge: 76% condition: N/A volts: 4.0 min: N/A model: N/A type: Li-ion
    serial: N/A status: charging
CPU:
  Info: model: Intel Atom Z3735F bits: 64 type: MCP arch: Silvermont level: v2 built: 2013-15
    process: Intel 22nm family: 6 model-id: 0x37 (55) stepping: 8 microcode: 0x838
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 224 KiB desc: d-4x24 KiB; i-4x32 KiB
    L2: 2 MiB desc: 2x1024 KiB
  Speed (MHz): avg: 546 high: 666 min/max: 500/1833 scaling: driver: intel_cpufreq
    governor: ondemand cores: 1: 521 2: 666 3: 500 4: 500 bogomips: 10666
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass status: Not affected
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: disabled, RSB
    filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display driver: i915 v: kernel
    arch: Gen-7 process: Intel 22nm built: 2012-13 ports: active: DSI-1 empty: DP-1, DP-2, HDMI-A-1,
    HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:0f31 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1280x800 s-dpi: 96 s-size: 339x212mm (13.35x8.35") s-diag: 400mm (15.74")
  Monitor-1: DSI-1 res: 1280x800 hz: 60 size: N/A modes: 800x1280
  API: OpenGL v: 4.2 Mesa 22.3.6 renderer: Mesa Intel HD Graphics (BYT) direct-render: Yes
Audio:
  Message: No device data found.
  API: ALSA v: k6.1.0-13-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 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:
  Message: No PCI device data found.
  IF-ID-1: wlan0 state: up mac: <filter>
  IF-ID-2: wwan0 state: down mac: <filter>
Drives:
  Local Storage: total: 28.91 GiB used: 7.77 GiB (26.9%)
  ID-1: /dev/mmcblk1 maj-min: 179:0 model: NCard size: 28.91 GiB block-size: physical: 512 B
    logical: 512 B type: SSD serial: <filter> rev: 0x7 scheme: GPT
  SMART Message: Unknown smartctl error. Unable to generate data.
Partition:
  ID-1: / raw-size: 28.65 GiB size: 28.04 GiB (97.84%) used: 7.77 GiB (27.7%) fs: ext4
    dev: /dev/mmcblk1p2 maj-min: 179:2
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 314 KiB (0.1%) fs: vfat
    dev: /dev/mmcblk1p1 maj-min: 179:1
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 1024 MiB used: 211.5 MiB (20.7%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 48.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2057 libs: 1041 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb https://fastmirror.pp.ua/mxlinux/mx/repo/ bookworm main non-free
Info:
  Processes: 214 Uptime: 30m wakeups: 27 Memory: 1.86 GiB used: 795.8 MiB (41.8%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12 Client: shell wrapper
  v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

This is my system . The Wi-Fi connection is constantly lost , but it is restored itself after 10 - 20 seconds . I think that it is necessary to update the drivers , but i don"t know to do this . Or maybe i"m wrong ...
Help me , please

[Charlie Brown]

It doesn't show the device and driver info:

Network:
Message: No PCI device data found.
IF-ID-1: wlan0 state: up mac: <filter>
IF-ID-2: wwan0 state: down mac: <filter>


Till then, you can:

Right-click on Network icon on panel: "Edit Connections" and edit your connection:

Tick the "All Users may ..."


While you're at it: Enter a number (whatever, 5 10 ..) rather than zero for "priority" there...

Also in next tab click the "BSSID" box and then click the (mac) number that appears (fill the box with that) .. Save ...


Also:

Code: Select all

echo -e "[device]\nwifi.scan-rand-mac-address=no" | sudo tee /etc/NetworkManager/conf.d/disable-random-mac.conf

(This will create a conf file to stop it generate/scan random mac addresses)

Reboot.

[Stevo]

Do you think the processor could be generating extra heat (i.e. working hard) when the wi-fi cuts out? Then maybe it comes back online when system temps cool down?

[j2mcgreg]

Please give us the complete make and model of the laptop.

[bogos]

Do you think the processor could be generating extra heat (i.e. working hard) when the wi-fi cuts out? Then maybe it comes back online when system temps cool down?

No , this is not related to CPU cooling . Moreover , on version 21.3 everything works flawlessly , there are no wi-fi interruptions at all .

[bogos]

Please give us the complete make and model of the laptop.

This is a Chinese -made Matrix 3000 tablet , which originally had Windows 10 installed on it .

[Charlie Brown]

Do you think the processor could be generating extra heat (i.e. working hard) when the wi-fi cuts out? Then maybe it comes back online when system temps cool down?

No , this is not related to CPU cooling . ...

Then why is that post marked as the solution ?

[bogos]

It doesn't show the device and driver info:

Network:
Message: No PCI device data found.
IF-ID-1: wlan0 state: up mac: <filter>
IF-ID-2: wwan0 state: down mac: <filter>


Till then, you can:

Right-click on Network icon on panel: "Edit Connections" and edit your connection:

Tick the "All Users may ..."


While you're at it: Enter a number (whatever, 5 10 ..) rather than zero for "priority" there...

Also in next tab click the "BSSID" box and then click the (mac) number that appears (fill the box with that) .. Save ...


Also:

Code: Select all

echo -e "[device]\nwifi.scan-rand-mac-address=no" | sudo tee /etc/NetworkManager/conf.d/disable-random-mac.conf

(This will create a conf file to stop it generate/scan random mac addresses)

Reboot.

Unfortunately , your advice did not help . It's strange that everything works on version MX 21.3
wlan0 802.11

[bogos]

Do you think the processor could be generating extra heat (i.e. working hard) when the wi-fi cuts out? Then maybe it comes back online when system temps cool down?

No , this is not related to CPU cooling . ...

Then why is that post marked as the solution ?

I apologize - I didn't quite get the hang of it accidentally pressed the wrong button

[j2mcgreg]

@bogos wrote:

Unfortunately , your advice did not help . It's strange that everything works on version MX 21.3
wlan0 802.11

802.11 indicates that it's a b/g/n type card. Usually with these cards the problem is that they are defaulting to the "n" protocol which is highly susceptible to interference. You can fix the problem by accessing the router and configuring it to broadcast in "g" only.