Hp Z23n Driver

[Marieta Reeks]

Mysystem is running Arch linux, with i3wm and using nvidia quadro k420 graphics card connected with display port to a hp z23n monitor. Since the past two months I have been getting Xid errors most of the times when I resume the system from hibernation. If I hibernate for a very short time, say a few minutes everything goes fine, but if the hibernation duration is longer, say 2+ hours, then at the time of resuming the system, it hangs and becomes jerky and the logs get filled with Xid errors. I tried disabling the compositor but still its the same, it fact at the time of writing this, the compositor is not running and I just woke up the system from hibernation, but had to reboot due to the Xid errors.

Also this card is just a couple months old, its a new system, so most likely it is not a thermal issue. And except for hibernation the system runs fine, there are no crashes or freezes while running the system only if I hibernate do I run into problems.

@generix, thanks for responding. I really cannot say for sure, since it is very unpredictable. Few hours back I suspended for 30 mins and then hibernated for 15 minutes and on both occasions I did not get any Xid error, but yesterday all my attempts to hibernate led to Xid errors. And a few weeks back, I did get these errors after suspending as well.

So I dont think this is because of the compositor or the kernel. I have not tried any older nvidia driver, have been using the current (387.34) from the official Arch repos. I see 390 has entered testing, any idea if this is fixed in the 390 series?

Downgrading to kernel 4.9 is not an option. Soon 4.14 will enter LTS and the mainline kernel will be 4.15, besides, there are some cgroup errors in 4.9 which have been fixed in kernels > 4.10. If there is a memory bug in the nvidia drivers > 378 and if its existence is known, then it should be fixed instead of downgrading the driver or kernel or both.

have you tried connecting a monitor directly to the 840 yet to see if the problem goes away? If it does not check the BIOS settings as it maybe telling the video to go to sleep and if it does then maybe you have a pair of bad docking stations but that seems unlikely to have two with the same problem.

@IT-Tony, thank you for your posting your issue here in Spiceworks and thanks to @Robert3914 for his helpful feedback. After sharing your issue with our consultant, he has provided the following feedback:

I have a feeling it could be similar or even identical problem as in this thread. Please follow for your case relevant instructions from this post: Problem: The log in screen turns black after user signs out

It is crucial and make please sure that latest Intel USB 3.0 and Intel HD Graphics 520 drivers are installed. Verify that only two displays are enabled and correctly configured in Windows 10 as with docking station 3 displays are supported.

Well the user has not had a black screen problem all day so I believe what corrected the issue was changing the monitors to always active! Of course it is always a good idea to have all of the drivers updated too!

This is probably going to be a really noob question ...but I cant find an answer for it. I was reading through Xorg.0.log and I saw a warning (ww) NVIDIA: option "PrimaryGpu" is not used at 21.637. I cant quite understand that. I went through this post while looking for an explanation =231370 but couldnt really understand the meaning of this warning and why it exists

This warning simply tells you that the NVIDIA driver is ignoring this option. This option is intended to be a information point for the X server (not the nvidia driver in particular) in the case of using Optimus enabled notebooks, so that the correct device will be used as primary, should one activate render offloading. It is of absolutely zero consequence to your usecase.

Yesterday, all of a sudden, the screen starts flicking to black and sometimes saying that there is no HDMI signal or scanning for signal. This does not appear to coincide with any updates or anything. This is happening every 20 seconds or so. I have since factory reset my Precision 7540 (much to my annoyance) as using the Dell Command Update application corrupted my network devices and I had no choice but to reinstall windows (Code 56 Class error).

With the assistance of Dell, the problem was identified and resolved. An old graphics driver installed was causing a problem, after uninstalling all installed graphics drivers until the default Microsoft driver was used, and then installing the latest dell drivers, the problem was finally resolved.

Its worth noting that the screen displays correctly (when it does display), but rarely stays visible for longer than 20 seconds. The screen spends most of its time powered on, but black and unresponsive.

The screen is basically black now. Laptop recognises the HDMI has been plugged in, drivers say they're ok. Even the Dell Graphics Control panel thinks everything is OK, but the screen stays black.

If I plug something else into the screen, everything is fine. If I plug the laptop via HDMI into anything else, all is fine. These two devices are not speaking to each other, after months and months of a happy relationship

The more I look into this, the more I feel like this a HDCP issue, sometimes the screen comes back for 10 seconds or so. Research suggests that this is a HDCP handshake fault. This may explain why only these two devices are affected when plugged into eachother. How would I go about resolving this?

When the screen saver is active, the monitor seems to display OK, it still drops out, but far far less. As soon as the screen saver is removed (by touching the keyboard / mouse), the screen drops out again. It also appears to be that when there is no movement on the screen (as in its just sat idle, but without the screen saver active) the picture frequents the monitor much more often.

Swapped the HDMI cable to an old cheap nasty one (much thinner, came with a cheap camera or something). The screen does not work at all with this one, however other devices such as an Xbox work absolutely fine. This is becoming increasingly annoying that its just these two devices that don't talk.

A friend lent me a newish PC. (Windows 10, with NVIDIA GeForce gtx 550 Ti) I hooked it up to my old monitor that I always used without problem on my old PC, but on this new PC the display is messed up.

All of those circles were copied and pasted and should appear as perfect circles all exactly the same size and ratio, but instead they're all stretched. The one in the middle is too thin, and the ones on the edges are too wide.

EDIT: My monitor is a "Emerson model number LD190EM2" I looked it up online and can confirm the max resolution listed for it is 1366 x 768. On my old PC, both 1366 x 768 and 1360 x 768 work perfectly. But on this new PC, neither work, both have the same problem I described here. I double checked the settings on the new PC. Here is a screenshot showing both the NVIDIA settings and the PC display settings:

Also, look through the menus on your monitor (not the computer) for a reset option and use it. If there is no reset option, unplug it from power and the computer and let it sit for an hour or so to see if this clears any setting. Or carefully examine the settings and try to set them all back to a Default state.

The root issue is still that the monitor is attempting to compensate for something. Typically this is a non-native resolution input, however, if you are 100% certain that is not the case, it is possible the monitor only THINKS that is it needs to compensate, and so is pinching and stretching the input image.

If you are 100% certain the computer is sending the correct signal, then the problem is with the monitor, and besides resetting the monitor settings to default, the only other option available is to replace the monitor.

How are you connecting this "monitor" (actually a TV) to your computer? HDMI, VGA... ? A lot of TVs do "odd" things when connected as monitors, such as simulating "overscan". This sometimes depends on which input you use, and sometimes on how you label that input in the TV's settings.

Your nVidia driver seems to think your panel's "native resolution" is 1920x1080. This does not seem to be settable, but you need to fix that. OR, try setting your computer (in the Windows settings) to 1920x1080).

If you would like to support the development of, technical assistance with, and continued availability of DisplayCAL and ArgyllCMS, please consider a financial contribution.As DisplayCAL wouldn't be useful without ArgyllCMS, all contributions received for DisplayCAL will be split between both projects.

For light personal non-commercial use, a one-time contribution may be appropriate.If you're using DisplayCAL professionally, an annual or monthly contribution would make a great deal of difference in ensuring that both projects continue to be available.

If you have decided to contribute (many thanks!), but you'd like to give to ArgyllCMS directly on your own behalf (visit argyllcms.com and scroll down a bit to get to its contribution links), please leave a message on your DisplayCAL contribution if contributing to both projects. Please note that if your contribution should be put towards adding a certain feature in ArgyllCMS, like support for a specific instrument, it will be more appropriate and efficient to contribute to ArgyllCMS only, and directly.

3a8082e126