| View previous topic :: View next topic |
| Author |
Message |
Landaro
n00b
Joined: 20 Oct 2010
Posts: 6
Location: Germany
|
 Posted: Wed Oct 20, 2010 10:55 pm Post subject: startx fails with fatal server error: no screen found |
 |
|
Hi,
I am fairly new to gentoo and I am trying to get a GUI working (in particular: gnome) It is my understanding that I have to get Xorg running before anything else, so that's what I am trying to achieve at the moment. I have some generic Linux experiance but not much.
So here is what I did so far: I followed the "X Server Configuration HOWTO" up to the point where I am asked to try startx without any further configurations. Doing this leads to the error below:
(looks like the drivers are not there, although I thought I had included them in the kernel I am running ...)
My machine is a Dell XPS M1330 notebook with a nvidia GeForce 8400 GS gfx card.
| Code: |
$ cat /var/log/Xorg.0.log
X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.34-gentoo-r12 x86_64
Current Operating System: Linux deepthought 2.6.34-gentoo-r12 #2 SMP Wed Oct 20 23:51:34 GMT 2010 x86_64
Kernel command line: root=/dev/sda5
Build Date: 20 October 2010 11:57:42PM
Current version of pixman: 0.18.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
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: Thu Oct 21 00:10:12 2010
(II) Loader magic: 0x7a70e0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 6.0
X.Org XInput driver : 7.0
X.Org Server Extension : 2.0
(--) using VT number 7
(--) PCI:*(0:1:0:0) 10de:0427:1028:0209 nVidia Corporation G86 [GeForce 8400M GS] rev 161, Mem @ 0xf5000000/16777216, 0xe0000000/268435456, 0xf2000000/33554432, I/O @ 0x0000ef00/128, BIOS @ 0x????????/131072
(==) Using default built-in configuration (39 lines)
(==) --- Start of built-in configuration ---
Section "Device"
Identifier "Builtin Default nouveau Device 0"
Driver "nouveau"
EndSection
Section "Screen"
Identifier "Builtin Default nouveau Screen 0"
Device "Builtin Default nouveau Device 0"
EndSection
Section "Device"
Identifier "Builtin Default nv Device 0"
Driver "nv"
EndSection
Section "Screen"
Identifier "Builtin Default nv Screen 0"
Device "Builtin Default nv Device 0"
EndSection
Section "Device"
Identifier "Builtin Default vesa Device 0"
Driver "vesa"
EndSection
Section "Screen"
Identifier "Builtin Default vesa Screen 0"
Device "Builtin Default vesa Device 0"
EndSection
Section "Device"
Identifier "Builtin Default fbdev Device 0"
Driver "fbdev"
EndSection
Section "Screen"
Identifier "Builtin Default fbdev Screen 0"
Device "Builtin Default fbdev Device 0"
EndSection
Section "ServerLayout"
Identifier "Builtin Default Layout"
Screen "Builtin Default nouveau Screen 0"
Screen "Builtin Default nv Screen 0"
Screen "Builtin Default vesa Screen 0"
Screen "Builtin Default fbdev Screen 0"
EndSection
(==) --- End of built-in configuration ---
(==) ServerLayout "Builtin Default Layout"
(**) |-->Screen "Builtin Default nouveau Screen 0" (0)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default nouveau Device 0"
(==) No monitor specified for screen "Builtin Default nouveau Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default nv Screen 0" (1)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default nv Device 0"
(==) No monitor specified for screen "Builtin Default nv Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default vesa Screen 0" (2)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default vesa Device 0"
(==) No monitor specified for screen "Builtin Default vesa Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default fbdev Screen 0" (3)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default fbdev Device 0"
(==) No monitor specified for screen "Builtin Default fbdev Screen 0".
Using a default monitor configuration.
(==) Not automatically adding devices
(==) Not automatically enabling devices
(WW) The directory "/usr/share/fonts/misc/" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/TTF/" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/OTF" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/Type1/" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/100dpi/" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/75dpi/" does not exist.
Entry deleted from font path.
(==) FontPath set to:
(==) ModulePath set to "/usr/lib64/xorg/modules"
(==) |-->Input Device "<default pointer>"
(==) |-->Input Device "<default keyboard>"
(==) The core pointer device wasn't specified explicitly in the layout.
Using the default mouse configuration.
(==) The core keyboard device wasn't specified explicitly in the layout.
Using the default keyboard configuration.
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) LoadModule: "extmod"
(II) Loading /usr/lib64/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.7.7, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib64/xorg/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.7.7, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.7.7, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "record"
(II) Loading /usr/lib64/xorg/modules/extensions/librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.7.7, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib64/xorg/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.7.7, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/lib64/xorg/modules/extensions/libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
compiled for 1.7.7, module version = 1.1.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "nouveau"
(WW) Warning, couldn't open module nouveau
(II) UnloadModule: "nouveau"
(EE) Failed to load module "nouveau" (module does not exist, 0)
(II) LoadModule: "nv"
(WW) Warning, couldn't open module nv
(II) UnloadModule: "nv"
(EE) Failed to load module "nv" (module does not exist, 0)
(II) LoadModule: "vesa"
(WW) Warning, couldn't open module vesa
(II) UnloadModule: "vesa"
(EE) Failed to load module "vesa" (module does not exist, 0)
(II) LoadModule: "fbdev"
(WW) Warning, couldn't open module fbdev
(II) UnloadModule: "fbdev"
(EE) Failed to load module "fbdev" (module does not exist, 0)
(II) LoadModule: "mouse"
(WW) Warning, couldn't open module mouse
(II) UnloadModule: "mouse"
(EE) Failed to load module "mouse" (module does not exist, 0)
(II) LoadModule: "kbd"
(WW) Warning, couldn't open module kbd
(II) UnloadModule: "kbd"
(EE) Failed to load module "kbd" (module does not exist, 0)
(EE) No drivers available.
Fatal server error:
no screens found
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
|
Let me know if you need further statistical output.
BTW: Is there a better way to post diagnostic data when on a Gentoo box without Xorg and GUI than the following:
save output in file, copy file to remote ftp server, reboot system into windows, grab file from remote ftp server, access forum and post file contents (after converting linux to windows line endings)
I'd prefer a solution that avoids swapping OSes all the time 
thanks in advance
Last edited by Landaro on Wed Oct 20, 2010 11:16 pm; edited 1 time in total |
|
| Back to top |
|
 |
Chiitoo
Administrator
Joined: 28 Feb 2010
Posts: 2587
Location: Here and Away Again
|
| Posted: Wed Oct 20, 2010 11:09 pm Post subject: |
|
|
While you're stuck with the text interface, you might want to have a quick peek at this guide:
Using a Mouse within the Console
http://www.gentoo.org/doc/en/gpm.xml
Can make things a lot better. ^^
But yeah, you need to decide whether you are going to use the nvidia-drivers or the nv/nouveau ones. As the guide mentions there are things to disable and/or enable in the kernel depending which ones you use.
If there are no screens found, I think it is very likely the (correct) module is not loaded.
Just some thoughts while waiting for the log(s) in anticipation. 
_________________
Kindest of regardses. |
|
| Back to top |
|
|
Landaro
n00b
Joined: 20 Oct 2010
Posts: 6
Location: Germany
|
| Posted: Wed Oct 20, 2010 11:20 pm Post subject: |
|
|
Logs are up, see above
I did exactly as told by the guide but I have the worrying feeling, that the guide might not be up to date (since it instructs to use HAL which apparently is deprecated for quite some time already). In particular where I am asked to disable all options under a particular section, VGA, nvidea et al. don't appear anymore while the guide mentions to disable especially those entries.
Ohh btw ... I am running a 64 bit system (thought I should add this ... )
EDIT: regarding your question: I believe the nouveau driver is the correct one to use and followed the relevant instructions ...
EDIT2: thx for the gpm link, works really nicely |
|
| Back to top |
|
|
Chiitoo
Administrator
Joined: 28 Feb 2010
Posts: 2587
Location: Here and Away Again
|
| Posted: Thu Oct 21, 2010 12:51 am Post subject: |
|
|
I think the current stable version still depends on hal, I may be wrong though... but I do know that I have hal in use still, and I have 1.7.7-r1 of xorg-server.
Yeah, some things might have been moved in the menu edit at times like for the
| Code: |
Device Drivers --->
Graphics support --->
Support for frame buffer devices --->
(Disable all drivers, including VGA, Intel, nVidia, and ATI)
(Further down, enable basic console support. KMS uses this.)
Console display driver support --->
<*> Framebuffer Console Support
|
it does seem to say that the drivers are actually inside Support for frame buffer devices ---> while they seem to be just below that and above the next step Console display driver support --->
While it is slightly confusing, I think Support for frame buffer devices ---> is mentioned not because you go up into that list, but because all the drivers below the option itself are related to this option. In other words, if you disable Support for frame buffer devices ---> you will see most of the stuff below it will be gone, including the <*> Framebuffer Console Support from inside Console display driver support --->...
I think you could use either one of them really. I usually first try nouveau but it didn't work with my current set-up so I went to nvidia-drivers pretty soon, didn't bother using much time into getting nouvea to work at the time, gotta take a look into it some other time though!
You have probably seen the guide for nvidia-drivers but I will link it here anyhoo.
http://www.gentoo.org/doc/en/nvidia-guide.xml
Now for the log.
| Code: |
(II) LoadModule: "nouveau"
(WW) Warning, couldn't open module nouveau
(II) UnloadModule: "nouveau"
(EE) Failed to load module "nouveau" (module does not exist, 0)
(II) LoadModule: "nv"
(WW) Warning, couldn't open module nv
(II) UnloadModule: "nv"
(EE) Failed to load module "nv" (module does not exist, 0)
(II) LoadModule: "vesa"
(WW) Warning, couldn't open module vesa
(II) UnloadModule: "vesa"
(EE) Failed to load module "vesa" (module does not exist, 0)
(II) LoadModule: "fbdev"
(WW) Warning, couldn't open module fbdev
(II) UnloadModule: "fbdev"
(EE) Failed to load module "fbdev" (module does not exist, 0)
|
If I'm right, here we see all the things listed it tried to use for producing graphics.
As I guessed, it can't find the module(s), did you emerge/install the drivers successfully?
Edit:
What does
| Code: |
modprobe nv
modprobe nouveau
|
I don't know which one it should be, really since I use nvidia.
I think nv is an old one and nouveau is with the newer drivers.
_________________
Kindest of regardses. |
|
| Back to top |
|
|
Landaro
n00b
Joined: 20 Oct 2010
Posts: 6
Location: Germany
|
| Posted: Thu Oct 21, 2010 9:26 am Post subject: |
|
|
| Code: |
modprobe -nv nouveau
FATAL: Module nouveau not found
|
Identical for nvidia and nv
I already tried emerge --pretend {nouveau, nvidea, nv} but neither results in any package found
I believe my kernel is now configured correctly but I am not sure ... |
|
| Back to top |
|
|
Chiitoo
Administrator
Joined: 28 Feb 2010
Posts: 2587
Location: Here and Away Again
|
| Posted: Thu Oct 21, 2010 10:29 am Post subject: |
|
|
For the nvidia-drivers you'd do
| Code: |
emerge nvidia-drivers
|
and for nouveau you'd want
| Code: |
emerge xf86-video-nouveau
|
but remember, you would need to do modifications to your kernel if you wanted to try the nvidia-driver now, if you followed the guide to go with nouveau. :]
The option -s and -S are useful if you're not certain of a package name. For example
would search the package names as well as the descriptions for the string you enter.
There is also a web-site version of the Portage with a search function:
http://gentoo-portage.com/
Good luck,
I hope this helps!
_________________
Kindest of regardses. |
|
| Back to top |
|
|
Landaro
n00b
Joined: 20 Oct 2010
Posts: 6
Location: Germany
|
| Posted: Thu Oct 21, 2010 8:25 pm Post subject: |
|
|
Hi again,
I played around a bit further and I am still stuck ...
so lets see what my system currently says (abridged transcriptions by hand since copy and paste doesn't work, even with gpm):
In my /etc/make.conf
| Code: |
USE="gnome X gtk laptop mmx sse sse2"
VIDEO_CARDS="nvidia"
INPUT_DEVICES="evdev synaptics"
|
lsmod turns up the following
| Code: |
ntfs
firewire_ohci
firewire_core
crc_itu_t
|
I have merged both the nouveau and nvidia-drivers after freshly compiling my kernel (at least I called emerge with the respective package names and the command completed without error)
I have merged xorg-server with these settings.
I have called env-update and source /etc/profile as instructed
now I am trying to load the modules ...
| Code: |
$ modprobe nvidia
FATAL: Error inserting nvidia (/lib/modules/2.6.34-gentoo-r12/video/nvidia.ko): No such device
$ modprobe nouveau
FATAL: Module nouveau not found
$ modprobe -vn nv
FATAL: module nv not found
|
Apart from following cookbook recipies I am trying to understand what is going on. From the three errors above I'd say that the nouveau and nv drivers are not properly installed and that for the nvidia driver kernel support is not enabled ... correct me if I am wrong and please tell me what to I can do to fix this issue.
I guess there is no point continuing the setup of xorg and gnome until I am able to load the video driver ...
Also, is there a comprehensive explanation of what each kernel config option does because I have absolutely no clue what the purpose of ca 95% of those is ... In particular whether enabling is necessary, optional or actually damaging (like the legacy framebuffer stuff ...)
As usual, any assistance is greatly appreciated |
|
| Back to top |
|
|
Chiitoo
Administrator
Joined: 28 Feb 2010
Posts: 2587
Location: Here and Away Again
|
| Posted: Thu Oct 21, 2010 11:12 pm Post subject: |
|
|
While at it, we could check your CFLAGS, CXXFLAGS, MAKEOPTS and CHOST as well just to be sure (and any other options in your make.conf).
OK, please note that I'm not very experienced myself, and the things I will write about is how I have come to do things from learning by myself, asking/searching around here and reading them manuals so I am not an expert but rather a newbie to Linux itself. Just a fore-warning.
Anyways, I would recommend some more USE flags, you will need to add them sooner or later.
If you are using xorg-server-1.7~ as I am guessing you are, add 'hal', then re-emerge xorg-server. This will automatically pull 'hal' which is used for detecting input devices and such.
There are a lot of other USE flags I would recommend such as 'alsa'. I will show you mine but it has a lot of things you (or anyone else for the matter) probably would not need but either way, just to give you an idea.
| Code: |
USE="3dnow 3dnowext X accessibility acl acpi alsa anthy berkdb bzip2 cairo
cdda cdr cdrom cjk cli consolekit cracklib crypt cups cxx dbus
device-mapper dri dvd exceptions extras fortran gd gdbm gdu glib gmplayer
gnutls gpm gtk hal iconv immqt-bc ipv6 kde lm_sensors mmx mmxext mng
modules mp3 mudflap multilib mysql ncurses nls nptl nptlonly opengl openmp
pae pam pcntl pcre perl png policykit pppd python qt3support qt4 readline
reflection scim session sqlite sse sse2 sse4a ssl ssse3 sysfs tcpd
truetype unicode xml xorg zlib -immqt"
|
At this point, I would suggest you to
You will see quite quickly what it is for and I think will be very useful in the future.
Another thing, for the nouveau you would have
| Code: |
VIDEO_CARDS="nouveau"
|
instead of
| Code: |
VIDEO_CARDS="nvidia"
|
I personally have
| Code: |
VIDEO_CARDS="nvidia nv vesa"
|
just to have the support for nv for when/if I wanted to try it out (though I should have probably used nouveau instead of nv haha).
Anyways, since you have only "nvidia" there, this would mean you'd be using the nvidia-drivers instead of nouveau which you configured the kernel for as far as I understood it. The kernel options probably are the reason for the "nvidia module" for not loading properly (just my guess though).
But like you are thinking yourself, I agree with that.
I think what you should do now is decide one of the drivers you want to use.
I think I'd personally suggest to go with "nvidia-drivers" though "nouveau" is generally suggested to be tried first, it seems, or maybe it was just the default instead of suggested...
If you want to go with "nvidia-drivers", follow the nvidia-guide I linked up there. If you need help with any specific part of it, just ask.
If you want to go with "nouveau" we can look into that as well more specific but then, I think you should unmerge "nvidia-drivers" and remerge "nouveau".
Yeah, leave gnome be until we have the xorg-server running. :]
Now some for the kernel configuration.
Try not to be overwhelmed with it all, I was too and still there are so much I don't know about.
At this point I'd ask, are you using Genkernel or manual configuration?
Genkernel is pretty easy, I had a lot of problems at first with doing a manual run but now I think I got it pretty well figured, what comes to getting required things enabled.
I do it like this now, have at least 2 terminals open, "make menuconfig" on the other and "lspci -k" in the other (or just write the drivers from next part on-to a piece of paper).
From "lspci -k" you can see the "kernel driver" names that any hardware is using.
Then I just copy those names and search for them in "menuconfig".
Press the "/" key to search.
Sometimes you may need to modify the name a bit to find it in the kernel, for example, ATIIXP_IDE doesn't find anything but with just ATIIXP I can find the right one (even though it pulls up several things).
That method should get you pretty much the things needed for a working system enabled (this not about xorg or gnome and that stuff yet though).
I still have a lot of things there that I don't need. I've only disabled things I really am sure I don't need (or I disable stuff little at a time and try if everything still works ha).
What comes to the graphics part of the "kernel drivers", "framebuffers" and all, the guides should have it all though it can be a bit confusing and it's only really important because the certain drivers in the kernel would conflict with those of the proprietary "nvidia-drivers" and of course, if you want to use a "framebuffer" or not.
Anyways, there's some thoughts I had in mind for now, I'll post this while it's all still written there, will probably post more later and ask more, it's important to ask!
I hope this helps!
_________________
Kindest of regardses. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
