** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)
--
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/1888992
Title:
[Realtek ALC892, Green Headphone Out, Front] Not
The patch of #17 is reverted from upstream, and the patch is cced to
stable, it will be in the ubuntu kernel sooner or later.
thx.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
I reverted that commit in the kernel of #16. So let me think about how
to fix it.
thx.
--
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/1888992
Title:
[Realtek ALC892, Green
Thank you for following up.
I have managed to complete a commit bisect of the Ubuntu kernels and can
confirm that the first bad commit is
851cc40f47677174527a1decbd1074feacd15a93:
ALSA: hda: call runtime_allow() for all hda controllers
BugLink: https://bugs.launchpad.net/bugs/1876765
Please test this kernel:
https://people.canonical.com/~hwang4/testdetect/
--
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/1888992
Title:
[Realtek ALC892, Green Headphone Out,
If you don't use "options snd_hda_intel power_save=0", instead you use
"options snd_hda_intel power_save_controller=0", is it a valid
workaround too?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
Last known working kernel: 5.4.0-33, next installable Ubuntu kernel
5.4.0-37 introduces the bug.
I have tested that saving "options snd_hda_intel power_save=0" to a file
under /etc/modprobe.d and rebooting to a kernel from -37 onwards is a
valid workaround.
Lines mentioning ALSA from
Ignore my last comment about last known working kernel, I've rebooted to
5.4.0.40 and I still see this issue, will try and do more testing on
kernel versions to see if I can find where it changes, and will also
look into the power_save options.
--
You received this bug notification because you
The output of cat /proc/asound/card1/codec#0 after running alsa-info
differs slightly to that included within the alsa-info log itself (in
#8):
26c335
< Converter: stream=0, channel=0
---
> Converter: stream=5, channel=0
38c347
< Converter: stream=0, channel=0
---
> Converter: stream=5,
So this is a kernel driver issue instead of pulseaudio issue. It has sth
to do with power management, and it is difficult to debug this kind of
issue without a physical machine.
you could use a workaround like snd_hda_intel.power_save=0 or
snd_hda_intel.power_save=,0 I don't whchi one is correct
To add to #9, as well as the headphones being detected after running
alsa-info, I can confirm that they still work as expected after
detection.
As this may be a bug introduced by a kernel change, the current kernel
running is 5.4.0.42.45 (generic, x86_64), whereas the previous one I was
running
Then after the fresh boot, I connected the headphones, verified no
sound, then re-ran alsa-info which gave the following attached log.
** Attachment added: "alsa-info log with headphones plugged in"
After running alsa-info, it appears that the headphones were detected
and started to show in Settings GUI, also showing in the attached pacmd
list report.
** Attachment added: "pacmd list after alsa-info with headphones connected"
For reference, after a fresh boot without headphones plugged in on my
machine, the alsa-info command gives the attached output.
** Attachment added: "alsa-info log fresh boot with no headphones connected"
After you plug in the headphone, the headphone jack should change to
available yes, but according to the log in the #3, it is still available
no:
analog-output-headphones: Headphones (priority 9900, latency
offset 0 usec, available: no)
properties:
And a log from after I use pavucontrol to manually enable the 17h audio
controller while the headphones are plugged in, and confirming that they
do work as they used to.
** Attachment added: "pacmd list after manual switch"
For comparison, a log from before I plug in the headphones (after a
fresh boot)
** Attachment added: "pacmd list after a fresh boot"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1888992/+attachment/5396218/+files/pacmd_list_fresh_boot.log
--
You received this bug notification
As requested - after a fresh boot, and plugging in headphones and
verifying that there is no sound from them.
** Attachment added: "pacmd list after plugging in headphones"
After you plug in the headphone, the Active Profile should change to be
Could you please redo the test and upload a log?
reboot with headphone unplugged,
after booting up, plug headphone, make sure the headphone couldn't output sound,
run 'pacmd list > pa.log', then upload the pa.log.
thx.
--
19 matches
Mail list logo
