26.09.2014 18:42, Arend van Spriel wrote: > Being bold here, but would you be willing to send that non-working part of > hardware to me. I seem to have 4313 cards over here that just work and it > would help greatly investigating the issue. I guess you do not care that much > anymore, but might be others do (myself included).
Please note that this is 2nd card of the same model which I come across in different laptops (one lenovo which I bought last December, and later in a HP Envy which I borrowed from my friend because my lenovo didn't work anymore). Both shows exactly the same sympthoms, on several different WiFi networks. The sympthoms are rehashed here several times -- sporaric stalls of different frequence of occurences, which can be cured by re-loading the driver. I can send it your way, -- guess it will be quite a bit costly, but I don't have any use for it anyway (short of throwing it away), and since I already spent significantly more money due to all this (whole thinkpad plus ssds and several wifi adaptors), this additional cost is just a small noize. But since that's 2nd card in a row, maybe there's something else in there, the prob is not in the card? I mentioned several times that here, both of these cards worked for long periods of time and for many gigabytes transfers (I used wget in a loop overnight), -- and worked very well. Just that these "working periods" changes into "non-working periods" without any clear cause, sporadically. And these working periods can be rather long, too. Maybe this is some uninitialized field somewhere, I dunno - at least that'd explain the "mystery" and inability to reproduce any of the two kinds of "periods". Ofcourse it's rather difficult to debug, but it might not be card-specific. I also noticed that quite often it does not work after rebooing the laptop from windows. But not always. I thought maybe win switches it into some mode which linux driver fails to notice, but no, the fact that it sometimes works after windows tells me that I'm not right. And note please that the closed-source wl driver always worked with both of these cards, at least when I was able to compile it (the prob is always the same - no support for more recent kernels; and I don't really like to use recent kernels (I myself currently stay with 3.10.x stable line), but both laptops actually requires recent kernels to work properly (either because of great energy saving support in latest intel cpus, or because of support of gpu in latest intel celerons) -- that's why I really prefer in-kernel driver). That to say - the fact that wl always works may tell that the hw is fine and the prob is elsewhere. Thanks, /mjt -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
