My monitor was dcc probed, but the frequency range boxes we're empty, I guessed this was normal, so I just clicked next, testing the config showed me that there we're no valid modes, since the monitor probing went wrong.
Still there in beta3
Will be fixed in the next cut of the beta.
I just tried the 4 march snapshot iso, and it still has this problem, it gets the name of the monitor right (DCC probed) but the frequency boxes are empty, I can continue, but testing any settings consistently fails.
This works for me with a NEC MultiSync E700.
It works for me with some DCC monitors too, but this specific monitor results in empty frequency range boxes. In other words the DCC probe partly failed, the monitor type detected is ok, but it didn't detect valid frequency ranges, and still shows the DCC-probed monitor and advises the user to use it. While using it won't work since there are no frequency ranges. I believe it should only show a DCC probed monitor if the frequency ranges match some kinda sanity check, not having any ranges at all seems like something which should fail this check. This is with a Funai 17" monitor type: FCM1764L
This should be fixed in the next cut of the installer. We found a loophole that needed to be closed up, so that should put an end to any empty sync range boxes.
I just tried 6.2 final (the zoot iso on gribble) and this bug is still there.
What happens if you actually click on the DDC-probed selection in the monitor listing?? Do the sync rates show up then?
Nope, the boxes still stay empty, I selected another monitor and then selected the DCC probed monitor again.
This issue is being forwarded to a developer for further action.
*** Bug 9633 has been marked as a duplicate of this bug. ***
*** Bug 9851 has been marked as a duplicate of this bug. ***
This is sorta fixed in 6.9.0 (Beta 1), now it fills the boxes with the values for a fixed frequency monitor if nothing is detected, wouldn't it be better to just select a generic monitor then, since now it looks to the user as if this is detected and hence is what he should use.
This defect is considered MUST-FIX for Winston Beta-5