I have been using the “Teams For Linux” flathub app for a few days and at first I celebrated, because I could finally use teams without major workarounds and so that it just works. However today it decided to crash my audio device after about 20 minutes and it did so consistently… It crashes it so hard, that I need to restart my system every time it occurrs…

Things that do not work to get my audio back up and running:

  • restarting pipewire service with systemctl --user restart pipewire.service
  • restarting pipewire-pulse with systemctl --user restart pipewire-pulse.service
  • restarting alsa with sudo alsactl -F restore
  • relogging
  • unplugging USB

I am using Fedora 41 and my audio interface is the Motu M2

As far as I can tell the audio is just broken beyond repair and I have no idea why. I’ve always had audio problems on linux, but never to this degree. Maybe I have to try another distro, but I actually don’t really want to. It is just super annoying and if anyone has an idea how to fix this mess I will try it and hope that it works :D

  • masterofn001@lemmy.caEnglish
    2·
    13 days ago

    I don’t know if I can resolve this, but I’ve done some reading and the m2/m4 have some known issues with Linux.

    Some patches and configs and instructions are here:

    https://github.com/kiosion/alsa-motu-m2

    Aside from that, there could be another application that is locking the card which is why you’re getting the resource busy error.

    As mentioned here:

    https://unix.stackexchange.com/questions/753676/pipewire-pulse-no-sound-playback-open-failed-device-or-resource-busy

    And some more issues/troubleshooting specifically with the m4:

    https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3312

    • BentiGorlich@gehirneimer.deOP
      1·
      10 days ago

      So these are the log messages right after the device failed:

      Jan 21 11:20:41 fedora pipewire[2460]: spa.alsa: set_hw_params: Protokollfehler Jan 21 11:20:41 fedora pipewire[2460]: pw.link: 0x55db4830afa0: one of the nodes is in error out:error in:suspended Jan 21 11:20:41 fedora pipewire[2460]: pw.link: 0x55db485f9360: one of the nodes is in error out:error in:suspended Jan 21 11:20:44 fedora pipewire[2460]: spa.alsa: set_hw_params: Protokollfehler Jan 21 11:20:44 fedora pipewire[2460]: spa.alsa: set_hw_params: Protokollfehler Jan 21 11:20:44 fedora pipewire[2460]: spa.alsa: set_hw_params: Protokollfehler Jan 21 11:20:44 fedora pipewire[2460]: pw.link: 0x55db48355240: one of the nodes is in error out:suspended in:error Jan 21 11:20:44 fedora pipewire[2460]: pw.node: (alsa_output.usb-MOTU_M2_M2MT15188F-00.Direct__Direct__sink-56) suspended -> error ((null)) Jan 21 11:20:44 fedora pipewire[2460]: pw.link: 0x55db482bdca0: one of the nodes is in error out:idle in:error Jan 21 11:20:44 fedora pipewire[2460]: pw.link: 0x55db47b39140: one of the nodes is in error out:idle in:error

      I have no idea how to unsuspend the device after it errored, nor do I know why it errored. Like I said in the OP I’ve tried turning it off and on again, but the only solution I have found is to reboot which sucks… I changed the sampling rate from 41k to 48k but that didn’t change anything. I have no idea how to change the bit depth of the device though. I applied the fixes from the repo you linked, but I am not able to install the version of alsa they referenced in there. Fedore 41 only comes with the 2 most recent versions it seems…