6230Wifi + Latest intel driver = packet loss?

So just got my 8150 and got it all setup.

I used most drivers from sager site except all the intel ones I got directly from intel and also using driver form nvidia for my 580m/

Anyway on the 6230 wifi it seems I have high packet loss. Like 50-70%. My pings are normal if they make it through but the packet loss I don't get.

So I uninstalled the bluetooth drivers first thinking maybe that, nope same. Took the wifi drivers off and put the ones from sager on and all seems to be working fine.

Anyone else notice this? Anyone got latest intel drivers and this wifi card with same issue?

I guess I can use the sager ones fine but just found it odd. I did some searching and found some people with dells that had similar problem but they had high pings also so not sure its the same, plus the fix they tried didn't work in my case. Only putting the sager provided drivers did.

Anyway just thought I would check on that as I found odd.

 

Where are you getting packet loss? Are you saying when you do a ping, you have a lot of failures? Slow speeds != packet loss.

What type of router are you using? You may need to change the settings to optimize the wireless card if you're running a router at home that supports 300Mbps (Start > control panel > network and sharing center > change adapter settings > right click wireless, properties > configure > advanced. Make sure 2.4ghz channel width is auto, wireless speed is max).

If you can provide more specifics on the problem, I may be able to narrow down the issue for you.

 

Its a Cisco WRVS4400N V2.

If I do a ping -t to anything on the local lan it will drop packets like crazy. The ping times are 1-2MS but 70% time out.

Does it on 144Mbps and 300Mbps setting. The same router hosts 4 other wireless devices from TV, Printer, Xbox down to another laptop with a 5300 intel wifi card, all of which work fine.

Its odd, because with the drivers on the sager site it seems fine. Maybe dropps 1 packet out of 700 which is less than a % but the intel direct ones dated last month are a failure.

Just was wondering if anyone else with a 6230 using intel direct drivers without issue or just sager ones (which seem to work) though I think they are just older direct intel ones repacked lol

 

That's strange, I've never heard of that happening when other devices connect just fine. But if the old drivers work just fine (and they're just an older set of the Intel Proset Wireless drivers as you surmised anyway), then there probably isn't anything to worry about.

It may be a driver conflict with the new set that were causing problems, but I wouldn't worry about it as long as your wireless is working now and you're getting speeds you expected

 

Well seems I still have an issue.

The best way I can duplicate it is if I have the laptop off while on battery and than power it on the wireless has massive packet losses. The signal and connection show strong, ping times are decent to local network when they pass but they drop most.

If I reinstall drivers it works fine again during that boot, but right when I repeate the turning it on from cold boot on battery its back to not working right.

I have now tried the latest intel drivers, the sager posted ones and the ones in the clevo driver thread on this board.

I have not tested bluetooth and have kept that off even during these issues.

Also note that all other wireless devices work fine so its something with this system. I would think its a driver issue but why on a clean install of windows and 3 different driver versions now.

I take it by lack of response no one else has had issues with the 6230 wireless card.

 

You should contact the reseller u bought your laptop from. Other than that I have nothing else.

 

Well guess I am to RMA it, I did a clean install of windows and just used the drivers direct from sager and still same issue.

If I boot on AC power all seems okay, it will drop maybe 1 out of 800 pings, but if I am on battery it is 70+% drop rate. I made sure no power management was on, everything was on max performance high power mode.

I saw some dell people with the 6230 with issues and it was just power management in that they needed to put card on max power while on battery but mine is that way by default already and still issues.

Guess its RMA time. Sucks because I would think the fact it works okay on AC would say hardware is fine but 3 different driver versions and 2 reinstalls with same issue and only on battery for the most part. Plus I have another issue with the GPU making an odd electical buzzing type sound when under load. Ugh, darn you sager! Waited 3 months for a laptop and than its got issues

My main worry is them exchanging it and getting a screen with bad pixels too and this one seems perfect, other than on a few parts its got some faint ghosting when on a dark image if you move the mouse araound it trails a little but just a few spots on screen do and I can live with, just not bad wifi and gpu I cant.

 

I've exactly the same problem ( 50-70% package loss) I'm using a Netgear WNDR37000 router. But I've come to the conclusion that this appears after/while the notebook is on battery power it starts power saving on the WiFi card ( u can check in battery plan settings) and I start to have massive package loss. To solve it I either start High performance profile or reboot while plugged in.
OR permanent fix : Use the drivers included from ur reseller and not from Intel =]

 

I ended up getting a replacement laptop due to other issues and at same time got a new router WNDR4500 router.

I honestly think it was incompatibility between the card and my router now but oh well, in the past now.

The 3700 router should be fine though because I helped with the development of the WNDR3800 and its based on same base hardware just with additional ram and it worked fine for me with this card.

The issue you speak of is common though with some Intel drivers.

I don't have that problem on the 14.2 release nor did I with 14.1 on this laptop but I have read a lot of people had that issue and it was related to power management and something iffy the drivers did and the fix was to put on max performance like you said.

My original issue wasn't that though.