Vista - Marvell Yukon disconnect issues

Hi folks
I've installed Vista Ultimate x64 and am having a networking issue that is driving me mad. I have a Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller that is connecting to my router ok, seeing the network ok and connecting to the internet... for a few very slow seconds, then it dies.
I have another box connected to the router that is absolutely fine, so I know there is nothing wrong with my connectivity. I have managed to use a USB wireless connection from the Vista x64 box with no problems at all.

The driver is yk60x64.sys v10.27.2.3 from the Marvell site dated 19th Nov 2007.

I've tried DHCP, static IP... running out of ideas!

Any suggestions gratefully received
Pete

P.S. Oh and I should add that it works fine under xp so not a problem with the hardware

Hi Recoil101,
Maybe one of these links could do the trick? Hope this helps.

Auto Tuning - TCP/IP receive level

QoS Bandwidth Reserve Limit

Also I was thinking what if you turn off I.P. version 6 and just leave I.P. version 4 enabled? Hmmm Let us know.

Raj

Thanks for that Raj,
Unfortunately I'm no further on with this. I tried turning off IP v 6 but no change, I went through the steps in your link, but when I restricted auto tuning it simply refused to connect at all.

It's very odd. I can browse (very slowly) for about 10 seconds then it stops. The Network and Sharing Centre then responds with a "limited connectivity" message. Clicking diagnose and repair doesn't fix it.

This is very frustrating as I bought an expensive graphics card to take advantage of DX10 and now I'm going to have to go back to XP :-( What a nightmare Vista is).

Any other ideas anyone???

Thanks

Hi recoil101,
What if you go to command prompt then type:
ping www. msn .com -t (no spaces between .msn.)

It should ping sucessfull everytime pretty much. But if your seeing

reply from
reply from
reply from
reply from
timed out
timed out
timed out
timed out
Then it sounds like your having packet loss. You got the latest Vista driver for the network card installed? Also If you having packet loss I would call your ISP and tell them.

Raj

Not that it is much help to you but I can report exactly the same issue as recoil01. Very slow and intermittment connections always ending in failure. I have tried several Yukon drivers but with no luck.
My experience with Marvell cards has not been good. The only glimmer of hope I can offer is that I had a similar kind of porblem with a Marvell on board card under XP 32 bits. After downloding new drivers every few weeks for months (it was amazing how often windows update wanted to give me a new marvell driver) and suddenly one day after yet another update, both machines (we had two with same spec and problem) started working.
Motherboard Asus A8N-SLI by the way
Marvell Yukon 88E8001/8003/8010 PCI is reported
driver 10.55.3.3 22feb 2008

Any help gratefully received.

I'm having the same exact problem. Was going out of my mind troubleshooting this. It is not your ISP, it is not your router, it is not your cables. It is 100% a driver issue! An unacceptable one at that. Has anyone found a solution to this yet?

It is a problem with 4GB or more memory.
It works with 2GB fine.
I called Microsoft - they blame it on the Marvel driver.
Driver was just updated but the same thing.

Back in July Marvell got interested and asked for information. Sent them a load of WMI dumps and they promised that the "Test & Verification Manager" was on the case - but they gradually stopped responding to e-mail. I'll ping the guy who was on the case and see if they've made any progress in 5 months!.

This is issue still has not been resolved; but it has nothing to do with memory or anything else. It has been confirmed to be a hardware error on the Marvell chip. Once disabled and another NIC is used, no problems arise. In another words, Marvell NIC's are very cheaply made with zero quality control, and in fact they use refurbished and scrap silicon materials to make their products. Took a lot of research and phone calls to determine all of this, but alas, it is fact.

Moral of the story? Avoid Marvell (both comic books and NIC's) at all costs!

I feel your pain, I've tried every thing no luck. I have three motherboards with the Marvell Yukon chipset.
The only solution for me was to buy separate nic cards and no more disconnects. The Marvell Yukon chipset is garbage, next motherboard I buy will not have a Marvell Yukon chipset on it. Good luck!