| Summary: | fedora 18 X fatal server error no screens found after boot | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Philippe Dax <dax> | ||||||||||
| Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> | ||||||||||
| Status: | RESOLVED NOTOURBUG | QA Contact: | Xorg Project Team <xorg-team> | ||||||||||
| Severity: | normal | ||||||||||||
| Priority: | medium | CC: | dax, radim.venglor | ||||||||||
| Version: | 7.7 (2012.06) | ||||||||||||
| Hardware: | x86-64 (AMD64) | ||||||||||||
| OS: | Linux (All) | ||||||||||||
| Whiteboard: | |||||||||||||
| i915 platform: | i915 features: | ||||||||||||
| Attachments: |
|
||||||||||||
Created attachment 73155 [details]
/var/log/gdm/:0.log
Created attachment 73157 [details]
/var/log/gdm/:0-slave.log
> Xorg.0.log > Fatal server error: > [ 212.065] xf86OpenConsole: VT_ACTIVATE failed: No such device or address I think this is the error message and it should refer to a failed open of a virtual terminal (may be /dev/fb0 or /dev/tty*). Can you manually switch to other virtual terminals? Can you manually start X? Is this issue related? http://forums.fedoraforum.org/showthread.php?p=1625857 Ciao! Created attachment 73191 [details]
dmesg
(In reply to comment #3) > Can you manually switch to other virtual terminals? I don't know how to do that > Can you manually start X? Yes, startx > Is this issue related? > http://forums.fedoraforum.org/showthread.php?p=1625857 No My GPU is 02:00.0 VGA compatible controller: NVIDIA Corporation G84 [Quadro FX 1700] (rev a1) (In reply to comment #3) > > Xorg.0.log > > Fatal server error: > > [ 212.065] xf86OpenConsole: VT_ACTIVATE failed: No such device or address > > I think this is the error message and it should refer to a failed open of a > virtual terminal (may be /dev/fb0 or /dev/tty*). > > Can you manually switch to other virtual terminals? > Can you manually start X? > > Is this issue related? > > http://forums.fedoraforum.org/showthread.php?p=1625857 > > > Ciao! This message occures after installing yum install xorg-x11-drv-nouveau The original message was : [ 801.991] Initializing built-in extension DRI2 [ 801.991] (II) LoadModule: "glx" [ 801.991] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so [ 801.991] (II) Module glx: vendor="X.Org Foundation" [ 801.991] compiled for 1.13.1, module version = 1.0.0 [ 801.991] ABI class: X.Org Server Extension, version 7.0 [ 801.991] (==) AIGLX enabled [ 801.991] Loading extension GLX [ 801.991] (==) Matched nouveau as autoconfigured driver 0 [ 801.991] (==) Matched nv as autoconfigured driver 1 [ 801.991] (==) Matched nouveau as autoconfigured driver 2 [ 801.991] (==) Matched nv as autoconfigured driver 3 [ 801.992] (==) Matched vesa as autoconfigured driver 4 [ 801.992] (==) Matched modesetting as autoconfigured driver 5 [ 801.992] (==) Matched fbdev as autoconfigured driver 6 [ 801.992] (==) Assigned the driver to the xf86ConfigLayout [ 801.992] (II) LoadModule: "nouveau" [ 801.992] (WW) Warning, couldn't open module nouveau [ 801.992] (II) UnloadModule: "nouveau" [ 801.992] (II) Unloading nouveau [ 801.992] (EE) Failed to load module "nouveau" (module does not exist, 0) [ 801.992] (II) LoadModule: "nv" [ 801.992] (WW) Warning, couldn't open module nv [ 801.992] (II) UnloadModule: "nv" [ 801.992] (II) Unloading nv [ 801.992] (EE) Failed to load module "nv" (module does not exist, 0) [ 801.992] (II) LoadModule: "vesa" [ 801.992] (WW) Warning, couldn't open module vesa [ 801.992] (II) UnloadModule: "vesa" [ 801.992] (II) Unloading vesa [ 801.992] (EE) Failed to load module "vesa" (module does not exist, 0) [ 801.992] (II) LoadModule: "modesetting" [ 801.992] (WW) Warning, couldn't open module modesetting [ 801.992] (II) UnloadModule: "modesetting" [ 801.992] (II) Unloading modesetting [ 801.992] (EE) Failed to load module "modesetting" (module does not exist, 0) [ 801.992] (II) LoadModule: "fbdev" [ 801.992] (WW) Warning, couldn't open module fbdev [ 801.992] (II) UnloadModule: "fbdev" [ 801.992] (II) Unloading fbdev [ 801.992] (EE) Failed to load module "fbdev" (module does not exist, 0) [ 801.992] (EE) No drivers available. [ 801.992] Fatal server error: [ 801.992] no screens found [ 801.993] (EE) I suspect a missing driver : $ yum list |grep xorg-x11-drv xorg-x11-drv-apm.x86_64 1.2.5-2.fc18 fedora xorg-x11-drv-ast.x86_64 0.97.0-2.fc18 fedora xorg-x11-drv-ati.x86_64 7.0.0-0.8.20121015gitbd9e2c064.fc18 xorg-x11-drv-catalyst.x86_64 12.11-0.3.beta11.fc18 rpmfusion-nonfree xorg-x11-drv-catalyst-devel.i686 12.11-0.3.beta11.fc18 rpmfusion-nonfree xorg-x11-drv-catalyst-devel.x86_64 12.11-0.3.beta11.fc18 rpmfusion-nonfree xorg-x11-drv-catalyst-libs.i686 12.11-0.3.beta11.fc18 rpmfusion-nonfree xorg-x11-drv-catalyst-libs.x86_64 12.11-0.3.beta11.fc18 rpmfusion-nonfree xorg-x11-drv-cirrus.x86_64 1.5.1-3.fc18 fedora xorg-x11-drv-dummy.x86_64 0.3.6-2.fc18 fedora xorg-x11-drv-evdev.x86_64 2.7.3-2.fc18 fedora xorg-x11-drv-evdev-devel.i686 2.7.3-2.fc18 fedora xorg-x11-drv-evdev-devel.x86_64 2.7.3-2.fc18 fedora xorg-x11-drv-fbdev.x86_64 0.4.3-3.fc18 fedora xorg-x11-drv-glint.x86_64 1.2.8-2.fc18 fedora xorg-x11-drv-i128.x86_64 1.3.6-2.fc18 fedora xorg-x11-drv-i740.x86_64 1.3.4-2.fc18 fedora xorg-x11-drv-intel.i686 2.20.17-1.fc18 updates xorg-x11-drv-intel.x86_64 2.20.17-1.fc18 updates xorg-x11-drv-intel-devel.i686 2.20.17-1.fc18 updates xorg-x11-drv-intel-devel.x86_64 2.20.17-1.fc18 updates xorg-x11-drv-ivtv.x86_64 1.2.0-0.1.fc18 fedora xorg-x11-drv-keyboard.x86_64 1.6.2-3.fc18 fedora xorg-x11-drv-mach64.x86_64 6.9.3-6.fc18 fedora xorg-x11-drv-mga.x86_64 1.6.1-2.fc18 fedora xorg-x11-drv-modesetting.x86_64 0.4.0-4.fc18 fedora xorg-x11-drv-mouse.x86_64 1.8.1-3.fc18 fedora xorg-x11-drv-mouse-devel.i686 1.8.1-3.fc18 fedora xorg-x11-drv-mouse-devel.x86_64 1.8.1-3.fc18 fedora xorg-x11-drv-nouveau.x86_64 1:1.0.3-1.fc18 fedora xorg-x11-drv-nv.x86_64 2.1.20-2.fc18 fedora xorg-x11-drv-nvidia.x86_64 1:304.64-3.fc18 rpmfusion-nonfree xorg-x11-drv-nvidia-173xx.x86_64 173.14.36-1.fc18 rpmfusion-nonfree xorg-x11-drv-nvidia-173xx-devel.i686 173.14.36-1.fc18 rpmfusion-nonfree xorg-x11-drv-nvidia-173xx-devel.x86_64 173.14.36-1.fc18 rpmfusion-nonfree xorg-x11-drv-nvidia-173xx-libs.i686 173.14.36-1.fc18 rpmfusion-nonfree xorg-x11-drv-nvidia-173xx-libs.x86_64 173.14.36-1.fc18 rpmfusion-nonfree xorg-x11-drv-nvidia-devel.i686 1:304.64-3.fc18 rpmfusion-nonfree xorg-x11-drv-nvidia-devel.x86_64 1:304.64-3.fc18 rpmfusion-nonfree xorg-x11-drv-nvidia-libs.i686 1:304.64-3.fc18 rpmfusion-nonfree ... Probably this is an installation problem and you should talk with the Fedora support first. The evidence is that you can manually start X from the terminal. As suggestion may be that you have too many video drivers installed for the same device: nouveau, nv and nvidia. Please to close this bug when the issue is resolved. Ciao I faced similar error like this one: xf86OpenConsole: VT_ACTIVATE failed: No such device or address when I tried use my NVidia after uprade from Fedora 16 -> 17. And found resolution for me. At first I would like mention that my notebook has Optimus and I had configured bumblebeed with bbswitch for NVidia (nVidia Corporation GF108 [Quadro 1000M]) usage. As resolution for me works: 1. reinstall bumblebee and bbswitch. 2. then I set nouveau driver load conditions (as described for bbswitch) modprobe bbswitch load_state=0 unload_state=1 3. Reboot I hope this post can be helpfull. It really sounds like you're having fedora issues, not nouveau issues. You either don't have some component installed, or have overwritten something with something else... it's a little hard to tell :) Please file a bug with them if you still haven't gotten it to work. We have some instructions in the wiki for getting stuff set up, perhaps they'll help you: http://nouveau.freedesktop.org/wiki/InstallNouveau/ |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 73154 [details] /var/log/Xorg.0.log Description of problem: I have installed the last release of Fedora F18 After booting, the graphic interface is not displayed and switched to textual interface (login:). Version-Release number of selected component (if applicable): xorg-x11-server 1.13.1-4.fc18 How reproducible: everytime after boot Steps to Reproduce: 1. reboot 2. 3. Actual results: login: in text mode Expected results: login screen under gdm