The RMN said that there presently were a discussion going on in the industry that tries to sort out the mess in the mean time NETGEAR (and I assume that this also is the policy of 3com and D-Link) does not intend to manufacture non-standard equipment (since it will create a bigger mess for other customers). BUT listen to this: many AMD mobos does NOT implement this standard, but rather something of their own mind and creativity. The RMN informed me that both the WG311 cards where built using the PCI 2.2 specification.
The WG311 does have a version 2 but is only 54 Mbps The WG311T does not presently, or is planned to get, a version 2 (see Atheros dependance above).Ģ. Since the 108 Mbps actually is a dual-band 54 Mbps solution that Atheros has some propreiety rights to, your are stuck with the Atheros chipset if you are looking for 108 Mbps.ġ. I talked to the NETGEAR Regional Manager Nordic (RMN) and he had some disappointing messages.Īll major manufacturers of the 108 Mbps WLAN PCI-cards 3com (confirmed by product specialist at 3com today), D-Link and NETGEAR all use the chipsets provided by Atheros. If I have to twiddle with the voltage setting, I let you know. I will return my v1's this week and go shopping for v2's. I think the solutions has been mentioned earlier in the thread already, but I thought it could be a good idea to sort out the causes once and for all. This would - qoute: "most likely fix all problems" I did not ask what to change it to though. However, he mentioned that you could change the voltage setting for the PCI-port of interest in the mobo BIOS to "raise it to the Intel equivalent". Unfortunately, the tech-guy did not know of a fix for the last 20% This should solve 80% of all problems experienced. If you dont have the WG311T version 2 (labelled WG311Tv2 on the box) return your v1 card and get a new one asap! (Unless is says "WG311Tv2" on the box, you can be damn sure it is a v1). The problem is hardware based, hence only a hardware solution apply (in most cases) ġ. Maybe it will get some part of the way, but far from everyone all of the way. So, what to do? Well, the NETGEAR support talks about applying XP SP1, get the latest WLAN, SATA and VIA drivers, to switch PCI-ports and bla bla bla.
WHEN the freeze occur (my guess) depends on the drivers you have, the tweaks you have applied, the services you have started/stopped, the tidyness of your registry etc etc. The Athlon64 CPU (which I have) is especially sensitive due to the new VIA chipset(s). This is something you all been tapping around but not pinpointed exactly (what I noticed anyway). The freeze can occur at boot, when running a certain program etc (in my cause when put under heavy stress/traffic) but seems to be quite random. This is due to that the VIA chipset on the AMD mobos has a different PCI-slot voltage setting than the Intel onesĤ. WG311T (version 1) is NOT AMD compatible (!!!)Ģ. I have followed this debate for some time since my brand new computer has been acting up real good due to my WG311T WLAN-card.ġ0 calls to the swedish NETGEAR support and nothing, but today (!) I got in touch with someone at the support desk that confirmed this to be a problem, since he had experienced the same problem himself.ġ. I believe the Linksys WUSB54G uses a PrismGT chipset, not Atheros. Seeing as I have a usb and not pci wireless adapter, does anyone have any suggestions as to what I could try to fix this without replacing hardware?
In all cases, the problem is remains the same. I have tried plugging the adapter in different usb ports. I have tried clean installs of Windows 2000, Windows XP with no service pack, and WinXP w/ SP2. Now my lockups are every few hours instead of minutes, but they still persist. I've tried installing the via PCI latency patch. I have the latest (and only) bios for my mobo, the latest via drivers, the latest linksys driver, and am using Windows XP SP2 to manage my connection. I am experiencing the same problem as described here only with a Linksys WUSB54G wireless-g usb adapter and FIC K8-800T motherboard (which has VIA VT8237 chipset).Įvery so often my mouse will stop tracking properly then Windows will totally lock up requiring a hard reboot.