P5P800 network port problems

[Paul Speller]

The Marvell Yukon gigabit ethernet port on my Asus P5P800 motherboard
has been playing up for some time.

What happens is it just suddenly stops receiving any data - only the
left-hand blue monitor icon in the systray is illuminated, and I can no
longer do anything over the network (or internet, through my router).
All other network machines are fine so I'm pretty sure it's this port at
fault.

The 'fix' is to go into the Windows XP Network Connections window,
select my Local Area Connection that this port is using, choose "Disable
this network device", then choose "Enable this network device". This
always works, although for varying lengths of time - sometimes minutes,
usually hours, occasionally days.

Just lately it's been getting even worse so that I don't think it ever
reaches a day without going wrong now

I've tried updating to the latest Marvell driver for the port but this
hasn't helped.

Does anyone have any suggestions of what I could do, or what could be
causing this behaviour?

Thanks,

Paul
London, UK

P.S. If it helps, I am running Windows XP Professional SP2, fully
patched, and my system spec is a P4 CPU 3.4GHz with hyperthreading
enabled, 2GB of RAM, several hard disks (all IDE), Matrox Parhelia 128
AGP graphics card, floppy drive, Sony DRU-500A DVD-writer, keyboard,
mouse, CanoScan N650U USB scanner, and everything else (sound, IEEE394,
USB2 etc.) using the on-board devices.

 

[Dan Calhoun]

Bingo me too!
I have two Asus P4C800-E motherboards each with a gig of ram and 3 gb procs
that are doing the same thing. One box is using Win 2K and the other is
using WinXPsp2. This started about a month and a half ago. No mail or
internet connection until you disable and enable the network connection. I
have upgraded the NIC firmware, run all the spy-ware apps, and ran Norton to
no avail. I'm with Comcast using a Linksys Cable modem that is version 2
connected to a wired linksys router. I have reason to believe that the V2
cable modem is not syncing with Comcast as the modem diagnostic log
continually has a timeout script every ten minutes. However once I do manage
a connection it stays connected and doesn't drop off. There is a lot of talk
on Broadband Reports about which cable modem is working the best with
Comcast. It appears that the latest Linksys v4 modem works properly.

 

[Paul Speller]

Bingo me too!
I have two Asus P4C800-E motherboards each with a gig of ram and 3 gb procs
that are doing the same thing. One box is using Win 2K and the other is
using WinXPsp2. This started about a month and a half ago. No mail or
internet connection until you disable and enable the network connection. I
have upgraded the NIC firmware, run all the spy-ware apps, and ran Norton to
no avail.

Interesting to hear someone else has the same problem.

I'm with Comcast using a Linksys Cable modem that is version 2
connected to a wired linksys router. I have reason to believe that the V2
cable modem is not syncing with Comcast as the modem diagnostic log
continually has a timeout script every ten minutes. However once I do manage
a connection it stays connected and doesn't drop off. There is a lot of talk
on Broadband Reports about which cable modem is working the best with
Comcast. It appears that the latest Linksys v4 modem works properly.

It's definitely not this in my case - for a start I don't have cable,
but it's also not the internet connection because the other PCs on the
network can all carry on using the internet and network perfectly well
when my PC has lost its connection, so my DSL modem/router is working
OK.

Does anyone know if ASUS tech support are any good? I might contact them
about the problem, as it's really making my PC quite painful to use at
the moment!

Paul

 

[PB]

The Marvell Yukon gigabit ethernet port on my Asus P5P800 motherboard
has been playing up for some time.

What happens is it just suddenly stops receiving any data - only the
left-hand blue monitor icon in the systray is illuminated, and I can no
longer do anything over the network (or internet, through my router).
All other network machines are fine so I'm pretty sure it's this port at
fault.

The 'fix' is to go into the Windows XP Network Connections window,
select my Local Area Connection that this port is using, choose "Disable
this network device", then choose "Enable this network device". This
always works, although for varying lengths of time - sometimes minutes,
usually hours, occasionally days.

Just lately it's been getting even worse so that I don't think it ever
reaches a day without going wrong now

I've tried updating to the latest Marvell driver for the port but this
hasn't helped.

Does anyone have any suggestions of what I could do, or what could be
causing this behaviour?

Thanks,

Paul
London, UK

P.S. If it helps, I am running Windows XP Professional SP2, fully
patched, and my system spec is a P4 CPU 3.4GHz with hyperthreading
enabled, 2GB of RAM, several hard disks (all IDE), Matrox Parhelia 128
AGP graphics card, floppy drive, Sony DRU-500A DVD-writer, keyboard,
mouse, CanoScan N650U USB scanner, and everything else (sound, IEEE394,
USB2 etc.) using the on-board devices.

There have been quite a few posts regarding the Marvell drivers.
Marvell has actually released some pretty horrible drivers for these
LOM's. The answers that seem to prevail are to use the drivers that
were supplied on the CD that accompanied the motherboard when [it] was
purchased. Although possibly older, the seems to do the trick for most,
but not all, of those requesting some assistance.

You could also look at the manual and your utilization of any PCI slots
for your configuration and review the interrupt sharing among those
devices and possibly move any PCI cards you may have installed to a
different slot.

Good Luck.

PB

 

[Paul Speller]

There have been quite a few posts regarding the Marvell drivers.

Yes, sorry, for some reason I didn't find any last night but I saw some
of these today. Hopefully ASUS will not go with this shoddy company for
networking in future!

The answers that seem to prevail are to use the drivers that
were supplied on the CD that accompanied the motherboard when [it] was
purchased. Although possibly older, the seems to do the trick for most,
but not all, of those requesting some assistance.

Thanks for this - I've now managed to get my drivers back to the ones
that came with the board (version 7.14.1.3), after quite a fight with
Windows XP, which really didn't want to let version 8 go! I'll let you
know if it still doesn't work, but here's hoping it does.

You could also look at the manual and your utilization of any PCI slots
for your configuration and review the interrupt sharing among those
devices and possibly move any PCI cards you may have installed to a
different slot.

Thanks very much for these extra tips!

Paul