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

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

Re: No sound

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

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: No sound David Wright <deblis@lionunicorn.co.uk> - 2019-05-12 19:40 +0200
    Re: No sound Kaj Persson <kape_fsp@telia.com> - 2019-05-14 17:50 +0200

#208602 — Re: No sound

On Sun 12 May 2019 at 13:08:33 (+0200), 70147persson@telia.com wrote:

> Inxi is telling that the sound card, Device-1, is Intel 82801I HD Audio, and the driver: snd_hda_intel.

This raises the question of what device 0 is, and whether the sound
is being routed there.

As a non-DE non-pulse user, I would run alsamixer, press F6 and
select the device 1. Then work my way along the bars, raising
levels with the arrows and unmuting with the M key.

As some applications have their own volume controls that may or
may not work, speaker-test is a useful command for a source.

Cheers,
David.

[toc] | [next] | [standalone]

#208642

Den 2019-05-12 kl. 19:30, skrev David Wright:
> On Sun 12 May 2019 at 13:08:33 (+0200), 70147persson@telia.com wrote:
>
>> Inxi is telling that the sound card, Device-1, is Intel 82801I HD Audio, and the driver: snd_hda_intel.
> This raises the question of what device 0 is, and whether the sound
> is being routed there.
>
> As a non-DE non-pulse user, I would run alsamixer, press F6 and
> select the device 1. Then work my way along the bars, raising
> levels with the arrows and unmuting with the M key.
>
> As some applications have their own volume controls that may or
> may not work, speaker-test is a useful command for a source.
>
> Cheers,
> David.
>
>
Well David, I did not describe the content of the link, but in short one 
creates as Device-0, a virtual device called Loopback, which does what 
its name is saying, it loops back to jack what was transferred to 
Device-0, the default device. So programmes not adapted to run jack, 
gets its signal connected to jack and handled by this.

OK, this is how I have understood it, my knowledge is not deep enough to 
exactly see what happens. Someone better skilled could perhaps give a 
better explanation.

By using mate-volume-control I could see that this Loopback was created 
as the default Device-0. The card itself "HDA Intel" is there too.

Kaj

[toc] | [prev] | [standalone]

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

csiph-web