I've added the intel driver as the probable source of the bug. Since "xresprobe i810" gives the correct result, it suggests the intel driver itself is to blame.
I've added the intel driver as the probable source of the bug. Since "xresprobe i810" gives the correct result, it suggests the intel driver itself is to blame.