
Originally Posted by
libv
Amazingly, very few seems to have grasped the key issue here.
* I am a very long term linux user, X developer and graphics driver developer and it so happens that I edited a config file (Oh! No!), which is one of the key reasons why one is a linux/free software users: one should be able to do _slightly_ out of the box things. Normal people wouldn't even call this out of the box at all, but i read all the above posts, and decided to tune the message to the... public?.
* X gave up, because i had made one minute error.
* My panel started bleeding, because plymouth, KMS and the radeon drm didn't work together, and none of them bothered to catch the fact that the Xserver gave up.
So: "Xserver gives up nicely before even trying to touch any hardware" translates to "panel starts bleeding".
That's grounds for firing people in my book: nobody tested what happens when X refuses to start. No driver issue, no hw issue, nothing: not a single bit on the hardware was touched by X.
Then, when the thing turns white, and only then, the whole patronizing thing comes back with a vengeance, and gives little to no option to to recover from this. Nothing present to try to catch a failed boot, no ssh, no grub menu.
Now what is it that most posters here fail to see?
And to the masses of anonymous posters who think that i got treated right, that it was fully correct for me to receive a bleeding panel and be given no way out. I hope that someone finds a novel way to quickly discharge your laptops LiIon batteries, to the extend that they explode. Then, when you click outside the area where the Designers believe you should click, your batteries will explodes in your laps, and the designer gets his/her way. Soon, they will have only users who click inside the pre-destined/designed area. How would that suit you?