Dual boot eth0 issue...

[fizzle]

Hi all,
Obviously, I'm a linux newbie. Heres the problem:
Dual booting an A64 3500+ system with winXP pro sp2 on one physical disk, suse 10.1 on the primary slave disk, GRUB bootloader.

I'm using an onboard LAN, on my ASUS board. Internet works fine in suse, but when i reboot to windows I have no internet at all, windows gives me the "network cable unplugged" popup in the system tray. Before installing suse, windows had no problem. Now, what I can only assume is, when suse shuts down, it kills eth0, because during the shutdown process, the light for that cable on my router goes dead, and doesnt come back on until i boot back to suse.

So, my question is, how can i stop suse from killing eth0 on shutdown? Or...any other remedy for this problem? I searched on google and here, and found the reverse of this problem, but no solutions that work for me...

Any help is greatly appreciated, and if you could please keep it in noob/laymans terms, that would be great

[smolloy]

This might be more of a windows problem than a linux problem. You should be able to reactivate the network card from the windows control panel, and there may be a way to set it to activate at boot time.

[fizzle]

Thanks for the reply.
I'm sure it is a windows problem, but its only a windows problem because SuSE is causing it to happen, if that...makes any sense.

I've tried everything I can think of on the windows side, including trying to activate the ethernet controller at boot (i have it set to do that for SuSE), and still nothing...

I rarely use windows anyway, but when I do, I need the internet, so its kind of an issue. Back to googling I go! Thanks again for the reply.

[fizzle]

Fixed it. Heres the problem for anybody who reads this in the future:

Windows drivers. yep. thats it. Just needed to update my windows drivers for the NIC (in this case, a marvell/yukon nic), now it works like a charm.

It's always something simple eh?