linux shuts down built in network card then windows tells me network card is unplugge
 

hi i have a dual boot system with suse and xp. linux shutsdown network card on exit and then windows tells me network is unplugged.The only way i can get it to work is to turn power off on computer when in linux.any help would be appreciated.


Les

Les,

May be a hardware problem. First try switching the ethernet cable; and if that doesn't work call your hardware vendor!

thanks for the reply but i think it must be something to do with commands sent to the computer on exit from linux just don't know where to look for the answer
Les

Can you be a little more specific about the exact problem?

After running linux... when you reboot... and log into WIndows... your network card doesn't work in Windows?

Is that accurate?

What kind of card is it?
What have you tried? Unplugging/replugging cable? New driver for card in Windows?
Does it happen if yo log into Windows first, then into XP? What about XP to XP?

it does not happen if i go into xp first or when going from xp to xp . but if i go into linux either first or after xp has been running and then go into windows then network cable unplugged message from windows. on my computer there seems to be a light flashing from the cable at the back of computer even when computer is switched off. but not after shutting down computer from linux.

Hi, i have the same problem,

If i shut down in linux in a regular way, xp says that the xp cable is unplugged, it seems that linux shuts down the network interface in a way that make windows unable to start the network card. If i just shut down the power in linux and then start windows everything is working, but this is not a nice way of solving the problem. However, i've got two built in networks cards on my motherboard wich is a ASUS A8N sli deluxe, and this problem only occur on my "second" network card.

The network card that work fine is a NVIDIA nForce networking controller which i think is based on Realtek chip rtl-8139
The second card is a Marvell Yukon 88e8001/8003/8010 PCI gigabit ethernet controller and it is with this one i'm experince my problems.

I'm running SUSE 10.0 rc1

I dont think its a hardware failure issue, i think its about the commands that linux sends to the card just before shutdown, and for some reason the Nvidia network card is unaffected by this but Marvell is not.

To be more precis, linux manage to shut off the marvell card so even during P.O.S.T. the card is switched off(but in bios settings it's enabled). The network led is not lit up wich it is normally even when the computer is switched off.

I really dont know how to solve this, maybe one can edit some shut down script in linux so the controller stays online

check here for possible solution

Hello, i just thought my Nic (Marvel Gigabit, on my DFI NF4 also) had died "just after installing SUSE"... so this is NO cable problem this is a SUSE problem, how can we fix this? I tried 2 deactivate the Marvell card on Linux but it still doesnt work on windows, what is going on?

I got the solution!!!

Just download this driver for WinXP/2003 and thats it!

http://www.marvell.com/drivers/drive...?dId=103&pId=1

IN the end that is all I had to do too.update the windows driver problem solved

That worked for me too
 

Thanks a million to everyone on this thread. I installed Suse 10.1 64bit earlier today on a machine with an Asus A8V Deluxe MB and an onboard Marvell Yukon GB Ethernet. Experienced the same issues as everyone above after switching back to XP from Suse. Went to Marvell's site, updated my NIC drivers, and voila! XP network drivers work again.

THANK YOU!!!