Re: Realtek 8185 chipset problem

[Paul Scott <waterhorse@ultrasw.com>]

On 01/30/2011 01:06 PM, consul tores wrote:
> 2011/1/30 Paul Scott<waterhorse@ultrasw.com>:
>    
> > On Sun, Jan 30, 2011 at 10:27:09AM +0200, Andrei Popescu wrote:
> >      
> > > On Sb, 29 ian 11, 19:02:38, Paul Scott wrote:
> > >        
> > > > > > I'm attaching a dmesg because this might help me get the Orinoco
> > > > > > Silver working again for
> > > > > > secured networks with a newer kernel.  It works fine using
> > > > > > dhclient now on unsecured
> > > > > >              
> > > > >                                          ^^^^^^^^
> > > > >                                         using what, wicd or ??
> > > > >            
> > > > With dhclient or /etc/network/interfaces.  wicd doesn't see it
> > > > either probably because of the firmware problem.
> > > >          
> > > I doubt that, a firmware problem will affect all frontends equally. You
> > > might want to check that wicd is trying to access the correct device.
> > >        
> > Could there be something else I have not installed?  I have not had this
> > problem with other installations.
> >
> > wicd.log says:
> >
> > 2011/01/22 13:34:02 :: Autoconnecting...
> > 2011/01/22 13:34:02 :: No wired connection present, attempting to autoconnect to wireless network
> > 2011/01/22 13:34:02 :: Unable to autoconnect, you'll have to manually connect
> >
> > Thanks,
> >
> > Paul
> >      
> What happend if you do:
>    

I have done these many times but I recently got and compiled a driver 
from Realtek (from Wayne's suggestion).  It isn't named rtl8185 but 
r8185b.  I thought I had tested that well enough and that it wasn't working,

> ifconfig wlanx up
> iwconfig wlanx essid "your_essid"
> dhclient wlanx
>    

These now work on my temporarily unsecured home network!

Now on to secured networks.

Thanks,

Paul