BulletProofX

Differences between revisions 9 and 10
Revision 9 as of 2006-12-29 03:30:48
Size: 3954
Editor: ip-66-254-43-35
Comment:
Revision 10 as of 2006-12-29 04:04:38
Size: 4288
Editor: ip-66-254-43-35
Comment: add back xforcevesa kernel parameter information
Deletions are marked like this. Additions are marked like this.
Line 45: Line 45:
"Start Ubuntu in safe graphics mode" option of the LiveCD, make '''xforcevesa''' added to the kernel boot parameters, which is fine for manually choosing safe mode, but not for automatically detecting bad X configuration. Moreover,[https://launchpad.net/distros/ubuntu/+source/xorg/+bug/59618 bug #59618] make it not work for now.

Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

Summary

The goal of the bullet proof X specification is to ensure that there is always a way to load the X server, by falling back, automatically or manually, on a working video mode if the default one failed.

Rationale

A lot of people are capable of configuring their systems (or getting help to do so) via a graphical interface but don't have a clue when it comes to the command line interface.

Use cases

Scope

Design

VESA mode 800x600x256 is hereafter called safeMode1. 'Safe Mode' is written on safeMode1 screen.

safeMode1 is triggered in any of the following circumstances:

  • gdm detects that the X server is failing to start (XKeepsCrashing)
  • grub have been booted with option safe mode boot (rather than normal boot)

Design discussion

The configuration fall back process should be:

  • safeMode1, which is sane given the current state of hardware out there, and Windows XP and above also use 800x600 in their safe mode.
    • run dpkg-recnofigure by passing an environment variable
    • xserver-xorg.config should check for an environment variable which behaves the same as xforcevesa
  • If that fails, provide an error on the console.
    • We discussed falling back to vga (safeMode2) instead of just provide an error to the console, but that would introduce another mode switch and delay before the error is shown, and vesa is very well established nowadays.

UI should offer the following options:

  • attempt automatic reconfiguration of video settings
    • can we do this first, and only prompt the user to accept/reject if the auto-config is different from their existing configuration? If yes, they should be prompted to restart in test mode, if no, continue in safe mode.
  • dpkg-reconfigure
  • if that produces a different configuration, allow the sure to test by logging them out and allowing the display manager to restart X
  • give up and use this mode: 'Use these video settings for your normal use'?
  • display diagnostics of what failed - for giving to technical support/showing their local 'computer expert.'

I suggest to do like Windows, that is when xserver is reconfigure or configured for the first time, ask the user if he/she should continue to use that video mode, or fallback on safeMode1. (The "Can you read this?" question on Windows) --Paul Dufresne

"Start Ubuntu in safe graphics mode" option of the LiveCD, make xforcevesa added to the kernel boot parameters, which is fine for manually choosing safe mode, but not for automatically detecting bad X configuration. Moreover,[https://launchpad.net/distros/ubuntu/+source/xorg/+bug/59618 bug #59618] make it not work for now.

Implementation

[This section should show how the implementation is different than the design section]

Code

Data preservation and migration

Unresolved issues

BoF agenda and discussion

From Forum topic [http://ubuntuforums.org/showthread.php?t=318142]

...sometimes logging out results in a black screen and a system freeze. None of the exit shortcut keys work, and I can't restart X.

I found a very reliable fix to this issue was changing the following line (line 96) in the /etc/gdm/gdm.conf file to this:

This forces GDM to restart X completely before returning to the login screen...

I propose to make this into the default configuration in Feisty Fawn.

In my opinion, a bug should be opened if not already done with previous mentioned problem [http://ubuntuforums.org/showthread.php?t=318142], and then removed as being outside the scope of this specification. --Paul Dufresne

Future work:

  • Fall back for thin clients (outside this spec? --Paul Dufresne)
  • Kubuntu (seems that spec take effect before GNOME or KDE is loaded, so it will surely apply to Kubuntu --Paul Dufresne)


CategorySpec

BulletProofX (last edited 2008-08-06 16:35:43 by localhost)