Can switching from CRT to LCD monitors cause system problems?

My 9.1 locks up periodically (but the cursor still moves) since I replaced two 20" CRT monitors with two Samsung 19" LCD monitors. Could this affect the performance of my machine? I've tried everything else to address the freeze problem but recall the issue started when I installed the LCD monitors. Anything I can do?

Studedot,
You may have issues with the amount of video memory depending on the resolutions of the new LCD screens.
I find LCD screens go up to insane resolutions, way more than the corresponding size CRT monitor, ie. a 17in Dell LCD monitor with higher resolution than a 21in CRT.
It shouldn't cause crashes or freezes, but may cause -redraw problems when closing / moving windows in 2D and playing 3D games.

Similar Messages

Dual Monitor Causing System Problems?

Hi, I'm new to this site, so I hope this is where I ask this question! My design group switched to G5/Cinema Display screen from old g4 setups mid 2005. I retained my Mitsubishi Diamond Pro 2020u monitor to use as a secondary display for pallettes, extra files, etc. It's hooked up using a dvi-vga adapter.
My new G5 had hiccups from the start, but around March 2006 I started getting Kernel Panics almost every week, serious slow-downs, Adobe app crashes, etc. It got to the point that I was troubleshooting every week, but could never put a finger on exactly what was happening. IT archive-installed 10.4.4 after we discovered the system had been updated to 10.4.6 and we thought that would solve the problem. While that solved the issues that were relevant to 10.4.6 glitches, it didn't fix everything and little, persistent problems remained, including stalls, crashes and kernel panics. After removing suspect fonts, wallpaper, icons, updating software, repairing permissions, tossing preferences, and other troubleshooting over and over, we (I.T.) finally switched my cpu to another one in the department using data migration (just my user information, not software or other files). Still the same hiccups and even new glitches appeared (InDesign crashing on spellcheck, Photoshop not granting me access to save changes to files, etc.), including two more Kernel panics (within 5 minutes of each other) in the two weeks since we switched hardware. More troubleshooting fixed the app-specific problems, but there are still the persistent annoyances occurring.
I again did all the troubleshooting mentioned above and finally someone mentioned that I'm the only designer in our group using a dual display set-up. Could there be validity to the non-cinema display monitor causing these problems and if so, what is the solution? I've disconnected the second monitor for now, but would love to have it back. Also, we work with a server (for instance, the kernel panics only happen when I try to place a file from the server into InDesign CS2 using the place command, so there's another avenue to go down if the monitor isn't the issue.)Thanks!
G5 Mac OS X (10.4.4) graphic design applications
G5 Mac OS X (10.4.4) graphic design applications
G5 Mac OS X (10.4.4) graphic design applications

I only just disconnected the monitor, so it will take time to tell if that's a factor. As for the kernel panics, although it's always the same scenario (placing images from server through InDesign) they happen very randomly; it's not happening every single time I place a file. In fact, I just placed an image on the server into an ID doc I have on my desktop, no problem. So I can't say for sure that it has happened when working from my desktop or only when working on the server.
G5 Mac OS X (10.4.4) graphic design applications

Switching from CRT to LCD

I am a print graphic designer in need of a new monitor and ahve been given 3 days to find one. My IT folks are suggesting a Samsung SnycmasterXL24. I am concerned with switching to an LCD from a CRT. I have seen some of the other flat screens the regular staff use in here and am not impressed. I am currently using a ViewSonic G225FB 21 with Matrox Parhelia 128 video card with Pantone color calibration software. I have the speed needed to run the graphics software and get great accuracy of color between my monitor and print. Anyone else out there use this monitor? Any issues with graphics software, video cards and color accuracy? Any input is greatly appreciated. I am running Windows XP.
Thank you for your input,
Laurie

Laurie,
I used a ViewSonic G220f CRT for a number of years, and then switched to a Samsung 213T LCD when my ViewSonic went to monitor heaven.
There are some differences between a CRT and and LCD, but I found the transition to be fairly painless. The Samsung is a good monitor, but there is some light falloff when you get to the edges and the corners, more than with the CRT. Still, it is no big deal, at least to me. I do a lot of fine art printing, and my previous job was as a director of marketing, and I sent a LOT of jobs to press.
LCDs are a little less forgiving if you don't view more or less perpendicular to the screen. But, to me, that is also no big deal. A monitor hood is always a good idea, to prevent ambient lighting from reflecting off the face of the monitor.
FWIW, I found the same calibration parameters worked fine on both monitors. I chose 5200K color temp, 2.2 gamma, and a luminance of 90 cd/m2. My monitor and inkjet proofs were dead ringers, and they matched the proofs I got back from my commercial printer very closely.
The 213T is no longer in production, but the Samsung synchmaster monitors are pretty good for the price. I have also heard good things about the NEC monitors, but haven't tried them. If you have money to burn, there are Eizo, LaCie and other high end LCD monitors. I also drive my monitor with a Matrox Parhelia 128 MB card. Be sure to use the digital connection.
Probably the biggest difference, at least to me, is that sharpening looks a little different on an LCD compared to a CRT. You will just have to get used to that. There is no "Perfect" monitor to print match, so whatever monitor you use, you need to get a feel for it.
Hope some of this helps.
Lou

Can I place a 19" LCD monitor over my Time Capsule (G4)?

Can I place a 19" LCD monitor over my Time Capsule (G4)?

No, absolutely not..
Although it has better life than the old ones you are tempting fate by cutting any ventilation at all.. stick the TC vertical on a wall (mounts are sold on ebay) anywhere but under something.

I have duplicate pictures in "my catalog" that I believe come from two Adobe folders found under "my pictures/adobe/ one is Revel and the other is Photoshop express which preceded revel. Can I delete those two folder without causing a problem with my cata

I have duplicate pictures in "my catalog" that I believe come from two Adobe folders found under "my pictures/adobe/ one is Revel and the other is Photoshop express which preceded revel. Can I delete those two folder without causing a problem with my catalog?

Thanks for the links, Limnos.
If you are willing to continue helping, here's what I found.
Just to clarify the two iTunes folders I am refering to are:
username-->Music-->iTunes
HD-->iTunes
I am presuming each location has a full set of files as outlined in the above links?
Not all the files are in both locations. Most are.
- The Itunes folder in my home folder does not have itunes library.xml.
- The Itunes folder in my home folder has a subfolder called Mobile Applications (username-->Music-->iTunes--> Mobile application). The Itunes folder at the HD level also has a Mobile Application folder but it is a subfolder of Itunes Media folder (HD-->iTunes--> iTunes Media-->Mobile applications) and has no files in it.
- I do not have an iTunes Media in the iTunes folder in my home folder.
- also the Itunes media folder (HD-->iTunes--> iTunes Media) has subfolders by type (books, movies, itunes u, music etc...) but the iTunes Media-->Music also has some of the same subfolders ( iTunes Media-->Music-->books, iTunes Media-->Music-->Movies, iTunes Media-->Music-->iTunes U). Is this normal repetition?
You say:
/itunes/itunes media/ music
but it is important to note what comes before all that.
There is nothing as far as I can tell before that first forward slash. Since the only iTunes Media folder I have is in the iTunes folder that resides at the HD level (HD-->iTunes--> iTunes Media folder) not the iTunes folder in my home folder (username-->Music-->iTunes) , I assume that's the one that holds the music.
Keep iTunes media folder organized and Copy files to iTunes Media folder when adding to library are both checked on
Does that give more clarity into my problem?

Greetings. Do you know if an unlocked Iphone 5S can switch from CDMA to GSM with a sim card, or if you have to choose one capacity or the other when you buy the phone? Many thanks.

Greetings. Do you know if an unlocked Iphone 5S can switch from CDMA to GSM with a sim card, or if you have to choose one capacity or the other when you buy the phone? Many thanks.

Is this a Verizon or Sprint iPhone 5S?

My latest pano photo have missing landscape. Some of the photos are merged into one. I can provide the examples. What could cause this problem on a new 5C?

My latest pano photo have missing landscape. Some of the photos are merged into one. I can provide the examples. What could cause this problem on a new 5C?

Thanks for the input. I was finally able to find some test conditions that duplicated the problem, and it is either that or some other out-of-spec diffraction distortion. So I sent it off for repair.

Don't know if this went through the first time. Cannon printer would not print black. bought a new Epson-800. Same problem. Can it be something in my Mac causing the problem. It's only the black that is not working.

Don't know if this went through the first time. Cannon printer would not print black. bought a new Epson-800. Same problem. Can it be something in my Mac causing the problem. It's only the black that is not working.

Bill ...
Believe it or not, might be a font issue > Computer won't print black text in...: Apple Support Communities

CRT vs Lcd monitoring

Believe me, I've been struggling with this question for years.
For long I felt CRT monitors were better than Lcd monitors for critical color correction. But feeling the current push in Lcd technology, is the acceptance for professional LCd displays such as the JVC 24"HD ok, or do the people with the golden eyes only see the bvm CRT as the only way for critical color grading?
Knowing I usually color 1080 24p.
If you make a good living coloring, I really would appreciate your comments.
- Eric.

Someday I will be done with this question.
CRT technology fails for a number of reasons over a certain display size, and it is for those reasons that the technology is no longer acceptable,both for the technical and economic challenges. At 24", it is almost not worth the justification for HD in any sense, since that technology really only starts pulling away from what went before it at maybe 36" and beyond.
In years past, the JVC LCD's may have been competitive in terms of rendition, but suffered from massive off-angle viewing problems. It is spectacularly difficult to build a decent LCD -- if you find one in a "reasonable" price category, +caveat emptor+ -- its a $38 Rolex.
Some of the recent plasmas are pretty good. Some high-end post facilities are actually using them, but have conditioned them behind LUT-boxes like Truelight's Northlight system, among others, and have a crack staff of technicians on standby with probes in hand -- and do routine daily/weekly checks, lineups and calibrations. Most of the time, its to make sure the monitor is displaying the AIM values of the day for the associated lab, but its also because they just wander, and not just over time, but with the intensity of the picture that happens to be up.
Consumer TVs are for folks at home to kick back and watch Glee or whatever, or ignore it altogether just to have enough noise in the background to cover what's going on in the foreground.
So if you're making video that people don't watch anyway, LCD is great, and doesn't cost very much either.
jPo
jPo

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.

Update from 04/09 (possibly kernel) causing system lock ups

It seems that this is happening only on battery power on my laptop. I'll be browsing the internet (nothing very intensive) and my laptop will hard lock: no caps lock toggle, can't ping from another networked PC, shutdown command via power button doesn't work. I just have to hold the power every time this happens. I tested last night and the longest uptime I had on battery was 30 minutes, while I never had a freeze on AC.
Has anyone else experienced this? I don't see anything in /var/log/everything.log, so I don't know of a good way to isolate this, so any advice would be appreciated. Here are my system specs via lspci:
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03)
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
03:00.0 Ethernet controller: Atheros Communications Atheros AR8132 / L1c Gigabit Ethernet Adapter (rev c0)

I attempted to roll back to a server last synced before the update, however this seemed to cause some problems, so I'm going to try another route. If it's related to ath9k hopefully this will fix it:
http://wireless.kernel.org/en/users/Download/stable/
If anyone has any ideas it would be appreciated....this is one nasty problem.

Time machine problem. Switching from one external drive to another. Problem started when upgrading to Mavrics, and changing to a WD drive

I am a long time Mac user, running my business on an apple platform since 1984. I currently use a 17" MacBook Pro as my primary computer for work. when it is at work it is plugged in via thunderbolt to my monitor and a one tb back up drive. I use time machine to back up the laptop to the one tb drive. When I go home, I take the laptop with me and use another drive at home as a back up. This way I have redundant back ups, in two separate locations. I have been doing this for years, and Time machine has worked flawlessly, automaticity switching from one drive to another.
I recently switched to Maverics, and got a new drive for home. Now whether I am at home or at work, time machine fails to automatically back up. It will alert me every hour that backups cannot be completed, and I must go to the time machine control panel and manually select a drive and click, "back up now". I also see an alert that says "waiting to complete first back up" even though each backup has been completed.
This is quite annoying, and sometimes embarrassing. When giving lectures in large venues, the backup failure alert appears and shuts down my keynote presentation (again, something new since switching to Maverics and the new WD drive.
I have reformatted the WD drive, and also spent time trying to change parameters in the time machine control panel, but so far no luck.
Any advice out there?

Time machine requires a GUID partion scheme, as well as a Mac OS X extended, journaled Volume.
It needs these to correctly:
1) copy the files
2) run a modified spotlight index pass on the files
Both are required to complete a abckup, and most new drives do not conme this way from the factory.

How can I connect HDTV and LCD monitor to PC using both -as a double monitor.

I recently purchased HP Pavilion PC a6600f with HP w1707 monitor. I also purchased a DVI to HDMI cable to hook PC to Samsung HDTV. I can use the VGA cable to hook to the monitor and the DVI to HDMI cable to hook to the HDTV but have to unplug one to use the other. Is there any way to configure Windows Vista Home Premium to show on both screens at same time or at least be able to switch between the two without having to unplug one and restart computer?
This question was solved.
View Solution.

I believe you have to press Source or the Mode button to switch between video inputs on your monitor.

Final Cut Studio 3 can switch from Japanese to english?

I live in Japan and I want to buy Final Cut Studio 3, but there is only Japanese language only. I'm afraid of purchasing it and it won't switch to 100% in English. Is there an International version in Japan? Has anyone purchased from Japan and using it in english? Any info would be most appreciated.
Thank you
Luis

Thank you for answering the question. I went ahead to call Apple Store Japan and ask the same question. It should work on any language once you set your main computer to the language your of choice. I will purchase and will keep you posted.
Thank you
Luis

I can switch from using pc to mac for my adobe cc without a problem?

I have been using adobe cc on a pc but i want to start using it on a mac. there should be no problem if I just sign out on the pc, right? I have a Creative Cloud Student and Teacher Edition subscription

you don't need to sign out of your pc (but you can if you want).
you are allowed up to two concurrent installations and one can be mac and one win (or both win or both mac).
just dl your desktop cc app to your mac and install your adobe programs using the desktop app, Download Adobe Creative Cloud apps | Free Adobe CC trial

Can switching from CRT to LCD monitors cause system problems?

Similar Messages

Maybe you are looking for