Akemi; Yes, lsmod shows the alx module there with a size of 29264.
I may be missing something completely basic here but am not sure what it is. alx is there, the right driver is there, the machine is hardwired to the router, etc. I saw this list of packages recommended for installation concerning a Fedora 19 box, and there are a bunch of them at the pkgs.org site for CentOS 6: cpp-4.8.1-1.fc19.x86_64.rpm gcc-4.8.1-1.fc19.x86_64.rpm gcc-c++-4.8.1-1.fc19.x86_64.rpm glibc-2.17-14.fc19.x86_64.rpm glibc-common-2.17-14.fc19.x86_64.rpm glibc-devel-2.17-14.fc19.x86_64.rpm glibc-headers-2.17-14.fc19.x86_64.rpm kernel-devel-3.9.5-301.fc19.x86_64.rpm kernel-headers-3.9.5-301.fc19.x86_64.rpm libmpc-1.0.1-1.fc19.x86_64.rpm libstdc++-devel-4.8.1-1.fc19.x86_64.rpm perl-5.16.3-264.fc19.x86_64.rpm perl-Carp-1.26-243.fc19.noarch.rpm perl-Encode-2.51-1.fc19.x86_64.rpm perl-Filter-1.49-1.fc19.x86_64.rpm perl-libs-5.16.3-264.fc19.x86_64.rpm perl-macros-5.16.3-264.fc19.x86_64.rpm perl-PathTools-3.40-1.fc19.x86_64.rpm perl-Pod-Escapes-1.04-264.fc19.noarch.rpm perl-Pod-Simple-3.20-264.fc19.noarch.rpm perl-Scalar-List-Utils-1.27-246.fc19.x86_64.rpm perl-Socket-2.009-2.fc19.x86_64.rpm perl-threads-1.87-1.fc19.x86_64.rpm perl-threads-shared-1.43-2.fc19.x86_ Should I be concerned with grabbing some or all of these, or others, and moving them to the RHEL 6.5 machine? Thanks! David On Fri, Feb 21, 2014 at 12:00 PM, <elrepo-requ...@lists.elrepo.org> wrote: > Send elrepo mailing list submissions to > elrepo@lists.elrepo.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.elrepo.org/mailman/listinfo/elrepo > or, via email, send a message with subject or body 'help' to > elrepo-requ...@lists.elrepo.org > > You can reach the person managing the list at > elrepo-ow...@lists.elrepo.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of elrepo digest..." > > > Today's Topics: > > 1. Re: elrepo Digest, Vol 56, Issue 5 (Akemi Yagi) > 2. Announcement: EL6 Updated kernel-lt Release [3.10.31-1] > (Alan Bartlett) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 20 Feb 2014 11:14:46 -0800 > From: Akemi Yagi <tora...@elrepo.org> > To: EL Repo General Mailing List <elrepo@lists.elrepo.org> > Subject: Re: [elrepo] elrepo Digest, Vol 56, Issue 5 > Message-ID: > <CABA31DoMXcRjDeXHr6kYwXVoEci8N=1aENPsK= > jv4qgvg_m...@mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On Wed, Feb 19, 2014 at 10:32 AM, D. R. Hardy <drhard...@gmail.com> wrote: > > Hi, guys, > > > > As it turns out, I'd correctly chosen the right kmod driver and had it > > installed already on the machine, which is a RHEL 6.5 (Santiago) x86_64. > > Also have the local repository of the DVD iso mounted. > > > > 'yum grouplist' shows the installed and available groups but 'yum update' > > won't work as there is still no net access (wired Ethernet) and of > course it > > wants me to register with Red Hat but unable to reach the server, > naturally. > > > > So as far as I know, 6.5 would have the latest kernel, right? Or am I > > missing something here when doing the update locally? > > > > Thanks! > > > > David > > Now that you mentioned you have 6.5, I just test-installed kmod-alx on > a RHEL-6.5 system. It installed fine and the modules was loaded with > no apparent error. Can you confirm that alx has been loaded on your > system (lsmod)? > > Akemi > > > ------------------------------ > > Message: 2 > Date: Fri, 21 Feb 2014 15:07:49 +0000 > From: Alan Bartlett <a...@elrepo.org> > To: ELRepo-users <elrepo@lists.elrepo.org> > Subject: [elrepo] Announcement: EL6 Updated kernel-lt Release > [3.10.31-1] > Message-ID: > <CA+_WhHxTnbTYPpWcbdWVROAXxeu= > hi3p11mzw3otf1xej6y...@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Announcing the release of the kernel-lt-3.10.31-1.el6.elrepo packages > into the EL6 elrepo-kernel repository: > > http://elrepo.org/tiki/kernel-lt > > The upstream changelog: > > https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.10.31 > > The following files are currently syncing to the mirrors: > > x86 > kernel-lt-3.10.31-1.el6.elrepo.i686.rpm > kernel-lt-devel-3.10.31-1.el6.elrepo.i686.rpm > kernel-lt-doc-3.10.31-1.el6.elrepo.noarch.rpm > kernel-lt-firmware-3.10.31-1.el6.elrepo.noarch.rpm > kernel-lt-headers-3.10.31-1.el6.elrepo.i386.rpm > kernel-lt-NONPAE-3.10.31-1.el6.elrepo.i686.rpm > kernel-lt-NONPAE-devel-3.10.31-1.el6.elrepo.i686.rpm > perf-3.10.31-1.el6.elrepo.i686.rpm > > x86_64 > kernel-lt-3.10.31-1.el6.elrepo.x86_64.rpm > kernel-lt-devel-3.10.31-1.el6.elrepo.x86_64.rpm > kernel-lt-doc-3.10.31-1.el6.elrepo.noarch.rpm > kernel-lt-firmware-3.10.31-1.el6.elrepo.noarch.rpm > kernel-lt-headers-3.10.31-1.el6.elrepo.x86_64.rpm > perf-3.10.31-1.el6.elrepo.x86_64.rpm > > src > kernel-lt-3.10.31-1.el6.elrepo.nosrc.rpm > > We provide these kernels for hardware testing in an effort to identify > new/updated drivers which can then be targeted for backporting as kmod > packages. Meanwhile, these kernels may provide interim relief to > people with non-functional hardware. We stress that we consider such > kernels as a last resort for those who are unable to get their > hardware working using the RHEL kernel with supplementary kmod > packages. > > These packages are provided "As-Is" with no implied warranty or > support. Using the kernel-lt may expose your system to security, > performance and/or data corruption issues. Since timely updates may > not be available from the ELRepo Project, the end user has the > ultimate responsibility for deciding whether to continue using the > kernel-lt packages in regular service. > > The packages are intentionally named kernel-lt so as not to conflict > with the RHEL kernels and, as such, they may be installed and updated > alongside the regular kernel. The kernel configuration is based upon a > default RHEL configuration with added functionality enabled as > appropriate. > > If a bug is found when using these kernels, the end user is encouraged > to report it upstream to the Linux Kernel Bug Tracker [1] and, for our > reference, to the ELRepo bug tracker [2]. By taking such action, the > reporter will be assisting the kernel developers, Red Hat and the Open > Source Community as a whole. > > Thank you, > > The ELRepo Team. > > [1] http://bugzilla.kernel.org/ > [2] http://elrepo.org/bugs/ > > > ------------------------------ > > _______________________________________________ > elrepo mailing list > elrepo@lists.elrepo.org > http://lists.elrepo.org/mailman/listinfo/elrepo > > > End of elrepo Digest, Vol 56, Issue 7 > ************************************* >
_______________________________________________ elrepo mailing list elrepo@lists.elrepo.org http://lists.elrepo.org/mailman/listinfo/elrepo
