Marvell nic works in FC4 but not in XP

[bigfootnmd]

Hi,

I had to replace the motherboard in my dual boot Windows XP FC4 box. The motherboard is from ASUS and the nic on the MB is a Marvell and I downloaded the LAN Driver V7.29.2.3 from ASUS for this nic in Windows. I know that I have the correct driver.

As a result of the MB change Windows would not boot.
I have repaired windows and I loaded the driver for the Marvel NIC. The motherboard is from ASUS and the nic on the MB is a Marvell and I downloaded the LAN Driver V7.29.2.3 from ASUS for this nic in Windows. I know that I have the correct driver.

The marvel nic is working fine in FC4 But, when windows boots and loads the driver for a second everything seems fine then Winodws immediately tells me that the Network cable is unplugged. I've even tried a different cable. Also, in case the linux driver was not "releasing" the nic I even waited 5 minutes before rebooting into windows.

Also, I have removed the NIC in Windows and rebooted and let Windows detect and install it.

So, if the NIC works in FC4 and won't in Windows XP (even after a prolonged cold boot) then what should I do? I have an old 3com 3c905 lan card and a new Dynex DX-E101 (which has no Linux drivers on its page) that I can put in the system. Either of these has the potential to work.

Any ideas will be appreciated.

[wesetters]

try booting XP in safe mode, uninstalling and then reinstalling the drivers for the nic. However, it's generally better to completely reinstall windows after a new mobo.

[darkpark]

I have the same problem but I did not replace the motherboard. i recently installed FC4 which has no problem working with my marvell card (model: 88E8001). Before installing FC4, XP didnt' have issues with the NIC but now it's reporting that the cable is unplugged.

[Firewing1]

that's hilarious... Linux running the proper drivers when windows can't....
Anyways, yeah, try safe mode. Hit F8 as soon after you select Windows from GRUB (Or if you're using NTLDR then just start hitting H8) as fast as you can. Start safe mode, and re-install the drivers.
Firewing1

[darkpark]

thank you Firewing1! I had to get the latest drivers for this card to fix this because using the same ones didn't do anything.