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

Groups > linux.debian.user > #201025 > unrolled thread

something wrong with audio

Back to article view | Back to linux.debian.user

Contents

  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

Page 1 of 2  [1] 2  Next page →

#201025 — something wrong with audio

[Multipart message — attachments visible in raw view] — view raw

Sorry for the subject not-so-specific but I hope this message can start a
first iteration to better focus my problem.

The problem in short: no sound card available to pulsaudio, while ALSA
seems to correctly detect HDA Intel PCH.
To make the problem more puzzling, in the same laptop with an ubuntu live
(with kernel 4.15) audio works correctly.

This means that the soundcard IS supported in some way (though I don't know
the ubuntu way). Tried to test if the cause is kernel regression: installed
kernel 4.15 (from debian snapshot), but the song remains the same (in this
case the song is the sound of silence).

This drives me crazy.

I'm ready to perform any diagnostics/tests you could imagine to get my
audio back.

Below I report the info on hardware and kernel.

Please help!!!

-- hardware: Lenovo Thinkpad X270;
-- soundcard (from lspci) 00:1f.3 Audio device: Intel Corporation Sunrise
Point-LP HD Audio (rev 21)
-- debian_version: sid
-- kernel: 4.18.0-2-amd64
-- kernel modules ( lsmod | grep snd)
snd_hrtimer            16384  1
snd_seq_midi           16384  0
snd_seq_midi_event     16384  1 snd_seq_midi
snd_rawmidi            40960  1 snd_seq_midi
snd_seq                81920  3 snd_seq_midi,snd_seq_midi_event
snd_seq_device         16384  3 snd_seq,snd_seq_midi,snd_rawmidi
snd_hda_codec_hdmi     61440  1
snd_hda_codec_realtek   110592  1
snd_hda_codec_generic    86016  1 snd_hda_codec_realtek
snd_soc_skl           118784  0
snd_soc_skl_ipc        73728  1 snd_soc_skl
snd_soc_sst_ipc        16384  1 snd_soc_skl_ipc
snd_soc_sst_dsp        36864  1 snd_soc_skl_ipc
snd_hda_ext_core       28672  1 snd_soc_skl
snd_soc_acpi           16384  1 snd_soc_skl
snd_soc_core          253952  1 snd_soc_skl
snd_compress           24576  1 snd_soc_core
snd_hda_intel          45056  3
snd_hda_codec         151552  4
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
snd_hda_core           94208  7
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek,snd_soc_skl
snd_hwdep              20480  1 snd_hda_codec
snd_pcm_oss            61440  0
snd_mixer_oss          28672  1 snd_pcm_oss
snd_pcm               118784  9
snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_pcm_oss,snd_soc_core,snd_soc_skl,snd_hda_core
snd_timer              36864  4 snd_seq,snd_hrtimer,snd_pcm
snd                    94208  21
snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_compress,snd_pcm_oss,thinkpad_acpi,snd_soc_core,snd_pcm,snd_rawmidi,snd_mixer_oss
soundcore              16384  1 snd

alsamixer see teo sound cards:
-- default (pulseaudio)
-- HDA Intel PCH
for this second card (when selected with F6), alsamixer displays a list
(relatively rich) of audio I/O controls

HOWEVER, pulsaudio only sees a (useless) dummy output, saying "no cards
available for configuration" in the Configuration tab.

[toc] | [next] | [standalone]

#201026

Hi,

You did verify that your sound is NOT muted in some gui or alsamixer,
didn't you ?

Steve

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

#201030

steve wrote:

> Hi,
> 
> You did verify that your sound is NOT muted in some gui or alsamixer,
> didn't you ?

removing the .pulse or .config/pulse directory followed by reboot, could
also help in similar cases

regards

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

#201033

[Multipart message — attachments visible in raw view] — view raw

On Mon, Oct 8, 2018 at 8:27 PM deloptes <deloptes@gmail.com> wrote:

> removing the .pulse or .config/pulse directory followed by reboot, could
> also help in similar cases
>
>
So sad! It didn't work. :(

Thank you anyway
a.

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

#201034

[Multipart message — attachments visible in raw view] — view raw

On Mon, Oct 8, 2018 at 7:16 PM steve <dlist@bluewin.ch> wrote:

>
> You did verify that your sound is NOT muted in some gui or alsamixer,
> didn't you ?
>
>
Thank you Steve fr your quick reply.

As I tried to explain (maybe not clearly enough, I'm sorry), pulse just
doesn't see any card at all.
In any case, following your suggestion I verified that alsamixer displays
non muted channels.

Thank you again.
Alberto

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

#201035

On Monday 08 October 2018 14:42:19 dotdeb@gmail.com wrote:

> On Mon, Oct 8, 2018 at 7:16 PM Jude DaShiell <jdashiel@panix.com> 
wrote:
> > Did you install the intel microcode package yet?  This may solve the
> > problem or may not.  Failing that, try an install of the debian
> > firmware
>
> Jude, it is very sad (for me, of course) to tell you that the intel
> microcode was already installed.
>
> Thank you anyway,
> alberto

But, does dmesg report its successful use at the last boot?

-- 
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>

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

#201037

[Multipart message — attachments visible in raw view] — view raw

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?
Alberto

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

#201038

On Monday 08 October 2018 14:52:28 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?
> Alberto

Yes and no. wheres the first 11 ports, it should be starting at port0.  
Odd...



-- 
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>

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

#201066

[Multipart message — attachments visible in raw view] — view raw

I replied to gheskett@shentel.net instead of sending the following to the
list.
Sorry.
a.

---------- Forwarded message ---------
From: <dotdeb@gmail.com>
Date: Tue, Oct 9, 2018 at 10:03 AM
Subject: Re: something wrong with audio
To: <gheskett@shentel.net>


On Mon, Oct 8, 2018 at 8:59 PM Gene Heskett <gheskett@shentel.net> wrote:

>
> Yes and no. wheres the first 11 ports, it should be starting at port0.
> Odd...
>
>
Looks like all the inputs are there: they are "system" inputs, not only for
audio device.

sudo dmesg | grep devices | grep input

[    1.465137] input: AT Translated Set 2 keyboard as
/devices/platform/i8042/serio0/input/input0
[    2.689597] input: SynPS/2 Synaptics TouchPad as
/devices/platform/i8042/serio1/input/input2
[    3.506497] input: TPPS/2 IBM TrackPoint as
/devices/platform/i8042/serio1/serio2/input/input3
[    3.545724] input: Sleep Button as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input4
[    3.547624] input: Lid Switch as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input5
[    3.548364] input: Power Button as
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6
[    3.640229] input: ThinkPad Extra Buttons as
/devices/platform/thinkpad_acpi/input/input7
[    3.708335] input: PC Speaker as /devices/platform/pcspkr/input/input8
[    3.812271] input: Video Bus as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input9
[    3.958218] input: HDA Digital PCBeep as
/devices/pci0000:00/0000:00:1f.3/sound/card0/input10
[    3.958608] input: HDA Intel PCH Mic as
/devices/pci0000:00/0000:00:1f.3/sound/card0/input11
[    3.958662] input: HDA Intel PCH Dock Mic as
/devices/pci0000:00/0000:00:1f.3/sound/card0/input12
[    3.958714] input: HDA Intel PCH Dock Headphone as
/devices/pci0000:00/0000:00:1f.3/sound/card0/input13
[    3.958765] input: HDA Intel PCH Headphone as
/devices/pci0000:00/0000:00:1f.3/sound/card0/input14
[    3.958818] input: HDA Intel PCH HDMI/DP,pcm=3 as
/devices/pci0000:00/0000:00:1f.3/sound/card0/input15
[    3.958868] input: HDA Intel PCH HDMI/DP,pcm=7 as
/devices/pci0000:00/0000:00:1f.3/sound/card0/input16
[    3.958917] input: HDA Intel PCH HDMI/DP,pcm=8 as
/devices/pci0000:00/0000:00:1f.3/sound/card0/input17
[    3.958965] input: HDA Intel PCH HDMI/DP,pcm=9 as
/devices/pci0000:00/0000:00:1f.3/sound/card0/input18
[    3.959020] input: HDA Intel PCH HDMI/DP,pcm=10 as
/devices/pci0000:00/0000:00:1f.3/sound/card0/input19
[    5.110165] input: Integrated Camera: Integrated C as
/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8:1.0/input/input20

Alberto

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

#201046

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.

Cheers,
David.

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

#201051

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>

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

#201036

[Multipart message — attachments visible in raw view] — view raw

On Mon, Oct 8, 2018 at 7:16 PM Jude DaShiell <jdashiel@panix.com> wrote:

> Did you install the intel microcode package yet?  This may solve the
> problem or may not.  Failing that, try an install of the debian firmware
>
>
Jude, it is very sad (for me, of course) to tell you that the intel
microcode was already installed.

Thank you anyway,
alberto

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

#201043

[Multipart message — attachments visible in raw view] — view raw

On Mon, Oct 8, 2018 at 12:09 PM <dotdeb@gmail.com> wrote:

> Sorry for the subject not-so-specific but I hope this message can start a
> first iteration to better focus my problem.
>
>
Sounds roughly similar to a problem I've been having. I tracked it down to
Timidity grabbing the sound card. I don't know enough to make it fixed
permanently, but as a temporary fix after a reboot when the problem
manifests, I do a

ps ax | grep timidity

and then kill the Timidity process. Then my sound card gets recognized, and
I have audio until my next reboot.

-- 
Kent West                    <")))><
Westing Peacefully - http://kentwest.blogspot.com

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

#201047

On Mon 08 Oct 2018 at 14:34:26 (-0500), Kent West wrote:
> On Mon, Oct 8, 2018 at 12:09 PM <dotdeb@gmail.com> wrote:
> 
> > Sorry for the subject not-so-specific but I hope this message can start a
> > first iteration to better focus my problem.
> >
> >
> Sounds roughly similar to a problem I've been having. I tracked it down to
> Timidity grabbing the sound card. I don't know enough to make it fixed
> permanently, but as a temporary fix after a reboot when the problem
> manifests, I do a
> 
> ps ax | grep timidity
> 
> and then kill the Timidity process. Then my sound card gets recognized, and
> I have audio until my next reboot.

I'm listening to a youtube video as I write this. Meanwhile:

 $ ps ax | grep -i 'timid\|mplay'
  743 ?        S      0:00 /usr/bin/timidity -Os -iAD
25430 pts/8    RLl+   2:19 mplayer -nojoystick -fs -zoom Met Opera & CAI Present Verdi's Aida  - 6th October 2018-qRQKuNcm0u4.mp4
25835 pts/14   S+     0:00 grep -i timid\|mplay
$ 

Cheers,
David.

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

#201068

[Multipart message — attachments visible in raw view] — view raw

On Mon, Oct 8, 2018 at 9:35 PM Kent West <westk@acu.edu> wrote:

>
> Sounds roughly similar to a problem I've been having. I tracked it down to
> Timidity grabbing the sound card. I don't know enough to make it fixed
> permanently, but as a temporary fix after a reboot when the problem
> manifests, I do a
>
> ps ax | grep timidity
>
> and then kill the Timidity process. Then my sound card gets recognized,
> and I have audio until my next reboot.
>
>
>
Well, no. Timidity is not running.
Thank you anyway.
a.

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

#201075

[Multipart message — attachments visible in raw view] — view raw

On Mon, Oct 8, 2018 at 7:08 PM <dotdeb@gmail.com> wrote:

> Sorry for the subject not-so-specific but I hope this message can start a
> first iteration to better focus my problem.
>
> The problem in short: no sound card available to pulsaudio, while ALSA
> seems to correctly detect HDA Intel PCH.
> To make the problem more puzzling, in the same laptop with an ubuntu live
> (with kernel 4.15) audio works correctly.
>
>
Dear all, I have some upgrade (that partly solved the problem):

1. if I do not login as user into a desktop environment (in other words, if
pulseaudio is not started) ALSA works correctly.
As I said in my first post, the strange stuff is that pulse does not see
any card and fallback to a "dummy" sink, while alsa looks OK.

2. in a small partition I installed debian/stable and then dist-upgrade to
sid to see how a fresh install behaves: everything is fine (both alsa and
pulse).
This makes me think of some bad interaction with other packages OR
configuration problems.
Actually, my sid have been alive for long time (years), and maybe some
wrong (legacy) file under /etc can be there and cause problems.

This does not add very much to understanding the problem, but I think that
working with unstable and keeping /etc for a long time, may generate some
inconsistency that cannot be considered real bugs or misbehaviuor.

Conclusion: I consider the problem solved (or better, a "non-problem").
Because I spent too much time on it, I'll give it up andl use the newly
installed and working debian/sid, transferring configuration step by step
and verify that sound continue working.

Thank you to you all for the very kind help.

Alberto

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

#201097

dotdeb@gmail.com wrote:

> Conclusion: I consider the problem solved (or better, a "non-problem").
> Because I spent too much time on it, I'll give it up andl use the newly
> installed and working debian/sid, transferring configuration step by step
> and verify that sound continue working.
> 

What Sid?
if you are not able to debug, why use sid? ... ok this is your choice, but
you also complain ... if I knew it is sid, I wouldnot spend a second.

There are instructions on how to debug pulse audio. There are also couple of
commands that help you understand what is going on.

regards

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

#201076

On 2018-10-08, dotdeb@gmail.com <dotdeb@gmail.com> wrote:
>
> The problem in short: no sound card available to pulsaudio, while ALSA
> seems to correctly detect HDA Intel PCH.
> To make the problem more puzzling, in the same laptop with an ubuntu live
> (with kernel 4.15) audio works correctly.
>

On the archlinux sound troubleshooting wiki ("The only device
shown is 'dummy output'..." section), they suggest
executing

  fuser -v /dev/snd/*

"to see which application is responsible for a direct access to the
sound card via alsa," and then perhaps closing that or those apps in
order to give pulseaudio precedence.

https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#The_only_device_shown_is_.22dummy_output.22_or_newly_connected_cards_are_not_detected

Maybe worth a shot.

-- 
"Now she understood that Anna could not have been in lilac, and that her charm
was just that she always stood out against her attire, that her dress could
never be noticeable on her." Leo Tolstoy, Anna Karenina 

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

#201077

[Multipart message — attachments visible in raw view] — view raw

On Tue, Oct 9, 2018 at 2:02 PM Curt <curty@free.fr> wrote:

> On the archlinux sound troubleshooting wiki ("The only device
> shown is 'dummy output'..." section), they suggest
> executing
>
>   fuser -v /dev/snd/*
>
>
Thank you for the hint. I never came across that link.
Unfortunately, I tried and it seems that no application is using /dev/dsp.

Thank you anyway.
Alberto

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

#201079

On 2018-10-09, dotdeb@gmail.com <dotdeb@gmail.com> wrote:
>
> On Tue, Oct 9, 2018 at 2:02 PM Curt <curty@free.fr> wrote:
>
>> On the archlinux sound troubleshooting wiki ("The only device
>> shown is 'dummy output'..." section), they suggest
>> executing
>>
>>   fuser -v /dev/snd/*
>>
>>
> Thank you for the hint. I never came across that link.
> Unfortunately, I tried and it seems that no application is using /dev/dsp.

Actually that would be '/dev/snd*' not '/dev/dsp' (the latter being the
old, obsolete oss sound device from way back when, which I doubt would
exist on Stretch at all).



> Thank you anyway.
> Alberto
>

-- 
"Now she understood that Anna could not have been in lilac, and that her charm
was just that she always stood out against her attire, that her dress could
never be noticeable on her." Leo Tolstoy, Anna Karenina 

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

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web