Bug 12439

Xorg.0.log with Option "ModeDebug" "YES" in your driver section required to actually help.  Output of xrandr --verbose may also help.

Created attachment 11606 [details]
xorg.0.log as requested

xorg.0.log as requested

Created attachment 11607 [details]
xrandr --verbose output 

xrandr --verbose output as requested

Thank you for assistence :)

Your log shows you getting the correct mode detected and chosen for your monitor.  You should also be getting an appropriate clock chosen I think.  Not sure what's going on here, but DDC seems fine.

Can you describe the flicker better?  Is it happening on a bare X Server?

It happens on clean Xserver, on kde, on gnome... Flickering is just flickering,the window "vibrate" like my frequencies are wrongs in top half of my screen (or 1/3 top)

All clear with <2.* drivers

It happens on clean Xserver, on kde, on gnome... Flickering is just flickering,the window "vibrate" like my frequencies are wrongs in top half of my screen (or 1/3 top)

All clear with <2.* drivers

we happen have this monitor. IIRC, though we have some issue with it, but didn't see this weird behavor... 

 re-assign to Hong.

ask me whatever you need and I will post it... I'm currently stuck with 1.7.4 driver because of this flickering with >=2.0

(In reply to comment #8)
> ask me whatever you need and I will post it... I'm currently stuck with 1.7.4
> driver because of this flickering with >=2.0
> 

what is your monitor saying about the mode (there should be somewhere in your monitor OSD menu).

Thanks,
Hong

On my OSD info:

with 1.7.4 driver

Analog
65KHz 60Hz PP
1680x1050

Kilohertz changes randomly every time I boot up, sometimes is 65, sametimes is 64.7 but no problem at all

With 2.0 driver

Analog
64.7KHz 60Hz NP
1680x1050

Every time 64.7 with 2.0 driver, but I don't know what this "NP" means

(In reply to comment #10)
> On my OSD info:
> 
> with 1.7.4 driver
> 
> Analog
> 65KHz 60Hz PP
> 1680x1050
> 
> Kilohertz changes randomly every time I boot up, sometimes is 65, sametimes is
> 64.7 but no problem at all
> 
> With 2.0 driver
> 
> Analog
> 64.7KHz 60Hz NP
> 1680x1050
> 
> Every time 64.7 with 2.0 driver, but I don't know what this "NP" means
> 

PP: +hsync +vsync
NP: -hsync +vsync
Seems we need to add a quirk to your monitor.

Would you please add a new modeline and try if it works?

#xrandr --newmode 1680x1050_60 146.2 1680 1784 1960 2240 1050 1053 1059 1089 +hsync +vsync
#xrandr --addmode VGA 1680x1050_60
#xrandr --output VGA --mode 1680x1050_60

(The only change of this mode is use +hsync.)

Thanks,
Hong

still no luck :(

sovereign flocchini # xrandr --newmode 1680x1050_60 146.2 1680 1784 1960 2240 1050 1053 1059 1089 +hsync +vsync
X Error of failed request:  BadName (named color or font does not exist)
  Major opcode of failed request:  156 (RANDR)
  Minor opcode of failed request:  16 ()
  Serial number of failed request:  16
  Current serial number in output stream:  16
sovereign flocchini # xrandr --addmode VGA 1680x1050_60
sovereign flocchini # xrandr --output VGA --mode 1680x1050_60

I paste exactly what you wrote, as user or root, flicker remains and my osd info now shows:

 Analog
 65KHz 60Hz NN
 1680x1050

Not the expected "PP"

I also tried to change to -hsync -vsync (same flicker problem, NN) and +hsync -vsync. With +hsync -vsync I only get 1400x1050, no flicker, PN, but if I force it to 1680x1050 (xrandr -s 1680x1050) flicker returns

For whatever reasons using xrandr doesn't work for you. I suggest to add the modeline manually to Section "Modes" of your /etc/X11/xorg.conf.

# 1680x1050 @ 60.00 Hz (CVT)
#   field rate 59.95 Hz; hsync: 65.29 kHz; pclk: 146.25 MHz
Modeline "1680x1050_60.00"  146.25  1680 1784 1960 2240  1050 1053 1059 1089
+HSync +Vsync

("Modeline..." is one line; stupid Bugzilla!)

Then make sure that your Section "Monitor" is referenced properly in Section "Device". And that Section "Modes" is again referenced in Section "Monitor". Something like this.

Section "Monitor"
  Identifier "Monitor[0]
  [...]
  UseModes     "Modes[0]"
EndSection

Section "Modes"
  Identifier   "Modes[0]"
  [...]
  # must be one line!
  Modeline "1680x1050_60.00"  146.25  1680 1784 1960 2240  1050 1053 1059 1089
  +HSync +Vsync
EndSection

Section "Device"
  [...]
  Option "monitor-VGA" "Monitor[0]"
  [...]
EndSection

it doesn't work. I still get flickering and my osd still shows 

Analog
64.7KHz 60Hz NP
1680x1050

Well, I forgot one important thing. Add the ""1680x1050_60.00" mode to the appropriate Subsection of Section "Screen".

wooooooooooow now it works! :D

I didn't notice previous mistake in xorg.conf because I usually define modeline in different way instead of your "Modes" section. I checked and even modifying my standard xorg.con works like a charm.

My current Monitor section:

Section "Monitor"
        # Block type: 2:0 3:fd
        # Block type: 2:0 3:fc
        Identifier "Desktop Monitor"
        Option "DPMS"
        VendorName "SAM"
        ModelName "SyncMaster"
        DisplaySize     433 270
        # Block type: 2:0 3:fd
        HorizSync 30-81
        VertRefresh 56-75
        # Max dot clock (video bandwidth) 160 MHz
        # Block type: 2:0 3:fc
        # Block type: 2:0 3:ff
        # DPMS capabilities: Active off:yes  Suspend:no  Standby:no

        Mode    "1680x1050"     # vfreq 59.954Hz, hfreq 65.290kHz
                DotClock        146.250000
                HTimings        1680 1784 1960 2240
                VTimings        1050 1053 1059 1089
                Flags   "+HSync" "+VSync"
        EndMode
        # Block type: 2:0 3:fd
        # Block type: 2:0 3:fc
        # Block type: 2:0 3:ff

Option              "PreferredMode" "1680x1050"
        Option              "DPMS"
        Option              "NoDDC"
        Option              "ModeValidation" "NoMaxPClkCheck"

EndSection

Thank you all very much

The inf file provided by Samsung for windows has this in it:

[SM205BWa.AddReg]
HKR,"MODES\1680,1050",Mode1,,"30-81,56-75,+,+"
HKR,,ICMProfile,0,"SM205BW.icm"

[SM205BWd.AddReg]
HKR,"MODES\1680,1050",Mode1,,"30-81,56-75,+,+"
HKR,,ICMProfile,0,"SM205BW.icm

Any hint we can get from it?

(In reply to comment #17)
> The inf file provided by Samsung for windows has this in it:
> 
> [SM205BWa.AddReg]
> HKR,"MODES\1680,1050",Mode1,,"30-81,56-75,+,+"
> HKR,,ICMProfile,0,"SM205BW.icm"
> 
> [SM205BWd.AddReg]
> HKR,"MODES\1680,1050",Mode1,,"30-81,56-75,+,+"
> HKR,,ICMProfile,0,"SM205BW.icm
> 
> Any hint we can get from it?
> 

It seems the 1680x1050 mode of this monitor always requires +hsync +vsync.

Created attachment 12379 [details] [review]
patch to try

Please try the attached patch which added a quirk to the samsung 205BW monitor to use +h +v for the  edid detailed mode.

Your monitor should work without the modeline hack to xorg.conf.

Thanks,
Hong

works on xorg 7.3 (xorg-server 1.4-r1)

 ;)

mark fixed. 

reopen for discussion, as the patch was reverted from tip...

Oh, this one was not about flipping polarities, just setting both to positive.  Re-commit it, I guess.

(In reply to comment #23)
> Oh, this one was not about flipping polarities, just setting both to positive. 
> Re-commit it, I guess.
> 

Eric, can you help to commit it to xorg? I don't have the commit right.

Thanks,
Hong

patch pushed, close this one.