- Alsa-devel - mailman.alsa-project.org

[BUG] HDA Intel PCH, HDMI , HDA Intel PCH, ALC886 Digital, no IEC958 / HDMI output/passthrough to AVR, partly fixed but HDMI AC3 passthrough
by schorpp 27 Nov '24

27 Nov '24

>>> >>> [BUG] HDA Intel PCH, HDMI , HDA Intel PCH, ALC886 Digital, no IEC958 / HDMI output/passthrough to AVR >>> >>> ALSA versions 1.0.28 >>> >>> Kernel Driver versions 3.12.40 > Partly FIXED in Longterm Stable Kernel 4.19.324 and using HDMI DEV 1 instead of 0. > > 2 CH PCM HDMI to AVR works now but AC3/DTS passthrough still not or is not recognized by AVR or some wrong AES setting but iec958 ALC886 optical toslink AC3/DTS output to AVR works. > > New BUG: No more 5.1 Analog Output on the CM106 USB Box if AC3 stream is selected. No. Sorry, VDR xineliboutput config error, needs speaker setup 5.1 instead of pass through. y tom > > Your ALSA information is located at http://alsa-project.org/db/?f=5ef8b56450583ba8afbcc705afc02228da4a3072 > > y > tom > >>> >>> Hardware: >>> >>> DFI Mainboard MB330-CRM >>> >>> https://www.dfi.com/de/product/index/273#specification >>> >>> Reproducible Always >>> >>> Steps to reproduce and full report: >>> >>> https://www-vdr--portal-de.translate.goog/forum/index.php?thread/136519-gel… >> Output of alsa-info.sh is here >> >> http://alsa-project.org/db/?f=fc4734deddd9a92331692bf94b15cf84b7722cd4 >> >>> >>> Software crosscheck with CM106 USB Soundbox iec958: works OK. >>> >>> Where to start in the drivers source code to fix it? >>> >>> y >>> tom >>> >>>

1 0

alsa-ucm-conf update from 1.2.12 to 1.2.13 causes HDMI/DsiplayPort outputs to disappear
by GitHub issues - opened 27 Nov '24

27 Nov '24

alsa-project/alsa-ucm-conf issue #477 was opened from mwsltn: Basic Info: Linux Distro: Arch Kernel Version: 6.12.1 I have very reliably been using a USB-C connected external monitor that has internal speakers represented by the output device: HDMI / DisplayPort 1 After running a package update this AM all the HDMI/DisplayPort outputs disappeared. First I downgraded the kernel which didn't help, then checked the pacman logs to see what else had changed and the list included the following: ``` [2024-11-26T05:07:01-0600] [ALPM] upgraded alsa-ucm-conf (1.2.12-1 -> 1.2.13-1) [2024-11-26T05:07:01-0600] [ALPM] upgraded alsa-lib (1.2.12-1 -> 1.2.13-1) [2024-11-26T05:07:01-0600] [ALPM] upgraded alsa-utils (1.2.12-1 -> 1.2.13-1) ``` So I downgrade: ``` [2024-11-26T06:51:22-0600] [PACMAN] Running 'pacman -U file:///var/cache/pacman/pkg/alsa-ucm-conf-1.2.12-1-any.pkg.tar.zst file:///var/cache/pacman/pkg/alsa-lib-1.2.12-1-x86_64.pkg.tar.zst file:///var/cache/pacman/pkg/alsa-utils-1.2.12-1-x86_64.pkg.tar.zst' [2024-11-26T06:51:24-0600] [ALPM] downgraded alsa-ucm-conf (1.2.13-1 -> 1.2.12-1) [2024-11-26T06:51:24-0600] [ALPM] downgraded alsa-lib (1.2.13-1 -> 1.2.12-1) [2024-11-26T06:51:24-0600] [ALPM] downgraded alsa-utils (1.2.13-1 -> 1.2.12-1) ``` Problem fixed. Please let me know if I can provide any other info. Originally I had opened an issue on the `alsa-lib` project and others are reporting the same: https://github.com/alsa-project/alsa-lib/issues/423 Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/477 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

alsactl.1: Some remarks and editorial changes for this man page
by Bjarni Ingi Gislason 27 Nov '24

27 Nov '24

Package: alsa-utils Version: 1.2.12-1 Severity: minor Tags: patch * What led up to the situation? Checking for defects with test-[g|n]roff -mandoc -t -K utf8 -rF0 -rHY=0 -ww -b -z < "man page" [Use "groff -e ' $' <file>" to find trailing spaces.] ["test-groff" is a script in the repository for "groff"; is not shipped] (local copy and "troff" slightly changed by me). [The fate of "test-nroff" was decided in groff bug #55941.] * What was the outcome of this action? troff: backtrace: file '<stdin>':93 troff:<stdin>:93: warning: trailing space in the line troff: backtrace: file '<stdin>':224 troff:<stdin>:224: warning: trailing space in the line * What outcome did you expect instead? No output (no warnings). -.- General remarks and further material, if a diff-file exist, are in the attachments. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.11.9-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) Versions of packages alsa-utils depends on: ii kmod 33+20240816-2 ii libasound2t64 1.2.12-1+b1 ii libatopology2t64 1.2.12-1+b1 ii libc6 2.40-3 ii libfftw3-single3 3.3.10-1+b3 ii libncursesw6 6.5-2+b1 ii libsamplerate0 0.2.2-4+b2 ii libtinfo6 6.5-2+b1 alsa-utils recommends no packages. Versions of packages alsa-utils suggests: pn dialog <none> -- no debconf information

1 0

alsabat.1: Some remarks and editorial changes for this man page
by Bjarni Ingi Gislason 27 Nov '24

27 Nov '24

Package: alsa-utils Version: 1.2.12-1 (Debian testing) Severity: minor Tags: patch * What led up to the situation? Checking for defects with test-[g|n]roff -mandoc -t -K utf8 -rF0 -rHY=0 -ww -b -z < "man page" [Use "groff -e ' $' <file>" to find trailing spaces.] ["test-groff" is a script in the repository for "groff"; is not shipped] (local copy and "troff" slightly changed by me). [The fate of "test-nroff" was decided in groff bug #55941.] * What was the outcome of this action? troff: backtrace: file '<stdin>':175 troff:<stdin>:175: warning: trailing space in the line * What outcome did you expect instead? No output (no warnings). -.- General remarks and further material, if a diff-file exist, are in the attachments. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.11.9-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) Versions of packages alsa-utils depends on: ii kmod 33+20240816-2 ii libasound2t64 1.2.12-1+b1 ii libatopology2t64 1.2.12-1+b1 ii libc6 2.40-3 ii libfftw3-single3 3.3.10-1+b3 ii libncursesw6 6.5-2+b1 ii libsamplerate0 0.2.2-4+b2 ii libtinfo6 6.5-2+b1 alsa-utils recommends no packages. Versions of packages alsa-utils suggests: pn dialog <none> -- no debconf information

1 0

RE: Set pcbeep to default value
by Kailang 26 Nov '24

26 Nov '24

Sorry! Attach again. Add ALSA: hda/realtek: to Title. > -----Original Message----- > From: Kailang > Sent: Tuesday, November 26, 2024 10:36 AM > To: 'Takashi Iwai' <tiwai(a)suse.de> > Cc: (alsa-devel(a)alsa-project.org) <alsa-devel(a)alsa-project.org>; > 'linux-sound(a)vger.kernel.org' <linux-sound(a)vger.kernel.org> > Subject: RE: Set pcbeep to default value > > OK. > > > -----Original Message----- > > From: Takashi Iwai <tiwai(a)suse.de> > > Sent: Monday, November 25, 2024 10:45 PM > > To: Kailang <kailang(a)realtek.com> > > Cc: Takashi Iwai <tiwai(a)suse.de> > > Subject: Re: Set pcbeep to default value > > > > > > External mail. > > > > > > > > On Mon, 25 Nov 2024 03:00:26 +0100, > > Kailang wrote: > > > > > > > > > > > > > -----Original Message----- > > > > From: Takashi Iwai <tiwai(a)suse.de> > > > > Sent: Friday, November 22, 2024 5:34 PM > > > > To: Kailang <kailang(a)realtek.com> > > > > Cc: (alsa-devel(a)alsa-project.org) <alsa-devel(a)alsa-project.org> > > > > Subject: Re: Set pcbeep to default value > > > > > > > > > > > > External mail. > > > > > > > > > > > > > > > > On Fri, 22 Nov 2024 08:29:56 +0100, Kailang wrote: > > > > > > > > > > Hi Takashi, > > > > > > > > > > Attach patch will set pcbeep to default value for ALC274. > > > > > > > > Could you resubmit with your Signed-off-by tag? > > > > > > Sorry! Attach again. > > > > You seem to have dropped Cc to alsa-devel ML. > > Also, nowadays we use linux-sound(a)vger.kernel.org for the main ML for > > kernel patches. Care to resubmit to there? > > > > > > thanks, > > > > Takashi

2 1

alsa-lib update from 1.2.12 to 1.2.13 causes HDMI/DsiplayPort outputs to disappear
by GitHub issues - opened 26 Nov '24

26 Nov '24

alsa-project/alsa-lib issue #423 was opened from mwsltn: Basic Info: Linux Distro: Arch Kernel Version: 6.12.1 I have very reliably been using a USB-C connected external monitor that has internal speakers represented by the output device: `HDMI / DisplayPort 1` After running a package update this AM all the HDMI/DisplayPort outputs disappeared. First I downgraded the kernel which didn't help, then checked the pacman logs to see what else had changed and the list included the following: ``` [2024-11-26T05:07:01-0600] [ALPM] upgraded alsa-ucm-conf (1.2.12-1 -> 1.2.13-1) [2024-11-26T05:07:01-0600] [ALPM] upgraded alsa-lib (1.2.12-1 -> 1.2.13-1) [2024-11-26T05:07:01-0600] [ALPM] upgraded alsa-utils (1.2.12-1 -> 1.2.13-1) ``` So I downgrade: ``` [2024-11-26T06:51:22-0600] [PACMAN] Running 'pacman -U file:///var/cache/pacman/pkg/alsa-ucm-conf-1.2.12-1-any.pkg.tar.zst file:///var/cache/pacman/pkg/alsa-lib-1.2.12-1-x86_64.pkg.tar.zst file:///var/cache/pacman/pkg/alsa-utils-1.2.12-1-x86_64.pkg.tar.zst' [2024-11-26T06:51:24-0600] [ALPM] downgraded alsa-ucm-conf (1.2.13-1 -> 1.2.12-1) [2024-11-26T06:51:24-0600] [ALPM] downgraded alsa-lib (1.2.13-1 -> 1.2.12-1) [2024-11-26T06:51:24-0600] [ALPM] downgraded alsa-utils (1.2.13-1 -> 1.2.12-1) ``` Problem fixed. Please let me know if I can provide any other info. Issue URL : https://github.com/alsa-project/alsa-lib/issues/423 Repository URL: https://github.com/alsa-project/alsa-lib

1 0

kernel snd seq bugs: SND_SEQ_EVENT_CLIENT_CHANGE & SND_SEQ_EVENT_PORT_CHANGE
by Mark Lentczner 26 Nov '24

26 Nov '24

I'm the author of amidiminder - a utility that keeps track of desired connections between ALSA Seq (MIDI) ports. I've found a bug in the kernel part of the ALSA Sequencer, and am not sure where or how to report it. Summary: The events: * SND_SEQ_EVENT_CLIENT_CHANGE is never sent * SND_SEQ_EVENT_PORT_CHANGE is not sent on common port changes (name and port info) I have a lot of detail on these bugs, what other software causes them to be a problem (PureData), and where the missing code in the kernel sound/core/seq files is. Before I dump all the details in this forum.... where is the right place for me to report and/or discuss this? - Mark

2 3

Build failures with GCC 15 (-std=gnu23)
by GitHub issues - edited 26 Nov '24

26 Nov '24

alsa-project/alsa-tools issue #25 was edited from kostadinsh: Some of the programs in alsa-tools fail to build with upcoming GCC 15 which uses `-std=gnu23` by default. This can be reproduced on older GCC and Clang versions by adding `-std=gnu23` to CFLAGS. Downstream Gentoo bug report: https://bugs.gentoo.org/943946 hdajackretask: ``` apply-changes.c:358:10: error: conflicting types for ‘reset_changes_boot’; have ‘gboolean(GError **)’ {aka ‘int(struct _GError **)’} 358 | gboolean reset_changes_boot(GError** err) | ^~~~~~~~~~~~~~~~~~ In file included from apply-changes.c:12: apply-changes.h:12:10: note: previous declaration of ‘reset_changes_boot’ with type ‘gboolean(void)’ {aka ‘int(void)’} 12 | gboolean reset_changes_boot(); | ^~~~~~~~~~~~~~~~~~ main-gtk.c: In function ‘reset_boot_clicked’: main-gtk.c:375:5: error: too many arguments to function ‘reset_changes_boot’ 375 | reset_changes_boot(&err); | ^~~~~~~~~~~~~~~~~~ In file included from main-gtk.c:11: apply-changes.h:12:10: note: declared here 12 | gboolean reset_changes_boot(); | ^~~~~~~~~~~~~~~~~~ ``` envy24control: ``` new_process.c: In function ‘new_process’: new_process.c:67:18: error: assignment to ‘void (*)(void)’ from incompatible pointer type ‘__sighandler_t’ {aka ‘void (*)(int)’} [-Wincompatible-pointer-types] 67 | int_stat = signal(SIGINT, SIG_IGN); | ^ new_process.c:68:19: error: assignment to ‘void (*)(void)’ from incompatible pointer type ‘__sighandler_t’ {aka ‘void (*)(int)’} [-Wincompatible-pointer-types] 68 | quit_stat = signal(SIGQUIT, SIG_IGN); | ^ new_process.c:69:19: error: assignment to ‘void (*)(void)’ from incompatible pointer type ‘__sighandler_t’ {aka ‘void (*)(int)’} [-Wincompatible-pointer-types] 69 | usr2_stat = signal(SIGUSR2, SIG_IGN); | ^ new_process.c:81:24: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 81 | signal(SIGINT, int_stat); | ^~~~~~~~ | | | void (*)(void) In file included from envy24control.h:4: /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ new_process.c:82:25: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 82 | signal(SIGQUIT, quit_stat); | ^~~~~~~~~ | | | void (*)(void) /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ new_process.c:83:25: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 83 | signal(SIGUSR2, usr2_stat); | ^~~~~~~~~ | | | void (*)(void) /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ ``` Issue URL : https://github.com/alsa-project/alsa-tools/issues/25 Repository URL: https://github.com/alsa-project/alsa-tools

1 0

Build failures with GCC 15 (-std=gnu23)
by GitHub issues - opened 26 Nov '24

26 Nov '24

alsa-project/alsa-tools issue #25 was opened from kostadinsh: Some of the programs in alsa-tools fail to build with upcoming GCC 15 which uses `-std=gnu23` by default. This can be reproduced on older GCC and Clang versions by adding `-std=gnu23` to CFLAGS. Downstream Gentoo bug report: https://bugs.gentoo.org/943946 hdajackretask: ``` main-gtk.c: In function ‘reset_boot_clicked’: main-gtk.c:375:5: error: too many arguments to function ‘reset_changes_boot’ 375 | reset_changes_boot(&err); | ^~~~~~~~~~~~~~~~~~ In file included from main-gtk.c:11: apply-changes.h:12:10: note: declared here 12 | gboolean reset_changes_boot(); | ^~~~~~~~~~~~~~~~~~ ``` envy24control: ``` new_process.c: In function ‘new_process’: new_process.c:67:18: error: assignment to ‘void (*)(void)’ from incompatible pointer type ‘__sighandler_t’ {aka ‘void (*)(int)’} [-Wincompatible-pointer-types] 67 | int_stat = signal(SIGINT, SIG_IGN); | ^ new_process.c:68:19: error: assignment to ‘void (*)(void)’ from incompatible pointer type ‘__sighandler_t’ {aka ‘void (*)(int)’} [-Wincompatible-pointer-types] 68 | quit_stat = signal(SIGQUIT, SIG_IGN); | ^ new_process.c:69:19: error: assignment to ‘void (*)(void)’ from incompatible pointer type ‘__sighandler_t’ {aka ‘void (*)(int)’} [-Wincompatible-pointer-types] 69 | usr2_stat = signal(SIGUSR2, SIG_IGN); | ^ new_process.c:81:24: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 81 | signal(SIGINT, int_stat); | ^~~~~~~~ | | | void (*)(void) In file included from envy24control.h:4: /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ new_process.c:82:25: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 82 | signal(SIGQUIT, quit_stat); | ^~~~~~~~~ | | | void (*)(void) /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ new_process.c:83:25: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 83 | signal(SIGUSR2, usr2_stat); | ^~~~~~~~~ | | | void (*)(void) /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ ``` Issue URL : https://github.com/alsa-project/alsa-tools/issues/25 Repository URL: https://github.com/alsa-project/alsa-tools

1 0

No built-in microphone in Thinkpad X1 Carbon (Gen 12) after update to v1.2.13
by GitHub issues - opened 26 Nov '24

26 Nov '24

alsa-project/alsa-ucm-conf issue #476 was opened from iyanmv: I think the title is self-explanatory. After updating from v1.2.12 to v1.2.13 in Arch Linux, the built-in microphone on my laptop is not working. Downgrading to previous versions fixes the issue. In addition, I also noticed that when attached to an external monitor using a docking station, the speakers of the monitor are not listed as before, and only the laptop's built-in speaker appears. I'm running linux 6.12.1 and KDE Plasma 6.2.3. Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/476 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0