Fatal server error no screens found

fatal server error no screens found

Before the system crashes and reboots, the specific error I receive is this, Fatal server error: No screens found. If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here. Fatal Server error: No screens found. Openbox-Message: Failed to open the display from the DISPLAY environment variable.

Thematic video

\

Fatal server error no screens found - and what

1- Error Message: Build Operating system: Slitaz GNU/Linux
Current Operating system: Linux Slitaz 2.6.30.6-Slitaz #1 SMP THU APR 8 21:19:10
CEST 2010 i686
Build Date: 02 March 2010 2:38:08AM

Before reporting problems; Check HTTP://wiki.x.org to make sure 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:Fri Aug 19 14;45;51 2011
[==] Using configed file; "/etc/X11/xorg.conf"
[EE] No device is detected

Fatal Server error:
No screens found
Openbox-Message: Failed to open the display from the DISPLAY environment variable.
[email protected]:~# DEBUS_SESSION_BUS_ADDRESS=Unix:abstract=/tmp/debus-Tn2iW06Bvd,guid=760017e207b52c44888090a24e4e771f
DEBUS_SESSION_BUS_PID=1342

[lxpanel:1293]: Gtk-WARNING **: cannot open display: localhost:0.0

2- System: Slitaz 3.0 Pentium 4 Processor 2.40 GHz, 740 MB ram, 6.4 GB Hard Drive

3- Video Card: Intel Integrated Graphics ( Not sure which one)

4- Has it happened before: I don't have a CD drive, I put the hard drive in another computer and installed it on their computer and put it back into mine. So I can't run live CD.

Posted 11 years ago #

grep `cat /tmp/.X0-lock`

If you see an output like:

root 2283 0.5 5.1 27796 6536 ? S Apr21 59:03 [X]

it indicates that there is indeed an Xserver running under this PID. To start a second server on the same system you have to give it a different dislay number. If you start your servers using startx you can do

startx -- :1

to start a server with display number 1. If you are sure there is no other server running on your system and above ps command indicates that no server with this PID is running, you should remove the file by doing (as 'root'):

rm -rf /tmp/.X0-lock

I keep getting the message: "Cannot establish any listening sockets..."

You get an error message like:

_XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running Fatal server error: Cannot establish any listening sockets - Make sure an X server isn't already running

This problem is very similar to the previous one. You will get this message possibly because the lock file was removed somehow or some other program which doesn't create a lock file is already listening on this port. You can check this by doing a . Xservers usually listen at tcp port 6000+

I keep getting the message "Unable to load required base modules, Exiting..."

You get an error message like:

(II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor="The X.Org Foundation" compiled for 6.7.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.6 Fatal server error: Unable to load required base modules, Exiting...

This means that the server has problems loading a module. The message immediately above tells you which module it was. The most likely cause is that the module doesn't exist. You may therefore try to reinstall your Xserver modules.

I keep getting the message: "no screens found"

This is a very general message telling you that something went wrong and there is no screen left which the server can successfully drive. Usually you'll see another error message describing what went wrong in more detail:

Message: "No devices detected"

You get an error message like:

(EE) No devices detected. Fatal server error: no screens found

It is very likely that your file doesn't contain the correct driver(s) for the chipset(s) in your system or that your chipset isn't supported by any of the drivers.
You can check for the detected devices in the log file (in most cases ) by looking for lines like:

In this example the active video device (the one with the ) is a Neomagic NM2200 video chip. In order to get this chipset to work you'd have to use the neomagic driver.
If you are using a distribution you should rerun its configuration tool. If there is no such tool, or if it keeps configuring your Xserver wrong you may want to try , the graphical tool shipped with Xorg. You can also let the server generate a config file: as root just run .
Please note: If you appear to use the correct driver and you still keep getting this message it is very likely that your chipset isn't supported (yet). In this case you may try the driver or - if this doesn't work - the driver. However both are entirely unaccellerated.

Message: "Screen(s) found, but none have a usable configuration.

You get an error message:

(EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found

In most cases this means there are no video modes available for your configuration. Each entry in the list of specified or default video modes gets checked if it lies withing the limit or the hardware: if it lies within the sync range specified or probed for the monitor, if it will work with the memory available on the video card or if the pixel clock lies within the range supported by the chipsets. There are many more limits. For each rejected mode you can see in the log file the reason for rejection:

... (II) VGA(0): Not using default mode "320x200" (vrefresh out of range) (II) VGA(0): Not using default mode "720x400" (insufficient memory for mode) (II) VGA(0): Not using default mode "360x200" (hsync out of range) ...

In most cases the monitor ranges are the reason why your modes where rejected. Please try to extend these ranges carefully until you get a working mode. Please note: on older monitors you need to be careful extending the ranges as it can be easily destroyed. There may be other reasons why you get this message.

  • If the specified depth is not supported with your hardware. In this case try depth 8, or if you
  • are using the driver even depth 4.
    • If you specified a combination of options the driver cannot handle.
    • If loading of a required sub module wasn't successful. In this case you'll get a message that the loading failed. Please try to investigate, why. The message may give you a clue: you may be using the wrong version of the module, or the file may not exist.

Message: "Unable to locate/open config file"

You are getting the message:

(EE) Unable to locate/open config file (EE) Error from xf86HandleConfigFile()

This means that the Xserver cannot find a configuration file because it has not been properly configured. Please check FAQMiscellaneous for information how to configure your Xserver.
Another reason for this error may be that you have created a configuration file but it is not in the correct location. The Xserver checks for configuration files at different locations. The usual locations are: or .
Another reason for this message may be that your Xserver cannot read the file because the server binary has the wrong permission. On UN*X like systems the server is usually owned by and runs with the SUID bit set so that it runs with root privileges even if started by an ordinary user. Therefore it should be able to open the configuration file regardless of who owns it or of its permissions. Please check "How do I check if my server bianry has the correct permissions?" on the FAQMiscellaneous page for futher information

Message: "Error from xf86HandleConfigFile()"

You are getting the message:

(EE) Unable to locate /open config file (EE) Error from xf86HandleConfigFile() Fatal server error no screens found

This indicates that you have a problem with your config file. It either doesn't exist, in which case you'll additionally see the message:

(EE) Unable to locate /etc/X11/xorg.conf config file

or your config file contains a typo. In this case you see the message:

(EE) Problem parsing the config file

You are even told where the error was:

Parse error on line 3 of section ServerLayout in file /etc/X11/xorg.conf "Idntifier" is not a valid keyword in this section.

You can then either correct the config file or regenerate the config file. How to do this is described here.