Saturday, September 20, 2008

No Progress Bar at System Startup due to monitor settings


I had a very annoying problem with the startup progress bar that wasn't showing at system boot (Ubuntu).
With the live cd no such problem, so it had to be a configuration error. Installed the startup manager with
sudo apt get install startupmanager
Then I made sure the login screen had a 8 bits 640x480 resolution. Other resolution didn't deliver on my IIyama E1900S.
Edited the xorg.conf file with
Section "Monitor"
Identifier "Configured Monitor"
HorizSync 30-80
VertRefresh 56-75
EndSection
First backup of the file and use a user switch to determine if your new settings work.
These settings are specific for my Iiyama: HorizSync 30-80; VertRefresh 56-75.
Try to determine the configuration of your monitor through documentation or internet.

How to proceed?
Example:
1. Make a backup copy of the current xorg.conf (ALWAYS DO THIS!):
Code:
sudo cp /etc/X11/xorg.conf /etc/X11/xorg.conf.known-to-work
2. Alter xorg.conf in any appropriate way*. (Maybe run "dpkg-reconfigure xserver-xorg" to fix that missing resolution?)
3. Choose System -> Quit -> Switch User

A new X session will start on a second display, and you can now switch between them using the combination Ctrl + Alt + F7 to F12. (Normally, the default X session will be available on Ctrl + Alt + F7, and the second you start will be on Ctrl + Alt + F9)

If you are thrown back into your original session when attempting this - your new xorg.conf probably has an error in it! Check /var/log/Xorg.*.log (usually Xorg.20.log for this second display), and don't forget to restore your backup configuration before rebooting!

Backup Xorg.conf file:
sudo cp /etc/X11/xorg.conf /etc/X11/xorg.conf_backup

Go to folder and file with root privileges for example in Ubuntu:
sudo gedit /etc/X11/xorg.conf


source:
HOWTO: YES! There IS an easy way of trying out Xorg.conf without reloading X
http://ubuntuforums.org/showthread.php?p=4211618


Other resolution/monitor problems:
https://help.ubuntu.com/community/FixVideoResolutionHowto

No comments:

Blog Archive