Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MacMini8,1 + Mint 22 = no sound #597

Open
igorsantos07 opened this issue Dec 19, 2024 · 20 comments
Open

MacMini8,1 + Mint 22 = no sound #597

igorsantos07 opened this issue Dec 19, 2024 · 20 comments

Comments

@igorsantos07
Copy link
Contributor

This could be a mild follow up to #203 lol

I've reinstalled Mint, moving to Wilma 22 with Cinnamon, a couple of months ago. Wi-Fi was working mostly fine, although now I'm not sure if it was because I had an extra Bluetooth+Wi-Fi dongle sneakily plugged in, which I forgot had Wi-Fi capabilities 😂
At some point that stopped working, though, and I came back to the wiki - then, I must say, the Wi-Fi script from the wiki was painless to use!

On the other hand, I can't get the audio jack to work, no matter what I try. Here's the information I have, given other posts I've found around:

  • I tried all the different kernel lines from the Debian/Ubuntu lines - currently I'm at 6.12.4-1-t2-noble
  • Easyeffects does show up as a device on the sound panel, but the best I can do is test left/right output, and it emits from the internal speaker.
  • tried the script from https://wiki.t2linux.org/guides/audio-config/#audio-configuration-files
  • cat /proc/cmdline yields BOOT_IMAGE=/boot/vmlinuz-6.12.4-1-t2-noble root=UUID=b35ca6bf-f93c-4d89-8051-607b2fa43340 ro quiet splash intel_iommu=on iommu=pt pcie_ports=compat
  • sed -n "s/.*\(AppleT2.*\) -.*/\1/p" /proc/asound/cards yields AppleT2x1

The only thing I didn't try was editing initramfs-tools, which seemed a bit too drastic / unrelated?

@AdityaGarg8
Copy link
Member

This could be a mild follow up to #203 lol

I've reinstalled Mint, moving to Wilma 22 with Cinnamon, a couple of months ago. Wi-Fi was working mostly fine, although now I'm not sure if it was because I had an extra Bluetooth+Wi-Fi dongle sneakily plugged in, which I forgot had Wi-Fi capabilities 😂 At some point that stopped working, though, and I came back to the wiki - then, I must say, the Wi-Fi script from the wiki was painless to use!

On the other hand, I can't get the audio jack to work, no matter what I try. Here's the information I have, given other posts I've found around:

  • I tried all the different kernel lines from the Debian/Ubuntu lines - currently I'm at 6.12.4-1-t2-noble
  • Easyeffects does show up as a device on the sound panel, but the best I can do is test left/right output, and it emits from the internal speaker.
  • tried the script from https://wiki.t2linux.org/guides/audio-config/#audio-configuration-files
  • cat /proc/cmdline yields BOOT_IMAGE=/boot/vmlinuz-6.12.4-1-t2-noble root=UUID=b35ca6bf-f93c-4d89-8051-607b2fa43340 ro quiet splash intel_iommu=on iommu=pt pcie_ports=compat
  • sed -n "s/.*\(AppleT2.*\) -.*/\1/p" /proc/asound/cards yields AppleT2x1

The only thing I didn't try was editing initramfs-tools, which seemed a bit too drastic / unrelated?

You have to manually change to audio jack from settings>sounds

@igorsantos07
Copy link
Contributor Author

Sorry for not making it clear: that's not an option. The only devices shown for me are the HDMI / DP built-in audio, and the internal speaker (which seems to vanish sometimes). If I open Easyeffects, that also shows as a device, as well as the Bluetooth speaker I'm using temporarily (the one selected in the screenshot below).

image

@AdityaGarg8
Copy link
Member

What ISO did you use?

@igorsantos07
Copy link
Contributor Author

igorsantos07 commented Dec 22, 2024 via email

@AdityaGarg8
Copy link
Member

The original one from the Mint website. Then I installed the T2 kernel for Noble, the equivalent Ubuntu release, and many different audio packages as suggested on the wiki. Igor Santos -- Desenvolvedor web [enviado do meu celular]

On Sat, 21 Dec 2024, 14:30 Aditya Garg, @.> wrote: What ISO did you use? — Reply to this email directly, view it on GitHub <#597 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEB6S3WS7PZZJYBHEZ6BOT2GWQUFAVCNFSM6AAAAABT375NU6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJYGE4DCNBXGM . You are receiving this because you authored the thread.Message ID: @.>

Is apple-t2-audio-config installed? Also, what is pactl info

@igorsantos07
Copy link
Contributor Author

igorsantos07 commented Dec 22, 2024

I had to reboot and the internal speaker showed up again. The only profile it has is "Mono output":

image

apple-t2-audio-config was already installed, sorry for not mentioning it.

$ pactl info
Server String: /run/user/1000/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 231
Tile Size: 65472
User Name: igoru
Host Name: mac-mint
Server Name: PulseAudio (on PipeWire 1.0.5)
Server Version: 15.0.0
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.pci-0000_02_00.3.mono-fallback
Default Source: alsa_input.usb-046d_Logitech_BRIO_E0CF9B71-03.iec958-stereo
Cookie: eaf5:3576

@AdityaGarg8
Copy link
Member

It's strange that it's not showing up. @Redecorating can you help?

@Redecorating
Copy link
Member

Redecorating commented Dec 23, 2024 via email

@igorsantos07
Copy link
Contributor Author

igorsantos07 commented Dec 24, 2024

Hope this is of any use 🙏

Dec 24 13:17:05 mac-mint kernel: aaudio: capturing our device
Dec 24 13:17:05 mac-mint kernel: aaudio 0000:02:00.3: enabling device (0000 -> 0002)
Dec 24 13:17:05 mac-mint kernel: aaudio aaudio: aaudio: bs len = 400000
Dec 24 13:17:05 mac-mint kernel: aaudio aaudio: Received boot notification from remote
Dec 24 13:17:05 mac-mint kernel: aaudio aaudio: Received alive notification from remote
Dec 24 13:17:05 mac-mint kernel: aaudio aaudio: Received alive notification from remote
Dec 24 13:17:05 mac-mint kernel: aaudio aaudio: Continuing init
Dec 24 13:17:05 mac-mint kernel: aaudio aaudio: Remote device 21 Codec Output
Dec 24 13:17:05 mac-mint kernel: aaudio aaudio: Remote device 35 Speaker
Dec 24 13:17:05 mac-mint kernel: aaudio aaudio: Remote device 3b Codec Input
Dec 24 13:17:05 mac-mint kernel: aaudio aaudio: aaudio: BufferStruct ver = 3
Dec 24 13:17:05 mac-mint kernel: aaudio aaudio: aaudio: Num devices = 2
Dec 24 13:17:05 mac-mint kernel: aaudio aaudio: aaudio: Device 0 Speaker
Dec 24 13:17:05 mac-mint kernel: aaudio aaudio: aaudio: Device 0 Stream 0: Output; Buffer Count = 1
Dec 24 13:17:05 mac-mint kernel: aaudio aaudio: aaudio: Device 1 Codec Output
Dec 24 13:17:05 mac-mint kernel: aaudio aaudio: aaudio: Device 1 Stream 0: Output; Buffer Count = 1
Dec 24 13:17:05 mac-mint kernel: aaudio aaudio: aaudio: Created device 2 Codec Input
Dec 24 13:17:05 mac-mint kernel: aaudio aaudio: aaudio: Device 2 Host Stream; Input
Dec 24 13:17:05 mac-mint kernel: input: Apple T2 Audio Codec Output as /devices/pci0000:00/0000:00:1b.0/0000:02:00.3/aaudio/aaudio/card0/input14
Dec 24 13:17:06 mac-mint kernel: usbcore: registered new interface driver snd-usb-audio
Dec 24 13:17:09 mac-mint kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
Dec 24 13:17:47 mac-mint kernel: aaudio_pcm_pointer while not started

Merry Christmas for you all, if that's your culture! 🎄

@Redecorating
Copy link
Member

Redecorating commented Dec 24, 2024 via email

@Redecorating
Copy link
Member

i can't seem to make that message not have terrible formatting by editing it, let's try again here:

[Mapping Speakers]
device-strings = hw:%f,0
paths-output = t2-speakers
channel-map = mono
direction = output

[Mapping Headphones]
device-strings = hw:%f,1
paths-output = t2-headphones
channel-map = mono
direction = output

[Mapping HeadsetMic]
device-strings = hw:%f,2
paths-input = t2-headset-mic
channel-map = mono
direction = input

[Profile Default]
description = Default Profile
output-mappings = Speakers Headphones
input-mappings = HeadsetMic

@igorsantos07
Copy link
Contributor Author

Thanks for that! No clue what you did with the markdown formatting 😂

And no, AFAIK there's no internal speaker. Not that I care for it either. The headphone jack is a single one, which should be stereo.

But also... no clue what I should do with that 😅 Could you point me to where I should place that config?

@Redecorating
Copy link
Member

Redecorating commented Dec 26, 2024 via email

@igorsantos07
Copy link
Contributor Author

Sorry! I said it wrong, I don't think it has an internal 🎙️

I created /usr/share/alsa-card-profile/mixer/profile-sets/apple-t2x1.conf and /usr/share/pulseaudio/alsa-mixer/profile-sets/apple-t2x1.conf, with the same contents you posted earlier. Rebooted and... nothing 😥
I see the script doesn't do anything after copying the files, either. Should I run some other command to refresh the related subsystems?

Trying to reboot again as the internal speaker didn't show up either.

@igorsantos07
Copy link
Contributor Author

igorsantos07 commented Dec 27, 2024

I rebooted three FOUR times in total:

  1. added files, rebooted. It only showed me the HDMI output.
  2. no changes; rebooted again, it took a while to boot up but other than that, same results.
  3. renamed the new files so they would go missing, and rebooted once more. This time, the internal speaker is back again.
  4. edited the file to say left,right in place of mono on the Speaker mapping, rebooted again, and the internal speaker is gone again (I mean, not that I care for it at all, but I guess it could mean something to you).

🤔 🤔 🤔

And btw, the only files under the alsa-mixer folder are the ones created by that script, so I guess that would be the wrong folder in my distro. But I added it to both anyway (the alsa-card-profile also includes config files for many other devices).

@Redecorating
Copy link
Member

Redecorating commented Dec 27, 2024 via email

@igorsantos07
Copy link
Contributor Author

No big changes to pactl info other than the default sink becoming my HDMI output, and numeric/hash changes in client index, tile size, and cookie.

Recently, I submitted a PR to some other unrelated repo, and learned there that user services would use systemctl --user. I added that option and the stop calls worked - without that and sudo, there would be simply a graphical password prompt and an error would be emitted.

Nonetheless, I had some trouble with the stop/restart commands; in the end, there was no output anymore in the Sound Settings screen, and pipewire said nothing useful. 😅 Not sure if all the trouble is because I got the stop order backwards, but... Here's what happened, in case you're curious:

$ systemctl --user stop pipewire.service
Stopping 'pipewire.service', but its triggering units are still active:
pipewire.socket
$ systemctl --user stop pipewire.socket
$ pipewire -v
[W][06132.324996] mod.jackdbus-detect | [module-jackdbus-:  216 on_is_started_received()] Failed to receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown: The name org.jackaudio.service was not provided by any .service files
# nothing else other than this; it didn't close either, just kept running in complete silence

On the other terminal I ended up running the restart/start/status multiple times, checking if pipewire would react:

 23:31:54  ~  systemctl --user restart pipewire-pulse
 23:32:02  ~  systemctl restart pipewire-pulse
Failed to restart pipewire-pulse.service: Unit pipewire-pulse.service not found.
 23:32:32  ~  systemctl --user restart pipewire-pulse
 23:32:43  ~  systemctl --user start pipewire-pulse
 23:33:51  ~  systemctl --user status pipewire-pulse
● pipewire-pulse.service - PipeWire PulseAudio
     Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; enabled; preset: enabled)
     Active: active (running) since Thu 2024-12-26 23:32:43 -03; 1min 12s ago
TriggeredBy: ● pipewire-pulse.socket
   Main PID: 106883 (pipewire-pulse)
      Tasks: 3 (limit: 23567)
     Memory: 1.9M (peak: 2.7M)
        CPU: 49ms
     CGroup: /user.slice/user-1000.slice/[email protected]/session.slice/pipewire-pulse.service
             └─106883 /usr/bin/pipewire-pulse

Dec 26 23:33:49 mac-mint pipewire-pulse[106883]: mod.protocol-pulse: client 0x5c3bb9215860 [Cinnamon Volume Control Media Keys]: ERROR command:9 (SET_CLIENT_NAME) tag:1 error:6 (Host is down)
Dec 26 23:33:49 mac-mint pipewire-pulse[106883]: mod.protocol-pulse: 0x5c3bb91e2050: failed to connect client: Host is down
Dec 26 23:33:49 mac-mint pipewire-pulse[106883]: mod.protocol-pulse: client 0x5c3bb9215670 [Sound150 Volume Control]: ERROR command:9 (SET_CLIENT_NAME) tag:1 error:6 (Host is down)
Dec 26 23:33:52 mac-mint pipewire-pulse[106883]: default: snap_get_audio_permissions: kernel lacks 'fine grained unix mediation'; snap audio permissions won't be honored.
Dec 26 23:33:54 mac-mint pipewire-pulse[106883]: default: snap_get_audio_permissions: kernel lacks 'fine grained unix mediation'; snap audio permissions won't be honored.
Dec 26 23:33:54 mac-mint pipewire-pulse[106883]: default: snap_get_audio_permissions: kernel lacks 'fine grained unix mediation'; snap audio permissions won't be honored.
Dec 26 23:33:54 mac-mint pipewire-pulse[106883]: mod.protocol-pulse: 0x5c3bb91e2050: failed to connect client: Host is down
Dec 26 23:33:54 mac-mint pipewire-pulse[106883]: mod.protocol-pulse: client 0x5c3bb9217220 [Cinnamon Volume Control Media Keys]: ERROR command:9 (SET_CLIENT_NAME) tag:1 error:6 (Host is down)
Dec 26 23:33:54 mac-mint pipewire-pulse[106883]: mod.protocol-pulse: 0x5c3bb91e2050: failed to connect client: Host is down
Dec 26 23:33:54 mac-mint pipewire-pulse[106883]: mod.protocol-pulse: client 0x5c3bb9216b60 [Sound150 Volume Control]: ERROR command:9 (SET_CLIENT_NAME) tag:1 error:6 (Host is down)
~
~

On a third terminal, I tried checking the status of the other services I had stopped, and turns out they also had trouble:

 23:34:31  ~  systemctl --user status pipewire.service
× pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Thu 2024-12-26 23:33:52 -03; 48s ago
   Duration: 20ms
TriggeredBy: × pipewire.socket
    Process: 108048 ExecStart=/usr/bin/pipewire (code=exited, status=245/KSM)
   Main PID: 108048 (code=exited, status=245/KSM)
        CPU: 16ms

Dec 26 23:33:52 mac-mint systemd[1270]: pipewire.service: Scheduled restart job, restart counter is at 5.
Dec 26 23:33:52 mac-mint systemd[1270]: pipewire.service: Start request repeated too quickly.
Dec 26 23:33:52 mac-mint systemd[1270]: pipewire.service: Failed with result 'exit-code'.
Dec 26 23:33:52 mac-mint systemd[1270]: Failed to start pipewire.service - PipeWire Multimedia Service.
~
~

 23:34:53  ~  systemctl --user start pipewire.service
 23:34:57  ~  systemctl --user status pipewire.service
× pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Thu 2024-12-26 23:34:59 -03; 650ms ago
   Duration: 24ms
TriggeredBy: × pipewire.socket
    Process: 109414 ExecStart=/usr/bin/pipewire (code=exited, status=245/KSM)
   Main PID: 109414 (code=exited, status=245/KSM)
        CPU: 17ms

Dec 26 23:34:59 mac-mint systemd[1270]: pipewire.service: Scheduled restart job, restart counter is at 5.
Dec 26 23:34:59 mac-mint systemd[1270]: pipewire.service: Start request repeated too quickly.
Dec 26 23:34:59 mac-mint systemd[1270]: pipewire.service: Failed with result 'exit-code'.
Dec 26 23:34:59 mac-mint systemd[1270]: Failed to start pipewire.service - PipeWire Multimedia Service.

 23:34:59  ~  systemctl --user status pipewire.socket
× pipewire.socket - PipeWire Multimedia System Sockets
     Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; preset: enabled)
     Active: failed (Result: service-start-limit-hit) since Thu 2024-12-26 23:34:59 -03; 9s ago
   Duration: 1.307s
   Triggers: ● pipewire.service
     Listen: /run/user/1000/pipewire-0 (Stream)
             /run/user/1000/pipewire-0-manager (Stream)

Dec 26 23:34:57 mac-mint systemd[1270]: Listening on pipewire.socket - PipeWire Multimedia System Sockets.
Dec 26 23:34:59 mac-mint systemd[1270]: pipewire.socket: Failed with result 'service-start-limit-hit'.

 23:35:08  ~  systemctl --user restart pipewire.socket
 23:35:22  ~  systemctl --user status pipewire.socket
● pipewire.socket - PipeWire Multimedia System Sockets
     Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; preset: enabled)
     Active: active (listening) since Thu 2024-12-26 23:35:22 -03; 1s ago
   Triggers: ● pipewire.service
     Listen: /run/user/1000/pipewire-0 (Stream)
             /run/user/1000/pipewire-0-manager (Stream)
     CGroup: /user.slice/user-1000.slice/[email protected]/app.slice/pipewire.socket

Dec 26 23:35:22 mac-mint systemd[1270]: Listening on pipewire.socket - PipeWire Multimedia System Sockets.

 23:35:24  ~  systemctl --user start pipewire.service
Job for pipewire.service failed because the control process exited with error code.
See "systemctl --user status pipewire.service" and "journalctl --user -xeu pipewire.service" for details.

 23:35:33  ~  systemctl --user status pipewire.service
× pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Thu 2024-12-26 23:35:25 -03; 28s ago
   Duration: 16ms
TriggeredBy: × pipewire.socket
    Process: 109885 ExecStart=/usr/bin/pipewire (code=exited, status=245/KSM)
   Main PID: 109885 (code=exited, status=245/KSM)
        CPU: 15ms

Dec 26 23:35:25 mac-mint systemd[1270]: pipewire.service: Scheduled restart job, restart counter is at 5.
Dec 26 23:35:25 mac-mint systemd[1270]: pipewire.service: Start request repeated too quickly.
Dec 26 23:35:25 mac-mint systemd[1270]: pipewire.service: Failed with result 'exit-code'.
Dec 26 23:35:25 mac-mint systemd[1270]: Failed to start pipewire.service - PipeWire Multimedia Service.
Dec 26 23:35:33 mac-mint systemd[1270]: pipewire.service: Start request repeated too quickly.
Dec 26 23:35:33 mac-mint systemd[1270]: pipewire.service: Failed with result 'exit-code'.
Dec 26 23:35:33 mac-mint systemd[1270]: Failed to start pipewire.service - PipeWire Multimedia Service.

 23:35:54  ~  journalctl --user -xeu pipewire.service
░░ 
░░ The unit UNIT has entered the 'failed' state with result 'exit-code'.
Dec 26 23:35:25 mac-mint systemd[1270]: Failed to start pipewire.service - PipeWire Multimedia Service.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 1392 and the job result is failed.
Dec 26 23:35:33 mac-mint systemd[1270]: pipewire.service: Start request repeated too quickly.
Dec 26 23:35:33 mac-mint systemd[1270]: pipewire.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit UNIT has entered the 'failed' state with result 'exit-code'.
Dec 26 23:35:33 mac-mint systemd[1270]: Failed to start pipewire.service - PipeWire Multimedia Service.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 1418 and the job result is failed.

That all said pasted, unless you're very interested in having this fixed for the repo as a whole, I'm really leaning towards buying a cheapo USB sound card and calling it a day. It doesn't seem worthy to spend all this valuable time of yours, trying to fix the soundcard of someone random on the web, given I think I could live with a dirty workaround behind my desk 🤷‍♂️

@Redecorating
Copy link
Member

Redecorating commented Dec 27, 2024 via email

@igorsantos07
Copy link
Contributor Author

Thanks for trying, anyway! Hope you two have an awesome 2025 🎆

@AdityaGarg8
Copy link
Member

Thanks for trying, anyway! Hope you two have an awesome 2025 🎆

Same to you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants