similar to: Semi-OT: hardware: NVidia proprietary driver, C7.4

Hi Mark, did you manage to sort out messages from Dracut and /sbin/weak-modules you received while installing kmod-nvidia? We get the same messages while installing kmod-nvidia-384.98-1.el7_4.elrepo.x86_64 on RHEL 7.4 with the kernel 3.10.0-693.5.2.el7.x86_64. Kr, Jens

On 11/20/2017 05:23 AM, Kretschmer, Jens wrote: > Hi Mark, > > did you manage to sort out messages from Dracut and /sbin/weak-modules you received while installing kmod-nvidia? We get the same messages while installing kmod-nvidia-384.98-1.el7_4.elrepo.x86_64 on RHEL 7.4 with the kernel 3.10.0-693.5.2.el7.x86_64. > weak modules allow modules built on one kernel version to apply to

On 27/09/17 07:56, Sorin Srbu wrote: >> -----Original Message----- >> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Phil Perry >> Sent: den 26 september 2017 21:46 >> To: centos at centos.org >> Subject: Re: [CentOS] Semi-OT: hardware: NVidia proprietary driver, C7.4 >> >> On 26/09/17 18:40, m.roth at 5-cent.us wrote: >>> This is

Le 26/09/2017 ? 19:59, Scott Robbins a ?crit?: > Why not use the elrepo repo? They've worked flawlessly for me, both with > legacy and new cards. I know this is weird, but I've had cases where the downloaded NVidia driver worked and the ELRepo driver didn't, and the other way around. Details here: https://blog.microlinux.fr/nvidia-centos/ Niki -- Microlinux - Solutions

On Tue, Sep 26, 2017 at 1:59 PM, Scott Robbins <scottro11 at gmail.com> wrote: > On Tue, Sep 26, 2017 at 01:40:54PM -0400, m.roth at 5-cent.us wrote: > > This is really frustrating. I've got a server with two K20c Tesla cards. > I > > need to use the proprietary drivers to use the CUDA toolkit. Btw, I had > no > > trouble at all with building for CentOS 7.3

On 27/09/17 16:49, m.roth at 5-cent.us wrote: > Hi, folks, > > Well, still more fun (for values of fun approaching zero): > > 1. Went to install CUDA 9.0... well, gee, there is *no* CUDA 9.0. > Even though I installed the 9 repo, all that I get is 8. I've > used their webform, and an waiting on a reply. > 2. I remove all nvidia packages.

> -----Original Message----- > From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Phil Perry > Sent: den 26 september 2017 21:46 > To: centos at centos.org > Subject: Re: [CentOS] Semi-OT: hardware: NVidia proprietary driver, C7.4 > > On 26/09/17 18:40, m.roth at 5-cent.us wrote: > > This is really frustrating. I've got a server with two K20c Tesla

On Tue, Sep 26, 2017 at 01:40:54PM -0400, m.roth at 5-cent.us wrote: > This is really frustrating. I've got a server with two K20c Tesla cards. I > need to use the proprietary drivers to use the CUDA toolkit. Btw, I had no > trouble at all with building for CentOS 7.3 > > I have what NVidia claims is the correct driver package, a 340 series. It > appears to build, but then

On 26/09/17 18:40, m.roth at 5-cent.us wrote: > This is really frustrating. I've got a server with two K20c Tesla cards. I > need to use the proprietary drivers to use the CUDA toolkit. Btw, I had no > trouble at all with building for CentOS 7.3 > > I have what NVidia claims is the correct driver package, a 340 series. It > appears to build, but then fails to load. The only

Phil Perry wrote: > On 27/09/17 16:49, m.roth at 5-cent.us wrote: >> Hi, folks, >> >> Well, still more fun (for values of fun approaching zero): >> >> 1. Went to install CUDA 9.0... well, gee, there is *no* CUDA 9.0. >> Even though I installed the 9 repo, all that I get is 8. I've >> used their webform, and an waiting on a

Hi, folks, Well, still more fun (for values of fun approaching zero): 1. Went to install CUDA 9.0... well, gee, there is *no* CUDA 9.0. Even though I installed the 9 repo, all that I get is 8. I've used their webform, and an waiting on a reply. 2. I remove all nvidia packages. 3. It appears that the kmod-nvidia is what I need; that's what nvidia-detect

This is really frustrating. I've got a server with two K20c Tesla cards. I need to use the proprietary drivers to use the CUDA toolkit. Btw, I had no trouble at all with building for CentOS 7.3 I have what NVidia claims is the correct driver package, a 340 series. It appears to build, but then fails to load. The only error I see is "no such device", which makes no sense to me, esp.

On Tue, 2017-09-26 at 13:40 -0400, m.roth at 5-cent.us wrote: > This is really frustrating. I've got a server with two K20c Tesla cards. I > need to use the proprietary drivers to use the CUDA toolkit. Btw, I had no > trouble at all with building for CentOS 7.3 > > I have what NVidia claims is the correct driver package, a 340 series. It > appears to build, but then fails to

Hi all, I just wanted to give a heads up to any NVIDIA users that NVIDIA are dropping support for older hardware based on G8xxx, G9xxx and GT2xx chipsets in their latest display drivers. The last version to support these older chipsets will be the current Long Lived 340.xx branch. If anyone is using NVIDIA driver packages from elrepo, legacy 340.xx driver packages are now available for those

Hi, folks, I'm about to build a filesystem on a CentOS 7 box, on a JetStore RAID box through a QLogic ISP2532 card. Do I need to specifiy sw and su, or will xfs query the subsystem and get that itself? mark (assuming nixpam lets me through....)

Valeri Galtsev wrote: <snip> >>> On Fri, 6 Apr 2018 17:25 , <m.roth at 5-cent.us> wrote: >>> >>>> CentOS 7 box. As there's no package in any of the repos, we're trying >>>> to install scikit-learn in the user's space. It refuses. My late try was, >>>> after d/l a .whl from last year, hoping that would work with the numpy

On 25/08/2019 02:28, Gregory P. Ennis wrote: > > On Sat, Aug 24, 2019 at 3:21 PM Ian Mortimer <i.mortimer at uq.edu.au> wrote: > > > > On Sat, 24 Aug 2019, Gregory P. Ennis wrote: > > > > > On August 2, my desktop unit updated with > > > kmod-nvidia-430.40-1.el7_6.elrepo.x86_64 > > > which broke yum having a multiple of dependencies not

Hi list, Some days ago I updated my centos 7.3 to 7.4 on a dell server. After this update I noticed a strange behaviour by sshd. I noticed this problem because trying to connect to ssh I got connection refused or high latency between connecting and password req. So I noticed that sshd will be restarted every ~2 min. >From log I get this: Received signal 15; terminating Failed to start

Hi list, I solved the problem. Anyone had answered but I report the solution for similar problem. The problem was caused by an sshd.service under /etc/systemd/system/. This file was placed because upgrading from 7.2 to 7.3 I got problem with ssh startup and someone suggested to add pidfile directive in sshd.service to solve the problem. Updating from 7.3 to 7.4 I think that 2 files for sshd

I am install C7.5 on a nvidia unit and nvidia-detect tells me to use kmod-nvidia-390xx so I do the yum install and and after a long time I see this -> Processing Dependency: kernel(__drm_atomic_helper_crtc_duplicate_state) = 0xa5f3a170 for package: kmod-nvidia-390xx-390.87-2.el7_6.elrepo.x86_64 --> Processing Dependency: kernel(__drm_atomic_helper_crtc_destroy_state) = 0x00a9c70b for