Hi Ralph, the Arch Linux install was used with a Gigabyte GA-B85M-D3H motherboard. Now the same install, on the same SSD is used by a Gigabyte B760 DS3H DDR4 (1.0) motherboard. Since 2015 I'm using the same alsa-base.conf: [rocketmouse@archlinux ~]$ /bin/ls -hl /etc/modprobe.d/alsa-base.conf; cat /etc/modprobe.d/alsa-base.conf -rw-r--r-- 1 root root 76 May 2 2015 /etc/modprobe.d/alsa-base.conf # ALSA module ordering options snd slots=snd_hdspm,snd_ice1712,snd_ice1712 My desktop is the window manager openbox, without a desktop environment. I'm either using plain alsa or jackd with the alsa backend. The snd_hdspm isn't plugged into the new mobo yet and no snd_ice1712 will be used with the new mobo at all. IOW at the moment only the crappy on-board audio device is available. After migrating from the old to the new mobo only one audio related file was edited: [rocketmouse@archlinux ~]$ cat .asoundrc; echo "# # # #"; cat .asoundrc_old defaults.pcm.card 3 defaults.pcm.device 3 # # # # defaults.pcm.card 3 defaults.pcm.device 7 [rocketmouse@archlinux ~]$ aplay -l | grep -e Analog -e HDMI\ 0 card 3: PCH [HDA Intel PCH], device 0: ALC897 Analog [ALC897 Analog] card 3: PCH [HDA Intel PCH], device 3: HDMI 0 [EV2450] If I launch [rocketmouse@archlinux ~]$ firefox https://www.youtube.com/watch?v=jC2ZY2loo74 >/dev/null 2>&1 I can listen to the music by my EIZO monitor's speakers using plain alsa. If I launch /usr/bin/jackd -dalsa -dhw:3,3 -r48000 -p256 -n2 or /usr/bin/jackd -dalsa -dhw:3,0 -r48000 -p256 -n2 by qjackctl, before I launch firefox, I can listen by the EIZO's speakers or by the computer's front panel headphones via jackd, with the alsa backend. If I run [rocketmouse@archlinux ~]$ alsamixer -Dhw:3 I cannot see anything related to the PC-Buzzer. There's an option named "Auto-Mut", likely for "Auto-Mute". It was enabled, but I disabled it. There's still no sound when (as root) running [root@archlinux rocketmouse]# printf "\a" [root@archlinux rocketmouse]# [root@archlinux rocketmouse]# beep -l300 -f750 --verbose --debug beep: Verbose: evdev: driver_detect 0x562bdb5890c0 (nil) beep: Verbose: lib: opened /dev/input/by-path/platform-pcspkr-event-spkr as fd=3 beep: Verbose: main: using evdev driver (fd=3, dev=/dev/input/by-path/platform-pcspkr-event-spkr) beep: Verbose: main: 1 times 300 ms beeps (100 ms delay between, 0 ms delay after) @ 750 Hz beep: Verbose: evdev: driver_begin_tone 0x562bdb5890c0 750 beep: Verbose: evdev: driver_end_tone 0x562bdb5890c0 beep: Verbose: evdev: driver_end_tone 0x562bdb5890c0 beep: Verbose: evdev: driver_fini 0x562bdb5890c0 With the old mobo " printf "\a" " always worked, independent from any alsamixer audio settings. The pcspkr module was and is always loaded. I'm using another kernel, than I used with the old mobo, but I seriously doubt that it's the culprit. I didn't get a final answer by Gigabyte support related to the beep issue. Meanwhile I noticed that the PC- Buzzer also fails often during the POST. I replied to a reply of the support with the following (translated from German to English (US) by https://www.deepl.com/de/translator : "Hello,yes I have tested with 3 different buzzers. All 3 buzzers work on power-on self-test (POST) with the old Gigabyte GA-B85M-D3H motherboard. POST has nothing at all to do with my Linux installations, it is a test done by your BIOS before anything else. If I plug the same buzzers one after the other into the new Gigabyte B760 DS3H DDR4 (1.0), a beep usually doesn't work. If I press the remove key after powering on to go into BIOS, then the beep usually works for that moment. Whenever it beeps, it does so only once, as it should. There are also no other problems during operation, the hardware seems to be ok.Kind regardsRalf Mardorf" "Remove key", a funny translation :D. I guess there is an issue with the motherboard's firmware, that is up-to-date. Only two releases are available, https://www.gigabyte.com/de/Motherboard/B760M-DS3H-DDR4-rev-10/support#support-dl-bios . It was delivered with F1 from 2022.10.12. I didn't test the PC-Buzzer with this version. I updated to F3 from 2023.03.10, before I tested the PC-Buzzer. Regards, Ralf
