From: "Grzesiek Sójka" <pld-t9zbU3WrWHI@public.gmane.org>
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: GeForce FX5200 dual DVI & Samsung 204b
Date: Sat, 25 Sep 2010 16:04:23 +0200 [thread overview]
Message-ID: <4C9E0167.8000507@pfu.pl> (raw)
Hi there,
Im using GeForce FX5200 dual DVI graphics adapter connected with two
Samsung 204b monitors. At the moment I'm using binary nvidia drivers and
everything works fine but I'm forced to switch to nouveau. Unfortunately
there are problems. It seems that nouveau.ko wrongly detects the
PixelClock of my monitors. More precisely, after loading of nouveu.ko
the screen starts to blink. According to my experience the problem is
too hight PixelClock. Moreover, in the /var/log/Xorg.0.log you can find
the line:
NOUVEAU(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 81 kHz,
PixClock max 175 MHz
which is false. The maximum PixClk for Sumsung 204b is 162MHz. I was
trying to play with the video= kernel parameter but there is no way to
force the PixClk. I was also trying to edit the suitable ModeLine in the
drivers/gpu/drm/drm_edid_modes.h but I thing nouveau.ko ignores it. So
my question is what to change (in the kernel source) to override the
detection and force MaxPixelClock to 162MHz just to make sure that the
problem is related to PixelClock. To build the kernel I used the kernel
tree downloaded from nouveau about one week ago.
Thanks in advance for any help.
next reply other threads:[~2010-09-25 14:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 14:04 Grzesiek Sójka [this message]
[not found] ` <4C9E0167.8000507-t9zbU3WrWHI@public.gmane.org>
2010-09-27 21:41 ` GeForce FX5200 dual DVI & Samsung 204b Pekka Paalanen
[not found] ` <20100928004117.0a0ae0ca-cxYvVS3buNOdIgDiPM52R8c4bpwCjbIv@public.gmane.org>
2010-09-28 10:43 ` Grzesiek Sójka
[not found] ` <4CA1C6C0.1000709-t9zbU3WrWHI@public.gmane.org>
2010-09-28 14:02 ` Pekka Paalanen
[not found] ` <20100928170227.00665f76-cxYvVS3buNOdIgDiPM52R8c4bpwCjbIv@public.gmane.org>
2010-09-28 16:17 ` Grzesiek Sójka
[not found] ` <4CA21515.4030903-t9zbU3WrWHI@public.gmane.org>
2010-09-29 16:31 ` Pekka Paalanen
[not found] ` <20100929193136.644e0d68-cxYvVS3buNOdIgDiPM52R8c4bpwCjbIv@public.gmane.org>
2010-09-30 10:41 ` Francisco Jerez
[not found] ` <878w2jike0.fsf-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>
2010-09-30 15:13 ` Grzesiek Sójka
[not found] ` <4CA4A934.4080109-t9zbU3WrWHI@public.gmane.org>
2010-09-30 16:05 ` Francisco Jerez
[not found] ` <87zkuzgqsv.fsf-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>
2010-09-30 18:06 ` Grzesiek Sójka
[not found] ` <4CA4D199.8010403-t9zbU3WrWHI@public.gmane.org>
2010-09-30 23:29 ` Francisco Jerez
[not found] ` <87pqvuhksw.fsf-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>
2010-10-01 10:22 ` Grzesiek Sójka
[not found] ` <4CA5B64D.8000608-t9zbU3WrWHI@public.gmane.org>
2010-10-02 13:31 ` Francisco Jerez
[not found] ` <871v88hgam.fsf-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>
2010-10-05 10:17 ` Grzesiek Sójka
[not found] ` <4CAAFB3A.8010804-t9zbU3WrWHI@public.gmane.org>
2010-10-05 12:55 ` Francisco Jerez
[not found] ` <87fwwkhk8h.fsf-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>
2010-10-05 13:27 ` Grzesiek Sójka
2010-10-05 14:53 ` Grzesiek Sójka
[not found] ` <4CAB3BDC.4070502-t9zbU3WrWHI@public.gmane.org>
2010-10-05 21:33 ` Pekka Paalanen
[not found] ` <20101006003325.3bfb33e9-cxYvVS3buNOdIgDiPM52R8c4bpwCjbIv@public.gmane.org>
2010-10-05 21:45 ` Marcin Slusarz
[not found] ` <20101005214537.GA4034-OI9uyE9O0yo@public.gmane.org>
2010-10-05 21:53 ` Grzesiek Sójka
[not found] ` <4CAB9E43.7080801-t9zbU3WrWHI@public.gmane.org>
2010-10-05 21:59 ` Grzesiek Sójka
2010-10-07 2:53 ` Francisco Jerez
[not found] ` <87wrpug1d0.fsf-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>
2010-10-07 19:34 ` Grzesiek Sójka
2010-10-07 18:47 ` Grzesiek Sójka
2010-09-28 10:53 ` Grzesiek Sójka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C9E0167.8000507@pfu.pl \
--to=pld-t9zbu3wrwhi@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.