On occasion, no internet at startup

[Member lgj100]

Hi Everyone,

Sometimes when I boot up or restart my antiX 23 system, for some reason, I have no internet. The Connman System Tray “Status” tab will be completely blank, as will be the “Wireless” tab. If I do do a reboot, usually the internet comes back. It doesn’t happen often – perhaps once every 10-15 times I start up/reboot the system, but it is annoying. What might cause this, and is there a way I can get the internet back without rebooting?

Sincerely,
Lars.

• This topic was modified 1 week, 6 days ago by lgj100.
• This topic was modified 1 week, 6 days ago by lgj100.
• This topic was modified 1 week, 6 days ago by lgj100.

[Member abc-nix]

Helpful

Up

0

::

I cannot remember what your system specs are or the antiX version you are running on your computer. If possible, please share them every time you start a support thread, or link to a different post where you have already shared this. This kind of information is important to get accurate support and recommendations.

If your system is antiX 23 runit edition, make sure you are fully up to date. There was a recent fix to runit-core (which manages the boot-up scripts) and I think this solved one of the problems I had with rebooting and connman reconnecting.

$ apt policy runit-core-services-antix 
runit-core-services-antix:
  Installed: 0.1.9
  Candidate: 0.1.9

• This reply was modified 1 week, 6 days ago by abc-nix.

[Moderator Brian Masinick]

Helpful

Up

0

::

I see occasional problems with the Connman/CMST combination too, but I’ve never been successfully able to diagnose EXACTLY what was happening.

Overnight I left my laptop powered on in xlock mode, intending to try a few more things in the morning.

When I woke up, CMST was “hung” and the Connman/CMST combination simply did not work; I even tried using antix-wifi-switch, oscillating to the alternative Ceni and back but CMST wouldn’t cooperate. Finally I used Ceni, which takes a LOT longer for some crazy reason to successfully initiate the WiFi connection. Ceni is more reliable, in my opinion; Connman/CMST *looks* better, is a bit faster, sometimes a LOT faster, but curiously it seems to depend on what you’re using.

I have THREE separate instances of antiX installed on the system I’m running on, and I rebooted to the SECOND instance; guess what? NO problem with Connman at all here!

My suggestion is therefore to keep the antix-wifi-switch tool available; use it if you are experiencing problems, switch to Ceni if necessary; I’m certainly open to anyone sharing a “magic” configuration parameter that ALWAYS works; that would be GREAT!

--
Brian Masinick

[Moderator Brian Masinick]

Helpful

Up

0

::

Oh yes, I have ATTEMPTED to locate some solid details about the establishment of network connections and I’ve examined as many different logs as I was able to locate; unfortunately NONE of them reported anything helpful, otherwise I would have reported the logs along with my use cases and a potential defect report, but with nothing definitive to report, I just move on, either to a different network manager or to the next of my three instances of antiX or one of my other installed distributions; it doesn’t stop me for long, but neither has it led to any scenarios I’ve been able to either diagnose myself or send to others, hence no defect report from me.

--
Brian Masinick

[Member lgj100]

Helpful

Up

0

::

@abc-nix
Please see below for my hardware info.

-Lars.

$ apt policy runit-core-services-antix
runit-core-services-antix:
  Installed: 0.1.9
  Candidate: 0.1.9
  Version table:
 *** 0.1.9 500
        500 http://la.mxrepo.com/antix/bookworm bookworm/main amd64 Packages
        500 http://la.mxrepo.com/antix/bookworm bookworm/main i386 Packages
        100 /var/lib/dpkg/status
     0.1.1 500
        500 http://la.mxrepo.com/antix/bookworm bookworm/nosystemd amd64 Packages
        500 http://la.mxrepo.com/antix/bookworm bookworm/nosystemd i386 Packages

and….

System:
  Kernel: 6.1.42-antix.1-amd64-smp arch: x86_64 bits: 64 compiler: gcc v: 13.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.42-antix.1-amd64-smp
    root=UUID=a6da5197-5248-441f-8355-ea04b2a45699 ro quiet selinux=0
  Desktop: IceWM v: 3.4.4 vt: 7 dm: slimski v: 1.5.0 Distro: antiX-23-runit_x64-full Arditi del
    Popolo 26 August 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Convertible System: Dell product: Latitude 5289 v: N/A serial: <superuser required>
    Chassis: type: 31 serial: <superuser required>
  Mobo: Dell model: 0PD00W v: A00 serial: <superuser required> UEFI: Dell v: 1.34.0
    date: 07/06/2023
Battery:
  ID-1: BAT0 charge: 9.7 Wh (100.0%) condition: 9.7/45.0 Wh (21.6%) volts: 12.4 min: 11.4
    model: SMP DELL X49C165 type: Li-ion serial: <filter> status: full
Memory:
  RAM: total: 15.51 GiB used: 4.53 GiB (29.2%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges required.
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i7-7600U bits: 64 type: MT MCP arch: Amber/Kaby Lake note: check
    gen: core 7 level: v3 note: check built: 2017 process: Intel 14nm family: 6 model-id: 0x8E (142)
    stepping: 9 microcode: 0xF4
  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: 4 MiB desc: 1x4 MiB
  Speed (MHz): avg: 869 high: 896 min/max: 400/2800 scaling: driver: intel_pstate
    governor: powersave cores: 1: 807 2: 890 3: 885 4: 896 bogomips: 23199
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat arch_capabilities arch_perfmon art
    avx avx2 bmi1 bmi2 bts clflush clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de
    ds_cpl dtes64 dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu fsgsbase
    fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs intel_pt invpcid invpcid_single
    lahf_lm lm mca mce md_clear mmx monitor movbe mpx msr mtrr nonstop_tsc nopl nx pae pat pbe
    pcid pclmulqdq pdcm pdpe1gb pebs pge pln pni popcnt pse pse36 pti pts rdrand rdseed rdtscp
    rep_good sdbg sep smap smep smx ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2
    tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi vpid x2apic xgetbv1 xsave xsavec
    xsaveopt xsaves xtopology xtpr
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: IBRS
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP: conditional, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel arch: Gen-9.5
    process: Intel 14nm built: 2016-20 ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2
    bus-ID: 00:02.0 chip-ID: 8086:5916 class-ID: 0300
  Device-2: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-5:2
    chip-ID: 0c45:6717 class-ID: 0e02
  Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: iris gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: eDP-1 model: LG Display 0x0542 built: 2016 res: 1920x1080 hz: 60 dpi: 177 gamma: 1.2
    chroma: red: x: 0.588 y: 0.357 green: x: 0.333 y: 0.565 blue: x: 0.157 y: 0.102 white: x: 0.314
    y: 0.329 size: 276x156mm (10.87x6.14") diag: 317mm (12.5") ratio: 16:9 modes: 1920x1080
  EDID-Warnings: 1: parse_edid: unknown flag 0
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 620 (KBL GT2)
    direct-render: Yes
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell driver: snd_hda_intel v: kernel
    alternate: snd_soc_skl,snd_soc_avs,snd_sof_pci_intel_skl bus-ID: 00:1f.3 chip-ID: 8086:9d71
    class-ID: 0403
  Sound API: ALSA v: k6.1.42-antix.1-amd64-smp running: yes
  Sound Server-1: PulseAudio v: 16.1 running: no
Network:
  Device-1: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel modules: wl pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 01:00.0 chip-ID: 8086:24fd class-ID: 0280
  IF: wlan0 state: up mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IP v6: <filter> scope: link
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 238.47 GiB used: 30.65 GiB (12.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: KSG60ZMV256G M.2 2280 256GB size: 238.47 GiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 4105
    scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 16.11 GiB size: 16.11 GiB (100.00%) used: 5.83 GiB (36.2%) fs: btrfs
    dev: /dev/sda5 maj-min: 8:5 label: rootantiX23 uuid: a6da5197-5248-441f-8355-ea04b2a45699
  ID-2: /boot/efi raw-size: 500 MiB size: 499 MiB (99.80%) used: 38.6 MiB (7.7%) fs: vfat
    dev: /dev/sda1 maj-min: 8:1 label: EFI-SYSTEM uuid: AA2C-E28E
  ID-3: /home raw-size: 143.53 GiB size: 143.53 GiB (100.00%) used: 24.79 GiB (17.3%) fs: btrfs
    dev: /dev/sda6 maj-min: 8:6 label: homeantiX uuid: 3cc8d8d9-1bac-4c19-b563-1ec755ab1404
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 50 (default 100)
  ID-1: swap-1 type: partition size: 4 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda4
    maj-min: 8:4 label: N/A uuid: 91f87000-fed6-4992-94b9-7cc3a2fc08c0
Unmounted:
  ID-1: /dev/sda2 maj-min: 8:2 size: 128 MiB fs: <superuser required> label: N/A uuid: N/A
  ID-2: /dev/sda3 maj-min: 8:3 size: 74.21 GiB fs: ntfs label: N/A uuid: BC62BE4462BE0366
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 1-5:2 info: Microdia Integrated_Webcam_HD type: Video driver: uvcvideo interfaces: 2
    rev: 2.0 speed: 480 Mb/s power: 500mA chip-ID: 0c45:6717 class-ID: 0e02
  Hub-2: 2-0:1 info: Super-speed hub ports: 6 rev: 3.0 speed: 5 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Device-1: 2-4:2 info: Realtek USB3.0-CRW type: Mass Storage driver: usb-storage interfaces: 1
    rev: 3.0 speed: 5 Gb/s power: 800mA chip-ID: 0bda:0328 class-ID: 0806 serial: <filter>
Sensors:
  System Temperatures: cpu: 31.0 C pch: 28.0 C mobo: 27.0 C
  Fan Speeds (RPM): cpu: 0
Repos:
  Packages: pm: dpkg pkgs: 2035 libs: 1020 tools: apt,apt-get,aptitude,synaptic
  Active apt repos in: /etc/apt/sources.list.d/antix.list
    1: deb [signed-by=/etc/apt/keyrings/antix-archive-keyring.gpg] http: //la.mxrepo.com/antix/bookworm/ bookworm main nonfree nosystemd
  Active apt repos in: /etc/apt/sources.list.d/bookworm-backports.list
    1: deb http: //deb.debian.org/debian/ bookworm-backports main contrib non-free non-free-firmware
  No active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http: //ftp.us.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: //ftp.us.debian.org/debian/ bookworm main contrib non-free non-free-firmware
    2: deb http: //security.debian.org/ bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
    1: deb [arch=amd64] https: //dl.google.com/linux/chrome/deb/ stable main
  No active apt repos in: /etc/apt/sources.list.d/librewolf.list
  No active apt repos in: /etc/apt/sources.list.d/liquorix.list
  Active apt repos in: /etc/apt/sources.list.d/megasync.list
    1: deb [signed-by=/usr/share/keyrings/meganz-archive-keyring.gpg] https: //mega.nz/linux/repo/Debian_12/ ./
  Active apt repos in: /etc/apt/sources.list.d/nordvpn.list
    1: deb https: //repo.nordvpn.com/deb/nordvpn/debian stable main
Processes:
  CPU top: 5 of 252
  1: cpu: 65.2% command: yad pid: 16203 mem: 31.9 MiB (0.2%)
  2: cpu: 16.9% command: chrome pid: 16086 mem: 229.1 MiB (1.4%)
  3: cpu: 2.2% command: chrome pid: 2387 mem: 365.2 MiB (2.2%)
  4: cpu: 1.5% command: google-chrome-stable pid: 2285 mem: 599.6 MiB (3.7%)
  5: cpu: 1.1% command: chrome pid: 15899 mem: 165.3 MiB (1.0%)
  Memory top: 5 of 252
  1: mem: 599.6 MiB (3.7%) command: google-chrome-stable pid: 2285 cpu: 1.5%
  2: mem: 478.9 MiB (3.0%) command: chrome pid: 2394 cpu: 0.6%
  3: mem: 365.2 MiB (2.2%) command: chrome pid: 2387 cpu: 2.2%
  4: mem: 344.1 MiB (2.1%) command: chrome pid: 2396 cpu: 0.0%
  5: mem: 306.7 MiB (1.9%) command: chrome pid: 2374 cpu: 0.4%
Info:
  Processes: 252 Uptime: 6h 41m wakeups: 10140 Init: runit v: N/A runlevel: 2 tool: service
  Compilers: gcc: 12.2.0 alt: 12 Client: shell wrapper v: 5.2.15-release inxi: 3.3.25

• This reply was modified 1 week, 6 days ago by lgj100.

[Member abc-nix]

Helpful

Up

0

::

Thanks, lgj100

Now that I know it is antiX 23 runit and fully updated, lets experiment with the runit services (don’t worry, this should not break anything).

You will be adding an instruction in the slimski runit service to try and start dbus and connman before it starts the graphical system. It may lead to an extra 1 second delay, but hopefully it forces connman to start before the graphical environment.

sudo xdg-open /etc/sv/slimski/run
Before the language is set (#Load Language code), we will ask the runit service manager to first start dbus and connman. It should look like this:

# Start elogind first (optional) - Don't start
# sv start elogind && sv check elogind || true
# Start dbus and connman before slimski
sv start dbus || true
sv start connman && sv check connman || true
# Load language code

Save and hopefully connman will always start before the graphical environment.

I also recommend you enable logging for the connman service if you continue to experience what you described in your post. This way, next time connman fails to start, you can copy over the logs for that failed session and share it here for us to try to figure out what is going on.

To enable the logs, run the runit service manager from App Select, click on the connman service on the list, and in the right side of the window, click “Enable” under the box titled “log”. You should be able to find the connman log in /var/log/runit/connman when you need it. The “current” file is the one for the running session. and you will find date and time stamps in said file.
Only enable logging if you need to. It is continuously writing to disk, wearing it down little by little, so I only enable it when I want to troubleshoot an issue.

[Member calciumsodium]

Helpful

Up

1

::

abc-nix wrote:

# Start dbus and connman before slimski
sv start dbus || true
sv start connman && sv check connman || true

Hello @abc-nix,
Thank you for this tip! I also have this issue. I also have a related issue that during startup, I run links2 that opens a specific news site. Sometimes links2 starts up faster than connman. So the news site does not open. Your tip solves this problem as well!

With this modification, I do see connman starting up during boot before X starts. The time difference is less than 1 sec. In one system, before modification boots with 9.39 s according to start-t icewm. After modification, about 9.96 s. In another system, before modification boots with 15.57 s according to start-t icewm. After modification, about 15.99 s.

Given the time difference is less than 1 sec and the added advantages of starting connman before X starts, I recommend having this modification as the default. Just my opinion. Thank you.

[Member anti-apXos]

Helpful

Up

0

::

In case something like this is made a default part of the slimski service, I’d suggest adding a check for the down file in the connman service directory in case a user doesn’t want connman/dbus/cmst at startup.

[Member Xunzi_23]

Helpful

Up

0

::

Modification slows boot on my main device, but still boot and have to reboot up to two times to get
Internet over Ethernet to work.

• This reply was modified 1 week, 4 days ago by Xunzi_23.

[Member abc-nix]

Helpful

Up

0

::

Xunzi_23 wrote:

Modification slows boot on my main device, but still boot and have to reboot up to two times to get
Internet over Ethernet to work.

Are you using connman or ceni (/etc/network/interfaces). Ethernet has issues with ceni for some reason.

anti-apXos wrote:

In case something like this is made a default part of the slimski service, I’d suggest adding a check for the down file in the connman service directory in case a user doesn’t want connman/dbus/cmst at startup.

Better not. This is only to fix it on some systems, and as you say, not everyone wants to use connman. Most people can way for the network connection 1 or 2 seconds (my case sometimes), but it eventually connects.

Since the runit-core update, I no longer have connman get stuck on my system during wake, or reboot. From time to time, I had to restart the connman service when this happened, but not anymore. I though the kernelmount script bug was the main reason for this issue, but it seems we still need to explore other issues.

Maybe adding dbus to the slimski service fixes the issue with pipewire on some systems (I think I read PPC mention that on some boots it doesn’t start, and they need to toggle off/on to fix it).

[Moderator Brian Masinick]

Helpful

Up

1

::

@abc-nix time will tell, but for a couple of days on my system I’ve adopted those extra couple of lines, namely

sudo xdg-open /etc/sv/slimski/run
and inserting the following after

# Start elogind first (optional) - Don't start
# sv start elogind && sv check elogind || true

# Start dbus and connman before slimski
sv start dbus || true
sv start connman && sv check connman || true 

and Before the language is set (#Load Language code).
So far it’s working fine; also as you specifically mentioned, this
modification is ONLY suggested for users who want to use
Connman rather than Ceni and seem to have some issues
connecting to the service; it DOES appear to make that
handshake work more reliably. I’ve tested it on three
separate installations of antiX 23 and 23.1 and it’s
helped stabilize that initial connection on all three of them;
thanks!

--
Brian Masinick

[Member PPC]

Helpful

Up

1

::

I’m lucky, I never ever had problems with getting ethernet to work for me (on my office I do have an ethernet connection).
At home, I use only wi-fi: I think I never ever had problems connecting to wi-fi when booting- but I reported that I sometimes lose wi-fi when my computers come off sleep mode- I either have to disable and reenable wifi on connman or, when using usb wifi dongles, just unplug and replug them again. I don’t recall ever having problems with wi-fi after sleep mode on my netbook, that uses built in wifi card – I’m not sure all this info is of any help on this particular subject….
This happens on runnit or sysv, on antiX 19.x and 22 (I only have 23 installed on my netbook, and it’s internal wifi card never had problems connecting to wi-fi.
Unproven hypothesis: can problems in having network connections working after boot be caused by hardware? Can wi-fi usb dongles have problems comming out of sleep/suspension be because the system does not properly wake them, sometimes (well, many times, in my case)?

Off topic – @abc-nix – I reported that antiX 23.1, version 2 Live, requires me to toggle pipewire off and back on to have sound, but only on my more powerful desktop. On my crappy old netbook, sound always works perfectly on trying that same Live OS. In antiX 23 and 23.1, version 1, in Live mode, pipewire never ever failed, on my desktop (strangly enough, it required more “sleep” time to start volumeicon, or else I had to start it manually – that’s to be expected, on a very slow device, starting from slow usb, but that got fixed, on my netbook, on 23.1)

P.

[Member calciumsodium]

Helpful

Up

1

::

abc-nix wrote:

# Start dbus and connman before slimski
sv start dbus || true
sv start connman && sv check connman || true

Hello @abc-nix,
In my last post in this thread, I tested your modification above. I had positive results and measured boot time. I found that the difference is less than 1 second before vs after modification.

In this post, I am tried this modification on two more different systems. Again positive results. In one system, before modification, boot time as measured by start-t icewm was 22.00 sec. After modification, 22.25 sec. Hardly noticeable.

In another system, an older one that tends boots up slower, boot time before modification was 48.63 sec. After modification, surprisingly, it was faster at 47.15 sec. I could not believe it. So I repeated it 3 more times. The data is repeatable in this system.

This is very good news.

A question, can one start pipewire in slimski similar to starting connman in your modification? If so, would this solve the wireplumber starting issue that was so troubling to many users, prior to your recent modifications of pipewire startup? Just a thought.

[Moderator Brian Masinick]

Helpful

Up

0

::

“A question, can one start pipewire in slimski similar to starting connman in your modification? If so, would this solve the wireplumber starting issue that was so troubling to many users, prior to your recent modifications of pipewire startup? Just a thought.”

I’d say give it a try, it ought to work as long as everything needed for it to work is started first.

--
Brian Masinick

[Member Xunzi_23]

Helpful

Up

0

::

Hi abc-nix,
I use conmann, and on the troublesome system only ethernet.

regarding no connection I have now, I hope managed to correctly
read one message which flashes by during start when connection fails.

connman d unable to connect to system bus address already in use.

I am not really worried about the issue for myself, I just restart,
others in my home town with same basic device are more irritated.

3 Devices I know of, so it is clearly not a problem with my hardware.

[Author]

Posts