@Artur,
a) you had a previous debdiff for mantic which used version
1.2.9-1ubuntu3.1, which is what we expect for an SRU to mantic, but now
in the mantic unapproved queue I see that you changed the version to
1.2.9-1ubuntu4 again.
The upgrade path between ubuntu releases still works:
alsa-ucm-conf | 1.2.9-1ubuntu3 | mantic | source
alsa-ucm-conf | 1.2.9-1ubuntu4 | mantic/unapproved/9e381c3 | source
alsa-ucm-conf | 1.2.10-1ubuntu1 | noble | source
But since you were asked to change this once in comment #8, and did so in
comment #10, I would ask that we stick to the correct version like you did
before already :)
I could fix that for you, but I have other questions:
b) In the test plan:
> 1. $ alsactl init
> alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf
> /var/lib/alsa/card0.conf.d' failed (exit code
> 1)
> (note: assuming that failed to remove the empty directory is not a
critical problem)
First of all, thanks a lot for noticing this!
I checked the alsa-lib main.c:779 code in jammy, and it does cause that
function to exit with an error. What implications that has to the rest
of the initialization I'm not sure:
if (ignore_error == false && err != 0) {
uc_error("exec '%s' failed (exit code %d)", s->data.exec, err);
goto __fail;
}
...
__fail:
free(cdev);
return err;
Did you get this error in all ubuntu releases with the patched package? What
about on systems which do NOT have this particular audio card, but another one?
I.e., would we regress those?
Whether it's a big problem or not, depends on who is calling alsactl
init, and what they do when this command fails.
I briefly searched in alsa-lib where it would be asking for that rm -rf,
but couldn't find it. I also checked git history, and didn't see
relevant mentions of that.
Do you have a better idea of what's going on with that rm -rf, why it's
being attempted on an empty directory, and if that's the case, why not
ignore the error?
** Changed in: alsa-ucm-conf (Ubuntu Jammy)
Status: In Progress => Incomplete
** Changed in: alsa-ucm-conf (Ubuntu Lunar)
Status: In Progress => Incomplete
** Changed in: alsa-ucm-conf (Ubuntu Mantic)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/2042902
Title:
ucm2: soundwire: add rt713 SDCA device
Status in OEM Priority Project:
In Progress
Status in alsa-ucm-conf package in Ubuntu:
Fix Released
Status in alsa-ucm-conf source package in Jammy:
Incomplete
Status in alsa-ucm-conf source package in Lunar:
Incomplete
Status in alsa-ucm-conf source package in Mantic:
Incomplete
Status in alsa-ucm-conf source package in Noble:
Fix Released
Bug description:
[ Impact ]
Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack
Codec-ALC713.
Without correct configurations in userspace above codecs cannot be used. Thus
in Settings > Sound > Output test doesn't produce sounds and Input device is
greyed out.
[ Fix ]
Adding rt713 config files in ucm2 will allow to utilize those codecs.
Upstream commit added support:
https://github.com/alsa-project/alsa-ucm-conf/pull/363
[ Test Plan ]
Device with the soundwire card
$ cat /proc/asound/cards
0 [sofsoundwire ]: sof-soundwire - sof-soundwire
Intel Soundwire SOF
Before fix:
1. $ alsactl init
alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration
file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf
alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file
/usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2
alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use
case configuration -2
Found hardware: "sof-soundwire" "Intel Meteorlake HDMI"
"HDA:8086281d,80860101,00100000 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316
mic:rt713-dmic" "" ""
Hardware is initialized using a generic method
2. $ amixer contents
...
numid=24,iface=MIXER,name='Headphone Switch'
; type=BOOLEAN,access=rw------,values=1
: values=off
...
numid=33,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw------,values=1
: values=off
After fix: after adding patch files
1. $ alsactl init
alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf
/var/lib/alsa/card0.conf.d' failed (exit code 1)
(note: assuming that failed to remove the empty directory is not a
critical problem)
2. $ amixer contents
...
numid=24,iface=MIXER,name='Headphone Switch'
; type=BOOLEAN,access=rw------,values=1
: values=on
...
numid=33,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw------,values=1
: values=on
[Where problems could occur]
* This change adds new hardware support.
* The change only adds new hardware support,
it will not affect other codec device.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2042902/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
