subscriber-only bounced, 2nd try.
--- On Wed, 7/5/08, Hin-Tak Leung <[EMAIL PROTECTED]> wrote:
> Here is my ugly patch to make the vendor 2.22 driver work
> with kernel
> 2.6.25.1, with a ZD1211B-based USB stick, and working in
> access-point/master mode against a managed-mod
Sorry to reply to my own post - nobody seems to find my post interesting?
I have a somewhat interesting issue/extension to my previous patch: I need
802.11g
compatibility (basically because my client gets a bit confused and the client
driver hasn't got the functionality to drop to 11b mode). The
You must be new - I sent a patch to zd1211-devs about two weeks ago
against vendor driver 2.22 to make it work for kernel 2.6.25.
I have been using that for two weeks in master mode now.
I found that the driver/hardware seems to require a
'iwpriv ethX card_reset' before it will serve any client
Consider following the guidelines for submitting patches, and/or post
to the linuxwireless devel list:
http://linuxwireless.org/en/developers/Documentation/SubmittingPatches
--- On Sun, 1/6/08, Gasper Zejn <[EMAIL PROTECTED]> wrote:
> From: Gasper Zejn <[EMAIL PROTECTED]>
> Subject: [zd1211-de
> It is as it says, can't load firmware. If you had not
> used this USB nic
> on a machine before, it is likely you did not have them
> installed.
> They should be under /lib/firmware/zd1211 . In whatever
> mode,
> the driver still needs the firmware.
>
> Mark Ryden wrote:
> > Hello,
> >
> > I ha
for zd1211rw
> To: "Hin-Tak Leung" <[EMAIL PROTECTED]>
> Cc: zd1211-devs@lists.sourceforge.net, [EMAIL PROTECTED], [EMAIL PROTECTED]
> Date: Friday, 11 July, 2008, 6:48 AM
> Hello,
> Thanks!
>
> Could it be a probelem of firmware version ?
> How can I kno
the linux wireless mailing list ?
>
> I am quite stuck with this problem,as you can see.
>
> Regards,
> Mark Ryden
>
> On Fri, Jul 11, 2008 at 12:31 PM, Hin-Tak Leung
> <[EMAIL PROTECTED]> wrote:
>> Hmm, a quick look around the net says your message possibly c
Mark Ryden wrote:
> Hello,
>> Here is a passage from around line 236 of zd_mac.c:
>
> 1) At which tree are you you looking ?
> I have the wireless-next-2.6 .git tree (updated as true for today).
> There is no such comment in this file
Sorry, quoted the wrong file - it is zd_usb.c -
I had wireles
Daniel Drake wrote:
> Hin-Tak Leung wrote:
>> "Because it doesn't work for your device"? That paragraph seems
>> to suggest that a solution to your problem is in the vendor driver
>> but is considered to ugly to copy. There is a clean
>> driver which
Mark Ryden wrote:
> Hi,
>> use the vendor driver.
> In fact it seems to me that it is impossible.
>
> I have 0ace:1211 as vendor id/product id.
> The zd1201.c seems *not* to support it.
> In the usb device id table, we have only
>
> {USB_DEVICE(0x0ace, 0x1201)}, /* ZyDAS ZD1201 Wireless USB Adapt
Mark Ryden wrote:
> Hello,
> I must say that I am a bit disappointed about that my problem is
> still unresolved ; I assume probably I am not the only one who
> encountered
> it. Though I googled for solution, I could not find some appropriate
> solution. Could anybody help in this point ?
>
I a
Mark Ryden wrote:
> Hello,
> I added:
> blacklist zd1211rw
> to /etc/modprobe.d/blacklist
> and , when there zd1201rw and zd1201 modules are not loaded,
> I tried plugging the zd1211 USB nic.
> None of the two drivers were insmoded.
>
> lsmod | grep zd
> gives nothing.
>
> I wonder: which kernel
Mark Ryden wrote:
> Hello,
>
> Thanks.
>
> In sys log I see:
> usbcore: registered new interface driver zd1201
>
> I tried "modprobe zd1201".
> I see no wireles card with iwconfig or ifconfig -a;
>
> running "iwconfig" gives:
>
> lono wireless extensions.
>
> eth0 no wireless ext
om: Mark Ryden <[EMAIL PROTECTED]>
> Subject: Re: [zd1211-devs] Problem when trying ad-hoc patch for zd1211rw
> To: "Hin-Tak Leung" <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED], zd1211-devs@lists.sourceforge.net, [EMAIL PROTECTED]
> Date: Tuesday, 15 July, 2008, 5:24
--- On Wed, 13/8/08, Kari Kallio <[EMAIL PROTECTED]> wrote:
> I also try
> ZD1211LnxDrv_2_22_0_0.working-on-2.6.25.1-but-ugly.diff
> patch and
> it works as well as my modified driver, it load the driver,
> but mac is same
> 00:00:00:00:00:00 :).
I have recently upgraded to 2.6.26.2 and the sa
--- On Tue, 7/10/08, Sundar Visvanathan <[EMAIL PROTECTED]> wrote:
> usb 1-1.1: USB control request for firmware upload failed.
> Error number -110
>
> usb 1-1.1: Could not upload firmware code uph. Error number
> -110
> zd1211rw 1-1.1:1.0: couldn't load firmware. Error
> number -110
firmware up
--- On Wed, 8/10/08, Sundar Visvanathan <[EMAIL PROTECTED]> wrote:
> I got the dongle to work inconsistently on
> "2.6.22.18-omap1" ,configured the
> same as earlier in the post.The dongle works fresh out of
> the box.But on
> second and consecutive attempts it stops working and goes
> into reset m
--- On Wed, 22/10/08, Eric Goff <[EMAIL PROTECTED]> wrote:
> > I bring up my system.
> > After enabling my zydas wireless card, system
> generally hangs after about
> > 10-20 seconds.
> > I have to reboot 9 or 10 times.
> > When it does not hang, then it is good for a very long
> time. (many days)
--- On Thu, 11/12/08, Nerijus Baliunas <[EMAIL PROTECTED]> wrote:
> From: Nerijus Baliunas <[EMAIL PROTECTED]>
> Subject: [zd1211-devs] ZD1211LnxDrv_2_22_0_0 + 2.6.26.5
> To: zd1211-devs@lists.sourceforge.net
> Date: Thursday, 11 December, 2008, 1:02 AM
> Hello,
>
--- On Thu, 11/12/08, Hin-Tak Leung wrote:
> 2.6.26.5-45.fc9 is not *just* some wireless stuff
> backported by Fedora -
> John Linville (the kernel wireless maintainer) works for
> redhat, so the fedora kernel 2.6.26.5-45.fc9 is effectively
> 2.6.27.* as far as the wi
u are doing. The patch is
the sourceforge mailing-list archive.
http://sourceforge.net/mailarchive/forum.php?thread_name=Mahogany-0.67.2-25950-20081211-030236.00%40nerijus.sat.lt&forum_name=zd1211-devs
The patch has been in the sourceforge mailing list archive all-along.
>
> Hin-Ta
--- On Fri, 26/12/08, monghitri wrote:
> You are right, sorry about that and thanks for having been
> so kind to reply me.
> I'm not familiar with mailing lists, i will read about
> that.
> I've originally found your patch here:
> http://www.nabble.com/ZD1211LnxDrv_2_22_0_0-%2B-2.6.26.5-tt2094784
The latest full dmesg is definitely more useful - it says you are on 64-bit
hardware. can you try with a 32-bit kernel? There are some 64-bit issue with
the vendor driver.
--
--- On Mon, 29/12/08, monghi...@aruba.it wrote:
> I thought to have a 32 bit kernel, i have installed 32 bit
> version of
> arch. Can you tell me where i'm supposed to search to
> understand if it
> is 32 or 64 bit? All i know is:
Sorry, I jusy noticed from your dmesg that you have an Athlon64
Most of the answer to your questions are in the wiki pages on the zd1211
sourceforge web site.
The vendor driver is, as it says, provided by the vendor and the authoritative
source of info. It does suffer from being small-endian and 32-bitness. The
latest community rewrite effort is neither on
Christoph Biedl wrote:
> Hi,
>
> I am pleased to tell the Allnet ALL0298 ALLSPORT USB WLAN Finder
> vid:pid 0ace:a211 seems to run like a charme in Linux 2.6.27.7
> after patching the sources as described in
> http://www.linuxwireless.org/en/users/Drivers/zd1211rw/AddID
> Several gigabytes were tr
I have gone through the process of getting code changes into the linux kernel
so it is relatively straight forward to do that if it isn't already done by
somebody else on the list. But
(1) I think I asked maybe somebody else if a new chip id is 1211 or 1211b -
for such simple changes it is easie
--- On Mon, 19/1/09, Giuseppe Calà wrote:
> Thank you,
> now the problem of the real name should be gone.
>
> Best regards
You should have gotten some automatic notification e-mails about the patches
being sent out. Apologies for sending it three times... kernel patches are
required to be for
Your system seems to be working in the beginning, you were just missing the
authentication credentials (ESSID, passphases) - clicking the network manager
applet icon should give you a few boxes to fill them in. Then you f*cked it up
by installing ndiswrapper. If you use ndiswrapper you should go
--- On Thu, 12/2/09, Redeye wrote:
> Rather than just going ahead and doing that, I went out of
> my way to find
> the developers, join the mailing list and asked for a
> little help, then
> received your response. To say that i am taken back by
> your comments is an
> understatement, so much f
--- On Thu, 12/2/09, Redeye wrote:
> I was told that i need the zd1211-firmware but apt-get
> cannot get it with
> all repo's ticked as it is moved or obselete.
> downlaoding and installing from
Still too much irrelevance. read this entry about the
'Debian users beware: don't use the the zd
--- On Thu, 12/2/09, Jelle de Jong wrote:
> Hi Hin-Tak, could you provide some more information about
> the debian
> zd1211-firmware package versus the firmware package of the
> zd1211 project:
> http://sourceforge.net/project/showfiles.php?group_id=129083&package_id=187875
>
> What are the dif
--- On Wed, 18/2/09, Redeye wrote:
> Hi Hin-Tak
>
> zd1211rw 1-1:1.0: couldn't load firmware. Error number
> -110
>
> Thats all i could get from looking at that page. Where do i
> look for the
> error codes please.
>
> Many Thanks,
-110 is timed out, possibly something to do with USB... do
--- On Thu, 19/2/09, Redeye wrote:
> I didnt know 8.10 meant october, thanks for the explanation
> :) I presume the
> 8, bit is the year then
Yes. Ubuntu are doing half-yearly releases .. HPLIP (printig
driver) has a similiar release naming system - it was 1.x.y, then
2.. .
> I dont believe
--- On Thu, 19/2/09, Redeye wrote:
> Yeh sorry same machine, completely flattened the xp
> partition, so its ubuntu
> only.
>
> Do i use chmod and chown, if you could supply examples that
> would be great.
> I was going to use
> sudo chown -R 644 /lib/firmware/zd1211
> sudo chmod 644 /lib/firm
--- On Thu, 19/2/09, Redeye wrote:
> Hi again,
>
> Thanks for suplying that, all actioned and ive still got
> the -110 error, so
> good try. Must admit this is bugging the hell out of
> me, seems no one knows
> what the problem is. I appreciate you trying
> considering your not one of
> the d
--- On Thu, 19/2/09, Redeye wrote:
> WELL DONE Hin-Tak!!!
>
> Your gut instinct on the permissions was obviously it,
> however it didn't
> show as i hadn't rebooted.
>
> So Fantastic news, i will alter my first post with the fix
> and also change
> subject to solved.
Oh, so changing the permi
May I ask where did you get the 3.0.0.56 driver? I heard of the rumour of an
update to the v 2.22 vendor driver a few weeks ago, but haven't seen it
materialized yet. I'll be interested to have a look.
The rumour was from an Atheros guy (Atheros bought Zydas) on the linux-wireless
mailing list
Detailed descriptions below. I'll update with a summary somewhere close by next
to the patches for comments, etc.
--- On Sun, 31/5/09, Hin-Tak Leung wrote:
> On Tue, May 26, 2009 at 5:30 PM, Luis
> R. Rodriguez
>
> wrote:
> > On Mon, May 25, 2009 at 12:08:05AM -0700
3.0 was hosted on the kernel web site.
http://www.kernel.org/pub/linux/kernel/people/mcgrof/zd1211/
You might want to get my patch sets if you want to run 3.0 on more recent
kernels than 2.6.26(?).
http://htl10.users.sourceforge.net/LinuxUSB_AR2524-3.0.0.56_2009May_pathset/
The in-kernel rw dri
--- On Tue, 23/6/09, Nazim Khan wrote:
> Looks like in 3.0.0.56 firmware is added as header files,
> compared to
> firmware upload from user space as it used to be in 2.22.
rw driver has them from user space, the vendor driver has always have them in
header files.
> Does you patches contains
--- On Tue, 23/6/09, Nazim Khan wrote:
> Hi Hin,
>
> Thanks for the info.
>
> So far my 2.22 driver is working fine except one problem
> that under
> stress I get AP loss
> (did not receive the beacon in the 5 seconds).
>
> I was hoping that this issue may get fixed with the latest
> driver
>
-145 is time out ('Use the source, Luke!'). mips is a bit exotic, not many
people have that, and probably not very well-tested; could try compat-wireless
to see if there is any endian fixes. The other thing is, ohci is a bit slow,
and the ZyDAS chip draws a fair amount of power and doesn't reall
presumably you already know that.
From 470a784d9ba4db962fb66080bdf2ca0d1d2edc9e Mon Sep 17 00:00:00 2001
From: Hin-Tak Leung
Date: Thu, 25 Jun 2009 00:09:08 +0100
Subject: [PATCH] 2.6.30-irqreturn_t-breakage
Change to deal with this change:
commit bedd30d986a05e32dc3eab874e4b9ed8a3
--- On Wed, 29/7/09, Mladen Horvat wrote:
> Hi again,
>
> perhaps this is an idea to try the vendor 3.0 driver with
> the new kernel.
>
> Just a question. Is the driver using the new mac80211
> wireless interface so i
> can use it over wpa supllicant 0.6.9 and the build-in wext
> interface ?
>
Do not write directly - all traffic should go into the mailing list archive..
That's very selfish behavior. I do not work for you and I'll have to charge you
on private consultancy rate for that.
Your kernel headers do not match your kernel. (supposedly 2.6.30), nothing to
do with
compiler ver
--- On Thu, 30/7/09, Mladen Horvat wrote:
> Ok, finally managed with the help of a friend to compile
> the vender driver
> 3.0.0.56 with the mips 2.6.30 kernel i use here.
> Here is a patch that was needed to get it finally compiled
> under 2.6.30.
> http://pastebin.com/m17687d4e
Hmm, the net_op
--- On Thu, 30/7/09, Mladen Horvat wrote:
> Using the offical 2.6.30 kernel from kernel.org:
> www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.30.tar.bz2
Hmm, I have that as well, and the patches I used are those I mentioned... Hmm,
did you copy over any compat-wireless headers? Those are beyond
--- On Fri, 7/8/09, "Sören Wellhöfer" wrote:
> While adding support for the
> TL-WN322G wireless usb adapter on an embedded system I
> devised a patch to be applied against the 2.6.22.x kernel to
> make it work.
>
> It basically integrates support for the uw2453 chip into
> the zd1211rw driver f
--- On Sat, 8/8/09, "Sören Wellhöfer" wrote:
> Hi Hin-Tak,
>
> one of my chief problems was that I was not at all able to
> get compat-wireless to work with this rather ancient kernel
> version. The driver file zd_rf_uw2453.c added in the patch
> is indeed taken from a recent version of compat-w
--- On Thu, 30/7/09, Hin-Tak Leung wrote:
> --- On Thu, 30/7/09, Mladen Horvat
>
> wrote:
>
> > Ok, finally managed with the help of a friend to
> compile
> > the vender driver
> > 3.0.0.56 with the mips 2.6.30 kernel i use here.
> > Here is a patch that
--- On Thu, 29/10/09, Daniel Schmitt wrote:
> Hello Hin-Tak,
>
> this URL does not work either:
> http://htl10.users.sourceforge.net/LinuxUSB_AR2524-3.0.0.56_2009May_pathset/
>
> Can you please mail me a .tar.bz-archive of the patches you
> did for the
> ZD1211 3.00 Vendor driver?
> I want to g
--- On Sun, 22/11/09, Daniel Drake wrote:
> Benoit PAPILLAULT wrote:
> > 1. I did not receive junk packet so far with only
> enabling CR_SNIFFER_ON.
>
> The reason we flip-flopped once or twice in the past is
> because
> CR_SNIFFER_ON behaves wildly differently on different
> revisions of the
--- On Mon, 23/11/09, Alejandro Grijalba wrote:
> Benoit PAPILLAULT escribió:
> > 1. I did not receive junk packet so far with only
> enabling CR_SNIFFER_ON.
> >
> If you apply the patch and there is a lot of wireless
> traffic going on
> you will start getting random frames too (sniffing with
--- On Sun, 6/12/09, Craig Niederberger wrote:
> Sorry about posting this
> configuration related question here, but I'm
> at my wits end trying to get an IOGear USB WiFi dongle to
> connect a
> TS-7800 ARM to a WPA2 Personal network via DHCP.
>
> # uname -a
> Linux ts7800 2.6.21-ts #1 PREEMPT F
--- On Mon, 7/12/09, Craig Niederberger wrote:
> > Get a new kernel...
>
> I appreciate the thought, but working with embedded systems
> often
> doesn't afford the luxury of getting a new kernel, as the
> hardware
> developers are more focused on stability than
> performance. This
> should work
--- On Mon, 7/12/09, Craig Niederberger wrote:
> > compat-wireless (a way of having
> old kernel plus the latest kernel wireless bits)
> http://linuxwireless.org/en/users/Download
> > only go as far back as 2.6.22 . Well, you can port it
> back to 2.6.21, and send the compat-wireless maintainer
--- On Mon, 7/12/09, Craig Niederberger wrote:
> Thanks!
>
> > Which ever way you choose, you'd possibly benefit from
> help from Luis - he is both the maintainer of
> compat-wireless and Atheros's contact for the zd1211 vendor
> driver. (the latest one is 3.0 - LinuxUSB_AR2524-3.0.0.56).
>
> M
Hmm, do you really need the echo part? current wireless-testing/compat-wireless
already have the 083a:e501 id.
--- On Sun, 10/1/10, Dani Gutiérrez wrote:
> Hi,
> I'm trying to use a wifi usb device in Kubuntu Karmic
> (9.10). Info of
> the hardware & system:
> * lsusb ID 083a:e501 Accton Techn
: Hin-Tak Leung
Date: Mon Jul 13 23:20:37 2009 +0100
zd1211rw: adding Accton Technology Corp (083a:e501) as a ZD1211B device
--
BTW, wiki is't always up to date... but in any case, the id is in 2.6.32 for
certain.
--- On Sun, 10/1/10, Dani Gutiérrez wrote:
> > Hm
You obviously did not read any of the archive postings, nor look at the web
site in details. The vendor-derived driver has been defunc for a while; most
people use the in-kernel rw driver, others use the vendor driver + my patchset.
Grep the latest vendor tar ball,
http://www.kernel.org/pub/li
Interesting - here used to be some info explaining the three at :
http://zd1211.wiki.sourceforge.net/
but now that's gone and get re--directed back to the download site.
--- On Mon, 18/1/10, Marc MERLIN wrote:
> Executive summary: thanks for the
> links. I built the driver but master mode
> d
--- On Thu, 21/1/10, Marc MERLIN wrote:
> Thanks for your replies and pointer
> to the code that builds.
> Unfortunately, after I bring it up, it doesn't seem
> reliable enough to
> allow connections.
The code works alright for me for the 6 months I used it as my main AP - until
the machine to
--- On Thu, 21/1/10, Marc MERLIN wrote:
> On Thu, Jan 21, 2010 at 03:20:05AM
> +0000, Hin-Tak Leung wrote:
> > The code works alright for me for the 6 months I used
> it as my main AP - until the machine to which it is
> connected to die of old age. (it is ust under 10 years
--- On Thu, 21/1/10, Benoit PAPILLAULT wrote:
> Side question : from this thread, it seems that zd1211rw
> driver supports
> AP mode. Is that true? Looking at the code (2.6.33-rc4-wl),
> it is
> supposed to only support station, adhoc and mesh mode. Does
> AP mode
> support has been dropped s
--- On Thu, 21/1/10, Marc MERLIN wrote:
> On Thu, Jan 21, 2010 at 08:14:41AM
> +0100, Benoit PAPILLAULT wrote:
> >From what I understand, the zd1211rw does not support
> AP mode (at least
> it did not for me) and one is required to use a patched up
> someone
> unmaintained upstream zd1211b drive
'Network is down' -> 'ifconfig wlan1 up' first...
also make sure NetworkManager/wpa_supplicant are down, as they interfere with
manual operation like these - you should do *either* iwconfig/iwlist *or*
networkmanger/wpa_supplicant but not both.
--- On Sat, 30/1/10, Dani Gutiérrez wrote:
> Hi
--- On Sat, 30/1/10, Dani Gutiérrez wrote:
> 'Network is down'
> -> 'ifconfig wlan1 up' first...
>
> also make sure NetworkManager/wpa_supplicant are down, as
> they interfere with manual operation like these - you should
> do *either* iwconfig/iwlist *or*
> networkmanger/wpa_supplicant but not
--- On Sat, 30/1/10, Dani Gutiérrez wrote:
> It
> isn't that much of a hack - the ifconfig is fairly
> standard for manually starting a network interface - if you
> go manual, you have to do ifconfig/iwconfig/iwlist all the
> way.
>
> Sure
> ifconfig is a very usual command. But in this thread
Hmm, there are anecdotal evidence that pid works better than minstrel for
mac80211-based drivers when the AP is a bit weak. Minstrel is the default from
2.6.30(31?) onwards, but you can choose pid with a module parameter in
modprobe.conf - see if that helps. The details are in two bug reports on
Hmm, the default(?) is 1500 - MTU=500 is way too low for normal usage.
since zd1211rw is also a mac80211 driver, can you give the pid modprobe.conf a
try to see if it helps? See http://bugzilla.kernel.org/show_bug.cgi?id=14168
--- On Sat, 13/2/10, Ernst J. Oud wrote:
> L.S.
>
> I am runnin
uthenticate with AP --:--:--:--:--:-- (try 1)
> wlan0: authenticated
> wlan0: associate with AP --:--:--:--:--:-- (try 1)
> wlan0: RX AssocResp from --:--:--:--:--:-- (capab=0x411
> status=0 aid=4)
> wlan0: associated
>
> Any clues?
>
> TIA
>
> Ernst
>
&g
Hmm, unfortunately yes - you can build both in to have it runtime switch-able,
but you have to have both in before that can happen.(mintrel is the default).
--- On Sat, 13/2/10, Ernst J. Oud wrote:
> Yes, it is a module and yes I did a
> reboot. I can remember having specified
> minstrel when
Hmm, what's the hardware (the zd1211rw: ... line in your dmesg, you can
probably just grep zd1211 /var/log/message for it as well) may be all the same.
There are quite a few variants.
I don't know if putting compat-wireless on will help, but you could give that a
try. FWIW, the driver developme
Have you tried using compat-wireless? That would give you the latest zd1211rw
code against an older kernel. (compat-wireless is equivalent to the
kernel-module-backport package on ubuntu, I think).
James Ronald wrote:
> I am trying to get a "safe home" brand USB zd1211b device to work with one o
--- On Tue, 23/2/10, James Ronald wrote:
> I'm running Linux 2.6.25 and the
> zd1211rw driver from 2.6.25. Does
> anyone know if this driver worked in 2.6.25 and if so what
> it's
> dependencies were? Which 802.11 stack? I am
> fairly new to the 802.11
> drivers and not familiar with everything
--- On Thu, 4/3/10, Ernst J. Oud wrote:
> L.S.
>
> Mmm I might be onto something about this weird MTU
> problem with Zydas
> 1211b based devices on my embedded box.
>
> This box has an RDC i486 SOC processor.
>
> Within the vendor driver of the Zydas 1211b there is an
> extra compiler fla
--- On Fri, 5/3/10, Benoit PAPILLAULT wrote:
> Regarding the source code you mentioned, I cannot find the
> R8610 thing.
> Which version/revision do you look at? Moreover, the
> RX_COPY_BREAK is 0
> in the source code I've looked at and this code is only
> used for RX (not
> TX), so it's unlik
I suspect it is just poor hardware. The more power-drawing devices you have
got, the current/power available to each can drop, and some devices are more
sensitive to drop in voltage than others. That seems to be the obvious
conclusion - the more bus-powered devices plugged in, the more likely th
Error -110 is USB timeout. it is just an indication that the device is not
responding - not enough power from the motherboard and is a hardware rather
than a software problem, is probably my guess, given recent problem reports.
--- On Mon, 26/4/10, Rich Rauenzahn wrote:
> zd1211rw 1-1:1.0: co
-- Forwarded message --
From: Hin-Tak Leung
To: Gavntery
Date: Tue, 12 Oct 2010 02:47:31 +0100
Subject: Re: About ZD1211LnxDrv
I haven't used that Vendor driver myself for a while (my older machine
which serves as AP died of old age, unrelated), but I did remember it
was
There are two things you can try -
1) there are some anecdotal evidence that the new default minstrel rate
algorithm doesn't work as good compared to the older default pid algorithm where
the signal strength is low. I don't remember when the switch for the default
algorithm has happened, but tha
--- On Thu, 28/10/10, julien cubizolles wrote:
> First : I have to manually set the bitrate like it was
> before.
>
> But the bug remains : I get deconnected after a few Mo
> uploaded.
Overriding bitrate is probably not advisable - why do you do that. (also,
please keep the cc to the list - th
julien cubizolles wrote:
> By default, the bitrate is set to 1Mb/s. I usually set it to 48Mb/s or
> upload is ridiculously slow. That's what I've been doing with kernel
> 2.6.32 for a year or so.
By default, the bitrate is set to 1Mb/s *when you are not using your
connection*. It should shift up
julien cubizolles wrote:
> Le vendredi 29 octobre 2010 à 00:38 +0100, Hin-Tak Leung a écrit :
>> julien cubizolles wrote:
>>> By default, the bitrate is set to 1Mb/s. I usually set it to 48Mb/s or
>>> upload is ridiculously slow. That's what I've been doing wi
Hi,
I added patch 13 and 14 to
http://htl10.users.sourceforge.net/patchsets/LinuxUSB_AR2524-3.0.0.56/
which allows the zd1211 vendor driver to build against recent kernel - in my
case, 2.6.35.10 .
I use it mainly for the AP mode, on an old machine that has just been
resurrected after over a yea
Nerijus Baliunas wrote:
> On Wed, 16 Feb 2011 01:28:19 + (GMT) Hin-Tak Leung
> wrote:
>
>> I use it mainly for the AP mode, on an old machine that has just been
>> resurrected after over a year, so the last it worked was on 2.6.31.x .
>> There are a couple of old
Nerijus Baliunas wrote:
> What are standard instructions? It works with hostapd here...
Perhaps I should say the patch looks incomplete, because I have seen the
"official" change I mentioned below, and it is more than just two lines.
>> in any case, the "official" change has
>> already happened
ownership of the firmware files (and the containing directories)?
Krzysztof Stankiewicz wrote:
> Im developing on LPC3250 NPX Embedded system, Ive placed the firmawere
> where instructed,
> and I keep getting this error no matter what I do?
> Ive gone as far ast tracing the kernel stack but mak
Michael Tokarev wrote:
> 13.05.2011 14:22, Hin-Tak Leung wrote:
>> ownership of the firmware files (and the containing directories)?
>
> The firmware loading is done from a root process, so permissions
> are largely irrelevant. Especially with this error number
> (-2 = E
0x0ACE 0x1215 should bind to the zd1211b kernel module (the vendor driver
builds two kernel modules, zd1211 and zd1211b). That said, compat-wireless is
probably the way to go...
--- On Thu, 17/11/11, Jussi Kivilinna wrote:
> Hello,
>
> zd1211rw gained master mode support in 2.6.39. For older
The message seems quite clear - missing firmware. Some *cough* zealous *cough*
distros ship kernels stripped of binary blobs crucial to the functionality of a
device, because it does not fit their ideology of software freedom. Download
and install a proper kernel, with all the necessary bits.
92 matches
Mail list logo
