(no subject)
Nov. 23rd, 2009 11:47 pmToday I discovered the following:
If the KVM isn't set to my Redhat Linux desktop when it starts, then it misdetects the monitor and decides that it is only capable of 800x600. Not unreasonable, but rather annoying.
KDE does not have an equivalent of the Windows "Hide modes that this monitor cannot display" checkbox. Instead KDE only shows modes that it thinks the monitor is capable of, and provides no way to override this in KDE's desktop properties.
Using the display properties to explicitly force the monitor type to "LCD, 1280x1024" requires logging out and back in.
Changing the resolution using the same program requires logging out and back in.
Yes, I have ranted about similar before. Except this time I wasn't running an unusual multi-monitor setup and I wasn't running from a LiveCD.
If the KVM isn't set to my Redhat Linux desktop when it starts, then it misdetects the monitor and decides that it is only capable of 800x600. Not unreasonable, but rather annoying.
KDE does not have an equivalent of the Windows "Hide modes that this monitor cannot display" checkbox. Instead KDE only shows modes that it thinks the monitor is capable of, and provides no way to override this in KDE's desktop properties.
Using the display properties to explicitly force the monitor type to "LCD, 1280x1024" requires logging out and back in.
Changing the resolution using the same program requires logging out and back in.
Yes, I have ranted about similar before. Except this time I wasn't running an unusual multi-monitor setup and I wasn't running from a LiveCD.
no subject
Date: 2009-11-24 06:51 pm (UTC)So far I've also discovered that it can only process change-system hotkeys when the system it's currently connected to is processing keyboard events, it appears to reinit the mouse on every switch, it doesn't manage keyboard repeat and mouse acceleration, and it's incapable of being hotplugged.
I do wonder how they managed to make it suck so much, as the KVM I have at home handles all of the above perfectly (maintains keyboard and mouse state, does not rely on host to process keyboard events, fully hotpluggable, has a reset button!) and only suffers from having Ctrl as the hotkey. Then again, I wouldn't be surprised if it solves the DDC problem by not implementing it (though a half-decent system should handle that situation...)