Linked by Thom Holwerda on Sun 20th Apr 2008 12:52 UTC, submitted by Michael Larabel
X11, Window Managers 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.
Thread beginning with comment 310587
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

1- write "hibernate" in the terminal emulator
2- turn the computer on
3- wait
4- wait
5- find yourself in a useless brick of a session with a psychedelic screen
6- reboot
7- run fsck
8- Now you are free to reload your applications and data one by one.
9- ????
10- $$$$!!!
(This is more like it)

If the GFX driver can load usually there's absolutely no justifiable reason for it to hang the whole system on dehibernation. I don't care if the driver is Nvidia, ATI or open source as in my case. You set the screen to the right mode and restore the windows. At most I would understand some garbled graphics if I was running a 3d game when I hibernated the thing.

Reply Parent Score: 1

sakeniwefu Member since:

Okay, now the wise person who modded me down will please tell me which statement in my previous post is false? Is there any opinion for you to disagree with? Can you justify that the design of hibernate makes a working part of the OS hang the whole system up? If so, please enlighten me.
If you must have the immature attitude of modding people down because they happen to describe non-functional parts of your favorite OS, at least you could make a reason up to justify it rationally.

Reply Parent Score: 0

elsewhere Member since:

Just a guess, since I didn't mod you down (hence I wouldn't be able to reply), but as is often typical of whiners, you are applying your own system's inability to to perform xyz as applying to everyone else.

I close my lid, and my system suspends. I open it up, and it gives me a desktop in 3 seconds. Unstable KDE 4.1 combined with nvidia proprietary driver. Could I be asking for more trouble?

So while your own personal frustration is understandable, and certainly many others have issues with suspend and other functions in linux, don't assume it applies to everyone, and don't assume it is the fault of the kernel devs, or the xorg team. There are a lot of corner cases where different hardware combinations will cause problems, compounded by the fact that many of the drivers are reverse-engineered by necessity since the hardware manufacturers often don't provide support or documentation to the developers.

Do what I did, and research your hardware before purchasing it if you are looking for linux compatibility. If you are expecting arbitrary compatibility with whatever hardware you happen to be using, you could very well wind up disappointed.

And for what it's worth, my work laptop, an old Compaq NC6000, with Windows XP, crashes roughly 1 out of every 10 times when I close the lid to suspend. That's not Microsoft's fault, it can likely be tracked to a faulty driver much as it can in linux, but just points out how fragile the whole infrastructure is when we're dependent upon the interaction of independent hardware vendors interoperating together.

Reply Parent Score: 5

Lighten up
by s_groening on Mon 21st Apr 2008 07:37 in reply to "RE[4]: More polished desktop experience"
s_groening Member since:

Not everyone, everything or every opinion is necessarily shared by everyone no matter whether you're right, but please don't whine about a silly mod ... There are much more important things to be concerned about if you ask me ...

Reply Parent Score: 2