Re: [zd1211-devs] zd1211rw problems, bit rate, icwonfig

2006-12-16 Thread Henrik Hjelte
On Sat, 2006-12-16 at 10:35 -0500, William Keaney wrote:
 What distribution are you using?  
It's ubuntu, recently upgraded to feisty to get kernel 2.6.19-7

 Some of the configuration methods you mentioned are unfamiliar to me. 
To me to. I usually do what Googling tells me. There seems to be many
ways to configure the kernel modules in ubuntu, most of debian
heritage. 

  I use wpa_supplicant for mine, and am able to associate with WEP and
 WPA2/tkip/PEAP networks without hassle.
I'll try this

/Henrik Hjelte

 
 On 12/16/06, Henrik Hjelte [EMAIL PROTECTED] wrote:
 Thanks,
 it works now!
 I had to set the essid with sudo iwconfig set essid
 MyWlanName.
 Then do a sudo dhclient to get a dhcp connection.
 Perhaps not surprising, but:
 
 Previously this was made automatically by a configuration
 option 
 wireless-essid in /etc/network/interfaces, but it doesn't seem
 to have
 an effect with the zd1211rw driver. Also I have specified
 iface eth1 inet dhcp, but that doesn't seem to do it.
 
 Also I have problems with starting the driver automatically at
 startup. 
 I've put zd1211rw last in /etc/modules. I have to unplug the
 usb stick
 before rebooting, and plug it in again after Linux has loaded,
 else it
 fails: USB control request for firmware upload failed. Error
 number
 -110. I suspect this has to do with zd1211rw being loaded too
 early in
 the process, but I don't know to fix it. What is the proper
 way to load
 the modules, is /etc/modules the right thing?
 
 But the driver seems to work fine! 
 Don't know how formal tests are required, but I suggest adding
 {USB_DEVICE(0x13b1, 0x0024), .driver_info = DEVICE_ZD1211B}
 to zd_usb.c
 
 
 /Henrik Hjelte
 
 
 
 
 On Fri, 2006-12-15 at 22:57 -0500, William Keaney wrote: 
  Mine does this when it has not associated properly with the
 AP.
  Notice that the output if 'iwconfig' says Access Point:
 Invalid.
  Are you using encryption on your AP?  I find that 'iwconfig
 eth1 enc 
  open' usually fixes the problem.  Failing that, make sure it
 is using
  the correct key.
 
  On 12/15/06, athoslnx [EMAIL PROTECTED] wrote: 
 
 
 
  Henrik Hjelte-2 wrote:
  
   I am trying to get my Linksys USB Network Adapter
 with Wi-Fi
  finder
   Linksys WUSBF54G 13b1:0024 to work with zd1211rw.
 Previously 
  I've had
   success version getting it to work with the old
 zd1211
  driver.
   I'm running Ubuntu feisty, which has kernel
 2.6.19-7.
   zd1211rw is snapshot 2006-12-14, with an edited
 zd_usb.c 
  with a new
   {USB_DEVICE(0x13b1, 0x0024), .driver_info =
 DEVICE_ZD1211B}
  
   I seem to get the usb adapter recognized, but the
 Bit Rate
  is only 1 
   Mb/s and I can't get an dhcp offer. I tried to set
 another
  bit rate with
   iwconfig (sudo iwconfig eth1 rate 11M), but it
 doesn't
  change. The
   output of iwconfig looks the same next time. 
  
   Any ideas how I can get further or what I'm doing
 wrong?
   /Henrik Hjelte
  
   dmesg:
  
   [ 1047.992000] usb 3-3: new high speed USB device
   using ehci_hcd and address 8
   [ 1048.124000] usb 3-3: configuration #1 chosen
 from 1
   choice
   [ 1048.156000] usb 3-3: firmware version 0x4810
 and
   device bootcode version 0x4802 differ
   [ 1048.264000] zd1211rw 3-3:1.0: firmware version
 4725
   [ 1048.308000] zd1211rw 3-3: 1.0: zd1211b chip
 13b1:0024
  v4802
   high00-14-bf AL2230_RF pa0 
   [ 1048.308000] zd1211rw 3-3:1.0: eth1
   [ 1048.432000] ADDRCONF(NETDEV_UP): eth1: link is
 not 
   ready
  
  
   iwconfig:
  
   eth1  IEEE
 802.11b/g  ESSID:O  Nickname:zd1211
 Mode:Managed  Frequency:2.412
 GHz  Access
   Point: Invalid
 Bit Rate=1 Mb/s
 Link 

Re: [zd1211-devs] errors make module zd1211-driver-r83

2006-12-16 Thread Harald Dunkel
athoslnx wrote:
 
 what I must make in order to repair the error?
 

Maybe you could consider to set ZDCONF_WE_STAT_SUPPORT
to 0? Worked for me (using 2.6.19.1).


Good luck

Harri
===
--- Makefile~   2006-07-09 11:59:42.0 +0200
+++ Makefile2006-12-16 19:14:55.0 +0100
@@ -55,7 +55,7 @@

 EXTRA_CFLAGS += -O2 -Wall -Wstrict-prototypes -pipe
 #EXTRA_CFLAGS += -Wa,-a,-ad -g
-EXTRA_CFLAGS += -DZDCONF_WE_STAT_SUPPORT=1
+EXTRA_CFLAGS += -DZDCONF_WE_STAT_SUPPORT=0
 EXTRA_CFLAGS += -DHOST_IF_USB
 EXTRA_CFLAGS += -DAMAC
 EXTRA_CFLAGS += -DGCCK
@@ -171,7 +171,7 @@
 CFLAGS += -D__SMP__ -DSMP
 endif

-CFLAGS += -DZDCONF_WE_STAT_SUPPORT=1
+CFLAGS += -DZDCONF_WE_STAT_SUPPORT=0
 CFLAGS += -DHOST_IF_USB
 CFLAGS += -DAMAC
 CFLAGS += -DGCCK




signature.asc
Description: OpenPGP digital signature
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Zd1211-devs mailing list - http://zd1211.ath.cx/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

Re: [zd1211-devs] Kernel OOPS in 2.6.20-rc1 with zd1211rw (possibly ieee80211softmac?)

2006-12-16 Thread Ulrich Kunitz
On 06-12-15 16:39 Chris wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Hi there,
 
 I'll apologise now, this is the first kernel-related issue i've ever
 experienced, so I may be doing this wrong or missing something :).
 
 I recently downloaded and compiled 2.6.20-rc1 and set it up nicely with
 my zd1211 card (Addon ADD-GWU180) and now the kernel oops's on boot in
 normal mode, or when issuing iwconfig eth1 essid essid_name in
 recovery mode. From the information it spews out at the time, it looks
 like possibly a ieee80211softmac issue, but it doesn't happen with an
 rt2570 card, and I thought it best to check with you first.
 
 Hopefully all the information you need is included below, if not, i'll
 be happy to provide anything else you need.
 
 Thanks in advance.

This is a bug resulting from the changes in the API. I have fixed
that last Sunday.

Here is the patch:

[PATCH] ieee80211softmac: Fix direct calls to ieee80211softmac_assoc_work

The signature of work functions changed recently from a context
pointer to the work structure pointer. This caused a problem in
the ieee80211softmac code, because the work function has  been
called directly with a parameter explicitly casted to (void*).
This compiled correctly but resulted in a softlock, because the
mutex_lock has been executed at the wrong memory address. The
patch fixes the problem. Softmac works again.

Signed-off-by: Ulrich Kunitz [EMAIL PROTECTED]
---
 net/ieee80211/softmac/ieee80211softmac_assoc.c |6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/net/ieee80211/softmac/ieee80211softmac_assoc.c 
b/net/ieee80211/softmac/ieee80211softmac_assoc.c
index eec1a1d..a824852 100644
--- a/net/ieee80211/softmac/ieee80211softmac_assoc.c
+++ b/net/ieee80211/softmac/ieee80211softmac_assoc.c
@@ -167,7 +167,7 @@ static void
 ieee80211softmac_assoc_notify_scan(struct net_device *dev, int event_type, 
void *context)
 {
struct ieee80211softmac_device *mac = ieee80211_priv(dev);
-   ieee80211softmac_assoc_work((void*)mac);
+   ieee80211softmac_assoc_work(mac-associnfo.work.work);
 }
 
 static void
@@ -177,7 +177,7 @@ ieee80211softmac_assoc_notify_auth(struc
 
switch (event_type) {
case IEEE80211SOFTMAC_EVENT_AUTHENTICATED:
-   ieee80211softmac_assoc_work((void*)mac);
+   ieee80211softmac_assoc_work(mac-associnfo.work.work);
break;
case IEEE80211SOFTMAC_EVENT_AUTH_FAILED:
case IEEE80211SOFTMAC_EVENT_AUTH_TIMEOUT:
@@ -438,7 +438,7 @@ ieee80211softmac_try_reassoc(struct ieee
 
spin_lock_irqsave(mac-lock, flags);
mac-associnfo.associating = 1;
-   schedule_work(mac-associnfo.work);
+   schedule_delayed_work(mac-associnfo.work, 0);
spin_unlock_irqrestore(mac-lock, flags);
 }
 
-- 
1.4.1

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Zd1211-devs mailing list - http://zd1211.ath.cx/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs


Re: [zd1211-devs] wireless-dev dont connect

2006-12-16 Thread Ulrich Kunitz
On 06-12-16 00:57 Fernando Toledo wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Hi all,
 i play with wireless-dev and wireless-2.6 git's (to make to work my
 onboard bcm43xx)
 in these kernels
 i cant connect with my zd1211 to the ap's
 i can scan and see the ap, the log say associted but i do not get the ip
 from my dhcp (also i test to put a fixed address)
 
 i dont have this problem on 2.6.19 (vanilla) from kernel.org
 
 when iwlist scann or ifconfig up :
 
 zd1211rw 2-6:1.0: zd_chip_unlock_phy_regs() CR_REG1: 0x20 - 0xa0
 SoftMAC: sent association request!
 SoftMAC: associated!
 zd1211rw 2-6:1.0: housekeeping_disable()
 zd1211rw 2-6:1.0: zd_chip_lock_phy_regs() CR_REG1: 0xa0 - 0x20
 zd1211rw 2-6:1.0: zd_chip_unlock_phy_regs() CR_REG1: 0x20 - 0xa0

Something shuts the interface down after being associated. No wonder that you 
get no IP over DHCP. This is certainly a configuration problem.

Regards,

Uli

-- 
Uli Kunitz

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Zd1211-devs mailing list - http://zd1211.ath.cx/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs