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

Groups > linux.debian.user > #201051

Re: something wrong with audio

Show all headers | View raw

On Monday 08 October 2018 15:52:08 David Wright wrote:

> On Mon 08 Oct 2018 at 20:52:28 (+0200), dotdeb@gmail.com wrote:
> > On Mon, Oct 8, 2018 at 8:48 PM Gene Heskett <gheskett@shentel.net> 
wrote:
> > > But, does dmesg report its successful use at the last boot?
> > >
> > > (dmesg | grep -i microcode)
> >
> > [    0.000000] microcode: microcode updated early to revision 0x8e,
> > date = 2018-03-24
> > [    1.472209] microcode: sig=0x806e9, pf=0x80, revision=0x8e
> > [    1.472347] microcode: Microcode Update Driver: v2.2.
> >
> > Looks like it loaded correctly
> >
> > alse had a look at "intel" in dmesg and found:
> >
> > [    3.939437] input: HDA Intel PCH Mic as
> > /devices/pci0000:00/0000:00:1f.3/sound/card0/input11
> > [    3.939489] input: HDA Intel PCH Dock Mic as
> > /devices/pci0000:00/0000:00:1f.3/sound/card0/input12
> > [    3.939537] input: HDA Intel PCH Dock Headphone as
> > /devices/pci0000:00/0000:00:1f.3/sound/card0/input13
> > [    3.939583] input: HDA Intel PCH Headphone as
> > /devices/pci0000:00/0000:00:1f.3/sound/card0/input14
> > [    3.939629] input: HDA Intel PCH HDMI/DP,pcm=3 as
> > /devices/pci0000:00/0000:00:1f.3/sound/card0/input15
> > [    3.939676] input: HDA Intel PCH HDMI/DP,pcm=7 as
> > /devices/pci0000:00/0000:00:1f.3/sound/card0/input16
> > [    3.939722] input: HDA Intel PCH HDMI/DP,pcm=8 as
> > /devices/pci0000:00/0000:00:1f.3/sound/card0/input17
> > [    3.939768] input: HDA Intel PCH HDMI/DP,pcm=9 as
> > /devices/pci0000:00/0000:00:1f.3/sound/card0/input18
> > [    3.939816] input: HDA Intel PCH HDMI/DP,pcm=10 as
> > /devices/pci0000:00/0000:00:1f.3/sound/card0/input19
> >
> > This also looks fine, didn't it?
>
> I don't know why, but ALSA seems to pick HDMI as the default card,
> whether or not anything is plugged into it.
>
> Perhaps you should run the alsa-info script from alsa-utils. That
> should tell you how to run speaker-test, also in there, to get
> some sound out.
>
> In my output, I see this fragment:
>
> !!Aplay/Arecord output
> !!--------------------
>
> APLAY
>
> **** List of PLAYBACK Hardware Devices ****
> card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> card 1: PCH [HDA Intel PCH], device 0: ALC3239 Analog [ALC3239 Analog]
>   Subdevices: 0/1
>   Subdevice #0: subdevice #0
>
> which means I can use any of:
>
> $ speaker-test -D hw:CARD=PCH,DEV=0 -c 2
> $ speaker-test -D hw:CARD=1,DEV=0 -c 2
> $ speaker-test -D hw:1,0 -c 2
> $ speaker-test -D plughw:CARD=PCH,DEV=0 -c 2
>
> to make hissing noises. Use alsamixer alongside to set the volumes,
> check mute etc. In my case,   alsamixer -c 1   starts it with the
> "rich" set of controls for the internal sound.
>
> With HDMI, I don't think the alsamixer control does much (IIRC).
> I use the volume on the TV remote to do that, after setting the
> correct HDMI source on the TV.
>
> BTW1 no pulse installed here. It's complicated enough already.
>
> BTW2 Gene, the inputs from dmesg are 8, 10 and 11. No zero.
>
They should be there someplace, but apparently your choice of drivers 
only hits the ones it can use.  Finding a full list, printing it, and 
taping it to the wall is something I've done in the distant past.  Might 
be helpfull here in the longer view.  Might have to do a bare bones boot 
to find them, possibly as another just created user.
> Cheers,
> David.



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

something wrong with audio dotdeb@gmail.com - 2018-10-08 19:10 +0200
  Re: something wrong with audio steve <dlist@bluewin.ch> - 2018-10-08 19:20 +0200
    Re: something wrong with audio deloptes <deloptes@gmail.com> - 2018-10-08 20:30 +0200
      Re: something wrong with audio dotdeb@gmail.com - 2018-10-08 20:50 +0200
    Re: something wrong with audio dotdeb@gmail.com - 2018-10-08 20:50 +0200
  Re: something wrong with audio Gene Heskett <gheskett@shentel.net> - 2018-10-08 20:50 +0200
    Re: something wrong with audio dotdeb@gmail.com - 2018-10-08 21:00 +0200
      Re: something wrong with audio Gene Heskett <gheskett@shentel.net> - 2018-10-08 21:00 +0200
        Fwd: something wrong with audio dotdeb@gmail.com - 2018-10-09 10:10 +0200
      Re: something wrong with audio David Wright <deblis@lionunicorn.co.uk> - 2018-10-08 22:00 +0200
        Re: something wrong with audio Gene Heskett <gheskett@shentel.net> - 2018-10-08 22:30 +0200
  Re: something wrong with audio dotdeb@gmail.com - 2018-10-08 20:50 +0200
  Re: something wrong with audio Kent West <westk@acu.edu> - 2018-10-08 21:40 +0200
    Re: something wrong with audio David Wright <deblis@lionunicorn.co.uk> - 2018-10-08 22:10 +0200
    Re: something wrong with audio dotdeb@gmail.com - 2018-10-09 10:20 +0200
  Re: something wrong with audio dotdeb@gmail.com - 2018-10-09 13:30 +0200
    Re: something wrong with audio deloptes <deloptes@gmail.com> - 2018-10-09 20:00 +0200
  Re: something wrong with audio Curt <curty@free.fr> - 2018-10-09 14:10 +0200
    Re: something wrong with audio dotdeb@gmail.com - 2018-10-09 14:10 +0200
      Re: something wrong with audio Curt <curty@free.fr> - 2018-10-09 14:40 +0200
        Re: something wrong with audio Michael Lange <klappnase@freenet.de> - 2018-10-10 11:20 +0200
          Re: something wrong with audio Curt <curty@free.fr> - 2018-10-10 14:10 +0200
            Re: something wrong with audio Michael Lange <klappnase@freenet.de> - 2018-10-11 01:00 +0200
              Re: something wrong with audio Curt <curty@free.fr> - 2018-10-11 10:00 +0200
          Re: something wrong with audio "Martin McCormick" <martin.m@suddenlink.net> - 2018-10-10 14:40 +0200

csiph-web