chromebook-linux-audio icon indicating copy to clipboard operation
chromebook-linux-audio copied to clipboard

LARS Internal mic and wired headset jack output does not work; speakers inexplicably work on Fedora 41 and OpenSUSE Tumbleweed

Open Zoatebix opened this issue 10 months ago • 5 comments

Describe the bug Despite the script telling me in no uncertain terms that the internal speakers will not work, the speakers work perfectly. However, the built-in microphone does not work. The 3.5mm headphone/headset jack does not work for audio output; at least not for system sounds, media playback, etc..

I don't know if I simply didn't notice this when testing on Fedora over the last few weeks, but on Tumbleweed the input from the headset microphone seems to be directly monitored by the headset's output.

Boardname LARS

Logs Logs on Fedora41 (headset input seems to work as expected, output does not) are from 2025-02-12 Logs on OpenSUSE Tumbleweed (headset input seems to work, though it is also piped directly to headset output) are from 2025-02-21

debug-logs-Lars-2025-02-12_07h08m trouchscreen not working.tar.gz

debug-logs-Lars-2025-02-21_18h51m.tar.gz

Zoatebix avatar Feb 22 '25 00:02 Zoatebix

Issue in script, pull it and try again.

WeirdTreeThing avatar Mar 17 '25 17:03 WeirdTreeThing

Thank you! Git is assuring me that my local copy is up to date when I run git pull, but the problem persists after re-running the script. I also tried deleting the folder and re-running git clone https://github.com/WeirdTreeThing/chromebook-linux-audio.

Speakers still work regardless of whether I run the script with no arguments or add the --force-avs-install argument. I thought the headset-mic to headset-output direct connection was solved after I ran the script with --force-avs-install and rebooted (though there was still no playback over headphones), but it started happening again after I removed and re-plugged the headset.

Here's the latest debug logs on OpenSUSE after running the script with --force-avs-install: https://drive.google.com/file/d/1HO9kCpyBo1jJFTHy-xHYvUJkLPvDgAC5/view?usp=sharing

Zoatebix avatar Mar 18 '25 05:03 Zoatebix

Can you send the output of arecord -l

WeirdTreeThing avatar Mar 20 '25 00:03 WeirdTreeThing

Absolutely!

**** List of CAPTURE Hardware Devices ****
card 2: avsdmic [avs_dmic], device 2: Digital Microphone (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 3: avsnau8825 [avs_nau8825], device 1: Headset (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

I've also noticed that the headphones are monitoring the headset input regardless of whether I ask KDE to switch to the internal mic or if I ask KDE to mute the headset mic.

Unrelated: Today, I managed to get the speakers to blare static when I tried the volume up and down buttons with a headset plugged in. I tried to recreate the sequence of plugging a headset, checking the KDE Plasma system tray icon, and pressing the volume keys that led to that outcome, but I've been unable to make it happen a second time.

Zoatebix avatar Mar 21 '25 18:03 Zoatebix

I swapped back to my Fedora 41 installation, upgraded everything everything dnf and flatpak had for me, and pulled and re-ran the script. Things are configured slightly differently than in OpenSUSE - the capture devices are listed as cards 3 and 4 instead of 2 and 3, but otherwise the behavior is the same:

~$ arecord -l
**** List of CAPTURE Hardware Devices ****
card 3: avsdmic [avs_dmic], device 2: Digital Microphone (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 4: avsnau8825 [avs_nau8825], device 1: Headset (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Zoatebix avatar Mar 24 '25 01:03 Zoatebix