Have you ever been annoyed by Linux' lack of a coherent graphical boot process? Graphics hardware causing problems during sleep/wake cycles? Problematic virtual terminal switches? Kernel-based mode-setting, a new feature of Xorg still in heavy development aims to solve many of these problems by moving the mode-setting code from the user-space X driver into the Linux kernel. Phoronix takes a look at this new feature.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-07-06
one should think so as there is no longer a need for a "sync" between the kernel and X about what state the card is in.
btw, is it just me or have there yet to be a "sync" based system that works flawlessly under load, for any kind of use?
cvs/svn/git is sync for code, and we have heard horror stories about having to clean up large syncs.
calender sync is a hit or miss experience, even when both sides are from the same company.
and the list goes on...
Member since:2006-03-10
I can assure you, with any recent Intel X-driver, it happens bl**dy constantly. I've tried every recent version but invariably end up going back to 1.7.4 so I can shut down without X falling over so badly I can't even SysReq out of it.
If this approach puts an end to this instability, I'm all for it. But I won't hold my breath...
Member since:2005-07-07
I can assure you, with any recent Intel X-driver, it happens bl**dy constantly. I've tried every recent version but invariably end up going back to 1.7.4 so I can shut down without X falling over so badly I can't even SysReq out of it.
If this approach puts an end to this instability, I'm all for it. But I won't hold my breath...
I am using the 2.2.1 driver without issues. I experienced a ton of instability with earlier versions but the current version works without a hitch.
Member since:
2005-07-24
It's always been somewhat embarrassing to me that switching from X to a character-based vt could sometimes lock up the console. Doesn't happen often. But on a busy machine it does occasionally happen. I take it that this enhancement corrects that situation.