similar to: Nvidia error

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

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

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

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

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

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 all, Having issues with the Nvidia drives on Centos 6.2. So after I do yum install kmod-nvidia and rebooting, I get no screen. My errors; /var/log/messages; kernel: NVRM: The NVIDIA GeForce4 MX 4000 GPU installed in this system is kernel: NVRM: supported through the NVIDIA 96.43.xx Legacy drivers. Please kernel: NVRM: visit http://www.nvidia.com/object/unix.html for more kernel: NVRM:

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

Hi, I'm currently trying to install CentOS 7 (desktop) on a Lenovo workstation with an NVidia Quadro 2000 graphical card. Normally I know my way around NVidia cards and how to configure them either using the ELRepo drivers or those downloaded from nvidia.com. I have written a corresponding article on my blog: https://blog.microlinux.fr/nvidia-centos/ But this time it looks like I have no

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

Just discovered these messages in /var/log/messages, while looking at the USB problem I just posted about, separately. Apr 27 20:23:16 fcshome kernel: NVRM: API mismatch: the client has the version 331.67, but Apr 27 20:23:16 fcshome kernel: NVRM: this kernel module has the version 331.49. Please Apr 27 20:23:16 fcshome kernel: NVRM: make sure that this kernel module and all NVIDIA driver Apr 27

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.

So, another admin I work with rolled out most (but not kernel) updates to 6.4... but including xorg. I log out the end of the day, and I'm hosed - no X. Now, my not-two-year-old workstation has an nvidia card, and I'd installed kmod-nvidia from elrepo. I figured I'd fix my problem by finishing the upgrade and rebooting. Nope. I try to upgrade kmod-nvidia from elrepo. Anyone got any

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

>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

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

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

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