New Intel 82579v network port Linux driver for Fedora?

[Jeff72]

I just got a new Sandy Bridge motherboard which comes with a single Intel 82579v network port adapter.

Does anyone know a way to make the Intel 82579v network port work with Linux on Fedora 14?

I tried finding an Intel Linux driver online for it but no luck so far.

Will the RPM Fusion kmod-staging help me out? I read something online about it may have the newer kernel drivers available for the Fedora kernel, but not familiar with how that works.

Any help would be appreciated.

Thanks,

Jeff

[stevea]

Could you please post the PCI ID numbers from "lspci -nnk", like:

03:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit Network Connection [8086:10d3]
Subsystem: Intel Corporation Gigabit CT Desktop Adapter [8086:a01f]
Kernel driver in use: e1000e
Kernel modules: e1000e



Unrelated to your problem, but how far can you overclock that CPU ? Which mobo ?

[Jeff72]

Originally Posted by stevea

Could you please post the PCI ID numbers from "lspci -nnk", like:

03:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit Network Connection [8086:10d3]
Subsystem: Intel Corporation Gigabit CT Desktop Adapter [8086:a01f]
Kernel driver in use: e1000e
Kernel modules: e1000e



Unrelated to your problem, but how far can you overclock that CPU ? Which mobo ?

8086:1503 (rev 04)

I just did a fresh install of Fedora 14 and without the LAN connection I have not updated yet.

I did just see this Debian site that had some info: http://ircbots.nanonanonano.net/factoid.php?key=82579v

I found this Intel Ethernet driver site, can this work? http://sourceforge.net/projects/e1000/

I was hoping that there was an easy driver package I could just USB drive to the new system and install and be good...either that or a kernel update that added the driver support?


I have the Asus P8P67 PRO motherboard. I have had some issues so far and found out 1 of my 4 DIMMs was bad. Running fairly smoothly on 2 DIMMs (4 GB) now. I still am having some BIOS bootup issues on occasion and not sure if it is the memory or what causing it. This Mushkin 996805 memory runs at 1600 MHz and this motherboards BIOS doesn't seem fully stable yet.

I have an Intel Core i5-2500K CPU with it, but because of all my memory issues over the last couple days i've not ventured into overclocking the CPU yet.

[DBelton]

the e1000e drivers should support the 82579v. It was initially added back in september of last year. But that driver is included in Fedora. It just might not be a late enough version to have your network adapter in it. I wonder if the e1000e driver in koji would have the additions for the 82579v in it.

[stevea]

I suspect it will me [8086:1C33] for the part id.

---------- Post added at 02:05 PM ---------- Previous post was at 02:04 PM ----------

*IF* you tell me the PCI ID - then I can tell you whih kernels supports it.

[stevea]

The driver fix for for 8086:1503 does not exist in the most recent F14 kernel. kernel-2.6.35.10-74
The pacth for this device was added just as 2.6.35 was closed.
So you'll need a 2.6.36 kernel.

The Fedora koji kernel *should* have what you need.
http://koji.fedoraproject.org/koji/b...buildID=208434
or
http://koji.fedoraproject.org/koji/b...buildID=213137
or any of the successful 2.6.36 or 2.6.37 kernels at ... (last pages)
http://koji.fedoraproject.org/koji/p...rt=0#buildlist

---------- Post added at 03:05 PM ---------- Previous post was at 03:01 PM ----------

Just select the proper kernel rpm and have the installer manage the package, then reboot.
You may as well install the kernel-devel and kernel-headers too.

[Panther505]

Jeff72,

If you do an install of the drivers from here:

http://sourceforge.net/projects/e100...stable/1.2.20/

Pull it, untar it, and to a make install in the src dir. Following a reboot that had me up and running on the same Asus board in about 10 minutes. I got the pointers from the debian factoids that you had linked.

Hope that you like the board, I got mine today and booted a prior Core Duo Quad Core install on it and the only thing that Linux puked up was the eth driver...

Panther505

[Jeff72]

Originally Posted by Panther505

Jeff72,

If you do an install of the drivers from here:

http://sourceforge.net/projects/e100...stable/1.2.20/

Pull it, untar it, and to a make install in the src dir. Following a reboot that had me up and running on the same Asus board in about 10 minutes. I got the pointers from the debian factoids that you had linked.

Hope that you like the board, I got mine today and booted a prior Core Duo Quad Core install on it and the only thing that Linux puked up was the eth driver...

Panther505

That worked great! Thanks!

By the way, how the heck did you know that the e1000e driver was applicable to the 82579v chip from this link:
http://sourceforge.net/projects/e1000/files/

What is that default ixgbevf driver they show on the front page to download for?

---------- Post added at 01:30 AM ---------- Previous post was at 12:45 AM ----------

FYI,

I posted a quick HOWTO guide for how I got this working at this link
forums.fedoraforum.org/showthread.php?t=257701

Thanks again Panther505!

---------- Post added at 02:01 AM ---------- Previous post was at 01:30 AM ----------

Originally Posted by Panther505

Jeff72,

Hope that you like the board, I got mine today and booted a prior Core Duo Quad Core install on it and the only thing that Linux puked up was the eth driver...

Panther505

The Asus P8P67 PRO is good but I did run into a couple issues. One was 1 bad DIMM module out of 4 that was tough to figure out because memtest86+ before 4.20b do not support this board it seems and would just lockup. Once I got memtest86+ 4.20b Beta, then I found the bad DIMM.

The Asus P8P67 PRO also has a BIOS issue that I resolved now and documented the fix for at the following link: http://mushkingames.com/phpbb2/viewt...hp?f=3&t=17934

I am happy with the system right now though, but working with the latest and greatest hardware takes some patience.

[akronis]

I have a centos 5.5 installation with the same problem, this driver solve my problem , is compatible with my centos ?

How is the procedure to install de driver ( iam no a expert linux admin )

Thanks in advance