headers
Daniel Drake | 1 Dec 2006 01:46
Picon
Favicon

Re: Philips snu5600 usb dongle

unibrow wrote:
> Oh, and the reason I think it uses the AL2230_RF transmitter is because
> that's what "dmesg | grep 'zd1211b\? chip'" told me ("zd1211rw 1-5:1.0:
> zd1211b chip 0471:1236 v4810 high 00-12-bf AL2230_RF pa0 g--", to be
> precise).

Thanks, added to my tree

-------------------------------------------------------------------------
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.php&p=sourceforge&CID=DEVDEV
Permalink | Reply | 0 comments |
headers
Jan Schiefer | 2 Dec 2006 09:36
Picon
Picon

Newest git: Compile problems on Ubuntu edgy

Hi all,

newest zd1211rw won't compile on my ubuntu edgy box anymore.

uname -a: Linux jan-laptop 2.6.17-10-generic #2 SMP Fri Oct 13 18:45:35 
UTC 2006 i686 GNU/Linux

sysadmin <at> jan-laptop:/home/mrsuicide/zd1211rw$ LC_ALL=C sudo make
make -C /lib/modules/`uname -r`/build M=`pwd`
make[1]: Entering directory `/usr/src/linux-headers-2.6.17-10-generic'
   CC [M]  /home/mrsuicide/zd1211rw/zd_mac.o
/home/mrsuicide/zd1211rw/zd_mac.c: In function 'bssinfo_change':
/home/mrsuicide/zd1211rw/zd_mac.c:454: error: 'struct 
ieee80211softmac_device' has no member named 'bssinfo'
/home/mrsuicide/zd1211rw/zd_mac.c:462: error: 
'IEEE80211SOFTMAC_BSSINFOCHG_SHORT_PREAMBLE' undeclared (first use in 
this function)
/home/mrsuicide/zd1211rw/zd_mac.c:462: error: (Each undeclared 
identifier is reported only once
/home/mrsuicide/zd1211rw/zd_mac.c:462: error: for each function it 
appears in.)
/home/mrsuicide/zd1211rw/zd_mac.c:464: error: dereferencing pointer to 
incomplete type
/home/mrsuicide/zd1211rw/zd_mac.c:469: error: 
'IEEE80211SOFTMAC_BSSINFOCHG_RATES' undeclared (first use in this function)
/home/mrsuicide/zd1211rw/zd_mac.c:471: warning: implicit declaration of 
function 'ieee80211softmac_highest_supported_rate'
/home/mrsuicide/zd1211rw/zd_mac.c:472: error: dereferencing pointer to 
incomplete type
/home/mrsuicide/zd1211rw/zd_mac.c:484: error: dereferencing pointer to
(Continue reading)

Permalink | Reply | 2 comments |
headers
Ulrich Kunitz | 2 Dec 2006 13:55
Picon

Re: Newest git: Compile problems on Ubuntu edgy

On 06-12-02 09:36 Jan Schiefer wrote:

> Hi all,
> 
> newest zd1211rw won't compile on my ubuntu edgy box anymore.
> 
> uname -a: Linux jan-laptop 2.6.17-10-generic #2 SMP Fri Oct 13 18:45:35 
> UTC 2006 i686 GNU/Linux

This is no surprise. I don't think, Daniel and me had a formal
decision, but recently we had the practice to support the latest
stable kernel in the master branch and the wireless-2.6 tree in
wireless-dev. I planned to switch today to 2.6.19 with the master
tree.

Supporting all the different kernel versions, is simply to much
effort. Daniel and I have both day jobs. You are always free to
support the driver on your own.

Kind regards,

Ulrich

--

-- 
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
(Continue reading)

Permalink | Reply | 1 comment |
headers
athoslnx | 2 Dec 2006 17:46
Picon
Favicon

longshine lcs-8131g3 wep shared key not work


Hi all,
i have a longshine lcs-8131g3, my kernel is 2.6.19 ( not a patched 2.6.18 to
a 2.6.19-rc6) Linux amd64 2.6.19 #1 Thu Nov 30 12:41:34 CET 2006 i686
GNU/Linux Debian Sid+Etch.

if i am plug the dogle dmesg:
http://www.nabble.com/file/4415/usb%20dongle%20plug.txt usb dongle plug.txt 

if i am start this script:
http://www.nabble.com/file/4420/wifi2.sh wifi2.sh 

dmesg change in:
http://www.nabble.com/file/4416/dmesg_later_script.txt
dmesg_later_script.txt 

the iwconfig,ifconfig and lsmod outpout:
http://www.nabble.com/file/4417/ifconfig.txt ifconfig.txt 
http://www.nabble.com/file/4418/iwconfig.txt iwconfig.txt 
http://www.nabble.com/file/4419/lsmod.txt lsmod.txt 
the problem remains the same one with all the types of driver tries to you!
unless with ndiswrapper

THE CARD WORK PERFECT WITH  ndiswrapper 
and kismet and airodump work "PERFECT" with my mixed firm-driv:
http://www.nabble.com/file/4421/driver_ZD1211_athoslnx.tar.bz2
driver_ZD1211_athoslnx.tar.bz2 

HELP MY !!!!!
--

--
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jan Schiefer | 2 Dec 2006 18:45
Picon
Picon

Re: Newest git: Compile problems on Ubuntu edgy

Ulrich Kunitz schrieb:
> On 06-12-02 09:36 Jan Schiefer wrote:
> 
>> Hi all,
>>
>> newest zd1211rw won't compile on my ubuntu edgy box anymore.
>>
>> uname -a: Linux jan-laptop 2.6.17-10-generic #2 SMP Fri Oct 13 18:45:35 
>> UTC 2006 i686 GNU/Linux
> 
> This is no surprise. I don't think, Daniel and me had a formal
> decision, but recently we had the practice to support the latest
> stable kernel in the master branch and the wireless-2.6 tree in
> wireless-dev. I planned to switch today to 2.6.19 with the master
> tree.
> 
> Supporting all the different kernel versions, is simply to much
> effort. Daniel and I have both day jobs. You are always free to
> support the driver on your own.
> 
> Kind regards,
> 
> Ulrich
> 

Thanks.

Greetings,
Jan Schiefer!
(Continue reading)

Permalink | Reply | 0 comments |
headers
Daniel Drake | 2 Dec 2006 19:48
Picon
Favicon

Re: [zd1211rw] Driver leaving device in bugged state ?

Matthieu CASTET wrote:
> I use a small program to dump the memory :
> http://castet.matthieu.free.fr/tmp/debug_ctrl0.c
> 
> I compared the eeprom state before and after firmware load.
> I notice only 0xffe9-0xffff changed.
> Also 0xfff7-0xffff where like memory address (and of course 
> LOAD_VECT_SIZE = 0x10000 - 0xfff7 in driver).
> 
> May be I shouldn't have given these names : the bootloader image
> (zd1211_ub) have vector at the beginning. Then there is 0xe unknow words
> (LOAD_CODE_SIZE). And the bootloader firmware image end at 0xffe8.
> 
> What I know is that at 0xfff7-0xffff there some interrupt vectors and
> that 0xffe9-0xfff6 is 0xe unknow words.

Thanks for looking into all that. This just started happening on one of 
my devices (ZD1211B) - it cannot survive a rmmod/insmod cycle without me 
having to unplug it. Same problem with the vendor driver. Same for reboots.

So, I researched the whole address space thing a bit further. I don't 
completely agree with the info above:
  - I think the load code comes before the load vector, but don't have
    solid evidence for this
  - I don't know why you think the bootloader firmware image ends at
    ffe8. My zd1211b_ub file is 4018 bytes, thats 0x7d9 words, i.e.
    it ends at 0xffd9. However, code in the vendor driver suggests it
    goes all the way up to cINT_VECT_ADDR (0xfff5).
  - As hinted above I believe the interrupt vector begins at 0xfff5
(Continue reading)

Permalink | Reply | 0 comments |
headers
athoslnx | 2 Dec 2006 23:42
Picon
Favicon

errors make module zd1211-driver-r83


zd1211-driver-r83/src/zd1205.c:34:26: error: linux/config.h: No such file or
directory
error one...

src/zd1205.c:#include <linux/config.h>  
src/zd1205_proc.c:#include <linux/config.h>
src/zd1211.c:#include <linux/config.h>
resolved with
/*include <linux/config.h>*/

error two... 	
this error I do not know like resolving it:

/zd1211-driver-r83/src/zd1211.c:1892: error: 'struct net_device' has no
member named 'get_wireless_stats'

what I must make in order to repair the error?

--

-- 
View this message in context: http://www.nabble.com/errors-make-module-zd1211-driver-r83-tf2744670.html#a7658204
Sent from the zd1211-devs mailing list archive at Nabble.com.

-------------------------------------------------------------------------
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.php&p=sourceforge&CID=DEVDEV
Permalink | Reply | 2 comments |
headers
pointlisse | 3 Dec 2006 00:40

Some help with new handheld install


Hello,

For those that may not (or may) be familiar with the Archos PMA400, it's a
handheld linux PC designed for multimedia playback, PIM, games, but also has
802.11b wifi built into it.
(http://www.pcmag.com/article2/0,1759,1892309,00.asp)

openPMA (http://www.openPMA.org) has developed opensource updated firmware
that includes the zd1211 drivers. I'm among the first (as far as I can tell)
to try to get this connected with a Hawking HWU54G and I'm having some
difficulty. I've provided my script, below, if someone has a minute to help
me work it out:

#!/bin/sh
cardctl eject
iwconfig eth0 essid <myssid> mode Managed
iwpriv eth0 set_mac_mode 2
ifconfig eth0 192.168.1.4 netmask 255.255.255.0 up
route add default gw 192.168.1.1

This device has a full linux distro, and a USB 1.1 host port (why it's
'eth0'), which may prevent full 'G' mode, but I'm not sure. The 'cardctl
eject' command is to disable the built-in PCMCIA 'b' card, just to save
battery.

The device stays lit for about 3 seconds; off for 2; then on for 3 and so
on. There are no blocks or firewalls on my router and the device was tested
on another PC and connected fine, with and without the same IP address
above.
(Continue reading)

Permalink | Reply | 0 comments |
headers
athoslnx | 3 Dec 2006 13:12
Picon
Favicon

Re: [zd1211rw] Driver leaving device in bugged state ?


	
it is the same problem that I have! I have resolved plug peripheral after
the pc  start or the reboot!
http://www.nabble.com/file/4430/grep_error_-110.txt grep_error_-110.txt 

Norman Jonas-4 wrote:
> 
> Hi,
> 
> could it be that zd1211rw ( kernel 2.6.18-rc4 ) leaves the device in a
> bugged state ? The reason why I think so is that :
> 
> - When I power on the computer everything is fine and the driver module
> gets loaded properly
> 
> - On every reboot afterwards there are error messages like this
> usb 5-7: device descriptor read/64, error -110
> and the driver doesn't load
> 
> - When the device is removed and plugged in everything works fine again
> ( like when powering on ... )
> 
> - Another driver ( ndiswrapper ) for the same device works fine under
> all circumstances and never causes the -110 bug.
> 
> -> That bug simply starts appears only when zd1211rw has been loaded.
> 
> And I am not the only one experiencing it :
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Arek Jankowski | 4 Dec 2006 00:39
Picon
Favicon

nslu2 arm observations

Hi All,

I just wanted to report my experiences running different drivers on a 
debian/nslu2 system, little endian version with kernel 2.6.18. The device is 
Zonet ZEW2501 using a zd1211b chip. In all cases below I use wpa_supplicant 
to connect to a wpa2 psk access point.

Using the zd1211rw driver:
- connects fine
- performance is very low - around 70-80kilobytes/s
- driver works reliably (does not hang)
- does not work after rebooting

Using the zd1211-r83 driver:
- connects fine
- performace fine at the beginning
- the driver hangs after a while - which is already known
- seems to work after rebooting

Using the zydas/atheros driver ver. 2_15_0_0 (ZD1211LnxDrv_2_15_0_0.tar.gz):
- connects fine
- performance fine - around 1700kilobytes/s
- need to use patched wpa_supplicant from atheros
- driver works reliably (does not hang)
- does not work after rebooting

Some of this is already known, but I hope this information may be still useful 
for some. My main question is why the zd1211rw performance is so low? Is 
there a way to debug this problem?
(Continue reading)

Permalink | Reply | 2 comments |

Gmane