The X Server cannot start because no screens are found
SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Knoppix 3.9, SimplyMEPIS 3.3.2, Mandrake 10.1, SUSE 10.0, Windows 2000 Pro, Windows XP Home + Pro
Posts: 138
Rep:
The X Server cannot start because no screens are found
I installed the official .rpm driver for the Intel 82865G graphics card, and it seemed to work. However, when I booted up SUSE 10 today, it didn't start the X server (despite reaching runlevel 5). I logged on and tried the "startx" command and it said that "no screens found".
Distribution: Knoppix 3.9, SimplyMEPIS 3.3.2, Mandrake 10.1, SUSE 10.0, Windows 2000 Pro, Windows XP Home + Pro
Posts: 138
Original Poster
Rep:
Readme.txt of what? When I try to re-install the package it says that it is already installed, and when I try to un-install it, it says that it isn't installed!
i've had the same problem. every thing that i have found says to use XFree86 i've just built it and installed it last night so i havent had much time to work with it but from what i've read it should work
I, too have had problems with the X-server complaining of "no screens" after installing a vendor-supplied display device handler (Nvidia in my own case). Multiple calls of "startx" and logging out of one userid and into another (my default runlevel is 3, so I start with a text screen anyway) can be done with no problem - until I reset the system or shut down and switch off overnight.
In the morning, the nvidia module has disappeared from /proc/modules, so the X-server doesn't know where to find it.
Clearly something in the shutdown process has done something that it ought not to do, but what? Is it a case, as a previous correspondent has written, of dumping the default xorg display environment and going back to good old xFree86 (for which, I suspect, the nvidia handler was written in any case)?
Well, I'm once AGAIN trying to see if Linux has come far enough to be a usable product. Suse really has some nice features, but the Linux people will never quite get it. To have widespread acceptance of a product, a large number (majority) of people have to be able to use it. I love Linux and the open source community, but it really needs a lot of help before it beats out Windows on the average desktop. People use apps, not operating systems.
For Suse 10 to download and apply a new incompatible Nvidia driver and leave users in text mode is yet another example of why Linux will continue to be shabby.
11/20/2005
Problem:
- Suse 10 update downloaded new incompatible vga drivers(version 1.0-7676) for NVidia card
- Xserver and KDE (startx & KDEinit) would not start, error: "No Screens Found", etc
- Forced to work in text mode.
Solution:
- Using Yast2, installed 'kernel-source', 'gcc', 'make'
- Downloaded legacy drivers from Nvidia site (version 1.0-7174)
- Istalled from command prompt like this; sh <driverfile> -q
- Ran Sax2 from command prompt to configure video settings
- Ran startx command
- Voila, all was well
I have had this problem somedays ago, but I fixed it. So I just think it is a driver of VideoCard or the vga display mode problem. In my case, it's just a vga wrong display mode, so, replace it & then everything is OK!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.