You are not logged in.
I wonder whether canberra actually uses pulses sample cache and if that isn't warm yet the first sound fails to play and/or it's a bug in canberra that it just uploads to the sample cache and does not trigger actual playback of the sample if it isn't yet present... which would however bite itself with the normal analog card working (... unless, you did completely reboot again before testing with the analog card so that it's a valid "first try" again, right?)
Does e.g.
PULSE_LATENCY_MSEC=30 canberra-gtk-play -i message #for the fun of it to check whether it's some internal canberra detail with the pulse backend CANBERRA_DRIVER=alsa canberra-gtk-play -i messagemake a difference. If my current theory is correct the first one should still fail for the first attempt and work fine for further ones and the second one should actually work (... granted you have a proper pulseaudio-alsa setup)
FWIW if my though process is correct you should be able to "force" the faulty behavior by restarting pulse ( systemctl --user restart pulseaudio ) an/ or playing with the sample cache e.g.
pacmd list-samples pacmd play-sample pacmd remove-sample-namebefore and after a canberra playback attempt
Unfortunately there is no difference ![]()
Ran the first command, sound only played on second attempt. Restarted pulseaudio, ran the second command, same problem.
Offline
Since his default environment is KDE, it's probably not canberra specific.
If this wasn't a problem also while the output is busy (during media playback over HDMI) I'd opt for snd-hda-codec-*hdmi.enable_silent_stream=true …
Where would I configure that setting?
Offline
https://wiki.archlinux.org/title/Kernel_parameters
Add "snd-hda-codec-hdmi.enable_silent_stream=true"
Offline
https://wiki.archlinux.org/title/Kernel_parameters
Add "snd-hda-codec-hdmi.enable_silent_stream=true"
Ok, so the article reads "The Arch Linux installation medium uses Syslinux for BIOS systems, and GRUB for UEFI systems" . I did install Arch following the installation guide. This is a UEFI system, but I can't find the /boot/grub/grub.cfg file. I don't even have the /boot/grub folder. Should I create them myself?
Offline
No, but you most likely have to mount the boot partition.
Otherwise: what /is/ in /boot?
Offline
No, but you most likely have to mount the boot partition.
Otherwise: what /is/ in /boot?
The boot images:
/boot: ls
initramfs-linux-fallback.img initramfs-linux.img vmlinuz-linux
/boot: sudo findmnt
. . .
└─/boot /dev/nvme0n1p1
vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-roSo it's already mounted.
Offline
What if you unmount it?
Also
lsblk -fEdit: btw. it's a much better idea to inject this at the bootloader for a test, not to reconfigure the bootloader.
Press "e" to edit the selected boot in grub.
Last edited by seth (2022-07-13 20:04:46)
Offline
What if you unmount it?
Can you please explain what's that going to achieve?
.
.
.
Also
lsblk -f
~: lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
nvme1n1
├─nvme1n1p1 vfat FAT32 4899-ED6A
├─nvme1n1p2 linux_raid_member 1.2 archiso:2 cde6eed0-0153-1240-74d7-f739c305a67b
│ └─md2 swap 1 21016c57-f912-4244-8cef-47091ee238b0
├─nvme1n1p3 linux_raid_member 1.2 archiso:3 d39fa2ee-195a-fe21-ab4f-843213d14741
│ └─md3 f2fs 1.14 37a431f4-d183-48d2-a56d-7768b990930b 66.3G 34% /
└─nvme1n1p4 linux_raid_member 1.2 archiso:4 df84c06b-0237-6a95-6e74-7c9cf79e239a
└─md4 f2fs 1.14 2140974e-3095-43bf-8f11-734ce281e81f 197G 41% /zork
nvme0n1
├─nvme0n1p1 vfat FAT32 484A-1131 445.7M 11% /boot
├─nvme0n1p2 linux_raid_member 1.2 archiso:2 cde6eed0-0153-1240-74d7-f739c305a67b
│ └─md2 swap 1 21016c57-f912-4244-8cef-47091ee238b0
├─nvme0n1p3 linux_raid_member 1.2 archiso:3 d39fa2ee-195a-fe21-ab4f-843213d14741
│ └─md3 f2fs 1.14 37a431f4-d183-48d2-a56d-7768b990930b 66.3G 34% /
└─nvme0n1p4 linux_raid_member 1.2 archiso:4 df84c06b-0237-6a95-6e74-7c9cf79e239a
└─md4 f2fs 1.14 2140974e-3095-43bf-8f11-734ce281e81f 197G 41% /zork.
.
.
Edit: btw. it's a much better idea to inject this at the bootloader for a test, not to reconfigure the bootloader.
Press "e" to edit the selected boot in grub.
Press e where? I don't have any grub menu choices at boot, everything boots really fast, in like 3-4 seconds.
Offline
Can you please explain what's that going to achieve?
See whether you're maybe booting from the boot partition, but the root partition.
Did you maybe install grub on nvme1n1p1 ?
I don't have any grub menu choices at boot, everything boots really fast, in like 3-4 seconds.
Are you sure that you're using grub? Did you install grub following https://wiki.archlinux.org/title/GRUB#Installation and ran grub-install?
Offline
Can you please explain what's that going to achieve?
See whether you're maybe booting from the boot partition, but the root partition.
Did you maybe install grub on nvme1n1p1 ?I don't have any grub menu choices at boot, everything boots really fast, in like 3-4 seconds.
Are you sure that you're using grub? Did you install grub following https://wiki.archlinux.org/title/GRUB#Installation and ran grub-install?
I never installed grub explicitly. I used the installation media provided via the installation guide.
https://wiki.archlinux.org/title/installation_guide
Last edited by mdcclxv (2022-07-13 21:53:31)
Offline
Choose and install a Linux-capable boot loader. If you have an Intel or AMD CPU, enable microcode updates in addition.
You've no boot loader at all, but the UEFI boot manager picks it up via https://wiki.archlinux.org/title/EFISTUB
https://wiki.archlinux.org/title/Kernel … odprobe.d/ - nb. that the syntax is slightly different.
You may have to rebuild the initramfs in case the module is in there (you can "lsinitcpio /boot/initramfs-linux.img" to check the contents)
Offline
https://wiki.archlinux.org/title/installation_guide#Boot_loader wrote:Choose and install a Linux-capable boot loader. If you have an Intel or AMD CPU, enable microcode updates in addition.
You've no boot loader at all, but the UEFI boot manager picks it up via https://wiki.archlinux.org/title/EFISTUB
https://wiki.archlinux.org/title/Kernel … odprobe.d/ - nb. that the syntax is slightly different.
You may have to rebuild the initramfs in case the module is in there (you can "lsinitcpio /boot/initramfs-linux.img" to check the contents)
I'll go for the modprobe, snd-hda-codec-hdmi module is not present in my initramfs image.
Besides, I don't think I want another component in the boot process, that is, grub. The EFISTUB article reads "using a boot loader is recommended if you have multiple kernel/initramfs pairs". Definitely not my case. I'm still struggling a lot with the only pair I got ![]()
Offline
You probably want a bootloader because of https://wiki.archlinux.org/title/Microc … ly_loading
Alternatively see https://wiki.archlinux.org/title/Microc … _initramfs
Offline
Bad news ![]()
I've created the /etc/modprobe.d/snd-hda-codec-hdmi.conf with the following content:
snd-hda-codec-hdmi.enable_silent_stream=trueAfter reboot, all media, not only the system sounds, get cut at the beginning when playing via HDMI. And is not a delay, the very first one or two seconds of media get cut out.
Removed the file, rebooted, media plays ok, system sounds can be heard only on second attempt, that is, the first attempt is not getting played.
Looks more and more like an initial buffering problem. have no idea why buffering is really needed when it has such disastrous side effects.
Can I disable buffering completely?
Offline
So, I ended up rewiring, that is, switched the speakers (and the fall back device) to the built in sound card and media now goes through HDMI.
IMHO the HDMI part of ALSA still needs some serious work, at least for AMD based hardware.
@seth, @V1del: thanks a lot for your time and effort.
Offline