I fairly new to Linux. Just setup a dual boot with separate drives FC4 and WinXP. All seemed fine. FC4 connected fine to my Belkin router, got on the net OK. Windows did the same. However, after updating FC4 upon rebooting into windows, the ethernet connection does not work. The light on the router does not come on to recognize the connection. The Device Manager states that network adapter is working correctly and is enabled. When rebooting into FC4, the connection works fine. Anyone with any ideas? Never imagined such a thing was possible since the two OS's are on separate drives. System specs:

Self build AMD64 3400+ with Gigabyte Geforce 250 mobo
windows on Hitachi 160GB
FC4 Maxtor 80GB
1.5GB memory
Marvel on board ethernet
Nvidia graphics 5700FX

Any help thoroughly appreciated.

being on seperate drives does not effect the router.

if you are 'just' rebooting (soft) then maybe your network card is not being 'released' for some reason.

try shutting down the pc completely and then restarting into to win and see what happens.

good luck.

If that doesn't work, then when you go into windows go to your Device Manager. Find your network card and delete it. Reboot your computer. If your NIC does not automatically re-install itself then install the driver.

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. Windows tells me that the Marvel nic
is working fine. 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, 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.

Any ideas will be appreciated.

lol, a card that works in lin and not in win

r u sure the 3com is not compatible in lin? double check that with another reference... you might to be able to at least use the tulip (generic one) on that one.

with xp i suppose you could try removing the card in your settings and then reinstall it (after shutting down).

also with some pc's shuting down is not really shuting all power off to the system. you shoul d unplug the system to ensure that no power is going to it.

good luck.

I don't think that I thought of unpluggin the power cord between boots. I will try that. I rarely need windows and if that is all I need to do once in a while, well that isn't so much.

Just thought I would mentioned and update the following. I have two NICs, one PCI netgear and one on-board Marvell on the K8N motherboard. As soon as I upgraded to the 2.6.14 kernel in FC4, everything worked fine. Wierd. Have no idea what was happening, but now FC4 recognizes both (eth0 and eth1) and windows does also.

Not sure why, but the upgrade cured the problem.

Bob

Problem solved.

I put in my spare Dynexs DX-E101 card. As soon as I powered the PC on the link lights lit up. Windows found the card immediately. Then I booted right into Fedora and FC4 saw the card. All is well.