Re: "alsaconf" successful. No sound!

Felix Karpfen wrote: I have "discover1" installed and would need more guidance before I had discover1 (1.7.$something), too, and got some problems with the sound: it didn't work, no sound from any programs but without errors. I had to run manually alsaconf everytime to make it work, and in t

Re: "alsaconf" successful. No sound!

On Tue, 07 Mar 2006 20:22:55 -0800, Mark Fletcher wrote (<[EMAIL PROTECTED]>): > > > --- Scott <[EMAIL PROTECTED]> wrote: > >> Francesco Bochicchio spake thusly on 03/07/2006 >> 02:54 PM: >> > Il Tue, 07 Mar 2006 21:50:14 +0100, Felix Karpfen >> ha scritto: >> >> >> >> However when checking th

Re: "alsaconf" successful. No sound!

On 3/9/06, Jon Dowland <[EMAIL PROTECTED]> wrote: > At 1141796294, Scott wrote: > > Well just because many aren't happy with the default muted setting in > > ALSA doesn't mean we'd prefer full-blast either. And just for > > clarification, this isn't a Debian issue. It's an ALSA issue. The > > sa

Re: "alsaconf" successful. No sound!

At 1141796294, Scott wrote: > Well just because many aren't happy with the default muted setting in > ALSA doesn't mean we'd prefer full-blast either. And just for > clarification, this isn't a Debian issue. It's an ALSA issue. The > same problem persists on other distros as well (I can speak >

Re: "alsaconf" successful. No sound!

On Wed, 08 Mar 2006 05:38:14 -0700 Scott <[EMAIL PROTECTED]> wrote: > > What would make sense is for a very low volume level for the default. > Just so you know the thing is working. Not to mention I've4 never been > alble figure out what specific controls (among the 20 or so) that I need >

Re: "alsaconf" successful. No sound!

On Wed, 8 Mar 2006 09:51:08 -0500 [EMAIL PROTECTED] wrote: > On Wed, Mar 08, 2006 at 05:40:12AM -0700, Scott wrote: > > > > Exactly. The first time I came across this I'd just naturally assumed > > something was *wrong* and spend several hours doing needless tweaking > > and researching only t

Re: "alsaconf" successful. No sound!

On Wed, Mar 08, 2006 at 05:40:12AM -0700, Scott wrote: > > Exactly. The first time I came across this I'd just naturally assumed > something was *wrong* and spend several hours doing needless tweaking > and researching only to find the volume was all the way down. I've > never seen this in W

Re: "alsaconf" successful. No sound!

Angelina Carlton spake thusly on 03/07/2006 07:34 PM: Bruno Buys <[EMAIL PROTECTED]> writes: I've always wondered what genius thought that default setting was a good idea.. It is indeed a good idea. It can prevent any non desired sound/music/popup-msg to wreak havoc into your speakers,

Re: "alsaconf" successful. No sound!

Bruno Buys spake thusly on 03/07/2006 04:52 PM: Scott wrote: Francesco Bochicchio spake thusly on 03/07/2006 02:54 PM: Il Tue, 07 Mar 2006 21:50:14 +0100, Felix Karpfen ha scritto: I ran "alsaconf" on my recently-updated Debian 3.1r1. It worked like a charm and ended with the following mes

Re: "alsaconf" successful. No sound!

At 1141803015, Felix Karpfen wrote: > I ran "alsaconf" on my recently-updated Debian 3.1r1. ... > However when checking the output of a .wav file by running > the "play" command from a console, I get a deafening > silence. What card? I recently discovered I had to turn off some channels for the m

Re: "alsaconf" successful. No sound!

You might be missing discover? http://packages.debian.org/unstable/sound/alsa-base kai Felix Karpfen wrote: What have I missed? Prior to the update (when using the Sarge pre-release) sound worked OK. Felix Karpfen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "u

Re: "alsaconf" successful. No sound!

--- Scott <[EMAIL PROTECTED]> wrote: > Francesco Bochicchio spake thusly on 03/07/2006 > 02:54 PM: > > Il Tue, 07 Mar 2006 21:50:14 +0100, Felix Karpfen > ha scritto: > > > >> I ran "alsaconf" on my recently-updated Debian > 3.1r1. > >> > >> It worked like a charm and ended with the > followin

Re: "alsaconf" successful. No sound!

Bruno Buys <[EMAIL PROTECTED]> writes: >> I've always wondered what genius thought that default setting was a >> good idea.. >> > It is indeed a good idea. It can prevent any non desired > sound/music/popup-msg to wreak havoc into your speakers, say, when you > load a livecd or something. Lik

Re: "alsaconf" successful. No sound!

Scott wrote: Francesco Bochicchio spake thusly on 03/07/2006 02:54 PM: Il Tue, 07 Mar 2006 21:50:14 +0100, Felix Karpfen ha scritto: I ran "alsaconf" on my recently-updated Debian 3.1r1. It worked like a charm and ended with the following messages: Running update-modules... Loading driver.

Re: "alsaconf" successful. No sound!

Francesco Bochicchio spake thusly on 03/07/2006 02:54 PM: Il Tue, 07 Mar 2006 21:50:14 +0100, Felix Karpfen ha scritto: I ran "alsaconf" on my recently-updated Debian 3.1r1. It worked like a charm and ended with the following messages: Running update-modules... Loading driver... Setting defau

Re: "alsaconf" successful. No sound!

On Wed, 08 Mar 2006 07:30:15 +1100 Felix Karpfen <[EMAIL PROTECTED]> wrote: > I ran "alsaconf" on my recently-updated Debian 3.1r1. > > It worked like a charm and ended with the following messages: hmmm... apparently not after all... > > Running update-modules... > Loading driver... > Setting

Re: "alsaconf" successful. No sound!

Il Tue, 07 Mar 2006 21:50:14 +0100, Felix Karpfen ha scritto: > I ran "alsaconf" on my recently-updated Debian 3.1r1. > > It worked like a charm and ended with the following messages: > > Running update-modules... > Loading driver... > Setting default volumes... > > > =

"alsaconf" successful. No sound!

I ran "alsaconf" on my recently-updated Debian 3.1r1. It worked like a charm and ended with the following messages: Running update-modules... Loading driver... Setting default volumes... === Now ALSA is ready to use.