MXLinux Audio Devices stop detecting shortly after boot  [Solved]

Forum rules
Post Reply
Message
Author
aspacegamer
Posts: 87
Joined: Fri Oct 13, 2023 7:59 am

MXLinux Audio Devices stop detecting shortly after boot

#1 Post by aspacegamer »

After a recent update of my system packages (including the pulsewire audio mx setup package) my audio devices keep dying shortly after i boot the device it works for a short time and then all audio devices vanish and leave me with a mute symbol in the taskbar but nothing else.
I am using MX Linux 23 and will provice additional information if asked.
Top
User avatar
j2mcgreg
Global Moderator
Posts: 7198
Joined: Tue Oct 23, 2007 12:04 pm

Re: MXLinux Audio Devices stop detecting shortly after boot

#2 Post by j2mcgreg »

We are going to need your computer’s complete profile before we can proceed, so you need to post the output from the QSI utility. The Quick System Info (QSI) utility is located in MX Tools and its output is automatically formatted for use here in the forum. Run the QSI utility, click “Copy for Forum” at the bottom and then just paste it here in your thread.
Forum Rules
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.
Top
aspacegamer
Posts: 87
Joined: Fri Oct 13, 2023 7:59 am

Re: MXLinux Audio Devices stop detecting shortly after boot

#3 Post by aspacegamer »

j2mcgreg wrote: Sun Jan 07, 2024 9:58 am We are going to need your computer’s complete profile before we can proceed, so you need to post the output from the QSI utility. The Quick System Info (QSI) utility is located in MX Tools and its output is automatically formatted for use here in the forum. Run the QSI utility, click “Copy for Forum” at the bottom and then just paste it here in your thread.
Forum Rules
Will post them as soon as i can boot back into MXLinux on my device.
Top
aspacegamer
Posts: 87
Joined: Fri Oct 13, 2023 7:59 am

Re: MXLinux Audio Devices stop detecting shortly after boot

#4 Post by aspacegamer »

aspacegamer wrote: Sun Jan 07, 2024 10:29 am
j2mcgreg wrote: Sun Jan 07, 2024 9:58 am We are going to need your computer’s complete profile before we can proceed, so you need to post the output from the QSI utility. The Quick System Info (QSI) utility is located in MX Tools and its output is automatically formatted for use here in the forum. Run the QSI utility, click “Copy for Forum” at the bottom and then just paste it here in your thread.
Forum Rules
Will post them as soon as i can boot back into MXLinux on my device.
I think i fixed it after disabling my Oculus audio device it seems to be stable again also i reinstalled pipewire-setup-mx too dunno why the oculus made it fail still gonna paste my QSI output trough:

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
    resume=UUID=<filter> resume_offset=121618432
  Desktop: KDE Plasma v: 5.27.5 info: kdocker wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.1_KDE_x64
    Libretto October 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: ROG STRIX Z490-F GAMING v: Rev 1.xx serial: <superuser required>
    UEFI: American Megatrends v: 2601 date: 05/17/2022
CPU:
  Info: model: Intel Core i9-10850K bits: 64 type: MT MCP arch: Comet Lake gen: core 10 level: v3
    note: check built: 2020 process: Intel 14nm family: 6 model-id: 0xA5 (165) stepping: 5
    microcode: 0xF8
  Topology: cpus: 1x cores: 10 tpc: 2 threads: 20 smt: enabled cache: L1: 640 KiB desc: d-10x32
    KiB; i-10x32 KiB L2: 2.5 MiB desc: 10x256 KiB L3: 20 MiB desc: 1x20 MiB
  Speed (MHz): avg: 815 high: 1105 min/max: 800/5200 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 802 3: 800 4: 800 5: 1105 6: 800 7: 800 8: 800 9: 800
    10: 800 11: 800 12: 800 13: 800 14: 800 15: 800 16: 800 17: 800 18: 800 19: 800 20: 800
    bogomips: 144000
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: Enhanced IBRS
  Type: spec_rstack_overflow status: Not affected
  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: Enhanced IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: SW
    sequence
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA TU104 [GeForce RTX 2070 SUPER] vendor: ASUSTeK driver: nvidia v: 525.147.05
    non-free: 530.xx+ status: current (as of 2023-03) arch: Turing code: TUxxx process: TSMC 12nm FF
    built: 2018-22 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:1e84
    class-ID: 0300
  Device-2: Oculus VR Rift CV1 Sensor type: USB driver: uvcvideo bus-ID: 1-13.2:11
    chip-ID: 2833:0211 class-ID: ef00 serial: <filter>
  Device-3: Oculus VR Rift CV1 Sensor type: USB driver: uvcvideo bus-ID: 2-2.2:4
    chip-ID: 2833:0211 class-ID: ef00 serial: <filter>
  Device-4: Oculus VR Rift CV1 Sensor type: USB driver: uvcvideo bus-ID: 2-3:3 chip-ID: 2833:0211
    class-ID: ef00 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: nvidia gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 5360x1440 s-dpi: 109 s-size: 1249x333mm (49.17x13.11")
    s-diag: 1293mm (50.89")
  Monitor-1: DP-0 pos: primary,left res: 3440x1440 hz: 60 dpi: 110 size: 797x334mm (31.38x13.15")
    diag: 864mm (34.02") modes: N/A
  Monitor-2: HDMI-0 pos: right res: 1920x1080 hz: 60 dpi: 102 size: 477x268mm (18.78x10.55")
    diag: 547mm (21.54") modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 525.147.05 renderer: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2
    direct-render: Yes
Audio:
  Device-1: Intel Comet Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel v: kernel
    bus-ID: 5-2.4.2:22 chip-ID: 2833:0330 alternate: snd_sof_pci_intel_cnl bus-ID: 00:1f.3
    class-ID: 0300 chip-ID: 8086:06c8 serial: <filter> class-ID: 0403
  Device-2: NVIDIA TU104 HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:10f8 class-ID: 0403
  Device-3: Oculus VR Rift CV1 Audio type: USB driver: hid-generic,snd-usb-audio,usbhid
  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: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel pcie: gen: 2 speed: 5 GT/s
    lanes: 1 port: N/A bus-ID: 04:00.0 chip-ID: 8086:15f3 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel modules: wl pcie: gen: 2 speed: 5 GT/s
    lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-6.2:17
    chip-ID: 8087:0029 class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
    sub-v: 2090 hci-v: 5.2 rev: 2090
  Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
    service-classes: rendering, capturing, object transfer, audio, telephony
Drives:
  Local Storage: total: 3.17 TiB used: 1.42 TiB (44.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Intenso model: SSD SATA III size: 447.13 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 4H scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 EVO 2TB size: 1.82 TiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 1B6Q scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 3B6Q
    scheme: GPT
Partition:
  ID-1: / raw-size: 734.86 GiB size: 722.26 GiB (98.28%) used: 234.1 GiB (32.4%) fs: ext4
    dev: /dev/sdb5 maj-min: 8:21
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 29.0 C mobo: N/A gpu: nvidia temp: 32 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 26%
Repos:
  Packages: 2997 pm: dpkg pkgs: 2984 libs: 1482 tools: apt,apt-get,aptitude,nala pm: rpm pkgs: 0
    pm: flatpak pkgs: 13
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
  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://mirror.easyname.ch/mxlinux-packages/mx/repo/ bookworm main non-free
    2: deb http://mirror.easyname.ch/mxlinux-packages/mx/repo/ bookworm ahs
  No active apt repos in: /etc/apt/sources.list.d/steam-beta.list
  Active apt repos in: /etc/apt/sources.list.d/steam-stable.list
    1: deb [arch=amd64,i386 signed-by=/usr/share/keyrings/steam.gpg] https://repo.steampowered.com/steam/ stable steam
    2: deb-src [arch=amd64,i386 signed-by=/usr/share/keyrings/steam.gpg] https://repo.steampowered.com/steam/ stable steam
  Active apt repos in: /etc/apt/sources.list.d/vscode.list
    1: deb [arch=amd64] https://packages.microsoft.com/repos/vscode stable main
Info:
  Processes: 404 Uptime: 5m wakeups: 1 Memory: 15.51 GiB used: 4.23 GiB (27.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: UEFI
Top
aspacegamer
Posts: 87
Joined: Fri Oct 13, 2023 7:59 am

Re: MXLinux Audio Devices stop detecting shortly after boot

#5 Post by aspacegamer »

aspacegamer wrote: Sun Jan 07, 2024 10:29 am
j2mcgreg wrote: Sun Jan 07, 2024 9:58 am We are going to need your computer’s complete profile before we can proceed, so you need to post the output from the QSI utility. The Quick System Info (QSI) utility is located in MX Tools and its output is automatically formatted for use here in the forum. Run the QSI utility, click “Copy for Forum” at the bottom and then just paste it here in your thread.
Forum Rules
Will post them as soon as i can boot back into MXLinux on my device.
Nevermind it happened again this time after waking up from sleep here is the new output from my QSI:

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
    resume=UUID=<filter> resume_offset=121618432
  Desktop: KDE Plasma v: 5.27.5 info: kdocker wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.1_KDE_x64
    Libretto October 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: ROG STRIX Z490-F GAMING v: Rev 1.xx serial: <superuser required>
    UEFI: American Megatrends v: 2601 date: 05/17/2022
CPU:
  Info: model: Intel Core i9-10850K bits: 64 type: MT MCP arch: Comet Lake gen: core 10 level: v3
    note: check built: 2020 process: Intel 14nm family: 6 model-id: 0xA5 (165) stepping: 5
    microcode: 0xF8
  Topology: cpus: 1x cores: 10 tpc: 2 threads: 20 smt: enabled cache: L1: 640 KiB desc: d-10x32
    KiB; i-10x32 KiB L2: 2.5 MiB desc: 10x256 KiB L3: 20 MiB desc: 1x20 MiB
  Speed (MHz): avg: 1420 high: 4350 min/max: 800/5200 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 4334 6: 800 7: 800 8: 800 9: 800
    10: 800 11: 800 12: 800 13: 800 14: 800 15: 3399 16: 3535 17: 800 18: 800 19: 4350 20: 800
    bogomips: 144000
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: Enhanced IBRS
  Type: spec_rstack_overflow status: Not affected
  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: Enhanced IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: SW
    sequence
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA TU104 [GeForce RTX 2070 SUPER] vendor: ASUSTeK driver: nvidia v: 525.147.05
    non-free: 530.xx+ status: current (as of 2023-03) arch: Turing code: TUxxx process: TSMC 12nm FF
    built: 2018-22 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:1e84
    class-ID: 0300
  Device-2: Oculus VR Rift CV1 Sensor type: USB driver: uvcvideo bus-ID: 1-13.2:11
    chip-ID: 2833:0211 class-ID: ef00 serial: <filter>
  Device-3: Oculus VR Rift CV1 Sensor type: USB driver: uvcvideo bus-ID: 2-2.2:4
    chip-ID: 2833:0211 class-ID: ef00 serial: <filter>
  Device-4: Oculus VR Rift CV1 Sensor type: USB driver: uvcvideo bus-ID: 2-3:5 chip-ID: 2833:0211
    class-ID: ef00 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: nvidia gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 5360x1440 s-dpi: 109 s-size: 1249x333mm (49.17x13.11")
    s-diag: 1293mm (50.89")
  Monitor-1: DP-0 pos: primary,left res: 3440x1440 hz: 60 dpi: 110 size: 797x334mm (31.38x13.15")
    diag: 864mm (34.02") modes: N/A
  Monitor-2: HDMI-0 pos: right res: 1920x1080 hz: 60 dpi: 102 size: 477x268mm (18.78x10.55")
    diag: 547mm (21.54") modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 525.147.05 renderer: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2
    direct-render: Yes
Audio:
  Device-1: Intel Comet Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel v: kernel
    alternate: snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:06c8 class-ID: 0403
  Device-2: NVIDIA TU104 HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:10f8 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: off with: 1: pipewire-pulse status: active 2: wireplumber
    status: off 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel pcie: gen: 2 speed: 5 GT/s
    lanes: 1 port: N/A bus-ID: 04:00.0 chip-ID: 8086:15f3 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel modules: wl pcie: gen: 2 speed: 5 GT/s
    lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-6.2:17
    chip-ID: 8087:0029 class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 4 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
    sub-v: 2090 hci-v: 5.2 rev: 2090
  Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
    service-classes: object transfer
Drives:
  Local Storage: total: 3.17 TiB used: 1.42 TiB (44.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Intenso model: SSD SATA III size: 447.13 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 4H scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 EVO 2TB size: 1.82 TiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 1B6Q scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 3B6Q
    scheme: GPT
Partition:
  ID-1: / raw-size: 734.86 GiB size: 722.26 GiB (98.28%) used: 234.11 GiB (32.4%) fs: ext4
    dev: /dev/sdb5 maj-min: 8:21
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 32.0 C mobo: N/A gpu: nvidia temp: 31 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 26%
Repos:
  Packages: 2997 pm: dpkg pkgs: 2984 libs: 1482 tools: apt,apt-get,aptitude,nala pm: rpm pkgs: 0
    pm: flatpak pkgs: 13
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
  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://mirror.easyname.ch/mxlinux-packages/mx/repo/ bookworm main non-free
    2: deb http://mirror.easyname.ch/mxlinux-packages/mx/repo/ bookworm ahs
  No active apt repos in: /etc/apt/sources.list.d/steam-beta.list
  Active apt repos in: /etc/apt/sources.list.d/steam-stable.list
    1: deb [arch=amd64,i386 signed-by=/usr/share/keyrings/steam.gpg] https://repo.steampowered.com/steam/ stable steam
    2: deb-src [arch=amd64,i386 signed-by=/usr/share/keyrings/steam.gpg] https://repo.steampowered.com/steam/ stable steam
  Active apt repos in: /etc/apt/sources.list.d/vscode.list
    1: deb [arch=amd64] https://packages.microsoft.com/repos/vscode stable main
Info:
  Processes: 577 Uptime: 4h 48m wakeups: 7 Memory: 15.51 GiB used: 3.62 GiB (23.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: UEFI
Top
aspacegamer
Posts: 87
Joined: Fri Oct 13, 2023 7:59 am

Re: MXLinux Audio Devices stop detecting shortly after boot

#6 Post by aspacegamer »

One thing i notice is obviously

Code: Select all

Audio:
  Device-1: Intel Comet Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel v: kernel
    alternate: snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:06c8 class-ID: 0403
  Device-2: NVIDIA TU104 HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:10f8 class-ID: 0403
  API: ALSA v: k6.6.9-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: off with: 1: pipewire-pulse status: active 2: wireplumber
    status: off 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Top
aspacegamer
Posts: 87
Joined: Fri Oct 13, 2023 7:59 am

Re: MXLinux Audio Devices stop detecting shortly after boot

#7 Post by aspacegamer »

I am gonna try a reinstall of mx for now
Top
aspacegamer
Posts: 87
Joined: Fri Oct 13, 2023 7:59 am

Re: MXLinux Audio Devices stop detecting shortly after boot

#8 Post by aspacegamer »

After a complete reinstall and updating all packages the issue still persists trough this time i was able to verify that pipewire seems to crash i was able to restart it by executing /etc/xdg/autostart/pipewire-start.desktop and temporarly resolve the issue trough why this happens i have no idea.
Top
aspacegamer
Posts: 87
Joined: Fri Oct 13, 2023 7:59 am

Re: MXLinux Audio Devices stop detecting shortly after boot

#9 Post by aspacegamer »

For now i am gonna try to switch to systemd as my init since i remember that that one at least has some restart handling if a service crashes
Top
django013
Posts: 199
Joined: Sat Feb 11, 2023 3:25 am

Re: MXLinux Audio Devices stop detecting shortly after boot

#10 Post by django013 »

Well, in my observations sound comes back after few seconds first time. Second come back takes few minutes ...
I waited quarter of an hour for third come back, but it did not happen.
I don't use systemd - so I don't believe, that pipewire crashed.

Time until first mute is different at every boot, but behaviour after first mute is the same each time.
MC: ASUS PRIME A320M-K, AMD Ryzen 5 3600, NVIDIA Quadro P400
WS: ASRock X670E Steel Legend, AMD Ryzen 5 7600X, NVIDIA GTX 1660 SUPER
Top
Post Reply

Return to “Software / Configuration”