netdev
[Top] [All Lists]

RE: ipw2100: firmware problem

To: abonilla@xxxxxxxxxxxxxxxxx
Subject: RE: ipw2100: firmware problem
From: Lee Revell <rlrevell@xxxxxxxxxxx>
Date: Fri, 10 Jun 2005 16:26:27 -0400
Cc: "'Denis Vlasenko'" <vda@xxxxxxxxxxxxx>, "'Pavel Machek'" <pavel@xxxxxx>, "'Jeff Garzik'" <jgarzik@xxxxxxxxx>, "'Netdev list'" <netdev@xxxxxxxxxxx>, "'kernel list'" <linux-kernel@xxxxxxxxxxxxxxx>, "'James P. Ketrenos'" <ipw2100-admin@xxxxxxxxxxxxxxx>
In-reply-to: <000f01c56dbf$9b15de90$600cc60a@xxxxxxxxxxxxxx>
References: <000f01c56dbf$9b15de90$600cc60a@xxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On Fri, 2005-06-10 at 07:23 -0600, Alejandro Bonilla wrote:
> >
> > Adding kernel level wireless autoconfiguration duplicates the effort.
> > Since I am not going to give up a requirement to be able to stay radio
> > silent at boot (me too wants freedom, not only you), you need to add
> > disable=1 module parameter to each driver, which adds to the mess.
> >
> > ALSA does the Right Thing. Sound is completely muted out at
> > module load.
> > It's a user freedom to set desired volume level after that.
> 
> Yeah right. I remember I had to google for 10 minutes to find the answer for
> this one. Why would you install something, for it to not work?
> 
> It thing of Mute in ALSA is stupid. If you want Sound, you install the Sound
> and enable it. Why would it make you google for more things to do? ALSA mute
> on install is WAY way, not OK.

It took you 10 minutes of googling before you thought to try the mixer?
Sorry dude, this is PEBKAC.

Lee


<Prev in Thread] Current Thread [Next in Thread>