Displayport

how do I shut off MacBook display when using an external monitor?
Mike

The computer goes to sleep.
This is functioning as expected. If you're going to use an external display, you must also have an external keyboard and mouse as well as being connected to the AC power. When you close the lid, the computer goes to sleep. But, with an external display, keyboard and mouse you can wake the computer with the mouse or keyboard to continue using it. There are no settings to configure. Here's the official word:
http://support.apple.com/kb/HT3131
-Doug

Similar Messages

27: iMac Apple Mini DisplayPort to DVI adapter quits working post-firmware

I iMac Apple Mini DisplayPort to DVI adapter suddenly quit working after I installed Apple's latest iMac display firmware update. This is an Intel Core i5; the monitor is an LG Flatron 24" Wide, and when it powers up it says "no video input" and goes into power-saving mode. No amount of replugging cables helps, but the monitor works fine on other computers.
The Displays control panel just shows one monitor, and clicking Detect Displays does nothing.
I suspect Apple's Display Firmware Update. My installer log shows the following, but the problem only happened today after the latest update:
6/1/10 9:45 AM 27-inch iMac EFI Firmware Update 1.0
6/1/10 9:45 AM 27-inch iMac Display Update 1.0
6/4/10 11:47 AM 27-inch iMac SMC Firmware Update 1.0
6/4/10 11:47 AM 27-inch iMac Display Update 1.0
6/5/10 7:29 AM 27-inch iMac Display Update 1.0
I have automatic updates disabled, but after each update I would see more firmware updates ready, but caution leads me to never install more than one of these at a time, and then to wait a while to see if anything bad happens. The odd thing is that the Display Update 1.0 seems to have been installed three times in this course of events. Alas, there appears to be no way to uninstall a firmware update.
Here is the System Profiler Graphics/Displays output:
Chipset Model: ATI Radeon HD 4850
Type: GPU
Bus: PCIe
PCIe Lane Width: x16
VRAM (Total): 512 MB
Vendor: ATI (0x1002)
Device ID: 0x944a
Revision ID: 0x0000
ROM Revision: 113-B9110C-425
EFI Driver Version: 01.00.383
Displays:
iMac:
Resolution: 2560 x 1440
Pixel Depth: 32-Bit Color (ARGB8888)
Main Display: Yes
Mirror: Off
Online: Yes
Built-In: Yes
Connection Type: DisplayPort
Display Connector:
Status: No Display Connected
It says the Mac sees no display connected, and the display gets no video signal. Since the adapter is an active device (it has powered electronics to convert DisplayPort signals to DVI signals) I suppose it could have just coincidentally died. But that seems unlikely given that the thing worked perfectly just before the last firmware update.
Does anybody have similar experience, or better yet, a fix?

Unfortunately the Apple Knowledge Base does not give much information about this update. Such has how to tell if it has been successfully installed. I suspect that because it keeps recurring in the install log that it has not been installed successfully as yet. Are you receiving this update through Software Update? Can you locate the installer for this update? It maybe located in Apps/Utilities.
Some firmware update installations can be interrupted/corrupted by attached devices. If you find the update's installer on your iMac, I suggest that you detach all external devices from the iMac, use an Apple USB keyboard & mouse if available, follow the instructions carefully and install the update manually. If you do not locate the installer I suggest downloading manually from the link below and installing it.
The Knowledge Base article mentions that your iMac should also have a Graphics Firmware Update. I suggest that you download and install that as well.
27-inch iMac Display Firmware Update 1.0
http://support.apple.com/kb/DL998
27-inch iMac Graphics Firmware Update 1.0
http://support.apple.com/kb/DL984
Dah•veed

Apple Mini DisplayPort to VGA Adapter flickers

I have 2 Samsung SyncMaster 23 in, HD Displays connected to my Mac Mini. The Display connected via the Mini DP to VGA adapter flickers erratically. This started happening after installing the latest upgrade of OSX Mountain Lion. I called Apple support, they gave me a list of steps to try to fix the problem, which I followed to the letter, to no avail. The problem is annoying, to say the least. I tried to find out if there was a firmware update for the adapter, but I am running the latest firmware (1.03).
I would appreciate any help to solve this issue.

Thank you for your message.
1. Both monitors only have VGA input.
2. The other adapter, Mini-DVI to VGA has always worked properly.
3. The Mini DisplayPort to VGA adapter is an Apple original product I bought at an Apple store. I bought 2 adapters.
4. Actually I have 2 Mini DisplayPort to VGA adapters: The one I use with my Mac Mini, and another adapter I use to connect my Mac Book Pro to a Panasonic projector.
5. I have tried using both adapters, and the flickering problem is present using either adapter.
6. I believe the flickering problem is definitely something that needs to be addressed and solved by Apple. The adapter is its product, and should work as advertised, no matter what version of OSX I am running. Please remember that there was no flickering before I upgraded to the latest OSX Mountain Lion.
7. I do not believe buying an adapter from another manufacturer, as you suggest, would solve the problem.
Thank you for your help.

How to connect a 2009 Cinema Display with mini DisplayPort to modern card

Hello:
I am ready to install a new NVidia Quadro K5000 for Mac in my not so old Mac Pro 4,1 (2009). I already installed Mountain Lion (10.8.3) as required. The problem is that the Mac Pro came with a Led Cinema Display which apparently only can be connected with a mini DisplayPort plug and the graphics card only have DVi and DP 1.2. I tried to find an adapter but the ones I have find are minidp male to DVI female and obviously I need a minidp female to DVI or DP female.
I will appreciate any help.
Alex Sierra

The fifth and sixth item on this page are DisplayPort male to Mini DisplayPort female "Extension cables". Under US$6 plus shipping from a reputable seller:
http://www.monoprice.com/products/subdepartment.asp?c_id=102&cp_id=10246#1024602

Thunderbolt display: devices not discovered after using Mini DisplayPort–to–VGA adapter

I have an interested problem related to using my MacBook Air in clamshell (closed) mode, connected to a Thunderbolt display. The problem appears to be related to moving my MacBook air between my office and my home.
At the office, I use the MacBook Air with an external VGA display, connected via the Mini DisplayPort–to–VGA adapter. At home, I use the MacBook Air together with a Thunderbolt display. An Apple USB keyboard is also connected to the display.
Mini DisplayPort–to–VGA adapter implicated
The following sequence of events causes the problem to occur:
Use the MacBook air (open) together with a VGA display, connected via a Mini DisplayPort–to–VGA adapter (depicted at right);
Put the MacBook Air to sleep by closing the lid, and disconnect the Mini DisplayPort–to–VGA adapter (I am not sure if the order of these two steps is significant—I usually perform them almost simultaneously when packing up my MacBook Air and getting ready to leave the office); and
With the MacBook Air still closed, connect it to a Thunderbolt display with a connected USB keyboard.
At this point, I would expect to be able to wake up the MacBook Air by tapping on the space bar of the keyboard. However, what I have observed is that this does not wake the MacBook Air.
I can wake the MacBook however by moving or clicking a Bluetooth mouse that is paired with the MacBook Air.
At this point, although the MacBook Air is awake, and the display is working, the USB keyboard connected to the display still does not work. This is the problem, in a nutshell.
Unplugging the USB keyboard from the display, and plugging it back in causes the MacBook Air properly to identify the keyboard.
I used Apple System Profiler to save a list of identified devices at two points in time:
Immediately after waking the MacBook Air by moving the Bluetooth mouse (at which point the USB keyboard was not working); and
After unplugging and plugging in again the USB keyboard (at which point the USB keyboard worked fine).
Many devices are enumerated in the second list that are missing from the first. For example:
Keyboard Hub@fe110000 <class IOUSBHubDevice, id 0x1000378ef, !registered, !matched, inactive, busy 3 (37993 ms), retain 6>
AppleUSBHub <class AppleUSBHub, id 0x1000378f2, !registered, !matched, inactive, busy 1 (37987 ms), retain 6>
IOUSBInterface@0 <class IOUSBInterface, id 0x1000378f4, !registered, !matched, inactive, busy 1 (37986 ms), retain 6>
Keyboard Hub@fe110000 <class IOUSBHubDevice, id 0x1000378f6, registered, matched, active, busy 0 (7 ms), retain 10>
AppleUSBHub <class AppleUSBHub, id 0x1000378f9, registered, matched, active, busy 0 (1 ms), retain 9>
IOUSBInterface@0 <class IOUSBInterface, id 0x1000378fb, !registered, !matched, active, busy 0, retain 7>
Apple Keyboard@fe112000 <class IOUSBDevice, id 0x1000378fd, registered, matched, active, busy 0 (112 ms), retain 11>
and many child devices…
Using the Mini DisplayPort–to–VGA adapter appears to be a necessary step to causing this problem to occur. If I merely disconnect the MacBook Air from the display, let it go to sleep, and then reconnect it again, the USB keyboard will work immediately and can be used to wake the computer from sleep.
Some devices are discovered even when the computer is in sleep mode. This is how it should work.
The problem appears to be that when a Mini DisplayPort–to–VGA adapter has been used since the last time the computer was connected to a Thunderbolt display, the MacBook air does not discover devices completely when it is again connected to the Thunderbolt display while in sleep mode.
Can anyone else reproduce this problem?

Hi glraczon.support,
It sounds like the external display you are using (projector) operates at a smaller resolution than your MacBook Pro. You may want to configure the display preferences in System Preferences for the external projector.
Here is an article that may help you with that process:
OS X Mountain Lion: About the Display pane of System Preferences
http://support.apple.com/kb/HT5369
Thanks,
Matt M.

No image on screen using Mini DisplayPort to VGA Adapter

Received mini today. After unboxing, read through the packet. Then began to hook everything up as directed. I used a Mini DisplayPort to VGA Adapter to connect the monitor from our now dead desktop to the mini. After double checking all connections, I hit the power button. I immediately heard the apple chime. Then the monitor showed the grey apple start up screen. Suddenly the monitor went black and said it was going into sleep mode. I can't get it out of sleep mode when connected to the mini. It is NOT the monitor or the adapter. I plugged the monitor straight into a netbook and it worked. Then, I plugged the monitor using the adapter into my MacBook Pro and also got it to work that way. So I tried replugging the adapter into the mini. Still can't get an image on the screen. I can't complete set up or use mini because I can't get an image. Any suggestions or ideas? I will call apple in the morning if I can't figure it out tonight. But I'm hoping someone can give me suggestions. Thanks for your help!

I had the same issue when I bought my mac mini last week apart from I wasn't even getting the initial grey screen. I went back to the Apple shop and they gave me another mini and fired it up in the shop using the adaptor on an old VGA monitor. It worked perfectly.
When I got home I set it all up again and still had the same issue. I nearly threw out a couple of monitors as I thought they were broken.
However, had a look around the web and found this suggestion:
Shut down the mac and disconnect the adaptor from it. Now fire the mac up and let it boot up FULLY. Once it has had a chance to boot up fully, only then plug the adaptor in.
Worked for me and I haven't had the issue since (touch wood). Hope this helps.

Using Mini DisplayPort to VGA Adapter to connect Macbook Pro (2009) for a presentation via projector.

When I connect my Macbook Pro (2009 model) using a Mini DisplayPort to VGA adapter to display a presentation via projector, only the top-left portion of what is displayed on my Macbook Pro's screen is displayed on the projector, as though I zoomed in on that portion of my screen. The projector is on and the adapter and the cable that connects the adapter to the projector machine is correctly connected. Any suggestions on how to fix this problem?

Hi glraczon.support,
It sounds like the external display you are using (projector) operates at a smaller resolution than your MacBook Pro. You may want to configure the display preferences in System Preferences for the external projector.
Here is an article that may help you with that process:
OS X Mountain Lion: About the Display pane of System Preferences
http://support.apple.com/kb/HT5369
Thanks,
Matt M.

Mini DVI to VGA or Mini DisplayPort to VGA

I've used up all the HDMI connectors on my 1080p LCD, so need to use the VGA connection, which thankfully supports 1920 x 1080 native.
I was in the Apple store today and noticed they sell both a mini DVI to VGA adapter, as well as a mini DisplayPort to VGA adapter - the latter being $5 more expensive.
Since it's converting to analog in both cases, I'm wondering if there's any potential advantage of one vs. the other.
I'm looking for the best possible picture as my new mini will be serving as my media hub, so any input is appreciated.
And I've been connecting a laptop to my TV via regular VGA up till now and it looks amazing, so not worried about going VGA instead of HDMI...
Edit: Sorry - somehow posted this in the totally wrong forum but don't see any option to move it to Early 2009 -> using the Mac mini...

Welcome to Apple Discussions!
I was half expecting to see that there would be a difference in maximum resolution between the two connectors when used with VGA adaptors, but there is not. You can get up to 2048x1536 using either. There should not be any difference in quality of output between them.

Mini-DVI to VGA or Mini DisplayPort to VGA Adapter?

Hi There,
I am so close to purchasing a new Mac Mini that I can almost taste it. When I finally get the Mini, I want to hit the ground running, so I am trying to research everything out so I do have any stupid delays.
With the Mini, I want to use my 17" Apple CRT Studio Display with its 15-pin miniature D-type connector (I'm assuming that this is the typical VGA display connector). When I first started looking into the Mini, I figured that I could use a Mini-DVI to VGA connector and just be done with it. When I looked at the Mac Mini Accessories page that Apple set up, however, Apple says that I need a Mini Display Port to VGA adaptor and doesn't say boo about the Mini DVI adaptor. Doing some cursory Googling lead me to believe that the most current MacBooks and Minis will not support Mini DVI to VGA adaptors. Is this true?
If you were me, if either adaptor can be used, which VGA adaptor would you use? Is one superior over another? Inquiring minds want to know.
Thank you very much in advance for your reply.
Sincerely,
Malcolm Fuller

Personally, I'm using a minidisplayport to vga adapter I had to pay $30 for and it's working great for me and I can't tell the difference in image quality from the minidvi to dvi cable that comes with the mini.
Also, why not get the displayport so you can run 2 monitors at once?
If the displayport doesn't work with your monitor then I would try the mini-dvi version.
But yeah don't be suprised if you have to mess with it to make it work since it seems to work for some like me and not for others:
http://discussions.apple.com/thread.jspa?messageID=9486562&#9486562

Using Mini DisplayPort to VGA adapter -- any settings on the Macbook Air I need to change?

Going into a meeting with my Macbook Air with Mini DisplayPort to VGA adapter, which will be connnected to a video projector on site. Never tried this setup before. Will this just work or do I need to adjust any video settings on my Macbook Air?

Hi glraczon.support,
It sounds like the external display you are using (projector) operates at a smaller resolution than your MacBook Pro. You may want to configure the display preferences in System Preferences for the external projector.
Here is an article that may help you with that process:
OS X Mountain Lion: About the Display pane of System Preferences
http://support.apple.com/kb/HT5369
Thanks,
Matt M.

Does Thunderbolt work with the Mini Displayport to DVI adapter?

I just ordered a new 13" MacBook Pro with Retina Display to replace my Mid-2010 15" MacBook Pro. I've been using the Mini Displayport to DVI adapter to extend my screen to an older 20" Cinema Display. From what I can find online, and I'm here asking for confirmation, I should still be able to use the Mini Displayport to DVI adapter with the new MacBook Pro's Thunderbolt port. Correct?

still be able to use the Mini Displayport to DVI adapter with the new MacBook Pro's Thunderbolt port. Correct?
Yes.

Problem with Displayport and M11x

Okay so I have an M11x R3 laptop running Arch x86_64. I have an issue I just got a Displayport to DVI and Displayport to VGA adapters. I have tried HDMI but it doesn't show up with xrandr -q command. I was wondering what I should do because it shows my VGA1 disconnected even when the DisplayPort adapter is connected to the monitor and to the laptop?
xrandr -q output:
Screen 0: minimum 320 x 200, current 1366 x 768, maximum 8192 x 8192
LVDS1 connected 1366x768+0+0 (normal left inverted right x axis y axis) 256mm x 144mm
1366x768 60.0*+
1024x768 60.0
800x600 60.3 56.2
640x480 59.9
VGA1 disconnected (normal left inverted right x axis y axis)
Now I try to run this to get the display extended to a secondary monitor. Nothing happens!
xrandr --output VGA1 --auto --left-of LVDS1
sudo lspci -v
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: Dell Device 04c8
Flags: bus master, fast devsel, latency 0, IRQ 51
Memory at d1400000 (64-bit, non-prefetchable) [size=4M]
Memory at c0000000 (64-bit, prefetchable) [size=256M]
I/O ports at 7000 [size=64]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
01:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 540M] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Dell Device 04c8
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at d0000000 (32-bit, non-prefetchable) [size=16M]
Memory at a0000000 (64-bit, prefetchable) [size=256M]
Memory at b0000000 (64-bit, prefetchable) [size=32M]
I/O ports at 6000 [size=128]
Expansion ROM at d1000000 [disabled] [size=512K]
Capabilities: [60] Power Management version 3
Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Endpoint, MSI 00
Capabilities: [b4] Vendor Specific Information: Len=14 <?>
Capabilities: [100] Virtual Channel
Capabilities: [128] Power Budgeting <?>
Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
Kernel driver in use: nvidia
Now under /etc/X11/xorg.conf.d/ I don't have a specific xorg.conf file for then Intel card that runs on the i915 driver. Should I make one that can help with the detection of the displayport?
here is my /etc/bumblebee/xorg.nvidia.conf
Section "ServerLayout"
Identifier "Layout0"
Option "AutoAddDevices" "false"
EndSection
Section "Device"
Identifier "Device1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
Option "NoLogo" "true"
Option "UseEDID" "false"
Option "ConnectedMonitor" "DFP"
EndSection
Last but not least here is my /var/log/Xorg.1.log
[ 3822.058]
X.Org X Server 1.13.2
Release Date: 2013-01-24
[ 3822.058] X Protocol Version 11, Revision 0
[ 3822.058] Build Operating System: Linux 3.7.4-1-ARCH x86_64
[ 3822.058] Current Operating System: Linux tux_laptop 3.7.4-1-ARCH #1 SMP PREEMPT Mon Jan 21 23:05:29 CET 2013 x86_64
[ 3822.058] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=ac0ab469-8109-477b-a746-13d28a8fe11b ro quiet
[ 3822.058] Build Date: 25 January 2013 09:33:50AM
[ 3822.058]
[ 3822.058] Current version of pixman: 0.28.2
[ 3822.058] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 3822.058] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 3822.058] (==) Log file: "/var/log/Xorg.1.log", Time: Sun Jan 27 21:12:19 2013
[ 3822.058] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 3822.059] (==) No Layout section. Using the first Screen section.
[ 3822.059] (==) No screen section available. Using defaults.
[ 3822.059] (**) |-->Screen "Default Screen Section" (0)
[ 3822.059] (**) | |-->Monitor "<default monitor>"
[ 3822.059] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 3822.059] (==) Automatically adding devices
[ 3822.059] (==) Automatically enabling devices
[ 3822.059] (==) Automatically adding GPU devices
[ 3822.059] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/OTF/".
[ 3822.059] Entry deleted from font path.
[ 3822.059] (Run 'mkfontdir' on "/usr/share/fonts/OTF/").
[ 3822.059] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 3822.059] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 3822.059] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 3822.059] (II) Loader magic: 0x7fcc40
[ 3822.059] (II) Module ABI versions:
[ 3822.059] X.Org ANSI C Emulation: 0.4
[ 3822.059] X.Org Video Driver: 13.1
[ 3822.059] X.Org XInput driver : 18.0
[ 3822.059] X.Org Server Extension : 7.0
[ 3822.059] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 3822.061] (--) PCI:*(0:0:2:0) 8086:0116:1028:04c8 rev 9, Mem @ 0xd1400000/4194304, 0xc0000000/268435456, I/O @ 0x00007000/64
[ 3822.061] (--) PCI: (0:1:0:0) 10de:0df4:1028:04c8 rev 161, Mem @ 0xd0000000/16777216, 0xa0000000/268435456, 0xb0000000/33554432, I/O @ 0x00006000/128, BIOS @ 0x????????/524288
[ 3822.061] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 3822.061] Initializing built-in extension Generic Event Extension
[ 3822.061] Initializing built-in extension SHAPE
[ 3822.061] Initializing built-in extension MIT-SHM
[ 3822.061] Initializing built-in extension XInputExtension
[ 3822.061] Initializing built-in extension XTEST
[ 3822.061] Initializing built-in extension BIG-REQUESTS
[ 3822.061] Initializing built-in extension SYNC
[ 3822.061] Initializing built-in extension XKEYBOARD
[ 3822.061] Initializing built-in extension XC-MISC
[ 3822.061] Initializing built-in extension SECURITY
[ 3822.061] Initializing built-in extension XINERAMA
[ 3822.061] Initializing built-in extension XFIXES
[ 3822.061] Initializing built-in extension RENDER
[ 3822.061] Initializing built-in extension RANDR
[ 3822.061] Initializing built-in extension COMPOSITE
[ 3822.061] Initializing built-in extension DAMAGE
[ 3822.061] Initializing built-in extension MIT-SCREEN-SAVER
[ 3822.061] Initializing built-in extension DOUBLE-BUFFER
[ 3822.061] Initializing built-in extension RECORD
[ 3822.061] Initializing built-in extension DPMS
[ 3822.061] Initializing built-in extension X-Resource
[ 3822.061] Initializing built-in extension XVideo
[ 3822.061] Initializing built-in extension XVideo-MotionCompensation
[ 3822.062] Initializing built-in extension XFree86-VidModeExtension
[ 3822.062] Initializing built-in extension XFree86-DGA
[ 3822.062] Initializing built-in extension XFree86-DRI
[ 3822.062] Initializing built-in extension DRI2
[ 3822.062] (II) LoadModule: "glx"
[ 3822.062] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 3822.062] (II) Module glx: vendor="X.Org Foundation"
[ 3822.062] compiled for 1.13.2, module version = 1.0.0
[ 3822.062] ABI class: X.Org Server Extension, version 7.0
[ 3822.062] (==) AIGLX enabled
[ 3822.062] Loading extension GLX
[ 3822.062] (==) Matched intel as autoconfigured driver 0
[ 3822.062] (==) Matched intel as autoconfigured driver 1
[ 3822.062] (==) Matched vesa as autoconfigured driver 2
[ 3822.062] (==) Matched modesetting as autoconfigured driver 3
[ 3822.062] (==) Matched fbdev as autoconfigured driver 4
[ 3822.063] (==) Assigned the driver to the xf86ConfigLayout
[ 3822.063] (II) LoadModule: "intel"
[ 3822.063] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 3822.064] (II) Module intel: vendor="X.Org Foundation"
[ 3822.064] compiled for 1.13.1, module version = 2.20.19
[ 3822.064] Module class: X.Org Video Driver
[ 3822.064] ABI class: X.Org Video Driver, version 13.1
[ 3822.064] (II) LoadModule: "vesa"
[ 3822.064] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 3822.064] (II) Module vesa: vendor="X.Org Foundation"
[ 3822.064] compiled for 1.13.0, module version = 2.3.2
[ 3822.064] Module class: X.Org Video Driver
[ 3822.064] ABI class: X.Org Video Driver, version 13.0
[ 3822.064] (II) LoadModule: "modesetting"
[ 3822.064] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 3822.065] (II) Module modesetting: vendor="X.Org Foundation"
[ 3822.065] compiled for 1.13.1, module version = 0.6.0
[ 3822.065] Module class: X.Org Video Driver
[ 3822.065] ABI class: X.Org Video Driver, version 13.1
[ 3822.065] (II) LoadModule: "fbdev"
[ 3822.065] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 3822.065] (II) Module fbdev: vendor="X.Org Foundation"
[ 3822.065] compiled for 1.13.0, module version = 0.4.3
[ 3822.065] Module class: X.Org Video Driver
[ 3822.065] ABI class: X.Org Video Driver, version 13.0
[ 3822.065] (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
[ 3822.066] (II) VESA: driver for VESA chipsets: vesa
[ 3822.066] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 3822.066] (II) FBDEV: driver for framebuffer: fbdev
[ 3822.066] (++) using VT number 1
[ 3822.066] (WW) Falling back to old probe method for vesa
[ 3822.066] (WW) Falling back to old probe method for modesetting
[ 3822.067] (WW) Falling back to old probe method for fbdev
[ 3822.067] (II) Loading sub module "fbdevhw"
[ 3822.067] (II) LoadModule: "fbdevhw"
[ 3822.067] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 3822.067] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 3822.067] compiled for 1.13.2, module version = 0.0.2
[ 3822.067] ABI class: X.Org Video Driver, version 13.1
[ 3822.067] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 3822.067] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 3822.067] (==) intel(0): RGB weight 888
[ 3822.067] (==) intel(0): Default visual is TrueColor
[ 3822.067] (--) intel(0): Integrated Graphics Chipset: Intel(R) Sandybridge Mobile (GT2)
[ 3822.067] (**) intel(0): Relaxed fencing enabled
[ 3822.067] (**) intel(0): Wait on SwapBuffers? enabled
[ 3822.067] (**) intel(0): Triple buffering? enabled
[ 3822.067] (**) intel(0): Framebuffer tiled
[ 3822.067] (**) intel(0): Pixmaps tiled
[ 3822.067] (**) intel(0): 3D buffers tiled
[ 3822.067] (**) intel(0): SwapBuffers wait enabled
[ 3822.067] (==) intel(0): video overlay key set to 0x101fe
[ 3822.067] (II) intel(0): Output LVDS1 has no monitor section
[ 3822.067] (--) intel(0): found backlight control interface /sys/class/backlight/acpi_video0
[ 3822.092] (II) intel(0): Output VGA1 has no monitor section
[ 3822.093] (II) intel(0): EDID for output LVDS1
[ 3822.093] (II) intel(0): Manufacturer: AUO Model: 305c Serial#: 0
[ 3822.093] (II) intel(0): Year: 2009 Week: 0
[ 3822.093] (II) intel(0): EDID Version: 1.4
[ 3822.093] (II) intel(0): Digital Display Input
[ 3822.093] (II) intel(0): 6 bits per channel
[ 3822.093] (II) intel(0): Digital interface is undefined
[ 3822.093] (II) intel(0): Max Image Size [cm]: horiz.: 26 vert.: 14
[ 3822.093] (II) intel(0): Gamma: 2.20
[ 3822.093] (II) intel(0): No DPMS capabilities specified
[ 3822.093] (II) intel(0): Supported color encodings: RGB 4:4:4
[ 3822.093] (II) intel(0): First detailed timing is preferred mode
[ 3822.093] (II) intel(0): Preferred mode is native pixel format and refresh rate
[ 3822.093] (II) intel(0): redX: 0.584 redY: 0.333 greenX: 0.338 greenY: 0.571
[ 3822.093] (II) intel(0): blueX: 0.158 blueY: 0.133 whiteX: 0.313 whiteY: 0.329
[ 3822.093] (II) intel(0): Manufacturer's mask: 0
[ 3822.093] (II) intel(0): Supported detailed timing:
[ 3822.093] (II) intel(0): clock: 70.0 MHz Image Size: 256 x 144 mm
[ 3822.093] (II) intel(0): h_active: 1366 h_sync: 1414 h_sync_end 1446 h_blank_end 1470 h_border: 0
[ 3822.093] (II) intel(0): v_active: 768 v_sync: 771 v_sync_end 777 v_blanking: 793 v_border: 0
[ 3822.093] (II) intel(0): Supported detailed timing:
[ 3822.093] (II) intel(0): clock: 70.0 MHz Image Size: 256 x 144 mm
[ 3822.093] (II) intel(0): h_active: 1366 h_sync: 1414 h_sync_end 1446 h_blank_end 1470 h_border: 0
[ 3822.093] (II) intel(0): v_active: 768 v_sync: 771 v_sync_end 777 v_blanking: 793 v_border: 0
[ 3822.093] (II) intel(0): 2VD2KB116XW3
[ 3822.093] (II) intel(0): Unknown vendor-specific block 0
[ 3822.093] (II) intel(0): EDID (in hex):
[ 3822.093] (II) intel(0): 00ffffffffffff0006af5c3000000000
[ 3822.093] (II) intel(0): 00130104901a0e780299859555569228
[ 3822.093] (II) intel(0): 22505400000001010101010101010101
[ 3822.093] (II) intel(0): 010101010101581b5668500019303020
[ 3822.093] (II) intel(0): 360000901000001a581b566850001930
[ 3822.093] (II) intel(0): 3020360000901000001a000000fe0032
[ 3822.093] (II) intel(0): 5644324b804231313658573300000000
[ 3822.093] (II) intel(0): 0000410a960111000002010a202000b6
[ 3822.093] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported)
[ 3822.093] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 3822.093] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 3822.093] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported)
[ 3822.093] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported)
[ 3822.093] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported)
[ 3822.093] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported)
[ 3822.093] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported)
[ 3822.093] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported)
[ 3822.093] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported)
[ 3822.093] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported)
[ 3822.093] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported)
[ 3822.093] (II) intel(0): Printing probed modes for output LVDS1
[ 3822.093] (II) intel(0): Modeline "1366x768"x60.0 70.00 1366 1414 1446 1470 768 771 777 793 +hsync -vsync (47.6 kHz eP)
[ 3822.093] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz d)
[ 3822.093] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz d)
[ 3822.093] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz d)
[ 3822.093] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz d)
[ 3822.119] (II) intel(0): EDID for output VGA1
[ 3822.119] (II) intel(0): Output LVDS1 connected
[ 3822.119] (II) intel(0): Output VGA1 disconnected
[ 3822.119] (II) intel(0): Using exact sizes for initial modes
[ 3822.119] (II) intel(0): Output LVDS1 using initial mode 1366x768
[ 3822.119] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 3822.119] (II) intel(0): Kernel page flipping support detected, enabling
[ 3822.119] (==) intel(0): DPI set to (96, 96)
[ 3822.119] (II) Loading sub module "fb"
[ 3822.119] (II) LoadModule: "fb"
[ 3822.119] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 3822.120] (II) Module fb: vendor="X.Org Foundation"
[ 3822.120] compiled for 1.13.2, module version = 1.0.0
[ 3822.120] ABI class: X.Org ANSI C Emulation, version 0.4
[ 3822.120] (II) Loading sub module "dri2"
[ 3822.120] (II) LoadModule: "dri2"
[ 3822.120] (II) Module "dri2" already built-in
[ 3822.120] (II) UnloadModule: "vesa"
[ 3822.120] (II) Unloading vesa
[ 3822.120] (II) UnloadModule: "modesetting"
[ 3822.120] (II) Unloading modesetting
[ 3822.120] (II) UnloadModule: "fbdev"
[ 3822.120] (II) Unloading fbdev
[ 3822.120] (II) UnloadSubModule: "fbdevhw"
[ 3822.120] (II) Unloading fbdevhw
[ 3822.120] (==) Depth 24 pixmap format is 32 bpp
[ 3822.120] (II) intel(0): [DRI2] Setup complete
[ 3822.120] (II) intel(0): [DRI2] DRI driver: i965
[ 3822.120] (II) intel(0): Allocated new frame buffer 1408x768 stride 5632, tiled
[ 3822.121] (II) UXA(0): Driver registered support for the following operations:
[ 3822.121] (II) solid
[ 3822.121] (II) copy
[ 3822.121] (II) composite (RENDER acceleration)
[ 3822.121] (II) put_image
[ 3822.121] (II) get_image
[ 3822.121] (==) intel(0): Backing store disabled
[ 3822.121] (==) intel(0): Silken mouse enabled
[ 3822.121] (II) intel(0): Initializing HW Cursor
[ 3822.121] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 3822.121] (==) intel(0): DPMS enabled
[ 3822.121] (==) intel(0): Intel XvMC decoder enabled
[ 3822.121] (II) intel(0): Set up textured video
[ 3822.121] (II) intel(0): [XvMC] xvmc_vld driver initialized.
[ 3822.121] (II) intel(0): direct rendering: DRI2 Enabled
[ 3822.121] (==) intel(0): hotplug detection: "enabled"
[ 3822.143] (--) RandR disabled
[ 3822.151] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 3822.151] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 3822.151] (II) AIGLX: enabled GLX_ARB_create_context
[ 3822.151] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 3822.151] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 3822.151] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 3822.151] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 3822.151] (II) AIGLX: Loaded and initialized i965
[ 3822.151] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 3822.151] (II) intel(0): Setting screen physical size to 361 x 203
[ 3822.232] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[ 3822.233] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 3822.233] (II) LoadModule: "evdev"
[ 3822.233] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 3822.234] (II) Module evdev: vendor="X.Org Foundation"
[ 3822.234] compiled for 1.13.0, module version = 2.7.3
[ 3822.234] Module class: X.Org XInput Driver
[ 3822.234] ABI class: X.Org XInput driver, version 18.0
[ 3822.234] (II) Using input driver 'evdev' for 'Power Button'
[ 3822.234] (**) Power Button: always reports core events
[ 3822.234] (**) evdev: Power Button: Device: "/dev/input/event3"
[ 3822.234] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 3822.234] (--) evdev: Power Button: Found keys
[ 3822.234] (II) evdev: Power Button: Configuring as keyboard
[ 3822.234] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
[ 3822.234] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 3822.234] (**) Option "xkb_rules" "evdev"
[ 3822.234] (**) Option "xkb_model" "evdev"
[ 3822.234] (**) Option "xkb_layout" "us"
[ 3822.258] (II) config/udev: Adding input device Video Bus (/dev/input/event12)
[ 3822.258] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 3822.258] (II) Using input driver 'evdev' for 'Video Bus'
[ 3822.259] (**) Video Bus: always reports core events
[ 3822.259] (**) evdev: Video Bus: Device: "/dev/input/event12"
[ 3822.259] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 3822.259] (--) evdev: Video Bus: Found keys
[ 3822.259] (II) evdev: Video Bus: Configuring as keyboard
[ 3822.259] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input12/event12"
[ 3822.259] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 3822.259] (**) Option "xkb_rules" "evdev"
[ 3822.259] (**) Option "xkb_model" "evdev"
[ 3822.259] (**) Option "xkb_layout" "us"
[ 3822.260] (II) config/udev: Adding input device Video Bus (/dev/input/event11)
[ 3822.260] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 3822.260] (II) Using input driver 'evdev' for 'Video Bus'
[ 3822.260] (**) Video Bus: always reports core events
[ 3822.260] (**) evdev: Video Bus: Device: "/dev/input/event11"
[ 3822.260] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 3822.260] (--) evdev: Video Bus: Found keys
[ 3822.260] (II) evdev: Video Bus: Configuring as keyboard
[ 3822.260] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:2f/LNXVIDEO:00/input/input11/event11"
[ 3822.260] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
[ 3822.260] (**) Option "xkb_rules" "evdev"
[ 3822.260] (**) Option "xkb_model" "evdev"
[ 3822.260] (**) Option "xkb_layout" "us"
[ 3822.261] (II) config/udev: Adding input device Lid Switch (/dev/input/event2)
[ 3822.261] (II) No input driver specified, ignoring this device.
[ 3822.261] (II) This device may have been added with another device file.
[ 3822.262] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 3822.262] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event6)
[ 3822.262] (II) No input driver specified, ignoring this device.
[ 3822.262] (II) This device may have been added with another device file.
[ 3822.263] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event7)
[ 3822.263] (II) No input driver specified, ignoring this device.
[ 3822.263] (II) This device may have been added with another device file.
[ 3822.263] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event8)
[ 3822.264] (II) No input driver specified, ignoring this device.
[ 3822.264] (II) This device may have been added with another device file.
[ 3822.264] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event9)
[ 3822.264] (II) No input driver specified, ignoring this device.
[ 3822.264] (II) This device may have been added with another device file.
[ 3822.265] (II) config/udev: Adding input device Plantronics Plantronics GameCom 780 (/dev/input/event1)
[ 3822.265] (**) Plantronics Plantronics GameCom 780: Applying InputClass "evdev keyboard catchall"
[ 3822.265] (II) Using input driver 'evdev' for 'Plantronics Plantronics GameCom 780'
[ 3822.265] (**) Plantronics Plantronics GameCom 780: always reports core events
[ 3822.265] (**) evdev: Plantronics Plantronics GameCom 780: Device: "/dev/input/event1"
[ 3822.265] (--) evdev: Plantronics Plantronics GameCom 780: Vendor 0x47f Product 0xc010
[ 3822.265] (--) evdev: Plantronics Plantronics GameCom 780: Found keys
[ 3822.265] (II) evdev: Plantronics Plantronics GameCom 780: Configuring as keyboard
[ 3822.265] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1c.5/0000:19:00.0/usb2/2-2/2-2:1.3/input/input1/event1"
[ 3822.265] (II) XINPUT: Adding extended input device "Plantronics Plantronics GameCom 780" (type: KEYBOARD, id 9)
[ 3822.265] (**) Option "xkb_rules" "evdev"
[ 3822.265] (**) Option "xkb_model" "evdev"
[ 3822.265] (**) Option "xkb_layout" "us"
[ 3822.266] (II) config/udev: Adding input device Microsoft Bluetooth Notebook Mouse 5000 (/dev/input/event14)
[ 3822.266] (**) Microsoft Bluetooth Notebook Mouse 5000: Applying InputClass "evdev pointer catchall"
[ 3822.266] (II) Using input driver 'evdev' for 'Microsoft Bluetooth Notebook Mouse 5000'
[ 3822.266] (**) Microsoft Bluetooth Notebook Mouse 5000: always reports core events
[ 3822.266] (**) evdev: Microsoft Bluetooth Notebook Mouse 5000: Device: "/dev/input/event14"
[ 3822.267] (--) evdev: Microsoft Bluetooth Notebook Mouse 5000: Vendor 0x45e Product 0x700
[ 3822.267] (--) evdev: Microsoft Bluetooth Notebook Mouse 5000: Found 8 mouse buttons
[ 3822.267] (--) evdev: Microsoft Bluetooth Notebook Mouse 5000: Found scroll wheel(s)
[ 3822.267] (--) evdev: Microsoft Bluetooth Notebook Mouse 5000: Found relative axes
[ 3822.267] (--) evdev: Microsoft Bluetooth Notebook Mouse 5000: Found x and y relative axes
[ 3822.267] (--) evdev: Microsoft Bluetooth Notebook Mouse 5000: Found absolute axes
[ 3822.267] (II) evdev: Microsoft Bluetooth Notebook Mouse 5000: Forcing absolute x/y axes to exist.
[ 3822.267] (II) evdev: Microsoft Bluetooth Notebook Mouse 5000: Configuring as mouse
[ 3822.267] (II) evdev: Microsoft Bluetooth Notebook Mouse 5000: Adding scrollwheel support
[ 3822.267] (**) evdev: Microsoft Bluetooth Notebook Mouse 5000: YAxisMapping: buttons 4 and 5
[ 3822.267] (**) evdev: Microsoft Bluetooth Notebook Mouse 5000: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 3822.267] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/hci0:11/input14/event14"
[ 3822.267] (II) XINPUT: Adding extended input device "Microsoft Bluetooth Notebook Mouse 5000" (type: MOUSE, id 10)
[ 3822.267] (II) evdev: Microsoft Bluetooth Notebook Mouse 5000: initialized for relative axes.
[ 3822.267] (WW) evdev: Microsoft Bluetooth Notebook Mouse 5000: ignoring absolute axes.
[ 3822.267] (**) Microsoft Bluetooth Notebook Mouse 5000: (accel) keeping acceleration scheme 1
[ 3822.268] (**) Microsoft Bluetooth Notebook Mouse 5000: (accel) acceleration profile 0
[ 3822.268] (**) Microsoft Bluetooth Notebook Mouse 5000: (accel) acceleration factor: 2.000
[ 3822.268] (**) Microsoft Bluetooth Notebook Mouse 5000: (accel) acceleration threshold: 4
[ 3822.268] (II) config/udev: Adding input device Microsoft Bluetooth Notebook Mouse 5000 (/dev/input/mouse1)
[ 3822.268] (II) No input driver specified, ignoring this device.
[ 3822.268] (II) This device may have been added with another device file.
[ 3822.269] (II) config/udev: Adding input device Laptop_Integrated_Webcam_2M (/dev/input/event10)
[ 3822.269] (**) Laptop_Integrated_Webcam_2M: Applying InputClass "evdev keyboard catchall"
[ 3822.269] (II) Using input driver 'evdev' for 'Laptop_Integrated_Webcam_2M'
[ 3822.269] (**) Laptop_Integrated_Webcam_2M: always reports core events
[ 3822.269] (**) evdev: Laptop_Integrated_Webcam_2M: Device: "/dev/input/event10"
[ 3822.269] (--) evdev: Laptop_Integrated_Webcam_2M: Vendor 0xc45 Product 0x6430
[ 3822.269] (--) evdev: Laptop_Integrated_Webcam_2M: Found keys
[ 3822.269] (II) evdev: Laptop_Integrated_Webcam_2M: Configuring as keyboard
[ 3822.269] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input10/event10"
[ 3822.269] (II) XINPUT: Adding extended input device "Laptop_Integrated_Webcam_2M" (type: KEYBOARD, id 11)
[ 3822.269] (**) Option "xkb_rules" "evdev"
[ 3822.269] (**) Option "xkb_model" "evdev"
[ 3822.269] (**) Option "xkb_layout" "us"
[ 3822.270] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 3822.270] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 3822.270] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 3822.270] (**) AT Translated Set 2 keyboard: always reports core events
[ 3822.271] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 3822.271] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 3822.271] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 3822.271] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 3822.271] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 3822.271] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 12)
[ 3822.271] (**) Option "xkb_rules" "evdev"
[ 3822.271] (**) Option "xkb_model" "evdev"
[ 3822.271] (**) Option "xkb_layout" "us"
[ 3822.272] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event13)
[ 3822.272] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 3822.272] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 3822.272] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
[ 3822.272] (II) LoadModule: "synaptics"
[ 3822.272] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 3822.273] (II) Module synaptics: vendor="X.Org Foundation"
[ 3822.273] compiled for 1.13.1, module version = 1.6.2
[ 3822.273] Module class: X.Org XInput Driver
[ 3822.273] ABI class: X.Org XInput driver, version 18.0
[ 3822.273] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[ 3822.273] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 3822.273] (**) Option "Device" "/dev/input/event13"
[ 3822.306] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
[ 3822.306] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5590
[ 3822.306] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4582
[ 3822.306] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 3822.306] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[ 3822.307] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right double triple
[ 3822.307] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[ 3822.307] (**) Option "TapButton1" "1"
[ 3822.307] (**) Option "TapButton2" "2"
[ 3822.307] (**) Option "TapButton3" "3"
[ 3822.307] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 3822.307] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 3822.316] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input13/event13"
[ 3822.316] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 13)
[ 3822.316] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[ 3822.316] (**) synaptics: SynPS/2 Synaptics TouchPad: MaxSpeed is now 1.75
[ 3822.316] (**) synaptics: SynPS/2 Synaptics TouchPad: AccelFactor is now 0.038
[ 3822.317] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 3822.317] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[ 3822.317] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 3822.317] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 3822.317] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 3822.318] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
[ 3822.318] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
[ 3822.318] (II) config/udev: Adding input device PC Speaker (/dev/input/event4)
[ 3822.318] (II) No input driver specified, ignoring this device.
[ 3822.318] (II) This device may have been added with another device file.
[ 3822.319] (II) config/udev: Adding input device Dell WMI hotkeys (/dev/input/event5)
[ 3822.319] (**) Dell WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[ 3822.319] (II) Using input driver 'evdev' for 'Dell WMI hotkeys'
[ 3822.320] (**) Dell WMI hotkeys: always reports core events
[ 3822.320] (**) evdev: Dell WMI hotkeys: Device: "/dev/input/event5"
[ 3822.320] (--) evdev: Dell WMI hotkeys: Vendor 0 Product 0
[ 3822.320] (--) evdev: Dell WMI hotkeys: Found keys
[ 3822.320] (II) evdev: Dell WMI hotkeys: Configuring as keyboard
[ 3822.320] (**) Option "config_info" "udev:/sys/devices/virtual/input/input6/event5"
[ 3822.320] (II) XINPUT: Adding extended input device "Dell WMI hotkeys" (type: KEYBOARD, id 14)
[ 3822.320] (**) Option "xkb_rules" "evdev"
[ 3822.320] (**) Option "xkb_model" "evdev"
[ 3822.320] (**) Option "xkb_layout" "us"
[ 3822.330] (II) intel(0): EDID vendor "AUO", prod id 12380
[ 3822.330] (II) intel(0): Printing DDC gathered Modelines:
[ 3822.330] (II) intel(0): Modeline "1366x768"x0.0 70.00 1366 1414 1446 1470 768 771 777 793 +hsync -vsync (47.6 kHz eP)
[ 3822.715] (II) intel(0): EDID vendor "AUO", prod id 12380
[ 3822.715] (II) intel(0): Printing DDC gathered Modelines:
[ 3822.715] (II) intel(0): Modeline "1366x768"x0.0 70.00 1366 1414 1446 1470 768 771 777 793 +hsync -vsync (47.6 kHz eP)
[ 3833.041] (II) intel(0): EDID vendor "AUO", prod id 12380
[ 3833.041] (II) intel(0): Printing DDC gathered Modelines:
[ 3833.041] (II) intel(0): Modeline "1366x768"x0.0 70.00 1366 1414 1446 1470 768 771 777 793 +hsync -vsync (47.6 kHz eP)
[ 3833.208] (II) intel(0): EDID vendor "AUO", prod id 12380
[ 3833.208] (II) intel(0): Printing DDC gathered Modelines:
[ 3833.208] (II) intel(0): Modeline "1366x768"x0.0 70.00 1366 1414 1446 1470 768 771 777 793 +hsync -vsync (47.6 kHz eP)
[ 3833.654] (II) intel(0): EDID vendor "AUO", prod id 12380
[ 3833.654] (II) intel(0): Printing DDC gathered Modelines:
[ 3833.654] (II) intel(0): Modeline "1366x768"x0.0 70.00 1366 1414 1446 1470 768 771 777 793 +hsync -vsync (47.6 kHz eP)
[ 4144.113] (II) evdev: Dell WMI hotkeys: Close
[ 4144.113] (II) UnloadModule: "evdev"
[ 4144.113] (II) UnloadModule: "synaptics"
[ 4144.113] (II) evdev: AT Translated Set 2 keyboard: Close
[ 4144.113] (II) UnloadModule: "evdev"
[ 4144.113] (II) evdev: Laptop_Integrated_Webcam_2M: Close
[ 4144.113] (II) UnloadModule: "evdev"
[ 4144.113] (II) evdev: Microsoft Bluetooth Notebook Mouse 5000: Close
[ 4144.114] (II) UnloadModule: "evdev"
[ 4144.114] (II) evdev: Plantronics Plantronics GameCom 780: Close
[ 4144.114] (II) UnloadModule: "evdev"
[ 4144.114] (II) evdev: Video Bus: Close
[ 4144.114] (II) UnloadModule: "evdev"
[ 4144.114] (II) evdev: Video Bus: Close
[ 4144.114] (II) UnloadModule: "evdev"
[ 4144.114] (II) evdev: Power Button: Close
[ 4144.114] (II) UnloadModule: "evdev"
[ 4144.870] Server terminated successfully (0). Closing log file.
I can use optirun or primusrun I have both installed. I have run both optirun and primusrun with the xrandr queries to see about detecting a secondary display with the Displayport or hdmi and nothing! Any helps, tips, tricks, comments would be greatly appreciated because I am designing an Android application for my work and could use my secondary display working for more screen space.
**EDIT #1**
What I am currently running:
nvidia bumblebee/primus-git driver from AUR 313.18-1 and I am going to update my git repos of lib32-primus-git and primus-git to see if that doesn't help...
Also using 3.7.4-1-ARCH kernel.
**EDIT #2**
Okay so I have found out that the HDMI/VGA1 are both I guess hooked up to the GT 540M card which means that it won't show up without bumblebee/primus working. So I have tried using the Bumblebee how-to guide on github how to setup an external secondary display and well it really didn't work well at all!
First I did this:
I removed from /etc/bumblebee/bumblebee.conf KeepUnusedXServer = false to = true. I also have removed the UseEDID, and Option "AutoAddDevices" "false", from /etc/bumblebee/xorg.conf.nvidia. Also have tried to setup an export path before running commands:
export DISPLAY=:8 LD_LIBRARY_PATH=/usr/lib/nvidia-bumblebee:$LD_LIBRARY_PATH
optirun -vv true
[ 711.059889] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
[ 711.250374] [DEBUG]optirun version 3.0.1 starting...
[ 711.250427] [DEBUG]Active configuration:
[ 711.250450] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
[ 711.250457] [DEBUG] X display: :8
[ 711.250464] [DEBUG] LD_LIBRARY_PATH: /usr/lib/nvidia-bumblebee:/usr/lib32/nvidia-bumblebee
[ 711.250470] [DEBUG] Socket path: /var/run/bumblebee.socket
[ 711.250476] [DEBUG] VGL Compression: proxy
[ 711.447419] [INFO]Response: No - error: Could not load GPU driver
[ 711.447441] [ERROR]Cannot access secondary GPU - error: Could not load GPU driver
[ 711.447447] [DEBUG]Socket closed.
[ 711.447463] [ERROR]Aborting because fallback start is disabled.
[ 711.447469] [DEBUG]Killing all remaining processes.
Last edited by adramalech (2013-01-31 20:55:47)

Thanks, I finally find the same question here,posted a year ago.
https://discussions.apple.com/thread/4249436?start=30&tstart=0
But there is still no solutions today.
Thanks God! I found a way to solve that.
MonitorMenu-DisplaySetting--Sharpness----Set it to 0. This finally solved my problem.

Dell 2400MP projector and mini-DisplayPort

I have a MacBook Pro with a mini-DisplayPort and wanted to know which mini-DisplayPort to VGA adapter should I get to connect to the Dell 2400MP? It only has a VGA port, and I'm doing a presentation at a place that uses such a projector, and wanted to be prepared in case no one there knows how to use the PC and bring my own laptop. I see the mileage on these adapters may vary, so which one works best?

Get the Apple adapter. It costs more, but it's made better than most.

Surface Pro 3 Display/Video/Graphics Driver Issues - DisplayPort, External Monitors, Windows 10 Build 9926

Surface Pro 3 - i5 with Intel HD Graphics 4400
Windows 10 build 9926
All Latest updates installed
Intel Graphics Driver 10.18.15.4079.
Latest system update released on Jan 22nd (which I understand is just the latest intel graphics driver?).
The display driver status has this error message: Windows has stopped this device because it
has reported problems. (Code 43) - I assume it's
reverting to the basic Microsoft driver when this occurs. Which explains why my displayport (External monitors) will not work.
I have uninstalled the driver completely (and deleted the driver files), tried the Windows basic driver,
and rebooted several times with no luck.
I cannot get my docking station displayport or the displayporton my surface pro 3 working.
According to Microsoft (see below), this is a known issue UNTIL you update to display driver
version 4079 - which I have.
Known issues on Surface after updating to Windows 10 January Technical Preview
On Surface Pro 2 and Surface Pro 3, the Mini DisplayPort won’t work on the Windows 10 January Technical Preview until you’ve installed graphics driver 4079 or later. Check Windows Update often for the most recent graphics driver.
On Surface Pro 2 and Surface Pro 3, you’ll notice poor graphics rendering on the Windows 10 January Technical Preview until you’ve installed graphics driver 4079 or newer from Windows Update. Check Windows Update often for the most recent graphics driver.
If you’re using video driver 3496, you may need to start in safe mode and remove that driver. Then restart Surface in normal mode and go to Windows Update to get the most recent graphics driver.

Hi Nicholas,
Similar issue has been asked here:
Surface Pro 3 restarting after a series of blank screens!
For error code 43, here is a reference:
Code 43: Windows has stopped this device because it has reported problems
For the current situation, please try to wait for the driver update, as display driver version 4079 didn't work well at your side, please submit this through Windows Feedback Tool.
Best regards
Michael Shao
TechNet Community Support

Mid 2010 Macbook pro - Mini DisplayPort to Hdmi issues

Hi there! I'm having some issues connecting my mid 2010 Macbook pro to my 32" Toshiba LED TV.
I'm running OS X Version 10.8.2 , as mentioned before, on the mid 2010 Macbook pro.
The issue which I have, is that when I connect my Hdmi cable to my minidisplay port through the adapter, I keep getting a blue screen popping up.
I am using a Startech MiniDisplay to HDMI Adapter Converter and ION 6FT Flat HDMI CABLE.
anyone with suggestions on help?

I had issues with getting my MBP to work with my Vizio XVT323SV via the RGB port. What worked for me was downloading SwitchResX (http://www.madrau.com/indexSRX4.html) and setting up a custom 1920x1080 resolution using the values found in the Vizio user guide. Works like a champ now. Best shareware investment I ever made. Now I can watch my EyeTV recordings at full HD resolution.
Hope this helps. Good luck!
Sidebar: I also bought the Griffin mini-DisplayPort to HDMI adapter and an HDMI cable, but I can't get any signal at all via that connection. The Mac doesn't see the TV and the TV doesn't see a signal. Very frustrating. My RGB connection is good enough but I bet HDMI would be even better.

External display via Mini DisplayPort to DVI no longer works with MacBook.

I had not used my external monitor in the last several weeks. I believe there have been a few OSX Lion updates since the last time I used the external monitor. I had installed all the updates prior to connecting my external monitor again. However, a few days ago I tried to connect the external monitor and all I get is a "No Signal" message on my external monitor. The Mini DisplayPort to HDMI works on my LCD TV, so I know the MDP works. I have also replaced the MDP-to-DVI cord and the external display still doesn't work.
I connected the external monitor to another computer running Snow Leopard and the external monitor works. So, the external monitor does work.
I have seen a few posts aboout this, but nobody seems to have a solution that works or is directly on point to my issue. I have tried to use all the scenarios for plugging in the external monitor and external monitor power. I tried to reboot the laptop with and withoout the external monitor connected. Same thing with the exteernal monitor plugged in and no power, etc. Nothing works. I have tried to repeatedly turn the external monitor on and off while connected to the MacBook. Again, that doesn't work.
So, I am open to any help someone may have. Here is what I am running:
MacBook, Aluminum 13" Late 2008
OSX 10.7.3
NVIDIA GeForce 9400M

While we all have MacBooks in this forum most of us don’t run Lion. There's a Lion Support Community where everybody has Lion. You should also post this question there to increase your chances of getting an answer. Lion seems to have problems with external monitors. https://discussions.apple.com/community/mac_os/mac_os_x_v10.7_lion

Displayport

Similar Messages

Maybe you are looking for