On Mon, 13 Aug 2007 07:50:44 +0200, Uli Kunitz wrote:
> cat /proc/version
> and could you send us the relevant output of /var/log/kern.log or dmesg.
I've repeated the process with a debug kernel and debugging zd1211rw
driver. Here is the output of /var/log/debug . I've left it completely
intact--page down to see the zd1211rw related material.
Starting at 56.765446 is a long series of `iwconfig eth0 essid off`.
After each successive one I would check the output of `iwconfig`. The
first time the essid was set to the only available AP in the area. The
next four or five `iwconfig eth0 essid off` resulted in the essid being
unchanged. The next after that successfully set the essid to "any/off"
but the connection was still successfully negotiated and the network was
available for use. I can't say exactly how many more after that but, at
one point, the result of `iwconfig eth0 essid off` set the essid (as
reported by iwconfig) to an AP which I have used before but is definitely
not reachable from within this building. Unless there was a stray beacon
which just happened to bounce around the walls Just Right then I have no
idea how it could've come up with that essid.
That's the output while running "1217432 Aug 15 10:57 vmlinuz-2.6.23-
rc3-070815-vnlla-dbg". I forgot to capture the actual /proc/version on
that boot. Here's /proc/version now (same gcc and Debian version that
was used to build the debug kernel this morning):
Linux version 2.6.23-rc2-070812-vanilla ([EMAIL PROTECTED]) (gcc version
4.1.3 20070718 (prerelease) (Debian 4.1.2-14)) #1 Sun Aug 12 15:41:11 PDT
I'm not familiar with the particulars but, every so often, I see
interrupt failures reported for usb 1-1. Could this be a problem with
UHCI and not zd1211rw?
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/