Displaying 3 results from an estimated 3 matches for "pixelclock".
Did you mean:
pixel_clock
2008 Feb 18
3
help with x config on centos 5.1
....500 MHz
(II) NVIDIA(0): HRes, HSyncStart : 1280, 1344
(II) NVIDIA(0): HSyncEnd, HTotal : 1504, 1728
(II) NVIDIA(0): VRes, VSyncStart : 1024, 1025
(II) NVIDIA(0): VSyncEnd, VTotal : 1028, 1072
(II) NVIDIA(0): H/V Polarity : +/+
(WW) NVIDIA(0): Mode is rejected: PixelClock (157.5 MHz) too high for
(WW) NVIDIA(0): Display Device (Max: 155.0 MHz).
(II) NVIDIA(0):
(II) NVIDIA(0): Validating Mode "640x512":
(II) NVIDIA(0): 640 x 512 @ 85 Hz
(II) NVIDIA(0): Mode Source: X Server
(II) NVIDIA(0): Pixel Clock : 78.750 MHz
(II) NVIDIA(0):...
2018 Jan 03
2
Nvidia maximum pixel clock issue in kmod-nvidia-384.98
...ncEnd, HTotal : 2000, 2080
[ 1354.589] (WW) NVIDIA(GPU-0): VRes, VSyncStart : 1200, 1203
[ 1354.589] (WW) NVIDIA(GPU-0): VSyncEnd, VTotal : 1209, 1235
[ 1354.589] (WW) NVIDIA(GPU-0): Sync Polarity : +H -V
[ 1354.589] (WW) NVIDIA(GPU-0): Mode is rejected: PixelClock
(154.0 MHz) too high for
[ 1354.589] (WW) NVIDIA(GPU-0): Display Device (Max: 0.0 MHz).
[ 1354.589] (WW) NVIDIA(GPU-0): Mode "1920x1200_60" is invalid.
Note that with the previous driver (version 384.90), a valid value was
detected for the 'maximum pixel clock'...
2018 Jan 03
0
Nvidia maximum pixel clock issue in kmod-nvidia-384.98
...80
> [ 1354.589] (WW) NVIDIA(GPU-0): VRes, VSyncStart : 1200, 1203
> [ 1354.589] (WW) NVIDIA(GPU-0): VSyncEnd, VTotal : 1209, 1235
> [ 1354.589] (WW) NVIDIA(GPU-0): Sync Polarity : +H -V
> [ 1354.589] (WW) NVIDIA(GPU-0): Mode is rejected: PixelClock
> (154.0 MHz) too high for
> [ 1354.589] (WW) NVIDIA(GPU-0): Display Device (Max: 0.0 MHz).
> [ 1354.589] (WW) NVIDIA(GPU-0): Mode "1920x1200_60" is invalid.
>
>
> Note that with the previous driver (version 384.90), a valid value was
> detected...