[SOLVED] cannot start xserver: addscreen/screeninit failed for driver 0
Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
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.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
cannot start xserver: addscreen/screeninit failed for driver 0
I already had OpenSUSE 10.3 installed and running perfectly on my computer when I decided to install OpenSUSE 11.1 on it. The installation was completed successfully. (I chose new installation, not upgrade.) When I booted into newly installed OpenSUSE 11.1, I saw the splash screen with progressbar and then was greeted by a cli login prompt on virtual terminal 1 instead of kde. One of the messages I could see here said that runlevel 5 has been reached, so I was confused as to why X hadn't started. None the less, I logged in and typed starx but X failed to start. The output of startx is as follows.
X.Org X Server 1.5.2
Release Date: 10 October 2008
X Protocol Version 11, Revision 0
Build Operating System: openSUSE SUSE LINUX
Current Operating System: Linux linux-esco 220.127.116.11-9-pae #1 SMP 2008-12-04 18:10:04 +0100 i686
Build Date: 03 December 2008 09:21:06AM
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: Mon Dec 22 19:13:47 2008
(==) Using config file: "/etc/X11/xorg.conf"
(EE) VIA(0): Internal error: could not map framebuffer
(EE) VIA(0): Internal error: could not map framebuffer
Fatal server error:
AddScreen/ScreenInit failed for driver 0
xinit: Connection refused (errno 111): unable to connect to X server
xinit: No such process (errno 3): Server error.
I've searched around in the forums and found that output of lspci is often asked for while solving these kinds of problems, so here it is.
00:00.0 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.1 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.3 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.4 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.7 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South]
00:0c.0 Communication controller: Conexant Systems, Inc. HSF 56k Data/Fax Modem (rev 01)
00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 80)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: VIA Technologies, Inc. K8M800/K8N800/K8N800A [S3 UniChrome Pro] (rev 01)
I also found this error in /var/log/Xorg.0.log
(EE) VIA(0): Internal error: could not map framebuffer.
http://unichrome.sourceforge.net/ (I found this address in /var/log/Xorg.0.log) says that my chipset i.e. VIA K8M800 is supported, but I can't get X to start. And since OpenSUSE 10.3 had worked fine on the same machine, I'm not sure where the problem lies. I'll be glad for any suggestions.
I know not if OpenSUSE automatically configures X, but you could back up your X configuration and reconfigure it with one of xorgsetup, xorgcfg, or 'X -configure' (the latter will generate xorg.conf in your home folder.) Each one alone and in combination often partly/fully fix errors, or can also make things worse, so you should read your X configuration afterwards. Xorgcfg is another program--but graphical. X usually eventually messes up, occasionally even at installation. The majority (51%) of the time, critical X errors seem easier to fix by reinstalling X or even the OS. Maybe there is someone working on OpenSUSE to report this to who could fix it....
I have a similar problem. Just upgraded from openSUSE 11.0 to 11.1 and now getting a cli login almost every time, but on the few (progressively less frequent) occasions I do get the kdm login, there's no obvious thing I've done that I could reproduce to make it happen again.
I've exhausted 1001 procedures I can't recount here, and analysed hundreds of system files to try and find a cause, but not being an expert I don't really know what to look out for. I've had versions of SUSE from 9.2 onwards running on this laptop and this is the first time such issues have arisen.
I'm seeing many vaguely similar posts on various forums including the SUSE forums, but none reach any useful conclusions, and my own post isn't getting anywhere. It leads me to suspect, however, that there may be some general underlying problems with Xorg or the distro's implementation of it in this release.
In my own case, I have an ATI card using the free radeon driver, and although I can 'startx' at the cli login, attempts to 'startkde' (for the default KDE4) or 'startkde3' tell me that the '$DISPLAY is not set correctly'. The startkde3 command spills out a load of more detailed errors but I cannot locate the log file on my system that contains them in order to post here.
I'm convinced there must be a simple fix behind this, and only want to attempt installing the proprietary ATI drivers, or to reinstall the root partition, as a last resort.