search

WeirdTreeThing / chromebook-linux-audio

Script to enable audio support on many Chrome devices
BSD 3-Clause "New" or "Revised" License
240 stars 47 forks source link

No audio on Fedora #151

Open Aeyk opened 2 months ago

Aeyk commented 2 months ago

Describe the bug Fedora Rawhide 41 on 6.10.0 Kernel. No audio on any of the devices. There are two sets of devices, default and Pro Audio, which has four devices, numberless, 1, 5, 6 and 7. If I change to default with the KDE Plasma Pulse applet they all disappear and all that remains are dummy outputs.

Boardname Lick

$ cat /proc/asound/cards 0 [sofglkda7219max]: sof-glkda7219ma - sof-glkda7219max Google-Lick-rev4

Logs debug-logs.tar.gz

Abubakr4Dev commented 2 months ago

i have solved my problem with this steps

1- first install package named pulseaudio-utils

2- run this command pactl list cards , The output will contain, for example, name: , copy card name

3- after that run this command pactl set-card-profile YourCardName pro-audio , replace YourCardName with your own one.

Now your problem should be solved, as happened to me. Perhaps this solution will be useful to you.

you can try this solution immediately after fresh installing without using chromebook-linux-audio , And it will work too.

WeirdTreeThing commented 2 months ago

@Abubakr4Dev Please do not comment on a thread if you don't have the same device, and especially stop giving unhelpful advice. Pro Audio may work in some cases, but there are always issues when using it.

Handrail9 commented 2 months ago

1- first install package named pactl

There is no such package on Fedora. There is a package named "pulseaudio-utils" that provides it, but your instructions are incorrect for Fedora specifically, and as WeirdTreeThing has stated this has a low probability of working for every device. (It does not work for the device I am currently testing and about to file an issue for)

Abubakr4Dev commented 1 month ago

There is no such package on Fedora. There is a package named "pulseaudio-utils"

You're right, I made an edit

But I want to understand what is wrong with Fedora, because it works for me without problems, and the microphone also works now.

Aeyk commented 1 month ago

But I want to understand what is wrong with Fedora, because it works for me without problems, and the microphone also works now.

We may have different devices.

ellyq commented 3 weeks ago

Well, rawhide isn't supposed to be used as a daily-driver. SOF often gets hit with regressions in pre-release kernels (and often even in release ones...)

[   62.384029] sof-audio-pci-intel-apl 0000:00:0e.0: Code loader DMA did not complete
[   62.384085] sof-audio-pci-intel-apl 0000:00:0e.0: ------------[ DSP dump start ]------------
[   62.384088] sof-audio-pci-intel-apl 0000:00:0e.0: Firmware download failed
[   62.384090] sof-audio-pci-intel-apl 0000:00:0e.0: fw_state: SOF_FW_BOOT_READY_OK (6)
[   62.384138] sof-audio-pci-intel-apl 0000:00:0e.0: 0x00000005: module: ROM, state: FW_ENTERED, running
[   62.384166] sof-audio-pci-intel-apl 0000:00:0e.0: extended rom status:  0x5 0x0 0x4000 0x0 0x0 0x0 0x0 0x0
[   62.384168] sof-audio-pci-intel-apl 0000:00:0e.0: ------------[ DSP dump end ]------------
[   62.384184] sof-audio-pci-intel-apl 0000:00:0e.0: Failed to start DSP
[   62.384186] sof-audio-pci-intel-apl 0000:00:0e.0: error: failed to boot DSP firmware after resume -110
[   62.384193] sof-audio-pci-intel-apl 0000:00:0e.0: ASoC: error at snd_soc_pcm_component_pm_runtime_get on 0000:00:0e.0: -110
[   62.384200]  SSP2-Codec: ASoC: error at __soc_pcm_open on SSP2-Codec: -110
[   62.384205]  Headset: ASoC: error at dpcm_be_dai_startup on Headset: -110
[   62.384251]  Headset: ASoC: error at dpcm_fe_dai_startup on Headset: -110