GA-81PE1000PRO-G: LAN driver has CODE 10

MilesG

I've just built a system with the above mobo, P4 2.8, 512mb RAM and had 2 Code 10 errors. One with the graphics card which seems to have been fixed with the latest driver from nvidia (still didn't have MS permissions though), and the other with the Marvell Yukon 10/100/1000 Base_T LAN driver. I downloaded the latest drivers from http://tw.giga-byte.com/Motherboard/Support/Driver/Driver_GA-8IPE1000%20Pro.htm
pointed Update Driver in the direction of the folder in which I extracted the d/load, but XP thinks that there's no point updating. So I seem to be stuck with this error.
Should I enable the "Onboard LAN Boot ROM" in the BIOS (don't know what this does because the Gigabyte manual has no reference to this item in the BIOS display? Or is there something else I can do? I assume that this error means the LAN won't work for my son who will need it soon when he returns to university next week.
Miles

MilesG

I can fix the error by uninstalling, and rebooting. XP finds the hardware, loads the driver and all seems well. But on rebooting the error returns.
Does XP look everywhere on the HardDrive for drivers? I installed the latest to the D: drive partition, so maybe it found the old one on the C: drive and looked no further?
Miles

MediaMan

No to ONBOARD LAN BOOT ROM.

I think it's the YUKON gigabit ethernet. Either the 88E8003 or the 88E8001. Follow this link

http://www.marvell.com/products/pcconn/yukon/index.jsp

Choose the appropriate 32-bit driver link and get the drivers from the download link on the right side of the page...and no...once the drivers are installed they should not do what you are saying is happening.

Step 1: Download drivers
Step 2; extract them to your hard drive.
Step 3: Uninstall NIC and software. Right click on MY COMPUTER...choose PROPERTIES...click HARDWARE TAB...click DEVICE MANAGER button. Find the nic under NETWORK ADAPTERS...expand the selection and right click and choose UNINSTALL on the MARVELL adapter.

REBOOT.

When the system attempts to find the drivers...choose install yourself and point to the new driver extracted directory.

MilesG

Thanks so much, MediaMan. I had given up on tw.gigabyte - the 10MB driver download for the GA-81PE1000PRO-G is useless - it seems to contain loads of CDrom files and folders for many different systems, but the crucial install hotlink doesn't link to anything or do anything! I finally figured I should uninstall the driver, and run the installation executable from the W9x folder, it seemed to install OK but I encountered the same symptom.
Then I thought what about Marvell pages, and found what could be the right .zip file - but checked out this forum before proceeding, and found your message. I'm most grateful.
There's just one thing - after uninstalling and rebooting, XP doesn't seem to present an option to choose the location myself; it sees the hardware and goes after the driver, finds it and installs it, presumably the one that got installed to the C: drive off the mobo drivers and utilities disc. How do I interrupt that procedure so I can point it to the correct (I hope) new driver once I've unzipped to where I keep data and downloads (D: partition)?
Miles

MediaMan

That's easy.

The original drivers really don't go away. They hang around in the system folders and the OS remembers where they are so it automatically install them figuring that's what you want to do.

But in this case...you don't.

Do what I said as far as finding the device in Device Manager but with a slight change in procedure.

When you locate the NIC in Device Manager right click and choose UPDATE DRIVER.

Choose INSTALL FROM LIST... (The bottom radio button) and then choose DON'T SEARCH from the next screen. Click NEXT and choose HAVE DISK button. Browse to where the new extracted drivers are and one file should show up...or two. One or the other will UPDATE the NIC drivers. If you choose the wrong one it will just say there's no info about your device...simply go and choose the other.

The NIC should work straight away...if not...reboot.

MilesG

Thanks again MediaMan. I figured that might be the way. Looks like the system is stable at last. What a disgrace those Gigabyte driver update files are - large downloads, most of the files within which are irrelevant, a cruddy interface that doesn't work, and out-of-date drivers!
I guess one should always head for the hardware component manufacturer rather than the mobo, as they will be the first to release the latest driver.
Regards
Miles

MediaMan

For a tier one motherboard manufacturer Gigabyte does have hits and misses.

Glad it all worked out.