Ok here the info:
Display gamma 2.20
Maximum Image Size 53x30cm
PowerManagement Standby no Suspend no ActiveOff yes
Monitor Name SyncMaster
Serial Number H9XSA38290

Established timings:
800x600@60
800x600@56
640x480@60
1024x768@60

Standard Timing Identification:
1280x800@60hz (16:10)
Not Found: 1280x800@60hz (16:10) - calling CVT(RB=1)
1280x960@60hz (4:3)
1280x1024@60hz (5:4)
1440x900@60hz (16:10)
Not Found: 1440x900@60hz (16:10) - calling CVT(RB=1)
1600x1200@60hz (4:3)
1680x1050@60hz (16:10)
Not Found: 1680x1050@60hz (16:10) - calling CVT(RB=1)

Mode 1920x1080@60hz 67khz
DotClock 148500000hz
HTimings 1920 2008 2052 2200
VTimings 1080 1084 1089 1125
Image Size 531x298mm
Flags progressive +hsync +vsync

Monitor Range Limits:
Horizontal frequency 30 - 81khz
Vertical frequency 56 - 60hz
Pixelclock 170Mhz

@stedy

Thank you for the detailed explanation which is no doubt also useful for some of our developers.

It is unfortunate you do not have access to an AmigaOS 4.1 capable computer, hopefully this situation can be rectified sometime in the future.

_________________

@rigo

DVI-VGA input Works (with DVI-VGA adaptor on video Card) (#1)
DVI-DVI does not (#2)
-------------------------------------------------------------------------
msr = 0x00001030
[keybdevLIBInit] LibInit of keyboard device
Scanning bus 'dvi'
0000: 00 FF FF FF FF FF FF 00 22 F0 12 26 01 01 01 01 ........"..&....
0010: 23 0F 01 03 0F 29 1F 78 EA 26 95 A2 57 4A 9D 25 #....).x.&..WJ.%
0020: 13 50 54 A5 6F 80 31 59 45 59 61 59 81 40 81 80 .PT.o.1YEYaY.@..
0030: 81 99 A9 40 A9 4F 48 3F 40 30 62 B0 32 40 40 C0 ...@.OH?@0b.2@@.
0040: 13 00 98 32 11 00 00 1E 00 00 00 FD 00 30 55 1E ...2.........0U.
0050: 5E 15 00 0A 20 20 20 20 20 20 00 00 00 FC 00 68 ^..............h
0060: 70 20 4C 32 30 33 35 0A 20 20 20 20 00 00 00 FF p.L2035.........
0070: 00 43 4E 50 35 33 35 59 32 58 36 0A 20 20 00 47 .CNP535Y2X6....G
EDID V1.3
ManufacturerID HWP ProductID 2612
SerialNo 16843009 Manufactured week 35 of 2005
Input type analog
Display gamma 2.20
Maximum Image Size 41x31cm
PowerManagement Standby yes Suspend yes ActiveOff yes
Monitor Name hp L2035
Serial Number CNP535Y2X6

Established timings:
800x600@60
640x480@75
640x480@60
720x400@70
1280x1024@75
1024x768@75
1024x768@70
1024x768@60
832x624@75
800x600@75

Standard Timing Identification:
640x480@85hz (4:3)
800x600@85hz (4:3)
1024x768@85hz (4:3)
1280x960@60hz (4:3)
1280x1024@60hz (5:4)
1280x1024@85hz (5:4)
1600x1200@60hz (4:3)
1600x1200@75hz (4:3)

Mode 1600x1200@60hz 75khz
DotClock 162000000hz
HTimings 1600 1664 1856 2160
VTimings 1200 1201 1204 1250
Image Size 408x306mm
Flags progressive +hsync +vsync

Monitor Range Limits:
Horizontal frequency 30 - 94khz
Vertical frequency 48 - 85hz
Pixelclock 210Mhz
it8212ide.device 53.3 (05.02.2009)
lsi53c8xx.device 53.3 (05.02.2009)
sii0680ide.device 53.3 (05.02.2009)
sii3112ide.device 53.3 (05.02.2009)
sii3114ide.device 53.3 (05.02.2009)
[sii3114ide/mode_select] xfer mode 70 asked not supported by unit 3, trimmed to 69
sii3512ide.device 53.3 (05.02.2009)
No cards found!
No SOLO_ONE found!
No SB128 found!
No FM801 found!
No Envy24HT found!
No Envy24 found!
No CMI8738 found!
----------------------------------------------------------------------------------------------------------------------------
msr = 0x00001030
[keybdevLIBInit] LibInit of keyboard device
Scanning bus 'dvi'
0000: 00 FF FF FF FF FF FF 00 22 F0 13 26 01 01 01 01 ........"..&....
0010: 23 0F 01 03 80 29 1F 78 EA 26 95 A2 57 4A 9D 25 #....).x.&..WJ.%
0020: 13 50 54 A5 6F 80 31 59 45 59 61 59 81 40 81 80 .PT.o.1YEYaY.@..
0030: 81 99 A9 40 01 01 48 3F 40 30 62 B0 32 40 40 C0 ...@..H?@0b.2@@.
0040: 13 00 98 32 11 00 00 1E 00 00 00 FD 00 30 55 1E ...2.........0U.
0050: 4C 11 00 0A 20 20 20 20 20 20 00 00 00 FC 00 68 L..............h
0060: 70 20 4C 32 30 33 35 0A 20 20 20 20 00 00 00 FF p.L2035.........
0070: 00 43 4E 50 35 33 35 59 32 58 36 0A 20 20 00 E1 .CNP535Y2X6.....
EDID V1.3
ManufacturerID HWP ProductID 2613
SerialNo 16843009 Manufactured week 35 of 2005
Input type digital
Display gamma 2.20
Maximum Image Size 41x31cm
PowerManagement Standby yes Suspend yes ActiveOff yes
Monitor Name hp L2035
Serial Number CNP535Y2X6

Established timings:
800x600@60
640x480@75
640x480@60
720x400@70
1280x1024@75
1024x768@75
1024x768@70
1024x768@60
832x624@75
800x600@75

Standard Timing Identification:
640x480@85hz (4:3)
800x600@85hz (4:3)
1024x768@85hz (4:3)
1280x960@60hz (4:3)
1280x1024@60hz (5:4)
1280x1024@85hz (5:4)
1600x1200@60hz (4:3)

Mode 1600x1200@60hz 75khz
DotClock 162000000hz
HTimings 1600 1664 1856 2160
VTimings 1200 1201 1204 1250
Image Size 408x306mm
Flags progressive +hsync +vsync

Monitor Range Limits:
Horizontal frequency 30 - 76khz
Vertical frequency 48 - 85hz
Pixelclock 170Mhz
it8212ide.device 53.3 (05.02.2009)
lsi53c8xx.device 53.3 (05.02.2009)
sii0680ide.device 53.3 (05.02.2009)
sii3112ide.device 53.3 (05.02.2009)
sii3114ide.device 53.3 (05.02.2009)
[sii3114ide/mode_select] xfer mode 70 asked not supported by unit 3, trimmed to 69
sii3512ide.device 53.3 (05.02.2009)
No cards found!
No SOLO_ONE found!
No SB128 found!
No FM801 found!
No Envy24HT found!
No Envy24 found!
No CMI8738 found!

_________________
Sam460ex : Radeon Rx550 Single slot Video Card : SIL3112 SATA card

Here is my config once again. Now is DDC enabled:
Scanning bus 'dvi'
0000: 00 FF FF FF FF FF FF 00 4C 2D 8B 05 34 32 49 4B ........L-..42IK
0010: 2C 13 01 03 80 35 1E 78 2A 60 41 A6 56 4A 9C 25 ,....5.x*`A.VJ.%
0020: 12 50 54 23 08 00 81 00 81 40 81 80 95 00 A9 40 .PT#.....@.....@
0030: B3 00 01 01 01 01 02 3A 80 18 71 38 2D 40 58 2C .......:..q8-@X,
0040: 45 00 13 2A 21 00 00 1E 00 00 00 FD 00 38 3C 1E E..*!........8

Here is my config once again. Now is DDC enabled:
Scanning bus 'dvi'

EDID V1.3
ManufacturerID SAM ProductID 058B
SerialNo 1263088180 Manufactured week 44 of 2009
Input type digital
Display gamma 2.20
Maximum Image Size 53x30cm
PowerManagement Standby no Suspend no ActiveOff yes
Monitor Name SyncMaster
Serial Number H9XSA38290

Established timings:
800x600@60
800x600@56
640x480@60
1024x768@60

Standard Timing Identification:
1280x800@60hz (16:10)
Not Found: 1280x800@60hz (16:10) - calling CVT(RB=1)
1280x960@60hz (4:3)
1280x1024@60hz (5:4)
1440x900@60hz (16:10)
Not Found: 1440x900@60hz (16:10) - calling CVT(RB=1)
1600x1200@60hz (4:3)
1680x1050@60hz (16:10)
Not Found: 1680x1050@60hz (16:10) - calling CVT(RB=1)

Mode 1920x1080@60hz 67khz
DotClock 148500000hz
HTimings 1920 2008 2052 2200
VTimings 1080 1084 1089 1125
Image Size 531x298mm
Flags progressive +hsync +vsync

Monitor Range Limits:
Horizontal frequency 30 - 81khz
Vertical frequency 56 - 60hz
Pixelclock 170Mhz
it8212ide.device 53.3 (05.02.2009)
lsi53c8xx.device 53.3 (05.02.2009)
sii0680ide.device 53.3 (05.02.2009)
sii3112ide.device 53.3 (05.02.2009)
sii3114ide.device 53.3 (05.02.2009)
sii3512ide.device 53.3 (05.02.2009)
No cards found!
No SOLO_ONE found!
No SB128 found!
No FM801 found!
No Envy24HT found!
No Envy24 found!
No CMI8738 found!
-----------------------------------------------------

Last edited by Deschain on 17-Jan-2010 at 06:11 PM.

@stedy
Quote:

What level of parameters can you pass to the monitor driver?

vsync min/max
hsync min/max
refreshrate of mode
width
height
doublescan mode (is automatically activated when the h frequency of the given mode drops below hsyncmin, but can be forced)
h/v sync polarity (default is +)
reduced blanking on/off

@rigo

EDID V1.3
ManufacturerID SAM ProductID 0526
SerialNo 1280455219 Manufactured week 46 of 2009
Input type digital
Display gamma 2.20
Maximum Image Size 51x29cm
PowerManagement Standby no Suspend no ActiveOff yes
Monitor Name SyncMaster
Serial Number H9MSB04126

Established timings:
800x600@60
800x600@56
640x480@60
1024x768@60

Standard Timing Identification:
1280x800@60hz (16:10)
Not Found: 1280x800@60hz (16:10) - calling CVT(RB=1)
1280x960@60hz (4:3)
1280x1024@60hz (5:4)
1440x900@60hz (16:10)
Not Found: 1440x900@60hz (16:10) - calling CVT(RB=1)
1600x1200@60hz (4:3)
1680x1050@60hz (16:10)
Not Found: 1680x1050@60hz (16:10) - calling CVT(RB=1)

Mode 1920x1080@60hz 67khz
DotClock 148500000hz
HTimings 1920 2008 2052 2200
VTimings 1080 1084 1089 1125
Image Size 510x287mm
Flags progressive +hsync +vsync

Monitor Range Limits:
Horizontal frequency 30 - 81khz
Vertical frequency 56 - 60hz
Pixelclock 170Mhz

Last edited by hotrod on 17-Jan-2010 at 07:46 PM.

..

Last edited by hotrod on 17-Jan-2010 at 08:16 PM.
Last edited by hotrod on 17-Jan-2010 at 07:59 PM.

@rigo

Any news, tips or something? I'm using analog at the moment which is better than nothing but I would really like to use DVI. I tried to edit the settings with picasso96mode which didn't work either.

One question... if I add a mode to the monitor driver tooltype like 1920x1080@60-vsync+RB isn't it supposted to show up in prefs/screenmode like +RB too? for some reason it didn't.

The Tool Picasso96Mode doesnt work here too

@thread

*bump*

@thread

Taking a look at the EDID data, nothing looks incorrect, I even check the values in the hex dump of the ROM!

Whilst the timings do not match exactly with the VESA CVT timings, the pixel clock is less than the 165 MHz limits of DVI.

Going back to the descriptions of the problem, I would suggest looking at the graphic card setup, possibly better suited to Hyperion?

Is the GPU and memory being clocked at the correct frequency?

Have experienced issues of graphics corruption where the graphics memory clock was running too fast. Is it possible to declock the DRAM interface and the GPU core by 10% and try again. As the display resolutions are large, you will put more strain on the framebuffer interface.

Is there any way to force a wait for VSYNC update?
Half finished framebuffers can have interesting results.

If anyone can get a picture or short video of the graphical glitches, that is good to see.

Good luck,

Ian

Someone any idea?

I think the GPU works in my SAM correctly. But i am also not able to change the card to an other. It is a low profile Radeon 9250 with 12MB it was never overclocked and works for example with QUAKE 3 in 3D very well. With 4.1 beta i never had blanking problems after i set "+RB" in the tooltypes.

@stedy: i cant make any movies about the blanking. but it is quiet easy to explain. it is enough to click on a window or open a draver so the screen is going black for few seconds. you also cant move the windows on the screen because the screen goes once again black. if you move it very very slow the screen steys ok but the system is not usable in this case.

Last edited by Deschain on 20-Jan-2010 at 06:39 PM.

@thread

Just plugged my viewsonic 22" monitor into my sam EP and got exactly this - works for a little while from cold then starts blanking out whenever a windowy type operation happens.

would be interested to know if anybody has solved this?

Rich.

@RockDemon

Also couldnt make up my mind if it happened more at higher resolutions. ( Max is 1680x1050) - i tried 640x480 and it didnt seem to go black as often.... I need to do a little more investigation to confirm this....

Last edited by RockDemon on 07-Feb-2010 at 10:34 PM.

@RockDemon

As suggested it works on VGA, but the output quality is horrid... Surely this isnt the best it's going to get? Going to have to go back tothe 15" monitor at 1024x768 if only to get a decent picture at this rate...

@All

YES! I've FINALLY got rid of the blanking! Sorry for screaming but I'm really happy right now. The quality of the picture is much better offcourse and makes using AmigaOS much more fun

None of the settings that I've tried worked, not DDC modes, not manual settings, nothing! But when I was using Linux on the PC I had a look at the "Information" on the OSD on the flatscreen and it showed that it was runing at 50Hz for some reason. Anyway, that fixed it!

I don't know why, when using Windows or MacOS X it shows that it's runing at 60Hz (yes it doesn't matter for flatscreens I know but how to figure that out?) . Using the VSYNC and HSYNC settings from the manual doesn't allow me to use something as low as 50Hz IIRC so I had to change the VSYNCMIN setting too.

Anyway, I don't care why it works I'm just happy that it works. Sounding like a complete n00b but I don't care, I'm really happy right now .

However, lets hope that it can made to work with DDC for the next release of AmigaOS anyway.

@hotrod

I had an older syncmaster. It would blank for a fraction of a second intermittently. It seems like it started when I updated to Windows Vista. I suspected it was a driver problem. This monitor had two input connectors, a VGA and DVI. If I used the VGA connector the blanking didn't occur and the picture quality was the same. I just used the VGA connector instead of the DVI.

_________________
X5000 / microA1(OS4.1 FE U2) / CodeBench / Imagine / Blender
Lightwave 2019 / Microsoft Visual C++

@thinkchip

Well this one isn't old, I got it for christmas last year, a Samsung P2350. DVI worked fine with Windows 7, MacOS X 10.5 and Linux but not with AmigaOS 4.1. VGA worked but it didn't look the same, the picture was darker and slightly flickering which was anoying compared to the quality when using the other operating systems. Sure it's ok but knowing that it can look better made the whole Amiga experience bad. The colours wasn't as strong and the picture wasn't as crisp.

I had an older 19" SyncMaster which worked great, this issue seems to happen with newer flatscreens (widescreen). It's supposed to work fine with DDC but it didn't, neither did the settings found in the manual work using tooltypes nor did I manage to get it to work with Picasso96Mode.

I wonder why the Hz/kHz settings are different in Windows compared to Linux though. Anyway, the picture is great now and it's a joy to use AmigaOS now, it just looks great. Not as dark and pale and without the slight flickering. It looks sharper too.

Last edited by hotrod on 27-Oct-2010 at 11:33 PM.

@thread

Reading about the issues with the DVI mode, I know what can cause it.

The DVI driver, built-in to a GPU has internal circuitry to detect external loads, this facilitates hot plugging of monitors. Obviously MS-Windows supports this implicitly.

Linux drivers do not have full support for this feature and sometimes the detection circutry is disabled, instead an xWindows -vidmode setting is used to implicitly enable DVI/TMDS output.

If the graphics card has an external DVI encoder device, it is less likely to be susceptible to such issues. If the graphics card has two DVI outputs, try the second one as it may not be on-chip.

I had a similar issue, with a graphics card I designed under Windows, it would work OK until the vendors drivers kicked in, then the DVI output would be flaky. Using the other driver, which did not have the detection logic, rather it initialised the DVI output, the display worked fine. The specifics of this mechanism should be known to Hyperion, sorry can't go into specifics here.

Part of the problem in my specific case was down to signal integrity. If I used a 5 Metre DVI cable, it helped to cancel out the small (less than 30mm) tracking stub caused by a test connector. So if you have a long, DVI cable, try it. DVI is specified for cables upto 50 metres, though I have run it at 8 metres with no problems at lower pixel rates.

DVI does work reliably at PAL (720x576 x 50 Hz interlaced) resolutions as the pixel clock is above the DVI minimum. How the panel handles non-standard pixel rates is down to the interface electronics. In the examples cited earlier, the LCD panel has a native resolution of 1920x1080 pixels @ 60 Hz, for any other screenmode, the control electronics will scale the display accordingly.

Hope this provides an insight into some of the joys of digital video.

Ian