On 12/10/18 1:25 AM, Joel Roth via Dng wrote:
> [...]
> One other good idea is this: alsactl init
> The command will put your soundcard in a usable
> state.
>
> As exemplified here:
>
>
https://unix.stackexchange.com/questions/15765/why-do-i-have-to-run-alsactl-init-each-time-i-boot-my-system
On Sun, Dec 09, 2018 at 01:25:05PM -1000, Joel Roth via Dng wrote:
> One other good idea is this: alsactl init
> The command will put your soundcard in a usable
> state.
Just a note on this: I use alsactl regularly to modify my alsa sound
settings when I switch to headphones for voip calls.
So I
On Mon, Dec 10, 2018 at 10:17:25AM +0200, Lars Noodén via Dng wrote:
>
>
> On 12/10/18 1:25 AM, Joel Roth via Dng wrote:
> > [...]
> > One other good idea is this: alsactl init
> > The command will put your soundcard in a usable
> > state.
> >
> > As exemplified here:
> >
> >
>
Le 07/12/2018 à 12:45, Michael K. a écrit :
¡Ola!
After a Dev1 Setup on a Laptop (whit eth0), i have to wait a long time
for the eth0 on "cold boot".
I "cold boot" my Laptop
I look to the "Boot Messages"
I see the following Msg:
Configuring Network Interfaces ifup: Waiting for Lock on
