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

Displaying 20 results from an estimated 6000 matches similar to: "Semi-OT: hardware: NVidia proprietary driver, C7.4"

2017 Sep 27
2
Semi-OT: hardware: NVidia proprietary driver, C7.4
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
2017 Sep 27
0
Semi-OT: hardware: NVidia proprietary driver, C7.4
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.
2017 Nov 20
2
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
2017 Dec 14
7
Question on CentoS 7.4 on nvidia
I installed the elrepo kmod-nvidia and also the nvidia-detect and modules (see below). I had X working with the 3.10 from Centos - but video was freezing. SO I thought I would try the elrepo kernel. I installed that and X does not come up? How do I re-make the nvidia module for 4.14.5 kernel? I want to make sure the kmod kernel did it. I 'm thinking it did not. lspci | grep VGA says
2017 Sep 27
2
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
2017 Dec 15
1
Question on CentoS 7.4 on nvidia
Yan Li wrote: > If you need to use a non stock kernel, you can also try to download the > latest driver directly from nvidia. The nvidia official driver is very > easy to install and works with almost all kernel versions. It can also be > easily uninstalled too. Make sure you have the correct one, though. I have a number of systems with older NVidia cards, and have to pick and choose
2018 Jan 03
2
Nvidia maximum pixel clock issue in kmod-nvidia-384.98
Hi everyone, On CentOS 7 I'm running into an issue with the latest nvidia driver from elrepo: kmod-nvidia-384.98-1.el7_4.elrepo.x86_64 This driver version seem to introduce issue in detecting video modes when a monitor is connected using DVI. As soon as the machine attempts to start X, nothing happens and the monitor goes into sleep mode reporting that it has 'no signal'. It is
2017 Nov 06
6
Nvidia error
I am getting this error on CentOS 7.4 kernel: NVRM: API mismatch: the client has the version 384.98, but#012NVRM: this kernel module has the version 384.90. Please#012NVRM: make sure that this kernel module and all NVIDIA driver#012NVRM: components have the same version nvidia-detect -v Probing for supported NVIDIA devices... [10de:1288] NVIDIA Corporation GK208 [GeForce GT 720] This device
2018 Jan 03
3
Nvidia maximum pixel clock issue in kmod-nvidia-384.98
On Wed Jan 03 07:43:04 PM, Phil Perry wrote: > > On CentOS 7 I'm running into an issue with the latest nvidia driver > > from elrepo: kmod-nvidia-384.98-1.el7_4.elrepo.x86_64 > > This driver version seem to introduce issue in detecting video modes > > when a monitor is connected using DVI. As soon as the machine attempts > > to start X, nothing happens and the
2017 Sep 26
7
Semi-OT: hardware: NVidia proprietary driver, C7.4
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.
2017 Sep 26
1
Semi-OT: hardware: NVidia proprietary driver, C7.4
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
2017 Sep 26
1
Semi-OT: hardware: NVidia proprietary driver, C7.4
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
2017 Sep 27
0
Semi-OT: hardware: NVidia proprietary driver, C7.4
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
2017 Nov 20
0
Semi-OT: hardware: NVidia proprietary driver, C7.4
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
2018 Apr 06
4
Semi-OT: install python package in userspace
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
2017 Sep 26
0
Semi-OT: hardware: NVidia proprietary driver, C7.4
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
2017 Sep 26
0
Semi-OT: hardware: NVidia proprietary driver, C7.4
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
2017 Sep 26
0
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 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
2017 Nov 22
0
Semi-OT: hardware: NVidia proprietary driver, C7.4
Thank you! I messaged the ELREPO Mailing List. We are currently investigating the cause of the messages. Br, Jens
2017 Oct 12
3
Kernel crash
Hi everyone, I updated the kernel from 3.10.0-514.16.1.el7.x86_64 to 3.10.0-693.2.2.el7.x86_64 . While I was following these steps https://wiki.centos.org/HowTos/Laptops/Wireless/Broadcom (I knew that I needed to compile again everything) in order to activate WIFI, the laptop crashed doing # depmod -a # modprobe wl Noting that I replaced (naively) # depmod $(uname -r) from the guide (stupid