https://bugzilla.novell.com/show_bug.cgi?id=350919 Steven Munroe changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |350920 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=350919 User ms@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350919#c2 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |sjmunroe@aol.com Summary|Sax2 Selects "Not Optimum Mode" for Samsumg |sax2: Selects "Not Optimum Mode" for Samsumg |SyncMister 213t |SyncMister 213t --- Comment #2 from Marcus Schaefer 2007-12-28 15:08:34 MST --- if you don't mind send the information from hwinfo --monitor thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=350919 User sjmunroe@aol.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350919#c4 --- Comment #4 from Steven Munroe 2007-12-29 17:24:42 MST --- I cloned this bug to 350920 to show this problem exists on the x86_64 platform as well. The "hwinfo --monitor out put is really off base on this system. sjmunroe@home1:~> /usr/sbin/hwinfo --monitor 31: None 00.0: 10000 Monitor [Created at fb.71] Unique ID: rdCR.EY_qmtb9YY0 Hardware Class: monitor Model: "Generic Monitor" Vendor: "Generic" Device: "Monitor" Resolution: 800x600@75Hz Driver Info #0: Max. Resolution: 800x600 Vert. Sync Range: 50-90 Hz Hor. Sync Range: 31-48 kHz Config Status: cfg=new, avail=yes, need=no, active=unknown This odd because sax2 is set for 1600-1200, gnome-display-properties will let me select 1600-1200 and 60Hz refresh. This gets ride of the "not Optimum Mode" pop up on the Samsung. So x86_64 is even less capable of correctly detecting the 213T correctly then PPC, but for some reason it is more willing to set the display up in a useful mode. This may be a difference in graphic chip set? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=350919 User ms@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350919#c6 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #6 from Marcus Schaefer 2008-01-01 07:45:52 MST --- the wrong timings are used. I update the CDB record with the correct timings according to your information from comment #3 - Modeline="1600x1200" 140.00 1600 1632 2024 2052 1200 1200 1208 1216 + Modeline="1600x1200" 130.37 1600 1648 1680 1760 1200 1202 1206 1235 thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.