Greetings. HP claims RHEL 4 supports their servers with the Intel 3000 and 5000 chipsets. Has anyone had any trouble/success building machines that use this?
For example, CentOS 4.4 on http://www.supermicro.com/products/system/1U/5015/SYS-5015M-T+.cfm
Thx. Mike
On Fri, 9 Feb 2007 at 11:53am, Mike wrote
Greetings. HP claims RHEL 4 supports their servers with the Intel 3000 and 5000 chipsets. Has anyone had any trouble/success building machines that use this?
For example, CentOS 4.4 on http://www.supermicro.com/products/system/1U/5015/SYS-5015M-T+.cfm
I'm running CentOS4 on several X7DVL-E motherboardas (5000V chipset). Most stuff works well (put the SATA in AHCI mode). The one caveat was that while the stock e1000 driver will somewhat work with the onboard NICs, it'll randomly decide to stop moving packets about. An upgrade to the most recent driver from Intel (7.3.20) fixed that.
On Feb 9, 2007, at 14:59, Joshua Baker-LePain wrote:
The one caveat was that while the stock e1000 driver will somewhat work with the onboard NICs, it'll randomly decide to stop moving packets about. An upgrade to the most recent driver from Intel (7.3.20) fixed that.
I apologize for hijacking this thread, but I've been meaning to ask this question for a while now. I suspect that the e1000 driver in CentOS 4.4 is the culprit for at least some of the strange hangs I have been seeing. What is the recommended way to install the latest e1000 driver on a CentOS system?
Alfred
On Fri, 9 Feb 2007 at 3:16pm, Alfred von Campe wrote
On Feb 9, 2007, at 14:59, Joshua Baker-LePain wrote:
The one caveat was that while the stock e1000 driver will somewhat work with the onboard NICs, it'll randomly decide to stop moving packets about. An upgrade to the most recent driver from Intel (7.3.20) fixed that.
I apologize for hijacking this thread, but I've been meaning to ask this question for a while now. I suspect that the e1000 driver in CentOS 4.4 is the culprit for at least some of the strange hangs I have been seeing. What is the recommended way to install the latest e1000 driver on a CentOS system?
Well, I don't know about recommended, but what I do is:
o Download driver from intel.com o unpack and compile (a simple make in the src/ directory works) o cd /lib/modules/2.6.9-42.0.8.ELsmp/kernel/drivers/net/e1000/ o mv e1000.ko e1000.inst o cp /path/to/newly/compiled/e1000.ko . o depmod -a o reboot
I'm sure someone will now post a far more elegant solution.
On Feb 9, 2007, at 5:19 PM, Joshua Baker-LePain wrote:
On Fri, 9 Feb 2007 at 3:16pm, Alfred von Campe wrote
On Feb 9, 2007, at 14:59, Joshua Baker-LePain wrote:
The one caveat was that while the stock e1000 driver will somewhat work with the onboard NICs, it'll randomly decide to stop moving packets about. An upgrade to the most recent driver from Intel (7.3.20) fixed that.
I apologize for hijacking this thread, but I've been meaning to ask this question for a while now. I suspect that the e1000 driver in CentOS 4.4 is the culprit for at least some of the strange hangs I have been seeing. What is the recommended way to install the latest e1000 driver on a CentOS system?
Well, I don't know about recommended, but what I do is:
o Download driver from intel.com o unpack and compile (a simple make in the src/ directory works) o cd /lib/modules/2.6.9-42.0.8.ELsmp/kernel/drivers/net/e1000/ o mv e1000.ko e1000.inst o cp /path/to/newly/compiled/e1000.ko . o depmod -a o reboot
I'm sure someone will now post a far more elegant solution.
Actually, the e1000 driver tarballs include spec files that will create some very clean RPMs. Just run "rpmbuild -tb <driver tarball>", install the freshly produced RPM, and it should handle all of the above steps for you.
-- Joshua Baker-LePain Department of Biomedical Engineering Duke University _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
William Dinkel Chief Technology Officer Team HPC http://www.teamhpc.com wdinkel@teamhpc.com 1-866-TEAMHPC
On Fri, 9 Feb 2007 at 5:39pm, William Dinkel wrote
On Feb 9, 2007, at 5:19 PM, Joshua Baker-LePain wrote:
I'm sure someone will now post a far more elegant solution.
Actually, the e1000 driver tarballs include spec files that will create some very clean RPMs. Just run "rpmbuild -tb <driver tarball>", install the freshly produced RPM, and it should handle all of the above steps for you.
See?
(Thanks. ;)
On Feb 9, 2007, at 18:39, William Dinkel wrote:
Actually, the e1000 driver tarballs include spec files that will create some very clean RPMs. Just run "rpmbuild -tb <driver tarball>", install the freshly produced RPM, and it should handle all of the above steps for you.
OK, I'll give that a try next week when I'm back in the office. Just to make sure, installing the new RPM will not cause any problems down the road? The original e1000 driver kernel module is part of the kernel RPM -- will there be any warnings or errors if I try to uninstall an older kernel RPM at a later date?
# rpm -qf /lib/modules/2.6.9-42.0.3.EL/kernel/drivers/net/e1000/ e1000.ko kernel-2.6.9-42.0.3.EL
Thanks, Alfred
On Feb 9, 2007, at 5:54 PM, Alfred von Campe wrote:
On Feb 9, 2007, at 18:39, William Dinkel wrote:
Actually, the e1000 driver tarballs include spec files that will create some very clean RPMs. Just run "rpmbuild -tb <driver tarball>", install the freshly produced RPM, and it should handle all of the above steps for you.
OK, I'll give that a try next week when I'm back in the office. Just to make sure, installing the new RPM will not cause any problems down the road? The original e1000 driver kernel module is part of the kernel RPM -- will there be any warnings or errors if I try to uninstall an older kernel RPM at a later date?
Thankfully the e1000 RPM makes a backup of any existing e1000.ko files, and will return to the original module upon removal of the e1000 RPM. Just make sure you remove the e1000 RPM before you start playing with the kernel RPMs and things should be fine. Rebuilding e1000 for a different kernel is as easy as running rpmbuild again.
On a side note, the e100 tarballs behave in exactly the same fashion, if anyone needs to update your 10/100 driver.
# rpm -qf /lib/modules/2.6.9-42.0.3.EL/kernel/drivers/net/e1000/ e1000.ko kernel-2.6.9-42.0.3.EL
Thanks, Alfred
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
William Dinkel Chief Technology Officer Team HPC http://www.teamhpc.com wdinkel@teamhpc.com 1-866-TEAMHPC
On Feb 9, 2007, at 19:04, William Dinkel wrote:
Thankfully the e1000 RPM makes a backup of any existing e1000.ko files, and will return to the original module upon removal of the e1000 RPM. Just make sure you remove the e1000 RPM before you start playing with the kernel RPMs and things should be fine. Rebuilding e1000 for a different kernel is as easy as running rpmbuild again.
Excellent, thanks for the information. I will definitely try this out next week. One follow up question. How do you specify what kernel version you want to build against/install into when executing the rpmbuild? I assume that the default is the running kernel?
Alfred
On Feb 9, 2007, at 7:08 PM, Alfred von Campe wrote:
On Feb 9, 2007, at 19:04, William Dinkel wrote:
Thankfully the e1000 RPM makes a backup of any existing e1000.ko files, and will return to the original module upon removal of the e1000 RPM. Just make sure you remove the e1000 RPM before you start playing with the kernel RPMs and things should be fine. Rebuilding e1000 for a different kernel is as easy as running rpmbuild again.
Excellent, thanks for the information. I will definitely try this out next week. One follow up question. How do you specify what kernel version you want to build against/install into when executing the rpmbuild? I assume that the default is the running kernel?
It should build modules for all subversions of the currently running kernel (up, smp, hugemem, etc.). Unfortunately, I don't see a provision in the spec file for passing a different kernel version to rpmbuild on the command line.
William Dinkel Chief Technology Officer Team HPC http://www.teamhpc.com wdinkel@teamhpc.com 1-866-TEAMHPC
Joshua Baker-LePain wrote:
On Fri, 9 Feb 2007 at 11:53am, Mike wrote
Greetings. HP claims RHEL 4 supports their servers with the Intel 3000 and 5000 chipsets. Has anyone had any trouble/success building machines that use this?
For example, CentOS 4.4 on http://www.supermicro.com/products/system/1U/5015/SYS-5015M-T+.cfm
I'm running CentOS4 on several X7DVL-E motherboardas (5000V chipset). Most stuff works well (put the SATA in AHCI mode). The one caveat was that while the stock e1000 driver will somewhat work with the onboard NICs, it'll randomly decide to stop moving packets about. An upgrade to the most recent driver from Intel (7.3.20) fixed that.
Thanks. Other than the stock e1000 driver issue, CentOS 4.4 will install from CD ok?
On Fri, 9 Feb 2007 at 1:33pm, Mike wrote
Joshua Baker-LePain wrote:
On Fri, 9 Feb 2007 at 11:53am, Mike wrote
Greetings. HP claims RHEL 4 supports their servers with the Intel 3000 and 5000 chipsets. Has anyone had any trouble/success building machines that use this?
For example, CentOS 4.4 on http://www.supermicro.com/products/system/1U/5015/SYS-5015M-T+.cfm
I'm running CentOS4 on several X7DVL-E motherboardas (5000V chipset). Most stuff works well (put the SATA in AHCI mode). The one caveat was that while the stock e1000 driver will somewhat work with the onboard NICs, it'll randomly decide to stop moving packets about. An upgrade to the most recent driver from Intel (7.3.20) fixed that.
Thanks. Other than the stock e1000 driver issue, CentOS 4.4 will install from CD ok?
Well, I kickstart from CD and do http installs. But that went without a hitch, so the full install from CD should as well.
-
Alfred von Campe -
Joshua Baker-LePain -
Mike -
William Dinkel