[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Linksys USB200M adapter failing under wicd



>Peter Crawford wrote:
>> Date: Thu, 27 Aug 2009 20:12:28 +0200
>> From: thveillon.debian@googlemail.com
>> To: debian-user@lists.debian.org
>> Subject: Re: Linksys USB200M adapter failing under wicd
> 
>> for wicd to work you need an empty /etc/network/interfaces file (except lo).
> 
> Yes; as specified in http://wiki.debian.org/WiFi/HowToUse#OtherGUI
> and my original message.
> 
>> Then in wicd preferences you can choose to (or not):
> 
> Well, the phenomenon is observed as the 
> system reaches the console in multi-user mode.
> No GUI is running yet.
OK
> 
>> Connection profiles are kept under
>> /etc/wicd/wire[d][less]-settings.conf, modify at will.
> 
> Yes, /etc/wicd/wired-settings.conf is adapted to the 
> static parameters which work properly when using 
> /etc/network/interfaces .
> 
>> But anyhow remember wicd is just a gui, 
> 
> Also a daemon.  Ref. wicd.man.
> "STRUCTURE
>        Wicd  has two major parts: the daemon, which runs with root 
>        privileges; and the user interface, which runs with normal  
>        user  privileges.   The two  parts  run as separate processes 
>        and make use of D-Bus to communicate."
Yes, what I meant is if the interface isn't properly supported, wicd
won't make it work. But in your case it seems fully functional.

Since the last update on Squeeze I use the "ioctl" backend, the
"external" default one was becoming really slow, sometimes not
connecting at all. But the three computers I use wicd on at the moment
are all wireless.

> 
>> your hardware need to be fully
>> recognized first (does it shows up with "ifconfig -a" ?).
> 
> Yes.  ifconfig reports both lo and eth2.  But eth2 does 
> not have the address & etc. specified in wired-settings.conf.
> 
> The machine has no wireless device attached.
> When eth2 is not configured according to /etc/network/interfaces, 
> wicd should configure according to the default in 
> /etc/wicd/wired-settings.conf ... shouldn't it?

It definitely should ;-)
Maybe this:
"Using wired interface...eth2
No previous wired profile available, wired autoconnect failed."

relates to the default "lastused = True" in wired-settings.conf, if
there is no "lastused" settings it fails instead of using default
profile (would look like a bug...). Did you try setting it to False ?

Puzzled Tom.


Reply to: