OS/2, eCS & ArcaOS - Technical > Hardware


(1/3) > >>

Dave Yeo:
So this computer I'm using has a Sandybridge/Ivybridge graphics controller with a VGA and a Displayport ports, monitor has VGA and DVI ports and supports 1920x1200 as its native resolution.
For quite a while I was simply using the VGA connection, everything worked fine but slightly blurry.
Then I came across a Displayport to DVI passive connector so I tried that.
While the graphics were sharper, especially text mode, I came across these limitations. The screensaver would put the monitor to sleep but it would not wake up, forcing a reboot to awaken it. Same with SNAP and Panorama. Nothing I tried helped here, worked fine under Linux, which reported a HDMI connection. The other thing was I tried using Xfree86 using the VESA (VBE) driver, it simply did not find a graphics card at all, which was weird. Works fine with the VGA connector and an older Panorama/SNAP, newer ones seem to have done something to support UEFI where switching back to the WPS fails, a bit of drawing and then a full hang.
Just wondering about others experience with Displayport and OS/2. Perhaps a monitor that supports Displayport would be better, it seems that Displayport falls back to a DVI compatible protocol when used with a passive converter.

Andi B.:

--- Quote ---Just wondering about others experience with Displayport and OS/2. Perhaps a monitor that supports Displayport would be better, it seems
--- End quote ---
I'm using DP out to DP in on the monitor since a while on this system. But I disabled all screen saving software long ago cause it didn't work. When I've the need for power saving (and don't wanted to switch off the whole system) I switch of the monitor with its remote control. Switching on afterwards works with OS/2. But not with Win7. As this simple test does not even work with Win I never tried to test anymore off this stuff.

Screen saver, actually switching monitor power on/off, never worked on this system. It worked on my old system when I patched black10x.zip to write the proper registers of my old ATI300 graphic card. But never on this newer system. Either with integrated (Intel) graphic nor with the PCIe Radeon 550.

--- Quote ---that Displayport falls back to a DVI compatible protocol when used with a passive converter.
--- End quote ---
This is a feature of your motherboard/graphic chip. The signals are different between DP and DVI. Your mobo detects the DVI adapter and tells the graphic chip and the output transmitter to switch signals to DVI standard. That's a feature of some mobos/graphic cards but not mandatory. Your DP output at your mobo emulates DVI signals when you put a passive adapter on that. But it does not make a real fully compatible DVI interface out of it.

--- Quote ---forcing a reboot to awaken it.
--- End quote ---
Maybe it's enough to disconnect the passive adapter and reconnect it again. But as it's an emulated DVI it will work different on different mobo/graphic cards. I think you would need reports from people with exactly the same motherboard.

Dariusz Piatkowski:
Hi Dave,

I'm afraid I cannot add much in terms of a "fix", but I will say this is interesting because having set up my dual display config here (Dell DU2412M) and being fed by my old trusty ATI X850XT PE, I am dealing with 1 of the units being hooked up through DVI and the 2nd one through VGA.

This is primarily a limitation of the current SNAP drivers, which do not support the ATI card's dual DVI ports to drive matching DVI ports on the display units.

The end result is that the VGA connected 2nd display is a little fuzzier (barely there, but my eyes pick this stuff up, so I can see it) and it does get slightly impacted by the VGA port's 'Pixel Clock' and 'Phase' settings. This sometimes results in that tell-tale noise when you display some dithered colour & texture combinations on the screen. Again, no biggie...but heck, with modern day hardware why suffer like this??? LOL

So point being, I have been meaning to try the monitor's DisplayPort as well, would need to use a DVI to DP connector, etc, but I'm curious how that might pan out?

Dave Yeo:
Hi Andi, so it seems to be a limitation of emulating DVI, makes sense.
As for the screensaver, it might wel work for you now given a recent Panorama.
I'll attach a simple test program, run "panodpms c" to see the capabilities of your system. Panoutil.cmd is a safe way to test, it should turn off your monitor and wait till you press a key and then turn it back on, if it works, then the most recent screensaver will work as well. Note that now a days only on and off make sense with LCD monitors.

Hi Dariusz, I'd guess the DVI to Displayport adapter might work, you'd have to test, might only be available as an active adapter, hopefully simply using USB power. Let us know if you ever try it. 

Ican't help wondering why people keep on using something designed to prevent phosphor burn in on CRT monitors when it doesn't work on modern LCD panels.  I gave up using a screen saver back in 1990 when I pensioned off my CRT monitor for a 28" LCD unit.

As for using the DISPLAY port, I started using that when I built my first third generation Ryzen computer (MSI B550-A Pro board with a AMD Ryzen 3 Pro 4350G CPU), coupled with a Samsung S24E650 LCD monitor (display port to display port cable supplied by Samsung).  It worked very well during the testing phase but I have since gone to using HDMI through a 4 port USB/HDMI switch to allow switching all the computers on the network.


[0] Message Index

[#] Next page

Go to full version