search for: 384.98

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

On 03/01/18 20:14, Zube wrote: > 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

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

On Thu, Jan 4, 2018 at 9:40 PM, Phil Perry <pperry at elrepo.org> wrote: > Normally elrepo only releases the long term branch for Enterprise Linux, on > the assumption EL users will welcome the implied stability over more > frequent and potentially buggy releases. > In this case I had built the current short lived release as a user requested > it for compatibility with the

On Sat Jan 06 12:27:22 PM, Danny Smit wrote: > I normally certainly prefer the stability of the long-lived releases. > I noticed an update was just released of the long-lived release: > 384.111. The notes for this release say: > > Fixed a regression that prevented displays connected via some > types of passive adapters (e.g. DMS-59 to VGA or DVI) from working >

On 06/01/18 12:00, Zube wrote: > On Sat Jan 06 12:27:22 PM, Danny Smit wrote: > >> I normally certainly prefer the stability of the long-lived releases. >> I noticed an update was just released of the long-lived release: >> 384.111. The notes for this release say: >> >> Fixed a regression that prevented displays connected via some >> types

On 03/01/18 15:45, Danny Smit wrote: > 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

On Sat, Jan 6, 2018 at 2:27 PM, Phil Perry <pperry at elrepo.org> wrote: > > I've just built and released 384.111 to the elrepo main repository, so it > should show up on the mirrors shortly. As expected, the 384.111 also solves the problem in my case. Thanks for the support everyone. Regards, Danny

On 04/01/18 09:12, Danny Smit wrote: > On Thu, Jan 4, 2018 at 5:22 AM, Phil Perry <pperry at elrepo.org> wrote: >> On 03/01/18 20:14, Zube wrote: >>> >>> I can confirm that this happens with the driver downloaded from NVIDIA. >>> I had to fall back to the .90 driver to get it to work for all my >>> NVS 315s (with dual DVI) running on 7.4 / 6.9.

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

To: CentOS mailing list <centos at centos.org> Thema: Re: [CentOS] Nvidia maximum pixel clock issue in kmod-nvidia-384.98 Dear All, Start BIOS Configuration and go to Graphic Configuration change On Board VGA to PCI Express x16 Automatic is VGA on Board Bis bald Alexander Am 09.01.2018 um 13:00 schrieb centos-request at centos.org: > Send CentOS mailing list submissions to >

On Thu, Jan 4, 2018 at 5:22 AM, Phil Perry <pperry at elrepo.org> wrote: > On 03/01/18 20:14, Zube wrote: >> >> I can confirm that this happens with the driver downloaded from NVIDIA. >> I had to fall back to the .90 driver to get it to work for all my >> NVS 315s (with dual DVI) running on 7.4 / 6.9. Thanks. For reference, I did the same test. With the driver

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

Hi, folks, Has anyone else seen the issue of having an excludes= in /etc/yum.conf, but yum-cron appears to be ignoring it? This may have been the case earlier this year, where it seemed to partly install a new kernel, then not done the post-install. I *think* that's what I'm seeing on a box with twin Tesla cards, with yum.conf: exclude=kernel* xorg* cuda* kmod* and yet cron.daily

Twitter user stintel, in this thread: https://twitter.com/stintel/status/948499157282623488 mentions a possible problem with the new patches and the nvidia driver: "As if the @Intel bug isn't bad enough, #KPTI renders @nvidia driver incompatible due to GPL-only symbol 'cpu_tlbstate'. #epicfail" Also: https://twitter.com/tomasz_gwozdz/status/948590364679655429

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 Thu, 4 Jan 2018, Zube wrote: > Twitter user stintel, in this thread: > > https://twitter.com/stintel/status/948499157282623488 > > mentions a possible problem with the new patches and the > nvidia driver: > > "As if the @Intel bug isn't bad enough, #KPTI renders @nvidia driver > incompatible due to GPL-only symbol 'cpu_tlbstate'. #epicfail" >

>I'll see if I can find some time this weekend to fix the elrepo package > and get it reinstated into the repository. >Phil Hi Phil, Thanks for the reply. Your correct this is OLD hardware. Everything was working with 7.5 thought I was good to go so to speak ... So When I was starting now to migrate OLD boxes from CentOS 6 to 7.6 it wasnt working. I can look at going