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

> -----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 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 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

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

vychytraly . wrote: > On Thu, Oct 5, 2017 at 9:51 PM, <m.roth at 5-cent.us> wrote: >> >> So, kmod-nvidia installed. Trouble is, I have no tool to test it. And my >> user might need nvcc, which, of course, is only provided by the NVidia >> CUDA, which won't install, because it conflicts with kmod-nvidia. >> >> Has *anyone* dealt with this? If so,

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

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

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

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

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

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 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.

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

Thank you! I messaged the ELREPO Mailing List. We are currently investigating the cause of the messages. Br, Jens

Stephen Berg (Code 7309) wrote: > On 1/11/19 10:41 AM, mark wrote: > >> C7, and I did a yum update --disableexcludes=all, and yet it's telling >> me [nvidia]: excluding kmod-nvidia-410.66-1.el7_5.elrepo.x86_64 >> [nvidia]: excluding kmod-nvidia-410.73-1.el7_5.elrepo.x86_64 >> [nvidia]: excluding kmod-nvidia-410.73-2.el7_6.elrepo.x86_64 >> [nvidia]: excluding

On Thu, 2017-10-05 at 17:07 -0400, m.roth at 5-cent.us wrote: > vychytraly . wrote: > > On Thu, Oct 5, 2017 at 9:51 PM, <m.roth at 5-cent.us> wrote: > > > > > > So, kmod-nvidia installed. Trouble is, I have no tool to test it. And my > > > user might need nvcc, which, of course, is only provided by the NVidia > > > CUDA, which won't install,

Got a HBS (y'know, Honkin' Big Server, one o' them technical terms), a Dell 720 with two Tesla GPUs. I updated the o/s, 6.5, and I cannot get the GPUs recognized. As a last resort, I d/l NVidia's proprietary driver/installer, 325, and it builds fine... I've yum removed the kmod-nvidia I had on the system, nouveau is blacklisted, and when I reboot, lsmod shows me nvidia loaded,

I have code like this: data <- read.csv("test1.csv", stringsAsFactors=FALSE, header=TRUE) # Graph myplot=ggplot(data, aes(fill=condition, y=value, x=condition)) + geom_bar(position="dodge", stat="identity", width=0.5) + scale_fill_manual(values=c("#7b3294", "#c2a5cf", "#a6dba0", "#008837"))+

> > Ok, final resolution: reinstalled the 390... and there's no driver for the > current kernel. I did an rpm -ql, and it's for an 862 kernel. > > Time to remove, and go to the proprietary (this server has two Tesla > cards, and uses CUDA). > Definitely. If you are using CUDA with Tesla cards go straight for the nVidia CUDA repo - it includes the necessary drivers.

regarding -------- Fixed address allocations weren't going to be part of that, but I see that it makes sense for a variety of use cases. One question I have here is how this is intended to work where the RM needs to make some of these allocations itself (for graphics context mapping, etc), how should potential conflicts with user mappings be handled? -------- As an initial implemetation you