[SOLVED] X11 Fails to load, black screen
alright, just so everyone knows im a linux noob.
ive just install arch after many hours of work, configured everything, made sure hal was running ect
when i do startx, it just goes to a blank screen.
ive made sure im using the right drivers, and that xterm is the only active DE in .xinitrc
suggestions?
Last edited by supaflyx3 (2010-05-02 20:54:39)
How old is your computer? About 5yo or more? I think your card is quite old and may not work with the recent drivers. Unfortunately the old drivers (xf86-video-intel-legacy) don't work w/ the new xorg so you (and I for that matter, as I have an old intel card too) are pretty much f***ed.
I can get my computer to run, but it will freeze 20 times a day so it's no fun. That's why I stick w/ the old drivers and the old xorg and I'm fine :-)
> xterm is the only active DE in .xinitrc
Can you post your .xinitrc? I think xterm should run ...
> im not getting any errors, just a blank black screen.
OK, what about the logs? 'grep EE /var/log/Xorg.0.log' will show the errors.
How did you configure xorg, do you have xorg.conf?
Similar Messages
-
[SOLVED] X11 Fatal server error: no screens found
Hello everyone!
I have just installed Arch x86_64 and I'm using a nVidia Corporation NV18 [GeForce4 MX 4000].
I'm running the command nvidia-xconfig to set up my xorg. Then I uncommented the line exec gnome-session in my .xinitrc. When run the command startx I get the following:
[root@work ~]# startx
xauth: creating new authority file /root/.serverauth.16103
xauth: creating new authority file /root/.Xauthority
xauth: creating new authority file /root/.Xauthority
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
X.Org X Server 1.6.1.901 (1.6.2 RC 1)
Release Date: 2009-5-8
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.29-ARCH x86_64
Current Operating System: Linux work 2.6.29-ARCH #1 SMP PREEMPT Wed May 20 06:42:43 UTC 2009 x86_64
Build Date: 28 May 2009 08:24:17PM
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: Tue Jun 16 15:08:09 2009
(==) Using config file: "/etc/X11/xorg.conf"
(EE) Failed to load module "type1" (module does not exist, 0)
(EE) Failed to load module "freetype" (module does not exist, 0)
(EE) No devices detected.
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.
And looking at the log:
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
X.Org X Server 1.6.1.901 (1.6.2 RC 1)
Release Date: 2009-5-8
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.29-ARCH x86_64
Current Operating System: Linux work 2.6.29-ARCH #1 SMP PREEMPT Wed May 20 06:42:43 UTC 2009 x86_64
Build Date: 28 May 2009 08:24:17PM
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: Tue Jun 16 15:03:08 2009
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Layout0"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Device0"
(**) |-->Input Device "Keyboard0"
(**) |-->Input Device "Mouse0"
(==) Automatically adding devices
(==) Automatically enabling devices
(==) FontPath set to:
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1,
built-ins
(==) ModulePath set to "/usr/lib/xorg/modules"
(WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
(WW) Disabling Keyboard0
(WW) Disabling Mouse0
(II) Loader magic: 0x3540
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 5.0
X.Org XInput driver : 4.0
X.Org Server Extension : 2.0
(II) Loader running on linux
(--) using VT number 7
(--) PCI:*(0@1:0:0) nVidia Corporation NV18 [GeForce4 MX 4000] rev 193, Mem @ 0xe0000000/16777216, 0xd8000000/134217728, BIOS @ 0x????????/131072
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "record" will be loaded by default.
(II) "dri" will be loaded by default.
(II) "dri2" will be loaded by default.
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.6.1.901, 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: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.6.1.901, 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: "type1"
(WW) Warning, couldn't open module type1
(II) UnloadModule: "type1"
(EE) Failed to load module "type1" (module does not exist, 0)
(II) LoadModule: "freetype"
(WW) Warning, couldn't open module freetype
(II) UnloadModule: "freetype"
(EE) Failed to load module "freetype" (module does not exist, 0)
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
(II) NVIDIA GLX Module 180.51 Fri Apr 17 00:35:49 PDT 2009
(II) Loading extension GLX
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.6.1.901, 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/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.6.1.901, 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/lib/xorg/modules/extensions//libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers//nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(II) NVIDIA dlloader X Driver 180.51 Fri Apr 17 00:15:00 PDT 2009
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 01@00:00:0
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "wfb"
(II) LoadModule: "wfb"
(II) Loading /usr/lib/xorg/modules//libwfb.so
(II) Module wfb: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(WW) NVIDIA(0): The NVIDIA GeForce4 MX 4000 GPU installed in this system is
(WW) NVIDIA(0): supported through the NVIDIA 96.43.xx Legacy drivers.
(WW) NVIDIA(0): Please visit http://www.nvidia.com/object/unix.html for
(WW) NVIDIA(0): more information. The 180.51 NVIDIA driver will ignore
(WW) NVIDIA(0): this GPU. Continuing probe...
(EE) No devices detected.
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.
Aaand my xorg.conf is:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder58) Fri Apr 17 00:40:10 PDT 2009
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
EndSection
Section "Module"
Load "dbe"
Load "extmod"
Load "type1"
Load "freetype"
Load "glx"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection
Something weird is that if I remove the file xorg.conf I can start Gnome normally. Can anyone please tell me what is wrong?
Last edited by kdjtar (2009-06-17 15:59:17)Problem solved! I just noticed that I hadn't check which nvidia version I was using, as the log says:
(WW) NVIDIA(0): The NVIDIA GeForce4 MX 4000 GPU installed in this system is
(WW) NVIDIA(0): supported through the NVIDIA 96.43.xx Legacy drivers.
(WW) NVIDIA(0): Please visit http://www.nvidia.com/object/unix.html for
(WW) NVIDIA(0): more information. The 180.51 NVIDIA driver will ignore
(WW) NVIDIA(0): this GPU. Continuing probe...
And in fact I was using the 180.51 driver. Then I did the following:
# pacman -Rd nvidia nvidia-utils
Then:
# pacman -S nvidia-96xx nvidia-96xx-utils
And it's working now!
Thank you guys -
[SOLVED] XOrg fails to load Nvidia driver on startup
Hi,
I'm having a fairly strange issue where XOrg is failing to load my driver when I start up my laptop. I'm using kdm, but this is causing it to fail. However, doing a simple
$sudo systemctl restart kdm
works, and everything starts up fine. When kdm is in the failed state, I see this:
$sudo systemctl status kdm
● kdm.service - K Display Manager
Loaded: loaded (/usr/lib/systemd/system/kdm.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2014-12-19 18:47:26 EST; 41s ago
Main PID: 247 (kdm)
CGroup: /system.slice/kdm.service
└─247 /usr/bin/kdm -nodaemon
Dec 19 18:47:26 laptop systemd[1]: Started K Display Manager.
Dec 19 18:47:27 laptop kdm[247]: X server died during startup
Dec 19 18:47:27 laptop kdm[247]: X server for display :0 cannot be started, session disabled
And in my XOrg log, I see:
[ 3.639]
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[ 3.639]
X.Org X Server 1.16.2.901 (1.16.3 RC 1)
Release Date: 2014-12-09
[ 3.639] X Protocol Version 11, Revision 0
[ 3.639] Build Operating System: Linux 3.17.2-1-ARCH x86_64
[ 3.639] Current Operating System: Linux laptop 3.17.6-1-ARCH #1 SMP PREEMPT Sun Dec 7 23:43:32 UTC 2014 x86_64
[ 3.639] Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/sda1 rw initrd=../initramfs-linux.img
[ 3.639] Build Date: 10 December 2014 02:34:24PM
[ 3.639]
[ 3.639] Current version of pixman: 0.32.6
[ 3.639] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 3.639] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 3.639] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Dec 19 18:47:26 2014
[ 3.645] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 3.649] (==) No Layout section. Using the first Screen section.
[ 3.649] (==) No screen section available. Using defaults.
[ 3.649] (**) |-->Screen "Default Screen Section" (0)
[ 3.649] (**) | |-->Monitor "<default monitor>"
[ 3.650] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 3.650] (==) Automatically adding devices
[ 3.650] (==) Automatically enabling devices
[ 3.650] (==) Automatically adding GPU devices
[ 3.658] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 3.658] Entry deleted from font path.
[ 3.659] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 3.659] Entry deleted from font path.
[ 3.659] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 3.660] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 3.660] Entry deleted from font path.
[ 3.660] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 3.660] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 3.660] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 3.660] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 3.660] (II) Loader magic: 0x818d80
[ 3.660] (II) Module ABI versions:
[ 3.660] X.Org ANSI C Emulation: 0.4
[ 3.660] X.Org Video Driver: 18.0
[ 3.660] X.Org XInput driver : 21.0
[ 3.660] X.Org Server Extension : 8.0
[ 3.662] (EE) systemd-logind: failed to get session: PID 267 does not belong to any known session
[ 3.663] (--) PCI:*(0:1:0:0) 10de:11a1:1558:0371 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 3.663] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 3.664] (II) LoadModule: "glx"
[ 3.675] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 3.767] (II) Module glx: vendor="NVIDIA Corporation"
[ 3.767] compiled for 4.0.2, module version = 1.0.0
[ 3.767] Module class: X.Org Server Extension
[ 3.768] (II) NVIDIA GLX Module 343.36 Mon Dec 1 15:50:02 PST 2014
[ 3.769] (==) Matched nouveau as autoconfigured driver 0
[ 3.769] (==) Matched nv as autoconfigured driver 1
[ 3.769] (==) Matched modesetting as autoconfigured driver 2
[ 3.769] (==) Matched fbdev as autoconfigured driver 3
[ 3.769] (==) Matched vesa as autoconfigured driver 4
[ 3.769] (==) Assigned the driver to the xf86ConfigLayout
[ 3.769] (II) LoadModule: "nouveau"
[ 3.769] (WW) Warning, couldn't open module nouveau
[ 3.769] (II) UnloadModule: "nouveau"
[ 3.769] (II) Unloading nouveau
[ 3.769] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 3.769] (II) LoadModule: "nv"
[ 3.769] (WW) Warning, couldn't open module nv
[ 3.769] (II) UnloadModule: "nv"
[ 3.769] (II) Unloading nv
[ 3.769] (EE) Failed to load module "nv" (module does not exist, 0)
[ 3.769] (II) LoadModule: "modesetting"
[ 3.769] (WW) Warning, couldn't open module modesetting
[ 3.769] (II) UnloadModule: "modesetting"
[ 3.769] (II) Unloading modesetting
[ 3.769] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 3.769] (II) LoadModule: "fbdev"
[ 3.769] (WW) Warning, couldn't open module fbdev
[ 3.769] (II) UnloadModule: "fbdev"
[ 3.769] (II) Unloading fbdev
[ 3.769] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 3.769] (II) LoadModule: "vesa"
[ 3.770] (WW) Warning, couldn't open module vesa
[ 3.770] (II) UnloadModule: "vesa"
[ 3.770] (II) Unloading vesa
[ 3.770] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 3.770] (EE) No drivers available.
[ 3.770] (EE)
Fatal server error:
[ 3.770] (EE) no screens found(EE)
[ 3.770] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 3.770] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 3.770] (EE)
Which looks like it loads my nvidia driver, but then just decides not to use it for some reason... After I restart kdm, it seems to use the driver fine:
[ 78.897]
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[ 78.897]
X.Org X Server 1.16.2.901 (1.16.3 RC 1)
Release Date: 2014-12-09
[ 78.897] X Protocol Version 11, Revision 0
[ 78.897] Build Operating System: Linux 3.17.2-1-ARCH x86_64
[ 78.897] Current Operating System: Linux laptop 3.17.6-1-ARCH #1 SMP PREEMPT Sun Dec 7 23:43:32 UTC 2014 x86_64
[ 78.897] Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/sda1 rw initrd=../initramfs-linux.img
[ 78.897] Build Date: 10 December 2014 02:34:24PM
[ 78.897]
[ 78.897] Current version of pixman: 0.32.6
[ 78.897] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 78.897] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 78.897] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Dec 19 18:48:38 2014
[ 78.897] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 78.897] (==) No Layout section. Using the first Screen section.
[ 78.897] (==) No screen section available. Using defaults.
[ 78.897] (**) |-->Screen "Default Screen Section" (0)
[ 78.897] (**) | |-->Monitor "<default monitor>"
[ 78.898] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 78.898] (==) Automatically adding devices
[ 78.898] (==) Automatically enabling devices
[ 78.898] (==) Automatically adding GPU devices
[ 78.898] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 78.898] Entry deleted from font path.
[ 78.898] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 78.898] Entry deleted from font path.
[ 78.898] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 78.898] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 78.898] Entry deleted from font path.
[ 78.898] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 78.898] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 78.898] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 78.898] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 78.898] (II) Loader magic: 0x818d80
[ 78.898] (II) Module ABI versions:
[ 78.898] X.Org ANSI C Emulation: 0.4
[ 78.898] X.Org Video Driver: 18.0
[ 78.898] X.Org XInput driver : 21.0
[ 78.898] X.Org Server Extension : 8.0
[ 78.900] (EE) systemd-logind: failed to get session: PID 542 does not belong to any known session
[ 78.900] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 78.901] (--) PCI:*(0:1:0:0) 10de:11a1:1558:0371 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 78.901] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 78.901] (II) LoadModule: "glx"
[ 78.902] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 78.913] (II) Module glx: vendor="NVIDIA Corporation"
[ 78.913] compiled for 4.0.2, module version = 1.0.0
[ 78.913] Module class: X.Org Server Extension
[ 78.913] (II) NVIDIA GLX Module 343.36 Mon Dec 1 15:50:02 PST 2014
[ 78.914] (II) Applying OutputClass "nvidia" to /dev/dri/card0
[ 78.914] loading driver: nvidia
[ 78.914] (==) Matched nvidia as autoconfigured driver 0
[ 78.914] (==) Matched nouveau as autoconfigured driver 1
[ 78.914] (==) Matched nv as autoconfigured driver 2
[ 78.914] (==) Matched nouveau as autoconfigured driver 3
[ 78.914] (==) Matched nv as autoconfigured driver 4
[ 78.914] (==) Matched modesetting as autoconfigured driver 5
[ 78.914] (==) Matched fbdev as autoconfigured driver 6
[ 78.914] (==) Matched vesa as autoconfigured driver 7
[ 78.914] (==) Assigned the driver to the xf86ConfigLayout
[ 78.914] (II) LoadModule: "nvidia"
[ 78.914] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 78.920] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 78.920] compiled for 4.0.2, module version = 1.0.0
[ 78.920] Module class: X.Org Video Driver
[ 78.920] (II) LoadModule: "nouveau"
[ 78.921] (WW) Warning, couldn't open module nouveau
[ 78.921] (II) UnloadModule: "nouveau"
[ 78.921] (II) Unloading nouveau
[ 78.921] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 78.921] (II) LoadModule: "nv"
[ 78.921] (WW) Warning, couldn't open module nv
[ 78.921] (II) UnloadModule: "nv"
[ 78.921] (II) Unloading nv
[ 78.921] (EE) Failed to load module "nv" (module does not exist, 0)
[ 78.921] (II) LoadModule: "modesetting"
[ 78.921] (WW) Warning, couldn't open module modesetting
[ 78.921] (II) UnloadModule: "modesetting"
[ 78.921] (II) Unloading modesetting
[ 78.921] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 78.921] (II) LoadModule: "fbdev"
[ 78.922] (WW) Warning, couldn't open module fbdev
[ 78.922] (II) UnloadModule: "fbdev"
[ 78.922] (II) Unloading fbdev
[ 78.922] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 78.922] (II) LoadModule: "vesa"
[ 78.922] (WW) Warning, couldn't open module vesa
[ 78.922] (II) UnloadModule: "vesa"
[ 78.922] (II) Unloading vesa
[ 78.922] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 78.922] (II) NVIDIA dlloader X Driver 343.36 Mon Dec 1 15:28:39 PST 2014
[ 78.922] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 78.922] (++) using VT number 7
[ 78.935] (II) Loading sub module "fb"
[ 78.935] (II) LoadModule: "fb"
[ 78.935] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 78.936] (II) Module fb: vendor="X.Org Foundation"
[ 78.936] compiled for 1.16.2.901, module version = 1.0.0
[ 78.936] ABI class: X.Org ANSI C Emulation, version 0.4
[ 78.936] (II) Loading sub module "wfb"
[ 78.936] (II) LoadModule: "wfb"
[ 78.936] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 78.937] (II) Module wfb: vendor="X.Org Foundation"
[ 78.937] compiled for 1.16.2.901, module version = 1.0.0
[ 78.937] ABI class: X.Org ANSI C Emulation, version 0.4
[ 78.937] (II) Loading sub module "ramdac"
[ 78.937] (II) LoadModule: "ramdac"
[ 78.937] (II) Module "ramdac" already built-in
[ 78.939] (II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 78.939] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 78.939] (==) NVIDIA(0): RGB weight 888
[ 78.939] (==) NVIDIA(0): Default visual is TrueColor
[ 78.939] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 78.940] (**) NVIDIA(0): Enabling 2D acceleration
[ 79.610] (II) NVIDIA(0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 79.610] (II) NVIDIA(0): 3D Vision stereo.
[ 79.610] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20130102)
[ 79.612] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 670MX (GK104) at PCI:1:0:0 (GPU-0)
[ 79.612] (--) NVIDIA(0): Memory: 3145728 kBytes
[ 79.612] (--) NVIDIA(0): VideoBIOS: 80.04.67.00.06
[ 79.612] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 79.616] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 670MX at PCI:1:0:0
[ 79.616] (--) NVIDIA(0): Chi Mei Optoelectronics corp. (DFP-0) (boot, connected)
[ 79.616] (--) NVIDIA(0): Samsung SyncMaster (DFP-1) (connected)
[ 79.616] (--) NVIDIA(0): DFP-2
[ 79.616] (--) NVIDIA(0): DFP-3
[ 79.616] (--) NVIDIA(0): DFP-4
[ 79.616] (--) NVIDIA(0): Chi Mei Optoelectronics corp. (DFP-0): Internal LVDS
[ 79.616] (--) NVIDIA(GPU-0): Chi Mei Optoelectronics corp. (DFP-0): 330.0 MHz maximum pixel clock
[ 79.616] (--) NVIDIA(0): Samsung SyncMaster (DFP-1): Internal TMDS
[ 79.616] (--) NVIDIA(GPU-0): Samsung SyncMaster (DFP-1): 165.0 MHz maximum pixel clock
[ 79.616] (--) NVIDIA(0): DFP-2: Internal TMDS
[ 79.616] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[ 79.616] (--) NVIDIA(0): DFP-3: Internal DisplayPort
[ 79.616] (--) NVIDIA(GPU-0): DFP-3: 960.0 MHz maximum pixel clock
[ 79.616] (--) NVIDIA(0): DFP-4: Internal DisplayPort
[ 79.616] (--) NVIDIA(GPU-0): DFP-4: 960.0 MHz maximum pixel clock
[ 79.616] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 79.616] (**) NVIDIA(0): device Chi Mei Optoelectronics corp. (DFP-0) (Using EDID
[ 79.616] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
[ 79.616] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 79.616] (**) NVIDIA(0): device Samsung SyncMaster (DFP-1) (Using EDID frequencies
[ 79.616] (**) NVIDIA(0): has been enabled on all display devices.)
[ 79.618] (==) NVIDIA(0):
[ 79.618] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 79.618] (==) NVIDIA(0): will be used as the requested mode.
[ 79.618] (==) NVIDIA(0):
[ 79.619] (II) NVIDIA(0): Validated MetaModes:
[ 79.619] (II) NVIDIA(0): "DFP-0:nvidia-auto-select,DFP-1:nvidia-auto-select"
[ 79.619] (II) NVIDIA(0): Virtual screen size determined to be 3600 x 1080
[ 80.144] (--) NVIDIA(0): DPI set to (128, 130); computed from "UseEdidDpi" X config
[ 80.144] (--) NVIDIA(0): option
[ 80.144] (--) Depth 24 pixmap format is 32 bpp
[ 80.144] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 80.144] (II) NVIDIA: access.
[ 80.150] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 80.150] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 80.150] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 80.150] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 80.150] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 80.150] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 80.150] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 80.150] (II) NVIDIA(0): Config Options in the README.
[ 80.155] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select,DFP-1:nvidia-auto-select"
[ 80.532] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 80.532] (==) NVIDIA(0): Backing store enabled
[ 80.532] (==) NVIDIA(0): Silken mouse enabled
[ 80.533] (==) NVIDIA(0): DPMS enabled
[ 80.533] (II) Loading sub module "dri2"
[ 80.533] (II) LoadModule: "dri2"
[ 80.533] (II) Module "dri2" already built-in
[ 80.533] (II) NVIDIA(0): [DRI2] Setup complete
[ 80.533] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 80.533] (--) RandR disabled
[ 80.539] (II) Initializing extension GLX
[ 80.605] (II) config/udev: Adding input device Power Button (/dev/input/event14)
[ 80.605] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 80.605] (II) LoadModule: "evdev"
[ 80.606] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 80.607] (II) Module evdev: vendor="X.Org Foundation"
[ 80.607] compiled for 1.16.2, module version = 2.9.1
[ 80.607] Module class: X.Org XInput Driver
[ 80.607] ABI class: X.Org XInput driver, version 21.0
[ 80.607] (II) Using input driver 'evdev' for 'Power Button'
[ 80.607] (**) Power Button: always reports core events
[ 80.607] (**) evdev: Power Button: Device: "/dev/input/event14"
[ 80.608] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 80.608] (--) evdev: Power Button: Found keys
[ 80.608] (II) evdev: Power Button: Configuring as keyboard
[ 80.608] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input18/event14"
[ 80.608] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 80.608] (**) Option "xkb_rules" "evdev"
[ 80.608] (**) Option "xkb_model" "pc104"
[ 80.608] (**) Option "xkb_layout" "us"
[ 80.635] (II) config/udev: Adding input device Video Bus (/dev/input/event15)
[ 80.635] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 80.635] (II) Using input driver 'evdev' for 'Video Bus'
[ 80.635] (**) Video Bus: always reports core events
[ 80.635] (**) evdev: Video Bus: Device: "/dev/input/event15"
[ 80.635] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 80.635] (--) evdev: Video Bus: Found keys
[ 80.635] (II) evdev: Video Bus: Configuring as keyboard
[ 80.635] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/LNXVIDEO:00/input/input19/event15"
[ 80.635] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 80.635] (**) Option "xkb_rules" "evdev"
[ 80.635] (**) Option "xkb_model" "pc104"
[ 80.635] (**) Option "xkb_layout" "us"
[ 80.636] (II) config/udev: Adding input device Power Button (/dev/input/event13)
[ 80.636] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 80.636] (II) Using input driver 'evdev' for 'Power Button'
[ 80.636] (**) Power Button: always reports core events
[ 80.636] (**) evdev: Power Button: Device: "/dev/input/event13"
[ 80.636] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 80.636] (--) evdev: Power Button: Found keys
[ 80.636] (II) evdev: Power Button: Configuring as keyboard
[ 80.636] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input17/event13"
[ 80.636] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[ 80.636] (**) Option "xkb_rules" "evdev"
[ 80.636] (**) Option "xkb_model" "pc104"
[ 80.636] (**) Option "xkb_layout" "us"
[ 80.637] (II) config/udev: Adding input device Lid Switch (/dev/input/event11)
[ 80.637] (II) No input driver specified, ignoring this device.
[ 80.637] (II) This device may have been added with another device file.
[ 80.637] (II) config/udev: Adding input device Sleep Button (/dev/input/event12)
[ 80.637] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 80.637] (II) Using input driver 'evdev' for 'Sleep Button'
[ 80.637] (**) Sleep Button: always reports core events
[ 80.637] (**) evdev: Sleep Button: Device: "/dev/input/event12"
[ 80.637] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[ 80.637] (--) evdev: Sleep Button: Found keys
[ 80.637] (II) evdev: Sleep Button: Configuring as keyboard
[ 80.637] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input16/event12"
[ 80.637] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
[ 80.637] (**) Option "xkb_rules" "evdev"
[ 80.637] (**) Option "xkb_model" "pc104"
[ 80.637] (**) Option "xkb_layout" "us"
[ 80.638] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event18)
[ 80.638] (II) No input driver specified, ignoring this device.
[ 80.638] (II) This device may have been added with another device file.
[ 80.638] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event19)
[ 80.638] (II) No input driver specified, ignoring this device.
[ 80.638] (II) This device may have been added with another device file.
[ 80.639] (II) config/udev: Adding input device LOGITECH G110 G-keys (/dev/input/event3)
[ 80.639] (**) LOGITECH G110 G-keys: Applying InputClass "evdev keyboard catchall"
[ 80.639] (II) Using input driver 'evdev' for 'LOGITECH G110 G-keys'
[ 80.639] (**) LOGITECH G110 G-keys: always reports core events
[ 80.639] (**) evdev: LOGITECH G110 G-keys: Device: "/dev/input/event3"
[ 80.639] (--) evdev: LOGITECH G110 G-keys: Vendor 0x46d Product 0xc22b
[ 80.639] (--) evdev: LOGITECH G110 G-keys: Found keys
[ 80.639] (II) evdev: LOGITECH G110 G-keys: Configuring as keyboard
[ 80.639] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.1/3-4.1.1/3-4.1.1:1.0/0003:046D:C22B.0003/input/input7/event3"
[ 80.639] (II) XINPUT: Adding extended input device "LOGITECH G110 G-keys" (type: KEYBOARD, id 10)
[ 80.639] (**) Option "xkb_rules" "evdev"
[ 80.639] (**) Option "xkb_model" "pc104"
[ 80.639] (**) Option "xkb_layout" "us"
[ 80.639] (II) config/udev: Adding input device Gaming Keyboard G110 (/dev/input/event4)
[ 80.639] (**) Gaming Keyboard G110: Applying InputClass "evdev keyboard catchall"
[ 80.639] (II) Using input driver 'evdev' for 'Gaming Keyboard G110'
[ 80.639] (**) Gaming Keyboard G110: always reports core events
[ 80.639] (**) evdev: Gaming Keyboard G110: Device: "/dev/input/event4"
[ 80.640] (--) evdev: Gaming Keyboard G110: Vendor 0x46d Product 0xc22a
[ 80.640] (--) evdev: Gaming Keyboard G110: Found keys
[ 80.640] (II) evdev: Gaming Keyboard G110: Configuring as keyboard
[ 80.640] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.1/3-4.1.3/3-4.1.3:1.0/0003:046D:C22A.0004/input/input8/event4"
[ 80.640] (II) XINPUT: Adding extended input device "Gaming Keyboard G110" (type: KEYBOARD, id 11)
[ 80.640] (**) Option "xkb_rules" "evdev"
[ 80.640] (**) Option "xkb_model" "pc104"
[ 80.640] (**) Option "xkb_layout" "us"
[ 80.640] (II) config/udev: Adding input device Gaming Keyboard G110 (/dev/input/event5)
[ 80.640] (**) Gaming Keyboard G110: Applying InputClass "evdev keyboard catchall"
[ 80.640] (II) Using input driver 'evdev' for 'Gaming Keyboard G110'
[ 80.640] (**) Gaming Keyboard G110: always reports core events
[ 80.640] (**) evdev: Gaming Keyboard G110: Device: "/dev/input/event5"
[ 80.640] (--) evdev: Gaming Keyboard G110: Vendor 0x46d Product 0xc22a
[ 80.640] (--) evdev: Gaming Keyboard G110: Found keys
[ 80.640] (II) evdev: Gaming Keyboard G110: Configuring as keyboard
[ 80.640] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.1/3-4.1.3/3-4.1.3:1.1/0003:046D:C22A.0005/input/input9/event5"
[ 80.640] (II) XINPUT: Adding extended input device "Gaming Keyboard G110" (type: KEYBOARD, id 12)
[ 80.640] (**) Option "xkb_rules" "evdev"
[ 80.640] (**) Option "xkb_model" "pc104"
[ 80.641] (**) Option "xkb_layout" "us"
[ 80.641] (II) config/udev: Adding input device Razer Razer Lachesis (/dev/input/event1)
[ 80.641] (**) Razer Razer Lachesis: Applying InputClass "evdev pointer catchall"
[ 80.641] (II) Using input driver 'evdev' for 'Razer Razer Lachesis'
[ 80.641] (**) Razer Razer Lachesis: always reports core events
[ 80.641] (**) evdev: Razer Razer Lachesis: Device: "/dev/input/event1"
[ 80.641] (--) evdev: Razer Razer Lachesis: Vendor 0x1532 Product 0xc
[ 80.641] (--) evdev: Razer Razer Lachesis: Found 12 mouse buttons
[ 80.641] (--) evdev: Razer Razer Lachesis: Found scroll wheel(s)
[ 80.641] (--) evdev: Razer Razer Lachesis: Found relative axes
[ 80.641] (--) evdev: Razer Razer Lachesis: Found x and y relative axes
[ 80.641] (II) evdev: Razer Razer Lachesis: Configuring as mouse
[ 80.641] (II) evdev: Razer Razer Lachesis: Adding scrollwheel support
[ 80.641] (**) evdev: Razer Razer Lachesis: YAxisMapping: buttons 4 and 5
[ 80.641] (**) evdev: Razer Razer Lachesis: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 80.641] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.2/3-4.2:1.0/0003:1532:000C.0001/input/input5/event1"
[ 80.641] (II) XINPUT: Adding extended input device "Razer Razer Lachesis" (type: MOUSE, id 13)
[ 80.642] (II) evdev: Razer Razer Lachesis: initialized for relative axes.
[ 80.642] (**) Razer Razer Lachesis: (accel) keeping acceleration scheme 1
[ 80.642] (**) Razer Razer Lachesis: (accel) acceleration profile 0
[ 80.642] (**) Razer Razer Lachesis: (accel) acceleration factor: 2.000
[ 80.642] (**) Razer Razer Lachesis: (accel) acceleration threshold: 4
[ 80.642] (II) config/udev: Adding input device Razer Razer Lachesis (/dev/input/mouse0)
[ 80.642] (II) No input driver specified, ignoring this device.
[ 80.642] (II) This device may have been added with another device file.
[ 80.643] (II) config/udev: Adding input device Razer Razer Lachesis (/dev/input/event2)
[ 80.643] (**) Razer Razer Lachesis: Applying InputClass "evdev keyboard catchall"
[ 80.643] (II) Using input driver 'evdev' for 'Razer Razer Lachesis'
[ 80.643] (**) Razer Razer Lachesis: always reports core events
[ 80.643] (**) evdev: Razer Razer Lachesis: Device: "/dev/input/event2"
[ 80.643] (--) evdev: Razer Razer Lachesis: Vendor 0x1532 Product 0xc
[ 80.643] (--) evdev: Razer Razer Lachesis: Found keys
[ 80.643] (II) evdev: Razer Razer Lachesis: Configuring as keyboard
[ 80.643] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.2/3-4.2:1.1/0003:1532:000C.0002/input/input6/event2"
[ 80.643] (II) XINPUT: Adding extended input device "Razer Razer Lachesis" (type: KEYBOARD, id 14)
[ 80.643] (**) Option "xkb_rules" "evdev"
[ 80.643] (**) Option "xkb_model" "pc104"
[ 80.643] (**) Option "xkb_layout" "us"
[ 80.643] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event6)
[ 80.643] (II) No input driver specified, ignoring this device.
[ 80.643] (II) This device may have been added with another device file.
[ 80.644] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event7)
[ 80.644] (II) No input driver specified, ignoring this device.
[ 80.644] (II) This device may have been added with another device file.
[ 80.644] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event8)
[ 80.644] (II) No input driver specified, ignoring this device.
[ 80.644] (II) This device may have been added with another device file.
[ 80.644] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event9)
[ 80.644] (II) No input driver specified, ignoring this device.
[ 80.644] (II) This device may have been added with another device file.
[ 80.645] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event10)
[ 80.645] (II) No input driver specified, ignoring this device.
[ 80.645] (II) This device may have been added with another device file.
[ 80.645] (II) config/udev: Adding input device BisonCam, NB Pro (/dev/input/event17)
[ 80.645] (**) BisonCam, NB Pro: Applying InputClass "evdev keyboard catchall"
[ 80.645] (II) Using input driver 'evdev' for 'BisonCam, NB Pro'
[ 80.645] (**) BisonCam, NB Pro: always reports core events
[ 80.645] (**) evdev: BisonCam, NB Pro: Device: "/dev/input/event17"
[ 80.645] (--) evdev: BisonCam, NB Pro: Vendor 0x5986 Product 0x512
[ 80.645] (--) evdev: BisonCam, NB Pro: Found keys
[ 80.645] (II) evdev: BisonCam, NB Pro: Configuring as keyboard
[ 80.645] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/input/input23/event17"
[ 80.645] (II) XINPUT: Adding extended input device "BisonCam, NB Pro" (type: KEYBOARD, id 15)
[ 80.645] (**) Option "xkb_rules" "evdev"
[ 80.645] (**) Option "xkb_model" "pc104"
[ 80.645] (**) Option "xkb_layout" "us"
[ 80.646] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 80.646] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 80.646] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 80.646] (**) AT Translated Set 2 keyboard: always reports core events
[ 80.646] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 80.646] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 80.646] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 80.646] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 80.646] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 80.646] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 16)
[ 80.646] (**) Option "xkb_rules" "evdev"
[ 80.646] (**) Option "xkb_model" "pc104"
[ 80.646] (**) Option "xkb_layout" "us"
[ 80.646] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event20)
[ 80.646] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 80.647] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 80.647] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
[ 80.647] (II) LoadModule: "synaptics"
[ 80.647] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 80.647] (II) Module synaptics: vendor="X.Org Foundation"
[ 80.647] compiled for 1.16.0, module version = 1.8.1
[ 80.647] Module class: X.Org XInput Driver
[ 80.647] ABI class: X.Org XInput driver, version 21.0
[ 80.647] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[ 80.647] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 80.647] (**) Option "Device" "/dev/input/event20"
[ 80.756] (II) synaptics: SynPS/2 Synaptics TouchPad: found clickpad property
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5662 (res 42)
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4660 (res 47)
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left double triple
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[ 80.757] (**) Option "TapButton1" "1"
[ 80.757] (**) Option "TapButton2" "2"
[ 80.757] (**) Option "TapButton3" "3"
[ 80.757] (**) Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 80.757] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 80.810] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio2/input/input22/event20"
[ 80.810] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 17)
[ 80.810] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[ 80.810] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
[ 80.810] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.038
[ 80.810] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 80.810] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[ 80.810] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 80.810] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 80.810] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 80.811] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
[ 80.811] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
[ 80.811] (II) config/udev: Adding input device PC Speaker (/dev/input/event16)
[ 80.811] (II) No input driver specified, ignoring this device.
[ 80.811] (II) This device may have been added with another device file.
[ 88.265] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 88.265] (II) NVIDIA(GPU-0): 3D Vision stereo.
[ 88.282] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 88.282] (II) NVIDIA(GPU-0): 3D Vision stereo.
[ 88.291] (II) NVIDIA(0): Setting mode "LVDS-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, HDMI-0: 1680x1050_60_0 @1680x1050 +1920+0 {ViewPortIn=1680x1050, ViewPortOut=1680x1050+0+0}"
[ 89.221] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 89.221] (II) NVIDIA(GPU-0): 3D Vision stereo.
[ 90.639] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 90.639] (II) NVIDIA(GPU-0): 3D Vision stereo.
[ 93.745] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 93.745] (II) NVIDIA(GPU-0): 3D Vision stereo.
Notably, the following lines appear in the working case, but not the broken case:
[ 78.914] (II) Applying OutputClass "nvidia" to /dev/dri/card0
[ 78.914] loading driver: nvidia
Does anyone know what might be going on here?
Last edited by straemer (2014-12-20 13:03:58)Hmmmm, that doesn't seem to be the issue. I have a nvidia geforce gtx 670mx. The nvidia website does link me to the 340xx driver for that card, but downgrading to that version still has the same issue. I suspect the issue is in Xorg, since it seems to load the module, but then decides it doesn't have a driver to run for some reason.
-
Windows boots but won't load (Black screen with cursor)
[Sorry for the long post, but I feel the need to fully explain my situation]
I have the following problem:
I turn on my PC, and Windows shows it's normal loading screen, after which it goes into a completely black screen, with just the mouse in the middle. By the cursor size I can tell that it's in a low resolution, probably 800x600 (compared to my usual 1920x1080). I am able to move the mouse around, but with no particular use without something to click on. No other keyboard input seems to work, except for Shift key 5 times, which brings up the Sticky Keys dialog box (with just "Yes" or "No" options, no other link); and Windows key+U which brings up the Ease of Access center. Ctr+Alt+Del does NOT work.
So far this is what I have tried (in chronological order):
Boot into Safe Mode, Safe Mode with Networking, Safe Mode with Command Prompt, Booting in low resolution video, Last known good configuration: all yield the same result as booting normally.
Repair your computer:
Startup Repair: Found Registry Errors (I realized and fixed this later on)
System Restore: Did not find any previous restore points (I know for sure that there are, I made a habit of making restore points regularly).
Windows Memory Diagnostics: Did not find errors.
Command prompt:
Ran chkdsk /f /r command, did not report errors.
Ran sfc /scannow : I don't remember the exact report, but it asked for a restart to finish repairing problems. I restarted, and ran the command again for the same result.
Forced the scan with: sfc /scannow /offbootdir=c:\ /offwindir=c:\windows , it found and repaired some errors, still could not load windows.
Ran Dell Startup Diagnostics, found no errors.
Ran Startup Repair again, found the registry errors again. I found the solution to this in a Microsoft Help forum ( answers.microsoft.com/.../f77d5355-b8be-41d6-af24-cae994e1768f ), and fixed the issue. I rebooted, but the problem persists.
Startup Repair now finds no errors. I tried System Restore again, it found 2 restore points dated AFTER my problem started. I decided to restore anyways, but neither of them worked.
I ran Windows Defender Offline:
Quick Scan: and found 2 threats and removed them.
Full System Scan: found 4 more threats, removed 2 of them, the other two couldn't be removed because they were within an ISO file.
I tried Steps 1, 2 and 3 again with no luck.
With each step I am aware that I'm closer to having to reinstall Windows, so I decided to see if I could still access my HHDD to save my personal files. I made a Linux live CD (with Ubuntu), but I am having trouble mounting the drives, because they are in a RAID0 configuration. "sudo dmraid -s" gives the following error: "ERROR: isw: wrong number of devices in RAID set "isw_dbdffjficc_ARRAY0" [1/2] on /dev/sdb".
Important Details:
I changed my graphics card about 4 months ago (an Nvidia GTX 750ti for an ATI Radeon HD 6450), and I was told that I may be running short with the Power Supply. The new card asks for a minimum of 450W and I think my PSU is 460W. This may or may not have something to do with this issue, I have no idea.
The RAID0 configuration of my 2 500GB Hard Drives brought me a lot of problems from day 1. One of the HDD would randomly fail (I am able to hear a different clicking sound when this happens), and the computer would crash. Upon startup, it would ask for a boot device. The Dell startup utility would then only recognize 1 of the drives, but would finish without errors. After a restart or two, all would be fine and windows would boot normally (aside from the usual error recovery screen) without any sign of corrupted data or anything. Like I said, this has been happening form the day my PC arrived, but restarting a couple of times always fixed it. As of now, both HHDD seem to be working fine, the Dell utility recognizes both of them, and does not find errors in any of them, and I can access any directory from the command prompt.
Is there anything else I should try before reinstalling Windows?
Before the install, I would really like to be able to recover my files (I have important documents from college), is there any way to do this?
Sorry again for the extremely long post (and for any language errors, English is not my native language), and thanks in advance.Since you still haven't got your data from the drive(s). I would advise performing a Windows installation without formatting the drive... I don't like this solution but at this stage you have probably tried everything else.
Use a Windows 7 Reinstallation DVD when installing ensure you select...
Select Custom: Install Windows only (advanced)
If you do not select any of the drive options and simply highlight the largest partition and select next:
Windows will dump all the old installation files in the Windows.old folder -
Failed win7 installation, black screen on boot
I have an Imac, about 4 years old, 2ghz core 2 duo.
Last night i attempted to install a copy on windows 7 in bootcamp. I created an install DVD, succesfully created a partition and got about 1/3 way through the installation when it failed. I tried twice then shut down the computer. Today i started the imac, boot sound worked, then after white screen for a few seconds, black screen with a flashing white - in the top left, like dos. I'm unable to type anything.
I've tried booting in safe mode, selecting boot device etc, but nothing. the only thing i've been able to do is eject the windows disk by holding f12.
I'm using a logitech wireleskeyboard and mouse if that matters.
I have also tried creating a bootable usb drive with mountain lion,but as i cant get to the boot menu, it's no use.
I've got all my dada backed up externally so i dont mind having to freshly install if that's an issue.
any ideas? thanksCould be your monitor power supply is going. could also be 10.6.6 so first try to get back to a OSX which did not give you problems.
-
Help me!!! SWFLoader loads black screen in front of Flashpaper2
if(printVB.getChildByName("fpSendfax")){printVB.re moveChild(printVB.getChildByName("fpSendfax"));}
var ldr:SWFLoader = new SWFLoader();
ldr.name = "fpSendfax";
var url:String = "flash/flashpaperloader.swf";
ldr.load(url);
ldr.addEventListener(Event.COMPLETE, function(event:Event):void {printVB.addChild(ldr)});
I use the above code to load a flashpaper which is generated by coldfusion cfc. When I load the movie for the first time it works great.
If i reload another movie I get a black screen and the flashpaper loads in the background.
why???
It there anything we can do?I'm having the exact same problem... did you find a solution????
-
Hey all,
I've got a fresh install of Arch on my workstation after successfully installing it on my netbook, but it's refusing to cooperate nicely with X.
Even after a fresh install of X, starting X as root merely gets me a black screen, usually with red lines on it. It also seems to have all the tty screens transplanted onto tty7 (or the X11 screen), so that tty1, for example, won't have any output (just the flashing cursor) but it gets put onto the X11 screen instead.
Could somebody help out here? I'm using an Nvidia 9800GT. X should work by itself, I managed to get it working somehow before, it gave me a fresh twm desktop. However, after installing SLiM and running that (both with inittab and daemon), X gives me the screen above.
What's going on?
Last edited by chaoticdefendant (2010-09-13 11:23:34)SLiM is wildly under-maintained, how are you launching it at the moment?
that nvidia card needs the "nvidia" module, do you have this installed?
if you disable slim and do the following:
cp /etc/skel/.xinitrc /home/username/
and then edit /home/username/.xinitrc to look like so:
#!/bin/sh
# ~/.xinitrc
# Executed by startx (run your window manager from here)
exec xterm
# exec startkde
# exec startxfce4
# ...or the Window Manager of your choice
and then start X using:
$ startx
do things then work properly? -
Firmward update failed... black screen..
My firmware update was interrupted or failed. I burned a cd with the firmware restoration and followed the instructions, but just get a black screen and nothing happens. Can anyone advise me on what to do next? Thanks in advance. Pam
Hey I just fixed this for a customer at Compusa. You need to make sure you hold the power button down until you see the power light flash 3 quick 3 slow 3 quick. When you see that put the disc in and let go of the power button. It will take a moment and then the restore should start.
Also make sure you bernt the disk right. You have to use disk utilites for it to work correctly, you must burn the image and not just the file. Open Disk Utilities, and drag the dgm file into the hard drive list on the left side. Select it and click burn. Feed it a disc and you should have a working firmware restore disc.
Also make sure you are using the right firmware restore disc. This one worked for me.
http://www.apple.com/support/downloads/macbookproefifirmwareupdate12.html
Hope that helps. -
YouTube loads black screen for first five seconds
Starting early January 2013 in Firefox, YouTube videos are loaded as blank black screens for the first five seconds. At the 0:06 mark, videos start playing normally. This is not an issue in Chrome or IE. Tested with all plug-ins and add-ons disabled (except Flash player). Plug-ins/add-ons updated. Tried re-installing Firefox with no solution. Help? Thanks!
You can check for problems caused by recent Flash updates and try these:
*disable a possible RealPlayer Browser Record Plugin extension for Firefox and update the RealPlayer if installed
*disable protected mode in Flash 11.3 and later
*disable hardware acceleration in the Flash plugin
*http://kb.mozillazine.org/Flash#Troubleshooting -
[SOLVED]Get [FAIL] when loading user specified modules.
That is it, when the system is booting i get a [FAIL] message when loading user specified modules after upgrading udev, and the kmod new module handling or something as say in the news. I dont have a modprobe.conf or a modprobe.conf.pacsave file either and creating a modprobe.conf file doesn't solve the problem. The strange thing is that the modules are loaded anyways. I mean the ones that are specified in rc.conf. I dont know if the system [FAIL] to load that modules or others...The system works fine for now too.
Thanks.
PD: sorry if you notice my poor english.
Last edited by Hyugga (2012-01-22 23:09:02)I had the same problem and removing the governor performance from rc.conf solved the problem. I tried however to remove both governors and only leave powernow-k8 (this is the only one that works for me) leaving rc.conf like this:
MODULES=(brcmsmac powernow-k8)
When I boot the laptop and check which governors are available and being used I get the following:
[netlak@soulrebel ~]$ cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to [email protected], please.
analyzing CPU 0:
driver: powernow-k8
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 8.0 us.
hardware limits: 800 MHz - 2.10 GHz
available frequency steps: 2.10 GHz, 1.50 GHz, 800 MHz
available cpufreq governors: performance
current policy: frequency should be within 800 MHz and 2.10 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 2.10 GHz.
This like as if the ondemand governor would not be available but when unplugging the laptop and check again I get this:
[netlak@soulrebel ~]$ cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to [email protected], please.
analyzing CPU 0:
driver: powernow-k8
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 8.0 us.
hardware limits: 800 MHz - 2.10 GHz
available frequency steps: 2.10 GHz, 1.50 GHz, 800 MHz
available cpufreq governors: ondemand, performance
current policy: frequency should be within 800 MHz and 2.10 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 800 MHz.
This shows that the ondemand module can be autoloaded when needed, so I leave rc.conf only with powernow-k8.
Thanks for your help. -
[SOLVED] Gnome 2.30 logout = black screen only
Are any of the rest of you that don't run a display manager getting a black screen only after logging out from version 2.30 of Gnome that just hit the repos?
This means no command line, no shutdown, no startx, or anything other than blackness. I have to reboot just to reach a command line again, then I can startx, or shutdown. Things worked fine before this, so I'm guessing it's a bug with one of the new packages.
If someone can confirm, I'll file a bug report.
Thanks.
Edit: added solved tag
Last edited by ozar (2010-04-01 03:06:12)Never mind... after a couple of reboots, it started working properly again.
-
Computer loads black screen installing Windows 7 / 8
Hello,
I have installed Windows 7 on my machine several times without any problems. After updating to Mountain Lion however my computer will always hang at a black screen when it is time to run the Windows installer.
I have tried this with Windows 8 and experience the same issue.
Any ideas / help would be very appreciated
Thank you so much
Josephbump
-
[Solved] Catalyst fails to load kernel module
I have just been through the Catalyst install guide, I installed from the Vi0L0 repos rather than building myself.
Everything appeared to go fine, however fglrx fails to load when I reboot. The xorg log contains;
fglrx(0): atiddxDriScreenInit failed. Probably kernel module missing or incompatible
fglrx(0): **********************************************************
fglrx(0): * DRI initialization failed
fglrx(0): * kernel module (fglrx.ko) may be missing or incompatible
fglrx(0): * 2D and 3D acceleration disabled
fglrx(0): **********************************************************
Is this recoverable? Or does this mean that the current Vi0L0 module has not been built for my kernel (3.11.5-1-ARCH)?
Last edited by ~lynks (2013-11-03 16:16:00)This issue has now been resolved after the update to xorg 1.14
lsmod | grep fglrx
shows fglrx is not loaded, and:
modprobe fglrx
returns with;
modprobe: ERROR: could not insert 'fglrx': Exec format error
Does that indicate a 32/64 bit issue?
This issue has now been resolved after the update to xorg 1.14
Last edited by ~lynks (2013-11-03 16:15:48) -
Hi,
Lately, colord.service fails to load with this message :
colord.service - Manage, Install and Generate Color Profiles
Loaded: loaded (/usr/lib/systemd/system/colord.service; static)
Active: failed (Result: core-dump) since lun. 2013-05-06 18:59:04 CEST; 6min ago
Process: 1480 ExecStart=/usr/lib/colord/colord (code=dumped, signal=SEGV)
mai 06 18:59:04 shellphone colord[1480]: Profile added: icc-6fb3a23d8d7d23908c613c556d3e10cf
mai 06 18:59:04 shellphone colord[1480]: Profile added: icc-99e1cb8aae315f3241bc6866325d7e1e
mai 06 18:59:04 shellphone colord[1480]: Profile added: icc-9641812b452fc79a145471df34e5133c
mai 06 18:59:04 shellphone colord[1480]: Profile added: icc-90bb3cf4d7f73e2aa1f2e7c93ca71710
mai 06 18:59:04 shellphone colord[1480]: Profile added: icc-bc2d6f78dfa777ece4bda1ecabceefc6
mai 06 18:59:04 shellphone colord[1480]: Profile added: icc-c3f7b1c952897dd0cea880a54292f0d1
mai 06 18:59:04 shellphone colord[1480]: (colord:1480): libcolord-CRITICAL **: cd_icc_load_data: assertion `data_len != 0' failed
mai 06 18:59:04 shellphone systemd-coredump[1483]: Process 1480 (colord) dumped core.
mai 06 18:59:04 shellphone systemd[1]: colord.service: main process exited, code=dumped, status=11/SEGV
mai 06 18:59:04 shellphone systemd[1]: MESSAGE=Unit colord.service entered failed state.
Does it work for you ? Any clue about what's happening ?
Last edited by omer666 (2013-05-14 12:26:08)Works here v0.1.34-1. What version are you running?
Does it occur at boot and/or manual start?
Have you checked colord's bug tracker? If there's not a report there it's probably worth reporting as even if you have a set-up issue, it shouldn't really core dump.
Last edited by skanky (2013-05-15 13:42:20) -
Lenovo 3000 N200 ( Bios flash failed) now just black screen
Updating bios and froze ,had to take power out, now when turning on just a black screen no sounds, no bios, nothing ,i downloaded the update from the lenovo website and started the bios flash on about block 7 or 17 the laptop froze for a hour so i decided to pull the power out, on booting the laptop doesnt get past post, just a black screen ive tried phoenix bios recovery but i dont know if im doing it right ?
There's a lot threads about this kind of issue.
Please, use the search form.
Thanks.
Best regards.
IPnaSh
First Spanish Community Guru - Colaborador ad honorem
Maybe you are looking for
-
Good morning. Can anyone point me to a link on Apple's site for Mac mini monitor compatibility? I'm considering purchasing an Intel Mac mini because I have a monitor that is large and a little old but excellent. It's the ViewSonic CRT PS790 with a 15
-
Is there a way to display folders differently in the same section?
I'm trying to change the view options in my folders, so that the subfolders in one folder don't display in the same way as the main folder. For instance, I'd like my music folder to display the artists with medium size icons, but when I click into an
-
Can't get layer with effects from photoshop into fcp
I imported a psd into fcp 2 but it doesn't have the effects applied to it . it is the basic element only with no effects the element was warped text Vic mac pro Mac OS X (10.4.9) mac pro Mac OS X (10.4.9)
-
AUTO-CREATE LONG LIST BY USING CRITERIAS FOR APPLICANTS
Hi, By defining criterias, is it possible to automatically create the long list on the system for suited applicants? Thanks in advance
-
Hi. Firefox 22 on my PC is not allowing uploads and other functions.
Hi I have uploaded Firefox 22 on my laptop but in various websites; i.e., shipspotting.com, You Tube, My Yahoo, etc. I am unable to utilize the upload functions on those websites and the bookmarks function is not working properly in the My Yahoo webs