hi,
the problem seems to have disappeared after installation of pulseaudio-alsa
which appears to be essential to the proper functioning of Chromium.
when Chromium had "the hand" on the audio and was able to produce sound, I
could not hear the other participants talking with Jitsi while I could he
with or without the option, Chromium is still willing to play sound once in
a while.
what really bothers me is the randomness of the problem.
some additional information :
$ journalctl -b | grep -i _hda_
May 09 08:39:09 archlive kernel: snd_hda_intel: probe of :00:1f.3
failed with error -2
May
Try loading snd_hda_intel without extra options. If this helps, you can
always use the ALSA_CARD environment variable for choosing the audio device.
hi,
neither one nor the other.
here is the return of the `aplay -l -L` command on my lenovo :
null
Discard all samples (playback) or generate zero samples (capture)
default:CARD=sofhdadsp
sof-hda-dsp,
Default Audio Device
sysdefault:CARD=sofhdadsp
sof-hda-dsp,
Default Audio Dev
Do you perhaps have any /etc/asound.conf or .asoundrc or similarly named
files messing up your sound config?
Additionally (another wild guess), try running aplay -l -L and report the
output.
On Thu, May 5, 2022, 16:00 Pascal via arch-general <
arch-general@lists.archlinux.org> wrote:
> I checked
I checked in my session the concurrent accesses with fuser -v /dev/snd/*
and killed the only one that was present and could interfere (volumeicon *that
was also present with Firefox and Mplayer*).
Le jeu. 5 mai 2022 à 15:50, Pascal a écrit :
> Alsa directly : no PA or PW.
>
> when i run Chromium
Alsa directly : no PA or PW.
when i run Chromium from a terminal, i get these two error messages about
Alsa but they also appear when the sound is working :
[4765:4765:0504/164956.649650:ERROR:alsa_util.cc(204)] PcmOpen:
default,Device or resource busy
[4765:4765:0504/164956.649811:ERROR:alsa_util
Are you using Alsa directly, no pulseaudio or pipewire? Something could be
wonky with your dmix config and it's getting disabled, thus only a single
application can have access to the sound playback at once.
I just did a little test like this:
# user add -m test
# passwd test
# echo "chromium https://youtube.com"; > /home/test/.xinitrc
logoff and then logon (slim) as test.
a first test "bingo", it works, there is sound !
I extend the test : I close Chromium, I reconnect again immediatly and KO,
no so
I just had a look in the wiki and did not see anything special.
sof-firmware is installed.
~ # pacman -Q | grep 'sof'
sof-firmware 2.1.1-1
the problem seems to be between chromium and my lenovo.
I will test on other machines soon...
Le jeu. 5 mai 2022 à 12:36, Damjan Georgievski via arch-genera
Pascal via arch-general wrote:
> hi,
>
> I have an ArchLinux installed on a usb disk (eg. "mobile").
>
> ~ # uname -r
> 5.15.37-1-lts
> ~ # pacman -Q | egrep 'alsa|chromium|firefox|mplayer'
> alsa-lib 1.2.6.1-1
> alsa-topology-conf 1.2.5.1-1
> alsa-ucm-conf 1.2.6.3-1
> alsa-utils 1.2.6-1
> chro
> on the other hand, when it runs on my Lenovo ThinkPad X1 Carbon, Chromium
> has problems with the sound
Check the Arch wiki for the requirements of the exact model and
generation of X1.
a wild guess would be, you need to install `sof-firmware` but it's
hard to say without more data
--
damja
hi,
I have an ArchLinux installed on a usb disk (eg. "mobile").
~ # uname -r
5.15.37-1-lts
~ # pacman -Q | egrep 'alsa|chromium|firefox|mplayer'
alsa-lib 1.2.6.1-1
alsa-topology-conf 1.2.5.1-1
alsa-ucm-conf 1.2.6.3-1
alsa-utils 1.2.6-1
chromium 101.0.4951.54-1
firefox 100.0-1
mplayer 38359-1
whe
13 matches
Mail list logo
