For information the default Xorg.0.log ranges when a monitor cannot be detected...

(II) VESA(0): Monitor0: Using default hsync range of 31.50-37.90 kHz

(II) VESA(0): Monitor0: Using default vrefresh range of 50.00-70.00 Hz

(WW) VESA(0): Unable to estimate virtual size

(II) VESA(0): Not using built-in mode "1280x1024" (hsync out of range)

(II) VESA(0): Not using built-in mode "1152x864" (hsync out of range)

(II) VESA(0): Not using built-in mode "1024x768" (hsync out of range)

(II) VESA(0): Not using built-in mode "320x200" (hsync out of range)

(--) VESA(0): Virtual size is 800x600 (pitch 800)

(**) VESA(0): *Built-in mode "800x600"

(**) VESA(0): *Built-in mode "640x480"

(==) VESA(0): DPI set to (75, 75)

(II) VESA(0): Attempting to use 60Hz refresh for mode "800x600" (114)

(II) VESA(0): Attempting to use 60Hz refresh for mode "640x480" (111)

I think Clear should consider defaulting to a standard VGA resolution and a very common driver (VESA?). This will reduce the number of times that Clear does not display correctly after install.

First impressions are important and showing a garbled screen does not instill confidence.

thanks.

Agreed, I am installing for the first time(s) and have come up against this issue. With new LCD monitors being so common place why would ClearOS not be able to recognise them. Sounds like an update is needed to rectify this.

Thanks for those who have explained this well and I will try my best to follow these instructions to get a successful install. Reinstalling now so will see how I go.

Humm interesting Tim, I'll have to spend some more time playing with this. I created a config as you instructed and tried with several values under the monitor field. the graphics console did not start with these present. I then removed the two lines - leaving just the configuration pre modification. With this the graphics console loaded, and you could log in (same screen resolution as before)....when you log out it took you to the logout screen...and then when you clicked exit console, the session locked up - no mouse or keyboard.

I ended the process from my remote session. When I deleted the xorg.conf I tried again and full functionality was returned, the 'close console' worked.


very weird :-)

David

Guys is there a straight 4ward way to resolve the display issue. I have spent countless hrs to resolve this matter and I keep sinking down for ever. I have tried this on a Ubuntu system with Virtualbox, then traied this with a new system HP XW workstation and the same issue appears

Hi everyone, AFAIK ClearOS does default to the VESA driver but a default of 800x600

David, thanks for the feedback - i'm not sure why it would cause the issue you described unless your hardware was unable to do 1024x768x60? or the issue was not related to the resolution used

Koketso, the above how to is not for diagnosing other display problems, you can usualy find the source of the problem often by looking at the logs. Often it's a result of a missing xorg driver - you can find out more by using the following

grep -e WW -e EE /var/log/Xorg.0.log

Somthing strange happened that none of the topis covered this. I have an HP XW6200 64bit Intell Xenon system, that refused to display through out the time I have been trying to install ClearOS 5.1 offline. I now got back to the office and I am now online and all is working I installed then after the text mode it went to GUI auto and that did not happened while I was offiline any reasons for this Guys? or does that means for successful installation of ClearOS particullry if your Display card is Invidia then you should be online?

Thank you Tim about the log, do you mind reading what i have just posted?

The procedure outlined in the first post produces the following error:

VESA(0): No valid modes.

Can I suggest that ClearOS simply copy another distro?
Ubuntoo, Puppy, etc etc. All those Distros are capable of booting either from a CD, or on a fresh install PERFECTLY, and often with 3D!
They all are capable of running X with no user configuration required.

Can't ClearOS do the same?

Either that, or just ditch the GUI, and enable the Text Mode Console to do the job.
(Given that the Text Mode Console is name similarily to Graphic Mode Console, my first presumption is that they can both do the same job. This is highly misleading)


Cheers
Michael

I've tried a bunch of stuff. I simply can't get X to pick up 1024x768 :/

I added Modes "1024x768" to the Screen subsections, and I added the VESA ModeLine for 1024x768@60hz to the Monitor section.

No dice.

Xorg simply keeps opening up at 800x600@72 (however, it did use 800x600@60 after adding VertRefresh to the Monitor section)

Hi

in the console
iam not able to get GUI

i killed X, so i get command level Console

when i run startx --configure

i get follow output


xauth: creating new authority file /root/.serverauth.15425


X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: Linux 2.6.18-53.el5 i686 Red Hat, Inc.
Current Operating System: Linux system.bipsum.lan 2.6.18-194.8.1.v5 #1 SMP Thu J ul 15 01:14:04 EDT 2010 i686
Build Date: 20 April 2011
Build ID: xorg-x11-server 1.1.1-48.76.el5_6.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat May 28 11:24:04 2011
(EE) Unable to locate/open config file
New driver is "ati"
(==) Using default built-in configuration (55 lines)
(EE) Failed to load module "ati" (module does not exist, 0)
(EE) Failed to load module "fbdev" (module does not exist, 0)
(EE) Failed to load module "vga" (module does not exist, 0)
(WW) VESA(0): Failed to set up write-combining range (0xfd780000,0x70000)
(WW) VESA(0): Failed to set up write-combining range (0xfd700000,0xf0000)
(WW) VESA(0): Failed to set up write-combining range (0xfd600000,0x1f0000)
(WW) VESA(0): Failed to set up write-combining range (0xfd400000,0x3f0000)
(WW) VESA(0): Failed to set up write-combining range (0xfd000000,0x7f0000)
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Multiple symbols for level 1/group 1 on key <I5F>
> Using XF86Sleep, ignoring XF86Standby
> Warning: Symbol map for key <I5F> redefined
> Using last definition for conflicting fields
Errors from xkbcomp are not fatal to the X server
Could not init font path element unix/:7100, removing from list!
localuser:root being added to access control list

waiting for X server to shut down FreeFontPath: FPE "built-ins" refcount is 2, s hould be 1; fixing.


any suggestions to fix this issue

Ram

my hardware config

PCI Devices
- Ethernet controller: Intel Corporation 82547EI Gigabit Ethernet Controller
- Ethernet controller: Intel Corporation 82562EZ 10/100 Ethernet Controller
- Ethernet controller: VIA Technologies, Inc. VT6105/VT6106S [Rhine-III]
- Host bridge: Intel Corporation 82875P/E7210 Memory Controller Hub
- IDE interface: Intel Corporation 82801EB
- IDE interface: Intel Corporation 82801EB/ER
- ISA bridge: Intel Corporation 82801EB/ER
- PCI bridge: Intel Corporation 82801 PCI Bridge
- PCI bridge: Intel Corporation 82875P Processor to AGP Controller
- PCI bridge: Intel Corporation 82875P/E7210 Processor to PCI to CSA Bridge
- SMBus: Intel Corporation 82801EB/ER
- System peripheral: Intel Corporation 82875P/E7210 Processor to I/O Memory Interface
- (5x) USB Controller: Intel Corporation 82801EB/ER
- VGA compatible controller: ATI Technologies Inc Rage XL