Community
cancel
Showing results for 
Search instead for 
Did you mean: 
idata
Community Manager
6,548 Views

Intel 82579v - Code 10 - media disconnected

After long shutdown and then power up ( eg. Power up in morning ) 82579v adapter shows Windows driver code 10 - with media disconnected status in ipconfig.

Shutdown and restart does not fix. Hard power off while machine running, wait 60 seconds and power on usually fix. Bio reset default also fix.

Problem re-occurs if machine is shutdown and powered off for a few hours.

It is not cabling or router since problem is resolved by one of the above power cycle steps.

Configuration:

Motherboard: Asus P8Z77-V Pro

Bios: Asus 2104 ( latest )

OS: Windows 10-x64

Network Driver: Intel 12.5.31.4 / ProSet 21.1.30.0

Applied NVRam update ( 82579VSKU ) adapter is now 82579V - no longer bounces to LM.

Tried:

Older BIOS

Microsoft Windows 10 Driver

Problem appears similar to:

/message/264820# 264820 https://communities.intel.com/message/264820

/thread/110194 https://communities.intel.com/thread/110194

0 Kudos
23 Replies
idata
Community Manager
1,062 Views

Hi Rman'1900,

 

 

Thank you for the post. Just wonder if you have tried using Asus* driver as this is onboard NIC on theri system.

 

 

rgds,

 

wb

 

idata
Community Manager
1,062 Views

Hello - Asus does not have a Windows 10 Network driver listed: https://www.asus.com/us/Motherboards/P8Z77V_PRO/HelpDesk_Download/ P8Z77-V PRO | Motherboards | ASUS USA

I have tried the generic MS Windows 10 driver, have tried Intel Proset. Tried Windows 7 and Linux.

The behavior is the same. After long shutdown and power off, network does not work. Shutdown/restart

does not help. Full power shutoff without shutdown and restart does resolve most of the time.

I have read some where in the design specs for the 82579V PHY where it seem that there is a process

whereby it switches from PCIe to SMBus when in power off state. I'm wondering if there is a problem

here.

There seem to be lots of threads around the net about bad behavior with 82579V PHY, but can't seem

to find a solution the works reliably.

Help appreciated.

Thanks.

idata
Community Manager
1,062 Views

Hi Rman'1900,

 

 

According to Microsoft* https://support.microsoft.com/en-ph/kb/943104 (note this is third party website for reference only, not under Intel's control) this is a generic error message, could be the device driver for device itself. Since there is no driver from Asus* , this could be part of the problem as well. As this is an onboard NIC (Here is the information about onboard NIC support http://www.intel.com/content/www/us/en/support/network-and-i-o/ethernet-products/000006628.html?wapk...) in which the controllers was supplied to Asus for integration on their system based on their specs. It is recommended to check with Asus* directly if they can provide driver support and further check on the hardware aspect.

 

 

Hope the above information clarified.

 

 

rgds,

 

wb

 

 

idata
Community Manager
1,062 Views

Hello - any way I can message you in private ?

Thanks,

idata
Community Manager
1,062 Views

Hi Rman'1900,

 

 

I sent a PM to you.

 

 

rgds,

 

wb

 

idata
Community Manager
1,062 Views

Did some more testing and here is what I've observed:

1) Windows Shutdown followed by total AC power off -> wait a few hours -> power up = Adapter Fail

2) Adapter Fail -> Shutdown -> Restart = Adapter Fail

3) Adapter Fail -> Shutdown -> Wait a few minutes -> Restart = Adapter Fail

4) Adapter Fail -> total AC power off ( no shutdown ) -> Wait a minute -> Restart = Adapter Ok

5) Adapter Ok -> Windows Shutdown -> Standby / keep AC power on -> wait a few hours -> power up = Adapter Ok

There is something happening when AC is off for significant time - I am guessing probably power saver / BIOS / Firmware related.

Thanks

idata
Community Manager
1,062 Views

Hi Rman'1900,

 

 

Thank you for the additional information provided.

 

 

rgds,

 

wb

 

idata
Community Manager
1,062 Views

Hello, I'm having an issue with a similar MB, P8Z77-I DELUXE. My Wifi, Bluetooth adapter work but for some reason my 82579v suddenly stopped working. It's been like that for a couple of days and almost had it identify my network cable when setting it to 100MB Half Duplex mode. That didn't work and it's been like this for a week. I've tried a new os, reinstalling BIOS, hard reset, leaving it off for 5-6 hours. Asus's support page doesn't have new drivers since 2014 for my adapter. I'm considering getting a USB to Ethernet adapter but I'd like to avoid that. Please if you could, help me out mate

idata
Community Manager
1,062 Views

Hi Rman'1900,

 

 

We tried to test in our lab but did not encountered the said issue.

 

 

Please contact Asus* to check if there are other user with the same board also experiences this issue.

 

 

Can you provide more reference information about the design regarding PCIe to SMBus,

 

so that we can further check.

 

 

The difference between 82579LM and 82579V is 82579LM supports vPro, macsec,

 

in terms of connectivity functionality should be the same.

 

 

Thanks,

 

wb

 

 

 

idata
Community Manager
1,062 Views

Hi Rman'1900,

 

 

Please feel free to update me the information.

 

 

rgds,

 

wb

 

idata
Community Manager
1,062 Views

@Intel... 82579V is seem a bit like like a lemon ... NEED THIS RESOLVED !!! ... been over 3 years of complaints from various folks and still no definitive answer

@Yuvraj - unfortunately I have not found a solution ... tried MS drivers, tried Intel drivers, tried Window7 - no luck

Tried Linux-Mint - same problem ... adapter goes AWOL when power is removed for a length of time - PHY does not come online on restart.

idata
Community Manager
1,062 Views

@Yuvraj - At the moment, the only workaround I have found is to completely turn off power ( do not shutdown ) - for 30 seconds and then restart.

This cannot be too good for the disk drive - but don't have much choice.

idata
Community Manager
1,062 Views

@ Yuvraj - if machines is left with not power for any length of time ( an hour or more ), I seem to have a problem. If machine if total powered off ( not shutdown / just kill power ), wait 1 minute for power capacitors to drain, and then restarted - Network Interface seem to recover.

idata
Community Manager
1,062 Views

In the end I bought a USB to Ethernet adapter. This should have been resolved, the MB I have is a deluxe they still should be supporting this. Oh and my cat5e cable was broke because something ate throughout but regardless no other cables work.

idata
Community Manager
1,062 Views

Hope your not facing much difficulties, I recommend just getting an adapter as well, thanks for your support rman1900

idata
Community Manager
1,062 Views

Hello WB - so far no luck. Same problem. Also requested help from ASUS.

There is something oddly wrong in software since, if I do a hard power cycle

( cur power, wait 30 seconds, restart ) the adapter recovers. There seem to

be an issue in the interface firmware or in the Bios. Can you check whether

I can "force" re-flash the 82579 firmware. I had used the following when

I used the following command when I did the initial flash:

82579VSKUW64e.exe -nosilent

However there seem to also be an option:

-nofunction0only - update shared EEPROM

Not sure what that does.

Thanks,

idata
Community Manager
1,062 Views

Hi Rman'1900,

 

 

Thanks for the update. Let me check on this.

 

 

rgds,

 

wb

 

idata
Community Manager
1,062 Views

Hi Rman'1900,

 

 

Can you share what happen after you run the command 82579VSKUW64e.exe -nosilent?

 

Where did you see the "-nofunction0only - update shared EEPROM" ?

 

 

thanks,

 

wb

 

idata
Community Manager
1,062 Views

C:\P8Z77-Drivers\Network\82579VSKU\Win64e>82579VSKUW64e.exe -?

LVDASKU version 1.2.2

Tool to update Lewisville NVM ASKU

Copyright (C) 2012 Intel Corporation

Usage: LVDASKU [options]

-noauto - wait for user input

-log [filename] - generate log info

-report [filename] - generate report file

-nosilent - display the user interface

-nofunction0only - update shared EEPROM <-------------------

-nodriver - don't auto-install driver

-p - only check for update needed

-undo - undo changes previously made

--------------------------------------------------------------

C:\P8Z77-Drivers\Network\82579VSKU\Win64e>82579VSKUW64e.exe -nosilent

LVDASKU version 1.2.2

Tool to update Lewisville NVM ASKU

Copyright (C) 2012 Intel Corporation

Loading driver...

Scanning...

# Ven Dev SVen SDev Rev ST Device

-------------------------------------

1. 8086 1503 1043 849C 4 -- Intel(R) 82579V Gigabit Network Connection

U = needs updating

S = shared NVM; no update needed

* = update already performed

- = no update possible

No update required.

idata
Community Manager
435 Views

Did some more testing. Found the following:

Does not matter whether Windows shutdown ...

1) simply turn off power - unplug machine

2) leave powered off for an hour or more

3) power up

4) NIC is broken

5) simply turn off power - unplug machine - *do not shutdown*

6) wait 30 seconds

7) power up

8) NIC is fine

Tried Linux ( Mint ) - same problem.

I'm thinking BIOS and NIC/PHY Firmware not playing together. I noticed that this PHY

has an option to switch SMBus when powered off and switch back to PCI-e on power

up. Wonder if the switch between SMBus and PCI-e is having problems.

Reply