boot status daemon error on MX23 [solved]

Report Bugs, Issues and non- package Requests
Message
Author
alp_c
Posts: 5
Joined: Wed Aug 25, 2021 2:12 pm

boot status daemon error on MX23 [solved]

#1 Post by alp_c »

Good day,

I am using MX23 64bit with KDE Plasma Desktop on Wayland with sysV init boot. For a couple of weeks now, about every third boot terminates with:
error: unexpectedly disconnected from Boot status daemon
This appears before reaching the login screen. The system is not frozen, I can do a regular shutdown by pressing the power button shortly.

There was a similar issue on MX19: viewtopic.php?t=75348 Could someone please advise how to fix this on MX23?

Thanks
alp_c

Edit: adding QSI:

Code: Select all

[CODE]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
    resume=UUID=<filter> resume_offset=2744320
  Desktop: KDE Plasma v: 5.27.5 wm: kwin_wayland vt: 8 dm: SDDM Distro: MX-23.2_KDE_x64 Libretto
    October 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Laptop System: FUJITSU SIEMENS product: LIFEBOOK S6410 v: N/A serial: <superuser required>
    Chassis: type: 10 v: S6410 serial: <superuser required>
  Mobo: FUJITSU model: FJNB1D3 v: CP329752-01 serial: <superuser required>
    BIOS: FUJITSU // Phoenix v: Version 1.30 date: 08/20/2008
Battery:
  ID-1: CMB1 charge: 50.7 Wh (91.4%) condition: 55.5/62.6 Wh (88.7%) volts: 11.5 min: 10.8
    model: Fujitsu CP345705-01 type: Li-ion serial: <filter> status: discharging
CPU:
  Info: model: Intel Core2 Duo T7250 bits: 64 type: MCP arch: Core2 Merom level: v1 built: 2006-09
    process: Intel 65nm family: 6 model-id: 0xF (15) stepping: 0xD (13) microcode: 0xA4
  Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB
    L2: 2 MiB desc: 1x2 MiB
  Speed (MHz): avg: 798 min/max: 800/2001 boost: enabled scaling: driver: acpi-cpufreq
    governor: ondemand cores: 1: 798 2: 798 bogomips: 7980
  Flags: ht lm nx pae sse sse2 sse3 ssse3
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX unsupported
  Type: l1tf mitigation: PTE Inversion
  Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; 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: Vulnerable
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not
    affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Mobile GM965/GL960 Integrated Graphics vendor: Fujitsu driver: i915 v: kernel
    arch: Gen-4 process: Intel 65n built: 2006-07 ports: active: LVDS-1 empty: DVI-D-1,SVIDEO-1,VGA-1
    bus-ID: 00:02.0 chip-ID: 8086:2a02 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_wayland
    driver: X: loaded: intel dri: i965 gpu: i915 display-ID: 0
  Monitor-1: LVDS-1 res: 1280x800 size: N/A modes: N/A
  API: OpenGL v: 2.1 Mesa 23.1.2-1~mx23ahs renderer: Mesa Intel 965GM (CL) direct-render: Yes
Audio:
  Device-1: Intel 82801H HD Audio vendor: Fujitsu driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
    chip-ID: 8086:284b class-ID: 0403
  API: ALSA v: k6.1.0-13-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 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: Marvell 88E8055 PCI-E Gigabit Ethernet vendor: Fujitsu driver: sky2 v: 1.30 pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 04:00.0 chip-ID: 11ab:4363 class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter driver: ath5k v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 0c:00.0 chip-ID: 168c:001c class-ID: 0200
  IF: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: Taiyo Yuden Bluetooth Device (V2.0+EDR) type: USB driver: btusb v: 0.8 bus-ID: 3-2:2
    chip-ID: 0c24:000f class-ID: fe01
  Report: hciconfig ID: hci0 rfk-id: 1 state: down bt-service: N/A rfk-block: hardware: no
    software: no address: <filter>
  Info: acl-mtu: 384:8 sco-mtu: 64:8 link-policy: rswitch hold sniff park
    link-mode: peripheral accept
Drives:
  Local Storage: total: 111.79 GiB used: 15.59 GiB (13.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: SanDisk model: SDSSDA120G size: 111.79 GiB block-size:
    physical: 512 B logical: 512 B speed: 3.0 Gb/s type: SSD serial: <filter> rev: 10RL scheme: MBR
Partition:
  ID-1: / raw-size: 40 GiB size: 39.08 GiB (97.69%) used: 15.59 GiB (39.9%) fs: ext4 dev: /dev/sda3
    maj-min: 8:3
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 4 GiB used: 727 MiB (17.7%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 48.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2590 pm: dpkg pkgs: 2583 libs: 1415 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 7
  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 http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bookworm main non-free
    2: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bookworm ahs
Info:
  Processes: 185 Uptime: 1h 40m wakeups: 2 Memory: 1.91 GiB used: 1.57 GiB (82.3%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)
Last edited by alp_c on Mon Mar 04, 2024 2:24 pm, edited 1 time in total.

User avatar
dolphin_oracle
Developer
Posts: 22110
Joined: Sun Dec 16, 2007 12:17 pm

Re: boot status daemon error on MX23

#2 Post by dolphin_oracle »

all that is is sddm reporting that it gets disconnected from plymouth with plymouth stops. plymouth is also the boot splash. the message is harmless so please just ignore it.

at the moment the only way to completly remove it is to not use a boot splash ("nosplash" boot code).

the message is likely always present, but its only sometimes that its visible before X starts.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
dolphin_oracle
Developer
Posts: 22110
Joined: Sun Dec 16, 2007 12:17 pm

Re: boot status daemon error on MX23

#3 Post by dolphin_oracle »

actually try this plymouth-modified-init package.

https://drive.google.com/file/d/1C1sU5G ... drive_link

it hides the message in my tests, from sddm and from others if present.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

alp_c
Posts: 5
Joined: Wed Aug 25, 2021 2:12 pm

Re: boot status daemon error on MX23

#4 Post by alp_c »

Thanks very much DO for taking a look and providing a fix so quickly.

I've installed the package and will post back after some reboots.

alp_c
Posts: 5
Joined: Wed Aug 25, 2021 2:12 pm

Re: boot status daemon error on MX23

#5 Post by alp_c »

About 10 reboots later... no more signs of any error message. Great job!

I'll mark the thread as solved. Thank you!

Post Reply

Return to “Bugs and Non-Package Requests Forum”