drm: Fixes it so we don't show a danglign cursor

When rotating the display right after start I'd get 2 cursors, one of them that doesn't move.

It's to be seen why drmModeSetCursor is failing on this AMD Ryzen based device and not on similar intel ones (I have the impression that we may be calling it wrong somehow because it's returning -EINVAL) but in any case we need this change in to make sure that when we fall back to software cursors, we won't be triggering the wrong code path.