[Desktop-packages] [Bug 2073552] Re: Add SoundWire devices to alsa-info reported in ACPI
Thanks @Dan. Will try to make an exception request for Oracular.
Proposed a MR for Oracular just in case.
https://code.launchpad.net/~mschiu77/ubuntu/+source/alsa-utils/+git/alsa-utils/+merge/472762
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/2073552
Title:
Add SoundWire devices to alsa-info reported in ACPI
Status in alsa-utils package in Ubuntu:
New
Status in alsa-utils source package in Jammy:
In Progress
Status in alsa-utils source package in Noble:
In Progress
Bug description:
[SRU Justifications]
[Impact]
Modern Intel platforms (RPL, MTL, LNL...etc) connect audio codecs on
Soundwire instead of HDA, but the soundwire devices are not well reflected on
the alsa-info report. In order to meet the increasing demands for SoundWire
debugging, we must enable alsa-info to provide more information about SoundWire.
[Fix]
Backport the upstream commit cc0bcef81389 ("alsa-info.sh: log SoundWire
devices reported in ACPI") of v1.2.12. The Oracular is expected to sync with
v1.2.12 and we may not have to backport to Oracular. The reported information
can reflect which soundwire devices are connected and which soundware link the
device connects to. It's quite sufficient for what driver should be ready and
what tplg/firmware file should be loaded.
[Test Case]
1. Find a machine with (RTK/Cirrus/TI) Soundwire audio device.
2. Install the new alsa-utils debian package
3. Execute `alsa-info` to generate the report
4. Check if the section "ACPI SoundWire Device Status Information" exists in
the output report.
[Where problems could occur]
It's simply an additional soundwire information when ACPI exposed the
soundwire device. The risk for regression is low.
[Other Info]
Verify if the official Oracular starts from version v1.2.12 to determine if
we have to land it on Oracular.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/2073552/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2073552] Re: Add SoundWire devices to alsa-info reported in ACPI
@Dan, I though the alsa-utils of Oracular should be rebased on v1.2.12
and I don't know how it will happen.
Can you suggest what I should do? I think the correct way is to trigger
the sync? Or I should do it manually?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/2073552
Title:
Add SoundWire devices to alsa-info reported in ACPI
Status in alsa-utils package in Ubuntu:
New
Status in alsa-utils source package in Jammy:
In Progress
Status in alsa-utils source package in Noble:
In Progress
Bug description:
[SRU Justifications]
[Impact]
Modern Intel platforms (RPL, MTL, LNL...etc) connect audio codecs on
Soundwire instead of HDA, but the soundwire devices are not well reflected on
the alsa-info report. In order to meet the increasing demands for SoundWire
debugging, we must enable alsa-info to provide more information about SoundWire.
[Fix]
Backport the upstream commit cc0bcef81389 ("alsa-info.sh: log SoundWire
devices reported in ACPI") of v1.2.12. The Oracular is expected to sync with
v1.2.12 and we may not have to backport to Oracular. The reported information
can reflect which soundwire devices are connected and which soundware link the
device connects to. It's quite sufficient for what driver should be ready and
what tplg/firmware file should be loaded.
[Test Case]
1. Find a machine with (RTK/Cirrus/TI) Soundwire audio device.
2. Install the new alsa-utils debian package
3. Execute `alsa-info` to generate the report
4. Check if the section "ACPI SoundWire Device Status Information" exists in
the output report.
[Where problems could occur]
It's simply an additional soundwire information when ACPI exposed the
soundwire device. The risk for regression is low.
[Other Info]
Verify if the official Oracular starts from version v1.2.12 to determine if
we have to land it on Oracular.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/2073552/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2073552] Re: Add SoundWire devices to alsa-info reported in ACPI
** Description changed:
[SRU Justifications]
[Impact]
Modern Intel platforms (RPL, MTL, LNL...etc) connect audio codecs on
Soundwire instead of HDA, but the soundwire devices are not well reflected on
the alsa-info report. In order to meet the increasing demands for SoundWire
debugging, we must enable alsa-info to provide more information about SoundWire.
[Fix]
- Backport the upstream commit cc0bcef81389 ("alsa-info.sh: log SoundWire
devices reported in ACPI"). The reported information can reflect which
soundwire devices are connected and which soundware link the device connects
to. It's quite sufficient for what driver should be ready and what
tplg/firmware file should be loaded.
+ Backport the upstream commit cc0bcef81389 ("alsa-info.sh: log SoundWire
devices reported in ACPI") of v1.2.12. The Oracular is expected to sync with
v1.2.12 and we may not have to backport to Oracular. The reported information
can reflect which soundwire devices are connected and which soundware link the
device connects to. It's quite sufficient for what driver should be ready and
what tplg/firmware file should be loaded.
[Test Case]
- 1. Find a machine with (RTK/Cirrus/TI) Soundwire audio device.
+ 1. Find a machine with (RTK/Cirrus/TI) Soundwire audio device.
2. Install the new alsa-utils debian package
3. Execute `alsa-info` to generate the report
- 4. Check if the section "ACPI SoundWire Device Status Information" exists in
the output report.
+ 4. Check if the section "ACPI SoundWire Device Status Information" exists in
the output report.
[Where problems could occur]
It's simply an additional soundwire information when ACPI exposed the
soundwire device. The risk for regression is low.
+
+ [Other Info]
+ Verify if the official Oracular starts from version v1.2.12 to determine if
we have to land it on Oracular.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/2073552
Title:
Add SoundWire devices to alsa-info reported in ACPI
Status in alsa-utils package in Ubuntu:
New
Status in alsa-utils source package in Jammy:
In Progress
Status in alsa-utils source package in Noble:
In Progress
Bug description:
[SRU Justifications]
[Impact]
Modern Intel platforms (RPL, MTL, LNL...etc) connect audio codecs on
Soundwire instead of HDA, but the soundwire devices are not well reflected on
the alsa-info report. In order to meet the increasing demands for SoundWire
debugging, we must enable alsa-info to provide more information about SoundWire.
[Fix]
Backport the upstream commit cc0bcef81389 ("alsa-info.sh: log SoundWire
devices reported in ACPI") of v1.2.12. The Oracular is expected to sync with
v1.2.12 and we may not have to backport to Oracular. The reported information
can reflect which soundwire devices are connected and which soundware link the
device connects to. It's quite sufficient for what driver should be ready and
what tplg/firmware file should be loaded.
[Test Case]
1. Find a machine with (RTK/Cirrus/TI) Soundwire audio device.
2. Install the new alsa-utils debian package
3. Execute `alsa-info` to generate the report
4. Check if the section "ACPI SoundWire Device Status Information" exists in
the output report.
[Where problems could occur]
It's simply an additional soundwire information when ACPI exposed the
soundwire device. The risk for regression is low.
[Other Info]
Verify if the official Oracular starts from version v1.2.12 to determine if
we have to land it on Oracular.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/2073552/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898483] Re: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected
@trurl42, seems you have different machine which I will need alsa-info and dmesg for your config. Could you file another bug and attached the detail information as comment #1. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1898483 Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected Status in alsa-driver package in Ubuntu: Incomplete Bug description: The volume bars in sound settings react to what sound is played correctly but I can't hear any sounds ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paramvir 1924 F pulseaudio /dev/snd/pcmC0D0p: paramvir 1924 F...m pulseaudio /dev/snd/pcmC0D6c: paramvir 1924 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 5 02:22:25 2020 InstallationDate: Installed on 2020-04-26 (161 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paramvir 1924 F pulseaudio /dev/snd/pcmC0D0p: paramvir 1924 F...m pulseaudio /dev/snd/pcmC0D6c: paramvir 1924 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0K1VDX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd07/22/2019:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0K1VDX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 dmi.product.sku: 0923 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-04T03:10:08.906233 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898483] Re: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected
@ Paramvir Could you try new kernel and update the information? Thanks ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1898483 Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected Status in alsa-driver package in Ubuntu: Incomplete Bug description: The volume bars in sound settings react to what sound is played correctly but I can't hear any sounds ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paramvir 1924 F pulseaudio /dev/snd/pcmC0D0p: paramvir 1924 F...m pulseaudio /dev/snd/pcmC0D6c: paramvir 1924 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 5 02:22:25 2020 InstallationDate: Installed on 2020-04-26 (161 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paramvir 1924 F pulseaudio /dev/snd/pcmC0D0p: paramvir 1924 F...m pulseaudio /dev/snd/pcmC0D6c: paramvir 1924 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0K1VDX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd07/22/2019:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0K1VDX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 dmi.product.sku: 0923 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-04T03:10:08.906233 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898483] Re: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected
@trurl42, does the sound used to work before (older kernel than 6.5)? >From the kernel log, the line out has no trivial problem. I need to know is >this a regression or something else. Thanks [5.221075] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC3254: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [5.221080] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1898483 Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: The volume bars in sound settings react to what sound is played correctly but I can't hear any sounds ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paramvir 1924 F pulseaudio /dev/snd/pcmC0D0p: paramvir 1924 F...m pulseaudio /dev/snd/pcmC0D6c: paramvir 1924 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 5 02:22:25 2020 InstallationDate: Installed on 2020-04-26 (161 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paramvir 1924 F pulseaudio /dev/snd/pcmC0D0p: paramvir 1924 F...m pulseaudio /dev/snd/pcmC0D6c: paramvir 1924 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0K1VDX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd07/22/2019:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0K1VDX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 dmi.product.sku: 0923 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-04T03:10:08.906233 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
