Issues detected on many computer cores: Since MiSTer v230223, OS v221224

[Maverick-Shark]

Hi

We're detected that a Iot of computer cores are not working or have lost video over VGA since the last firmware and framework update.

I.e.:

-x68000: Video missmatches -Vic20: Green line (on Top)

Current workaround: The only way is rollback to the previous release of MiSTer.

Thanks, Shark

[birdybro]

I suspect this has to do with these changes:

https://github.com/MiSTer-devel/Main_MiSTer/commit/8d735d4e772613f27275e7e476c610c71221eab7

https://github.com/MiSTer-devel/Main_MiSTer/commit/6dcd754ac994f482f51326c0bf98e5564893c02c

Rename your current MiSTer.ini to MiSTerold.ini and then download a new MiSTer.ini (https://github.com/MiSTer-devel/Main_MiSTer/raw/master/MiSTer.ini) and see if that resolves the issue. If not, change the new vga_mode and ntsc_mode ini settings to match your particular situation and see if that resolves it.

[sorgelig]

I wonder why it affects only computer cores according to subject.

[birdybro]

Hrmm good point... I did originally suspect something is incorrect with 31kHz video with the YC changes, however VIC20's native output horizontal frequency is 15.6kHz and x68k is 34kHz, and I think this would be an issue in the template instead of Main if it were the case.

[virtualisoftware]

Something must have changed in the latest Main. After updating, my monitor went black on start, it's a Dell 2007FPb, which is DVI, 4:3 1600x1200, connected with an HDMI->DVI cable, and it always worked fine with this video mode:

video_mode=1600,64,192,304,1200,1,3,46,162

Updating to main, this video mode shows a black screen, although the monitor doesn't display any message which suggests it can't sync (it usually does when there's a problem), it seems it's just black. I also have a Sony CRT connected at the same time through VGA->ScartRGB cable, and that was working normally, even if the DVI monitor was all black.

I had to change the video mode to be like this:

video_mode=1600,48,32,112,1200,3,4,32,130250

Which works but, it would be interesting to know why a Main update would make the video mode I used for a long time inoperative.

[sorgelig]

Any pixel clock mode beyond 148MHz should be considered as a bonus, not documented. Higher clock may work or not depending on many factors like FPGA temperature, voltage fluctuation, if FPGA has not enough cooling then chip may degrade over time. It's unclear from which Main version you updated - may be it was too old and some features were absent. You can try to downgrade Main and see if old video mode works or not.