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

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

No sound

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

Contents

  No sound Rodolfo Medina <rodolfo.medina@gmail.com> - 2017-02-28 16:30 +0100
    Re: No sound Hans <hans.ullrich@loop.de> - 2017-02-28 18:40 +0100
      Re: No sound Jude DaShiell <jdashiel@panix.com> - 2017-02-28 19:00 +0100
        Re: No sound darkestkhan <darkestkhan@gmail.com> - 2017-02-28 19:10 +0100
    Re: No sound David Christensen <dpchrist@holgerdanske.com> - 2017-02-28 18:50 +0100
    Re: No sound Jude DaShiell <jdashiel@panix.com> - 2017-02-28 18:50 +0100
    Re: No sound deloptes <deloptes@gmail.com> - 2017-02-28 19:40 +0100
      Re: No sound Darac Marjal <mailinglist@darac.org.uk> - 2017-03-01 11:50 +0100
        Re: No sound deloptes <deloptes@gmail.com> - 2017-03-01 17:50 +0100
    [solved] Re: No sound Rodolfo Medina <rodolfo.medina@gmail.com> - 2017-02-28 21:30 +0100
      Re: [solved] Re: No sound deloptes <deloptes@gmail.com> - 2017-02-28 22:30 +0100
      Re: [solved] Re: No sound GiaThnYgeia <GiaThnYgeia@openmailbox.org> - 2017-02-28 23:20 +0100
        Re: [solved] Re: No sound deloptes <deloptes@gmail.com> - 2017-02-28 23:40 +0100
          No sound-inputs but sound recording FMIT GiaThnYgeia <GiaThnYgeia@openmailbox.org> - 2017-03-03 02:00 +0100
            Re: No sound-inputs but sound recording FMIT deloptes <deloptes@gmail.com> - 2017-03-03 12:00 +0100
              Re: No sound-inputs but sound recording FMIT The Wanderer <wanderer@fastmail.fm> - 2017-03-03 13:20 +0100
                Re: No sound-inputs but sound recording FMIT Greg Wooledge <wooledg@eeg.ccf.org> - 2017-03-03 14:20 +0100
                  Re: No sound-inputs but sound recording FMIT The Wanderer <wanderer@fastmail.fm> - 2017-03-03 14:50 +0100
                    Re: No sound-inputs but sound recording FMIT deloptes <deloptes@gmail.com> - 2017-03-03 20:50 +0100
                      Re: No sound-inputs but sound recording FMIT The Wanderer <wanderer@fastmail.fm> - 2017-03-03 21:00 +0100
                        Re: No sound-inputs but sound recording FMIT GiaThnYgeia <GiaThnYgeia@openmailbox.org> - 2017-03-04 12:30 +0100
                          Re: No sound-inputs but sound recording FMIT <tomas@tuxteam.de> - 2017-03-04 16:10 +0100
                        Re: No sound-inputs but sound recording FMIT rhkramer@gmail.com - 2017-03-04 14:40 +0100
                  Re: No sound-inputs but sound recording FMIT Frank <zuiderduin@gmx.com> - 2017-03-03 15:00 +0100
    Re: No sound Cindy-Sue Causey <butterflybytes@gmail.com> - 2017-02-28 22:50 +0100
      Re: No sound deloptes <deloptes@gmail.com> - 2017-02-28 23:30 +0100

Page 1 of 2  [1] 2  Next page →

#178273 — No sound

Please help with no sound issue.  I installed the following packages:

 alsa-oss alsa-tools alsa-tools-gui alsa-utils alsamixergui gstreamer1.0-alsa
 libalsaplayer0 libasound2 libasound2-data libasound2-dev libasound2-plugins
 libsox-fmt-alsa python-alsaaudio

, then ran alsamixer and unmuted all volumes, but still:

$ mplayer *
MPlayer 1.3.0 (Debian), built with gcc-6.2.1 (C) 2000-2016 MPlayer Team
do_connect: could not connect to socket
connect: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

Playing 21-apr-2011.flv.
libavformat version 57.56.101 (external)
Mismatching header version 57.56.100
libavformat file format detected.
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f4b77ce5d00]Protocol name not provided, cannot determine if input is local or a network protocol, buffers and access patterns cannot be configured optimally without knowing the protocol
[lavf] stream 0: video (h264), -vid 0
[lavf] stream 1: audio (aac), -aid 0, -alang und
VIDEO:  [H264]  400x300  24bpp  30.000 fps  512.0 kbps (62.5 kbyte/s)
==========================================================================
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
libavcodec version 57.64.101 (external)
Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
==========================================================================
Clip info:
 major_brand: FACE
 minor_version: 1337
 compatible_brands: isomavc1FACE
 creation_time: 2011-04-21T22:58:18.000000Z
Load subtitles in ./
==========================================================================
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 22050 Hz, 1 ch, floatle, 36.8 kbit/5.21% (ratio: 4596->88200)
Selected audio codec: [ffaac] afm: ffmpeg (FFmpeg AAC (MPEG-2/MPEG-4 Audio))
==========================================================================
AO: [pulse] Init failed: Connection refused
Failed to initialize audio driver 'pulse'
[AO_ALSA] alsa-lib: pcm_hw.c:1602:(snd_pcm_hw_open) open '/dev/snd/pcmC0D0p' failed (-2): No such file or directory
[AO_ALSA] alsa-lib: pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave
[AO_ALSA] Playback open error: No such file or directory
Failed to initialize audio driver 'alsa'
[AO SDL] Samplerate: 22050Hz Channels: Mono Format floatle
[AO SDL] using aalib audio driver.
[AO SDL] Unsupported audio format: 0x1d.
[AO SDL] Unable to open audio: No available audio device
Failed to initialize audio driver 'sdl:aalib'
Could not open/initialize audio device -> no sound.
Audio: no sound
Starting playback...
Movie-Aspect is undefined - no prescaling applied.
VO: [vdpau] 400x300 => 400x300 Planar YV12 
V:   2.7   0/  0  9%  3%  0.0% 0 0 

Exiting... (Quit)


Thanks for any help,

Rodolfo

[toc] | [next] | [standalone]

#178277

Am Dienstag, 28. Februar 2017, 15:27:46 CET schrieb Rodolfo Medina:
Hi Rodolfo, 

I am not sure, but it looks like you need pulseaudio for sound. Did you 
install the pulseaudio package?

Pulseaudio is the next generation audiodriver and uses alsa as well.

Hope it helps. Good luck!

Hans
> Please help with no sound issue.  I installed the following packages:
> 
>  alsa-oss alsa-tools alsa-tools-gui alsa-utils alsamixergui
> gstreamer1.0-alsa libalsaplayer0 libasound2 libasound2-data libasound2-dev
> libasound2-plugins libsox-fmt-alsa python-alsaaudio
> 
> , then ran alsamixer and unmuted all volumes, but still:
> 
> $ mplayer *
> MPlayer 1.3.0 (Debian), built with gcc-6.2.1 (C) 2000-2016 MPlayer Team
> do_connect: could not connect to socket
> connect: No such file or directory
> Failed to open LIRC support. You will not be able to use your remote
> control.
> 
> Playing 21-apr-2011.flv.
> libavformat version 57.56.101 (external)
> Mismatching header version 57.56.100
> libavformat file format detected.
> [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f4b77ce5d00]Protocol name not provided, cannot
> determine if input is local or a network protocol, buffers and access
> patterns cannot be configured optimally without knowing the protocol [lavf]
> stream 0: video (h264), -vid 0
> [lavf] stream 1: audio (aac), -aid 0, -alang und
> VIDEO:  [H264]  400x300  24bpp  30.000 fps  512.0 kbps (62.5 kbyte/s)
> ==========================================================================
> Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
> libavcodec version 57.64.101 (external)
> Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
> ==========================================================================
> Clip info:
>  major_brand: FACE
>  minor_version: 1337
>  compatible_brands: isomavc1FACE
>  creation_time: 2011-04-21T22:58:18.000000Z
> Load subtitles in ./
> ==========================================================================
> Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
> AUDIO: 22050 Hz, 1 ch, floatle, 36.8 kbit/5.21% (ratio: 4596->88200)
> Selected audio codec: [ffaac] afm: ffmpeg (FFmpeg AAC (MPEG-2/MPEG-4 Audio))
> ==========================================================================
> AO: [pulse] Init failed: Connection refused
> Failed to initialize audio driver 'pulse'
> [AO_ALSA] alsa-lib: pcm_hw.c:1602:(snd_pcm_hw_open) open '/dev/snd/pcmC0D0p'
> failed (-2): No such file or directory [AO_ALSA] alsa-lib:
> pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave [AO_ALSA] Playback
> open error: No such file or directory
> Failed to initialize audio driver 'alsa'
> [AO SDL] Samplerate: 22050Hz Channels: Mono Format floatle
> [AO SDL] using aalib audio driver.
> [AO SDL] Unsupported audio format: 0x1d.
> [AO SDL] Unable to open audio: No available audio device
> Failed to initialize audio driver 'sdl:aalib'
> Could not open/initialize audio device -> no sound.
> Audio: no sound
> Starting playback...
> Movie-Aspect is undefined - no prescaling applied.
> VO: [vdpau] 400x300 => 400x300 Planar YV12
> V:   2.7   0/  0  9%  3%  0.0% 0 0
> 
> Exiting... (Quit)
> 
> 
> Thanks for any help,
> 
> Rodolfo

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

#178285

Pulseaudio is needed for sound to the same level as a fish needs a 
bicycle.On Tue, 28 Feb 2017, Hans wrote:

> Date: Tue, 28 Feb 2017 12:32:30
> From: Hans <hans.ullrich@loop.de>
> To: debian-user@lists.debian.org
> Subject: Re: No sound
> Resent-Date: Tue, 28 Feb 2017 17:32:56 +0000 (UTC)
> Resent-From: debian-user@lists.debian.org
> 
> Am Dienstag, 28. Februar 2017, 15:27:46 CET schrieb Rodolfo Medina:
> Hi Rodolfo,
>
> I am not sure, but it looks like you need pulseaudio for sound. Did you
> install the pulseaudio package?
>
> Pulseaudio is the next generation audiodriver and uses alsa as well.
>
> Hope it helps. Good luck!
>
> Hans
>> Please help with no sound issue.  I installed the following packages:
>>
>>  alsa-oss alsa-tools alsa-tools-gui alsa-utils alsamixergui
>> gstreamer1.0-alsa libalsaplayer0 libasound2 libasound2-data libasound2-dev
>> libasound2-plugins libsox-fmt-alsa python-alsaaudio
>>
>> , then ran alsamixer and unmuted all volumes, but still:
>>
>> $ mplayer *
>> MPlayer 1.3.0 (Debian), built with gcc-6.2.1 (C) 2000-2016 MPlayer Team
>> do_connect: could not connect to socket
>> connect: No such file or directory
>> Failed to open LIRC support. You will not be able to use your remote
>> control.
>>
>> Playing 21-apr-2011.flv.
>> libavformat version 57.56.101 (external)
>> Mismatching header version 57.56.100
>> libavformat file format detected.
>> [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f4b77ce5d00]Protocol name not provided, cannot
>> determine if input is local or a network protocol, buffers and access
>> patterns cannot be configured optimally without knowing the protocol [lavf]
>> stream 0: video (h264), -vid 0
>> [lavf] stream 1: audio (aac), -aid 0, -alang und
>> VIDEO:  [H264]  400x300  24bpp  30.000 fps  512.0 kbps (62.5 kbyte/s)
>> ==========================================================================
>> Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
>> libavcodec version 57.64.101 (external)
>> Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
>> ==========================================================================
>> Clip info:
>>  major_brand: FACE
>>  minor_version: 1337
>>  compatible_brands: isomavc1FACE
>>  creation_time: 2011-04-21T22:58:18.000000Z
>> Load subtitles in ./
>> ==========================================================================
>> Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
>> AUDIO: 22050 Hz, 1 ch, floatle, 36.8 kbit/5.21% (ratio: 4596->88200)
>> Selected audio codec: [ffaac] afm: ffmpeg (FFmpeg AAC (MPEG-2/MPEG-4 Audio))
>> ==========================================================================
>> AO: [pulse] Init failed: Connection refused
>> Failed to initialize audio driver 'pulse'
>> [AO_ALSA] alsa-lib: pcm_hw.c:1602:(snd_pcm_hw_open) open '/dev/snd/pcmC0D0p'
>> failed (-2): No such file or directory [AO_ALSA] alsa-lib:
>> pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave [AO_ALSA] Playback
>> open error: No such file or directory
>> Failed to initialize audio driver 'alsa'
>> [AO SDL] Samplerate: 22050Hz Channels: Mono Format floatle
>> [AO SDL] using aalib audio driver.
>> [AO SDL] Unsupported audio format: 0x1d.
>> [AO SDL] Unable to open audio: No available audio device
>> Failed to initialize audio driver 'sdl:aalib'
>> Could not open/initialize audio device -> no sound.
>> Audio: no sound
>> Starting playback...
>> Movie-Aspect is undefined - no prescaling applied.
>> VO: [vdpau] 400x300 => 400x300 Planar YV12
>> V:   2.7   0/  0  9%  3%  0.0% 0 0
>>
>> Exiting... (Quit)
>>
>>
>> Thanks for any help,
>>
>> Rodolfo
>
>
>

-- 

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

#178287

99% of my sound issues are resolved by:

sudo aptitude purge pulseaudio

(the remaining 1% tends to be some do-once-and-forget-forever-tweak in
alsa config files)

On Tue, Feb 28, 2017 at 5:51 PM, Jude DaShiell <jdashiel@panix.com> wrote:
> Pulseaudio is needed for sound to the same level as a fish needs a
> bicycle.On Tue, 28 Feb 2017, Hans wrote:
>
>> Date: Tue, 28 Feb 2017 12:32:30
>> From: Hans <hans.ullrich@loop.de>
>> To: debian-user@lists.debian.org
>> Subject: Re: No sound
>> Resent-Date: Tue, 28 Feb 2017 17:32:56 +0000 (UTC)
>> Resent-From: debian-user@lists.debian.org
>>
>>
>> Am Dienstag, 28. Februar 2017, 15:27:46 CET schrieb Rodolfo Medina:
>> Hi Rodolfo,
>>
>> I am not sure, but it looks like you need pulseaudio for sound. Did you
>> install the pulseaudio package?
>>
>> Pulseaudio is the next generation audiodriver and uses alsa as well.
>>
>> Hope it helps. Good luck!
>>
>> Hans
>>>
>>> Please help with no sound issue.  I installed the following packages:
>>>
>>>  alsa-oss alsa-tools alsa-tools-gui alsa-utils alsamixergui
>>> gstreamer1.0-alsa libalsaplayer0 libasound2 libasound2-data
>>> libasound2-dev
>>> libasound2-plugins libsox-fmt-alsa python-alsaaudio
>>>
>>> , then ran alsamixer and unmuted all volumes, but still:
>>>
>>> $ mplayer *
>>> MPlayer 1.3.0 (Debian), built with gcc-6.2.1 (C) 2000-2016 MPlayer Team
>>> do_connect: could not connect to socket
>>> connect: No such file or directory
>>> Failed to open LIRC support. You will not be able to use your remote
>>> control.
>>>
>>> Playing 21-apr-2011.flv.
>>> libavformat version 57.56.101 (external)
>>> Mismatching header version 57.56.100
>>> libavformat file format detected.
>>> [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f4b77ce5d00]Protocol name not provided,
>>> cannot
>>> determine if input is local or a network protocol, buffers and access
>>> patterns cannot be configured optimally without knowing the protocol
>>> [lavf]
>>> stream 0: video (h264), -vid 0
>>> [lavf] stream 1: audio (aac), -aid 0, -alang und
>>> VIDEO:  [H264]  400x300  24bpp  30.000 fps  512.0 kbps (62.5 kbyte/s)
>>>
>>> ==========================================================================
>>> Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
>>> libavcodec version 57.64.101 (external)
>>> Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
>>>
>>> ==========================================================================
>>> Clip info:
>>>  major_brand: FACE
>>>  minor_version: 1337
>>>  compatible_brands: isomavc1FACE
>>>  creation_time: 2011-04-21T22:58:18.000000Z
>>> Load subtitles in ./
>>>
>>> ==========================================================================
>>> Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
>>> AUDIO: 22050 Hz, 1 ch, floatle, 36.8 kbit/5.21% (ratio: 4596->88200)
>>> Selected audio codec: [ffaac] afm: ffmpeg (FFmpeg AAC (MPEG-2/MPEG-4
>>> Audio))
>>>
>>> ==========================================================================
>>> AO: [pulse] Init failed: Connection refused
>>> Failed to initialize audio driver 'pulse'
>>> [AO_ALSA] alsa-lib: pcm_hw.c:1602:(snd_pcm_hw_open) open
>>> '/dev/snd/pcmC0D0p'
>>> failed (-2): No such file or directory [AO_ALSA] alsa-lib:
>>> pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave [AO_ALSA]
>>> Playback
>>> open error: No such file or directory
>>> Failed to initialize audio driver 'alsa'
>>> [AO SDL] Samplerate: 22050Hz Channels: Mono Format floatle
>>> [AO SDL] using aalib audio driver.
>>> [AO SDL] Unsupported audio format: 0x1d.
>>> [AO SDL] Unable to open audio: No available audio device
>>> Failed to initialize audio driver 'sdl:aalib'
>>> Could not open/initialize audio device -> no sound.
>>> Audio: no sound
>>> Starting playback...
>>> Movie-Aspect is undefined - no prescaling applied.
>>> VO: [vdpau] 400x300 => 400x300 Planar YV12
>>> V:   2.7   0/  0  9%  3%  0.0% 0 0
>>>
>>> Exiting... (Quit)
>>>
>>>
>>> Thanks for any help,
>>>
>>> Rodolfo
>>
>>
>>
>>
>
> --
>



-- 

darkestkhan
------------------------------------------
Feel free to CC me.
jid: darkestkhan@gmail.com
May The Source be with You.

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

#178279

On 02/28/2017 07:27 AM, Rodolfo Medina wrote:
> Please help with no sound issue.

What release of Debian?  What kernel?

2017-02-28 08:03:16 dpchrist@jesse ~
$ cat /etc/debian_version; uname -a
8.7
Linux jesse 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u1 (2017-02-22) 
x86_64 GNU/Linux


David

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

#178282

Have you got pulseaudio installed?  If so, see if you can find 
pulsemixer and run pulsemixer and repeat your work then everything 
should be sounding.  If that's not the case, you may need to do aplay -l 
and check devices one at a time with speaker-test.   Hope this helps.

On Tue, 28 Feb 2017, Rodolfo Medina wrote:

> Date: Tue, 28 Feb 2017 10:27:46
> From: Rodolfo Medina <rodolfo.medina@gmail.com>
> To: debian-user@lists.debian.org
> Subject: No sound
> Resent-Date: Tue, 28 Feb 2017 15:28:14 +0000 (UTC)
> Resent-From: debian-user@lists.debian.org
> 
> Please help with no sound issue.  I installed the following packages:
>
> alsa-oss alsa-tools alsa-tools-gui alsa-utils alsamixergui gstreamer1.0-alsa
> libalsaplayer0 libasound2 libasound2-data libasound2-dev libasound2-plugins
> libsox-fmt-alsa python-alsaaudio
>
> , then ran alsamixer and unmuted all volumes, but still:
>
> $ mplayer *
> MPlayer 1.3.0 (Debian), built with gcc-6.2.1 (C) 2000-2016 MPlayer Team
> do_connect: could not connect to socket
> connect: No such file or directory
> Failed to open LIRC support. You will not be able to use your remote control.
>
> Playing 21-apr-2011.flv.
> libavformat version 57.56.101 (external)
> Mismatching header version 57.56.100
> libavformat file format detected.
> [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f4b77ce5d00]Protocol name not provided, cannot determine if input is local or a network protocol, buffers and access patterns cannot be configured optimally without knowing the protocol
> [lavf] stream 0: video (h264), -vid 0
> [lavf] stream 1: audio (aac), -aid 0, -alang und
> VIDEO:  [H264]  400x300  24bpp  30.000 fps  512.0 kbps (62.5 kbyte/s)
> ==========================================================================
> Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
> libavcodec version 57.64.101 (external)
> Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
> ==========================================================================
> Clip info:
> major_brand: FACE
> minor_version: 1337
> compatible_brands: isomavc1FACE
> creation_time: 2011-04-21T22:58:18.000000Z
> Load subtitles in ./
> ==========================================================================
> Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
> AUDIO: 22050 Hz, 1 ch, floatle, 36.8 kbit/5.21% (ratio: 4596->88200)
> Selected audio codec: [ffaac] afm: ffmpeg (FFmpeg AAC (MPEG-2/MPEG-4 Audio))
> ==========================================================================
> AO: [pulse] Init failed: Connection refused
> Failed to initialize audio driver 'pulse'
> [AO_ALSA] alsa-lib: pcm_hw.c:1602:(snd_pcm_hw_open) open '/dev/snd/pcmC0D0p' failed (-2): No such file or directory
> [AO_ALSA] alsa-lib: pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave
> [AO_ALSA] Playback open error: No such file or directory
> Failed to initialize audio driver 'alsa'
> [AO SDL] Samplerate: 22050Hz Channels: Mono Format floatle
> [AO SDL] using aalib audio driver.
> [AO SDL] Unsupported audio format: 0x1d.
> [AO SDL] Unable to open audio: No available audio device
> Failed to initialize audio driver 'sdl:aalib'
> Could not open/initialize audio device -> no sound.
> Audio: no sound
> Starting playback...
> Movie-Aspect is undefined - no prescaling applied.
> VO: [vdpau] 400x300 => 400x300 Planar YV12
> V:   2.7   0/  0  9%  3%  0.0% 0 0
>
> Exiting... (Quit)
>
>
> Thanks for any help,
>
> Rodolfo
>
>

-- 

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

#178289

Rodolfo Medina wrote:

> [AO_ALSA] alsa-lib: pcm_hw.c:1602:(snd_pcm_hw_open) open
> ['/dev/snd/pcmC0D0p' failed (-2): No such file or directory

As no one answered with a meaningful suggestion. The problem is as you see
above that alsa can not locate your hardware (audio card)

you need to debug this first

regards

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

#178311

On Tue, Feb 28, 2017 at 07:32:29PM +0100, deloptes wrote:
>Rodolfo Medina wrote:
>
>> [AO_ALSA] alsa-lib: pcm_hw.c:1602:(snd_pcm_hw_open) open
>> ['/dev/snd/pcmC0D0p' failed (-2): No such file or directory
>
>As no one answered with a meaningful suggestion. The problem is as you see
>above that alsa can not locate your hardware (audio card)

Actually, the fact that the OP was able to adjust the volumes in 
alsamixer suggests that ALSA *can* find the card, but mplayer *can't*.  
This is probably just a matter of defining the default card properly.

>
>you need to debug this first
>
>regards
>

-- 
For more information, please reread.

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

#178329

Darac Marjal wrote:

> Actually, the fact that the OP was able to adjust the volumes in
> alsamixer suggests that ALSA can find the card, but mplayer *can't*.
> This is probably just a matter of defining the default card properly.

/dev/snd/pcmC0D0p missing - what default card?

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

#178292 — [solved] Re: No sound

Rodolfo Medina <rodolfo.medina@gmail.com> writes:

> Please help with no sound issue.  I installed the following packages:
>
>  alsa-oss alsa-tools alsa-tools-gui alsa-utils alsamixergui gstreamer1.0-alsa
>  libalsaplayer0 libasound2 libasound2-data libasound2-dev libasound2-plugins
>  libsox-fmt-alsa python-alsaaudio
>
> , then ran alsamixer and unmuted all volumes, but still:


I installed alsaplayer-alsa and pulseaudio and now I have sound, I don't know
thanks to which of the two.

$ cat /etc/debian_version; uname -a
9.0
Linux lenovo 4.9.0-2-amd64 #1 SMP Debian 4.9.10-1 (2017-02-17) x86_64 GNU/Linux

Cheers,

Rodolfo

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

#178296 — Re: [solved] Re: No sound

Rodolfo Medina wrote:

> I installed alsaplayer-alsa and pulseaudio and now I have sound, I don't
> know thanks to which of the two.

the dependencies (libasound2 libasound2-data) I guess. But most likely it
triggered a proper configuration of your driver

regards

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

#178299 — Re: [solved] Re: No sound

Rodolfo Medina:
> Rodolfo Medina <rodolfo.medina@gmail.com> writes:
> I installed alsaplayer-alsa and pulseaudio and now I have sound, I don't know
> thanks to which of the two.
> 
> $ cat /etc/debian_version; uname -a
> 9.0
> Linux lenovo 4.9.0-2-amd64 #1 SMP Debian 4.9.10-1 (2017-02-17) x86_64 GNU/Linux
9.0
Linux DellUziOn 4.9.0-1-amd64 #1 SMP Debian 4.9.6-3 (2017-01-20) x86_64
GNU/Linux

How does one trace the inputs of the audio system?  Basic hardware
configuration only shows usual mic input, but using FMT for example
after mic gets unplugged some sound input is getting recorded.  Banging
on the box records well.  None of the hardware specs I've found list any
other device.  Could the mini-speaker-beeper on the board act as a mic?
Why would audio software be allowed to use a speaker as a mic?

> Cheers,
> Rodolfo

Peace and quiet

-- 
 "The most violent element in society is ignorance" rEG

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

#178302 — Re: [solved] Re: No sound

GiaThnYgeia wrote:

> How does one trace the inputs of the audio system?  Basic hardware
> configuration only shows usual mic input, but using FMT for example
> after mic gets unplugged some sound input is getting recorded.  Banging
> on the box records well.  None of the hardware specs I've found list any
> other device.  Could the mini-speaker-beeper on the board act as a mic?
> Why would audio software be allowed to use a speaker as a mic?

don't hijack please. open new thread

show us your hardware and other useful info. may be you have built in mic?

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

#178355 — No sound-inputs but sound recording FMIT

OK, I did some testing on an other machine with a testing installation,
downloaded FMIT (an instrument tuner that will pickup audio inpur/analog
and tell you all kinds of stuff about the wave that is fed).
Same exact behavior, hardware only lists two audio inputs and are both
unplugged.  The lower the db threshold for sound recording the more
apparent the sound becomes.  Each nock on the box shows corresponding
amplification of that noise.

Ok, so I picked up 2-3 live debian based USB sticks I have.  I plugged
then in to 3 different machines, downloaded FMIT and run it.  Similar
results.  So it has nothing to do with my configuration of stuff.  I say
if some software is picking up sound from your environment and records
it when no inputs are plugged in I would call this a "security" issue
not a malfunction.

It probably has nothing to do with the program itself but its
dependencies and some code feeding in wrong data as audio input.  But it
is actual sound


-------- Forwarded Message --------
Subject: Re: [solved] Re: No sound
Resent-Date: Tue, 28 Feb 2017 22:30:30 +0000 (UTC)
Resent-From: debian-user@lists.debian.org
Date: Tue, 28 Feb 2017 23:27:17 +0100
From: deloptes <deloptes@gmail.com>
Reply-To: deloptes@gmail.com
To: debian-user@lists.debian.org

GiaThnYgeia wrote:

> How does one trace the inputs of the audio system?  Basic hardware
> configuration only shows usual mic input, but using FMT for example
> after mic gets unplugged some sound input is getting recorded.  Banging
> on the box records well.  None of the hardware specs I've found list any
> other device.  Could the mini-speaker-beeper on the board act as a mic?
> Why would audio software be allowed to use a speaker as a mic?

don't hijack please. open new thread

show us your hardware and other useful info. may be you have built in mic?

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

#178360 — Re: No sound-inputs but sound recording FMIT

GiaThnYgeia wrote:

> It probably has nothing to do with the program itself but its
> dependencies and some code feeding in wrong data as audio input.  But it
> is actual sound

you have to provide information so that it may be reproduced. Please open
another thread. The information you provided so far is a user story and
does not help further.

regards

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

#178362 — Re: No sound-inputs but sound recording FMIT

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

On 2017-03-03 at 05:46, deloptes wrote:

> GiaThnYgeia wrote:
> 
>> It probably has nothing to do with the program itself but its 
>> dependencies and some code feeding in wrong data as audio input.
>> But it is actual sound
> 
> you have to provide information so that it may be reproduced. Please
> open another thread. The information you provided so far is a user
> story and does not help further.

To clarify this, since many people in the modern era apparently don't
realize it:

Changing the Subject line on a reply E-mail does not make that E-mail be
the first mail in a new thread. (Although some E-mail clients, such as
Outlook, will probably display it as if it was.)

In order to start a new thread, you have to create the E-mail from
scratch, e.g. by using a "New Mail" button or the equivalent. Creating
an E-mail by replying to an existing message puts the new message into
an existing thread, even if the Subject line is changed.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

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

#178364 — Re: No sound-inputs but sound recording FMIT

On Fri, Mar 03, 2017 at 07:13:37AM -0500, The Wanderer wrote:
> In order to start a new thread, you have to create the E-mail from
> scratch, e.g. by using a "New Mail" button or the equivalent. Creating
> an E-mail by replying to an existing message puts the new message into
> an existing thread, even if the Subject line is changed.

Or manually remove the In-Reply-To: header, if your mail user agent
permits you to do this.

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

#178365 — Re: No sound-inputs but sound recording FMIT

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

On 2017-03-03 at 08:15, Greg Wooledge wrote:

> On Fri, Mar 03, 2017 at 07:13:37AM -0500, The Wanderer wrote:
> 
>> In order to start a new thread, you have to create the E-mail from
>> scratch, e.g. by using a "New Mail" button or the equivalent.
>> Creating an E-mail by replying to an existing message puts the new
>> message into an existing thread, even if the Subject line is
>> changed.
> 
> Or manually remove the In-Reply-To: header, if your mail user agent
> permits you to do this.

True, although someone who doesn't know that hitting Reply on an
existing message threads the reply in under the existing message is
unlikely to even know what message headers are, much less know how to do
this. (Or be using a mail client which does permit that.)

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

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

#178378 — Re: No sound-inputs but sound recording FMIT

The Wanderer wrote:

> True, although someone who doesn't know that hitting Reply on an
> existing message threads the reply in under the existing message is
> unlikely to even know what message headers are, much less know how to do
> this. (Or be using a mail client which does permit that.)

But why would you do this. You could simply press new and start a thread
with your question

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

#178380 — Re: No sound-inputs but sound recording FMIT

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

On 2017-03-03 at 14:35, deloptes wrote:

> The Wanderer wrote:
> 
>> True, although someone who doesn't know that hitting Reply on an 
>> existing message threads the reply in under the existing message
>> is unlikely to even know what message headers are, much less know
>> how to do this. (Or be using a mail client which does permit
>> that.)
> 
> But why would you do this. You could simply press new and start a
> thread with your question

Because hitting New means you have to put in the To address, but hitting
Reply means the address is already there and you can just start typing
your message (and possibly delete the quoted text, change the Subject
line, et cetera).

Yes, this apparently is enough of a convenience factor to affect
people's behavior.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

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

Page 1 of 2  [1] 2  Next page →

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

csiph-web