WeirdTreeThing
No audio out of internal speakers on Gateway N6000 Chromebook
Describe the bug
After doing a fresh install of LMDE 6 and running the script from this page, I can get audio out of the headphone jack, but nothing out of the internal speakers. Pipewire shows audio being properly routed into the speakers as well.
If there is any other commands for further information that you need to look further into this, please do not hesitate to ask.
Boardname Pasara
Logs debug-logs-Pasara-2024-08-20_22h28m.tar.gz
JasperLake is such a cursed architecture...
It looks like ALSA doesn't follow boardname reported by dmidecode for some reason.
access("/usr/share/alsa/ucm2/0/0.conf", R_OK) = -1 ENOENT (No such file or directory)
Is there anything I could do on my end to try something else or any further information I could provide?
JasperLake is such a cursed architecture...
It looks like ALSA doesn't follow boardname reported by dmidecode for some reason.
access("/usr/share/alsa/ucm2/0/0.conf", R_OK) = -1 ENOENT (No such file or directory)
audio-debug.log shows that the audio server does correctly load the UCM, so it should be safe to ignore that.
Poking my head back here to see if there has been any update. Still have this machine and would love to have audio working on the built in speakers. Nothings changed software wise from the original post about a year ago.
I think it has been too long since I last did that. I don't remember what the script was, could I kindly ask for a refresher? I will give it a try and report back.
I should have opened my eyes a little more, but I removed the folder, re-ran the download script, cd into the directory and ran the command again and what is shown in the screenshot is what I have now. I did do a restart as well and the audio source on the right still shows as a dummy output.
Linux mint is based on Ubuntu LTS, which has libraries too old to support the alsa UCM for chromebooks.
I know the list of OS listed says Debian Testing, but would the latest Debian 13 work as well? I would be willing to install that then running the command and come back with my results.
Moved over to Debian 13 and here is what I get when running through the command again.
Ah yeah, at the time Debian 13 was testing. It looks like there is an issue in the UCM where it can't detect the platform you are on.
I need to figure out the best way to detect a JSL chromebook as google didn't set the smbios platform name for some reason.
Copy that. If there is anything you need me to run on my end on this machine and feed the info back to you, please let me know and I will help out when and how I can. Thank you again for your help and attention to all of this.
Pinging everyone who created issues which I've merged into this one: @ruocchio @errtun @bobbyxdevel-gh @HWdriver @GamesphereOo
Can you all send the output of cat /sys/bus/pci/devices/0000:00:02.0/device
Pinging everyone who created issues which I've merged into this one: @ruocchio @errtun @bobbyxdevel-gh @HWdriver @GamesphereOo
Can you all send the output of
cat /sys/bus/pci/devices/0000:00:02.0/deviceWehrcraft@Chromehack:~$ cat /sys/bus/pci/devices/0000:00:02.0/device 0x4e71
here are the two outputs. I am on a fresh fedora install and on the BOTENFLEX board
Sure thing, here it is for Drawman (HP Chromebook 14 G7):
ls /sys/bus/platform/devices
ACPI0003:00 cros-usbpd-logger.4.auto i2c_designware.3 INT3403:00 PNP0C0A:00 alarmtimer.0.auto dmic-codec i2c_designware.4 INT3403:01 PNP0C0D:00 BOOT0000:00 dw-apb-uart.5 i8042 INT3403:02 PRP0001:00 coretemp.0 dw-apb-uart.6 idma64.0 INT3403:03 pxa2xx-spi.7 cros-charge-control.7.auto efivars.0 idma64.1 INT3403:04 reg-dummy cros-ec-chardev.8.auto GOOG0002:00 idma64.2 INT34C8:00 regulatory.0 cros-ec-debugfs.9.auto GOOG0003:00 idma64.3 INTC1026:00 rtc-efi.0 cros-ec-dev.1.auto GOOG0004:00 idma64.6 intel_rapl_msr.0 serial8250 cros-ec-gpio.2.auto GOOG0006:00 idma64.7 jsl_rt5682_def simple-framebuffer.0 cros-ec-hwmon.10.auto GOOG0007:00 INT0800:00 microcode snd-soc-dummy cros-ec-led.5.auto GOOG0014:00 INT33A1:00 MX98360A:00 cros-ec-sysfs.11.auto i2c_designware.0 INT33D3:00 pcspkr cros-keyboard-leds.6.auto i2c_designware.1 INT33D6:00 PNP0C04:00 cros-usbpd-charger.3.auto i2c_designware.2 INT3400:00 PNP0C09:00
cat /sys/bus/pci/devices/0000:00:02.0/device
0x4e61
@azurusnova:
Here is what i found to get it working:
https://github.com/WeirdTreeThing/chromebook-linux-audio/issues/348
Sure thing, here it is for Drawman (HP Chromebook 14 G7):
ls /sys/bus/platform/devices
ACPI0003:00 cros-usbpd-logger.4.auto i2c_designware.3 INT3403:00 PNP0C0A:00 alarmtimer.0.auto dmic-codec i2c_designware.4 INT3403:01 PNP0C0D:00 BOOT0000:00 dw-apb-uart.5 i8042 INT3403:02 PRP0001:00 coretemp.0 dw-apb-uart.6 idma64.0 INT3403:03 pxa2xx-spi.7 cros-charge-control.7.auto efivars.0 idma64.1 INT3403:04 reg-dummy cros-ec-chardev.8.auto GOOG0002:00 idma64.2 INT34C8:00 regulatory.0 cros-ec-debugfs.9.auto GOOG0003:00 idma64.3 INTC1026:00 rtc-efi.0 cros-ec-dev.1.auto GOOG0004:00 idma64.6 intel_rapl_msr.0 serial8250 cros-ec-gpio.2.auto GOOG0006:00 idma64.7 jsl_rt5682_def simple-framebuffer.0 cros-ec-hwmon.10.auto GOOG0007:00 INT0800:00 microcode snd-soc-dummy cros-ec-led.5.auto GOOG0014:00 INT33A1:00 MX98360A:00 cros-ec-sysfs.11.auto i2c_designware.0 INT33D3:00 pcspkr cros-keyboard-leds.6.auto i2c_designware.1 INT33D6:00 PNP0C04:00 cros-usbpd-charger.3.auto i2c_designware.2 INT3400:00 PNP0C09:00
cat /sys/bus/pci/devices/0000:00:02.0/device
0x4e61
Here is what i found to get it working:
I tried this and this did not work for me. Followed your steps and saw the same things in the pavucontrol window, but audio did not work for me and in the normal audio window, several devices would pop up.
Pinging everyone who created issues which I've merged into this one: @ruocchio @errtun @bobbyxdevel-gh @HWdriver @GamesphereOo
Can you all send the output of
cat /sys/bus/pci/devices/0000:00:02.0/device
I tried this and this did not work for me. Followed your steps and saw the same things in the pavucontrol window, but audio did not work for me and in the normal audio window, several devices would pop up.
For me it worked with the Audio Pro, without any numbers, not sure if it required a reboot though.
You're still on LMDE 6?