Switching from Sun monitor output to VGA ourput.

How do I change the primary display output on a Solaris box from the Solaris video output to the VGA video output?
I have a KVM feeding a LCD monitor and I have to change the setting on the monitor from VDI to subd when I go from Solaris to the Windows boxes. I have a VDI cable that currently connects directly from the Solaris box whereas all the rest of my systems connect via the VGA from the KVM.

Similar Messages

Glitch in Audio when switching from Source Monitor to timeine in PPro

I am running a nMP 3ghz 8-core, 16gb ram, D700's, on osx 10.10. PProCC is 8.2.0 (65) Build. It is the most up to date version on CC. I also have a Focusrite Scarlette 2i2 for my Audio interface. This is where I'm having the issue. When I playback a clip in the source monitor, then go to play something in the timeline I get a weird 2 second delay with 2 pop's in my speakers, the lights on the XLR gain knobs on the focusrite audio interface flash twice in sync with the audio pops, then the timeline will play. And if I now go to play something in the source monitor coming from the timeline it does the same thing, 2 seconds, pops, lights then it plays. But if I stop and start the clip in either the source monitor or timeline without switching between, it plays fine. Only switching between the source monitor and the timeline. I have tried numerous things in the ASIO settings but nothing seems to get rid of this glitch and it drives me and my clients insane because it does it every single time I switch between the two. HELP!

Cam, I have this exact same problem. I plan on sending out some emails to hopefully find a solution, but I thought I would check here quick. Did you ever find an answer to your question elsewhere?

Lose Dock when switching from External monitor

When I disconnect my external monitor and open my MacBook monitor the Dock is not visible except when I cursor over the Dock area it's starts to reappear? It's very strange.

I think the problem revolves around the change of resolution when switching back. Because my Windows for Safari are out of whack too. So I am thinking the Dock is position wrong at first.

PDFs not displaying properly when switching from multiple monitors to single screen

OK, here’s one I can’t find online anywhere. When I am at home I use a second monitor on my Macbook. Adobe reader works just fine opening files and displaying them, but if I disconnect the monitor and just go to the single laptop screen, adobe will no longer display the pdf file. Reader stays open and will display the toolbar from the file or files I had open, but it won’t display the actual documents. I have to quit reader and re-open it in order to display my files correctly.
Any ideas?

OK, here’s one I can’t find online anywhere. When I am at home I use a second monitor on my Macbook. Adobe reader works just fine opening files and displaying them, but if I disconnect the monitor and just go to the single laptop screen, adobe will no longer display the pdf file. Reader stays open and will display the toolbar from the file or files I had open, but it won’t display the actual documents. I have to quit reader and re-open it in order to display my files correctly.
Any ideas?

Switching from apple monitor to another

My mac screen is cracked and I want to use another monitor

Connect and external display then. Did you have a question?
http://support.apple.com/kb/ht5019

Lost full hd resolution output via VGA to monitor

Hello Everyone,
I was happily recieving full hd output from my macbook to my monitor via a VGA cable. I then disconnected the VGA cable (and the connected mini-displayport to VGA adaptor) from my macbook. I then plugged them back in as before. However, this time I can no longer select 1920*1080 (Full Hd) from my macbook's display settings for my external monitor. What went wrong?
Thank you

Not sure; you may try and check all settings after a reset
of the System Management Controller (SMC) to see if
that makes a difference. Or spend some time with a whole
pile of things, as some of us said in the early Mac OS X
days, throw the kitchen sink at it.
Boot into SafeBook mode, repair disk permissions, check
or verify the hard drive, get a coffee. Check the wires to
see if one of them went on permanent vacation, & so on.
Looking at 1:14AM here, so not sticking around...
Good luck with taming gremlins!

Did anyone get reasonable output from -Xrunhprof:monitor=y?

Hi folks,
I'm trying to profile on monitor contention. But whatever combination of VM and switches I use the output remains meaningless, although there have to be monitor waits (see code below).
MONITOR DUMP BEGIN
MONITOR java.lang.ref.ReferenceQueue$Lock(24ae5178) unowned
     waiting to be notified: thread 2
MONITOR java.lang.ref.Reference$Lock(24ae5648) unowned
     waiting to be notified: thread 1
MONITOR DUMP END
MONITOR TIME BEGIN (total = 0 ms) Tue Mar 30 10:06:58 2004
MONITOR TIME END
OS is Windows 2000 Pro.
VM's used are Suns 1.4.1_01-b01 and 1.4.2_02-b03.
Switches used are "-Xrunhprof:monitor=y,depth=50" with different combinations of "thread=y|n", "cpu=times|samples" as well as "-Xint", "-Xcheck:jni", "-Xss1m" and "-Xmx256m".
Oh, and btw, if I use "cpu=samples" the VM crashes after about several hundred lines are printed to the console.
On exit I see something like this:
HPROF ERROR: thread local table NULL in method exit 0093D9F8
HPROF ERROR: thread local table NULL in method exit 0093D9F8
HPROF ERROR: class ID already in use
HPROF ERROR : stack underflow in method exit
HPROF ERROR : stack underflow in method exit
HPROF ERROR : stack underflow in method exit
Dumping contended monitor usage ... CPU usage by timing methods ... done.
Any ideas what's happening here? Thanks!
robert
Now here's the code if anyone is interested:
package threads;
public class ThreadLockProfileTest implements Runnable {
    // class level
    private static final Object[] LOCKS = {"Lock1", "Lock2"};
    public static void main( String[] args ) throws InterruptedException {
        Thread[] threads = new Thread[30];
        // create
        System.out.println( "Creating" );
        for ( int i = 0; i < threads.length; ++i ) {
            ThreadLockProfileTest t = new ThreadLockProfileTest( LOCKS[i % LOCKS.length], "T" + i, 10 );
            threads[i] = new Thread( t );
        // start
        System.out.println( "Starting" );
        for ( int i = 0; i < threads.length; ++i ) {
            threads.start();
// wait for exit
System.out.println( "Waiting" );
for ( int i = 0; i < threads.length; ++i ) {
try {
threads[i].join();
catch ( InterruptedException e ) {
System.err.println( "Interrupted during wait for " + threads[i] );
// done
System.out.println( "Exiting" );
// instance level
private final Object lock;
private String label;
private int number;
ThreadLockProfileTest( Object lock, String label, int number ) {
this.lock = lock;
this.label = label;
this.number = number;
public void run() {
message( "Started" );
for ( int i = 0; i < number; ++i ) {
test();
message( "Finished" );
private void test() {
message( "Entering" );
synchronized ( lock ) {
message( "Entered" );
// spend some time here
StringBuffer sb = new StringBuffer();
for ( int i = 0; i < 10000; ++i ) {
sb.append( "x" );
message( "About to leave (" + sb.length() + ")" );
message( "Leaving" );
private void message( String msg ) {
System.out.println( label + ":" + lock + ":" + msg );

Odd, which version did you test? Can't determine at the moment, but I downloaded it mid last week, so it should be quite current.
I do use jmp often on quite big projects (~4000 own
classes ~300 000 lines of own code, also have a bunch
of other jar files). Nowdays it only crashes very
rarely for me.
Also given the right flags it is really fast. What OS are you on? Maybe just the Windows version is instable. Also it could be caused by WinGTK...
Jmp can tell you how much monitor contention you have
although that information is only summarized per
thread (see
http://www.khelekore.org/jmp/sc-threads-0.30.png).
Oh, I didn't see that one. Although I've to admit I didn't bother to dig further since the frequent crashes turned me off...
If you want the monitor contention shown in other
ways, you can hack the code or ask for a feature...
Anyway why do you need to measure contention? That is
something that I do not hear much about. Since I do
develop a profiler I have some ideas of what other
people try to do when profiling... Well, high measures for contention signal that there is a concurrency issue, i.e., some concurrently accessed resource is a bottleneck. Throughput of the whole application can be improved if those contention times can be reduced - unless there are other bounds to the throughput. IMHO this is not too specialized, but maybe not many people do thorough profiling let alone thread profiling.
regards
robert

Forms behavior differences switching from JInit to Sun's Plug-in?

What differences are there in Forms behavior after switching from JInit v 1.3.1.26 to Sun's 1.4.2_06 plugin?
We are running Oracle Forms v 10.1.2.2.0, Internet Application Server v 10.1.2, and IE 7.
Thanks
KenV

The biggest differences I have seen has to do with fonts and space between lines.
If you have a tightly built form where prompts and items are close together, they might be aligned slightly differently.
Prompts for column headings that may be on two lines might have more space or less space between the two lines.
In LOVs, the lines are farther apart or closer together.
Same goes for fields where word wrap is allowed (where text in the item displays on more than one line).

Switching from MSJVM to Sun Virtual machine

I am a developer who wants to switch from the old MSJVM to the Sun virtual machine, I wanted to know what are the differences between them?
What does one has more than the other?(besides support).
Also i have heard that my software might not be totally compatible with the Sun's JVM. I have compiledin 1.3
Thank you.

If in Java code written for MSJVM you do not use MS Java specific classes then you can compile your code with any SUN Java compiler. MS Java is the same as SUN Java ver.1.1.
While writing Java code MSJava I used pure AWT classes instread of MS specific GUI classes. Then this code I recompiled with SUN Java without changes.

I am a brand new mac user...trying to figure out how to switch from the Mac Pro screen to my external monitor. Appreciate any help.

am a brand new mac user...trying to figure out how to switch from the Mac Pro screen to my external monitor. Appreciate any help. thanks

In Finder... goto Help... In the Search Window type in Displays...
Lots of Useful Information there...
You may find these Links Useful too:
http://www.apple.com/support/mac101/
http://www.apple.com/support/macbookpro/
Cheers,

Switching from MS VM to Sun VM on an IIS web server.

Good day,
I can easily switch back and forth from Sun's JRE to MS VM on my browser, no problem there.
However, what is the procedure to indicate to IIS to use the Sun's VM instead of the MS one ?
I've search different forums, but couldn't find precise information.
Could not find anything informative on MS site either.
Regards.

Steve,
To summarize, here are the main lines.
Let say I have a class, which has few methods in it and I want to use these methods to process some information via an ASP page for instance.
1) Given the following code as an example :
// ============================================
import java.io.*;
public class javacomp {
public String Diagnose() {
return "Diagnose() - javacomp : Class accessed successfully !";
}2) I compile it, then put the resulting class in the TrustLib sub-directory of the server, normally "%system%\java\trustblib".
(The compile was done using jsdk v1.4.2_01 with "-target 1.1")
3) Once the class is in place, and IIS re-cycled if the class was re-compiled between accesses, I then invoke the method(s) via an ASP page using VBScript.
<%
Set javaObject = GetObject("java:javacomp")
strResult = javaObject.Diagnose()
set javaObject=nothing
Response.Write strResult & "<br><br>"
%>On my Win98SE/PWS based computer, this is working just fine. When I tried it on a Win2K Server box, it worked fine as well. I asked my web hosting service technician to put it on their system, they aggreed, however it doesn't work, but the reason is still unknown to me.
With the actual setup, IIS or PWS are using the default MS VM to run the "servlet", which is the VM installed my MS JAVA SDK v4.0. MS VM supports only Java 1.1 classes, explaining why the methods are working as planned.
The actual class I want to put in place, is a class with methods allowing to zip/unzip gzip/ungzip files. Version 1.4 introduced the "setModifiedDate()" which I want to use when extracting or decompressing the files from the archive files. The thing is that a server Java VM v1.4 is necessary to run the code, since the "setModifiedDate()" is not available in earlier versions.
As far as adding packages like JRun or Tomcat, this could induce unnecessary overhead. Also, the Win2K box I'm using for test purposes, is not a computer assigned to host sites, so doing tests with only one site is irrevelant for performance evaluations.
On the other hand, the box where the "final" site resides on has roughly 460 sites on it, so the addition of any additional element needs to be weighted carefully, not to stay very difficult to justify for 1 user out of 460. Re-cycling the whole box and disabling JRun or Tomcat because of the overhead during the middle of the day would not be an appreciated action either.
The approach I would suggest to the web hosting service is to install the latest Java VM machine from Sun, and use it as the one by default for the server. Before doing so, I want to do tests on the server for which I have access to as an administrator, preventing chaos at the web hosting place in case something does not go as expected.
Having a procedure that can somehow automate/minimize the delays when switching between the VM machines would a need be necessary, would be much more appreciated than a "...you can try this, or that..." approach.
Also, having the web hosting service to install JRun or Tomcat to accomodate my needs is less likely to happen, however updating the server's VM could be something possible, knowing that MS will no longer update their's, which haven't been updated/optimized for a while anyhow.
Hoping this is clarifying my idea.
Regards.

Huge debugging binaries after switching from C++ Sun Studio 11 to 12u1

Hello
I changed the compiler in our C++ project from Sun Studio 11 to Sun Studio 12u1 (12u3 is currently not available).
The only change on the command line I had to do was replacing -xarch=v9 with -m64.
The command line now is "CC -c -g -features=rtti -mt -KPIC -w -staticlib=Cstd,Crun -m64 ...".
Our static libraries are now 50% bigger, the executables are 10x bigger (200 MB to now 2 GB!!!).
This also affected the debugger sessions, they are slow and the print statement only produces internal errors.
I think this is due to the size of the binaries.
Please help to reduce the binary size.
Best regards
Hans

The debug data format changed between Studio 11 and 12u1 from Sun stabs to the industry-standard dwarf format. (The Studio 12u1 C++ Users Guide is incorrect where it says stabs is the default format.)
The change in debug format has two consequences:
1. Debug data is typically 10-15% larger, due to increased information about the program being available (a major reason for the change).
2. Whereas stabs data resides in the .o files with only index information in the executable program, all the dwarf data is copied into the executable. With dwarf, you can fully debug the program without access to the .o files that make up the program.
To verify this reason for the larger binaries, try building your program using Studio 11, adding the -xs option. This option causes the stabs to be copied into the executable program. You should find the binaries are similar in size compared to building with Studio 12u1. If this is not the case, we'll need to dig deeper.
You can revert to using stabs by adding the option -xdebugformat=stabs to every compile and link command (CC or cc).
In a future version of Studio, we plan to provide an option to leave dwarf data in the .o files with only index information in the executable, so that you can have a smaller executable when you don't mind requiring access to the .o files in order to debug.
By the way, we do not recommend static linking of libCstd and libCrun. Unless you have a particular reason for linking the static libraries, we recommend the default dynamic linking.

Trying to switch from nvidia to nouveau; startx freezes system

I'm having high cpu issues, possibly related to nvidia and want to switch to nouveau to test this out. I followed the Arch Wiki for nouveau but am having issues being able to startx. My process:
- Logout of openbox
- Remove nvidia stuff:
# pacman -Rsc nvidia nvidia-utils opencl-nvidia
# pacman -S xf86-video-nouveau
Installing nouveau also prompted the removal of nvidia-libgl and replaced it with mesa-libgl, as well as the installation of nouvea-dri.
- Removed my existing monitor config file:
# mv /etc/X11/xorg.conf.d/10-monitor.conf /etc/X11/xorg.conf.d/10-monitor.conf.bk
- Verified that I have no modeset options specified to kernel options via syslinux, nor blacklisting of nouveau in /etc/modprobe.d/ files.
$ cat /etc/modprobe.d/modprobe.conf
# /etc/modprobe.d/modprobe.conf
blacklist uvcvideo
blacklist pcspkr
$ ls /etc/X11/xorg.conf.d/
10-evdev.conf 10-monitor.conf.bk 10-quirks.conf 50-synaptics.conf
Nothing related to monitors or screens in 10-evdev, 10-quirks or 50-synaptics, and the 10-monitor.conf.bk file has the following contents (just in the event it *is* picked up by Xorg):
$ cat /etc/X11/xorg.conf.d/10-monitor.conf.bk
Section "Monitor"
Identifier "Monitor0"
ModelName "LGD"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
# Option "Enable" "True"
# Option "PreferredMode" "1600x900"
EndSection
Section "Device"
Identifier "Device0"
Driver "nouveau"
# Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "Quadro FX 1800M"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1600x900"
EndSubSection
# Option "SLI" "Auto"
# Option "AddARGBGLXVisuals" "True"
EndSection
- Reboot
I am at work and have my computer docked. Nouveau seemed to be active, observed by the fact that it auto-switched to KMS during boot. It also picked up my external monitor, which was off, and started duplicating the display on my external monitor and laptop during text boot (which nvidia does not do). The laptop had what I'll call "screen artifacts" on the lower right (white lines, jumbled pixels) after switching to KMS, but not a huge deal. I went to startx and it just froze after spitting out the various initialization lines. I have to hard kill and reboot. From there, I uninstall nouveau, re-install nvidia (which replaces mesa-libgl with nvidia-libgl), and reboot again to a working system.
Any suggestions?
Last edited by jwhendy (2013-10-24 16:36:15)

Here's the recent Xorg.log:
X.Org X Server 1.14.3
Release Date: 2013-09-12
[ 102.581] X Protocol Version 11, Revision 0
[ 102.581] Build Operating System: Linux 3.11.1-1-ARCH x86_64
[ 102.581] Current Operating System: Linux bigBang 3.11.6-1-ARCH #1 SMP PREEMPT Fri Oct 18 23:22:36 CEST 2013 x86_64
[ 102.581] Kernel command line: root=/dev/mapper/root cryptdevice=/dev/sda3:root ro initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux
[ 102.581] Build Date: 08 October 2013 08:48:10PM
[ 102.581]
[ 102.581] Current version of pixman: 0.30.2
[ 102.581] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 102.581] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 102.582] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 24 19:46:30 2013
[ 102.599] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 102.618] (==) No Layout section. Using the first Screen section.
[ 102.618] (==) No screen section available. Using defaults.
[ 102.618] (**) |-->Screen "Default Screen Section" (0)
[ 102.618] (**) | |-->Monitor "<default monitor>"
[ 102.618] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 102.618] (==) Automatically adding devices
[ 102.618] (==) Automatically enabling devices
[ 102.618] (==) Automatically adding GPU devices
[ 102.666] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 102.666] Entry deleted from font path.
[ 102.666] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 102.667] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 102.667] Entry deleted from font path.
[ 102.667] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 102.667] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/
[ 102.667] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 102.667] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 102.667] (II) Loader magic: 0x7fdc20
[ 102.667] (II) Module ABI versions:
[ 102.667] X.Org ANSI C Emulation: 0.4
[ 102.667] X.Org Video Driver: 14.1
[ 102.667] X.Org XInput driver : 19.1
[ 102.667] X.Org Server Extension : 7.0
[ 102.667] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 102.671] (--) PCI:*(0:1:0:0) 10de:0cbc:103c:1521 rev 162, Mem @ 0xd2000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x00005000/128, BIOS @ 0x????????/524288
[ 102.671] Initializing built-in extension Generic Event Extension
[ 102.672] Initializing built-in extension SHAPE
[ 102.672] Initializing built-in extension MIT-SHM
[ 102.672] Initializing built-in extension XInputExtension
[ 102.672] Initializing built-in extension XTEST
[ 102.672] Initializing built-in extension BIG-REQUESTS
[ 102.672] Initializing built-in extension SYNC
[ 102.672] Initializing built-in extension XKEYBOARD
[ 102.673] Initializing built-in extension XC-MISC
[ 102.674] Initializing built-in extension SECURITY
[ 102.675] Initializing built-in extension XINERAMA
[ 102.676] Initializing built-in extension XFIXES
[ 102.677] Initializing built-in extension RENDER
[ 102.678] Initializing built-in extension RANDR
[ 102.679] Initializing built-in extension COMPOSITE
[ 102.680] Initializing built-in extension DAMAGE
[ 102.681] Initializing built-in extension MIT-SCREEN-SAVER
[ 102.682] Initializing built-in extension DOUBLE-BUFFER
[ 102.683] Initializing built-in extension RECORD
[ 102.684] Initializing built-in extension DPMS
[ 102.684] Initializing built-in extension X-Resource
[ 102.685] Initializing built-in extension XVideo
[ 102.686] Initializing built-in extension XVideo-MotionCompensation
[ 102.687] Initializing built-in extension XFree86-VidModeExtension
[ 102.688] Initializing built-in extension XFree86-DGA
[ 102.689] Initializing built-in extension XFree86-DRI
[ 102.690] Initializing built-in extension DRI2
[ 102.690] (II) LoadModule: "glx"
[ 102.691] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 102.719] (II) Module glx: vendor="X.Org Foundation"
[ 102.719] compiled for 1.14.3, module version = 1.0.0
[ 102.719] ABI class: X.Org Server Extension, version 7.0
[ 102.719] (==) AIGLX enabled
[ 102.721] Loading extension GLX
[ 102.721] (==) Matched nouveau as autoconfigured driver 0
[ 102.721] (==) Matched nvidia as autoconfigured driver 1
[ 102.721] (==) Matched nv as autoconfigured driver 2
[ 102.721] (==) Matched nouveau as autoconfigured driver 3
[ 102.721] (==) Matched nvidia as autoconfigured driver 4
[ 102.721] (==) Matched nv as autoconfigured driver 5
[ 102.721] (==) Matched vesa as autoconfigured driver 6
[ 102.721] (==) Matched modesetting as autoconfigured driver 7
[ 102.721] (==) Matched fbdev as autoconfigured driver 8
[ 102.721] (==) Assigned the driver to the xf86ConfigLayout
[ 102.721] (II) LoadModule: "nouveau"
[ 102.721] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[ 102.751] (II) Module nouveau: vendor="X.Org Foundation"
[ 102.751] compiled for 1.14.2, module version = 1.0.9
[ 102.751] Module class: X.Org Video Driver
[ 102.751] ABI class: X.Org Video Driver, version 14.1
[ 102.751] (II) LoadModule: "nvidia"
[ 102.765] (WW) Warning, couldn't open module nvidia
[ 102.765] (II) UnloadModule: "nvidia"
[ 102.765] (II) Unloading nvidia
[ 102.765] (EE) Failed to load module "nvidia" (module does not exist, 0)
[ 102.765] (II) LoadModule: "nv"
[ 102.765] (WW) Warning, couldn't open module nv
[ 102.765] (II) UnloadModule: "nv"
[ 102.765] (II) Unloading nv
[ 102.765] (EE) Failed to load module "nv" (module does not exist, 0)
[ 102.765] (II) LoadModule: "vesa"
[ 102.765] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 102.776] (II) Module vesa: vendor="X.Org Foundation"
[ 102.776] compiled for 1.14.0, module version = 2.3.2
[ 102.776] Module class: X.Org Video Driver
[ 102.776] ABI class: X.Org Video Driver, version 14.1
[ 102.776] (II) LoadModule: "modesetting"
[ 102.776] (WW) Warning, couldn't open module modesetting
[ 102.776] (II) UnloadModule: "modesetting"
[ 102.776] (II) Unloading modesetting
[ 102.776] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 102.776] (II) LoadModule: "fbdev"
[ 102.776] (WW) Warning, couldn't open module fbdev
[ 102.776] (II) UnloadModule: "fbdev"
[ 102.776] (II) Unloading fbdev
[ 102.776] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 102.776] (II) NOUVEAU driver
[ 102.776] (II) NOUVEAU driver for NVIDIA chipset families :
[ 102.776] RIVA TNT (NV04)
[ 102.776] RIVA TNT2 (NV05)
[ 102.776] GeForce 256 (NV10)
[ 102.776] GeForce 2 (NV11, NV15)
[ 102.776] GeForce 4MX (NV17, NV18)
[ 102.776] GeForce 3 (NV20)
[ 102.776] GeForce 4Ti (NV25, NV28)
[ 102.776] GeForce FX (NV3x)
[ 102.776] GeForce 6 (NV4x)
[ 102.776] GeForce 7 (G7x)
[ 102.776] GeForce 8 (G8x)
[ 102.776] GeForce GTX 200 (NVA0)
[ 102.776] GeForce GTX 400 (NVC0)
[ 102.776] (II) VESA: driver for VESA chipsets: vesa
[ 102.776] (++) using VT number 1
[ 102.776] (II) [drm] nouveau interface version: 1.1.1
[ 102.777] (WW) Falling back to old probe method for vesa
[ 102.777] (II) Loading sub module "dri2"
[ 102.777] (II) LoadModule: "dri2"
[ 102.777] (II) Module "dri2" already built-in
[ 102.777] (--) NOUVEAU(0): Chipset: "NVIDIA NVA3"
[ 102.777] (II) NOUVEAU(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 102.777] (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
[ 102.777] (==) NOUVEAU(0): RGB weight 888
[ 102.777] (==) NOUVEAU(0): Default visual is TrueColor
[ 102.777] (==) NOUVEAU(0): Using HW cursor
[ 102.777] (==) NOUVEAU(0): GLX sync to VBlank disabled.
[ 102.777] (==) NOUVEAU(0): Page flipping enabled
[ 102.777] (==) NOUVEAU(0): Swap limit set to 2 [Max allowed 2]
[ 102.845] (II) NOUVEAU(0): Output LVDS-1 has no monitor section
[ 102.950] (II) NOUVEAU(0): Output DP-1 has no monitor section
[ 103.056] (II) NOUVEAU(0): Output DP-2 has no monitor section
[ 103.056] (II) NOUVEAU(0): Output eDP-1 has no monitor section
[ 103.163] (II) NOUVEAU(0): Output DP-3 has no monitor section
[ 103.184] (II) NOUVEAU(0): Output VGA-1 has no monitor section
[ 103.211] (II) NOUVEAU(0): EDID for output LVDS-1
[ 103.211] (II) NOUVEAU(0): Manufacturer: CMO Model: 1595 Serial#: 0
[ 103.211] (II) NOUVEAU(0): Year: 2009 Week: 12
[ 103.211] (II) NOUVEAU(0): EDID Version: 1.3
[ 103.211] (II) NOUVEAU(0): Digital Display Input
[ 103.211] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 34 vert.: 19
[ 103.211] (II) NOUVEAU(0): Gamma: 2.20
[ 103.211] (II) NOUVEAU(0): No DPMS capabilities specified
[ 103.211] (II) NOUVEAU(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 103.211] (II) NOUVEAU(0): First detailed timing is preferred mode
[ 103.211] (II) NOUVEAU(0): redX: 0.610 redY: 0.343 greenX: 0.342 greenY: 0.581
[ 103.211] (II) NOUVEAU(0): blueX: 0.162 blueY: 0.083 whiteX: 0.313 whiteY: 0.329
[ 103.211] (II) NOUVEAU(0): Manufacturer's mask: 0
[ 103.211] (II) NOUVEAU(0): Supported detailed timing:
[ 103.211] (II) NOUVEAU(0): clock: 107.8 MHz Image Size: 344 x 193 mm
[ 103.211] (II) NOUVEAU(0): h_active: 1600 h_sync: 1626 h_sync_end 1686 h_blank_end 1892 h_border: 0
[ 103.211] (II) NOUVEAU(0): v_active: 900 v_sync: 909 v_sync_end 919 v_blanking: 949 v_border: 0
[ 103.212] (II) NOUVEAU(0): N156O6-L01
[ 103.212] (II) NOUVEAU(0): CMO
[ 103.212] (II) NOUVEAU(0): N156O6-L01
[ 103.212] (II) NOUVEAU(0): EDID (in hex):
[ 103.212] (II) NOUVEAU(0): 00ffffffffffff000daf951500000000
[ 103.212] (II) NOUVEAU(0): 0c130103802213780a7b959c57579429
[ 103.212] (II) NOUVEAU(0): 15505400000001010101010101010101
[ 103.212] (II) NOUVEAU(0): 0101010101011c2a4024618431301a3c
[ 103.212] (II) NOUVEAU(0): 9a0058c110000018000000fe004e3135
[ 103.212] (II) NOUVEAU(0): 364f362d4c30310a2020000000fe0043
[ 103.212] (II) NOUVEAU(0): 4d4f0a202020202020202020000000fe
[ 103.212] (II) NOUVEAU(0): 004e3135364f362d4c30310a2020001c
[ 103.212] (II) NOUVEAU(0): Printing probed modes for output LVDS-1
[ 103.212] (II) NOUVEAU(0): Modeline "1600x900"x60.0 107.80 1600 1626 1686 1892 900 909 919 949 -hsync -vsync (57.0 kHz eP)
[ 103.212] (II) NOUVEAU(0): Modeline "1152x864"x60.0 81.75 1152 1216 1336 1520 864 867 871 897 -hsync +vsync (53.8 kHz e)
[ 103.212] (II) NOUVEAU(0): Modeline "1024x768"x59.9 63.50 1024 1072 1176 1328 768 771 775 798 -hsync +vsync (47.8 kHz e)
[ 103.212] (II) NOUVEAU(0): Modeline "800x600"x59.9 38.25 800 832 912 1024 600 603 607 624 -hsync +vsync (37.4 kHz e)
[ 103.212] (II) NOUVEAU(0): Modeline "640x480"x59.4 23.75 640 664 720 800 480 483 487 500 -hsync +vsync (29.7 kHz e)
[ 103.212] (II) NOUVEAU(0): Modeline "720x400"x59.6 22.25 720 744 808 896 400 403 413 417 -hsync +vsync (24.8 kHz e)
[ 103.212] (II) NOUVEAU(0): Modeline "640x400"x60.0 20.00 640 664 720 800 400 403 409 417 -hsync +vsync (25.0 kHz e)
[ 103.212] (II) NOUVEAU(0): Modeline "640x350"x59.8 17.50 640 664 720 800 350 353 363 366 -hsync +vsync (21.9 kHz e)
[ 103.316] (II) NOUVEAU(0): EDID for output DP-1
[ 103.423] (II) NOUVEAU(0): EDID for output DP-2
[ 103.423] (II) NOUVEAU(0): EDID for output eDP-1
[ 103.530] (II) NOUVEAU(0): EDID for output DP-3
[ 103.550] (II) NOUVEAU(0): EDID for output VGA-1
[ 103.550] (II) NOUVEAU(0): Output LVDS-1 connected
[ 103.550] (II) NOUVEAU(0): Output DP-1 disconnected
[ 103.550] (II) NOUVEAU(0): Output DP-2 disconnected
[ 103.551] (II) NOUVEAU(0): Output eDP-1 disconnected
[ 103.551] (II) NOUVEAU(0): Output DP-3 disconnected
[ 103.551] (II) NOUVEAU(0): Output VGA-1 disconnected
[ 103.551] (II) NOUVEAU(0): Using exact sizes for initial modes
[ 103.551] (II) NOUVEAU(0): Output LVDS-1 using initial mode 1600x900
[ 103.551] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 103.551] (--) NOUVEAU(0): Virtual size is 1600x900 (pitch 0)
[ 103.551] (**) NOUVEAU(0): Driver mode "1600x900": 107.8 MHz (scaled from 0.0 MHz), 57.0 kHz, 60.0 Hz
[ 103.551] (II) NOUVEAU(0): Modeline "1600x900"x60.0 107.80 1600 1626 1686 1892 900 909 919 949 -hsync -vsync (57.0 kHz eP)
[ 103.551] (**) NOUVEAU(0): Driver mode "1152x864": 81.8 MHz (scaled from 0.0 MHz), 53.8 kHz, 60.0 Hz
[ 103.551] (II) NOUVEAU(0): Modeline "1152x864"x60.0 81.75 1152 1216 1336 1520 864 867 871 897 -hsync +vsync (53.8 kHz e)
[ 103.551] (**) NOUVEAU(0): Driver mode "1024x768": 63.5 MHz (scaled from 0.0 MHz), 47.8 kHz, 59.9 Hz
[ 103.551] (II) NOUVEAU(0): Modeline "1024x768"x59.9 63.50 1024 1072 1176 1328 768 771 775 798 -hsync +vsync (47.8 kHz e)
[ 103.551] (**) NOUVEAU(0): Driver mode "800x600": 38.2 MHz (scaled from 0.0 MHz), 37.4 kHz, 59.9 Hz
[ 103.551] (II) NOUVEAU(0): Modeline "800x600"x59.9 38.25 800 832 912 1024 600 603 607 624 -hsync +vsync (37.4 kHz e)
[ 103.551] (**) NOUVEAU(0): Driver mode "640x480": 23.8 MHz (scaled from 0.0 MHz), 29.7 kHz, 59.4 Hz
[ 103.551] (II) NOUVEAU(0): Modeline "640x480"x59.4 23.75 640 664 720 800 480 483 487 500 -hsync +vsync (29.7 kHz e)
[ 103.551] (**) NOUVEAU(0): Driver mode "720x400": 22.2 MHz (scaled from 0.0 MHz), 24.8 kHz, 59.6 Hz
[ 103.551] (II) NOUVEAU(0): Modeline "720x400"x59.6 22.25 720 744 808 896 400 403 413 417 -hsync +vsync (24.8 kHz e)
[ 103.551] (**) NOUVEAU(0): Driver mode "640x400": 20.0 MHz (scaled from 0.0 MHz), 25.0 kHz, 60.0 Hz
[ 103.551] (II) NOUVEAU(0): Modeline "640x400"x60.0 20.00 640 664 720 800 400 403 409 417 -hsync +vsync (25.0 kHz e)
[ 103.551] (**) NOUVEAU(0): Driver mode "640x350": 17.5 MHz (scaled from 0.0 MHz), 21.9 kHz, 59.8 Hz
[ 103.551] (II) NOUVEAU(0): Modeline "640x350"x59.8 17.50 640 664 720 800 350 353 363 366 -hsync +vsync (21.9 kHz e)
[ 103.551] (==) NOUVEAU(0): DPI set to (96, 96)
[ 103.551] (II) Loading sub module "fb"
[ 103.551] (II) LoadModule: "fb"
[ 103.551] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 105.504] (II) Module fb: vendor="X.Org Foundation"
[ 105.504] compiled for 1.14.3, module version = 1.0.0
[ 105.504] ABI class: X.Org ANSI C Emulation, version 0.4
[ 105.504] (II) Loading sub module "exa"
[ 105.504] (II) LoadModule: "exa"
[ 105.504] (II) Loading /usr/lib/xorg/modules/libexa.so
[ 105.508] (II) Module exa: vendor="X.Org Foundation"
[ 105.508] compiled for 1.14.3, module version = 2.6.0
[ 105.508] ABI class: X.Org Video Driver, version 14.1
[ 105.508] (II) Loading sub module "shadowfb"
[ 105.508] (II) LoadModule: "shadowfb"
[ 105.508] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
[ 105.518] (II) Module shadowfb: vendor="X.Org Foundation"
[ 105.518] compiled for 1.14.3, module version = 1.0.0
[ 105.518] ABI class: X.Org ANSI C Emulation, version 0.4
[ 105.518] (II) UnloadModule: "vesa"
[ 105.518] (II) Unloading vesa
[ 105.518] (--) Depth 24 pixmap format is 32 bpp
[ 105.521] (II) NOUVEAU(0): Opened GPU channel 0
[ 105.547] (II) NOUVEAU(0): [DRI2] Setup complete
[ 105.547] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau
[ 105.547] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau
[ 108.224] (II) EXA(0): Driver allocated offscreen pixmaps
[ 108.224] (II) EXA(0): Driver registered support for the following operations:
[ 108.224] (II) Solid
[ 108.224] (II) Copy
[ 108.224] (II) Composite (RENDER acceleration)
[ 108.224] (II) UploadToScreen
[ 108.224] (II) DownloadFromScreen
[ 108.224] (==) NOUVEAU(0): Backing store disabled
[ 108.224] (==) NOUVEAU(0): Silken mouse enabled
[ 108.226] (II) NOUVEAU(0): [XvMC] Associated with Nouveau GeForce 8/9 Textured Video.
[ 108.226] (II) NOUVEAU(0): [XvMC] Extension initialized.
[ 108.226] (==) NOUVEAU(0): DPMS enabled
[ 108.226] (II) NOUVEAU(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 108.228] (--) RandR disabled
[ 142.503] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 142.503] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 142.504] (II) AIGLX: enabled GLX_ARB_create_context
[ 142.504] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 142.504] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 142.504] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 142.504] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 142.505] (II) AIGLX: Loaded and initialized nouveau
[ 142.505] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 159.503] (II) NOUVEAU(0): NVEnterVT is called.
[ 159.532] (II) NOUVEAU(0): Setting screen physical size to 423 x 238
[ 159.532] resize called 1600 900
[ 160.324] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[ 160.324] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 160.324] (II) LoadModule: "evdev"
[ 160.324] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 160.355] (II) Module evdev: vendor="X.Org Foundation"
[ 160.355] compiled for 1.14.3, module version = 2.8.2
[ 160.355] Module class: X.Org XInput Driver
[ 160.355] ABI class: X.Org XInput driver, version 19.1
[ 160.355] (II) Using input driver 'evdev' for 'Power Button'
[ 160.355] (**) Power Button: always reports core events
[ 160.355] (**) evdev: Power Button: Device: "/dev/input/event3"
[ 160.355] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 160.355] (--) evdev: Power Button: Found keys
[ 160.355] (II) evdev: Power Button: Configuring as keyboard
[ 160.355] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
[ 160.355] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 160.355] (**) Option "xkb_rules" "evdev"
[ 160.355] (**) Option "xkb_model" "pc104"
[ 160.355] (**) Option "xkb_layout" "us"
[ 160.392] (II) config/udev: Adding input device Video Bus (/dev/input/event4)
[ 160.392] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 160.392] (II) Using input driver 'evdev' for 'Video Bus'
[ 160.392] (**) Video Bus: always reports core events
[ 160.392] (**) evdev: Video Bus: Device: "/dev/input/event4"
[ 160.392] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 160.392] (--) evdev: Video Bus: Found keys
[ 160.392] (II) evdev: Video Bus: Configuring as keyboard
[ 160.392] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:03/LNXVIDEO:00/input/input4/event4"
[ 160.392] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 160.392] (**) Option "xkb_rules" "evdev"
[ 160.392] (**) Option "xkb_model" "pc104"
[ 160.393] (**) Option "xkb_layout" "us"
[ 160.393] (II) config/udev: Adding input device Lid Switch (/dev/input/event2)
[ 160.393] (II) No input driver specified, ignoring this device.
[ 160.393] (II) This device may have been added with another device file.
[ 160.394] (II) config/udev: Adding input device Sleep Button (/dev/input/event1)
[ 160.394] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 160.394] (II) Using input driver 'evdev' for 'Sleep Button'
[ 160.394] (**) Sleep Button: always reports core events
[ 160.394] (**) evdev: Sleep Button: Device: "/dev/input/event1"
[ 160.394] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[ 160.394] (--) evdev: Sleep Button: Found keys
[ 160.394] (II) evdev: Sleep Button: Configuring as keyboard
[ 160.394] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input1/event1"
[ 160.394] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
[ 160.394] (**) Option "xkb_rules" "evdev"
[ 160.394] (**) Option "xkb_model" "pc104"
[ 160.394] (**) Option "xkb_layout" "us"
[ 160.395] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 160.396] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event13)
[ 160.396] (II) No input driver specified, ignoring this device.
[ 160.396] (II) This device may have been added with another device file.
[ 160.396] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event14)
[ 160.396] (II) No input driver specified, ignoring this device.
[ 160.396] (II) This device may have been added with another device file.
[ 160.397] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event15)
[ 160.397] (II) No input driver specified, ignoring this device.
[ 160.397] (II) This device may have been added with another device file.
[ 160.397] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event16)
[ 160.397] (II) No input driver specified, ignoring this device.
[ 160.397] (II) This device may have been added with another device file.
[ 160.398] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event6)
[ 160.398] (II) No input driver specified, ignoring this device.
[ 160.398] (II) This device may have been added with another device file.
[ 160.398] (II) config/udev: Adding input device HDA Intel MID Mic (/dev/input/event10)
[ 160.398] (II) No input driver specified, ignoring this device.
[ 160.398] (II) This device may have been added with another device file.
[ 160.399] (II) config/udev: Adding input device HDA Intel MID Dock Headphone (/dev/input/event7)
[ 160.399] (II) No input driver specified, ignoring this device.
[ 160.399] (II) This device may have been added with another device file.
[ 160.399] (II) config/udev: Adding input device HDA Intel MID Headphone (/dev/input/event8)
[ 160.399] (II) No input driver specified, ignoring this device.
[ 160.399] (II) This device may have been added with another device file.
[ 160.400] (II) config/udev: Adding input device HDA Intel MID Line (/dev/input/event9)
[ 160.400] (II) No input driver specified, ignoring this device.
[ 160.400] (II) This device may have been added with another device file.
[ 160.400] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 160.400] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 160.401] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 160.401] (**) AT Translated Set 2 keyboard: always reports core events
[ 160.401] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 160.401] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 160.401] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 160.401] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 160.401] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 160.401] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
[ 160.401] (**) Option "xkb_rules" "evdev"
[ 160.401] (**) Option "xkb_model" "pc104"
[ 160.401] (**) Option "xkb_layout" "us"
[ 160.402] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/event11)
[ 160.402] (**) PS/2 Generic Mouse: Applying InputClass "evdev pointer catchall"
[ 160.402] (II) Using input driver 'evdev' for 'PS/2 Generic Mouse'
[ 160.402] (**) PS/2 Generic Mouse: always reports core events
[ 160.402] (**) evdev: PS/2 Generic Mouse: Device: "/dev/input/event11"
[ 160.402] (--) evdev: PS/2 Generic Mouse: Vendor 0x2 Product 0x1
[ 160.402] (--) evdev: PS/2 Generic Mouse: Found 3 mouse buttons
[ 160.402] (--) evdev: PS/2 Generic Mouse: Found relative axes
[ 160.402] (--) evdev: PS/2 Generic Mouse: Found x and y relative axes
[ 160.402] (II) evdev: PS/2 Generic Mouse: Configuring as mouse
[ 160.402] (**) evdev: PS/2 Generic Mouse: YAxisMapping: buttons 4 and 5
[ 160.402] (**) evdev: PS/2 Generic Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 160.402] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input11/event11"
[ 160.402] (II) XINPUT: Adding extended input device "PS/2 Generic Mouse" (type: MOUSE, id 10)
[ 160.402] (II) evdev: PS/2 Generic Mouse: initialized for relative axes.
[ 160.402] (**) PS/2 Generic Mouse: (accel) keeping acceleration scheme 1
[ 160.403] (**) PS/2 Generic Mouse: (accel) acceleration profile 0
[ 160.403] (**) PS/2 Generic Mouse: (accel) acceleration factor: 2.000
[ 160.403] (**) PS/2 Generic Mouse: (accel) acceleration threshold: 4
[ 160.403] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/mouse0)
[ 160.403] (II) No input driver specified, ignoring this device.
[ 160.403] (II) This device may have been added with another device file.
[ 160.403] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event17)
[ 160.403] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 160.403] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 160.403] (II) LoadModule: "synaptics"
[ 160.403] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 160.415] (II) Module synaptics: vendor="X.Org Foundation"
[ 160.415] compiled for 1.14.1, module version = 1.7.1
[ 160.415] Module class: X.Org XInput Driver
[ 160.415] ABI class: X.Org XInput driver, version 19.1
[ 160.415] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[ 160.415] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 160.415] (**) Option "Device" "/dev/input/event17"
[ 160.503] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
[ 160.503] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5600 (res 57)
[ 160.503] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4884 (res 123)
[ 160.503] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 160.503] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[ 160.503] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right middle double triple
[ 160.503] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[ 160.503] (**) Option "VertScrollDelta" "250"
[ 160.503] (**) Option "VertTwoFingerScroll" "on"
[ 160.504] (**) Option "HorizTwoFingerScroll" "off"
[ 160.504] (**) Option "TapButton1" "1"
[ 160.504] (**) Option "TapButton2" "2"
[ 160.504] (**) Option "TapButton3" "3"
[ 160.504] (**) Option "CoastingSpeed" "0"
[ 160.504] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 160.504] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 160.530] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio4/input/input17/event17"
[ 160.530] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 11)
[ 160.530] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[ 160.530] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
[ 160.530] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.037
[ 160.531] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 160.531] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[ 160.531] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 160.531] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 160.531] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 160.531] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
[ 160.531] (II) No input driver specified, ignoring this device.
[ 160.531] (II) This device may have been added with another device file.
[ 160.532] (II) config/udev: Adding input device ST LIS3LV02DL Accelerometer (/dev/input/event5)
[ 160.532] (II) No input driver specified, ignoring this device.
[ 160.532] (II) This device may have been added with another device file.
[ 160.532] (II) config/udev: Adding input device ST LIS3LV02DL Accelerometer (/dev/input/js0)
[ 160.532] (II) No input driver specified, ignoring this device.
[ 160.532] (II) This device may have been added with another device file.
[ 160.533] (II) config/udev: Adding input device HP WMI hotkeys (/dev/input/event12)
[ 160.533] (**) HP WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[ 160.533] (II) Using input driver 'evdev' for 'HP WMI hotkeys'
[ 160.533] (**) HP WMI hotkeys: always reports core events
[ 160.533] (**) evdev: HP WMI hotkeys: Device: "/dev/input/event12"
[ 160.533] (--) evdev: HP WMI hotkeys: Vendor 0 Product 0
[ 160.533] (--) evdev: HP WMI hotkeys: Found keys
[ 160.533] (II) evdev: HP WMI hotkeys: Configuring as keyboard
[ 160.533] (**) Option "config_info" "udev:/sys/devices/virtual/input/input12/event12"
[ 160.533] (II) XINPUT: Adding extended input device "HP WMI hotkeys" (type: KEYBOARD, id 12)
[ 160.533] (**) Option "xkb_rules" "evdev"
[ 160.533] (**) Option "xkb_model" "pc104"
[ 160.533] (**) Option "xkb_layout" "us"
[ 164.083] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 164.083] (II) NOUVEAU(0): NVLeaveVT is called.
[ 181.123] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 181.123] (II) NOUVEAU(0): NVEnterVT is called.
[ 181.179] (II) NOUVEAU(0): EDID vendor "CMO", prod id 5525
[ 181.179] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 181.179] (II) NOUVEAU(0): Modeline "1600x900"x0.0 107.80 1600 1626 1686 1892 900 909 919 949 -hsync -vsync (57.0 kHz eP)
[ 181.517] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 181.517] setversion 1.4 failed
(EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x57f67d]
(EE) 1: /usr/bin/X (mieqEnqueue+0x22b) [0x5615bb]
(EE) 2: /usr/bin/X (QueueKeyboardEvents+0x52) [0x44d452]
(EE) 3: /usr/bin/X (xf86PostKeyboardEvent+0x44) [0x483e84]
(EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f4f79e94000+0x5591) [0x7f4f79e99591]
(EE) 5: /usr/bin/X (0x400000+0x73da8) [0x473da8]
(EE) 6: /usr/bin/X (0x400000+0x9c330) [0x49c330]
(EE) 7: /usr/lib/libpthread.so.0 (0x7f4f7f8af000+0xf870) [0x7f4f7f8be870]
(EE) 8: /usr/lib/libc.so.6 (ioctl+0x7) [0x7f4f7e9eef17]
(EE) 9: /usr/lib/libdrm.so.2 (drmCommandWrite+0x5d) [0x7f4f8055e9fd]
(EE) 10: /usr/lib/libdrm_nouveau.so.2 (nouveau_bo_wait+0x8a) [0x7f4f8058446a]
(EE) 11: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f4f7d349000+0x716b) [0x7f4f7d35016b]
(EE) 12: /usr/lib/xorg/modules/libexa.so (0x7f4f7cd05000+0xb308) [0x7f4f7cd10308]
(EE) 13: /usr/bin/X (0x400000+0x170563) [0x570563]
(EE) 14: /usr/bin/X (0x400000+0xc0f95) [0x4c0f95]
(EE) 15: /usr/bin/X (0x400000+0x104193) [0x504193]
(EE) 16: /usr/bin/X (0x400000+0x373be) [0x4373be]
(EE) 17: /usr/bin/X (0x400000+0x2693a) [0x42693a]
(EE) 18: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7f4f7e932bc5]
(EE) 19: /usr/bin/X (0x400000+0x26c81) [0x426c81]
(EE)
(EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack.
(EE) [mi] mieq is *NOT* the cause. It is a victim.
(EE) [mi] EQ overflow continuing. 100 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x57f67d]
(EE) 1: /usr/bin/X (QueueKeyboardEvents+0x52) [0x44d452]
(EE) 2: /usr/bin/X (xf86PostKeyboardEvent+0x44) [0x483e84]
(EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f4f79e94000+0x5591) [0x7f4f79e99591]
(EE) 4: /usr/bin/X (0x400000+0x73da8) [0x473da8]
(EE) 5: /usr/bin/X (0x400000+0x9c330) [0x49c330]
(EE) 6: /usr/lib/libpthread.so.0 (0x7f4f7f8af000+0xf870) [0x7f4f7f8be870]
(EE) 7: /usr/lib/libc.so.6 (ioctl+0x7) [0x7f4f7e9eef17]
(EE) 8: /usr/lib/libdrm.so.2 (drmCommandWrite+0x5d) [0x7f4f8055e9fd]
(EE) 9: /usr/lib/libdrm_nouveau.so.2 (nouveau_bo_wait+0x8a) [0x7f4f8058446a]
(EE) 10: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f4f7d349000+0x716b) [0x7f4f7d35016b]
(EE) 11: /usr/lib/xorg/modules/libexa.so (0x7f4f7cd05000+0xb308) [0x7f4f7cd10308]
(EE) 12: /usr/bin/X (0x400000+0x170563) [0x570563]
(EE) 13: /usr/bin/X (0x400000+0xc0f95) [0x4c0f95]
(EE) 14: /usr/bin/X (0x400000+0x104193) [0x504193]
(EE) 15: /usr/bin/X (0x400000+0x373be) [0x4373be]
(EE) 16: /usr/bin/X (0x400000+0x2693a) [0x42693a]
(EE) 17: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7f4f7e932bc5]
(EE) 18: /usr/bin/X (0x400000+0x26c81) [0x426c81]
(EE)
[ 216.437] [mi] Increasing EQ size to 512 to prevent dropped events.
[ 216.438] [mi] EQ processing has resumed after 188 dropped events.
[ 216.438] [mi] This may be caused my a misbehaving driver monopolizing the server's resources.
[ 216.438] Failed to switch from vt01 to vt06: Input/output error
[ 216.438] Failed to switch from vt01 to vt06: Input/output error
[ 216.438] Failed to switch from vt01 to vt06: Input/output error
[ 216.438] Failed to switch from vt01 to vt02: Input/output error
[ 216.438] Failed to switch from vt01 to vt03: Input/output error
[ 216.438] Failed to switch from vt01 to vt04: Input/output error
[ 216.438] Failed to switch from vt01 to vt05: Input/output error
[ 216.438] Failed to switch from vt01 to vt06: Input/output error
[ 216.438] Failed to switch from vt01 to vt07: Input/output error
[ 216.438] Failed to switch from vt01 to vt08: Input/output error
[ 216.438] Failed to switch from vt01 to vt09: Input/output error
[ 216.438] Failed to switch from vt01 to vt10: Input/output error
[ 216.438] Failed to switch from vt01 to vt11: Input/output error
[ 216.438] Failed to switch from vt01 to vt02: Input/output error
[ 216.810] (II) evdev: HP WMI hotkeys: Close
[ 216.811] (II) UnloadModule: "evdev"
[ 216.811] (II) UnloadModule: "synaptics"
[ 216.811] (II) evdev: PS/2 Generic Mouse: Close
[ 216.811] (II) UnloadModule: "evdev"
[ 216.811] (II) evdev: AT Translated Set 2 keyboard: Close
[ 216.811] (II) UnloadModule: "evdev"
[ 216.811] (II) evdev: Sleep Button: Close
[ 216.811] (II) UnloadModule: "evdev"
[ 216.811] (II) evdev: Video Bus: Close
[ 216.811] (II) UnloadModule: "evdev"
[ 216.811] (II) evdev: Power Button: Close
[ 216.811] (II) UnloadModule: "evdev"
In addition, I can't seem to find any other files related nvidia that seem like they would matter, except for ~/.nvidia-settings-rc, which I moved to ~/.nvidia-settings-rc.bk (prior to the attempt which created the log above). Keep in mind that this is after re-installing nvidia so I can startx and have a working system... Is there anything that looks like it wouldn't be removed by the nvidia package?
# find / -name *nvidia*
/proc/irq/63/nvidia
/proc/driver/nvidia
/home/jwhendy/.nvidia-settings-rc.bk
[hits from /usr/share/icons excluded]
[hits from /usr/share/ excluded]
/usr/lib/libnvidia-tls.so
/usr/lib/modules/extramodules-3.11-ARCH/nvidia.ko.gz
/usr/lib/modules/3.11.6-1-ARCH/kernel/drivers/net/ethernet/nvidia
/usr/lib/nvidia
/usr/lib/libnvidia-tls.so.325.15
/usr/lib/libnvidia-ml.so
/usr/lib/libnvidia-glcore.so
/usr/lib/vdpau/libvdpau_nvidia.so
/usr/lib/vdpau/libvdpau_nvidia.so.1
/usr/lib/vdpau/libvdpau_nvidia.so.325.15
/usr/lib/libnvidia-glcore.so.325.15
/usr/lib/libnvidia-ml.so.325.15
/usr/lib/libnvidia-cfg.so
/usr/lib/xorg/modules/drivers/nvidia_drv.so
/usr/lib/libnvidia-cfg.so.325.15
/usr/lib/modprobe.d/nvidia.conf # owned by nvidia; removed when I switch to nouveau
/usr/lib/libnvidia-cfg.so.1
/usr/lib/libnvidia-ml.so.1
/usr/bin/nvidia-settings
/usr/bin/nvidia-xconfig
/usr/bin/nvidia-smi
/usr/bin/nvidia-bug-report.sh
/usr/bin/nvidia-debugdump
/root/.nvidia-settings-rc
[hits from /var/abs/ removed]
/dev/nvidia0
/dev/nvidiactl
/sys/bus/pci/drivers/nvidia
/sys/kernel/slab/nvidia_p2p_page_t
/sys/module/drm/holders/nvidia
/sys/module/i2c_core/holders/nvidia
/sys/module/nvidia
/sys/module/nvidia/drivers/pci:nvidia
Anything look odd in the log or the files?
As always, feel free to suggest other things to try -- I can pipe ls into files to show what files are available when I'm pre-startx with nouveau installed, or more Xorg logs... My computer is not happy wtih nvidia at all and is nearly unusable. I really need to solve this until nvidia is compatible with 3.11 kernels again.

Z77A-G45 + i5-3570K = no monitor output

Hi guys,
at first I´m sorry for my bad english and sorry if this topic doesn´t belong here.
Three days ago I have just built my first pc. When I plug my CPU i5-3570K (which should be fully supported) into my main board (Z77A-G45) and switch the power on, I have no monitor output from either the MB or GPU output, while computer is still running. Everything else is plugged correctly. Then I borrowed and tried to put another CPU (i5-2500) into my main board and monitor display worked fine. It means to me that mother board is not damaged. Then I have tried to put my CPU (i5-3570K) into different main board (PA65-UD3-B3) and it worked correctly also. (I was able to get into bios, could install OS, etc...). That means to me that my cpu (i5-3570K) is not damaged as well. I have also tried several times flash bios for CPU 3570K version but without any changes. ( If I remember correctly default bios version was 7752v25. So I have tried to flash at first into 7752v23 and than to newer 7752v28 and 7752v29). My main board (Z77A-G45) is working, my CPU (i5-3570K) is working also but only separately. My question is: why this main board (Z77A-G45) doesn´t work with this CPU (i5-3570K) together and what can i do next? I am pretty desperate because i can´t return my main board or cpu to seller when every part work separately. And MSI bench in Czech republic only repair laptops and all-in-one pc (thats what they said to me through phone call)
I am kindly asking you for any recommendation and advice in this regretful situation.
Thank you all.
Board: MSI Z77A-G45
Bios: 2.8 or 2.9 (not sure because i can´t get into bios now)
VGA: Sapphire HD 7870 XT BOOST 2GB DDR5
PSU: Seasonic S12II-620W
CPU: Intel Core i5-3570K BOX
MEM: CRUCIAL 8GB (kit 2x 4GB) Ballistix Sport 1600MHz CL9
HDD: WD Blue WD10EZEX 3.5" 1TB
COOLER: default intel cooler in box with CPU
OS: don´t have any

I have attached bios version .2A0 for you to try. This is the next full release although it hasn't made it to the website yet.
>>Use the MSI HQ Forum USB flasher<<
Use option 1 of the tool and point it at the compressed archive. Do no decompress. Then point it at your fat 32 formatted flash drive. When the tool is done, boot to the usb drive and follow the directions.
You will need to re-install the ME drivers when complete.
You can see the release notes here:
https://forum-en.msi.com/index.php?topic=161033.0

Multiple displays with 15"and 19"monitor using a VGA splitter on my Mac Pro

Hi, so I have a brand spanking new Mac Pro and have been using a cheap, basic 15" monitor with it. As I'm doing lots of Edit/graphics work I've just purchased a new monitor, it's a 19" Acer flatscreen. Now I'm hoping to work the same display across both monitors, so I can set up my preview window on the 15" and do my work on the 19" screen.
The Mac has two DVI output sockets in the back, both monitors are VGA but I only have one DVI to VGA adaptor. Though I do have a VGA splitter! So I've tried going from one DVI socket to VGA, then put the splitter into that and then each monitor into each split socket, if that makes sense? I now have the same display on each screen i.e. while I'm typing this I'm looking at it twice but I want to see it once over two screens, how do I adjust this, there's no option in display settings?
Is it simply that I need to buy another DVI to VGA adaptor and use the other port? Just looking to save myself a tenner, that's all!
Thanks!
Alex

Yep, you're right! Thanks, working now, very useful.

Switching from Sun monitor output to VGA ourput.

Similar Messages

Maybe you are looking for