Intel 82579V NIC problem - kernel regression?

Hi all,
I recently upgraded my desktop motherboard to an Asus Maximus GENE-IV, which has the Intel 82579V Gigabit NIC. I installed arch the usual way, dd-ing the latest install image onto a USB stick, and what have you. Trouble is, as soon as I upgrade the kernel and reboot, my NIC stops working in a peculiar manner. It will come up after I do 'sudo ip link set eth0 up', and acquire a carrier. Then, after about ten seconds, the carrier drops. Then it'll come back up again... and drop again. Over, and over, and over. This does not happen with kernel 3.0.3, which is the kernel installed by the latest install image, but it happens with every kernel from 3.0.7 onward (3.0.7 is the oldest kernel I have available to test with, from /var/cache/pacman/pkg on another machine). The most frustrating thing is that I've been googling the problem for two days now, and I can't find anyone who has quite the same issue
The driver is e1000e, and it's autoloaded. My system is an x86_64 one. Has anyone experienced this themselves or heard of it anywhere else? I'd like to avoid manually building the intel driver sources if it's at all possible, because it works fine with an old kernel. /frustration
Edit: dmesg is flooded with "e1000e: eth0 NIC Link is Up" messages.
Edit: further weirdness: when I set a static IP on boot from rc.conf, the interface stays up, but I can only see machines on my local network - DNS does not work, even after putting a nameserver entry into resolv.conf and rebooting.
Edit: I did a clean install, marked the linux kernel as a package not to be upgraded, and did a pacman -Syu. Even with the old 3.0.3 kernel, after the update, my NIC is broken in exactly the same way. I'm really stumped on this!
Last edited by andrew-wja (2012-01-10 21:21:29)

Works fine here, same driver, static IP though.
$ uname -a
Linux amalthea 3.1.8-1-ARCH #1 SMP PREEMPT Sat Jan 7 08:03:08 UTC 2012 i686 Intel(R) Celeron(R) CPU G530 @ 2.40GHz GenuineIntel GNU/Linux
$ lspci|grep Ethernet
00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 05)
$ lspci -nn|grep 00:19.0
00:19.0 Ethernet controller [0200]: Intel Corporation 82579V Gigabit Network Connection [8086:1503] (rev 05)
$ dmesg|grep e1000e
[ 3.965629] e1000e: Intel(R) PRO/1000 Network Driver - 1.4.4-k
[ 3.965632] e1000e: Copyright(c) 1999 - 2011 Intel Corporation.
[ 3.965664] e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 3.965673] e1000e 0000:00:19.0: setting latency timer to 64
[ 3.965772] e1000e 0000:00:19.0: irq 43 for MSI/MSI-X
[ 4.271943] e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) xx:xx:xx:xx:xx:xx
[ 4.271946] e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
[ 4.271980] e1000e 0000:00:19.0: eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
[ 7.196733] e1000e 0000:00:19.0: irq 43 for MSI/MSI-X
[ 7.248933] e1000e 0000:00:19.0: irq 43 for MSI/MSI-X
[ 10.186878] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Last edited by .:B:. (2012-01-09 21:24:59)

Similar Messages

  • Z77A-GD65 Problems with Ethernet (Intel 82579V) Code 10 and 55 error

    it is just a day with disaster. I bought Z77A-GD65 yesterday, and now it almost driver me crazy , i have two most famous problem of the board ,the CODE10 and ERROR 55!!!
    after i bought this board to home ,i spend few hour to figure out the reason why the system can not be booted.
    the DIMM SLOT 3&4 of my board is malfunction,no matter what combination i use (1&3,2&3, 3&4...etc),but it works for 1 and 2(i have 4 ram sticks,all of them is fine)
    i do upgrade to BIOS 10.5(thx god ,i have two computer ,otherwise i cant even do it because of following issue)
    after i solve the problem by only plug in 2 ram (DIMM1&2), succeed to boot up, a new problem occurred to me ,the CODE10!
    latest driver , clean system install ,cmos cleaned, does not help.
    i have read this thread for code10
    https://forum-en.msi.com/index.php?topic=158591.msg1167303#msg1167303
    and  for error55
    https://forum-en.msi.com/index.php?topic=158224.0
    it seems the best way to solve it is RMA.
    I notice that there is an Authorized Motherboard Repair Center (East Coast):
    361 Alden Road
    Markham, Ontario, L3R 3L
    i live in Toronto, can i just go there and give the board to them  to fix it or i can only mail it?
    If i need to mail it ,what should i do?

    Code 10 means the device cannot start. You have the right driver for the Intel 82579V is shorted by either a motherboard screw or a raiser under it. The ethernet adapter has lights which light up id driver is installed (even though code 10 is in effect).
    Solution: Remove 1 or 2 motherboard screws and turn the pc on. Repeat until you find out which screw caused the issue. For me it was the screw closest to the ethernet controller.
    The wa i fixed it was I was used a plastic washer and I was still able to have the motherboard screw in and at the same time not get code 10 anymore and my Intel 82579V worked fine since.

  • Unplayably bad stuttering in Unity/Mono games -- kernel regression?

    hi folks,
    I'm fairly new to Arch, so bear with me here -- I'm running Gnome 3 with gdm, on the newest kernel / mesa / etc. from pacman. i5-4300Y with haswell graphics. have had this system running for a few weeks. when I first got it, everything was working OK, except I noticed that performance was implausibly bad in a handful of steam games -- like 2-3 frames per second bad. thinking on it, this seems to be only games that make use of the Unity or Mono middleware.
    originally, I was running lightdm, and I thought it was narrowly possible that might be the issue, since I know upstream Gnome 3 doesn't really support anything other than gdm at this point. I switched to gdm, and the problem seemed to go away, but in hindsight, that might've been the same time as I updated from 3.18.2 to 3.18.3 or 3.18.4 (sorry I can't isolate this better, but I'm at least certain it was one of those).
    however, the issue has come back this week, though I noticed I'm now on 3.18.5 -- so that might be it? I guess it no longer seems like it could be a lightdm issue, since I'm still on gdm, and I don't think it's an upstream mesa issue, since I'm running git mesa (newer than the bleeding edge unstable releases in arch sources) on my Ubuntu box which also uses Intel graphics, and it's not showing any of the same issues (but it's on a 3.13 kernel).
    other games perform fine, so I don't think it's an issue with my GPU somehow underclocking itself. it's just Unity/Mono stuff. the games in question have not updated over this time period (or at least, all of them haven't updated the Unity/Mono runtimes such that this is plausibly the issue).
    any thoughts? thanks!

    Sorry to bump this thread, but I'm still having the issue -- kernel's only been bumped from 3.18.5 to 3.18.6 in the past month, so I suppose it could be a kernel regression that's still unfixed, but I'm really skeptical that this could be a kernel problem. Anyone have any thoughts? It's a mystery to me...
    I'll note that this machine is also powertopped, though the issue persists when I disable all of the powertop optimizations to test.
    Last edited by axfelix (2015-03-03 17:35:36)

  • Window 10 build 10041 does not work with Intel 82579V Gigabit Ethernet on ASUS motherboard

          
    I originally posted this question here:
    answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_update/window-10-build-10041-does-not-work-with-intel/6729892f-83aa-4822-b20a-ea84f4fd06c7
    and was asked to post it on this forum...
    I updated a computer I have which is a quad core i7 that I built and includes an ASUS motherboard with Intel 82579V Gigabit Ethernet built in. Windows 10 preview 9926 worked fine with this network adapter. Window 10 build 10041 does not, and I have tried
    it twice so far. I even went as far as buying a Thunderbolt-Gigabit Ethernet Adapter (Broadcom, sold by Apple)... and while it installed the driver automatically, it did not work either. Each time you try to view the properties of either of them, it locks
    up or give an error. In fact, doing much of anything with the Intel adapter icon assures you of not being able to do a clean reboot... have to kill power.  I have finally gone back the previous version 9926, which has its issues but no where near as bad
    as not having any network connectivity!  Does anyone have this issue and a workaround? 
    Note, there are two images on the windows 10 preview forum that I posted this question on. I could not post the full link as I was getting a message here that links and graphics are not allowed.

    Thanks Roger, I posted the following yesterday in the other thread (thinking it was this thread - confusing after they moved it here)... It may be that the new driver fixes the issue that 10041 has with it, but I have not tried that yet. If I do I will update
    this... Thanks!
    I have more information about this, which basically exonerates any issue with the Intel 82579V Gigabit Ethernet hardware or software. I have 3 computers with Windows 10 preview so I have multiple angles to see issues from. With this I have found a culprit
    (but I suspect not just the only culprit) in this above mentioned problem...
    10041 build combined with installing (or attempting to install) CISCO VPN Windows 7 64bit 5.0.07.0440-k9 client causes the issue mentioned above. I confirmed this on a completely different machine with a totally different Ethernet adapter. First machine
    is an ASUS motherboard in a tower system I built, with the Intel 82579V Gigabit Ethernet hardware built in. Second machine is a Gateway Laptop from 2008 which has a Marvell Yukon 88E8057 PCI-E Gigabit adapter built in. Build 10041 will work fine with my 2008
    laptop, including the MS VPN client (which I have tested). However, if you attempt to install or even uninstall the Cisco client you will have to do a recovery to a restore point (as I have done twice) in order to get your network working again. Installing
    or attempting to install (because it never even does install properly and times out), CISCO VPN client will render your entire network unusable. Going back to a restore point saved me and I am still running 10041 but I can't use CISCO VPN client any longer.
    I could with build 9926, including on all 3 machines. I now have 9926 on two machines and 10041 on only the 2008 laptop. 
    Hopefully this above information helps someone resolve the issue. I will also mention, even though my network is working on the 2008 laptop, I still can't go into the Control Panel\Network and Internet\Network Connections and right mouse click on the Marvell
    Yukon 88E8057 PCI-E Gigabit adapter icon. I get an error when clicking on Properties menu popup : "An unexpected error has occurred". So something is still up with my network adapter driver or windows software, but it could be a side effect of all
    that has happened with the Cisco software install attempts under 10041.
    Another note: CISCO Anyconnect also has the issue.

  • Intel 82579V network controller "This device cannot start" (code 10) error"

    I've just finished installing a Z77A-GD55 motherboard and had a problem where the Intel 82579V network controller wouldn't start after a cold boot. Device manager would show “This device cannot start" (code 10) error”.
    After a reboot it would work every time. During the time it didn't work the adapter was incorrectly shown in device manager as 82579LM. There's an older thread about this issue but the fix described there were of no help with my problem.
    After a lot of searching I found Intel has provided a fix for people having this issue after sleep mode so I gave it a try and it seems to work for my issue too, so far anyway.
    So if anyone else is having this problem with the same Intel network controller I suggest giving this try.
    Go to the Intel Download Center and search for 82579V. Select the first result entitled "NVM Update Utility for Intel® 82579V Gigabit Ethernet PHY Network Connection" and follow the instructions. Good Luck!

    Thanks for the information. 

  • Please help [Realtek LAN NIC problem]

    Hi everyone, this might be a long post but PLEASE read it if you have the time, you might just know the solution to this problem. to begin with, here is my system:
    Windows 2000 pro sp4
    AMD Athlon64 3000+
    MSI K8T Neo (BIOS rev. 1.10)
    1 GB (2x512) PC3500 Mushkin level 2 hi performance @ 2-3-2-6 timings
    Samsung SATA 160 GB hard drive
    ATI Radeon 9700 pro (catalyst 4.1)
    Lite On 52x-32x-52x IDE CD Drive
    Enermax EG465P-VE FC (460W) 3.3V/35A , 5V/35A , 12V/33A
    *There are not any other PCI cards installed.
    Now, here is the problem:
    I did not notice the problem right away, you will not notice this if you are doing normal browsing or downloads. It came to my attention while I was receiving a file on IRC (using mIRC). while I was recieving the file I noticed that, somehow, I could no longer access the internet at all (neither on IRC, http, ftp .. nothing). I tried to find out why, I couldn't. so I rebooted the system and tried to continue receiving that file ... same thing happens. after a while of digging around my system and experimenting I found that sends from certain people will cause the problem, and i simply need to restart to get back online. this will happen always whenever those certain people send me anything. so, what's going on:
    1 - Windows 2000 pro is freshly installed and up to date. i tried XP, it had the same problem; however, 2000pro is the operating system i will be using.
    2 - the client is not the problem because i tried another one and the same thing happened. I have also tested 2 other computers and they worked fine (same file .. same person). note that the download was going faster on the other 2 computers.
    3 - it is not the router because a direct link to the modem did not solve the problem. also, the other 2 computers had no problem with the router.
    4 - i tested the Realtek driver that was included on the motherboard CD as well as the updated drivers from realtek website. that also did not help.
    5 - windows reports that the device (realtek NIC adapter) is working properly and that there are no conflicts. realtek diagnostics utility also reports no problems.
    6 - Realtek's Gigabit NIC shares IRQ 16 with the radeon 9700 pro, so I figured that i could reserve some of main memory to IRQ 16 to make sure things run with maximum stability:
    on system.ini added the line -> IRQ[16] = 8192 (reserve 8MB of main memory for IRQ 16). this did not help. so i removed it.
    7 - changing the NIC setting from "auto negotiation" to "100Mbps/Full duplex" did not help either.
    8 - one time, the Realtek diagnostics utility was able to reload the device driver, and of course, i was able to go online without restarting. this happened only once. note that I tried to unload/reload the device through device manager many times but i always failed and then i have to press the power switch or reset button to actually reboot. normal windows shutdown/reboot is not possible. the same thing happens when Realtek's diagnostics finishes a test and tries to reload the driver (remember, it only succeeded once).
    9 - system logs do not seem to report any problem. i even tried using inspectr.exe to try and find the reason for the driver crash but no crash was detected.
    10- disabling the IEEE 1394 controller did not help.
    it is obvious that there is something wrong with the driver, but there is a possibility it could be the board/device. if the driver is "flakey", it will mess up. if the device/chip/board is not working properly, then the driver will get stuck just as well.
    so, the solution?
    I- Hit the wall with my head 7 times (2-3-2) then roll on the ground for a few minutes .. get up and hit the wall 13 more times (2-3-2-6) and then roll on the ground and sleep.
    or
    II- burn it all .. yes ... BURN IT ALL. MOAHAHAHAHAH!!!
    or
    III- RMA board or change it :(
    I'm trying to decide whether it is the board or if it is the driver. I'm trying to find any excuse not to RMA or change the board. I will be installing linux, and networking is important to get rest of the files I need. I really would like not to rely on flakey hardware or driver. if it is the chip, i have to RMA. if it is the driver, change MB or get a NIC card and install it until realtek decides that it is a good idea to fix the driver.
    i tried to check realtek's website but there was very little or no real helpful information to the end user (either that, or i was too upset to find the info i need on their website). I wish they had a forum like this one.
    That is basically what i was thinking about .. of course, i could be wrong and the solution might be simple (i wish).
    any suggestions, tweaks, patches, information that you guys know about are appreciated and may be of great help. Are there any setting in the BIOS that i need to set in some way to make sure this works properly? would the new BIOS revision 1.20 fix this?
    I apologize for the lengthy post. I believe that I've managed to fry whatever brain cells I had left over the past few days. So,  I apologize for any spelling/grammer mistakes
    thank you in advance

    Blaming every problem on the MSI K8T NEO FSR on a 350w power source is utter crap!  
    Why would ANY Computer hardware shops even SELL SYSTEMS on a 350w powersource on the thousands if a 350watt power source wouldnt be enough for the motherboard, what you are saying that hundreds of HW stores are just saying FU to every customer they sell a computer unit WHICH COMES PRE-EQUIPPED with a 350W powersource!!! I've seen various configurations using a 350w power source working just fine!
    I simply DO NOT believe that the system aint getting enough power, that's bull! This would cause considerable UNSTABILITIES and other problems on the system besides dysfunctional S-ATA Hard drives and NIC problems, eg. like artifacts while playing games, crackling in audio, bluescreens and other symptoms!
    I just noticed today that my on board NIC had jammed while downloading Torrent files, had to reboot my cable modem, this could be nothing and could simply be an ISP matter, or it could be that my K8T NEO FSR also has a problem with the NIC, again i stress that i havent done really any testing so this raving could be about nothing.
    I solved my S-ATA problem by changing back to a similiar IDE 8MB cache 7200 rpm Samsung 160 GB drive. No problems what so ever with register / file corruption! I've also been in contact with VIA who are currently investigating problems with the 8237 Southbridge controller equipped motherboards like the K8T NEO FSR (http://www.viaarena.com -> forums)

  • Z77A-GD65 intel 82579v code 10..

    Hello..
    Korea because I'm not good at English.
    To Z77A-GD65. Something else rather than intel 82579v due to an error code 10 is crazy right before ..
    Left did not have to install the new driver, the only way to change the BIOS, seriously, do I know you yihyeonsang resolve BIOS version?

    Please read this thread
    https://forum-en.msi.com/index.php?topic=158591.0

  • Z77A-GD65 Problems with Ethernet (Intel 82579V) Code 10

    Hi,
    on a fresh install of Windows 7 64bit i cannot make the Ethernet port on the motherboard work. It installs fine, but when i check device manager i see this message:
    This device cannot start. (Code 10)
    I downloaded the latest driver, but still no change.
    Looking in device manager, i noticed that the driver Windows had selected was Intel 82579LM, so i reinstalled the driver, and forced 82579V driver, but still no change. I assumed this must be a defect motherboard, so i rma'd it, and got a new one....with the same problem!!!
    So any ideas with to do ?

    Quote from: Warner on 11-May-12, 04:10:22
    Hello kaizerman,
    Are you in the US?
    Can you send the motherboard to me directly for analysis?
    If needed, I will replace the board for you through RMA service.
    Please email me at [email protected] but be sure to put my name in the subject field and your board model so it will come to me correctly.
    Sincerely,
    Warner
    Hi Warner
    Thanks for the reply. Unfortunately i'm not not in the US, i'm in In South Africa. Ive tried pro17 with no success... currently its showing the 82579V driver. but no still has the cannot start error code 10. I cant understand why it was working for a few days. then suddenly stopped. i made no hardware or software changes.
    regards
    Utterly perturbed 

  • Problems with Intel 4965AGN and iwlagn kernel module

    Hi everyone.
    I having a couple of issues since my last kernel upgrade (2.6.27.5-1) and wanted to check if its my problem or if it is some kind of bug, before reporting it to the tracker.
    I have the iwlagn (or iwl4965, as it is the same) kernel module in the MODULES array in /etc/rc.conf. Even tried removing it from there and leaving all the work to the module autodetect. No changes.
    This is my dmesg | grep iwl output after boot:
    iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks
    iwlagn: Copyright(c) 2003-2008 Intel Corporation
    iwlagn 0000:0b:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    iwlagn 0000:0b:00.0: setting latency timer to 64
    iwlagn: Detected Intel Wireless WiFi Link 4965AGN REV=0x4
    iwlagn: Tunable channels: 11 802.11bg, 13 802.11a channels
    iwlagn 0000:0b:00.0: PCI INT A disabled
    phy0: Selected rate control algorithm 'iwl-agn-rs'
    iwlagn: Failed to register hw (error -2)
    iwlagn: probe of 0000:0b:00.0 failed with error -2
    I do have the firmaware (iwlwifi-4965-ucode) installed and enabled "firmware" in the mkinitcipio.conf image.
    I have to do the following to get it working:
    modprobe -r iwlagn
    modprobe iwlagn
    After which the output of dmesg | grep iwl is the following (added a line to split the reload of the module):
    iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks
    iwlagn: Copyright(c) 2003-2008 Intel Corporation
    iwlagn 0000:0b:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    iwlagn 0000:0b:00.0: setting latency timer to 64
    iwlagn: Detected Intel Wireless WiFi Link 4965AGN REV=0x4
    iwlagn: Tunable channels: 11 802.11bg, 13 802.11a channels
    iwlagn 0000:0b:00.0: PCI INT A disabled
    phy0: Selected rate control algorithm 'iwl-agn-rs'
    iwlagn: Failed to register hw (error -2)
    iwlagn: probe of 0000:0b:00.0 failed with error -2
    ///////////////////// this is added after reload of iwlagn ///////////////
    iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks
    iwlagn: Copyright(c) 2003-2008 Intel Corporation
    iwlagn 0000:0b:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    iwlagn 0000:0b:00.0: setting latency timer to 64
    iwlagn: Detected Intel Wireless WiFi Link 4965AGN REV=0x4
    iwlagn: Tunable channels: 11 802.11bg, 13 802.11a channels
    phy0: Selected rate control algorithm 'iwl-agn-rs'
    iwlagn 0000:0b:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    firmware: requesting iwlwifi-4965-2.ucode
    Registered led device: iwl-phy0:radio
    Registered led device: iwl-phy0:assoc
    Registered led device: iwl-phy0:RX
    For what i can tell... the module seems to be loading to soon. Could this be the problem?
    On the other hand, it happened a couple of times that I just lost the device (the module quit working in the middle of a session).
    Any ideas?
    ps. I already reinstalled the previous kernel without results. Remade the kernel26.img changing options (HOOKS) and modified the order of services in the DAEMONS array, to no avail.

    Nope. I'm still having problems.
    Replaced NetworkManager with ntcfg2, but no changes so far.
    Here is the kernel package I have installed:
    core/kernel26 2.6.27.6-1 (x86-64)
    Keep having to reload the module:
    modprobe -r iwlagn
    modprobe iwlagn
    Output from dmesg | grep iwlagn seems to be the same:
    [23:06:57 crow]$ dmesg | grep iwl
    sda:<6>iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks
    iwlagn: Copyright(c) 2003-2008 Intel Corporation
    iwlagn 0000:0b:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    iwlagn 0000:0b:00.0: setting latency timer to 64
    iwlagn: Detected Intel Wireless WiFi Link 4965AGN REV=0x4
    iwlagn: Tunable channels: 11 802.11bg, 13 802.11a channels
    iwlagn 0000:0b:00.0: PCI INT A disabled
    phy0: Selected rate control algorithm 'iwl-agn-rs'
    iwlagn: Failed to register hw (error -2)
    iwlagn: probe of 0000:0b:00.0 failed with error -2
    iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks
    iwlagn: Copyright(c) 2003-2008 Intel Corporation
    iwlagn 0000:0b:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    iwlagn 0000:0b:00.0: setting latency timer to 64
    iwlagn: Detected Intel Wireless WiFi Link 4965AGN REV=0x4
    iwlagn: Tunable channels: 11 802.11bg, 13 802.11a channels
    phy0: Selected rate control algorithm 'iwl-agn-rs'
    iwlagn 0000:0b:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    firmware: requesting iwlwifi-4965-2.ucode
    Registered led device: iwl-phy0:radio
    Registered led device: iwl-phy0:assoc
    Registered led device: iwl-phy0:RX
    Registered led device: iwl-phy0:TX
    My loaded modules: lsmod
    [23:12:15 crow]$ lsmod | grep iwl
    iwlagn 102148 0
    iwlcore 86084 1 iwlagn
    rfkill 12068 2 iwlcore
    led_class 6408 1 iwlcore
    mac80211 182184 2 iwlagn,iwlcore
    cfg80211 29840 3 iwlagn,iwlcore,mac80211
    On the other hand, I found someone with the same problem in the Poland Arch Linux Forums:
    http://forum.archlinux.pl/viewtopic.php?pid=31341
    But I dont understand if the second person is giving its setup (and has it working) or if it is reporting problems too.
    No one else is having issues with this wireless card?

  • Ethernet problem (Intel 82579V)

    Hello,
    got a laptop which doesn't recognize the ethernet driver properly (yellow exclamation mark). It's disconnected, ethernet cannot be used. Driver is showing a code 10 error ('this device cannot start').
    The eventlog id: 24
    source: e1cexpress
    Uninstalled the driver and tryed the hp listet network driver (v12.2.45.5033) as well as the latest original driver from Intels website (v19.5.303.0). Also unpacked the Intel-exe and installed it manually via hardware manager.
    Hardware-IDs:
    PCI\VEN_8086&DEV_1503&SUBSYS_17AB103C&REV_04
    PCI\VEN_8086&DEV_1503&SUBSYS_17AB103
    PCI\VEN_8086&DEV_1503&CC_020000
    PCI\VEN_8086&DEV_1503&CC_0200
    Any suggestions?
    BR
    Michael

    Hi,
    Please download the right version (32bit or 64bit) and install on your computer:
         https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18713&lang=eng&OSVersion=Windows%207...
    Regards.
    BH
    **Click the KUDOS thumb up on the left to say 'Thanks'**
    Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

  • How do I add an undetected Intel 82559 NIC to my Sparc Solaris 9 install?

    All,
    I bought a combo LSI SCSI and Intel NIC card for my Ultra 5. I'm running Solaris 9 9/04. The card was added after the os was installed. The OS is currently using the hme0 adapter detected on the system but I need to multi-home this system.
    first I did a "touch /reconfigure" and a "boot -r" when that failed. Then I checked the net and found the driver ought to be iprb. according to the manpage for iprb, there should be a /kernel/drv/iprb entry but there is none on my system. I tried to `devfsadm -i iprb` anyhow but I got a "failed to attach" although that's the right driver. I suspect that some magic is needed in /etc/devlink.tab
    So The card is not detected but prtconf seems to see it as an network device. I'm at a loss on how to proceed to get the nic recognized. The scsi is working just fine. Here is what I know:
    -- begin `prtconf -vp` snippit
    Node 0xf0083784
    assigned-addresses: 81032010.00000000.00001000.00000000.00000100.82032014.00000000.00100000.00000000.00000100.82032018.00000000.00102000.00000000.00001000.82032030.00000000.00120000.00000000.00020000
    reg: 00032000.00000000.00000000.00000000.00000000.01032010.00000000.00000000.00000000.00000100.02032014.00000000.00000000.00000000.00000100.02032018.00000000.00000000.00000000.00001000.02032030.00000000.00000000.00000000.00020000
    compatible: 'pci1000,c.2' + 'pci1000,c' + 'pciclass,010000' + 'pciclass,0100'
    name: 'scsi'
    devsel-speed: 00000001
    class-code: 00010000
    interrupts: 00000001
    max-latency: 00000040
    min-grant: 0000001e
    revision-id: 00000002
    device-id: 0000000c
    vendor-id: 00001000
    Node 0xf00839e4
    assigned-addresses: 81032810.00000000.00001400.00000000.00000080.82032814.00000000.00140000.00000000.00000400.82032830.00000000.00180000.00000000.00040000
    reg: 00032800.00000000.00000000.00000000.00000000.01032810.00000000.00000000.00000000.00000080.02032814.00000000.00000000.00000000.00000400.02032830.00000000.00000000.00000000.00040000
    compatible: 'pci1011,19.1011.500b.41' + 'pci1011,19.1011.500b' + 'pci1011,500b' + 'pci1011,19.41' + 'pci1011,19' + 'pciclass,020000' + 'pciclass,0200'
    name: 'ethernet'
    fast-back-to-back:
    devsel-speed: 00000001
    class-code: 00020000
    interrupts: 00000001
    max-latency: 00000028
    min-grant: 00000014
    subsystem-vendor-id: 00001011
    subsystem-id: 0000500b
    revision-id: 00000041
    device-id: 00000019
    vendor-id: 00001011
    --end `prtconf -vp` snippit
    Please let me know if more detail is needed, which man page to read or how else to proceed.
    Thanks!!

    All,
    I've found the problem. It seems that Solaris 9 does not ship a driver for this. Anyhow, I found a GPL driver at:
    http://homepage2.nifty.com/mrym3/taiyodo/eng/
    Use the "tu" driver. Although the chip is clearly marked as an Intel 82559 it responds to the tu (DEC Chip 211x) and not the Intel ife driver.
    So that others can find this solution, I have added these keywords:
    lsi IntraServer ITI-6110U2-X
    Ebay combo Ultra2 SCSI NIC
    LSI/Sun Dual Ultra2-LVD/SE SCSI Ethernet Combo PCI Card

  • Kvm-intel module broken after kernel upgrade 3.8.11-1 - 3.9.4-1

    Hey guys,
    since todays update kvm is no longer working on my pretty old intel CPU.
    I'm getting the usual from "qemu -enable-kvm":
    KVM: entry failed, hardware error 0x80000021
    A downgrade to 3.8.11-1 made it work again.
    I load the module as followed:
    modprobe kvm-intel emulate_invalid_guest_state=0
    Anyone having the same issue?
    Here the output of lscpu and /proc/cpuinfo:
    $ lscpu
    Architecture: i686
    CPU op-mode(s): 32-bit
    Byte Order: Little Endian
    CPU(s): 2
    On-line CPU(s) list: 0,1
    Thread(s) per core: 1
    Core(s) per socket: 2
    Socket(s): 1
    Vendor ID: GenuineIntel
    CPU family: 6
    Model: 14
    Model name: Genuine Intel(R) CPU T2400 @ 1.83GHz
    Stepping: 8
    CPU MHz: 1000.000
    BogoMIPS: 3659.99
    Virtualization: VT-x
    L1d cache: 32K
    L1i cache: 32K
    L2 cache: 2048K
    $ cat /proc/cpuinfo
    processor : 0
    vendor_id : GenuineIntel
    cpu family : 6
    model : 14
    model name : Genuine Intel(R) CPU T2400 @ 1.83GHz
    stepping : 8
    microcode : 0x39
    cpu MHz : 1000.000
    cache size : 2048 KB
    physical id : 0
    siblings : 2
    core id : 0
    cpu cores : 2
    apicid : 0
    initial apicid : 0
    fdiv_bug : no
    hlt_bug : no
    f00f_bug : no
    coma_bug : no
    fpu : yes
    fpu_exception : yes
    cpuid level : 10
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon bts aperfmperf pni monitor vmx est tm2 xtpr pdcm dtherm
    bogomips : 3659.99
    clflush size : 64
    cache_alignment : 64
    address sizes : 32 bits physical, 32 bits virtual
    power management:
    processor : 1
    vendor_id : GenuineIntel
    cpu family : 6
    model : 14
    model name : Genuine Intel(R) CPU T2400 @ 1.83GHz
    stepping : 8
    microcode : 0x39
    cpu MHz : 1000.000
    cache size : 2048 KB
    physical id : 0
    siblings : 2
    core id : 1
    cpu cores : 2
    apicid : 1
    initial apicid : 1
    fdiv_bug : no
    hlt_bug : no
    f00f_bug : no
    coma_bug : no
    fpu : yes
    fpu_exception : yes
    cpuid level : 10
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon bts aperfmperf pni monitor vmx est tm2 xtpr pdcm dtherm
    bogomips : 3659.99
    clflush size : 64
    cache_alignment : 64
    address sizes : 32 bits physical, 32 bits virtual
    power management:

    Also, you can rebuild the kernel package(linux and linux-headers) using the given patch
    The problem mentioned by perseus, discussed in the topic Linux 3.15: WLAN regression on WRL54GL/B43
    This method is slower and more difficult, but allows you to get the latest working kernel. You do not need to downgrade version of b43-firmware.
    To do this you need to put the patch in a file called fix-b43-frequency-detection-bug.patch edit PKGBUILD as described below and rebuild the package.
    --- a/drivers/net/wireless/b43/xmit.c
    +++ b/drivers/net/wireless/b43/xmit.c
    @@ -811,9 +811,13 @@ void b43_rx(struct b43_wldev *dev, struct sk_buff *skb, const void *_rxhdr)
    break;
    case B43_PHYTYPE_G:
    status.band = IEEE80211_BAND_2GHZ;
    - /* chanid is the radio channel cookie value as used
    - * to tune the radio. */
    - status.freq = chanid + 2400;
    + /* Somewhere between 478.104 and 508.1084 firmware for G-PHY
    + * has been modified to be compatible with N-PHY and others.
    + */
    + if (dev->fw.rev >= 508)
    + status.freq = ieee80211_channel_to_frequency(chanid, status.band);
    + else
    + status.freq = chanid + 2400;
    break;
    case B43_PHYTYPE_N:
    case B43_PHYTYPE_LP:
    ➜ linux diff /var/abs/core/linux/PKGBUILD ~/tmp/linux/PKGBUILD
    9c9
    < pkgrel=1
    > pkgrel=2
    22a23
    > 'fix-b43-frequency-detection-bug.patch'
    30c31,32
    < '79359454c9d8446eb55add2b1cdbf8332bd67dafb01fefb5b1ca090225f64d18')
    > '79359454c9d8446eb55add2b1cdbf8332bd67dafb01fefb5b1ca090225f64d18'
    > '0debdba07be9061e030a4c6d20bdd42934ada227c168e9a10f1baab1da8e41d9')
    52a55,57
    > # fix b43 G-PHY frequency
    > patch -Np1 -i "${srcdir}/fix-b43-frequency-detection-bug.patch"
    >
    305c310,311
    < '79359454c9d8446eb55add2b1cdbf8332bd67dafb01fefb5b1ca090225f64d18')
    > '79359454c9d8446eb55add2b1cdbf8332bd67dafb01fefb5b1ca090225f64d18'
    > '0debdba07be9061e030a4c6d20bdd42934ada227c168e9a10f1baab1da8e41d9')

  • What's the deal with Intel and the new kernel?

    Hi
    I have trouble understanding the whole deal behind Intel's video drivers and the new kernel. What doesn't work and why? Could someone please try to explain what the problem is in a way so that a newbie like me can understand it?
    Thanks

    Intel and Linux are transitioning to a new graphics system. We're in the middle of the transition, so everything's kinda suckish right now. Old kernel and drivers are better, development kernel and drivers are almost as good, and they will get much better soon.
    www.phoronix.com for up-to-date info.

  • Any advice on mixing broadcom and intel iscsi nics between hyper-v hosts?

    Hello,
    Way back in 2008 when we configured our virtualized datacenter (used Virtual Iron, now defunct) it was recommended practice to use identical iscsi cards for all hostnodes.  We have since migrated to hyper-v 2008 r2, and are now moving on to hyper-v
    2012 r2.  We are currently spec'ing out a new hostnode, and I'm looking for advice on whether it's still the recommended practice to keep all iscsi cards as similar as possible. 
    The hosts will be connected to a MD3220i SAN.
    The reason I'm asking is because we currently use Broadcom's 5709c's in all our hosts.  They have had their problems, so I'd like to move away from them.  Right now I have my eye on the Intel i350's.  It's a choice between the two since those
    are the only affordable offers we have.  I did a quick search online and found that Intel iscsi cards are much preferred over Broadcoms.  It's not in our budget to switch out all existing cards with intel's, so I'm wondering if it's now considered
    relatively safe practice to let iscsi cards from different manufacturers play together, since the technology has become more mature.  Any advice would be welcome.
    Thanks in advance

    Yes, it is still a recommended practice to use the same vendor for critical components across the cluster.  But it is not a requirement. It is recommended to use common hardware because management/troubleshooting is easier. If there is a networking
    problem and you are using two different vendors, which one is NOT going to say to contact the other vendor because, of course, it is not 'my' problem.
    You will also get some warnings in the cluster validation wizard.  These are warnings, so they don't prevent the building of the cluster, but they are warnings for good reason.
    Anytime you have two different vendors, that is going to be a potential point of problem when you need to debug.  And because neither vendor is likely to test their environment with the other vendor's products, they may say they don't support the configuration
    you are trying to put together.  So even though the validation wizard accepts it with warnings, you may end up with something that is unsupported by the NIC vendors.  Ask them what their stance is.
    . : | : . : | : . tim

  • C220M3 and Intel I350T NIC

    I've got a C220 M3 and I'm trying to add an Intel I350T quad port NIC to the server.
    If I just plug in the NIC into the second PCIe slot, the server doesn't complete POST - it hangs after displaying the messages from the onboard NICs. (The server has two CPUs so I can use this second slot)
    If I remove the RAID card from slot 1 and put the NIC into slot 1, the server does complete POST and I see all six network ports during the server POST.
    What do I need to do for the server to accept this NIC in slot 2?
    GTG

    My Cisco branded Intel i350 arrived yesterday. Sure enough, the C220M3 starts up with that in, but just refuses to start up with the genuine Intel card in. Comparing the two cards, the hardware looks identical. Looking at the firmware, the Cisco branded card has a different firmware on it: The Cisco firmware supports more features than the generic Intel firmware.
    I'm guessing the server is refusing to complete POST as it's trying to ask the card for the missing modules but is crashes when the modules don't exist.
    Any suggestions on how to load the extra modules?
    I tried doing a backup/restore of the firmware between the cards but the Intel tools wouldn't let me. I also extracted the Intel NIC firmware from the UCS firmware update CD and applied that. The problem is, is that Intel's firmware upgrade tools only allow you to install two features, and Cisco's version of the card has four/five features installed.
    GTG

Maybe you are looking for

  • Is there a way to access my iTunes library that's stored on my Mac Mini Server at home over the internet while I'm away on business?

    Hello. I've done a bit of searching on Google and have come up empty so far and am looking for your help. Here's my situation: I have my iTunes media files stored on my NAS on my home network along with my Mac Mini Server with the iTunes library file

  • Updating AP Invoice Question

    Hi, I am trying to write code to update an existing AP Invoice and cannot get it working. Basically the code I am using is: Dim itemCode As String             REM set the item code             itemCode = "P-0004-SAP001-2" 'Not sure where to get this

  • Turning on/off the flash while is recording a video in iOS 6 with an iPhone 4?

    As the title says, from iOS 6 the turn on and turn off flash while I'm recording a video is gone. I have an iPhone 4, but I think the problem is with the iPhone 4S too. Could someone confirm that is a "new feature" of the magical and beautiful iOS 6?

  • PL/SQL dynamic insert using cursor

    Hello all, I'm having big performance issues with (as you'll see below, a very simple) stored procedure. Any hints/suggestions would be really appreciated. Query below in the Loop is used to create a list of all months that fall within a member's sta

  • Signing Client up for BC usage

    Hi everyone, This is my first post in here I am a full CC 2014 member and I am building a website in Muse and hosting it on BC for a client. I am also building my OWN new site to be hosted on BC and have a couple of questions; Firstly, I see in the D