Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.os.linux.slackware > #25398 > unrolled thread

Lost HDMI sound with recent current upgrade.

Back to article view | Back to alt.os.linux.slackware

Contents

  Lost HDMI sound with recent current upgrade. "Rinaldi J. Montessi" <rinaldi@notaserver.com> - 2015-08-24 09:44 -0500
    Re: Lost HDMI sound with recent current upgrade. "Mr. Mxyztplk" <user@foobar.com.invalid> - 2015-08-26 23:33 +0000
      Re: Lost HDMI sound with recent current upgrade. "Rinaldi J. Montessi" <rinaldi@notaserver.com> - 2015-08-26 22:23 -0500
        Re: Lost HDMI sound with recent current upgrade. "Rinaldi J. Montessi" <rinaldi@notaserver.com> - 2015-08-27 15:55 -0500
    Re: Lost HDMI sound with recent current upgrade. "Mr.  Mxyztplk" <user@foobar.com.invalid> - 2015-08-26 18:51 -0500
      Re: Lost HDMI sound with recent current upgrade. "Rinaldi J. Montessi" <rinaldi@notaserver.com> - 2015-08-26 22:24 -0500
        Re: Lost HDMI sound with recent current upgrade. "Mr. Mxyztplk" <user@foobar.com.invalid> - 2015-08-27 14:24 +0000
          Re: Lost HDMI sound with recent current upgrade. Jerry Peters <jerry@example.invalid> - 2015-08-27 20:18 +0000
            Re: Lost HDMI sound with recent current upgrade. "Rinaldi J. Montessi" <rinaldi@notaserver.com> - 2015-08-27 15:56 -0500
              Re: Lost HDMI sound with recent current upgrade. Eef Hartman <E.J.M.Hartman@gmail.com> - 2015-08-27 23:12 +0000
                Re: Lost HDMI sound with recent current upgrade. "Rinaldi J. Montessi" <rinaldi@notaserver.com> - 2015-08-27 20:20 -0500
                  Re: Lost HDMI sound with recent current upgrade. Rich <rich@example.invalid> - 2015-08-28 01:58 +0000
                    Re: Lost HDMI sound with recent current upgrade. JohnF <john@please.see.sig.for.email.com> - 2015-08-28 02:22 +0000
                      Re: Lost HDMI sound with recent current upgrade. Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2015-08-28 05:41 +0000
                        Re: Lost HDMI sound with recent current upgrade. Rich <rich@example.invalid> - 2015-08-28 09:12 +0000

#25398 — Lost HDMI sound with recent current upgrade.

Slackware14-1 x86_64 current repository.

Anyone else see this?

Aplay -l* still sees the device and speaker-test** shows that is is
doing the right thing but no sound comes out.  This is an ati radeon
6450 card with an HDMI output cable that I use for watching movies on an
old flat screen TV and as a second monitor (HDMI-0)

I have done the google thing to no avail.  Added boot parameter
(probably not needed)   radeon.audio=1 and tried the xrandr --output
HDMI-0 --set audio on solution posted elsewhere.

Any advice appreciated.

*$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC888 Analog [ALC888 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 1: ALC888 Digital [ALC888 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

**$ speaker-test -c 2 -r 48000 -D hw:1,3

speaker-test 1.0.29

Playback device is hw:1,3
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 64 to 524288
Period size range from 32 to 262144
Using max buffer size 524288
Periods = 4
was set period_size = 131072
was set buffer_size = 524288
 0 - Front Left
 1 - Front Right
Time per period = 5.470557
 0 - Front Left
 1 - Front Right
^CTime per period = 5.412347

-- 
There is nothing wrong with Southern California that a rise in the
ocean level wouldn't cure.
		-- Ross MacDonald

[toc] | [next] | [standalone]

#25420

On Mon, 24 Aug 2015 09:44:29 -0500, Rinaldi J. Montessi wrote:

What's your .asoundrc file (if there is one) in your home directory look 
like

Make/rewrite it
try something like this

pcm.!default {
	type hw
	card 1
	device 3
}

ctl.!default {
	type hw           
	card 1
	device 3
}
timer.!default {
	type hw
	card 1
	device 3
}

[toc] | [prev] | [next] | [standalone]

#25422

Mr. Mxyztplk decreed, Read These Runes!:
> On Mon, 24 Aug 2015 09:44:29 -0500, Rinaldi J. Montessi wrote:
> 
> What's your .asoundrc file (if there is one) in your home directory look 
> like
> 
> Make/rewrite it
> try something like this
> 
> pcm.!default {
> 	type hw
> 	card 1
> 	device 3
> }
> 
> ctl.!default {
> 	type hw           
> 	card 1
> 	device 3
> }
> timer.!default {
> 	type hw
> 	card 1
> 	device 3
> }

Works fine for HDMI, thank you.  But now I have no analog speakers,
hw:0,0.  Is this an either/or situation?

Thanks again!
-- 
Drugs may be the road to nowhere, but at least they're the scenic
route!

[toc] | [prev] | [next] | [standalone]

#25426

Rinaldi J. Montessi decreed, Read These Runes!:
> Mr. Mxyztplk decreed, Read These Runes!:
>> On Mon, 24 Aug 2015 09:44:29 -0500, Rinaldi J. Montessi wrote:
>> 
>> What's your .asoundrc file (if there is one) in your home directory look 
>> like
>> 
>> Make/rewrite it
>> try something like this
>> 
>> pcm.!default {
>> 	type hw
>> 	card 1
>> 	device 3
>> }
>> 
>> ctl.!default {
>> 	type hw           
>> 	card 1
>> 	device 3
>> }
>> timer.!default {
>> 	type hw
>> 	card 1
>> 	device 3
>> }
> 
> Works fine for HDMI, thank you.  But now I have no analog speakers,
> hw:0,0.  Is this an either/or situation?

Answering my own question:

Adding this stanza to the top of /etc/pulse/default.pa:

### Load analog device ##added by RJM
load-module module-alsa-sink device=hw:0,0
load-module module-combine-sink sink_name=combined
set-default-sink combined

gives total control of speakers through pavucontrol.

-- 
"Nuclear war would really set back cable."
		-- Ted Turner

[toc] | [prev] | [next] | [standalone]

#25421

by your home directory I should have said your /home/user, i.e ~ directory
you can also check what is in /etc/asound.conf (if it exists yet), put what 
I suggested in there and that should be system-wide

[toc] | [prev] | [next] | [standalone]

#25423

Mr.  Mxyztplk decreed, Read These Runes!:

> by your home directory I should have said your /home/user, i.e ~ directory
> you can also check what is in /etc/asound.conf (if it exists yet), put what 
> I suggested in there and that should be system-wide

There is an /etc/asound.state.  Same thing?

Rinaldi
-- 
Drugs may be the road to nowhere, but at least they're the scenic
route!

[toc] | [prev] | [next] | [standalone]

#25424

On Wed, 26 Aug 2015 22:24:23 -0500, Rinaldi J. Montessi wrote:

> Mr.  Mxyztplk decreed, Read These Runes!:
> 
>> by your home directory I should have said your /home/user, i.e ~
>> directory you can also check what is in /etc/asound.conf (if it exists
>> yet), put what I suggested in there and that should be system-wide
> 
> There is an /etc/asound.state.  Same thing?
> 
> Rinaldi

Yeah, except that it's system wide for all users, .asoundrc is just for 
whatever user's ~ directory it belongs to.

[toc] | [prev] | [next] | [standalone]

#25425

Mr. Mxyztplk <user@foobar.com.invalid> wrote:
> On Wed, 26 Aug 2015 22:24:23 -0500, Rinaldi J. Montessi wrote:
> 
>> Mr.  Mxyztplk decreed, Read These Runes!:
>> 
>>> by your home directory I should have said your /home/user, i.e ~
>>> directory you can also check what is in /etc/asound.conf (if it exists
>>> yet), put what I suggested in there and that should be system-wide
>> 
>> There is an /etc/asound.state.  Same thing?
>> 
>> Rinaldi
> 
> Yeah, except that it's system wide for all users, .asoundrc is just for 
> whatever user's ~ directory it belongs to.

No, you want to create /etc/asound.conf.

/etc/asound.state is used to save volatile settings over boot. It's
written by 'alsactl store' during shutdown. 

[toc] | [prev] | [next] | [standalone]

#25427

Jerry Peters decreed, Read These Runes!:
> Mr. Mxyztplk <user@foobar.com.invalid> wrote:
>> On Wed, 26 Aug 2015 22:24:23 -0500, Rinaldi J. Montessi wrote:
>> 
>>> Mr.  Mxyztplk decreed, Read These Runes!:
>>> 
>>>> by your home directory I should have said your /home/user, i.e ~
>>>> directory you can also check what is in /etc/asound.conf (if it exists
>>>> yet), put what I suggested in there and that should be system-wide
>>> 
>>> There is an /etc/asound.state.  Same thing?
>>> 
>>> Rinaldi
>> 
>> Yeah, except that it's system wide for all users, .asoundrc is just for 
>> whatever user's ~ directory it belongs to.
> 
> No, you want to create /etc/asound.conf.
> 
> /etc/asound.state is used to save volatile settings over boot. It's
> written by 'alsactl store' during shutdown. 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Didn't know that.  I thought alsactl only ran on demand.  Thanks!

Rinaldi
-- 
Succumb to natural tendencies.  Be hateful and boring.

[toc] | [prev] | [next] | [standalone]

#25428

Rinaldi J. Montessi <rinaldi@notaserver.com> wrote:
>> /etc/asound.state is used to save volatile settings over boot. It's
>> written by 'alsactl store' during shutdown. 
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> Didn't know that.  I thought alsactl only ran on demand.  Thanks!

IF you made rc.alsa executable, of course:
> if [ -r /etc/asound.state ]; then
>   echo "Loading ALSA mixer settings:  /usr/sbin/alsactl restore"
>   /usr/sbin/alsactl restore
at boot-up, cq.
>   echo "Storing default ALSA mixer settings:  /usr/sbin/alsactl store"
>   /usr/sbin/alsactl store
when that file is NOT there yet.

Note: nothing is done at shutdown!

[toc] | [prev] | [next] | [standalone]

#25429

Eef Hartman decreed, Read These Runes!:
> Rinaldi J. Montessi <rinaldi@notaserver.com> wrote:
>>> /etc/asound.state is used to save volatile settings over boot. It's
>>> written by 'alsactl store' during shutdown. 
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> 
>> Didn't know that.  I thought alsactl only ran on demand.  Thanks!
> 
> IF you made rc.alsa executable, of course:
>> if [ -r /etc/asound.state ]; then
>>   echo "Loading ALSA mixer settings:  /usr/sbin/alsactl restore"
>>   /usr/sbin/alsactl restore
> at boot-up, cq.
>>   echo "Storing default ALSA mixer settings:  /usr/sbin/alsactl store"
>>   /usr/sbin/alsactl store
> when that file is NOT there yet.
> 
> Note: nothing is done at shutdown!

Thanks for the clarification.  I have rc.alsa executable but bootup is
so quick I only get to see a fraction of the messages and dmesg isn't
helpful.

Rinaldi
-- "I went to the museum where they had all the heads and arms from the
statues that are in all the other museums."
		-- Steven Wright

[toc] | [prev] | [next] | [standalone]

#25430

Rinaldi J. Montessi <rinaldi@notaserver.com> wrote:
> Eef Hartman decreed, Read These Runes!:
> > Rinaldi J. Montessi <rinaldi@notaserver.com> wrote:
> >>> /etc/asound.state is used to save volatile settings over boot. It's
> >>> written by 'alsactl store' during shutdown. 
> >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >> 
> >> Didn't know that.  I thought alsactl only ran on demand.  Thanks!
> > 
> > IF you made rc.alsa executable, of course:
> >> if [ -r /etc/asound.state ]; then
> >>   echo "Loading ALSA mixer settings:  /usr/sbin/alsactl restore"
> >>   /usr/sbin/alsactl restore
> > at boot-up, cq.
> >>   echo "Storing default ALSA mixer settings:  /usr/sbin/alsactl store"
> >>   /usr/sbin/alsactl store
> > when that file is NOT there yet.
> > 
> > Note: nothing is done at shutdown!

> Thanks for the clarification.  I have rc.alsa executable but bootup is
> so quick I only get to see a fraction of the messages and dmesg isn't
> helpful.

Look in /var/log/.  The kernel boot messages get logged into files in
/var/log/ when syslog starts up.  That's why dmesg isn't helpful,
syslog has already emptied the kernel ring buffer to a disk file by the
time you can get to a shell to type dmesg.

[toc] | [prev] | [next] | [standalone]

#25431

Rich <rich@example.invalid> wrote:
><<snip>>
> Look in /var/log/.  The kernel boot messages get logged into files in
> /var/log/ when syslog starts up.

Somewhat off topic, but yeah, that can be very helpful.
I've added a line to /etc/syslog.conf
   *.*    -/var/log/allmessages
just to accumulate all messages in one place for easy reference or grep.

> That's why dmesg isn't helpful,
> syslog has already emptied the kernel ring buffer to a disk file
> by the time you can get to a shell to type dmesg.
-- 
John Forkosh  ( mailto:  j@f.com  where j=john and f=forkosh )

[toc] | [prev] | [next] | [standalone]

#25435

On Fri, 28 Aug 2015 02:22:22 +0000, JohnF wrote:
> Somewhat off topic, but yeah, that can be very helpful. I've added a
> line to /etc/syslog.conf
>    *.*    -/var/log/allmessages
> just to accumulate all messages in one place for easy reference or grep.

Dmesg can be very helpful for many things, but those boot messages coming 
from echo lines in rc.d scripts are only seen during boot.

fgrep echo /etc/rc.d/rc.alsa 
gives:
-8<-----------------
    echo "Loading ALSA mixer settings:  /usr/sbin/alsactl restore"
      echo "Setting default ALSA mixer settings."
      echo "Storing default ALSA mixer settings:  /usr/sbin/alsactl store"
    echo "Loading OSS compatibility modules for ALSA."
    echo "Loading ALSA kernel modules."
-8<-----------------

None of those messages will be seen by dmesg or in any log file.

regards Henrik
-- 
The address in the header is only to prevent spam. My real address is:
hc351(at)poolhem.se Examples of addresses which go to spammers:
root@localhost postmaster@localhost

[toc] | [prev] | [next] | [standalone]

#25436

Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> wrote:
> On Fri, 28 Aug 2015 02:22:22 +0000, JohnF wrote:
> > Somewhat off topic, but yeah, that can be very helpful. I've added a
> > line to /etc/syslog.conf
> >    *.*    -/var/log/allmessages
> > just to accumulate all messages in one place for easy reference or grep.

> Dmesg can be very helpful for many things, but those boot messages coming 
> from echo lines in rc.d scripts are only seen during boot.

> fgrep echo /etc/rc.d/rc.alsa 
> gives:
> -8<-----------------
>     echo "Loading ALSA mixer settings:  /usr/sbin/alsactl restore"
>       echo "Setting default ALSA mixer settings."
>       echo "Storing default ALSA mixer settings:  /usr/sbin/alsactl store"
>     echo "Loading OSS compatibility modules for ALSA."
>     echo "Loading ALSA kernel modules."
> -8<-----------------

> None of those messages will be seen by dmesg or in any log file.

Very true.  If you want to see those in the logs after the fact, you'd
need to change your rc files to call 'logger' instead of echo.  Of
course, you need to make sure that syslogd is up before you start
calling 'logger' with those messages.

[toc] | [prev] | [standalone]

Back to top | Article view | alt.os.linux.slackware

csiph-web