Volume noisy and loud with no level control [HDA Intel PCH / Realtek ALC295]

Bug #1810039 reported by Jule Marcoueille
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
alsa-driver (Ubuntu)
New
Undecided
Unassigned
pulseaudio (Ubuntu)
New
Undecided
Unassigned

Bug Description

What I expect:
When I use slider volume or when I use volume up button of my laptop, I expect that the volume goes up slightly.

What happens:
From the mute state, one press on volume up do graphically well but in reality the volume is loud and noisy from the first step. And all other up steps do not change the volume.
Doing this with `alsamixer` started show me what you can see in volume-issue.gif attached file.
Indeed when I press volume up PCM volume is maxed to 100 instantly and then Speaker volume and then Master volume.

In my case manually changing the PCM volume in `alsamixer` is the only way to change the actual volume of my laptop. Even changing Master volume has no effect!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jule 1680 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec 29 16:04:58 2018
InstallationDate: Installed on 2018-12-29 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: alsa-driver
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/25/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX390UAK.312
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX390UAK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX390UAK.312:bd04/25/2017:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX390UAK
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Jule Marcoueille (jule.createrocks) wrote :
Revision history for this message
Jule Marcoueille (jule.createrocks) wrote :

Do not know if it is a pulseaudio or a alsa-driver bug (cf. https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/PulseAudioStoleMyVolumes/) but I think it is both:
1/ ALSA driver may not report correct dB information.
2/ PulseAudio may not correctly mix PCM into Master since changing Master volume does nothing at all.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The animation in volume-issue.gif doesn't seem to show any bug that I can see.

My working system has the same behaviour, so I don't think the gif is relevant.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1773700, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

Revision history for this message
Jule Marcoueille (jule.createrocks) wrote :

@vanvugt: the gif is relevant in order to understand well the bug I think, I mean it may show the correct way of handling some devices but as I said in my case changing PCM volume is the only way to get volume react normally since Master volume does nothing at all. I guess it can help devs understand where the bug is coming from.

And indeed this is a duplicate of https://bugs.launchpad.net/bugs/1773700. I did not find him before, sorry for this one.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.