On 12/19/06, Daniel Drake [EMAIL PROTECTED] wrote:
Jon Smirl wrote:
ifup eth1
[ 1457.671472] SoftMAC: Associate: Scanning for networks first.
[ 1457.671487] SoftMAC: Associate: failed to initiate scan. Is device up?
You have some configuration agent running which is screwing things up.
Jon Smirl wrote:
It looks to me like Ubuntu told the interface to initialize and then
told it to associate before the initialization was complete.
No - your trace clearly shows that it is setting security keys and
trying to associate *before* the interface is brought up.
Daniel
On 12/19/06, Daniel Drake [EMAIL PROTECTED] wrote:
Jon Smirl wrote:
I disabled auto start in /etc/network/interfaces
/etc/network/interface is an Ubuntu thing, you want to completely
disable whatever is using it.
Now I type ifup eth1 and get this trace.
Your trace shows that something
On 12/19/06, Jon Smirl [EMAIL PROTECTED] wrote:
On 12/19/06, Daniel Drake [EMAIL PROTECTED] wrote:
Jon Smirl wrote:
It looks to me like Ubuntu told the interface to initialize and then
told it to associate before the initialization was complete.
No - your trace clearly shows that it
On Sun, 2006-12-17 at 18:31 -0500, Jon Smirl wrote:
Linus git kernel, 2.6.20-rc1+
patched softmac for work queue changes
Ubuntu Edgy
WEP encryption
ifup eth1
Won't start the network, if I look in dmesg
ADDRCONF(NETDEV_UP): eth1: link is not ready
ifup will timeout after a while because
Is this a problem with Ubuntu not setting the essid when the interface
first comes up? Or is it a problem with the driver not performing the
first setting of the essid correctly?
Other than this issue everything seems to be working for me.
On 12/18/06, Henrik Hjelte [EMAIL PROTECTED] wrote:
On
I am using different hardware but that doesn't seem to be the problem.
zd1211rw 5-3:1.0: firmware version 4721
zd1211rw 5-3:1.0: zd1211b chip 0ace:1215 v4810 high 00-02-72 AL2230_RF pa0 g--N
--
Jon Smirl
[EMAIL PROTECTED]
I turned up debug in the zd1211rw driver and can see what the problem
is. Tomorrow I'll see if I can learn enough about the driver to fix
it. The problem has nothing to do with setting an essid, that just
happens to be a way to recover from it.
modprobe the driver in.
[ 1850.103620] zd1211rw
