T500 Closing Laptop Lid but no External Monitor Output

Hello everyone. I have a Lenovo T500 (WInXP) with an external monitor. I usually just want to use that external monitor and not the one for my laptop. However, every time I close the lid, the output to the monitor disappears a few seconds later. I've used google and searched this forum and found something similar, change the power settings. I changed it so it would "Do nothing" when the lid is closed. However, this does nothing and doesn't help me.
Is there a registry I have ti change?
Related links I've look at and tried
From Knowledge Base:
http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/Configuring-a-ThinkPad-T500-to-run-with-the...
Another person
http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T500-goes-to-sleep-with-lid-closed/td-p/307...
T500 2081 CTO ~ T9600 2.8GHz ~ WXP Pro 32bit ~ WSXGA+ 15.4 LED ~ATI 3650 ~ 4GB DDR3 RAM ~ 500GB WD 7200rpm
Camera ~ AT&T WWAN ~ CD/DVD Combo Drive ~ Intel WiFi 5300 AGN

I didn't see if your connected to power? there are different settings for both power and battery.
There are also bios settings for the display, since I am using my T500 now with an external LCD I have it set to external display or something like that. Its worth a shot.
BIOS>>CONFIG>DISPLAY read the output options.
IT Specialist and Consultant
Lenovo Tablet Evangelist
Current Machines: IdeaCentre A300, ThinkPad Tablet, IdeaPad U410, and Yoga 3 Pro Touch
Deutsche Community Comunidad en Español
Lenovo - the latest in DOtabs, DOpads, DOcentre's, DOstations and DOservers!

Similar Messages

HT5019 MacPro laptop display and 2 external monitors (three displays). Can I have more than one application displayed at a time?

I would like to have my MacPro laptop display and 2 external monitors (three displays). Question, how can I have more than one application displayed at a time? IE: I would like email on one monitor, Finder on my laptop, and iTunes on the other. Possible?
With extended desktop, it appears that I can only have one application presenting at a time. Sort of defeats the purpose of having multiple displays.
I am using the HDMI and the mini HDMI connectors.

I would like to have my MacPro laptop display and 2 external monitors (three displays). Question, how can I have more than one application displayed at a time? IE: I would like email on one monitor, Finder on my laptop, and iTunes on the other. Possible?
With extended desktop, it appears that I can only have one application presenting at a time. Sort of defeats the purpose of having multiple displays.
I am using the HDMI and the mini HDMI connectors.

MacBook Pro keeps going to sleep in closed-lid mode and external monitor

I am trying to run the MacBook in closed lid mode with an external monitor. It seems to work fine at first, but after about 10 seconds, it goes to sleep. I can wake it back up but it just goes to sleep again.
Has anyone seen this before?

I figured it out. Apparently you can't run in closed-lid mode on battery. I plugged in the power adapter and it's working fine now.

Closed lid, connected to external monitor with no image...

So I followed the directions on Apple support regarding setting up a Macbook Pro (Early 2008) to an external monitor. I'm using a Gateway FPD2275w (if that helps) connected to the DVI-VGA adapter, or whatever Apple calls it. I'm using a Bluetooth mouse and keyboard and have set the option to wake the Mac from sleep with them. I've set the display to mirror, though it doesn't seem to matter what I set that option to. WHen I close the lid the Mac goes to sleep and the external display goes to sleep as well, but when typing on the keyboard it shows on the screen, when I open it up again. Any thoughts?

You must also have an external USB or BlueTooth keyboard connected, not just a display. Alternatively, you can try the third-party utility InsomniaX - VersionTracker or MacUpdate.

External HDD and closing laptop lid

I have a Seagate external hdd connected to my Macbook Pro via Firewire 800. I use it exclusively for Time Machine backups. Can I just close the lid of my laptop when it's done backing up or do I have to eject the drive each time?
-Skifahrer7

Hi Skifahrer7,
You do not need to properly eject the external HD before closing the lid. When the machine wakes (on lid open) it will automatically remount the volume/drive.

Xorg not functional after closing laptop lid.

Hi all!
Recently I've bought a monitor and I wanted to use my laptop more like a pc. But when I close the lid my both my screens go black. I'd like to use my computer with the lid closed normally.
Also, when I open the lid back I still have black screen only, both on laptop and monitor.
When I go to other terminal (ctrl+alt+F1..6) everything is fine on both screens. When I press alt+f7 and go back I have a black screen again.
I've looked at https://wiki.archlinux.org/index.php/Acpid and then looked at /etc/acpi/handler.sh, but it seems that I have no action assigned at lid closure so it should do nothing.
Here is the mentioned file:
#!/bin/sh
# Default acpi script that takes an entry for all actions
minspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq`
maxspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq`
setspeed="/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed"
set $*
case "$1" in
button/power)
echo "PowerButton pressed!">/dev/tty5
case "$2" in
PBTN|PWRF) logger "PowerButton pressed: $2" ;;
*) logger "ACPI action undefined: $2" ;;
esac
button/sleep)
case "$2" in
SLPB) echo -n mem >/sys/power/state ;;
*) logger "ACPI action undefined: $2" ;;
esac
ac_adapter)
case "$2" in
AC|ACAD|ADP0)
case "$4" in
00000000)
echo -n $minspeed >$setspeed
#/etc/laptop-mode/laptop-mode start
00000001)
echo -n $maxspeed >$setspeed
#/etc/laptop-mode/laptop-mode stop
esac
*) logger "ACPI action undefined: $2" ;;
esac
battery)
case "$2" in
BAT0)
case "$4" in
00000000) echo "offline" >/dev/tty5
00000001) echo "online" >/dev/tty5
esac
CPU0)
*) logger "ACPI action undefined: $2" ;;
esac
button/lid)
case "$3" in
close)
echo "LID closed!">/dev/tty5
open)
echo "LID opened!">/dev/tty5
esac
logger "ACPI group/action undefined: $1 / $2"
esac
As you can see on the bottom I do not have anything assigned to lid action.
Any thoughts?
cheers,
kajman

I'm using xfce4.
Here's my /etc/X11/xorg.conf.d/10-monitor.conf:
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
Option "BlankTime" "0"
Option "StandbyTime" "0"
Option "SuspendTime" "0"
Option "OffTime" "0"
EndSection
Section "Monitor"
Identifier "Monitor0"
EndSection
Section "Device"
Identifier "Device0"
Driver "radeon" #Choose the driver used for this monitor
EndSection
Section "Screen"
Identifier "Screen0" #Collapse Monitor and Device section to Screen section
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24 #Choose the depth (16||24)
SubSection "Display"
Depth 16
Modes "1366x768_60.00" #Choose the resolution
Virtual 1920 1080
EndSubSection
EndSection
But i think that this configuration may be irrevelant.
When I connect my external monitor I always type
xrandr --auto
When unplugging the monitor I also type the same command.
Also I have turned my laptop's screen off (using settings/screen I've unchecked "use this output").
Last edited by kajman (2012-02-15 17:42:43)

Yosemite: Turning off Macbook Pro screen (lid open) with external monitor connected

Here we go again, this worked pre-Yosemite. Now it seems this trick no longer works. After following these steps again the screen on my Macbook Pro now turns on after logging in and opening the clam shell.
Anyone figure out/know a way to turn off the screen on the Macbook Pro with external monitors plugged in? (yes, closing the clam shell–but I'm referring to keeping the clam shell open with the display turned off)
http://gizmodo.com/5938452/a-trick-to-make-using-an-external-monitor-with-your-m acbook-way-better
To execute in Terminal:
sudo nvram boot-args="iog=0x0"
To undo in Terminal:
sudo nvram -d boot-args
Once you type it into terminal I believe you need to enter your password. I then restart my machine. Now the TRICK is to either restart your machine with the lid already closed (hit restart then slam the lid!) OR turn the machine on for the first time (then quickly slam the lid!) once you are past the login screen you can open the lid.

Has anyone experimented with tip 2 (active corners)? Perhaps it still works.
http://www.cultofmac.com/176329/turn-off-internal-lcd-display-of-your-macbook-ai r-os-x-tips/
Κοσμά τι λες; Τα έχεις μπερδέψει. Άλλο συζητάμε εδώ. Το ότι δεν μπορείς πια να δουλεύεις μόνο με την εξωτερική οθόνη (να έχεις σβηστή την ενσωματωμένη οθόνη όταν έχεις συνδεμένη εξωτερική).

Time machine disk failure after closing laptop lid

I have a Seagate 1.5 TB disk that I'm using for a time machine backup (USB). For a long time, I had the disk formatted wrong and had this problem, but I re-formatted it (per Apple's instructions) and have been trying again. Now, with it correctly formatted, I still have the same problem.
This is a laptop, so I don't leave the Time Machine application on, nor do I leave the TM disk connected all the time. If I plug in the drive, run TM, and eject the disk before closing the laptop lid, I do not have any issues. If, however, the laptop lid is shut at any point after TM completes, I have can never seem to eject nor unmount the TM disk. For example, last night I ran TM and left the machine open overnight. In the morning, the machine was used and shut per usual routine, except the drive was still connected. Now there is a critical failure on the drive (Disk Utility can do nothing to repair the drive and suggests re-formatting). Last night, the computer was plugged in and went to sleep after 15 minutes. I have changed no settings regarding what the computer does on lid shutdown.
What used to work to eject/unmount the drive is to shutdown the computer. Then I would unplug the drive before re-starting. Now, however, I had errors with the drive (Disk Utility) and went ahead with a force eject. That worked, and the drive still had errors that Disk Utility could not address.
I have a Macbook Pro (13-inch, mid 2012) running Mac OS X Version 10.9.2 (13C64); processor 2.9 GHz Intel Core i7 with 8 GB 1600 MHz DDR3 memory. My main drive is 750 GB (Macintosh HD). I also backup a firewire 400 drive to this TM drive, capacity 250 GB.
So, first question: why is this happening over and over and over? Is there anything I can do, apart from immediate removal of the TM drive after the backup completes, to ensure that it doesn't happen in the future? Should I be concerned that the disk is failing mechanically?
Thanks

I don't think you quite understand how Time Machine really works. But then hardly anyone does. Time Machine is intended to be left enabled always whether a backup drive is connected or not. What Time Machine cannot handle properly is a situation where the backup drive loses power for whatever reason. Time Machine treats this, as does the OS, as an improper disconnect of an external drive without being properly ejected. This in turn throws Time Machine a little bit of a loop.
For you I would suggest not using Time Machine. Instead use a third-party backup utility that you can either schedule or run manually as you wish. They will work with the same drive you have used for Time Machine, but you will need to first erase the Time Machine drive using Disk Utility. Please DO NOT try dragging the Time Machine backups to the Trash.
Here are some good backup utilities you can try:
Suggested Backup Software
1. Carbon Copy Cloner
2. Get Backup
3. Deja Vu
4. SuperDuper!
5. Synk Pro
6. Tri-Backup
Others may be found at MacUpdate. Each one can be used for a trial period. No need to pay for one until you've decided on which one you like best. I, for example, use Carbon Copy Cloner but please don't take that as a recommendation over the others. It's just my preference. All can be operated manually or can be set up to backup on a schedule you determine. Some can even be set up to backup as soon as the backup drive is connected.
Visit The XLab FAQs and read the FAQ on backup and restore. Also read How to Back Up and Restore Your Files.

How to blank laptop screen when using external monitor/

Hi there
I need some help with figuring out how to configure my xorg.conf for my Arch Linux 64 bit installation on a HP Pavilion dv 5000 laptop so that I can automatically blank my laptop screen when using an external monitor. I have Arch Linux installed along with Ubuntu Feisty. In Ubuntu my external monitor (Viewsonic 1912WB) was not detected at the time of installation but with the native 1280X800 resolution that is good for the laptop takes effect for the external monitor automatically when the external monitor is plugged in. The laptop monitor goes blank when the external monitor is plugged in.
In my Arch Linux installation I have not been able to configure a dual head configuration using the ATI Radeon drivers (fglrx). I have the native 1280X800 resolution set up for the laptop monitor and this resolution takes effect for the external monitor also. However the laptop monitor also continues to function when the external monitor is plugged in. I would like to blank the laptop monitor when using the external monitor.
I am attaching my Arch Linux xorg.conf and the Ubuntu xorg.conf below. Thanks for anyone who can help, I am having a lot of difficulty in figuring out how to set up xorg.conf among all the things that I have had to learn so far in Linux and I am a relative newcomer to the whole thing. I have tried to compare the two xorg.conf files and edit my Arch xorg.conf in accordance with the Ubuntu one but it did not work and I keep getting errors!
I am using XFCE as my Desktop environment.
Arch Linux xorg.conf
# File generated by xorgconfig.
# Copyright 2004 The X.Org Foundation
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
# Refer to the xorg.conf(5) man page for details about the format of
# this file.
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# Files section. This allows default font and rgb paths to be set
# Server flags section.
# Input devices
# Core keyboard's InputDevice section
# Core Pointer's InputDevice section
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the xorg.conf man page for a description of the options.
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Monitor section
# Any number of monitor sections may be present
# Graphics device section
# Any number of graphics device sections may be present
# Standard VGA Device:
# Device configured by xorgconfig:
# Screen sections
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
# ServerLayout sections.
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
# Section "DRI"
# Mode 0666
# EndSection
Section "ServerLayout"
# The Identifier line must be present
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
Identifier "Simple Layout"
Screen 0 "aticonfig-Screen[0]" 0 0
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
# RgbPath "/usr/share/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
# FontPath "/usr/share/fonts/TTF"
# FontPath "/usr/share/fonts/Type1"
# FontPath "/usr/lib/X11/fonts/local/"
# FontPath "/usr/lib/X11/fonts/misc/"
# FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/Speedo/"
# FontPath "/usr/lib/X11/fonts/Type1/"
# FontPath "/usr/lib/X11/fonts/TrueType/"
# FontPath "/usr/lib/X11/fonts/freefont/"
# FontPath "/usr/lib/X11/fonts/75dpi/"
# FontPath "/usr/lib/X11/fonts/100dpi/"
# The module search path. The default path is shown here.
# ModulePath "/usr/lib/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
EndSection
Section "Module"
# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the font modules
# Load "type1"
# This loads the GLX module
# Load "glx"
# This loads the DRI module
# Load "dri"
Load "dbe" # Double buffer extension
SubSection "extmod"
Option    "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "freetype"
# Load "xtt"
EndSection
Section "InputDevice"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Identifier "Keyboard1"
Driver "kbd"
Option    "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
Option    "XkbRules" "xorg"
Option    "XkbModel" "pc104"
Option    "XkbLayout" "us"
EndSection
Section "InputDevice"
# Identifier and driver
# the following line.
# Option "Protocol" "Xqueue"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Mouse wheel mapping. Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7. Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
Identifier "Mouse1"
Driver "mouse"
Option    "Protocol" "Auto" # Auto detect
Option    "Device" "/dev/input/mice"
# When using XQUEUE, comment out the above two lines, and uncomment
Option    "ZAxisMapping" "4 5 6 7"
# Emulate3Buttons is an option for 2-button mice
EndSection
Section "Monitor"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
Identifier "My Monitor"
HorizSync 30.0 - 62.0
VertRefresh 50.0 - 70.0
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]"
Option    "VendorName" "ATI Proprietary Driver"
Option    "ModelName" "Generic Autodetecting Monitor"
Option    "DPMS" "true"
EndSection
Section "Device"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
Identifier "Standard VGA"
Driver "vga"
VendorName "Unknown"
BoardName "Unknown"
EndSection
Section "Device"
#VideoRam 131072
# Insert Clocks lines here if appropriate
Identifier "* Generic VESA compatible"
Driver "vesa"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
EndSection
Section "Screen"
Identifier "Screen 1"
Device "* Generic VESA compatible"
Monitor "My Monitor"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 8
Modes "1280x800" "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1280x800" "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x800" "800x600" "640x480"
EndSubSection
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]"
Device "aticonfig-Device[0]"
Monitor "aticonfig-Monitor[0]"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Ubuntu xorg.conf
# /etc/X11/xorg.conf (xorg X Window System server configuration file)
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
# Edit this file with caution, and see the xorg.conf(5) manual page.
# (Type "man xorg.conf" at the shell prompt.)
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg
Section "Files"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
# path to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection
Section "Module"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "vbe"
EndSection
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection
Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizScrollDelta" "0"
EndSection
Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection
Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/input/wacom"
Option "Type" "eraser"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection
Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/input/wacom"
Option "Type" "cursor"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection
Section "Device"
Identifier "ATI Technologies Inc ATI Radeon XPRESS 200M 5955 (PCIE)"
Driver "ati"
BusID "PCI:1:5:0"
EndSection
Section "Monitor"
Identifier "Generic Monitor"
Option "DPMS"
EndSection
Section "Screen"
Identifier "Default Screen"
Device "ATI Technologies Inc ATI Radeon XPRESS 200M 5955 (PCIE)"
Monitor "Generic Monitor"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1280x800"
EndSubSection
SubSection "Display"
Depth 4
Modes "1280x800"
EndSubSection
SubSection "Display"
Depth 8
Modes "1280x800"
EndSubSection
SubSection "Display"
Depth 15
Modes "1280x800"
EndSubSection
SubSection "Display"
Depth 16
Modes "1280x800"
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x800"
EndSubSection
EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "stylus" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
InputDevice "Synaptics Touchpad"
EndSection
Section "DRI"
Mode 0666
EndSection

Xrandr 1.2 provides means for this. But today the only supported configuration is xorg-server-1.3 + xf86-video-intel-2.0. So for Radeon you'll have to wait for drivers that support Randr 1.2.
On my laptop (Thinkpad x60s) that would be:
xrandr --output VGA --auto
xrandr --output LVDS --off

Kernel 2.6.32.2-2 black screen after closing laptop lid (intel + KMS)

Today I updated my laptop with the new 2.6.32.2-2 kernel from core. Previous update of my system was just a few days back, so there are no massive changes to other packages and I also don't use testing packages.
Since the update, after closing the laptop lid (which just blanks my screen) and I want to continue working I just have a black screen (no backlight) and the screen won't respond to mouse or keyboard input. I have to reboot (ctr-alt-del or pushing my power button) or switch to VT1 and back to VT7 to get my screen back. I'm absolutely positive that this was not a problem before, it worked fine with 2.6.30 and 2.6.31 kernels with my same configuration.
HP 6730b laptop
Intel GMA 4500 (Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07))
Intel driver 2.9.1-1 using KMS with early start (modprobe.conf) and I rebuilt my initcpio to the new 2.6.32.2-2 kernel
Gnome 2.28.2
Can anyone confirm this behaviour? Should I file a bug somewhere? I read about lots of upgrade problems with this new kernel, but for the rest everything else works fine so far.
Thanks for your feedback.
Ulukai

moose jaw wrote:
ulukai wrote:@ Moose Jaw: I also looked into pm-suspend, but i guess it is only usefull for suspending and resuming sessions (something I never do)? Is there a command you know for simulating closing the lid and reopening it again?
Isn't suspending and resuming a session exactly what you're doing (or hoping to do) when you close your lid and then open it up again? I.e., putting the machine into a low-power sleep state and then having everything come back to where you were when you wake it up? You mentioned that the Gnome power management tools depend on pm-utils, which suggests that somewhere in there "pm-suspend" is getting called. If you can find out where it's getting called (i.e., in some script that Gnome power manager uses), and try changing it to "pm-suspend --quirk-vbestate-restore" (or one of the other quirks, perhaps), then that may bring your screen back on wakeup.
Hehe, nope I don't hope to suspend :-) I just close the lid to save the display (and some power) but want my machine to keep running (when downloading torrents or when I'm going to eat etc...) Also it keeps the dust from entering the keyboard ;-)
I also took a look at the post where there should be a patch present, but I think it's for another problem: flickering screens.
For me it's a bug in intel driver or kernel, but still it's strange that KDE doesn't suffer from this!

Hard lockup when closing laptop lid (Linux 2.6.23)

I just found this out a few days ago, telling my laptop to shut down a few hours later, and still finding it running half a day later, severely overheated (!).
I am running a custom kernel (2.6.23.1 with some of the kamikaze broken out patches). I get this:
- I unplug the laptop USB mouse
- I close the lid
- I reopen the lid, only to find my system completely locked up (no screen refresh anymore, no possibility to switch to a virtual terminal, no possibility to restart X or restart the system (Ctrl+Alt+Del/Backspace aren't working at all).
I have no action specified for closing the lid (I plan on making it do suspend to RAM as soon as this issue is cleared up). Now if I leave the USB laptop mouse plugged in all works fine. I can close the lid, open it up again, and my system remains fully usable.
To make sure this wasn't just me being clumsy and compiling a bad kernel, I tried the 2.6.23-ARCH kernel from testing. It exhibits exactly the same behaviour. 2.6.22-ARCH works just fine.
Are there people having the same issue?
Last edited by B (2007-10-21 12:16:32)

Okay guys . I got some goodies up . For those interested:
- 2.6.22.12 kernel with CFS v22, hrtimers, powertop, Reiser4 and default CPU frequency governor 'ondemand'
- iwlwifi 1.1.21
- Authentec fingerprint reader driver
I guess that should get you going pretty much . The iwlwifi drivers have been built out-of-tree since my efforts to merging in the newer mac80211 stack & latest iwlwifi drivers amounted to nothing but a boatload of patch errors :-( (yes i can hack up patches to work but I felt like not doing it, since iwlwifi builds just fine out-of-tree). This kernel is tailored to the 6510 hardware, I cannot tell what is different in the 6170b lineup, but you definitely should not try this kernel on just any machine .
If you have any questions, drop me a line.
Credit of course to waninkoko for his kamikaze patchset, from which most of the patches come.
Update: to the latest 2.6.22.12 kernel + corresponding driver packages
Last edited by B (2007-11-11 16:39:48)

Poor Lightroom 4.4 performance when laptop connected to an external monitor

Hello everyone,
I have recently purchased an external monitor JUST to be able to edit my photos at a higher resolution (1920*1080). However, Lightroom performance is extremely bad and the sliders and crop tool are all laggy when I just connect the monitor that I have bought . Doing the same task on my laptop monitor takes much less time and runs perfectly smooth (the resolution of the laptop is 1366*768).
Is this an issue with Lightroom 4.4 or is it my because my laptop is not fast enough?
Here is some more information about my system specs:
The Lightroom version is 4.4 and I have a laptop with 8 GB ram, a 2.4 GHz Intel Core i5 CPU, the GPU is Radeon HD 5650.
My OS is Windows 7 64 bit and the connection to the monitor is via a VGA cable
I just want to use the external monitor (single display) so I use it as a projector and I do not extend the displays. I just wanted to edit my photos with a higher resolution monitor so that I see the editing flaws in them more easily.
Please help me if you know how to deal with this because otherwise I have to return the monitor because it's of no use.

The higher resolution is pushing you to the next higher rendering resolution. If you are in Develop and set zoom position to 1:4 or 1:8 it should speed back up (each level is 4 times as fast as tge previous).

[SOLVED] how to prevent suspending/sleeping when closing laptop lid

Hi all,
My laptop, a Lenovo Thinkpad T430u, suspends whenever I close the lid. It's been doing this since I first installed Arch. I want to turn this feature off. How can I do it?
Relevant information:
acpid is installed
the configuration file /etc/acpi/handler.sh
#!/bin/bash
# Default acpi script that takes an entry for all actions
case "$1" in
button/power)
case "$2" in
PBTN|PWRF)
logger 'PowerButton pressed'
logger "ACPI action undefined: $2"
esac
button/sleep)
case "$2" in
SLPB|SBTN)
logger 'SleepButton pressed'
logger "ACPI action undefined: $2"
esac
ac_adapter)
case "$2" in
AC|ACAD|ADP0)
case "$4" in
00000000)
logger 'AC unpluged'
00000001)
logger 'AC pluged'
esac
logger "ACPI action undefined: $2"
esac
battery)
case "$2" in
BAT0)
case "$4" in
00000000)
logger 'Battery online'
00000001)
logger 'Battery offline'
esac
CPU0)
*) logger "ACPI action undefined: $2" ;;
esac
button/lid)
case "$3" in
close)
logger 'LID closed'
open)
logger 'LID opened'
logger "ACPI action undefined: $3"
esac
case $(cat /proc/acpi/button/lid/LID0/state | awk '{print $2}') in
closed) XAUTHORITY=$(ps -C xinit -f --no-header | sed -n 's/.*-auth //; s/ -[^ ].*//; p') xset -display :0 dpms force off ;;
open) XAUTHORITY=$(ps -C xinit -f --no-header | sed -n 's/.*-auth //; s/ -[^ ].*//; p') xset -display :0 dpms force on ;;
esac
logger "ACPI group/action undefined: $1 / $2"
esac
# vim:set ts=4 sw=4 ft=sh et:
dmesg output:
[ 1530.790532] PM: Syncing filesystems ... done.
[ 1530.805678] PM: Preparing system for mem sleep
[ 1530.844445] Freezing user space processes ... (elapsed 0.01 seconds) done.
[ 1530.856658] Freezing remaining freezable tasks ... (elapsed 0.10 seconds) done.
[ 1530.963435] PM: Entering mem sleep
[ 1530.963572] Suspending console(s) (use no_console_suspend to debug)
[ 1531.123543] iwlwifi 0000:03:00.0: iwl_pcie_cmdq_reclaim: Read index for DMA queue txq id (9), index 207 is out of range [0-256] 208 208.
[ 1531.124216] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 1531.124579] sd 0:0:0:0: [sda] Stopping disk
[ 1531.360682] mei 0000:00:16.0: suspend
[ 1531.440517] ahci 0000:00:1f.2: power state changed by ACPI to D3hot
[ 1531.687309] PM: suspend of devices complete after 722.490 msecs
[ 1531.687784] PM: late suspend of devices complete after 0.469 msecs
[ 1531.688232] pcieport 0000:00:1c.3: System wakeup enabled by ACPI
[ 1531.714222] ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
[ 1531.727619] ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
[ 1531.754015] xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
[ 1531.767422] PM: noirq suspend of devices complete after 79.565 msecs
[ 1531.768301] ACPI: Preparing to enter system sleep state S3
[ 1531.797647] PM: Saving platform NVS memory
[ 1531.799282] Disabling non-boot CPUs ...
[ 1531.900721] smpboot: CPU 1 is now offline
[ 1532.004162] smpboot: CPU 2 is now offline
[ 1532.107554] smpboot: CPU 3 is now offline
I have pmutils and tlpinstalled
tlp config
# tlp - Parameters for power save
# Hint: some features are disabled by default, remove the leading # to enable them
# Set to 0 to disable/1 to enable TLP
TLP_ENABLE=1
# Seconds laptop mode has to to wait after the disk goes idle before doing a sync.
# Non-zero value enables, zero disables laptop mode.
DISK_IDLE_SECS_ON_AC=0
DISK_IDLE_SECS_ON_BAT=2
# Dirty page values (timeouts in secs).
MAX_LOST_WORK_SECS_ON_AC=15
MAX_LOST_WORK_SECS_ON_BAT=60
# Select a cpu frequency scaling governor: ondemand/powersave/performance/conservative
# Important:
# - You *must* disable your distribution's governor settings or conflicts will occur
# - ondemand is sufficient for *almost all* workloads, you should know what you're doing!
#CPU_SCALING_GOVERNOR_ON_AC=ondemand
#CPU_SCALING_GOVERNOR_ON_BAT=ondemand
# Set the min/max frequency available for the scaling governor.
# Possible values strongly depend on your cpu. For available frequencies see
# tlp-stat output, Section "+++ Processor".
# Hint: Parameters are disabled by default, remove the leading # to enable them,
# otherwise kernel default values are used.
#CPU_SCALING_MIN_FREQ_ON_AC=0
#CPU_SCALING_MAX_FREQ_ON_AC=0
#CPU_SCALING_MIN_FREQ_ON_BAT=0
#CPU_SCALING_MAX_FREQ_ON_BAT=0
# Set the cpu "turbo boost" feature: 0=disable / 1=allow
# Requires an Intel Core i processor and kernel 3.7 or later.
# Important:
# - This may conflict with your distribution's governor settings
# - A value of 1 does *not* activate boosting, it just allows it
#CPU_BOOST_ON_AC=1
#CPU_BOOST_ON_BAT=0
# Minimize number of used cpu cores/hyper-threads under light load conditions
SCHED_POWERSAVE_ON_AC=0
SCHED_POWERSAVE_ON_BAT=1
# Kernel NMI Watchdog
# 0=disable (default, saves power) / 1=enable (for kernel debugging only)
NMI_WATCHDOG=0
# Change CPU voltages aka "undervolting" - Kernel with PHC patch required
# Freq:voltage pairs are written to /sys/devices/system/cpu/cpu0/cpufreq/phc_controls
# CAUTION: only use this, if you thoroughly understand what you are doing!
#PHC_CONTROLS="F:V F:V F:V F:V"
# Hard disk devices, separate multiple devices with spaces (default: sda).
# Devices can be specified by disk id too (lookup with: tlp diskid).
DISK_DEVICES="sda sdb"
# Hard disk advanced power management level: 1(max saving)..254(off)
# Levels 1..127 may spin down the disk.
# Separate values for multiple devices with spaces.
DISK_APM_LEVEL_ON_AC="254 254"
DISK_APM_LEVEL_ON_BAT="128 128"
# Hard disk spin down timeout:
# 0: spin down disabled
# 1..240: timeouts from 5s to 20min (in units of 5s)
# 241..251: timeouts from 30min to 5.5 hours (in units of 30min)
# (see 'man hdparm' for details)
#DISK_SPINDOWN_TIMEOUT_ON_AC="0 0"
#DISK_SPINDOWN_TIMEOUT_ON_BAT="0 0"
# Select io scheduler for the disk devices: noop/deadline/cfq (Default: cfq)
# Separate values for multiple devices with spaces.
#DISK_IOSCHED="cfq cfq"
# SATA aggressive link power management (ALPM):
# min_power/medium_power/max_performance
SATA_LINKPWR_ON_AC=max_performance
SATA_LINKPWR_ON_BAT=min_power
# PCI Express Active State Power Management (PCIe ASPM):
# default/performance/powersave
# Hint: needs kernel boot option pcie_aspm=force on some machines
PCIE_ASPM_ON_AC=performance
PCIE_ASPM_ON_BAT=powersave
# Radeon graphics clock speed (profile method): low/mid/high/auto/default
# auto = mid on BAT, high on AC; default = use hardware defaults
# (Kernel >= 2.6.35 only, not with fglrx driver!)
RADEON_POWER_PROFILE_ON_AC=high
RADEON_POWER_PROFILE_ON_BAT=low
# WiFi power saving mode: 1=disable/5=enable
# (Linux 2.6.32 and later, some adapters only!)
WIFI_PWR_ON_AC=1
WIFI_PWR_ON_BAT=5
# Disable wake on lan: Y/N
WOL_DISABLE=Y
# Enable audio power saving for Intel HDA, AC97 devices (timeout in secs).
# A value of 0 disables / >=1 enables power save.
SOUND_POWER_SAVE=1
# Disable controller too (HDA only): Y/N
SOUND_POWER_SAVE_CONTROLLER=Y
# Set to 1 to power off optical drive in UltraBay (ThinkPads only)
# when running on battery. A value of 0 disables this Feature (Default).
# Drive can be powered on again by releasing (and reinserting) the
# eject lever or by pressing the disc eject button on newer models.
# Note: an UltraBay hard disk is never powered off.
BAY_POWEROFF_ON_BAT=0
# Optical drive device to power off (default sr0)
BAY_DEVICE="sr0"
# Runtime Power Management for pci(e) bus devices
# (Kernel >= 2.6.35 only): on=disable/auto=enable
RUNTIME_PM_ON_AC=on
RUNTIME_PM_ON_BAT=auto
# Runtime PM for *all* pci(e) bus devices: 0=disable / 1=enable
# Warning: experimental option, could cause system instabilities
RUNTIME_PM_ALL=0
# Set to 0 to disable/1 to enable usb autosuspend feature
USB_AUTOSUSPEND=1
# Devices from the following list are excluded from usb autosuspend
# (separate with spaces). Use lsusb to get the id's.
# Note: input devices (usbhid) are excluded automatically
#USB_BLACKLIST="1111:2222 3333:4444"
# Set to 1 to disable autosuspend before shutdown/0 to do nothing
# (workaround for usb devices that cause shutdown problems)
#USB_AUTOSUSPEND_DISABLE_ON_SHUTDOWN=1
# Restore radio device state (bluetooth, wifi, wwan) from previous shutdown
# on system startup: 0=disable/1=enable
# Hint: the parameters DEVICES_TO_DISABLE/ENABLE_ON_STARTUP/SHUTDOWN below
# are ignored when this is enabled!
RESTORE_DEVICE_STATE_ON_STARTUP=0
# Radio devices to disable on startup: bluetooth wifi wwan
#DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi wwan"
# Radio devices to enable on startup: bluetooth wifi wwan
#DEVICES_TO_ENABLE_ON_STARTUP="wifi"
# Radio devices to disable on shutdown: bluetooth wifi wwan
# (workaround for devices that are blocking shutdown)
#DEVICES_TO_DISABLE_ON_SHUTDOWN="bluetooth wifi wwan"
# Radio devices to enable on shutdown: bluetooth wifi wwan
# (to prevent other operating systems from missing radios)
#DEVICES_TO_ENABLE_ON_SHUTDOWN="wwan"
# Radio devices to enable when wireless radio switch is turned on:
# bluetooth wifi wwan (Ubuntu + ThinkPad only)
#DEVICES_TO_ENABLE_ON_RADIOSW="wifi wwan"
# Battery charge thresholds (ThinkPad only, tp-smapi or acpi-call kernel module required)
# Charging starts when the remaining capacity falls below the START_CHARGE_TRESH
# value and stops when exceeding the STOP_CHARGE_TRESH value.
# Main battery (values in %)
#START_CHARGE_THRESH_BAT0=75
#STOP_CHARGE_THRESH_BAT0=80
# Ultrabay or slice battery (values in %)
#START_CHARGE_THRESH_BAT1=75
#STOP_CHARGE_THRESH_BAT1=80
# Set to 1 to disable use of tpacpi-bat on Sandy Bridge or newer Thinkpads
# and force usage of tp-smapi instead
#DISABLE_TPACPIBAT=1
# tlp-rdw - Parameters for the radio device wizard
# Possible devices: bluetooth/wifi/wwan
# Hint: parameters are disabled by default, remove the leading # to enable them
# Radio devices to disable on connect
DEVICES_TO_DISABLE_ON_LAN_CONNECT="wifi wwan"
DEVICES_TO_DISABLE_ON_WIFI_CONNECT="wwan"
DEVICES_TO_DISABLE_ON_WWAN_CONNECT="wifi"
# Radio devices to enable on disconnect
DEVICES_TO_ENABLE_ON_LAN_DISCONNECT="wifi wwan"
#DEVICES_TO_ENABLE_ON_WIFI_DISCONNECT=""
#DEVICES_TO_ENABLE_ON_WWAN_DISCONNECT=""
# Radio devices to enable/disable when docked
#DEVICES_TO_ENABLE_ON_DOCK=""
#DEVICES_TO_DISABLE_ON_DOCK=""
# Radio devices to enable/disable when undocked
#DEVICES_TO_ENABLE_ON_UNDOCK="wifi"
#DEVICES_TO_DISABLE_ON_UNDOCK=""
thanks guys
I love arch
Last edited by beitme (2013-06-08 10:05:37)

@ Karol, done
@ 65kid, here's my logind.conf
[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#Controllers=
#ResetControllers=cpu
#InhibitDelayMaxSec=5
#HandlePowerKey=poweroff
#HandleSuspendKey=suspend
#HandleHibernateKey=hibernate
#HandleLidSwitch=ignore
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
#IdleAction=ignore
#IdleActionSec=30min

Closing the lid but not sleeping

I dont know whats going on, but now everytime I close the lid and go around with my MBP (I work on the road, so I keep it in my bag closed, when I stop the car, do my work, close the lid, get back to the road and stop again and so on...) it seems that the MBP does not go sleep. It gets really hot and the battery goes flat very quick. Am I doing sth wrong or is a kind of malfunction?
Thanks
Wagner

Same problem here - started about a week ago or so. Someone posted this solution on another forum and it seems to have worked for me - I didn't reset the PRAM however.
Hi all.
Just spent an hour on the phone with an Apple Care guy. Besides being sort of a twit, he suggested reseting the SMC. Here's how:
1) If the computer is on, turn it off.
2) Disconnect the AC Adapter and remove the computer's battery.
3) Press and hold down the power button for 5 seconds and then release the button.
4) Reconnect the battery and AC Adapter.
We also reset the PRAM... the problem seems to be solved (for now). We'll see if it happens again.
Hope it helps.
-GSO
Macbook Pro 2.0 Ghz Mac OS X (10.4.8)
Macbook Pro 2.0 Ghz Mac OS X (10.4.8)

OS X 10.8 Sleep on lid close with external monitor

I have just upgradet to 10.8 Mountaiun Lion and i have noticed a strange bug.
When I have attached my secondary monitor and i close the macbook it doesn't go to sleep.
The laptop monitor is turn off, the main still remains working and no sleep.
How can I sleep my MAC when i close the laptop with attached secondary monitor ?

I have a comment and a question:
Comment: I can connect to my Dell monitor that supports 1920x1080 using either DVI or HDMI and get the full resolutions of 1920x1080 no matter what (at least that is what Mountain Lion reports). Any video I watch seems to be at just fine when viewed at a distance or up close. Granted that the monitor is not 51" like yours, but still...
Question: For my own knowledge, how are you determining that you are seeing the video at a lower resolution? I am curious because I don't notice this, and can't figure out how it could happen unless the source was 720p instead of 1080p. Can you give me some pointers on how to check for this?

T500 Closing Laptop Lid but no External Monitor Output

Similar Messages

Maybe you are looking for