NEC PA241W-BK-SV: sRGB Emulation; DisplaySync Pro
DisplaySync Pro:
I have a Dual 867Mhz G4 on which I do all my graphics work with two CRT monitors. I also have a MacBook Pro which I'd like to transition some of my work in the future as its likly to be much faster.
The NEC PA241W-BK-SV claims to feature "DisplaySync Pro" technology from NEC which would allow you to hook two computers to the same display and then control both computers with a single keyboard and mouse (one at a time). They have a white paper located here:
http://www.google.com/url?sa=t&source=web&cd=1&ved=0CBYQFjAA&url=http%3A%2F%2Fww w.necdisplay.com%2Fcms%2Fdocuments%2FMiscellaneous%2FDisplaySyncPro_TechPaper.pdf&ei=n9BdTZ_pCIPDgQe4zaGiDQ&usg=AFQjCNG0g5ZfMs4nrMy2GPxkoXdC5pXE 7g&sig2=EwXyyde-gEpt8F2grCasw
Does anyone have any practical experience with this? Being that the G4 is a PowerPC using 10.4 and the MacBook Pro is a Intel machine using 10.5 exactly what type of mouse and keyboard would work to control both through the panel? Can I use my G4 mouse and keypad or will I have to buy an updated keyboard and mouse for the MacBook Pro instead?
sRGB Emulation:
It would seem I am stuck with either buying a standard gamut lcd that has no calibration / useless software calibration -OR- buying a wide / ultra gamut lcd that features hardware calibration, but whose srgb "mode" may not work correctly.
Do any Mac users have any experience with PA241W-BK-SV in regards to its srgb mode? Several in-depth reviews from PC (non Apple) sites said its color accuracy was good once calibrated (one using a 3rd party calibrator said the blacks were not as deep as they like while another using the NEC SV calibrator said the blacks were only off one shade from true black).
I had also been looking at the NEC LCD2490WUXi; however, its no longer made, and its replacement (LCD2490WUXi2) is not as highly regarded. And strangely while the NEC FAQ says this unit is a standard gamut lcd the actual product page for this lcd clearly states it is a "ultra wide" gamut lcd, which I think might make it more difficult to emulate sRGB over the PA241 which is just a wide gamut lcd.
And other suggestions? I am looking for something with 1920 x 1200 resolution as thats as high of a resolution the G4 will support for digital monitors. Note: I'd have to use the lcds with 8 bit color (24/30).
Similar Messages
-
hi there
i've been thinking about getting a new ips monitor for my mac mini and the NEC PA241W looks pretty good, but i'm not sure if my mac mini (intel, GF9400) is good enough for this hi-end monitor. Does anyone have a similar setup, or any feedback on this?
many thx!This is a good review of NVIDIA ION platform, and I think you will very most likely find your answer somewhere within what the reviewer has to say:
http://www.guru3d.com/article/nvidia-ion-platform-review-preview/2 -
Connecting 2013 MacPro to NEC PA271w
This is not a question but a comment on my search to obtain the 2560 x 1440 resolution from the NEC PA271w monitor from the new Mac Pro. After trying both the Thunderbold to DVI-D connector and the HDMI to DVI-D connectors, both of which had a maximum resolution of 1920 x 1080 and talking a couple of times to Apple Support, I was referred to Apple bulletin HT5918 which claims that one has to use the Dual Link Apple Mini Display Port to obtain the 2560 x 1440 resolution. However, after talking to NEC technical support, for the PA271w this is not correct. I was pointed to their Mini Display Port to Display Port Cable (a Thunderbold to Display Port) Part number PA-MDP-CABL. I now have this on order but was assured that this is the only cable I need to connect the late 2013 Mac Pro to the NEC.
A number of threads since the nMP 6,1 "Late 2013" shipped.
http://www.bing.com/search?q=NEC+PA271w+Mac+Pro+2013
Wit h some on the side bar's "More Like This" and a search of this forum and the Mac Pro forum on MacRumors, and look for Grant's posts here if you want to narrow it down. -
Sony/NEC Optiarc AD-7170A Problems
I added a 2nd Sony/NEC Optiarc AD-7170A to my Mac Pro Purchased through Newegg. The new Optiarc drive will play DVDs but will not burn. It says it is unsupported. It also has another firmware version. Both drives are on CSL.
How do you update the drives firmware? Is there another setting that needs to be adjusted?Sorry to hear you are having problems. It does sound as if the drive may be bad. I would try a few things first if you haven't already done so. Have you tried using Patchburn? It is a free program widely used in the Mac world to allow newer drives to work with older versions of the operating system. Although 10.4.10 would work with your Sony, 10.3.9 won't. The drive is too new for the OS. It's easy to download and install and I've never heard of it causing problems. Have you also tried different brands of media?
Both these things can make a difference. But if the drive really is bad, you really don't need to buy an Apple drive, in fact, there are many reasons not to. My MacPro came with a Sony Optiarc that was defective - it's not just retail or oem drives that can go bad. Apple almost never updates their firmware, and from all your work you should now realize how important good firmware is. I have 2 non-Apple drive in my MacPro (a Pioneer and an LG) and two in my G4 (a Pioneer and an LG) and all work just fine. You just happened to get a defective drive. It has nothing to do with EFI, or having the drive supplied by Apple. Please consider a Pioneer 112. It is a much more reliable drive than the Sony, and is being used in the latest MacPro's. If you get an "Apple" drive it will simply be another Sony or the Pioneer for twice the money you could get it online. It would have Apple firmware, which is never as good as the original drive makers firmware. A Pioneer you buy online will do everything an Apple supplied drive does, only better, because of Pioneer's superior firmware.
Good luck, don't let this get you down it's fixable without spending $80 more. I always tell myself in situations like this (and I've been there often) that I spent my money not on a bad drive but on all that I learned in putting it right. It helps a little
Message was edited by: bicomputational
Message was edited by: bicomputational -
Best $1k-$2k monitor for editing HD video?
I'm finding myself lately doing quite a bit of color correction to HD video footage lately, and my extremely old monitor (Planar PX2611W) just isn't sufficient anymore, so I'm hoping you all might be able to help me. I've looked at a number of different monitors, and am starting to get confused by all of the Gamut discussions and whether they play at all into video editing (or are just for photo editing - which is also important to me), calibration issues (or devices), etc.
What I am looking for is around 27", preferably closer to $1k but willing to go up to $2k'ish, professional grade and calibrated monitor for editing HD video footage (displayed on everything from HD TVs to smart phones) and photos (mostly for web but also definitely do some printing - usually all in the sRGB gamut).
Also looking for calibration device suggestions if the monitor doesn't have such functionality built in.
Any help on this would be greatly appreciated!You said:
"It seems the playback is the same when viewed on both monitors."
Both monitors at the same time ? That's the same (or worse) as using only the larger monitor.
You should do the test again using just the older monitor with the smaller resolution.
I believe the higher the resolution the harder the CPU and graphics card has to work. This could mean slowdowns and maybe choppy playback.
A better solution would be to use 2 monitors. The playback monitor should be maybe only 1920 resolution. And in Nvidia panel you should set the hardware acceleration only for this monitors and not for both. On the second monitor you can move most of your toolbars. In this way you will have a giant workspace/resolution - but only 1920 pixels accelerated.
I also bought a NEC PA241W and I searched high and low and could only find discussions about photography and printing. Like calibration and this monitor is good only for printing. And not one discussion on any forum about calibration and After Effects for example. Like the video people are not interested at all in calibration.
I would really like to know if calibration with the X-rite i1Display Pro is also good for video ? Or only for printing. -
Need help! w530 or T540p for photography??
Hello everyone and thank you in advance for your help and expertise! :-)
I am trying to figure out which of these two laptops would serve me better for my photography and Photoshop needs. Having lots of memory, a great screen that will run with Photoshop CS6, IPS and the best color available on the monitor is extremely important to me. Having a vibrant screen is also a must.
It looks like its a trade off between the two. It appears the color gamut and calibration might be better with the w530 but I don't think it has IPS. The T540 doesn't look like it has the color features but has IPS. I just cant decide and really want to get this right because its a huge purchase for me.
If you can help me I would appreciate it so much.
Please let me knowgreyhoundrick,
I'm a photographer and I produce multimedias. I hope I can help.
"Having lots of memory, a great screen that will run with Photoshop CS6, IPS and the best color available on the monitor is extremely important to me. Having a vibrant screen is also a must."
I need to narrow these in points to make it simple and hope to help in your choice of laptop:
On Panels...
* Normally, IPS and full coverage of AdobeRGB don't go hand in hand unless you have a true high end panel. These panels would usually be made by NEC (in their PA and Spectraview lines) or Eizo.
* The W530 panel does indeed cover AdobeRGB (I have one and can attest to it since I also own an NEC PA241w) but the viewing angles are not the greatest (albeit much better than the vast majority of TN panels)
* I don't know the quality of Lenovo's IPS panels but the X230 did not really cover much of the sRGB space although it doesgive you the nice viewing angles. However good will the T540/W540 panels be, I don't know and I can't advise.
http://www.notebookcheck.net/Lenovo-ThinkPad-X230-2306-2AU-Laptop-Review.75317.0.html
* Apple's MBP Retina however does indeed cover almost all of sRGB but goes about halfway on AdobeRGB. A really good performance, indeed.
http://www.notebookcheck.net/Review-Apple-MacBook-Pro-15-Retina-2-3-GHz-Mid-2012.78959.0.html
* In Conclusion, what is more important to you? A wide-gamut display or an IPS screen? I work with Ps, Lr and DxO and I can tell you that the colours are very different when you work in either scenario. More so if your cameras are shooting in the AdobeRGB space (which Sony, Canon and Nikon can do)
Is the viewing angle imporant? is it more important that the colour gamut? Only you can answer that. I am completely happy with the W530's screen and I can work seamlessly with it along with my NEC monitor (both can be calibrated almost identically with Spectraview II for the NEC and DispcalGUI for the W530's screen)
You also mention "vibrant", but that is as subjective as you can get in the visual field. We could discuss contrast ratios, colour gamut coverage, brightness, gamma... all of these can affect "vibrancy" depending on who you talk to.
On Memory...
* You can do that with either system so money is the only issue, if an issue.
Photoshop is RAM intensive in as much as you open many files at the same time (not just open them in ACR before opening them in Ps) and it can, indeed, use as much RAM as you give it. The second most needed part of Ps is CPU power for filters and batch operations (like the ones you can use with Bridge)
Lightroom (if you ever consider it) is a resource idiot. Even if you had 32GB of RAM, it would still stick to 4...or 5...and will always lag behind. Why does Adobe not make it more powerful, no one knows.
On Video Cards...
This is more complex and I have yet to find a proper answer. I chose W530 because I also work on video and it handles Premiere Pro very well. The nicest thing about Quadro is the ability to give me 10bit all the way to the NEC monitor, which helps greatly with the gradients thanks to its ability to show a billion colours instead of just 16 million. That, and also the ability of handling Premiere Pro so well. I don't know if the T540 video card will be able to do this.
It sounds like you are starting in photography. If you have the means to get any of these two systems, I would suggest saving some cash and buying a proper IPS monitor like an NEC PA or an Eizo. Whatever you do, do not buy the HP or Dell monitors since they will not be able to do hardware calibration and their price isn't as competitive for the class as one might think. Same goes for the apple monitors. Not worth the money in the long run.
Hope this helps. -
Wide-gamut displays and Thunderbolt
I returned an ASUS PA279Q wide-gamut monitor because several important advertised functions (Adobe RGB and sRGB modes) were not supported through the Thunderbolt connection on my 2013 MacBook Pro Retina (15”). ASUS support explained to me that the Thunderbolt port output was YUV rather than RBG and their calibrated modes were disabled with that output. The monitor worked perfectly on a 2009 non-Thunderbolt MacBook Air through the mini-DisplayPort.
I am now considering the NEC PA272W but it appears to be the same panel as the ASUS monitor. Could anyone confirm that the NEC can utilize its Adobe RGB and sRGB functions when connected by a mini-DisplayPort cable through a Thunderbolt port?
Or could anyone recommend another wide-gamut display that works for sure through a mini-DisplayPort/Thunderbolt connection…
Would you consider the Apple Thunderbolt Display for critical color work?
Thanks.chris.dg wrote:
So I am curious how well the sRGB mode works? I've read reports on other NEC wide-gamut monitors that when switched into sRGB mode you lose a bit of luminance, that the reds over oversaturated, and general desktop/browser colors are obviously not "normal". Have you noticed anything of the sort with your new PA272, or in sRGB mode is it still a cream of the crop display?
I have not noticed anything odd about sRGB mode. The problems you mentioned, where colors can look horribly oversaturated or shifted, I have seen (or seen documented by others) when the monitor is in Adobe RGB mode. But that is not the fault of the monitor at all. It is always the fault of the OS or an application not adapted to work with such a wide color space, mistakenly assuming the monitor is sRGB. The colors look fine in high-end graphics apps even when the OS X desktop and web browsers look oversaturated.
But like Charles says, other features compensate for this. For example, the Adobe RGB and sRGB modes are just two of the built-in presets for the (highly accurate and factory verified) internal calibration. But you also get to store a number of your own presets. I do not even use the factory Adobe RGB and sRGB presets. I made two of my own. One I calibrated for "widest possible" gamut for photo work, at a certain luminance, the other an "sRGB emulation" preset at a completely different luminance. Because I didn't agree with the luminance of the factory presets. When you make a preset you can set the luminance, white point, gamut, etc. so if you don't like the factory presets it doesn't matter, just make your own. (Note: I am using the PA272-SV with one of the calibrator devices that actually talks to the internal monitor circuitry, so I am not sure how well this works if you get the more commonPA272 model without it and use a cheaper calibrator that only creates a profile without talking to the monitor.)
The factory Adobe RGB and sRGB presets are very useful if you don't want to get into customizing the color specifications, but any limitations they have are easily understood and remedied if you have some knowledge of color management concepts and have a compatible integrated calibrator.
What you might glean from this is that the true value of the PA272 is if you are an experienced graphics user who knows enough about color to get the most out of the monitor. If you are a casual user who just wants to flip back and forth between sRGB and Adobe RGB once in a while, things might not always work as expected and a more conventional monitors could have been a better deal. If you understand how the PA272 is designed relative to color science, and in terms of how it's an internal calibration compared to the external profiling of most monitors, the sRGB mode makes a lot of sense.
chris.dg wrote:
The PA272 has a number of key features for me: the 2560x1600 native resolution, the built-in KVM switch, DisplayPort, wide-gamut for when I want it,etc. But the only thing holding me back is whether or not I should simply stick with a "normal" gamut range monitor because that is where I'll spend most of my time. Cost is not so much of an issue, i just want the best of both worlds, if it even exists.
Although you said cost is not an issue there seem to be a decent selection of monitors out there that would get you similar features, without wide gamut, for a lot less money. Monitors with that resolution, DisplayPort, pivoting, etc. are now widely available.
One last note: Minor problems have been observed with these monitors in OS X Mavericks. I think they started turning up in 10.9.2. It still performs the same but some things don't work right and it looks like Apple's fault:
OS X 10.9.2 Breaks Display Support with NEC Displays: Sleep, 90° Rotation Failure
Apparently all is needed is for Apple to fix it in the next release, whenever that is. A later post on that same blog indicates that a fix may be coming from Apple. Again, these problems do not stop the monitor from doing its job so if you want one you should still buy it. -
Hi.
I am a graphic designer and I am currently working with a MacBook Pro 13 inch (mid 2010) with Mac OSX 10.8.3 and an external Dell U2412M display. I use mostly Adobe Photoshop CS6 and Adobe Illustrator CS6.
Since I would like to add another external display I have recently ordered the Matrox DualHead2Go DP Edition.
I am however, unsure of which 2nd external display is better for me: another Dell U2412M display (which is sRGB) or the Dell U2413 display which is a wide gamut display.
The main reason for my indecision is as follows: since the MacBook Pro doesn't allow for a graphics card exchange, the Matrox DualHead2Go is really the only feasible option to another external display. But this product has a caveat and that is that the operating system doesn't really "see" two independent displays. It "sees" a desktop space that occupies two displays but it thinks of it as a single big display. As such, I don't think I will, for example, be able to use 2 different display calibration profiles simultaneously.
Also, since my system isn't a true 10-bit system (the graphics card on the MacBook Pro is a Nvidia GeForce 320M) I wonder if I will see any difference in the total number of colours displayed by the wide gamut display or if I will still be seeing "only" 16 million colours but just a different 16 million than I see on the sRGB display.
Having a wide gamut display running alongside a normal gamut display seems to me like a good solution since I could just focus on the best display for color critical work and use the other one to preview things on a normal gamut display. But considering the calibration profile issue, would both displays render very different colours or would the difference be minimal if, for example, I set the wide gamut display to its sRGB emulation mode?
If I got a colorimeter to calibrate my display(s), would the Matrox DualHead2Go caveat still be there?
If anyone has tried a similar setup I would really appreciate your feedback since I am really lost on this issue, even after extensively researching it online.
Thank you.Lucypug08 wrote:
So really, I don't even see how there could be a solution, other than getting a new monitor that isn't wide gamut. But I'm open for any advice. (by the way, if you dont' need to work on RAW files, and just go straight to jpeg, you're fine._ -Chance
Nope...sorry, you're all screwed up. First off, what display and how is it profiled? What OS? Since you have dual displays, are you absolutely sure your video card supports different profiles for multiple displays? On Mac, no problem, on Windows that depends on your vid card.
Camera Raw (and Photoshop) get's it's ability to accurately display you image directly from your display profile. If something is not showing up accurately in ACR or PS, then it's not the application's fault. ACR/Photoshop/Lightroom should all display your images accurately (and the same BTW). If it doesn't then it's something on your system that is breaking down...
BTW, you really don't seem to understand how ACR/PS and color management work. You need to do some reading on that. ACR takes the raw image, demosiaces the image and applies certain default correction. It then takes the image color (internally ProPhoto RGB with a linear gamma) and transforms the image data by way of your display profile for accurate display in the ACR preview. It's the display profile that needs to be accurate...ACR will only provide a preview based on the display profile and if that's hosed the preview is hosed.
I work with wide gamut displays (NEC) and I have zero problems dealing with color management. My images look accurate on the display and in print. So, if YOU can't get an accurate preview display on your monitors, you need to look inwards, not outwards. -
I'm trying to decide on a mac mini or whether I need a mac pro. How would I hook up two monitors to a mini ? I have an NEC PA241W with a Display Port, DVI and VGA array of graphic ports and a Samsung with a DVI and VGA port. I use them quite a bit for photo imaging editing.
Apple is telling me I need to go from the Thunderbolt mini output to the NEC and then go from the NEC to the Samsung for daisy chaining. I don't know if I could go into the monitor via Display Port and out to the Samsung via the NEC DVI port ? Or do I need to find a 3rd party "box" that will manage the connections and/or daisy chaining ?? Anybody know or have ideas ?
Thanks
Tony MMac mini comes with a HDMI to DVI Adapter. Then you can connect the NEC PA241W with the Display Port and the Samsung with DVI Port.
The Mini DisplayPort to DisplayPort adapter is like this:
http://estore.circuitassembly.com/products/Mini-Displayport-to-Displayport-Adapt er-Cable.html?setCurrencyId=1 -
[solved] ThinkPad connect with extern Monitor Problem
Hello community
I have installed arch on my T420 integrated HD 3000 and i have the Problem that when i start arch and the boot messages comes i can see the deamon starts ok,ok,ok who should be on the right side but on the NEC they was displayed 5 cm inside. Also when iam on the console and i type dmesg all the output scroll down and broke 5 cm from the roof. And when iam on openbox and i will maximize one window it would be maximized on the size from the Laptop LCD.
I have made an .xinitrc
#!/bin/sh
# ~/.xinitrc
# Executed by startx (run your window manager from here)
#xrandr --output DP2 --auto --output LVDS --right-of LVDS
#xrandr --output DP1 --auto --output LVDS --auto --same-as DP1
xrandr -d DP2 -s 1900x1200
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
# exec gnome-session
# exec startkde
# exec startxfce4
and here is my Xorg.0.log
[ 81.298]
X.Org X Server 1.12.4
Release Date: 2012-08-27
[ 81.298] X Protocol Version 11, Revision 0
[ 81.298] Build Operating System: Linux 3.4.8-1-ARCH x86_64
[ 81.298] Current Operating System: Linux bullitt 3.5.4-1-ARCH #1 SMP PREEMPT Sat Sep 15 08:12:04 CEST 2012 x86_64
[ 81.298] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=7b8780ba-278c-4d61-a1ec-ba2a6f96c6ba ro quiet
[ 81.299] Build Date: 27 August 2012 08:04:39AM
[ 81.299]
[ 81.299] Current version of pixman: 0.26.2
[ 81.299] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 81.299] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 81.306] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Oct 7 16:33:34 2012
[ 81.307] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 81.308] (==) No Layout section. Using the first Screen section.
[ 81.308] (==) No screen section available. Using defaults.
[ 81.308] (**) |-->Screen "Default Screen Section" (0)
[ 81.308] (**) | |-->Monitor "<default monitor>"
[ 81.308] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 81.308] (==) Automatically adding devices
[ 81.308] (==) Automatically enabling devices
[ 81.308] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 81.308] Entry deleted from font path.
[ 81.308] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 81.308] Entry deleted from font path.
[ 81.308] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 81.308] Entry deleted from font path.
[ 81.308] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 81.308] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 81.308] Entry deleted from font path.
[ 81.308] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 81.308] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/
[ 81.308] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 81.308] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 81.308] (II) Loader magic: 0x7c8b00
[ 81.308] (II) Module ABI versions:
[ 81.308] X.Org ANSI C Emulation: 0.4
[ 81.308] X.Org Video Driver: 12.1
[ 81.308] X.Org XInput driver : 16.0
[ 81.308] X.Org Server Extension : 6.0
[ 81.308] (--) PCI:*(0:0:2:0) 8086:0126:17aa:21ce rev 9, Mem @ 0xf0000000/4194304, 0xe0000000/268435456, I/O @ 0x00005000/64
[ 81.308] (II) Open ACPI successful (/var/run/acpid.socket)
[ 81.308] (II) LoadModule: "extmod"
[ 81.309] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 81.309] (II) Module extmod: vendor="X.Org Foundation"
[ 81.309] compiled for 1.12.4, module version = 1.0.0
[ 81.309] Module class: X.Org Server Extension
[ 81.309] ABI class: X.Org Server Extension, version 6.0
[ 81.309] (II) Loading extension MIT-SCREEN-SAVER
[ 81.309] (II) Loading extension XFree86-VidModeExtension
[ 81.309] (II) Loading extension XFree86-DGA
[ 81.309] (II) Loading extension DPMS
[ 81.309] (II) Loading extension XVideo
[ 81.309] (II) Loading extension XVideo-MotionCompensation
[ 81.309] (II) Loading extension X-Resource
[ 81.309] (II) LoadModule: "dbe"
[ 81.309] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 81.309] (II) Module dbe: vendor="X.Org Foundation"
[ 81.309] compiled for 1.12.4, module version = 1.0.0
[ 81.309] Module class: X.Org Server Extension
[ 81.309] ABI class: X.Org Server Extension, version 6.0
[ 81.309] (II) Loading extension DOUBLE-BUFFER
[ 81.309] (II) LoadModule: "glx"
[ 81.309] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 81.309] (II) Module glx: vendor="X.Org Foundation"
[ 81.309] compiled for 1.12.4, module version = 1.0.0
[ 81.309] ABI class: X.Org Server Extension, version 6.0
[ 81.309] (==) AIGLX enabled
[ 81.309] (II) Loading extension GLX
[ 81.309] (II) LoadModule: "record"
[ 81.309] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 81.309] (II) Module record: vendor="X.Org Foundation"
[ 81.309] compiled for 1.12.4, module version = 1.13.0
[ 81.309] Module class: X.Org Server Extension
[ 81.309] ABI class: X.Org Server Extension, version 6.0
[ 81.309] (II) Loading extension RECORD
[ 81.309] (II) LoadModule: "dri"
[ 81.309] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 81.309] (II) Module dri: vendor="X.Org Foundation"
[ 81.309] compiled for 1.12.4, module version = 1.0.0
[ 81.309] ABI class: X.Org Server Extension, version 6.0
[ 81.309] (II) Loading extension XFree86-DRI
[ 81.309] (II) LoadModule: "dri2"
[ 81.309] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 81.309] (II) Module dri2: vendor="X.Org Foundation"
[ 81.309] compiled for 1.12.4, module version = 1.2.0
[ 81.309] ABI class: X.Org Server Extension, version 6.0
[ 81.309] (II) Loading extension DRI2
[ 81.309] (==) Matched intel as autoconfigured driver 0
[ 81.309] (==) Matched vesa as autoconfigured driver 1
[ 81.309] (==) Matched fbdev as autoconfigured driver 2
[ 81.309] (==) Assigned the driver to the xf86ConfigLayout
[ 81.309] (II) LoadModule: "intel"
[ 81.310] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 81.310] (II) Module intel: vendor="X.Org Foundation"
[ 81.310] compiled for 1.12.4, module version = 2.20.9
[ 81.310] Module class: X.Org Video Driver
[ 81.310] ABI class: X.Org Video Driver, version 12.1
[ 81.310] (II) LoadModule: "vesa"
[ 81.310] (WW) Warning, couldn't open module vesa
[ 81.310] (II) UnloadModule: "vesa"
[ 81.310] (II) Unloading vesa
[ 81.310] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 81.310] (II) LoadModule: "fbdev"
[ 81.310] (WW) Warning, couldn't open module fbdev
[ 81.310] (II) UnloadModule: "fbdev"
[ 81.310] (II) Unloading fbdev
[ 81.310] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 81.310] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
Ivybridge Server (GT2), Haswell Desktop (GT1), Haswell Desktop (GT2),
Haswell Desktop (GT2+), Haswell Mobile (GT1), Haswell Mobile (GT2),
Haswell Mobile (GT2+), Haswell Server (GT1), Haswell Server (GT2),
Haswell Server (GT2+), Haswell SDV Desktop (GT1),
Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT2+),
Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
Haswell SDV Mobile (GT2+), Haswell SDV Server (GT1),
Haswell SDV Server (GT2), Haswell SDV Server (GT2+),
Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
Haswell ULT Desktop (GT2+), Haswell ULT Mobile (GT1),
Haswell ULT Mobile (GT2), Haswell ULT Mobile (GT2+),
Haswell ULT Server (GT1), Haswell ULT Server (GT2),
Haswell ULT Server (GT2+), Haswell CRW Desktop (GT1),
Haswell CRW Desktop (GT2), Haswell CRW Desktop (GT2+),
Haswell CRW Mobile (GT1), Haswell CRW Mobile (GT2),
Haswell CRW Mobile (GT2+), Haswell CRW Server (GT1),
Haswell CRW Server (GT2), Haswell CRW Server (GT2+),
ValleyView PO board
[ 81.310] (--) using VT number 7
[ 81.313] drmOpenDevice: node name is /dev/dri/card0
[ 81.314] drmOpenDevice: open result is 8, (OK)
[ 81.314] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
[ 81.314] drmOpenDevice: node name is /dev/dri/card0
[ 81.314] drmOpenDevice: open result is 8, (OK)
[ 81.314] drmOpenByBusid: drmOpenMinor returns 8
[ 81.314] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[ 81.314] drmOpenDevice: node name is /dev/dri/card0
[ 81.314] drmOpenDevice: open result is 9, (OK)
[ 81.314] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
[ 81.314] drmOpenDevice: node name is /dev/dri/card0
[ 81.314] drmOpenDevice: open result is 9, (OK)
[ 81.314] drmOpenByBusid: drmOpenMinor returns 9
[ 81.314] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[ 81.314] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 81.314] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 81.314] (==) intel(0): RGB weight 888
[ 81.314] (==) intel(0): Default visual is TrueColor
[ 81.314] (--) intel(0): Integrated Graphics Chipset: Intel(R) Sandybridge Mobile (GT2+)
[ 81.314] (**) intel(0): Relaxed fencing enabled
[ 81.314] (**) intel(0): Wait on SwapBuffers? enabled
[ 81.314] (**) intel(0): Triple buffering? enabled
[ 81.314] (**) intel(0): Framebuffer tiled
[ 81.315] (**) intel(0): Pixmaps tiled
[ 81.315] (**) intel(0): 3D buffers tiled
[ 81.315] (**) intel(0): SwapBuffers wait enabled
[ 81.315] (==) intel(0): video overlay key set to 0x101fe
[ 81.315] (II) intel(0): Output LVDS1 has no monitor section
[ 81.315] (--) intel(0): found backlight control interface /sys/class/backlight/acpi_video0
[ 81.315] (II) intel(0): Output VGA1 has no monitor section
[ 81.340] (II) intel(0): Output HDMI1 has no monitor section
[ 81.380] (II) intel(0): Output DP1 has no monitor section
[ 81.393] (II) intel(0): Output HDMI2 has no monitor section
[ 81.406] (II) intel(0): Output HDMI3 has no monitor section
[ 81.464] (II) intel(0): Output DP2 has no monitor section
[ 81.506] (II) intel(0): Output DP3 has no monitor section
[ 81.507] (II) intel(0): EDID for output LVDS1
[ 81.507] (II) intel(0): Manufacturer: AUO Model: 213e Serial#: 0
[ 81.507] (II) intel(0): Year: 2010 Week: 33
[ 81.507] (II) intel(0): EDID Version: 1.4
[ 81.507] (II) intel(0): Digital Display Input
[ 81.507] (II) intel(0): 6 bits per channel
[ 81.507] (II) intel(0): Digital interface is undefined
[ 81.507] (II) intel(0): Max Image Size [cm]: horiz.: 31 vert.: 17
[ 81.507] (II) intel(0): Gamma: 2.20
[ 81.507] (II) intel(0): No DPMS capabilities specified
[ 81.507] (II) intel(0): Supported color encodings: RGB 4:4:4
[ 81.507] (II) intel(0): First detailed timing is preferred mode
[ 81.507] (II) intel(0): Preferred mode is native pixel format and refresh rate
[ 81.507] (II) intel(0): redX: 0.610 redY: 0.350 greenX: 0.320 greenY: 0.560
[ 81.507] (II) intel(0): blueX: 0.150 blueY: 0.130 whiteX: 0.313 whiteY: 0.329
[ 81.507] (II) intel(0): Manufacturer's mask: 0
[ 81.507] (II) intel(0): Supported detailed timing:
[ 81.507] (II) intel(0): clock: 110.0 MHz Image Size: 309 x 174 mm
[ 81.507] (II) intel(0): h_active: 1600 h_sync: 1664 h_sync_end 1706 h_blank_end 2010 h_border: 0
[ 81.507] (II) intel(0): v_active: 900 v_sync: 903 v_sync_end 906 v_blanking: 912 v_border: 0
[ 81.507] (II) intel(0): Supported detailed timing:
[ 81.507] (II) intel(0): clock: 73.3 MHz Image Size: 309 x 174 mm
[ 81.507] (II) intel(0): h_active: 1600 h_sync: 1664 h_sync_end 1706 h_blank_end 2010 h_border: 0
[ 81.507] (II) intel(0): v_active: 900 v_sync: 903 v_sync_end 906 v_blanking: 912 v_border: 0
[ 81.507] (II) intel(0): AUO
[ 81.507] (II) intel(0): B140RW02 V1
[ 81.507] (II) intel(0): EDID (in hex):
[ 81.507] (II) intel(0): 00ffffffffffff0006af3e2100000000
[ 81.507] (II) intel(0): 21140104901f11780261959c59528f26
[ 81.507] (II) intel(0): 21505400000001010101010101010101
[ 81.507] (II) intel(0): 010101010101f82a409a61840c30402a
[ 81.507] (II) intel(0): 330035ae10000018a51c409a61840c30
[ 81.507] (II) intel(0): 402a330035ae10000018000000fe0041
[ 81.507] (II) intel(0): 554f0a202020202020202020000000fe
[ 81.507] (II) intel(0): 004231343052573032205631200a00d0
[ 81.507] (II) intel(0): EDID vendor "AUO", prod id 8510
[ 81.507] (II) intel(0): Printing DDC gathered Modelines:
[ 81.508] (II) intel(0): Modeline "1600x900"x0.0 110.00 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (54.7 kHz eP)
[ 81.508] (II) intel(0): Modeline "1600x900"x0.0 73.33 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (36.5 kHz e)
[ 81.508] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported)
[ 81.508] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 81.508] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 81.508] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported)
[ 81.508] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported)
[ 81.508] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported)
[ 81.508] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported)
[ 81.508] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported)
[ 81.508] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported)
[ 81.508] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported)
[ 81.508] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported)
[ 81.508] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported)
[ 81.508] (II) intel(0): Printing probed modes for output LVDS1
[ 81.508] (II) intel(0): Modeline "1600x900"x60.0 110.00 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (54.7 kHz eP)
[ 81.508] (II) intel(0): Modeline "1600x900"x40.0 73.33 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (36.5 kHz e)
[ 81.508] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz d)
[ 81.508] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz d)
[ 81.508] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz d)
[ 81.508] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz d)
[ 81.508] (II) intel(0): EDID for output VGA1
[ 81.533] (II) intel(0): EDID for output HDMI1
[ 81.573] (II) intel(0): EDID for output DP1
[ 81.586] (II) intel(0): EDID for output HDMI2
[ 81.600] (II) intel(0): EDID for output HDMI3
[ 81.657] (II) intel(0): EDID for output DP2
[ 81.657] (II) intel(0): Manufacturer: NEC Model: 67d1 Serial#: 0
[ 81.657] (II) intel(0): Year: 2011 Week: 33
[ 81.657] (II) intel(0): EDID Version: 1.4
[ 81.657] (II) intel(0): Digital Display Input
[ 81.657] (II) intel(0): 10 bits per channel
[ 81.657] (II) intel(0): Digital interface is DisplayPort
[ 81.657] (II) intel(0): Max Image Size [cm]: horiz.: 52 vert.: 32
[ 81.657] (II) intel(0): Gamma: 2.20
[ 81.657] (II) intel(0): DPMS capabilities: StandBy Suspend Off
[ 81.657] (II) intel(0): Supported color encodings: RGB 4:4:4
[ 81.657] (II) intel(0): First detailed timing is preferred mode
[ 81.657] (II) intel(0): Preferred mode is native pixel format and refresh rate
[ 81.657] (II) intel(0): redX: 0.679 redY: 0.310 greenX: 0.210 greenY: 0.686
[ 81.657] (II) intel(0): blueX: 0.149 blueY: 0.047 whiteX: 0.313 whiteY: 0.329
[ 81.657] (II) intel(0): Supported established timings:
[ 81.657] (II) intel(0): 720x400@70Hz
[ 81.657] (II) intel(0): 640x480@60Hz
[ 81.657] (II) intel(0): 640x480@67Hz
[ 81.657] (II) intel(0): 640x480@72Hz
[ 81.657] (II) intel(0): 640x480@75Hz
[ 81.657] (II) intel(0): 800x600@56Hz
[ 81.657] (II) intel(0): 800x600@60Hz
[ 81.657] (II) intel(0): 800x600@72Hz
[ 81.657] (II) intel(0): 800x600@75Hz
[ 81.657] (II) intel(0): 832x624@75Hz
[ 81.657] (II) intel(0): 1024x768@60Hz
[ 81.657] (II) intel(0): 1024x768@70Hz
[ 81.657] (II) intel(0): 1024x768@75Hz
[ 81.657] (II) intel(0): 1280x1024@75Hz
[ 81.657] (II) intel(0): 1152x864@75Hz
[ 81.657] (II) intel(0): Manufacturer's mask: 0
[ 81.657] (II) intel(0): Supported standard timings:
[ 81.657] (II) intel(0): #0: hsize: 1280 vsize 720 refresh: 60 vid: 49281
[ 81.657] (II) intel(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 81.657] (II) intel(0): #2: hsize: 1400 vsize 1050 refresh: 60 vid: 16528
[ 81.657] (II) intel(0): #3: hsize: 1360 vsize 765 refresh: 60 vid: 49291
[ 81.657] (II) intel(0): #4: hsize: 1440 vsize 900 refresh: 60 vid: 149
[ 81.657] (II) intel(0): #5: hsize: 1600 vsize 1200 refresh: 60 vid: 16553
[ 81.657] (II) intel(0): #6: hsize: 1680 vsize 1050 refresh: 60 vid: 179
[ 81.657] (II) intel(0): #7: hsize: 1920 vsize 1200 refresh: 60 vid: 209
[ 81.657] (II) intel(0): Supported detailed timing:
[ 81.657] (II) intel(0): clock: 154.0 MHz Image Size: 518 x 324 mm
[ 81.657] (II) intel(0): h_active: 1920 h_sync: 1968 h_sync_end 2000 h_blank_end 2080 h_border: 0
[ 81.657] (II) intel(0): v_active: 1200 v_sync: 1203 v_sync_end 1209 v_blanking: 1235 v_border: 0
[ 81.657] (II) intel(0): Ranges: V min: 50 V max: 85 Hz, H min: 31 H max: 92 kHz, PixClock max 165 MHz
[ 81.657] (II) intel(0): Monitor name: PA241W
[ 81.657] (II) intel(0): Serial No: 18107120UB
[ 81.657] (II) intel(0): EDID (in hex):
[ 81.657] (II) intel(0): 00ffffffffffff0038a3d16700000000
[ 81.657] (II) intel(0): 21150104b5342078e2de45ad4f35af26
[ 81.657] (II) intel(0): 0c5054bfef8081c0818090408bc09500
[ 81.657] (II) intel(0): a940b300d100283c80a070b023403020
[ 81.657] (II) intel(0): 360006442100001a000000fd0032551f
[ 81.657] (II) intel(0): 5c10000a202020202020000000fc0050
[ 81.657] (II) intel(0): 41323431570a202020202020000000ff
[ 81.657] (II) intel(0): 00313831303731323055420a2020004b
[ 81.657] (II) intel(0): Printing probed modes for output DP2
[ 81.657] (II) intel(0): Modeline "1920x1200"x60.0 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync (74.0 kHz eP)
[ 81.657] (II) intel(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 81.657] (II) intel(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
[ 81.657] (II) intel(0): Modeline "1680x945"x60.0 131.48 1680 1784 1960 2240 945 946 949 978 -hsync +vsync (58.7 kHz)
[ 81.657] (II) intel(0): Modeline "1400x1050"x74.9 156.00 1400 1504 1648 1896 1050 1053 1057 1099 -hsync +vsync (82.3 kHz e)
[ 81.657] (II) intel(0): Modeline "1400x1050"x60.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
[ 81.657] (II) intel(0): Modeline "1600x900"x60.0 118.96 1600 1696 1864 2128 900 901 904 932 -hsync +vsync (55.9 kHz)
[ 81.657] (II) intel(0): Modeline "1280x1024"x85.0 157.50 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync (91.1 kHz e)
[ 81.657] (II) intel(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 81.657] (II) intel(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 81.657] (II) intel(0): Modeline "1440x900"x84.8 157.00 1440 1544 1696 1952 900 903 909 948 -hsync +vsync (80.4 kHz e)
[ 81.657] (II) intel(0): Modeline "1440x900"x75.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vsync (70.6 kHz e)
[ 81.657] (II) intel(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e)
[ 81.657] (II) intel(0): Modeline "1280x960"x85.0 148.50 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync (85.9 kHz e)
[ 81.657] (II) intel(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 81.657] (II) intel(0): Modeline "1360x768"x59.8 84.75 1366 1431 1567 1776 768 771 781 798 -hsync +vsync (47.7 kHz)
[ 81.657] (II) intel(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
[ 81.657] (II) intel(0): Modeline "1280x800"x84.9 122.50 1280 1360 1496 1712 800 803 809 843 -hsync +vsync (71.6 kHz e)
[ 81.657] (II) intel(0): Modeline "1280x800"x74.9 106.50 1280 1360 1488 1696 800 803 809 838 -hsync +vsync (62.8 kHz e)
[ 81.657] (II) intel(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
[ 81.657] (II) intel(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 81.657] (II) intel(0): Modeline "1280x768"x84.8 117.50 1280 1360 1496 1712 768 771 778 809 -hsync +vsync (68.6 kHz e)
[ 81.657] (II) intel(0): Modeline "1280x768"x74.9 102.25 1280 1360 1488 1696 768 771 778 805 +hsync -vsync (60.3 kHz e)
[ 81.657] (II) intel(0): Modeline "1280x768"x59.9 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e)
[ 81.657] (II) intel(0): Modeline "1280x720"x60.0 74.44 1280 1336 1472 1664 720 721 724 746 -hsync +vsync (44.7 kHz)
[ 81.658] (II) intel(0): Modeline "1024x768"x85.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz e)
[ 81.658] (II) intel(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[ 81.658] (II) intel(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 81.658] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 81.658] (II) intel(0): Modeline "1024x576"x60.0 46.97 1024 1064 1168 1312 576 577 580 597 -hsync +vsync (35.8 kHz)
[ 81.658] (II) intel(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 81.658] (II) intel(0): Modeline "800x600"x85.1 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz e)
[ 81.658] (II) intel(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 81.658] (II) intel(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 81.658] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 81.658] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 81.658] (II) intel(0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e)
[ 81.658] (II) intel(0): Modeline "640x480"x85.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz e)
[ 81.658] (II) intel(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
[ 81.658] (II) intel(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 81.658] (II) intel(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
[ 81.658] (II) intel(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 81.658] (II) intel(0): Modeline "720x400"x85.0 35.50 720 756 828 936 400 401 404 446 -hsync +vsync (37.9 kHz e)
[ 81.658] (II) intel(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 81.658] (II) intel(0): Modeline "640x400"x85.1 31.50 640 672 736 832 400 401 404 445 -hsync +vsync (37.9 kHz e)
[ 81.658] (II) intel(0): Modeline "640x350"x85.1 31.50 640 672 736 832 350 382 385 445 +hsync -vsync (37.9 kHz e)
[ 81.700] (II) intel(0): EDID for output DP3
[ 81.700] (II) intel(0): Output LVDS1 connected
[ 81.700] (II) intel(0): Output VGA1 disconnected
[ 81.700] (II) intel(0): Output HDMI1 disconnected
[ 81.700] (II) intel(0): Output DP1 disconnected
[ 81.700] (II) intel(0): Output HDMI2 disconnected
[ 81.700] (II) intel(0): Output HDMI3 disconnected
[ 81.700] (II) intel(0): Output DP2 connected
[ 81.700] (II) intel(0): Output DP3 disconnected
[ 81.700] (II) intel(0): Using exact sizes for initial modes
[ 81.700] (II) intel(0): Output LVDS1 using initial mode 1600x900
[ 81.700] (II) intel(0): Output DP2 using initial mode 1600x900
[ 81.700] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 81.700] (II) intel(0): Kernel page flipping support detected, enabling
[ 81.700] (**) intel(0): Display dimensions: (310, 170) mm
[ 81.700] (**) intel(0): DPI set to (131, 134)
[ 81.700] (II) Loading sub module "fb"
[ 81.700] (II) LoadModule: "fb"
[ 81.701] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 81.701] (II) Module fb: vendor="X.Org Foundation"
[ 81.701] compiled for 1.12.4, module version = 1.0.0
[ 81.701] ABI class: X.Org ANSI C Emulation, version 0.4
[ 81.701] (II) Loading sub module "dri2"
[ 81.701] (II) LoadModule: "dri2"
[ 81.701] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 81.701] (II) Module dri2: vendor="X.Org Foundation"
[ 81.701] compiled for 1.12.4, module version = 1.2.0
[ 81.701] ABI class: X.Org Server Extension, version 6.0
[ 81.701] (==) Depth 24 pixmap format is 32 bpp
[ 81.702] (II) intel(0): [DRI2] Setup complete
[ 81.702] (II) intel(0): [DRI2] DRI driver: i965
[ 81.702] (II) intel(0): Allocated new frame buffer 1600x900 stride 6656, tiled
[ 81.704] (II) UXA(0): Driver registered support for the following operations:
[ 81.704] (II) solid
[ 81.704] (II) copy
[ 81.704] (II) composite (RENDER acceleration)
[ 81.704] (II) put_image
[ 81.704] (II) get_image
[ 81.704] (==) intel(0): Backing store disabled
[ 81.704] (==) intel(0): Silken mouse enabled
[ 81.704] (II) intel(0): Initializing HW Cursor
[ 81.704] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 81.707] (==) intel(0): DPMS enabled
[ 81.707] (==) intel(0): Intel XvMC decoder enabled
[ 81.707] (II) intel(0): Set up textured video
[ 81.707] (II) intel(0): [XvMC] xvmc_vld driver initialized.
[ 81.707] (II) intel(0): direct rendering: DRI2 Enabled
[ 81.707] (==) intel(0): hotplug detection: "enabled"
[ 82.106] (--) RandR disabled
[ 82.107] (II) Initializing built-in extension Generic Event Extension
[ 82.107] (II) Initializing built-in extension SHAPE
[ 82.107] (II) Initializing built-in extension MIT-SHM
[ 82.107] (II) Initializing built-in extension XInputExtension
[ 82.107] (II) Initializing built-in extension XTEST
[ 82.107] (II) Initializing built-in extension BIG-REQUESTS
[ 82.107] (II) Initializing built-in extension SYNC
[ 82.107] (II) Initializing built-in extension XKEYBOARD
[ 82.107] (II) Initializing built-in extension XC-MISC
[ 82.107] (II) Initializing built-in extension SECURITY
[ 82.107] (II) Initializing built-in extension XINERAMA
[ 82.107] (II) Initializing built-in extension XFIXES
[ 82.107] (II) Initializing built-in extension RENDER
[ 82.107] (II) Initializing built-in extension RANDR
[ 82.107] (II) Initializing built-in extension COMPOSITE
[ 82.107] (II) Initializing built-in extension DAMAGE
[ 82.119] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 82.119] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 82.119] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 82.119] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 82.119] (II) AIGLX: Loaded and initialized i965
[ 82.119] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 82.119] (II) intel(0): Setting screen physical size to 423 x 238
[ 82.158] (II) config/udev: Adding input device Power Button (/dev/input/event4)
[ 82.158] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 82.158] (II) LoadModule: "evdev"
[ 82.159] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 82.159] (II) Module evdev: vendor="X.Org Foundation"
[ 82.159] compiled for 1.12.3.901, module version = 2.7.3
[ 82.159] Module class: X.Org XInput Driver
[ 82.159] ABI class: X.Org XInput driver, version 16.0
[ 82.159] (II) Using input driver 'evdev' for 'Power Button'
[ 82.159] (**) Power Button: always reports core events
[ 82.159] (**) evdev: Power Button: Device: "/dev/input/event4"
[ 82.159] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 82.159] (--) evdev: Power Button: Found keys
[ 82.159] (II) evdev: Power Button: Configuring as keyboard
[ 82.159] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event4"
[ 82.160] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 82.160] (**) Option "xkb_rules" "evdev"
[ 82.160] (**) Option "xkb_model" "evdev"
[ 82.160] (**) Option "xkb_layout" "de"
[ 82.160] (**) Option "xkb_variant" "nodeadkeys"
[ 82.193] (II) config/udev: Adding input device Video Bus (/dev/input/event12)
[ 82.193] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 82.193] (II) Using input driver 'evdev' for 'Video Bus'
[ 82.193] (**) Video Bus: always reports core events
[ 82.193] (**) evdev: Video Bus: Device: "/dev/input/event12"
[ 82.193] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 82.193] (--) evdev: Video Bus: Found keys
[ 82.193] (II) evdev: Video Bus: Configuring as keyboard
[ 82.193] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input12/event12"
[ 82.193] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 82.193] (**) Option "xkb_rules" "evdev"
[ 82.193] (**) Option "xkb_model" "evdev"
[ 82.193] (**) Option "xkb_layout" "de"
[ 82.193] (**) Option "xkb_variant" "nodeadkeys"
[ 82.195] (II) config/udev: Adding input device Lid Switch (/dev/input/event2)
[ 82.195] (II) No input driver specified, ignoring this device.
[ 82.195] (II) This device may have been added with another device file.
[ 82.195] (II) config/udev: Adding input device Sleep Button (/dev/input/event3)
[ 82.195] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 82.195] (II) Using input driver 'evdev' for 'Sleep Button'
[ 82.195] (**) Sleep Button: always reports core events
[ 82.195] (**) evdev: Sleep Button: Device: "/dev/input/event3"
[ 82.195] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[ 82.195] (--) evdev: Sleep Button: Found keys
[ 82.195] (II) evdev: Sleep Button: Configuring as keyboard
[ 82.195] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input3/event3"
[ 82.195] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
[ 82.195] (**) Option "xkb_rules" "evdev"
[ 82.196] (**) Option "xkb_model" "evdev"
[ 82.196] (**) Option "xkb_layout" "de"
[ 82.196] (**) Option "xkb_variant" "nodeadkeys"
[ 82.197] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/event1)
[ 82.197] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "evdev pointer catchall"
[ 82.197] (II) Using input driver 'evdev' for 'Logitech USB-PS/2 Optical Mouse'
[ 82.197] (**) Logitech USB-PS/2 Optical Mouse: always reports core events
[ 82.197] (**) evdev: Logitech USB-PS/2 Optical Mouse: Device: "/dev/input/event1"
[ 82.197] (--) evdev: Logitech USB-PS/2 Optical Mouse: Vendor 0x46d Product 0xc01e
[ 82.197] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found 12 mouse buttons
[ 82.197] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found scroll wheel(s)
[ 82.197] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found relative axes
[ 82.197] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found x and y relative axes
[ 82.197] (II) evdev: Logitech USB-PS/2 Optical Mouse: Configuring as mouse
[ 82.197] (II) evdev: Logitech USB-PS/2 Optical Mouse: Adding scrollwheel support
[ 82.197] (**) evdev: Logitech USB-PS/2 Optical Mouse: YAxisMapping: buttons 4 and 5
[ 82.197] (**) evdev: Logitech USB-PS/2 Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 82.197] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input1/event1"
[ 82.197] (II) XINPUT: Adding extended input device "Logitech USB-PS/2 Optical Mouse" (type: MOUSE, id 9)
[ 82.197] (II) evdev: Logitech USB-PS/2 Optical Mouse: initialized for relative axes.
[ 82.197] (**) Logitech USB-PS/2 Optical Mouse: (accel) keeping acceleration scheme 1
[ 82.197] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration profile 0
[ 82.197] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration factor: 2.000
[ 82.197] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration threshold: 4
[ 82.197] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/mouse0)
[ 82.197] (II) No input driver specified, ignoring this device.
[ 82.197] (II) This device may have been added with another device file.
[ 82.197] (II) config/udev: Adding input device Integrated Camera (/dev/input/event10)
[ 82.197] (**) Integrated Camera: Applying InputClass "evdev keyboard catchall"
[ 82.197] (II) Using input driver 'evdev' for 'Integrated Camera'
[ 82.197] (**) Integrated Camera: always reports core events
[ 82.197] (**) evdev: Integrated Camera: Device: "/dev/input/event10"
[ 82.197] (--) evdev: Integrated Camera: Vendor 0x4f2 Product 0xb221
[ 82.197] (--) evdev: Integrated Camera: Found keys
[ 82.197] (II) evdev: Integrated Camera: Configuring as keyboard
[ 82.197] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input10/event10"
[ 82.197] (II) XINPUT: Adding extended input device "Integrated Camera" (type: KEYBOARD, id 10)
[ 82.197] (**) Option "xkb_rules" "evdev"
[ 82.197] (**) Option "xkb_model" "evdev"
[ 82.197] (**) Option "xkb_layout" "de"
[ 82.197] (**) Option "xkb_variant" "nodeadkeys"
[ 82.198] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event13)
[ 82.198] (II) No input driver specified, ignoring this device.
[ 82.198] (II) This device may have been added with another device file.
[ 82.198] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=8 (/dev/input/event14)
[ 82.198] (II) No input driver specified, ignoring this device.
[ 82.198] (II) This device may have been added with another device file.
[ 82.198] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7 (/dev/input/event15)
[ 82.198] (II) No input driver specified, ignoring this device.
[ 82.198] (II) This device may have been added with another device file.
[ 82.198] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event16)
[ 82.198] (II) No input driver specified, ignoring this device.
[ 82.198] (II) This device may have been added with another device file.
[ 82.198] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event17)
[ 82.198] (II) No input driver specified, ignoring this device.
[ 82.198] (II) This device may have been added with another device file.
[ 82.198] (II) config/udev: Adding input device HDA Intel PCH Dock Mic (/dev/input/event18)
[ 82.198] (II) No input driver specified, ignoring this device.
[ 82.198] (II) This device may have been added with another device file.
[ 82.198] (II) config/udev: Adding input device HDA Intel PCH Dock Headphone (/dev/input/event19)
[ 82.198] (II) No input driver specified, ignoring this device.
[ 82.198] (II) This device may have been added with another device file.
[ 82.198] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event20)
[ 82.198] (II) No input driver specified, ignoring this device.
[ 82.198] (II) This device may have been added with another device file.
[ 82.199] (II) config/udev: Adding input device HID 046a:0101 (/dev/input/event5)
[ 82.199] (**) HID 046a:0101: Applying InputClass "evdev keyboard catchall"
[ 82.199] (II) Using input driver 'evdev' for 'HID 046a:0101'
[ 82.199] (**) HID 046a:0101: always reports core events
[ 82.199] (**) evdev: HID 046a:0101: Device: "/dev/input/event5"
[ 82.199] (--) evdev: HID 046a:0101: Vendor 0x46a Product 0x101
[ 82.199] (--) evdev: HID 046a:0101: Found keys
[ 82.199] (II) evdev: HID 046a:0101: Configuring as keyboard
[ 82.199] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input5/event5"
[ 82.199] (II) XINPUT: Adding extended input device "HID 046a:0101" (type: KEYBOARD, id 11)
[ 82.199] (**) Option "xkb_rules" "evdev"
[ 82.199] (**) Option "xkb_model" "evdev"
[ 82.199] (**) Option "xkb_layout" "de"
[ 82.199] (**) Option "xkb_variant" "nodeadkeys"
[ 82.199] (II) config/udev: Adding input device HID 046a:0101 (/dev/input/event7)
[ 82.199] (**) HID 046a:0101: Applying InputClass "evdev keyboard catchall"
[ 82.199] (II) Using input driver 'evdev' for 'HID 046a:0101'
[ 82.199] (**) HID 046a:0101: always reports core events
[ 82.199] (**) evdev: HID 046a:0101: Device: "/dev/input/event7"
[ 82.199] (--) evdev: HID 046a:0101: Vendor 0x46a Product 0x101
[ 82.199] (--) evdev: HID 046a:0101: Found 1 mouse buttons
[ 82.199] (--) evdev: HID 046a:0101: Found scroll wheel(s)
[ 82.199] (--) evdev: HID 046a:0101: Found relative axes
[ 82.199] (II) evdev: HID 046a:0101: Forcing relative x/y axes to exist.
[ 82.199] (--) evdev: HID 046a:0101: Found absolute axes
[ 82.199] (II) evdev: HID 046a:0101: Forcing absolute x/y axes to exist.
[ 82.199] (--) evdev: HID 046a:0101: Found keys
[ 82.199] (II) evdev: HID 046a:0101: Configuring as mouse
[ 82.199] (II) evdev: HID 046a:0101: Configuring as keyboard
[ 82.199] (II) evdev: HID 046a:0101: Adding scrollwheel support
[ 82.199] (**) evdev: HID 046a:0101: YAxisMapping: buttons 4 and 5
[ 82.199] (**) evdev: HID 046a:0101: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 82.199] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.1/input/input7/event7"
[ 82.199] (II) XINPUT: Adding extended input device "HID 046a:0101" (type: KEYBOARD, id 12)
[ 82.199] (**) Option "xkb_rules" "evdev"
[ 82.199] (**) Option "xkb_model" "evdev"
[ 82.199] (**) Option "xkb_layout" "de"
[ 82.199] (**) Option "xkb_variant" "nodeadkeys"
[ 82.199] (II) evdev: HID 046a:0101: initialized for relative axes.
[ 82.199] (WW) evdev: HID 046a:0101: ignoring absolute axes.
[ 82.199] (**) HID 046a:0101: (accel) keeping acceleration scheme 1
[ 82.199] (**) HID 046a:0101: (accel) acceleration profile 0
[ 82.199] (**) HID 046a:0101: (accel) acceleration factor: 2.000
[ 82.199] (**) HID 046a:0101: (accel) acceleration threshold: 4
[ 82.200] (II) config/udev: Adding input device HID 046a:0101 (/dev/input/event8)
[ 82.200] (**) HID 046a:0101: Applying InputClass "evdev pointer catchall"
[ 82.200] (II) Using input driver 'evdev' for 'HID 046a:0101'
[ 82.200] (**) HID 046a:0101: always reports core events
[ 82.200] (**) evdev: HID 046a:0101: Device: "/dev/input/event8"
[ 82.200] (--) evdev: HID 046a:0101: Vendor 0x46a Product 0x101
[ 82.200] (--) evdev: HID 046a:0101: Found 9 mouse buttons
[ 82.200] (--) evdev: HID 046a:0101: Found scroll wheel(s)
[ 82.200] (--) evdev: HID 046a:0101: Found relative axes
[ 82.200] (--) evdev: HID 046a:0101: Found x and y relative axes
[ 82.200] (II) evdev: HID 046a:0101: Configuring as mouse
[ 82.200] (II) evdev: HID 046a:0101: Adding scrollwheel support
[ 82.200] (**) evdev: HID 046a:0101: YAxisMapping: buttons 4 and 5
[ 82.200] (**) evdev: HID 046a:0101: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 82.200] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.2/input/input8/event8"
[ 82.200] (II) XINPUT: Adding extended input device "HID 046a:0101" (type: MOUSE, id 13)
[ 82.200] (II) evdev: HID 046a:0101: initialized for relative axes.
[ 82.200] (**) HID 046a:0101: (accel) keeping acceleration scheme 1
[ 82.200] (**) HID 046a:0101: (accel) acceleration profile 0
[ 82.200] (**) HID 046a:0101: (accel) acceleration factor: 2.000
[ 82.200] (**) HID 046a:0101: (accel) acceleration threshold: 4
[ 82.200] (II) config/udev: Adding input device HID 046a:0101 (/dev/input/mouse1)
[ 82.200] (II) No input driver specified, ignoring this device.
[ 82.200] (II) This device may have been added with another device file.
[ 82.200] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 82.200] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 82.200] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 82.200] (**) AT Translated Set 2 keyboard: always reports core events
[ 82.200] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 82.200] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 82.200] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 82.200] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 82.200] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 82.200] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 14)
[ 82.200] (**) Option "xkb_rules" "evdev"
[ 82.200] (**) Option "xkb_model" "evdev"
[ 82.200] (**) Option "xkb_layout" "de"
[ 82.200] (**) Option "xkb_variant" "nodeadkeys"
[ 82.201] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event11)
[ 82.201] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 82.201] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 82.201] (II) LoadModule: "synaptics"
[ 82.201] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 82.201] (II) Module synaptics: vendor="X.Org Foundation"
[ 82.201] compiled for 1.12.2, module version = 1.6.2
[ 82.201] Module class: X.Org XInput Driver
[ 82.201] ABI class: X.Org XInput driver, version 16.0
[ 82.201] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[ 82.201] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 82.201] (**) Option "Device" "/dev/input/event11"
[ 82.203] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
[ 82.203] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5888
[ 82.203] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4820
[ 82.203] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 82.203] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[ 82.203] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right double triple
[ 82.203] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[ 82.203] (**) Option "TapButton1" "1"
[ 82.203] (**) Option "TapButton2" "2"
[ 82.203] (**) Option "TapButton3" "3"
[ 82.203] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 82.203] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 82.204] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input11/event11"
[ 82.204] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 15)
[ 82.204] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[ 82.204] (**) synaptics: SynPS/2 Synaptics TouchPad: MaxSpeed is now 1.75
[ 82.204] (**) synaptics: SynPS/2 Synaptics TouchPad: AccelFactor is now 0.036
[ 82.204] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 82.204] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[ 82.204] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 82.204] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 82.204] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 82.204] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse2)
[ 82.204] (II) No input driver specified, ignoring this device.
[ 82.204] (II) This device may have been added with another device file.
[ 82.204] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/event21)
[ 82.204] (**) TPPS/2 IBM TrackPoint: Applying InputClass "evdev pointer catchall"
[ 82.204] (II) Using input driver 'evdev' for 'TPPS/2 IBM TrackPoint'
[ 82.204] (**) TPPS/2 IBM TrackPoint: always reports core events
[ 82.204] (**) evdev: TPPS/2 IBM TrackPoint: Device: "/dev/input/event21"
[ 82.204] (--) evdev: TPPS/2 IBM TrackPoint: Vendor 0x2 Product 0xa
[ 82.204] (--) evdev: TPPS/2 IBM TrackPoint: Found 3 mouse buttons
[ 82.204] (--) evdev: TPPS/2 IBM TrackPoint: Found relative axes
[ 82.204] (--) evdev: TPPS/2 IBM TrackPoint: Found x and y relative axes
[ 82.204] (II) evdev: TPPS/2 IBM TrackPoint: Configuring as mouse
[ 82.204] (**) evdev: TPPS/2 IBM TrackPoint: YAxisMapping: buttons 4 and 5
[ 82.204] (**) evdev: TPPS/2 IBM TrackPoint: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 82.204] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/serio2/input/input21/event21"
[ 82.204] (II) XINPUT: Adding extended input device "TPPS/2 IBM TrackPoint" (type: MOUSE, id 16)
[ 82.205] (II) evdev: TPPS/2 IBM TrackPoint: initialized for relative axes.
[ 82.205] (**) TPPS/2 IBM TrackPoint: (accel) keeping acceleration scheme 1
[ 82.205] (**) TPPS/2 IBM TrackPoint: (accel) acceleration profile 0
[ 82.205] (**) TPPS/2 IBM TrackPoint: (accel) acceleration factor: 2.000
[ 82.205] (**) TPPS/2 IBM TrackPoint: (accel) acceleration threshold: 4
[ 82.205] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/mouse3)
[ 82.205] (II) No input driver specified, ignoring this device.
[ 82.205] (II) This device may have been added with another device file.
[ 82.205] (II) config/udev: Adding input device PC Speaker (/dev/input/event6)
[ 82.205] (II) No input driver specified, ignoring this device.
[ 82.205] (II) This device may have been added with another device file.
[ 82.205] (II) config/udev: Adding input device ThinkPad Extra Buttons (/dev/input/event9)
[ 82.205] (**) ThinkPad Extra Buttons: Applying InputClass "evdev keyboard catchall"
[ 82.205] (II) Using input driver 'evdev' for 'ThinkPad Extra Buttons'
[ 82.205] (**) ThinkPad Extra Buttons: always reports core events
[ 82.205] (**) evdev: ThinkPad Extra Buttons: Device: "/dev/input/event9"
[ 82.205] (--) evdev: ThinkPad Extra Buttons: Vendor 0x17aa Product 0x5054
[ 82.205] (--) evdev: ThinkPad Extra Buttons: Found keys
[ 82.205] (II) evdev: ThinkPad Extra Buttons: Configuring as keyboard
[ 82.205] (**) Option "config_info" "udev:/sys/devices/platform/thinkpad_acpi/input/input9/event9"
[ 82.205] (II) XINPUT: Adding extended input device "ThinkPad Extra Buttons" (type: KEYBOARD, id 17)
[ 82.205] (**) Option "xkb_rules" "evdev"
[ 82.205] (**) Option "xkb_model" "evdev"
[ 82.205] (**) Option "xkb_layout" "de"
[ 82.205] (**) Option "xkb_variant" "nodeadkeys"
[ 82.222] (II) intel(0): EDID vendor "AUO", prod id 8510
[ 82.222] (II) intel(0): Printing DDC gathered Modelines:
[ 82.222] (II) intel(0): Modeline "1600x900"x0.0 110.00 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (54.7 kHz eP)
[ 82.222] (II) intel(0): Modeline "1600x900"x0.0 73.33 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (36.5 kHz e)
[ 82.415] (II) intel(0): Allocated new frame buffer 1920x1200 stride 7680, tiled
[ 106.807] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 117.740] (II) Open ACPI successful (/var/run/acpid.socket)
[ 117.740] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 117.767] (II) intel(0): EDID vendor "AUO", prod id 8510
[ 117.767] (II) intel(0): Printing DDC gathered Modelines:
[ 117.767] (II) intel(0): Modeline "1600x900"x0.0 110.00 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (54.7 kHz eP)
[ 117.767] (II) intel(0): Modeline "1600x900"x0.0 73.33 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (36.5 kHz e)
[ 117.959] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
I have connect my ThinkPad per Dockingstation Displayport (I try also DVI) with an NEC PA241W. It seems arch takes the 1600x900 resolution from the Laptop :-(
I dont know what to do makes the Kernel the Problem?
On my second PC i have there an Nvidia when i start arch for install all are perfect on my NEC i connected it with DVI
here is my xrandr
[frank@bullitt ~]$ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 8192 x 8192
LVDS1 connected 1600x900+0+0 (normal left inverted right x axis y axis) 309mm x 174mm
1600x900 60.0*+ 40.0
1024x768 60.0
800x600 60.3 56.2
640x480 59.9
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
DP1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
DP2 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm
1920x1200 60.0*+
1600x1200 60.0
1680x1050 60.0
1680x945 60.0
1400x1050 74.9 60.0
1600x900 60.0
1280x1024 85.0 75.0 60.0
1440x900 84.8 75.0 59.9
1280x960 85.0 60.0
1360x768 59.8 60.0
1280x800 84.9 74.9 59.8
1152x864 75.0
1280x768 84.8 74.9 59.9
1280x720 60.0
1024x768 85.0 75.1 70.1 60.0
1024x576 60.0
832x624 74.6
800x600 85.1 72.2 75.0 60.3 56.2
848x480 60.0
640x480 85.0 72.8 75.0 66.7 60.0
720x400 85.0 70.1
640x400 85.1
640x350 85.1
DP3 disconnected (normal left inverted right x axis y axis)
Does anybody have the same kind of connected an Laptop with an external Monitor and knows what was the Problem?
I like arch very much but so it doesnt make fun :-(
I hope someone can help me
the picture shows openbox with the Thunar maximized
Last edited by kerasi (2012-10-12 23:12:12)@trilby
i use my Laptop at home 95% and at work 5%
so my first choice would be to have the perfect resolution on my NEC external and when i opened a window it would display there and i dont have to open my Laptop to move the screen to see it on my external or is it so that you must have opened the laptop display to move the windows?
And when i would take it at work it would be perfect if i see it on the laptop with his resolution 1600x900
i hope i explained it well.
@anoknusa
i change your config to this
xrandr --output LVDS1 --mode 1600x900 --pos 0x900 --rotate normal --output DP2 --mode 1920x1200 --pos 0x0 --rotate normal
when i start firefox it was displayes well on my external but when i opened xterm or thunar pcman i have to open my laptop and move from it up to the external do i make a mistake?
anoknusa wrote:I stuck that in a script to run when I start X; if the external monitor isn't plugged in, only the laptop display is used. This sets each screen to act as a seperate display; I can still drag windows between them if I wish, as well as assign windows to open on one screen or the other through DWM's configuration file. As mentioned earlier, this is also the only way (I think) to get each screen to display at its native resolution. Note that I specify the resolution for both my T520 LCD and my external monitor, and specify their positions (my external is mounted to the wall above my desk, directly above my laptop); change those as necessary.
what has xrandr to look like for my external monitor and laptop?
and what would the script look like for me?
external 1920x1200
T420 1600x900
and thank you for your patience and have a nice day
ps: i know iam very close to find a solution for my problem
Last edited by kerasi (2012-10-11 00:05:55) -
Dear all,
Some months ago, in this forum, I was requesting information about the compatibility of panels for the W530 wince my panel, AUO B156HTN01, is an underperforming panel. The contrast ratio I get is lower than 400:1 (average 330:1) and the colour cast I get from it is too blue. While I do have an X Rire i1 Display Pro to correct any casts with the LUT of the graphics card, I still have issues with viewing angles (quite poor) and a bit of a magenta cast and the low contrast ratio as well as the screen door effect which is annoying in white or near white surfaces.
I am a photographer and I would love to trust this computer for field work and colour sensitive work but the difference between this and my NEC monitor is too great to ignore. So, hoping that the v4 or v7 will improve things compared to the panel I was given, I feel like I have nothing much to loose.
So, I have researched a bit on trying to get my hands on a B156HW01 v4 panel or a v7 (glossy with better contrast ratio than v4) and besides the used ones cannibalized from other systems, I have never been able to get a good replacement.
Until now. I managed to get one old stock seller through a contact in Asia and will be getting a v7 since v4s are really out of stock everywhere I can find. The ones that try to sell you v4s will likely send you a "compatible" part...but not the same panel.
I know glossy isn't everyone's taste and it is certainly not mine, but I have colleagues that happily work on their very glossy macs and while they do appreciate the nice matt monitors, the gloss hasn't stopped any of them from working. The colour discrepancy in the B156HTN01 is definitively stopping me from working so I am going to give that a go. Better accuracy on glossy is better than a crap matt.
I'll be posting differences on a before and after state of the computer. To make it very fair, I will re-install everything (windows and the lot) to make sure nothing from previous colour calibration is left behind on this computer to alter the perception of the panels.
If anyone in the UK or EU is interested, I'd be happy to get another one and we can split the total. The panels would be coming to to the UK so if you are in the EU you would need to cover the postage from me to you.
Solved!
Go to Solution.Final part.
For anyone in the UK, please be aware that your parcel may take around 10 days to clear customs and an extra 48hrs for Parcelforce to deliver the parcel to you.
So, after that long wait, I received the new v7 panel and proceeded to make the exchange.
Before that, however, to give the B156HTN01 panel a fair opportunity to prove itself, I took some photographs with the default colour management profile from Lenovo. See the first two images, blue cast, two angles.
Now, to make my point, I ran a quick profile with the largest palette in i1 Profiler (Yes, I know it has its drawbacks, but for a quickie, the profile is not horribly wrong and the contrast ratio is persistent)
This is the result.
See the contrast ratio here is 247:1...very poor.
I followed this gentleman's video to make the exchange.
http://www.youtube.com/watch?v=Igk0MiqZ_ck
To take the bezel out, however, I used a lens clening microfibre cloth to place my fingertips in between the screen and bezel and it popped out in an easier fashion than what that video shows. So if you go through with this, mind that.
Test after replacement to see if it works.
Glossy Display W530
Default color management profile on new v7 panel vs NEC PA241w monitor for reference (the NEC screen is calibrated for 6500k, aRGB gamut and gamma 2.2)
Now, profling with DispcalGUI takes a while, but, since we want to measure the success or failure of the new v7 panel, I ran it. The following screenshot shows the almost matching screens with the v7 and NEC monitor AFTER profliing with DispcalGUI.
I was a bit tired so I missed the horizontal framing for these two photos. This is DiscalpGUI's report.
Mind the 632:1 contrast ratio now and that the black luminance is not too bad at 0.2cd/m2. It is not an impressive contrast ratio by today's many 1000+:1 screens but it is very good for a 2 year old panel able to display most of Adobe RGB's colour gamut as seen in this comparison with NEC's Spectraview graph. DispcalGUI for v7 on the left and Spectraview for NEC PA241w on the right.
On DispcaGUI, the dotted line is the AdobeRGB spectrum and in Spectraview's its the yellow line.
Not bad, eh? -
My Equipment:
Nikon D300s
Color space: Adobe 1998
Picture Control Setting: Neutral
NEF files
Mac Computer
PPC and Intel based processors (problem does not change with computer)
Monitor NEC PA241W wide gamut monitor, calibrated with Spectraview
WD External Hardrive stores all my files
Software
Lightroom 2 and 3
Capture One
Photoshop CS 4
Canon iPF6300
Up to date print drivers
Canson paper with icc profiles for printer
Problem: Images Export with Heavy Red Tone
All images appear correct in all software applications. Upon export to the printer, the images appear with heavy red toning in printer preview window. This also happens exporting to file. Image correct appearance in file, then lab produces a heavy red print.
This is the original image from Lightroom 3, zero edit, camera calibration Camera D2X Mode 2 for better Nikon RAW processing.
As far as I can tell, I have calibrated every portion of my system. I have selected the most current printer drivers and icc profiles. However, no matter what I do, this is what I get...
Exporting for print: Canon Printer Preview window opens. This is what the image will look like upon printing.
Shockingly RED!!
This same result happens out of any software program – LR, CS4, Capture One
Any thoughts or input would be greatly appreciated. Very frustrated at seeing red.
CelestOk a few more discoveries....I found last night a possible solution.
In continuing research, I found a link on Canon Digital Photography site regarding printing red images. It seems that Canon has traditionally had this problem on new printers. As my iPF 6300 is the new version from the iPF 6100, I thought I would try the correction suggested and so far it seems to work a treat.
The solution: Uncheck the print preview button!
After selecting print from LR, the Print window automatically opens. Select the Main window. At the bottom there is a check box for Print Preview. Deselect this!
This still not giving me a perfect match to my LR image, however it is very agreeable.
In regards to the lab printing. My best results have been in giving the lab sRGB files. I have only had one lab error with red printing and I gave Profoto RGB space.
Kelly, I'm wondering about your import as DNG...why not NEF? When I import my files as a NEF I can choose a better RAW converter in LR. This is under the Develop Module at the very bottom, Camera Calibration. LR automatically sets the file under Adobe Standard which does not render the same image as the JPEG on the back of my camera. The skin tones are more harsh and have a redder tone. LR has created additional calibration selections for better RAW processing. For skin tones I would recommend using one of the Nikon options...These are listed as Camera D2X Mode 1/2/3. I like the mode 1 or 2 the best as I do portrait work.
Any further thoughts on this Print Preview check selection are greatly appreciated!
Thanks -
Lightroom image not the same as PS image
LR4 image (no adjustments other than initial rendering) is dull compared to opening same raw image directly into PS (CS5) via ACR. If I set monitor profile to sRGB there is no problem, suggesting that I had a corrupt profile.(According to several forums I read). I have redone my color calibration and restarted my computer. The problem exists.
Both ACR and LR are using Adobe Standard for the camera calibration,
Using Version 2010 for both was no different than using 2012 for LR and 2010 for Photoshop
Color Space,ProPhoto is the same, and all other menu items are set correctly , according to LR Forums
Please help! Jeannie"So, what method are you using to tell software which monitor profile to use? Is it Windows? If so, what version of Windows? Are you using the gamma loader that came with the profiler software or are you asking Windows to do it for you using its built-in means?"
Thanks for your interest in my situation. To answer your question: I select the correct monitor and icc profile deep within the Control Panel of Windows 7. I don't understand the second sentence. Eye One Display 3 software is what I use to create custom monitor profiles. If, on the other hand, I revert back to a canned profile I select one of the profiles that came with the MultiProfiler that came with my NEC PA241W. "Gamma Loader" is not something that I am familiar with. The closest I come to understanding you is that when I have a choice I select Gamma = 2.2 -
Wide gamut monitor on Mac, worth it?
I have the need for a new monitor to be tethered to a MacBook Pro. Experiencing wide gamut images on screen is something I looked for, but after checking some reviews on recent additions, I have mixed feelings.
Here are some conclusions I came to:
— From what I have gathered, Apple, creator of ColorSync, still has 8 bit support only both in OS and hardware.
— Wide gamut monitors can dispaly a more saturated image in the wide gamut Adobe RGB space even with an 8 bit path, but need the 10 bit path to have the corresponding smoother gradient.
— Wide gamut monitors are difficult to calibrate—some require specific devices for internal hardware calibration, and some will not be able to take profit of some of their interesting features like Uniformity Control when set to a personal calibration mode.
— If he who can do more can do less, I would take the 10 bit option anyway. But, it seems that sRGB emulation is at the cost of some gradient degradation — how bad, I don't know.
Ok, that's for theory. But in practice, is the wide gamut image on Mac, an enjoyable experience anyway?Why is there not one single reply on this issue? Has it been resolved? I still hear quite a few people complaining on this issue.
I don't see why this is something that belongs in your code (AS3 colorCorrection). You don't do so with seperate jpg images on a html-page either ;]
Just posted a comment at http://blogs.adobe.com/jnack/2008/10/get_better_color_online_through_flash_play.html but it's gone now.. -
MacPro 1,1 Video card died ! Options ?
Hey all, I'm having some problems with my MacPro and I'm suspecting the video card at this point.
http://discussions.apple.com/thread.jspa?threadID=2558303&tstart=0
I was looking at the Apple store website and see only 2 listed in my price range, the NVIDIA GeForce GT 120, and the ATI Radeon HD 5770.
Will both these cards work in a MacPro 1,1 (2006 model) I've done a search but have found conflicting information. Any help would be appreciated.
Thanks in advance.
- JayDP Art is right I expect and the table appearing on this page that compares the 5770 and the 5870 presents it in "black and white":
http://www.apple.com/macpro/features/graphics.html
I've got a 4870 card on backorder ($349) with Apple and am seriously considering forking out another $100 to get the 5870, if reports continue to be positive about the use of the 5870 in a Mac Pro 1,1.
I've been on an upgrade path the last few months to help my MP Xeon give me a few more good years doing design work in CS apps. (New hard drives, SL upgrade, new NEC PA241W monitor, soon the card and then more RAM.) Seems wise to go for the best I can get with the card - hoping the 5870 reports continue to confirm I can. Need to decide before Apple ships the 4870 to me.
If anyone that is now reading my post in this designers' thread possesses new info on the wisdom of my thinking, please comment. Thanks!
Maybe you are looking for
-
How do you buy adobe acrobat x standard?
Hi, where can you buy adobe acrobat x standard? All I can find for purcahse anywhere are the upgrades? Thx:)
-
I cant find my Face time icon in iphone 4
ladies and gentlemen after i got my phone from some shop repair i lost my i phone icon how can get it back Mohamed Zadjali
-
can i declare a structure as in C language, then to use it as an array..... but this time i want to use java.... how can this be done... let say my structure have studid and age, i want my array to be of size 3.... pls help
-
Properties for MenuBar Widget cs5 Gone
On all of my websites, when I click on the Light Blue Box on my menuBar widgets, when it brings up the properties it just says: Widget & the Name of the MenuBar. Gone is the ability to quickly name & move submenus, point links, etc. How do I get t
-
while executing the below query. I m getting this error ora error 02287 " sequence # not allowed here" SELECT SVC_ORD_DETAIL_ID.NEXTVAL, K.SVC_ORDER_ID, 'RELEASED_DATE', K.RELEASEDT FROM (S