| Summary: | amixer audio - sound on/off - is failing | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BSPs | Reporter: | Ionut Chisanovici <ionutx.chisanovici> | ||||
| Component: | bsps-tools | Assignee: | Jussi Kukkonen <jku> | ||||
| Status: | VERIFIED FIXED | QA Contact: | Cristina Agurida <cristina-danielax.agurida> | ||||
| Severity: | normal | ||||||
| Priority: | Medium | CC: | alexandru.c.georgescu, bogdanx.a.voiculescu, jku, ross.burton, tanuk | ||||
| Version: | 1.8 | ||||||
| Target Milestone: | 1.9 M3 | ||||||
| Hardware: | x86 | ||||||
| OS: | Multiple | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | Regression (Used to work) | ||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||
| Bug Depends on: | 7517 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Ionut Chisanovici
2015-03-09 13:36:19 UTC
Investigation started. This is a NUC with both HDMI audio (in the back) and a headphone port (in the front), right? My D54250WYK plays no audio through the headphones by default because there are two alsa cards, and the wrong one is the default. "aplay -l" shows two "HDMI" devices on card 0 and a "PCM" analog device on card 1. The HDMI devices do not seem to have any volume control capabilities so the amixer commands fail. I'm not sure if this should work out of the box (without pulseaudio) but you can either change the default card (see bug 7430) or use the amixer option "-c 1" or "-c PCM" to make the amixer commands work: amixer -c 1 set Master on Issue is reproducible on 1.7.1 and coupled meta-nuc release also, so I am not really sure about the "regression" part. Hi Jussi, what MACHINE have you used to build the image? Also, the recommended NUC machine to test this on and supported by meta-nuc is "Next Unit of Computing Kit DC3217IYE" with Intel Centrino Advanced-N 6235 Wireless mini PCI Express card. This specific NUC does not have any audio output except via HDMI. I also tested this with IntelĀ® NUC Kit D54250WYK, issue is still reproducible. (In reply to comment #4) > Hi Jussi, what MACHINE have you used to build the image? I build for "intel-corei7-64". > Also, the recommended NUC machine to test this on and supported by meta-nuc > is "Next Unit of Computing Kit DC3217IYE" Unfortunately what I have on the desk is not that one. > with Intel Centrino Advanced-N 6235 Wireless mini PCI Express card. > This specific NUC does not have any audio output except via HDMI. > I also tested this with IntelĀ® NUC Kit D54250WYK, issue is still > reproducible. Ok, good to know. Testing HDMI output has proven difficult here. I still don't have the right cables... Have you checked if your device still shows up as two alsa cards ("aplay -l")? Ok, I think I've figured out how to get the HDMI audio working. I'll explain that in the other bug but this bug is in my opinion not really a bug: > 2. Run "amixer set Master on" to turn on audio device The mixer is not called Master for the HDMI device, but IEC958. So this should work: "amixer set IEC958 on" > 3. Run "amixer set Master 64" to adjust to maxium volumn This should not work because the card does not seem to support volume adjustment. > 4. Run "amixer set Master off" to turn off audio device "amixer set IEC958 off" > 5. Run "amixer set Speaker on" to turn on speaker (when Speaker is available) > 6. Run "amixer set Speaker 64" to adjust to maxium volumn (when Speaker is available) > 7. Run "amixer set Speaker off" to turn off speaker (when Speaker is available) There are no other controls than IEC958. Comment from Ross Burton: "So this is exactly the sort of thing that the "machine autoconfiguration" was meant to help with, but that means writing configuration files for every machine, which sucks. I'm rapidly thinking that for 1.9 we should integrate PulseAudio properly into the Sato images and let PA deal with this. For 1.8 we have to admit that raw ALSA on modern hardware is a losing battle and we can't fix this generally, and fixing it for one NUC breaks for another NUC." Hi Alex, This bug should be re-tested, because PulseAudio has now been integrated into Sato. Can someone recheck this on master with core-image-sato image, please? I had a look at the test case, and I have a couple of notes about it now that amixer goes through PulseAudio by default: Setting the Master volume to 64 will result in very low volume, because PulseAudio exposes a very fine-grained volume scale. Since the success condition of the test is just that the command can be run without errors, maybe this doesn't matter. The optional steps that modify the Speaker volume will not work, because PulseAudio doesn't expose a volume control named "Speaker". Marking this NEEDINFO as it should be retested now that pulseaudio is handling things. See Tanus comment 9 for possibly needed changes in the test procedure. Tanu: if you think other tools than alsamixer (like some pulseaudio tool) should be used for tests like this, please comment. My proposal would be to modify step 3 to use command "amixer set Master 30%", and to drop steps 5-7. I chose 30%, because it's likely to be easily audible, but not annoyingly loud, although the exact loudness is very much hardware dependent. I'm not proposing to use pulseaudio tools, because "amixer set Master 30%" has the nice feature that it will modify the default sink volume. Doing the same with pactl would require a bit more complicated scripting (first getting the default sink name, which requires grepping, and then another command for setting the volume of the default sink). Needinfo answer given. Stephen, I marked it needinfo because it should be retested/re-evaluated. Tanus comment does not change that. I'm resetting NEEDINFO. If there's actually another way I should be marking 'needs testing', please let me know. Verified on latest master, and the issue is not present anymore. For better using it is good to set the value as a percentage just as Tanu said in the above comments. That's fixed then, thanks Cristina. As per last comments set it as verified. Created attachment 3840 [details]
qemux86_log
(In reply to comment #18) > Created attachment 3840 [details] > qemux86_log wrong bug? |