Hard to say for sure, we know your adapter sends bogus EDID, kernel mode setting seems to be either more strict or had a regression regarding this, the latter could possibly get fixed, but as we cannot reproduce this on machines here it's hard to diagnose for use, and as there seems to be a valid workaround using the
If it's a more of a general issue, i.e., hitting quite some MGA based systems I'd figure that it will get fixed.
nomodeset param the actual impact can be reduced to about zero, FWICT.If it's a more of a general issue, i.e., hitting quite some MGA based systems I'd figure that it will get fixed.