Comment # 5 on bug 952781 from Felix Miata

AFAICT, it's not a SiS chipset. It only depends on the SiS driver for access to
non-VESA modes native to virtually all displays made in the past decade:
# lspci | grep VGA
0a:03.0 VGA compatible controller: XGI Technology Inc. (eXtreme Graphics
Innovation) Z7/Z9 (XG20 core) (prog-if 00 [VGA controller])

It's on a 64-bit server motherboard:
http://b2b.gigabyte.com/products/product-page.aspx?pid=2350

Thus, it wouldn't have been a big seller, like those server motherboards with
prior century Matrox gfxchips sold around a decade ago and with its users
complaining in the not too distant past about mga driver foibles. Couple that
with the fact that pre-release bug reporters and pre-release testers are a tiny
fraction of total user population, and nobody would expect to hear much from
users of this particular gfxchip. That's something I can do, give people a
chance to find out about bugs before it's too late for them to get fixed
(hopefully before an upcoming GA), so they don't blindly upgrade into an
unacceptable condition. Whether it would ever get fixed is a whole different
matter. *I* don't need it to work, because it's nothing but a test machine.
Some among the multitude of others might not be so lucky.

I would like to have reported this upstream, but wasn't able to reproduce on
this machine for lack of the sis driver in other installed distros, which
apparently force many users needing to stay secure into either using distorted
non-native display modes, changing their hardware, or changing to a more
complete distro.