On Linux Mint 22.3 Cinnamon Framework 13 with jack 3.5mm being plugged to BOSE SoundLink Mini II I correctly get a new *Device*, but there is no physical sound output, what is this issue? I am not interested in Bluetooth.
Aug 24, 6:02pm

The issue you're describing—where your Bose SoundLink Mini II is detected as a device when connected via a 3.5mm jack on Linux Mint 22.3 (Cinnamon, Framework 13) but produces no sound—could stem from several common causes. Let's break this down systematically:


1. Check the Output Device Selection

  • Issue: The system may default to another output (e.g., built-in speakers) even if the Bose device is detected.
  • Solution:
    • Open Sound Settings (via the menu or pavucontrol in the terminal).
    • Go to the Output tab and ensure the Bose SoundLink Mini II (or the 3.5mm jack) is selected as the active output device.
    • Test sound while toggling between devices.

2. Volume and Mute Controls

  • Issue: The output volume for the 3.5mm jack or the Bose device might be muted or set to zero.
  • Solution:
    • In Sound Settings, check the volume slider for the Bose device.
    • Use alsamixer in the terminal to verify that the 3.5mm output is not muted (look for MM indicators, which mean muted; press M to unmute).
    • Ensure the Bose device's physical volume is turned up.

3. Driver or ALSA/PulseAudio Configuration

  • Issue: The 3.5mm jack might not be properly recognized or routed by the audio subsystem (ALSA/PulseAudio).
  • Solution:
    • Run aplay -l in the terminal to list available ALSA playback devices. Verify that the 3.5mm jack is listed.
    • Run pactl list sinks to check if PulseAudio detects the Bose device as a sink.
    • If the device is listed but not working, try restarting PulseAudio:
      bash
      pulseaudio -k && pulseaudio --start

4. Hardware or Connection Issues

  • Issue: The 3.5mm jack or the Bose device might have a loose connection, or the cable might be faulty.
  • Solution:
    • Test the 3.5mm cable with another device (e.g., phone or tablet) to rule out cable issues.
    • Try plugging the cable into a different port (if available) on your Linux Mint machine.
    • Ensure the Bose device is powered on and the 3.5mm input is selected (some speakers have a physical switch or button for input mode).

5. Audio Profile Misconfiguration

  • Issue: The system might be defaulting to a non-functional audio profile (e.g., "Digital Stereo (HDMI)" instead of "Analog Stereo").
  • Solution:
    • Open Sound Settings > Configuration tab.
    • Select the Analog Stereo Output profile for the 3.5mm jack.
    • If using pavucontrol, go to the Configuration tab and ensure the correct profile is selected.

6. Kernel or Driver Bugs

  • Issue: Rarely, kernel or driver bugs can cause audio routing issues for specific hardware.
  • Solution:
    • Check for updates:
      bash
      sudo apt update && sudo apt upgrade
    • If the issue persists, search for known issues with your sound card model (run lspci | grep -i audio to identify it) and the Linux Mint 22.3 kernel version (run uname -r).

7. Test with Another Application

  • Issue: The problem might be application-specific (e.g., browser, media player).
  • Solution:
    • Test sound with multiple applications (e.g., aplay /usr/share/sounds/alsa/Front_Center.wav, VLC, or a YouTube video).
    • If sound works in some apps but not others, the issue is likely with the application's audio settings.

8. Debugging with Logs

  • Issue: Errors in the audio subsystem might not be visible in the GUI.
  • Solution:
    • Check PulseAudio logs:
      bash
      pulseaudio --log-level=debug
    • Check kernel logs for audio-related errors:
      bash
      dmesg | grep -i audio

Next Steps

If none of the above works:

  • Try the Bose device on another computer to confirm it works via 3.5mm.
  • Test another set of speakers/headphones on your Linux Mint machine to isolate the issue.

Question: Have you tried any of these steps already? If so, which ones, and what was the outcome? This will help narrow down the issue.

Aug 24, 6:02pm

This is a shared conversation and may include unverified content that doesn't reflect Mistral AI's views. Login to resume chatting.

Vibe can make mistakes. Check answers. Learn more