Description of problem: Ican't find any settings that work with my soundcard to get any audio what so ever. I'm not using any Testing-medias. Here's my info: Output of modinfo soundcore as root: filename: /lib/modules/3.3.6-desktop-2.mga2/kernel/sound/soundcore.ko.xz alias: char-major-14-* license: GPL author: Alan Cox description: Core sound module srcversion: 4FE38E80FCFA494206C29AB depends: intree: Y vermagic: 3.3.6-desktop-2.mga2 SMP mod_unload modversions parm: preclaim_oss:int alsamixer shows that master-level is set to 0 as standard. lspcidrake -vv as root shows: snd_hda_intel : Intel Corporation|N10/ICH 7 Family High Definition Audio Controller (vendor:8086 device:27d8 subv:1849 subd:3662) (rev: 01) Kernel-version is: 3.3.6-desktop-2.mga2 Here's my alsa-info.sh output: http://www.alsa-project.org/db/?f=b4e60694ebf2ccc840a5ea52649e1da4e2ed5109 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
CC: (none) => kristoffer.grundstrom1983
Source RPM: task-kde4 => snd_hda_intel
Component: New RPM package request => RPM Packages
From the output it looks like you do not have any ACLs on your sound device nodes. Can you confirm this by doing: "getfacl /dev/snd/pcm*"? If this is the case, can I ask *how* you login? Is it via GDM, KDM, autologin or startx?
CC: (none) => mageia
Actually it seems the alsa-info script doesn't really show ACLs properly, so this could be bogus, but please confirm first. If the ACLs are correct, please attach the output of "pacmd ls".
Result of pacmd ls: http://pastebin.ca/2158988 Result of getfacl /dev/snd/pcm*: >>> [kristoffer@localhost ~]$ getfacl /dev/snd/pcm* getfacl: Removing preliminary "/" from absolute searchpaths # file: dev/snd/pcmC0D0c # owner: root # group: audio user::rw- user:kristoffer:rw- group::rw- mask::rw- other::--- # file: dev/snd/pcmC0D0p # owner: root # group: audio user::rw- user:kristoffer:rw- group::rw- mask::rw- other::--- # file: dev/snd/pcmC0D2c # owner: root # group: audio user::rw- user:kristoffer:rw- group::rw- mask::rw- other::---
Created attachment 2437 [details] pacmd ls output. Please don't use pastebin URLs for content as they expire which is not good for bug history.
(In reply to comment #4) > Created attachment 2437 [details] > pacmd ls output. > > Please don't use pastebin URLs for content as they expire which is not good for > bug history. OK, but I did set it to expire in 1 year. ;)
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD
Created attachment 4539 [details] Here's the new pacmd ls output I have to open this again since I can't get any settings in kmix to work.
Attachment 2437 is obsolete: 0 => 1
Version: 2 => CauldronSeverity: major => normal
Resolution: OLD => (none)Status: RESOLVED => REOPENED
I'm using 3.12.1-desktop-1.mga4 as kernel.
getfacl /dev/snd/pcm* shows: # file: dev/snd/pcmC0D0c # owner: root # group: audio user::rw- user:kristoffer:rw- group::rw- mask::rw- other::--- # file: dev/snd/pcmC0D0p # owner: root # group: audio user::rw- user:kristoffer:rw- group::rw- mask::rw- other::--- # file: dev/snd/pcmC1D3p # owner: root # group: audio user::rw- user:kristoffer:rw- group::rw- mask::rw- other::--- # file: dev/snd/pcmC1D7p # owner: root # group: audio user::rw- user:kristoffer:rw- group::rw- mask::rw- other::--- # file: dev/snd/pcmC1D8p # owner: root # group: audio user::rw- user:kristoffer:rw- group::rw- mask::rw- other::--- # file: dev/snd/pcmC1D9p # owner: root # group: audio user::rw- user:kristoffer:rw- group::rw- mask::rw- other::---
I use KDM to login with.
The sound works if/when I connect headphones.
Attachment 4539 mime type: application/octet-stream => text/plain
(In reply to Kristoffer Grundström from comment #8) > Created attachment 4539 [details] > Here's the new pacmd ls output ports: analog-output: Analog Output (priority 9900, latency offset 0 usec, available: unknown) properties: analog-output-speaker: Speakers (priority 10000, latency offset 0 usec, available: unknown) properties: device.icon_name = "audio-speakers" analog-output-headphones: Headphones (priority 9000, latency offset 0 usec, available: no) properties: device.icon_name = "audio-headphones" active port: <analog-output> You have the "analog-output" port selected. This is not the highest priority port. Try unplugging your headphones and then select the "Speakers" output (just do "pactl set-sink-port 1 analog-output-speaker" if you don't have a GUI and your sink index is still 1 - it might not be if you rebooted etc). If that works, check that plugging in your Headphones properly changes the port to Headphones and then back to Speakers again on unplug. If this fixes things then all is well. If it doesn't make sure Speakers is selected, set the volume to some sensible level in a PA mixer GUI (i.e. don't fiddle with ALSA controls directly) and then attach the output of amixer -c0 as plain text.
Result of amixer -c0 since changing priority from Analog to HDMI: http://pastebin.ca/2484109
(In reply to Kristoffer Grundström from comment #14) > Result of amixer -c0 since changing priority from Analog to HDMI: > http://pastebin.ca/2484109 HDMI is a completely different card, so not sure what you did before creating this file. Can you please confirm that you did as I asked with the ports in PA (forget HDMI, it's irrelevent, we're only interested in the Sink Ports for your Analog card. I've quoted the relevant snipped from your pacmd ls, so use this as reference to make sure you've definitely set things up as requested in my previous comment (i.e. check the "active port: ..." for the sink). Also please attach the output here as requested. Relying on pastebin links in 1 years time is totally unreliable.
Giving pactl set-sink-port 1 analog-output-speaker & reconnecting the headphones & then unplug them seems to solve the issue. Possible regression?
New output of pacmd ls after previous command & unplugin' theheadphones: [kristoffer@localhost ~]$ amixer -c0 Simple mixer control 'Master',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono Limits: Playback 0 - 74 Mono: Playback 64 [86%] [-10.00dB] [on] Simple mixer control 'Headphone',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right Limits: Playback 0 - 74 Mono: Front Left: Playback 0 [0%] [-74.00dB] [off] Front Right: Playback 0 [0%] [-74.00dB] [off] Simple mixer control 'Speaker',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right Limits: Playback 0 - 74 Mono: Front Left: Playback 74 [100%] [0.00dB] [on] Front Right: Playback 74 [100%] [0.00dB] [on] Simple mixer control 'PCM',0 Capabilities: pvolume Playback channels: Front Left - Front Right Limits: Playback 0 - 255 Mono: Front Left: Playback 255 [100%] [0.00dB] Front Right: Playback 255 [100%] [0.00dB] Simple mixer control 'Mic Boost',0 Capabilities: volume Playback channels: Front Left - Front Right Capture channels: Front Left - Front Right Limits: 0 - 4 Front Left: 0 [0%] [0.00dB] Front Right: 0 [0%] [0.00dB] Simple mixer control 'Beep',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono Limits: Playback 0 - 7 Mono: Playback 0 [0%] [-28.00dB] [off] Simple mixer control 'Capture',0 Capabilities: cvolume cswitch Capture channels: Front Left - Front Right Limits: Capture 0 - 80 Front Left: Capture 80 [100%] [6.00dB] [on] Front Right: Capture 80 [100%] [6.00dB] [on] Simple mixer control 'Auto-Mute Mode',0 Capabilities: enum Items: 'Disabled' 'Enabled' Item0: 'Enabled' Simple mixer control 'Digital',0 Capabilities: cvolume Capture channels: Front Left - Front Right Limits: Capture 0 - 120 Front Left: Capture 60 [50%] [0.00dB] Front Right: Capture 60 [50%] [0.00dB] Simple mixer control 'Internal Mic Boost',0 Capabilities: volume Playback channels: Front Left - Front Right Capture channels: Front Left - Front Right Limits: 0 - 4 Front Left: 3 [75%] [36.00dB] Front Right: 3 [75%] [36.00dB]
(In reply to Kristoffer Grundström from comment #16) > Giving pactl set-sink-port 1 analog-output-speaker & reconnecting the > headphones & then unplug them seems to solve the issue. > > Possible regression? Not really as far as I can tell. The priorites of the ports are correct and the only way that analog-output could be selected is if it's done manually or via a specific choice. The preferred port is saved and restored in PA so once it's set once it will be remembered. Something must have set it, either by the user accidentally when playing with some GUI or via some other application fiddling with underlying alsa controls outside of PA. Either way things are working as intended here. I do have a bug report where a fresh user account seems to select profiles and ports of incorrect priority which might cross over with the issues here. Without the hardware for me to test on tho', it's next to impossible to get the right debug information remotely as it's something you need to do several times and put in very specific breakpoints to see when the configuration is getting messed up. See also bug #11642 As things physically work for you and it's just an officially non-default (i.e. not highest priority) port that is not working for you, I'll close this bug again. Thanks.
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
Created attachment 4560 [details] amixer-logfile from a fresh installation without any updates
Created attachment 4561 [details] pacmd -ls from the same installation without updates
Created attachment 4562 [details] lspcidrake for this laptop
This is not fixed. I see it in Mageia 3 now also. Had to change main channel from HDMI to Analog audio & then raise the volume.
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
This is a cauldron bug and it should stay closed as you reported further up. It serves no purpose to stay open - default values are correct and I still need to look at issues which affect headphones and incorrect profiles on first fresh boot, but there are plenty open bugs for that already and I don't need more.