[Enlightenment] Switching from xinerama 4k resolution to 2k

Hello,
to make a long story short: How can I switch off xinerama mode in Enlightenment e19 while running the DE?"
Let me explain...
I am about to reinstall my entire Arch Linux system, but before doing that I decided to test the latest Arch Linux on a different disk.
My trouble is my monitor setup. I have an IBM T221 monitor, which is basically four 1920x1200 monitors in one big screen. I have figured out xorg.conf to get the "4K" resolution, and with this line in ~/.xinitrc:
exec enlightenment_start -fake-xinerama-screen 3840x2400+0+0
... it all works perfectly fine.
However, movies don't run so well in that resolution. So what I do in my older e17 install is to simply run this xrandr command:
xrandr \
--screen 0 --size 1920x1200 \
--output DisplayPort-0 --off \
--output DisplayPort-1 --primary --mode 1920x1200 --pos 0x0 \
--output DisplayPort-2 --off \
--output DisplayPort-3 --off
... and that works as expected--I then get the "2K" resolution and movies run smoothly.
On e19 however, that does not work anymore
After running the xrandr script, I get the 2K resolution, but with a framebuffer of 4K; in otherwords, xinerama does not turn off, my screen shows the top left quarter of the 4K setup and when maximizing windows they maximize into the non-existent space...
My solution so far has been to logout, and "startx" with a different xorg.conf file. I wrote two scripts, one called "e2k" and another "e4k", and modified ~/.xinitrc:
e2k
#!/bin/sh
export RESOLUTION=lowres
/usr/bin/startx -- -config xorg.conf-2k
e4k
#!/bin/sh
export RESOLUTION=hires
/usr/bin/startx -- -config xorg.conf
~/.xinitrc
#!/bin/sh
# ~/.xinitrc
# Executed by startx (run your window manager from here)
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
if [ ${RESOLUTION} == 'lowres' ];
then
exec enlightenment_start
else
exec enlightenment_start -fake-xinerama-screen 3840x2400+0+0
fi
And this works well. However, it requires me to logout and login everytime I want to switch resolutions.
Is there a better way?

Just to follow up, Our compositing supervisor was still convinced that running with MP was the way to go, so I worked
with him to run some benchmarks on medium and heavy shots that we determinied would trigger the issue in -MP mode.
The test scene was about 50 frames in length, and we ran it on the same hosts with -MP on and -MP off, and also ran a 
version of bundled frames (10 frames per host/task) and another where we did all 50 frames on a single host (with and without MP).
Interestingly, in every scenerio of these 4 cases, the version with -MP on, was 2-15% faster (despite the 10-11 minute delay at the start in MP mode).
His conclusion was it's still faster with -MP mode ON, and requested that I continue to explore for patches or theories how we might get around the delay.
Have read links:
http://forums.creativecow.net/thread/2/1025525
http://helpx.adobe.com/content/help/en/after-effects/using/memory-storage1.html
Regards,
-Jay-

Similar Messages

  • HT201269 I switched from an iPhone to an LG g2, but now all my iMessages keep going to my old iPhone rather than the new one.  I know the resolution to the problem is to turn off my iMessage, but I no longer have the iPhone because I sold it to the phone

    I switched from an iPhone to an LG g2, but now all my iMessages keep going to my old iPhone rather than the new one.  I know the resolution to the problem is to turn off my iMessage, but I no longer have the iPhone because I sold it to the phone carrier.  Question is how do I turn my iMessage off through a computer that is not a mac. 

    http://support.apple.com/kb/TS5185
    last paragrapgh of Resolution

  • What would cause my iMac's desktop resolution to briefly readjust whenever I switch from my user to another?

    I recently started to notice that whenever I switch from one user account to another on my recently purchased iMac, the resolution of my desktop wallpaper very briefly readjusts.  Both users have the same default resolution and are using wallpaper that came standard with Mavericks.  Does anyone have any suggestions as to what could be causing this?
    Thanks!

    Hello there, Conor68.
    The following Knowledge Base article provides some great recommendations for troubleshooting display issues on your Mac:
    Apple computers: Troubleshooting issues with video on internal or external displays
    http://support.apple.com/kb/ht1573
    Once you're reviewed the recommendations in regards to updates, this portion of the section on "No video or no signal, image distortion, "snow," or flickering" is useful:
    Reset the system
    You can reset the Mac's parameter RAM and SMC.
    Reset the resolution
    Start by resetting the Mac's parameter RAM. If the display does not come up, was previously set to an unsupported resolution, and still results in no video:
    Start up in Safe Mode.
    From the Apple () menu, choose System Preferences.
    Choose Displays from the View menu to open the preferences pane.
    Select any resolution and refresh rate that your display supports.
    Restart your computer.
    Thanks for reaching out to Apple Support Communities.
    Cheers,
    Pedro.

  • Switching from FCP7 to CS6! Two BIG questions I can't figure out...

    Hello!
    So I'm running CS6.01 on my new 27" iMac running OS 10.6.8. I'm excited to be transitioning over to CS6 after the last 6 or 7 years using Final Cut Pro. But I don't have time to mess around as I'm in the middle of projects so here are my 2 main questions right off the bat:
    First I should say that I edit AVCHD footage shot from Panasonic HMC150's. I shoot Weddings. About 35-40/year. In FCP, my workflow was...shoot EVERYTHING at 720p60 and TRANSCODE it in FCP to ProRes Proxy. Then I'd CONFORM it to 23.98 (using Cinema Tools which takes all of about 30 seconds to do 400 clips) so that it was all in slow-mo looking smooth and beautiful. Then, I'd drop it all on the timeline and edit. Most clips I need in slow-mo but the ones I don't (eg. the Ceremony) I just speed up 250% and it's full speed. Then at the end of editing I'd batch capture and re-transcode to ProRes 422 and I'm done. It all looks great.
    Here's the important thing:
    I edit on a 23.98fps timeline that way it maintains a bit of the film-stuttery look instead of the video/soap-opera look of 60fps footage and also it naturally has everything at 40% smooth slow-mo. I dont want that video/soap opera look that I would get if I edited my 60p footage on a 60p timeline! This is important to me.
    1) I know with CS6 I don't "have" to transcode, but I can just ingest and edit the AVCHD files natively, right? Well, okay, but if I do that will dropping those 60p clips on a 23.98fps timeline give me the same look I got when I use to conform the footage first? Specifically is it just as smooth to just change the speed of a 60p clip by 40% and drop it on a 24p timeline? And what about the stuff I want at full speed...if I drop that 60p footage right on the timeline and don't speed it up it will be full speed but will it look the same as my conformed footage looked when sped up in FCP? Please elaborate for me.
    2) Audio. When I bring in audio clips from my 2 cameras each track has 2 separate audio feeds (eg. 2 wireless mics, a shotgun mic, an internal mic). CS6 brings them in on one track. I read up where I need to "Modify the clips" and adjust the Audio Channels so that there are 2 tracks. Then I'm guessing I just make one track the left track and one the right? This seems to work and makes a separate track that is balanced to the center and has each of the 4 channels as its own separate adjustable track. Am I doing that right? And more importantly...my real question...if I'm scrubbing thru the timeline and I double click on one of the audio tracks to bring up the waveform and edit, sometimes it doesn't come up where I stopped in the timeline. Unless the clips are linked. But don't I have to unlink them to edit them individually? So how do I do this where I can be in the timeline, watching the video and when I hear something I want to adjust, I stop the video and quickly access the individual track (eg. one of the wireless mics) to make the adjustments?
    Hope my questions make sense. Thanks SO much in advance for all your help! It took me like 20 minutes to figure out how to post a question but now that I've done it I'm very excited that I've got it out there and hopefully I'll get past my current workflow roadblocks. Thank you!!!!!!!

    Jim Simon wrote:
    I'd recommend a different work flow.  Shoot what you want at full speed in 720p/24.  Shoot what you want in slow motion at 720p/60...
    I would respectfully disagree with Jim's statement and endorse the OP's technique of shooting at 60 fps for purposes of playback at both normal speed and slow motion at 24 fps.
    I think the more creative choices you give yourself in post the better.
    Since you (DMH79) are using the same footage for both normal speed and slow motion playback, I think your way is definitely the way to go as long as you are happy with the resolution.
    Even if you were not using the same clips at different speeds, I would still disagree with the opinion that you should be able to predict in advance which shots from a hectic live action event such as a wedding you will want to use in slow motion. In fact, I would go so far as to say that it would be impossible, no matter how easy it is to switch modes.
    Given that slow motion is a reasonable priority for you, I think there is much less to be gained by shooting at 24 fps for clips that you might use at normal speed than by giving yourself the option of both normal speed and slow motion with a 60 fps recording. (To me the bigger tradeoff is not being able to shoot 1080p at 60 fps, which I think applies to your HMC150.)
    I love the look of 24p and will shoot that way for scripted work or if I am absolutely certain that I won't want to use a single shot in slow motion, but for many live events, my preference is to shoot at 720p60, shutter angle 180, for eventual output at 30 fps. I edit in a 60 fps timeline in Premiere, but I export at 30 fps. I find that exporting at 30 fps in combination with the 1/120 shutter speed removes much of the soap opera look (a great description, by the way), but there is no jerkiness in normal speed clips because 30 is exactly half of 60. Media Encoder simply removes every other frame during export. Yet, this allows me to drop any clip to 50% speed and achieve perfectly matched, silky smooth slow motion.
    You probably prefer the 40% speed slow motion and added stutter of 24 fps, but regardless, if you do find that controlling the speed via Speed/Duration is equal in quality to conforming, you may want to consider cutting in a 60 fps timeline and giving yourself the option to export at either 24 or 30 fps.
    Your last post on this topic was from a few months ago. I also switched from FCP7 and would be very curious to know what you have discovered!

  • 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.

  • Put my macbook pro to sleep. When I opened it, the desktop window is small and I can't resize it. All applications now run in the smaller size window.  Can't make it fill the screen. Just switched from windows.  Thank you.

    Put my macbook pro to sleep. When I opened it, the desktop window is small and I can't resize it. All applications now run in the smaller size window.  Can't make it fill the screen. Just switched from windows.  Thank you.

    Check to see if the resolution has been changed in System Preferences.
    Allan

  • Has anyone switched from a PC notebook to a MacBook Pro?

    I am a PC user who is considering switching my 1-year old Toshiba notebook to a MacBook Pro. My reasons for doing so are:
    (1) I would like to simplify the number of applications from various vendors on my computer in order to reduce software conflicts and memory "hogs" that run in the background.
    (2) I have heard that MacBooks are much more secure -- so much so that anti-virus software isn't even usually required. (However, I'm not sure what the constraints are when running a Mac on a home wireless network in conjunction with a desktop PC computer.)
    (3) My understanding is that working with photo's is much more effective with a Mac than a PC. I currently run ACDSee Pro and PhotoShop Elements, and the former has really slowed down my system.
    (4) I've been told that any type of setup -- be it new software, connecting to a network, or finding a wireless Internet connection -- is very easy and straight forward.
    If anyone has experience with switching from a PC notebook to a MacBook Pro, I would appreciate hearing your opinion on doing so, both positive and negative. Alternatively, if you know of a good Web site that provides this type of information, please point me to the URL.
    Thank you!
    ~Kelly

    Hello,
    I switched from a Pentium 4 2.2GHz Dell laptop to a Intel CD 2GHz MacBook Pro.
    This what I found (the good):
    - the spotlight search on a mac is soo much better and faster compared to a windows search.
    - No need for all those extra programs that scan you PC for virusses, spyware, mallware,...
    - No need to download additional drivers or programs before you can do anything.
    - No third pary software that messes up the whole system. Apple software appears to be more reliable, even from third parties.
    - Backlight keyboard with shaped keys
    - You can do more with a mac trackpad than with a windows trackpad. It does not bother me when I forget the mouse on my desk. The trackpad scrolls and has a "right mouse button" as well.
    - Multitasking without systemwide slow downs.
    - I have an iPod, so iTunes is all I need/want.
    What I also found (the bad):
    - the screen resolution on my Dell was higher.
    - Some apps still need Rosetta (office, photoshop,...). If pictures are your thing, iPhoto is no replacement for Adobe photoshop.
    - I sometimes miss the picure viewer thing you have in windows XP. When you select picures and open them, they open in a window with nice back/forward controls,...
    The Preview app in Mac just isn't the picture viewer I hoped it would be. But maybe that's just me...
    - there is a lot more freeware for PC than for Mac. This can also be a good thing for Apple if you consider that most of these freeware things are crap anyway...
    - iChat only works with specific accounts and other iChat programs. I hoped it would be a more "universal" chat program without these limitations. To chat to windows people you need a serious work-around (jabber) or just use MSN messenger.
    - no good at games unless you have bootcamp and a windows CD.
    Overall: I would not go back to windows. I really like the MacBookpro and OSX.
    I have to say that I was not unsatisfied with windows, so I will not trash it. It always worked well for me and did't crash. Programs crashed, but windows did not. I believe a lot of these crashes are due too crappy third party software installed by the user at their own risk...
    I'm saying this to let you know that I happely use the 2 systems, but the mac wins for me. OSX is nice to work with and nice to look at.
    Hope this helps...
    Bjorn

  • NI-4060 giving invalid 1st reading after switching from or to LOW Resistance Measurements

    We've been using TestStand & LabView to test various Circuit board. On series of test involves checking for a short circuit (Measure Low Resistance 4-wire) then measuring for a 3.5Vrms signal on another part of the board.
    For each measurement, the following NI-DMM VI's are used in order:
    niDMMInit, niDMMAutoZero, niDMMConfigure, niDMMMeasure, niDMMClose.
    If we do the Low Resistance 4WR measurement, then a AC V measurement, the 1st reading from the DMM is approx 10x too high, if a 2nd reading it done it is then OK.
    It doesn't matter how long a delay is before we take the 1st measurement, it's always approx a factor of 1E+1 out.
    If however we don't do a Low Restance prior to
    the AC V measurement, then the measurement is always correct.
    I expermented with turning AutoZero on & off, and various resolution settings, however none of these seem to have an effect on the result.
    Can anyone explain these strange results?
    Thanks
    Simon Holman
    Simon Holman
    Software Engineer
    Certified LabVIEW Developer
    Certified TestStand Developer
    measX GmbH & Co. KG.
    http://www.measx.com

    Thanks, after playing with a few more settings I found if I turned the Cacheing off niDMMInitWithOptions, with "Cache=0" that everything worked fine, but it would take a couple of seconds to get the first AC measurement after switching from resistance.
    Simon
    Simon Holman
    Software Engineer
    Certified LabVIEW Developer
    Certified TestStand Developer
    measX GmbH & Co. KG.
    http://www.measx.com

  • Did Mac OS recently switch from 72 DPI to 96 DPI?

    Did Mac OS recently switch from 72 DPI to 96 DPI?
    I ask this because my MacBook renders text at 96 DPI, whereas I read everywhere that Mac OS (X?) renders text at 72 DPI, and MS Windows renders text at 96 dpi.
    Note I'm only talking font points to pixels, not pixels to screen (which is dependent on the display).
    For example, on TextEdit in plain text mode a 16 point font is rendered at 21 pixels, and that corresponds to 96 DPI (if it was rendered at 72 DPI, it would be 16 pixels instead of 21).
    I had a look at the "System Profiler" > Graphics/Display, but I couldn't find a DPI value. It only mentions resolution (e.g. 1366x768).
    So, do you know if Mac OS recently switched from 72 DPI to 96 DPI? And if yes, do you know at which version it made the switch?

    Thanks Kurt, but this was not the info I was looking for.
    My point is, how comes my Mac is behaving as a 96 dpi OS, where this is not documented anywhere that I know of?
    In fact, as I said, I've found plenty of documentation saying the mac is a 72 DPI OS
    (for example, wikipedia) and, even after extensive googling, I have found none saying it is a 96 DPI OS?
    In fact, everywhere it says Windows is a 96 dpi OS, and I've verified that.
    Every rendering engine has a specific DPI count, which does NOT relate to the question "how many pixels (or points) do I need to specify if I want my text to be x inches tall" (by the way, I call that "pixel-to-screen" resolution, or "points-to-screen" resolution). That depends on the screen.
    The DPI I'm talking about answers the question "how many points do I need to specify if I want my text to be x pixels tall". I call that the "points-to-pixel" resolution. That doesn't depend on the screen, it only depends on the OS (at least, when there's no "software" zoom, that's why I take TextEdit as a test on Mac, and Notepad on Windows).

  • I am switching from a pc to mac and want to know how I go about transferring files from one to the other.  There is a chance that I will have to hand my pc back before I receive my MacBook so I will need to transfer on to some sort of external hard drive.

    I am switching from an acer laptop to a MacBook Pro.  I may have to hand in my laptop before I receive my new MacBook. What is the best way to back up my files so that I can transfer them to my MacBook.  I cloud cannot be installed on my laptop because it uses a version of windows that is older and doesn't support it.  Hope someone can help.

    Connect a blank powered external drive to the PC.
    Right click on the Disk in the File manager and choose format: exFAT 
    (if it's a XP machine, first install exFAT from Microsoft and reboot)
    navigate to your user account folders on the PC and drag and drop copy (or copy and paste) to the external drive.
    (if a program has your files, then export them out first)
    Hook up the drive to the Mac, and transfer files to the desktop or to their same appropritate folders.
    Import photo's into iPhoto program, import music into iTunes etc and they will manage those files.
    You can continue to use the external exFAT drive between Mac's and PC's
    Do not format the drive NTFS or FAT, NTFS can't be written too by the Mac and FAT can't hold over 4GB sized files.
    If you format exFAT on the Mac, it likely won't work correctly on the  PC.
    "Migration" type programs are a utter waste of time and effort between PC's and Mac's for the fact that only certain files (and no programs or anything else) will work between them, also it's a hassle and takes too long. So don't even bother with it.

  • I switched from an iPhone to a Droid and can't receive texts from iPhones now, help?

    I switched from my iPhone 4s to a Droid and I do not have that phone anymore. I can not recieve texts from anyone with an iPhone and can not get in contact with my girlfriend or siblings now. I think their phones are trying to send their texts as iMessages to my phone that does not recieve iMessages. How can I just delete my Apple account and recieve texts again?

    Sounds like you didn't turn of iMessage on your iPhone before making the switch.  If you registered your iPhone with Apple using a support profile, try going to https://supportprofile.apple.com/MySupportProfile.do and unregistering it.  Also, try changing the password associated with the Apple ID that you were using for iMessage.

  • My wife recently switched from an iPhone to a Samsung and she can send text messages but she can't receive texts or emails. Any suggestions?

    My wife recently switched from an iPhone to a Samsung and she can send texts but she can't receive them nor receive emails. Her iPhone has had her info removed and the settings have all been set to default. What else does she need to do to correct this?

    In particular the last link is for you
    iMesssage to old phone
    If you move to another phone and forget to turn off iMessage then read “if you no longer have the device in http://support.apple.com/kb/HT5661  If you still cannot resolve it call Apple http://support.apple.com/kb/HE57
    To deactivate iMessage http://support.apple.com/kb/ts5185
    Read http://m.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00053450&fm_s eq=62995

  • I switched from an iPhone to a Galaxy s4.  Everything seems ok except text messaging with people who have an iPhone.  I can send them a text, they can see it, but I cannot see what they text back.  What can I do please?

    I just switched from an iPhone to a Galaxy 4S and I like it except for text messaging.  I can text, they can see it, but I cannot see their response if they are using an iPhone.  Can you help me with this?  What do I do please?

        Congratulations on your new phone kathdogg! Now let's get your messaging working correctly. If you still have your old device, turn it on, go to settings, and turn off iMessaging.
    If you are no longer in possession of your old device, you will need to remove your phone number from your Apple Support Profile. This can be done here: http://bit.ly/1cst2SC 
    Please keep us posted, and let us know if this resolves your issue!
    Thank you,
    MichelleH_VZW
    Follow us on Twitter @VZWSupport

  • Data network errors when manually switching from 3g to 2g

    Hi everyone,
    Apologies if this has been posted before but im running out of ideas! - Got my iphone 4 a couple of weeks ago and have noticed a rather irritating problem with it. For some reason, if i manually switch from 3g to 2g the data connection drops.. I get 'cannot activate cellular data network' errors and i have to toggle airplane mode on/off to reset the connection. Is this a network issue? - I live in London and am with Vodafone... Their tech support are useless as all they suggest is resetting the phone or getting it replaced. Its my third handset in 2 weeks and im getting close to calling it a day and sending the phone back to Apple. Anyone out there in a similar situation? - Advice??

    Bump
    So no-one has suffered this issue? - Not even fellow vodafone uk users?

  • IPhone 4s Voice mail notification not working after switching from Verizon to PagePlus.

    iPhone 4s Voice mail notification not working after switching from Verizon to PagePlus.  How can I get the notifications working?

    Contact your carrier - voicemail, and visual voicemail, is a carrier feature.

Maybe you are looking for

  • MS ACcess and Oracle CLOBs

    I am trying to transfer data into an Oracle Database from Access. The table I'm aiming at is a CLOB, and Access/Windows ODBC are complaining about the sql data type being out of range. Experimenting with removing fields from my script I have narrowed

  • After upgrading to Mountain Lion, Windows doesn't work

    Hello, I've just upgraded my computer to Mountain Lion (from Leopard) and Microsoft windows 'the Power PC applications are no longer supported'.  I've tried to download different version of Microsoft windows - still doesn't work.  Help!? I'm aware th

  • ITunes and surround sound internet streams

    Hi all, I'm looking to broadcast internet streams in surround sound and I want to select an audio codec which iTunes will play. Does anyone know which surround audio codecs are supported for internet streaming? Best regards, Daren.

  • What is the sql query to know the database name having known table name?

    when i am running the following query....error coming select * from information_schema.tables where table_name = 'articles' Error starting at line 1 in command: select * from information_schema.tables where table_name = 'articles' Error at Command Li

  • Why does Xcode crash after it finds a device for development and I press "ignore"?

    When I try to program with java, inevitably, Xcode detects an iOS device and asks me if I want to use it for development, even with bluetooth disabled. When I press either button, it crashes. How do I stop this?