Upon booting with dkms+dotdeb#29 installed, had triple-dash by spkr-icon in systray (still have autospawn=no). Ran espeak, worked (same errors as usual). Ran speaker-test, found new and interesting problems. $ speaker-test -D default -t wav -c 6 -l 1
speaker-test 1.0.25 Playback device is default Stream parameters are 48000Hz, S16_LE, 6 channels WAV file(s) Rate set to 48000Hz (requested 48000Hz) Buffer size range from 2048 to 8192 Period size range from 1024 to 1024 Using max buffer size 8192 Periods = 4 was set period_size = 1024 was set buffer_size = 8192 0 - Front Left 4 - Center Write error: -32,Broken pipe Write error: -32,Broken pipe 1 - Front Right Write error: -32,Broken pipe Write error: -32,Broken pipe 3 - Rear Right Write error: -32,Broken pipe Write error: -32,Broken pipe 2 - Rear Left Write error: -32,Broken pipe Write error: -32,Broken pipe 5 - LFE Write error: -32,Broken pipe Time per period = 26.014328 FrontLeft and FrontRight functioned... there was also some audible pop- pop sounds during the test, and FrontRight was not a clean playback- attempt (it paused-slash-glitched in the middle of the words). See also, errors above. Alsa-info.txt attached Next, started up pulseaudio, which caused the systray-spkr-icon to have rparens again. j@j-P180HMx:~$ ps aux | grep -i pulseaudio | grep -v grep j@j-P180HMx:~$ pulseaudio --start j@j-P180HMx:~$ ps aux | grep -i pulseaudio | grep -v grep j 3032 7.5 0.0 418176 5664 ? S<l 14:41 0:00 pulseaudio --start j 3036 0.0 0.0 95956 2980 ? S 14:41 0:00 /usr/lib/pulseaudio/pulse/gconf-helper espeak still works (albeit still with the usual errors) $ speaker-test -D default -t wav -c 6 -l 1 speaker-test 1.0.25 Playback device is default Stream parameters are 48000Hz, S16_LE, 6 channels WAV file(s) Rate set to 48000Hz (requested 48000Hz) Buffer size range from 32 to 349525 Period size range from 10 to 116509 Using max buffer size 349524 Periods = 4 was set period_size = 87381 was set buffer_size = 349524 0 - Front Left 4 - Center 1 - Front Right 3 - Rear Right 2 - Rear Left 5 - LFE Time per period = 10.817687 (this test worked much better -- no broken-pipe-write-errors for starters, plus all sounds were clear and non-glitchy) (still silent for LFE, and still quiter-than-maybe-is-proper for rearLeft and rearRight, however). Opening up sound-settings from the systray, we see new and interesting content in the lefthand and righthand panels. the output tab now offers: digital output (spdif) built-in audio [been around a long time but relatively useless with nothing plugged in] analog output built-in audio [newly visible now that dotdeb#29 is installed] speaker built-in audio [visible due to workaround#32 from other thread... but righthand panel now improved] the righthand panel for spdif shows: balance, greyed-out fade, greyed-out subwoofer, test sound btn (when clicked offers only frontLeft/frontRight subtests) the righthand panel for the new analog-output entry shows: balance, fade (non-grey), subwoofer (non-grey), mode dropdown (default Analog Surround 4.1 Output but also offers 4.0 5.0 5.1 options), test sound btn (when clicked has frontLeft/frontRight/rearLeft/rearRight/subwoofer with 4.1 in combobox, selecting 5.1 in combobox adds FrontCenter as a subtest). Clicking all the subtest-buttons with 5.1 in the combobox is successful, with much-louder-volume from rearRight/rearLeft speakers, and finally some sound from the subwoofer. All the subtests have spoken lines, except for the subwoofer which makes pink noise, but methinks that is just a missing wav-file. the righthand panel for the speaker-built-in-audio entry shows: almost identical to the analog-input entry... and in fact, if you change from 4.1 to 5.1 in the analog-entry, the speaker-entry combobox also changes, and ditto if you make the change in speaker-entry, the analog-entry follows along. The only difference I noticed was that the dropdown for speaker-built-in has 4.1 + 5.0 + 4.0 + AnalogStereoOutpu + 5.1 whereas analog-entry dropdown simply has 4.1 + 5.0 + 4.0 + AnalogStereoOutpu + 5.1 Leaving the dropdown set to 5.1, and the speaker-built-in-audio as the selected output-device, I closed sound-settings. $ speaker-test -D default -t wav -c 6 -l 1 speaker-test 1.0.25 Playback device is default Stream parameters are 48000Hz, S16_LE, 6 channels WAV file(s) Rate set to 48000Hz (requested 48000Hz) Buffer size range from 32 to 349525 Period size range from 10 to 116509 Using max buffer size 349524 Periods = 4 was set period_size = 87381 was set buffer_size = 349524 0 - Front Left 4 - Center 1 - Front Right 3 - Rear Right 2 - Rear Left 5 - LFE Time per period = 9.360410 (ahhhh... for the first time, all six channels were nice and loud... LFE was verbalized as "Rear Center") (that one seemed to be coming from the same speaker as FrontCenter... rather than from subwoofer?) I also tried this, just for kicks, just relying on the onboard speakers like usual, not plugging anything in: $ speaker-test -D default -t wav -c 8 -l 1 speaker-test 1.0.25 Playback device is default Stream parameters are 48000Hz, S16_LE, 8 channels WAV file(s) Rate set to 48000Hz (requested 48000Hz) Buffer size range from 24 to 262144 Period size range from 8 to 87382 Using max buffer size 262144 Periods = 4 was set period_size = 65536 was set buffer_size = 262144 0 - Front Left 4 - Center 1 - Front Right 7 - Side Right 3 - Rear Right 2 - Rear Left 6 - Side Left 5 - LFE Time per period = 12.472912 (all outputs were as before, with the addition of sideLeft/sideRight, which seemed somewhat-quiet-but-still-audible) (since those speakers do not actually exist, p'raps this is not surprising.) j@j-P180HMx:~$ espeak "sweet" ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5) ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5) ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5) ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5) ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream Cannot connect to server socket err = No such file or directory Cannot connect to server socket jack server is not running or cannot be started (the word 'sweet' is spoken nice and loudly) Switching over to pavucontrol, there are all kinds of changes here as well. On the output devices tab, I still have the two dropdowns, like before, but I now see a bunch more sliders and checkboxes and such. Under the soundcard-on-the-videocard, the dropdown has HDMI/DisplayPort by default, and no other options. By default only the PCM checkbox is on, which means you only see frontLeft/frontRight volume-sliders. Other checkboxes are AC3/EAC3/DTS/MPEG. Checking those boxes does not give me more than 2ch for hdmi, however. Under the built-in-audio-analog-surround-5.1 section (new&improved), we now have a bunch of new stuff. Volume-sliders for frontLeft/frontRight/rearLeft/rearRight/frontCenter/subwoofer. The 'port' dropdown defaults to Speakers, but can also be changed to AnalogOutput (prolly line-out... or maybe 7.1 out?) Over under the configuration-tab of pavucontrol, there are two dropdowns like before. the hdmi-oriented soundcard-on-videocard dropdown is still the same, either hdmi or off the built-in-audio dropdown has a large number of options available now: default is analog surround 5.1 output + analog stereo input (can also be 4.0 4.1 5.0) can also be 4.0 4.1 5.0 5.1 without mention of the analog stereo input and, we additionally retain all the options we saw last time: Analog Stereo Duplex, Analog Stereo Output, Digital Stereo (IEC 598) Output Plus Analog Stereo Input, Digital Stereo (IEC 598) Output, Analog Stereo Input, Off playback of a sample mp3 in rhythmbox is nice and loud... not sure if all the speakers are being exercised, however. (is there a vox-level tool that will tell me what the volume-output is on various individual speakers?) comparing the aggregate-pulseaudio volume to the individual alsamixer-channels, it *looks* like it is doing the wrong thing, because when I slight the sound-setting-volume-slider up and down, only the alsa master channel follows along... until almost the very bottom of the volume-range, when suddenly speakerCLFE + speakerFront + speakerSurround channels in alsamixer start to rapidly fall from max, and shortly afterwards, the alsamixer PCM channel also drops rapidly from max to zero. That's the theory. In practice, the volume-slider on teh systray works just peachy-keen, despite what alsamixer might show. Max-volume on the systray slider is very loud, and actual-in-practice volume goes down smoothly. So, in other words, works fine by my standards, even though the alsamixer rendering of the current volume-settings might leave something to be desired. Finally, a note on the names. Alsamixer no longer cuts off channel- names, but not because the length was permitted to exceed 32 bytes including terminator... instead, the channels have been renamed, with shorter monikers. Master, Headphone, Speaker CLFE, Speaker Front, Speaker Surround, PCM, Line, Line Boost, Line Boost (again), Mic, Mic Boost, Mic Boost, S/PDIF, S/PDIF Default, Capture, Auto-Mute Mode, Digital, Internal Mic -- those are the alsamixer channels for the ALC892. (the r6xx still offers just S/PDIF and nothing more). So -- progress. Any tests somebody would like me to run, with this new setup? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1236965 Title: pulseaudio does not recognize internal speakers [P180HMx, Realtek ALC892, Speaker, Internal] volume slider problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1236965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
