Quote:
That's even more frightening, considering the resolution mentioned last in my screenmode selection

Quote:
Unfortunately windows does not let me select this resolution by default. So, instead i fired up amipup.

Ok, i've seen a lot of weird things in my life but this.... !?

All of a sudden (after booted into linux) my monitor started spilling refresh rates in the OSD menu as well (for AROS/Windows also now). Is there any sense in asking how that is possible ?

Now, if i select that same screenmode (640) it actually reports as being in 640x480 mode.

Testing the 640x480 resolution in amipup provided me with a refreshrate of 75Hz.


Quote:
This resolution still seems to be a problem. Also not possible to select in Windows and unfortunately also not in AmiPup. (the attached log might perhaps tell why)

Quote:
Instead of my clumsy attempts to make sense of this all, i thought it would perhaps be easier for you if i attached a log from amipup's Video-Info tool.

I would also like to make a note, that might or might not be of importance. I never understood it, but windows always reported that i have 2 monitors, both having the same list of supported resolution. The second monitor (that isn't identifiable) supports more resolutions, both as combined with the other monitor (f.i. 2048x5136) as well as lower resolution (640x480). The second monitor also reports to support a bitdepth of 8 while the first doesn't.

I figured that might be because the video connector on the eee-box is actually a DVI-I connector, in which case it should theoretically be possible to attach both a digital as well as analog connector (by using a splitter). The monitor currently attached uses a (analog) vga cable.

I have no idea, but perhaps this could confuse AROS (just as it does me )

Please let me know if there is anything else i can test/do/etc. as it would be nice to know how these things can be avoided in future (besides smashing faulty reporting monitors too smithereens )

red: typo's and better description.

RED2: happen to have stumbled on a 1.4.5 icaros pendrive, dopus config opens a 640x480@60 screen according to the monitor OSD. e.g. it worked then.

Attach file:

---

Link only for registered users

Quote:

At what refresh rate? What does the monitor report if you select 640x480 at the same refresh rate in Windows?

Quote:

Again, if possible compare this with the same mode in Windows (or a VESA mode).

Update: the modelines appear to be correct in IntelGMA, and I'm assuming for now that they are set up correctly in the hardware registers.

My plan is to check that all details of IntelGMA's modes are correct, i.e. that the "modelines" (in X Windows parlance) match the CVT standard. Consequently, please don't go to too much trouble testing all modes with your monitor just yet

The 69Hz vs 70Hz is more likely to be dodgy arithmetic than a typo

Ok, it seems i need a little more time gathering evidence (taking pictures with camera).

Attached is a snapshot of the resolutions for AROS. It's quite a list, and the monitor's OSD is able to show the active resolution (but to be able to do so, i need to press the button approx. 18 times. That'll take me some time to do for all).

One thing i noticed is that when i select the 640 resolution in screenprefs for testing, that my monitor reports it's in 720x400 mode.

When i select 720x400 mode, my monitor reports it is in 1280x000 mode (tripple zero is not an error/fall off: 1280x1024 displays correctly).

Unfortunately the monitor's OSD does not display the refresh rate :/

Is it really a possibility that the monitor reports back so much bogus information ?

PS: what confuses me even more is that when switching to dopus config it want to switch to "[GMA] InitMode 720x400x16 @ 69Hz" while screenprefs reports 720x400x70. Could that be a typo somewhere ?

Attach file:

---

  (0.00 KB)

Good question.

Other then attached picture, i am not 100% sure how i could gather that information in a more trusted way (*).

In case it matters (i just remembered): when i hooked up this monitor (in a hurry) i got problems using the aros gma driver with default boot option. I needed to explicitly change the refresh rate in order to get a signal for my monitor.

If there is a better way of retrieving diagnostic information (puppy, ubuntu, windows, aros) then please feel free to let me know as i'm out of idea's atm.

I will at least do some testing tomorrow and play with some settings. If it's listed in aros then i should be able to switch to that resolution or use boot options to fine-tune refresh-rate. afaik, i should then be able to figure out if the monitor really supports that resolution/refreshrate or not.

in case wondering, i lack documentation for this monitor, as it's a very old medion (not listed on their website anymore, and generic search did not reveal the correct docs yet :/)

(*) i meant, a method which gathers more reliable values.

Attach file:

---

  (0.00 KB)

@Magorium

Does 1280x1024@60 work in Windows or Linux? If so, maybe the 1Hz difference matters.

/me scratches head...

@ncafferkey:
I would have sworn the following are not all listed in aros monitor selection. i shall pay better attention next time on native aros.

The information i was able to quickly verify was using intel driver utilities, which reported the following:


As you migh see (i just realized it myself), my main resolution in aros is also off by 1Hz :-S

Strange....

Yeah, using the wb clone solution might perhaps be an option as well, maybe even quicker (i have no idea tbh).

This is intriguing

@Magorium

You could compare the monitor's docs with the list of modes reported by AROS and other OSes.

Looking at the problem another way, it might be better if ConfigOpus clones WB.

Wow, thank you very much for having taking a look at this. I had no idea where to start.

First of all, it seems i missed something regarding the amiga m-n switchback, as i've attempted that in the past (and failed). I now realize that is/was because the monitor turned off too quickly and AROS was unable to bring it back, initially letting me believe there was no way out of that situation.

Now (the wiser), i was fast enough to switch back and catch sashimi

I believe you are spot on, if i look at my log (sorry as i pressed owb by mistake first, i did close it before running dopus though):


Is there any way that i (can be programmatically as well) could verify what my monitor is reporting back ? because (indeed) that frequency alone is dead wrong.

And now that you've discovered the culprit, i realize i ran into this problem because my hd monitor broke down and i connected it to an old lcd monitor when i ran into this issue.

Does that (automatically) means there isn't anything that can be done about this particular issue, unless my monitor starts reporting back correct id's ?

Nice catch btw :thumbsup:

@magorium

I finally got around to testing your Dopus4 problem with analogue output from IntelGMA. I found that ConfigOpus chooses its mode ID automatically with BestModeID(), which may result in an unusual screenmode being selected. For me, it selected 720x400@69Hz (which my monitor reports as 600x400@70Hz).

It's likely either IntelGMA is misinterpreting your monitor's capabilities, or your monitor is providing bogus values. If you run sashimi while ConfigOpus in opening, you can capture output from IntelGMA about what mode is being used. You should be able to return to your workbench screen with LAmiga-M to see/save the results.