similar to: Nvidia maximum pixel clock issue in kmod-nvidia-384.98

Displaying 20 results from an estimated 400 matches similar to: "Nvidia maximum pixel clock issue in kmod-nvidia-384.98"

2018 Jan 03
0
Nvidia maximum pixel clock issue in kmod-nvidia-384.98
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
2013 Jan 24
2
[PATCH 1/2] lib: Add CLEANUP_FREE macro which automatically calls 'free' when leaving scope.
From: "Richard W.M. Jones" <rjones@redhat.com> Use the macro like this to create temporary variables which are automatically cleaned up when the scope is exited: { CLEANUP_FREE (char *, foo, strdup (bar)); /* char *foo = strdup (bar) */ ... // no need to call free (foo)! } On GCC and LLVM, this is implemented using __attribute__((cleanup(...))).
2019 Aug 28
2
[PATCH v3 5/7] drm/nouveau: utilize subconnector property for DP
On Wed, Aug 28, 2019 at 10:47:08AM -0400, Ilia Mirkin wrote: > On Wed, Aug 28, 2019 at 10:38 AM Ville Syrjälä > <ville.syrjala at linux.intel.com> wrote: > > > > On Mon, Aug 26, 2019 at 09:36:50AM -0400, Ilia Mirkin wrote: > > > This should probably be fixed to account for the scenario where an > > > HDMI connector is plugged directly into the DP++ port. I
2016 Mar 01
1
Dual monitors have same identifier
------------------------ From: Efrem Mc <efremmc2 at gmail.com> Date: Tue, 1 Mar 2016 00:27:52 -0500 > 'Normally, the monitor-edid, can report the options as well as the > journalctl -k on boot. I have a GTX 960, and it has a DVI-I, DVI-D, > DP 1.2, HDMI, and it names the ports as follows, DVI-I as > (DVI-I-1/DFP-0, DFP-1 (HDMI-1), DFP-2 (DVI-D-1/DFP-2), and for the
2019 Aug 28
2
[PATCH v3 5/7] drm/nouveau: utilize subconnector property for DP
On Mon, Aug 26, 2019 at 09:36:50AM -0400, Ilia Mirkin wrote: > This should probably be fixed to account for the scenario where an > HDMI connector is plugged directly into the DP++ port. I don't think > the dp.subconnector property will be valid in that case. > (Unfortunately I don't remember how one detects that particular > situation.) One may or may not be able to detect
2009 Jan 20
3
Setting Resolution Modes in xorg.conf
I asked on the Gentoo forums, and surprisingly haven't gotten an answer. When I run xrandr, I get this output: Code: Screen 0: minimum 2960 x 1050, current 2960 x 1050, maximum 2960 x 1050 default connected 2960x1050+0+0 0mm x 0mm 2960x1050 50.0* I'm using TwinView with a 1680x1050 monitor and a 1280x1024 monitor. And I want to set up some different modes in xrandr. When
2020 Aug 20
2
[RFC 13/20] drm/i915/dp: Extract drm_dp_downstream_read_info()
On Wed, Aug 19, 2020 at 05:34:15PM -0400, Lyude Paul wrote: > (adding Ville and Imre to the cc here, they might be interested to know about > this, comments down below) > > On Wed, 2020-08-19 at 11:15 -0400, Sean Paul wrote: > > On Tue, Aug 11, 2020 at 04:04:50PM -0400, Lyude Paul wrote: > > > We're going to be doing the same probing process in nouveau for > >
2008 Feb 18
3
help with x config on centos 5.1
Hi all, Typically I dont have issues with configuring X. However this time its an issue. I have an NVIDIA graphics card trying to do 1920x1080. If I configure the screen by hand with the nvidia config utility it works at 1920x1080. However when I reboot its 800x600. When I use the nvidia config utility to set 1920x1080 then save the xorg.conf file, and reboot (yes I copied
2004 Feb 08
1
APE: compar.gee( )
Dear all, I don't understand the following behaviour: Running compar.gee (in library ape ) with and without the option 'data', it give me different results Example: .... Start R .... > load("eiber.RData") > ls() [1] "gee.na" "mydata" "mytree" > library(ape) > # runnig with the option data= mydata > compar.gee(alt ~ R,
2014 Sep 24
1
[PATCH 1/2] allow path to envyas binary to be specified
Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- src/shader/Makefile | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/src/shader/Makefile b/src/shader/Makefile index 46658e9..2d789be 100644 --- a/src/shader/Makefile +++ b/src/shader/Makefile @@ -24,20 +24,21 @@ NVF0_SHADERS = xfrm2nvf0.vpc \
2016 Oct 10
0
External monitor support changes.
I've been working on this issue for quite a while. Back in January of 2015 I posted about how well external monitors worked with the out-of-the-box CentOS 7 ATI radeon drivers and my Dell M6500 with an ATI FirePro M7820. At the time the support was seamless and 'Just Worked' without any issue. A few months later, some update came down the pipe and this broke completely, with the
2019 May 19
5
[PATCH v1 0/4] drm/nouveau: drop use of drmP.h
The following patchset remove use of the deprecated drmP.h header file in the nouveau driver(s). As preparation a dependency on drm_os_linux.h is dropped. The list of include files are sorted and are in some cases divided up in blocks of linux/* drm/* etc. The removal is divided up in a few patches that was the logical steps to remove the use of drmP.h. Build tested with allmodconfig and
2020 Aug 19
3
[RFC 13/20] drm/i915/dp: Extract drm_dp_downstream_read_info()
On Tue, Aug 11, 2020 at 04:04:50PM -0400, Lyude Paul wrote: > We're going to be doing the same probing process in nouveau for > determining downstream DP port capabilities, so let's deduplicate the > work by moving i915's code for handling this into a shared helper: > drm_dp_downstream_read_info(). > > Note that when we do this, we also do make some functional
2011 Apr 01
2
[LLVMdev] Scheduler Integration Questions
Hello llvm-dev, I'm doing some experimentation on instruction scheduling and would like to use LLVM as a testbed, by integrating our existing (compiler-agnostic) scheduler into it. I have tinkered enough with the LLVM code to know how to create and run a new scheduler, access the DAG and target info, etc. However, I've come upon some questions that I have been unable to answer so far, and
2010 Mar 17
9
[Bug 27136] New: blank screen with G98 [Quadro NVS 420] (NV98) dual GPU, 4-head
http://bugs.freedesktop.org/show_bug.cgi?id=27136 Summary: blank screen with G98 [Quadro NVS 420] (NV98) dual GPU, 4-head Product: xorg Version: 7.5 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component:
2020 Aug 21
0
[RFC 13/20] drm/i915/dp: Extract drm_dp_downstream_read_info()
On Fri, 2020-08-21 at 01:37 +0300, Imre Deak wrote: > On Wed, Aug 19, 2020 at 05:34:15PM -0400, Lyude Paul wrote: > > (adding Ville and Imre to the cc here, they might be interested to know > > about > > this, comments down below) > > > > On Wed, 2020-08-19 at 11:15 -0400, Sean Paul wrote: > > > On Tue, Aug 11, 2020 at 04:04:50PM -0400, Lyude Paul wrote:
2013 Mar 28
6
Does CentOS support dual graphics cards with 2 monitors each?
I have a user who wants to have 4 monitors attached to his CentOS 6.4 system. I know that you can't use both on-board video and a PCI video card at the same time, but what about two PCI video cards? The system seems to recognize them as shown by the lspci -v output below, but I can't get Xorg to use the second card. Has anyone done this? If so, what is the trick to get it to work?
2011 Jan 24
1
Problems with Wine and twin view
Hello all, I'm using wine 1.3.11 on gentoo and i'm having some problems As far as i understand, in order to stop games spanning on both of my monitors i have to add a metamode in xorg.conf. So i've edited my xorf.conf to: Code: Option "metamodes" "CRT: 1280x1024_75 +1920+0, DFP: 1920x1080_60 +0+0; DFP: 1920x1080_60 +0+0, CRT: NULL" This is fine for
2019 Aug 28
0
[PATCH v3 5/7] drm/nouveau: utilize subconnector property for DP
On Wed, Aug 28, 2019 at 10:54 AM Ville Syrjälä <ville.syrjala at linux.intel.com> wrote: > > On Wed, Aug 28, 2019 at 10:47:08AM -0400, Ilia Mirkin wrote: > > On Wed, Aug 28, 2019 at 10:38 AM Ville Syrjälä > > <ville.syrjala at linux.intel.com> wrote: > > > > > > On Mon, Aug 26, 2019 at 09:36:50AM -0400, Ilia Mirkin wrote: > > > > This
2020 Aug 20
0
[RFC v2 06/20] drm/nouveau/kms: Search for encoders' connectors properly
While the way we find the associated connector for an encoder is just fine for legacy modesetting, it's not correct for nv50+ since that uses atomic modesetting. For reference, see the drm_encoder kdocs. Fix this by removing nouveau_encoder_connector_get(), and replacing it with nv04_encoder_get_connector(), nv50_outp_get_old_connector(), and nv50_outp_get_new_connector(). v2: * Don't