Re: [zd1211-devs] zd1211rw 2.6.23-rc2 (git)
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. http://pastebin.com/m2079365a kern.log: http://pastebin.com/m734f8cb7 dmesg: http://pastebin.com/m68fd0102 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 2007 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/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] zd1211rw 2.6.23-rc2 (git)
Steven wrote: I've noticed this behavior in the zd1211rw driver for a few months now and haven't seen anyone else mention it. I think it's odd. The system is Debian Sid with a git kernel, usually daily. When I first boot and plug in the wireless usb stick Debian properly identifies it and hotplugs it. However, the usb stick will not actually associate with any given AP until I use `iwconfig eth0 essid off` at which point it will pick the first AP with which it can negotiate a connection with. Subsequent `iwconfig eth0 essid off` will toggle the essid (and related AP) between off/any and the target essid. This is where things become hazy. If, instead of `iwconfig eth0 essid off` I used `iwconfig eth0 essid ap_essid` the `iwconfig` output will change to reflect the desired essid (and related AP) but the wireless connection will still not be negotiated until `iwconfig eth0 essid off`. Well, sometimes it will--about one in ten tries. This leads me to, most often, need to do the following: On one tty (or screen), `ifdown eth0 ifup eth0` and then, while dhclient is trying to find a connection, `iwconfig eth0 essid off` on another tty (or screen). This is using an AirLink 101, firmware version 4605, zd1211 chip 0ace:1211 v4330 full 00-11-a3 AL2230_RF pa0 Steven, I have seen the later mail and starting now to see your problem. It seems that you can get associated if you are not giving the essidi (off), but you have trouble with the initial setup. I have not a lot of experience with Debians init scripts and WLAN installation, but there have been reports that they doesn't work well with WLAN adapters. I know this a poor situation, but currently we cannot do a lot about it. For the softmac driver I'm always recommending to set all the necessary parameters before you call ifconfig eth0 up and I believe this is the problem with the default debian configuration. ifconfig eth0 up means in the WLAN code that the device should start to associate and this requires the parameters to be set beforehand. Kind regards, Ulrich -- Uli Kunitz - 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/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] zd1211rw 2.6.23-rc2 (git)
On Wed, 15 Aug 2007 23:34:32 +0200, Ulrich Kunitz wrote: For the softmac driver I'm always recommending to set all the necessary parameters before you call ifconfig eth0 up and I believe this is the problem with the default debian configuration. ifconfig eth0 up means in the WLAN code that the device should start to associate and this requires the parameters to be set beforehand. This makes sense. Before Debian had a wireless infrastructure that's exactly what I did. How long do you expect before mac80211 will fully replace SoftMAC in the vanilla kernel tree? I have the mac80211 kernel tree but haven't been able to try it yet. - 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/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] zd1211rw 2.6.23-rc2 (git)
I hope I've made the correct decision not to have the PAN editor automatically wrap lines. On Mon, 13 Aug 2007 07:50:44 +0200, Uli Kunitz wrote: could you please provide the output of: cat /proc/version /proc/version: 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 2007 and could you send us the relevant output of /var/log/kern.log or dmesg. dmesg: [ 41.522418] uhci_hcd :00:07.2: UHCI Host Controller [ 41.525012] uhci_hcd :00:07.2: new USB bus registered, assigned bus number 1 [ 41.527358] uhci_hcd :00:07.2: irq 11, io base 0x4000 [ 41.530533] usb usb1: configuration #1 chosen from 1 choice [ 41.533003] hub 1-0:1.0: USB hub found [ 41.535378] hub 1-0:1.0: 2 ports detected [ 41.879794] usb 1-1: new full speed USB device using uhci_hcd and address 2 [ 42.052160] usb 1-1: configuration #1 chosen from 1 choice [ 43.012361] ieee80211_crypt: registered algorithm 'NULL' [ 43.029959] ieee80211: 802.11 data/management/control stack, git-1.1.13 [ 43.032656] ieee80211: Copyright (C) 2004-2005 Intel Corporation [EMAIL PROTECTED] [ 43.211683] usb 1-1: reset full speed USB device using uhci_hcd and address 2 [ 43.339402] zd1211rw 1-1:1.0: eth0 [ 43.342473] usbcore: registered new interface driver zd1211rw [ 46.670149] zd1211rw 1-1:1.0: firmware version 4605 [ 46.706631] zd1211rw 1-1:1.0: zd1211 chip 0ace:1211 v4330 full 00-11-a3 AL2230_RF pa0 - [ 46.985900] NET: Registered protocol family 17 [ 54.594641] SoftMAC: Open Authentication completed with 00:20:a6:50:93:2b (some extraneous messages removed) Off-topic: While the USB hub detects 2 ports, I only find one on this Thinkpad 600X. The completed SoftMAC authentication is after I've logged in and issued `iwconfig eth0 essid off`, as can be seen in the syslog. kern.log looks the same as dmesg. You can see the reported behavior in syslog: Aug 13 12:15:08 celestial kernel: [ 46.670149] zd1211rw 1-1:1.0: firmware version 4605 Aug 13 12:15:08 celestial kernel: [ 46.706631] zd1211rw 1-1:1.0: zd1211 chip 0ace:1211 v4330 full 00-11-a3 AL2230_RF pa0 - Aug 13 12:15:08 celestial kernel: [ 46.985900] NET: Registered protocol family 17 Aug 13 12:15:10 celestial dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 Aug 13 12:15:18 celestial dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 Aug 13 12:15:28 celestial dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19 Aug 13 12:15:28 celestial kernel: [ 54.594641] SoftMAC: Open Authentication completed with 00:20:a6:50:93:2b Aug 13 12:15:47 celestial dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20 Aug 13 12:15:47 celestial dhclient: DHCPOFFER from 192.168.0.1 Aug 13 12:15:47 celestial dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Aug 13 12:15:47 celestial dhclient: DHCPACK from 192.168.0.1 Aug 13 12:15:48 celestial dhclient: bound to 192.168.0.65 -- renewal in 1626 seconds. (extraneous entries from avahi-daemon, cron, and others removed) At 12:15:10 the debian dhclient begins polling. Just before 12:15:28 is when I've successfully logged in and issued `iwconfig eth0 essid off`, at which point the SoftMAC authentication is completed. dhclient is then able to successfully negotiate with the access point. I'll begin building a full debug kernel with debug zd1211rw support today. This laptop is only 500 MHz. I may have debugging output available in a few hours. - 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/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
[zd1211-devs] zd1211rw 2.6.23-rc2 (git)
I've noticed this behavior in the zd1211rw driver for a few months now and haven't seen anyone else mention it. I think it's odd. The system is Debian Sid with a git kernel, usually daily. When I first boot and plug in the wireless usb stick Debian properly identifies it and hotplugs it. However, the usb stick will not actually associate with any given AP until I use `iwconfig eth0 essid off` at which point it will pick the first AP with which it can negotiate a connection with. Subsequent `iwconfig eth0 essid off` will toggle the essid (and related AP) between off/any and the target essid. This is where things become hazy. If, instead of `iwconfig eth0 essid off` I used `iwconfig eth0 essid ap_essid` the `iwconfig` output will change to reflect the desired essid (and related AP) but the wireless connection will still not be negotiated until `iwconfig eth0 essid off`. Well, sometimes it will--about one in ten tries. This leads me to, most often, need to do the following: On one tty (or screen), `ifdown eth0 ifup eth0` and then, while dhclient is trying to find a connection, `iwconfig eth0 essid off` on another tty (or screen). This is using an AirLink 101, firmware version 4605, zd1211 chip 0ace:1211 v4330 full 00-11-a3 AL2230_RF pa0 - 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/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] zd1211rw 2.6.23-rc2 (git)
Steven, could you please provide the output of: cat /proc/version and could you send us the relevant output of /var/log/kern.log or dmesg. Kind regards. Ulrich Am 12.08.2007 um 01:09 schrieb Steven: I've noticed this behavior in the zd1211rw driver for a few months now and haven't seen anyone else mention it. I think it's odd. The system is Debian Sid with a git kernel, usually daily. When I first boot and plug in the wireless usb stick Debian properly identifies it and hotplugs it. However, the usb stick will not actually associate with any given AP until I use `iwconfig eth0 essid off` at which point it will pick the first AP with which it can negotiate a connection with. Subsequent `iwconfig eth0 essid off` will toggle the essid (and related AP) between off/any and the target essid. This is where things become hazy. If, instead of `iwconfig eth0 essid off` I used `iwconfig eth0 essid ap_essid` the `iwconfig` output will change to reflect the desired essid (and related AP) but the wireless connection will still not be negotiated until `iwconfig eth0 essid off`. Well, sometimes it will--about one in ten tries. This leads me to, most often, need to do the following: On one tty (or screen), `ifdown eth0 ifup eth0` and then, while dhclient is trying to find a connection, `iwconfig eth0 essid off` on another tty (or screen). This is using an AirLink 101, firmware version 4605, zd1211 chip 0ace:1211 v4330 full 00-11-a3 AL2230_RF pa0 -- --- 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/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs -- Uli Kunitz - 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/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
