External display incorrect resolution when MBP lid is closed

Hi,
I've just bought a 24" Samsung monitor for use with my 2011 MBP. The optimum resolution for the monitor is 1920 x 1080. I ahave it hooked up through a minidisplay to vga adapter. When I have this resolution selected in extended display mode it works fine, however when I close the lid and run the monitor with the same resolution as the main display, the image gets squashed and the screen flickers, I can also see faint lines in the background and the display is not centred, leaving black gaps on either side of the screen.
The frustrating thing is it was originally running fine before I temporarily changed the resolution in display preferences when in closed lid mode. Is there any kind of fix for this?? I know it's not the monitor's fault because it's displaying the correct resolution when in extended desktop and on other systems.
Any help would be greatly appreciated!
Chris

tjk wrote:
chrisfromuxbridge wrote:
So I've tried everything I can find on the internet relating to resetting display settings on mac osx, including resetting PRAM and SMC, tried deleting com.apple.windowserver.plist from the preferences folder, tried starting in safe mode and reselecting the correct resolution (i.e. switching to something different and then switching back to 1920 x 1080), nothing. What else can I try??
Any bossy third party apps trying to control things?
Run Apple Hardware Test, and/or a trip to the "genius" bar.
No thrid party apps have access to my display prefs as far as I know. And the hardware test did not indicate that anyhting was wrong. I would like to leave the "Genius" bar as a last resort, they weren't much help last time...
Ok so moving the menu bar is allowing me to use the external as native desktop, but this doesn't fix the resolution problem when I close the lid even though the resolution in display prefs is set the same. Is it possible then to tell the mbp not to sleep when I close the lid?? I know you can do this in windows. Please note that I am still using Snow Leopard v10.6.8

Similar Messages

Can i choose the resolution of my external display for when the lid is closed when my lid is open

When I close the lid of my MacBook Pro for an external display apple chooses a resolution that isn't compatible with my display can I choose the resolution when the lid is open in any way of my external display for the mode when the lid is closed?

Hi there, I had a similar problem and was unable to resolve it. I spent about an hour on the phone with a very helpful AppleCare rep who was also completely stuck. It would seem that the only solution is to choose a setting with trial and error while the lid is closed.
My MacBook ended up getting stuck on a closed-lid reoslution that wasn't supported, so I had to do a screen-share with another device to see what the video card was sending to the external display and change it back that way.

How many external displays dose the Retina MBP suport?

How many external displays dose the Retina MBP support? I have herd conflicting information about this, an apple store employee told me that it could support 2 thunderbolt displays while simultaneously running a HDMI connected display (witch would be awesome if true) but I am extremely skeptical, that seems like to much for one GPU.

Graphics and Video support:
Intel HD Graphics 4000
NVIDIA GeForce GT 650M with 1GB of GDDR5 memory and automatic graphics switching
Dual display and video mirroring: Simultaneously supports full native resolution on the built-in display and up to 2560 by 1600 pixels on up to two external displays, at millions of colors
Thunderbolt digital video output
Native Mini DisplayPort output
DVI output using Mini DisplayPort to DVI Adapter (sold separately)
VGA output using Mini DisplayPort to VGA Adapter (sold separately)
Dual-link DVI output using Mini DisplayPort to Dual-Link DVI Adapter (sold separately)

How do I put an external display to sleep when I am using my MacBook Air for presentation?

How do I put an external display to sleep when I am using my MacBook Air for presentation? I do not want to go to the projector just to turn it off and turn on again after a while? Is there a keyboard shortcut for that?

I want to be able to sleep the external display and at the same time do things in the MacBook.( This feature is useful for me so that I can prepare some things and so that my audience will not see what I am about to show them.)
Is there a feature for Mountain Lion?

After 10.8.2 update i can no longer wake my macbook from standby with keyboard when the lid is closed

I just updated to 10.8.2 and now i can no longer wake my macbook froom standby when the lid is closed, it directly goes back to sleep
steps to reproduce:
1. attach secondary monitor and keyboard
2. close lid
3. wait 5 seconds for going to standby
4. press any key on keyboard and type in user-credentials (notice how the 2nd monitor becomes the mainscreen)
5. wait 5 seconds
6. standby again
side note:
i also have sudo nvram boot-args="iog=0x0" enabled, because i like to not use the integrated screen when its attached to a secondary screen, but since it goes back to standby right after login this is pretty much pointless

Same here, I think changed something in 10.8.2 that wrecked the "Open-MBP Clamshell Mode." sigh

Powerbook does not sleep when the lid is closed

my tibook does not go to sleep when i close the lid. the screen stays on when the lid is closed. the screen was replaced a few months ago. i have to hit the power button and choose sleep or choose sleep from the menu. does anyone know how to fix this. Thanks.

Hi, fatchance. You have a hardware issue. The reed switch that puts the PB to sleep when it is closed is a two-part device. The latch mechanism in the main body of the Powerbook contains a magnet (which you can detect by moving a paper clip over it), and the switch itself is located inside the small latch opening in the display bezel. When the display is closed, the magnet is supposed to actuate the switch, putting the PB to sleep. If that isn't happening on your PB, the switch is broken or its wiring is damaged. Either way, the remedy will be to replace the entire display assembly. It's made not to be disassembled. Most technicians won't do so, because of the great likelihood of damaging the display housing/bezel or the display itself while prying it apart (it's epoxied together). Since the display is the PB's most costly part, replacing it merely to fix your reed switch would be a poor bargain, and I can't recommend it. Just put the PB to sleep manually or set a suitable sleep delay in the Energy Saver control pane instead.

[SOLVED]Gnome 3.4 is not suspending when the lid is closed.

Hey..
Since upgrading to gnome 3.4.1, my laptop does not suspend when the lid is closed.
I have read this this thread without getting a clear answer...
I have checked the setting in gnome tweak tool, and they are both set to "Suspend"
The laptop has no problem suspending, if i run the command, or choose the option in the menu to the right.
Is this a bug ?
What can i do to fix it. ?
Last edited by Munken (2012-06-20 05:54:08)

See this thread for updates on the problem.

How to run something when laptop lid is closed?

Hi,
I'm running Arch on my EEEpc 1000h. I'd like to run certain commands when I close the lid. Can this be done?
Thanks in advance.

Check the aur for acpi-eee and acpi-eeepc-generic. Install one of them and configure it to do a specific task when the lid is closed.

My macbook pro shuts down OSX and all my programs when the lid is closed

Hi,
I am having a problem. My macbook pro shuts down OSX and all my programs when the lid is closed. I close the lid, and then I hear the shutdown music and then when I open it again it automatically restarts OSX and all my windows and programs are closed, any info gone.
This doesn't happen all the time. Just once a day or maybe twice a day. It seems like it happens basically when I have my computer just the way I want it, to keep an eye on things for the day.
I just recently switched to a mac and while somewhat savvy, I am not a programmer or techie, but it seems to me that when I shut the lid, it should do the same thing every time.
I have a intel core 2 duo 17 inch macbook pro with 2.33 processr and 2 gig ram, if that helps.
I am in alaska and there is no genius bar here and I am hoping to figure this out before I begin bugging our local independant mac store about this.
Thanks in advance,
Lylah
17 inch Macbook Pro Mac OS X (10.4.9) intel core 2 duo 2.33g. 2 gig ram

Ahhh, enlightenment!
That would make sense. What I usually do, after closing the lid, is to wait for the apple to turn off and then set it down on it's side leaning it against the side table. I will try to wait for it to indicate that it is fully asleep before I move it next time. Personally, I prefer my computer to NOT fall asleep at all, but I am told it is not an option. Apparently this function is hardware related accoring to my local mac shop. They tracked it down for me because I hated this feature when I first bought my computer and was trying some way around it.
The shutdown music I was refering to was that music the mac makes when shutting down, which doesnt usually occur when it goes to sleep, unless it is malfunctioning like this.
What does resetting the pmu do? (what is a pmu as well?)
Thank you very much.
Lylah

System always auto-suspends when the lid is closed

Hello,
I am trying to prevent my laptop (a System76 Lemur Ultra 3) from suspending when the lid is closed. No matter what I change in the configuration, the laptop always suspends when the lid is closed. The output of journalctl is as follows after this happens:
Feb 21 04:35:32 hostname systemd-logind[196]: Lid closed.
Feb 21 04:35:32 hostname systemd-logind[196]: Suspending...
Feb 21 04:35:32 hostname systemd[1]: Starting Sleep.
Feb 21 04:35:32 hostname systemd[1]: Reached target Sleep.
Feb 21 04:35:32 hostname systemd[1]: Starting Suspend...
Feb 21 04:35:33 hostname systemd-sleep[2001]: Suspending system...
Feb 21 04:35:33 hostname kernel: PM: Syncing filesystems ... done.
Feb 21 04:35:33 hostname kernel: PM: Preparing system for mem sleep
Feb 21 04:35:43 hostname kernel: Freezing user space processes ... (elapsed 0.06 seconds) done.
Feb 21 04:35:43 hostname kernel: Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
Feb 21 04:35:43 hostname systemd[1]: Time has been changed
Feb 21 04:35:43 hostname systemd[1]: systemd-tmpfiles-clean.timer: time change, recalculating next elapse.
Feb 21 04:35:43 hostname systemd-logind[196]: Lid opened.
Feb 21 04:35:43 hostname acpid[190]: client 1812[0:100] has disconnected
Feb 21 04:35:43 hostname kernel: PM: Entering mem sleep
Feb 21 04:35:43 hostname kernel: Suspending console(s) (use no_console_suspend to debug)
Feb 21 04:35:43 hostname kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Feb 21 04:35:43 hostname kernel: sd 0:0:0:0: [sda] Stopping disk
Feb 21 04:35:43 hostname kernel: PM: suspend of devices complete after 1092.547 msecs
Feb 21 04:35:43 hostname kernel: PM: late suspend of devices complete after 0.556 msecs
Feb 21 04:35:43 hostname kernel: jme 0000:03:00.0: wake-up capability enabled by ACPI
Feb 21 04:35:43 hostname kernel: ehci_hcd 0000:00:1d.0: wake-up capability enabled by ACPI
Feb 21 04:35:43 hostname kernel: ehci_hcd 0000:00:1a.0: wake-up capability enabled by ACPI
Feb 21 04:35:43 hostname kernel: PM: noirq suspend of devices complete after 66.095 msecs
Feb 21 04:35:43 hostname kernel: ACPI: Preparing to enter system sleep state S3
Feb 21 04:35:43 hostname kernel: PM: Saving platform NVS memory
Feb 21 04:35:43 hostname kernel: Disabling non-boot CPUs ...
Feb 21 04:35:43 hostname kernel: smpboot: CPU 1 is now offline
Feb 21 04:35:43 hostname kernel: smpboot: CPU 2 is now offline
Feb 21 04:35:43 hostname kernel: smpboot: CPU 3 is now offline
Feb 21 04:35:43 hostname kernel: smpboot: CPU 4 is now offline
Feb 21 04:35:43 hostname kernel: smpboot: CPU 5 is now offline
Feb 21 04:35:43 hostname kernel: smpboot: CPU 6 is now offline
Feb 21 04:35:43 hostname kernel: smpboot: CPU 7 is now offline
Feb 21 04:35:43 hostname kernel: Extended CMOS year: 2000
Feb 21 04:35:43 hostname kernel: ACPI: Low-level resume complete
Feb 21 04:35:43 hostname kernel: PM: Restoring platform NVS memory
Feb 21 04:35:43 hostname kernel: Extended CMOS year: 2000
Feb 21 04:35:43 hostname kernel: Enabling non-boot CPUs ...
Feb 21 04:35:43 hostname systemd-sleep[2001]: System resumed.
Feb 21 04:35:43 hostname kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Feb 21 04:35:43 hostname kernel: CPU1 is up
Feb 21 04:35:43 hostname kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Feb 21 04:35:43 hostname kernel: CPU2 is up
Feb 21 04:35:43 hostname kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Feb 21 04:35:43 hostname kernel: CPU3 is up
Feb 21 04:35:43 hostname kernel: smpboot: Booting Node 0 Processor 4 APIC 0x1
Feb 21 04:35:43 hostname kernel: CPU4 is up
Feb 21 04:35:43 hostname kernel: smpboot: Booting Node 0 Processor 5 APIC 0x3
Feb 21 04:35:43 hostname kernel: CPU5 is up
Feb 21 04:35:43 hostname kernel: smpboot: Booting Node 0 Processor 6 APIC 0x5
Feb 21 04:35:43 hostname kernel: CPU6 is up
Feb 21 04:35:43 hostname kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7
Feb 21 04:35:43 hostname kernel: CPU7 is up
Feb 21 04:35:43 hostname kernel: ACPI: Waking up from system sleep state S3
Feb 21 04:35:43 hostname kernel: ehci_hcd 0000:00:1a.0: wake-up capability disabled by ACPI
Feb 21 04:35:43 hostname kernel: ehci_hcd 0000:00:1d.0: wake-up capability disabled by ACPI
Feb 21 04:35:43 hostname kernel: PM: noirq resume of devices complete after 133.251 msecs
Feb 21 04:35:43 hostname kernel: PM: early resume of devices complete after 0.425 msecs
The first thing I did was to disable systemd's acpi features by setting /etc/systemd/logind.conf as follows:
# This file is part of systemd.
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
# See logind.conf(5) for details
[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#Controllers=
#ResetControllers=cpu
#InhibitDelayMaxSec=5
HandlePowerKey=ignore
HandleSuspendKey=ignore
HandleHibernateKey=ignore
HandleLidSwitch=ignore
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
IdleAction=suspend
IdleActionSec=45min
However, the behavior was the same as before. I also tried setting
LidSwitchIgnoreInhibited=no
but after reading man 5 logind.conf it seems that this is unnecessary (and it had no effect when I tried it).
acpid is also installed but I have commented out the contents of /etc/acpi/handler.sh as well as all the scripts in /etc/acpi/actions. I noticed that there is also a UPower daemon which was installed as a dependency and thought that it might be triggering the suspend. I tried setting
IgnoreLid=true
in /etc/UPower/UPower.conf but this also had no effect.
systemctl list-units has the following output:
UNIT LOAD ACTIVE SUB DESCRIPTION
proc-sys-fs-binfmt_misc.automount loaded active waiting Arbitrary Executable File Formats File System Automount Point
sys-devices-pci0000:00-0000:00:1b.0-sound-card0.device loaded active plugged /sys/devices/pci0000:00/0000:00:1b.0/sound/card0
sys-devices-pci0000:00-0000:00:1c.2-0000:02:00.0-net-wlan0.device loaded active plugged /sys/devices/pci0000:00/0000:00:1c.2/0000:02:00.0/net/wlan0
sys-devices-pci0000:00-0000:00:1c.3-0000:03:00.0-net-eth0.device loaded active plugged /sys/devices/pci0000:00/0000:00:1c.3/0000:03:00.0/net/eth0
sys-devices-pci0000:00-0000:00:1d.0-usb2-2\x2d1-2\x2d1.2-2\x2d1.2.1-2\x2d1.2.1.1-2\x2d1.2.1.1.1-2\x2d1.2.1.1.1:1.2-sound-card1.device loaded active plugged 0819
sys-devices-pci0000:00-0000:00:1d.0-usb2-2\x2d1-2\x2d1.2-2\x2d1.2.1-2\x2d1.2.1.3.device loaded active plugged Deskjet_5400_series
sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda1.device loaded active plugged ST9500420AS
sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda2.device loaded active plugged ST9500420AS
sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda.device loaded active plugged ST9500420AS
sys-devices-pci0000:00-0000:00:1f.2-ata3-host2-target2:0:0-2:0:0:0-block-sr0.device loaded active plugged TSSTcorp_CDDVDW_SN-208AB
sys-devices-platform-serial8250-tty-ttyS0.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS0
sys-devices-platform-serial8250-tty-ttyS1.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS1
sys-devices-platform-serial8250-tty-ttyS2.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS2
sys-devices-platform-serial8250-tty-ttyS3.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS3
sys-module-configfs.device loaded active plugged /sys/module/configfs
sys-subsystem-net-devices-eth0.device loaded active plugged /sys/subsystem/net/devices/eth0
sys-subsystem-net-devices-wlan0.device loaded active plugged /sys/subsystem/net/devices/wlan0
-.mount loaded active mounted /
dev-hugepages.mount loaded active mounted Huge Pages File System
dev-mqueue.mount loaded active mounted POSIX Message Queue File System
media-usbhd\x2dsda1.mount loaded active mounted /media/usbhd-sda1
sys-kernel-config.mount loaded active mounted Configuration File System
sys-kernel-debug.mount loaded active mounted Debug File System
tmp.mount loaded active mounted Temporary Directory
cups.path loaded active waiting CUPS Printer Service Spool
systemd-ask-password-console.path loaded active waiting Dispatch Password Requests to Console Directory Watch
systemd-ask-password-wall.path loaded active waiting Forward Password Requests to Wall Directory Watch
acpid.service loaded active running ACPI event daemon
atd.service loaded active running ATD daemon
cronie.service loaded active running Periodic Command Scheduler
cups.service loaded active running CUPS Printing Service
dbus.service loaded active running D-Bus System Message Bus
[email protected] loaded active running Getty on tty1
laptop-mode.service loaded active exited Laptop Mode Tools
polkit.service loaded active running Authorization Manager
postfix.service loaded active running Postfix Mail Transport Agent
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-modules-load.service loaded active exited Load Kernel Modules
systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-tmpfiles-setup.service loaded active exited Recreate Volatile Files and Directories
systemd-udev-trigger.service loaded active exited udev Coldplug all Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-user-sessions.service loaded active exited Permit User Sessions
systemd-vconsole-setup.service loaded active exited Setup Virtual Console
upower.service loaded active running Daemon for power management
wicd.service loaded active running Wicd a wireless and wired network manager for Linux
acpid.socket loaded active listening ACPID Listen Socket
cups.socket loaded active running CUPS Printing Service Sockets
dbus.socket loaded active running D-Bus System Message Bus Socket
dmeventd.socket loaded active listening Device-mapper event daemon FIFOs
lvmetad.socket loaded active listening LVM2 metadata daemon socket
systemd-initctl.socket loaded active listening /dev/initctl Compatibility Named Pipe
systemd-journald.socket loaded active running Journal Socket
systemd-shutdownd.socket loaded active listening Delayed Shutdown Socket
systemd-udevd-control.socket loaded active listening udev Control Socket
systemd-udevd-kernel.socket loaded active running udev Kernel Socket
basic.target loaded active active Basic System
cryptsetup.target loaded active active Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User
network.target loaded active active Network
printer.target loaded active active Printer
remote-fs.target loaded active active Remote File Systems
sockets.target loaded active active Sockets
sound.target loaded active active Sound Card
suspend.target loaded active active Suspend
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
systemd-tmpfiles-clean.timer loaded active waiting Daily Cleanup of Temporary Directories
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
74 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
Any ideas on what might be causing the system to suspend when the lid is closed would be appreciated.
Thanks
Last edited by Superposition (2013-02-21 15:48:06)

qinohe wrote:You don't have to disable acpi!
Since you made the complete switch to systemd, why not let systemd handle this kind of events?
I was referring to the suggestion of setting acpi=off on the kernel line. systemd can only run a few preset actions on events like lid close (e.g. suspend, poweroff, ignore, etc.). I need to run custom scripts. Also, for some reason I still do not fully understand, it was not working properly. The log in my original post seems to show that it was initiating the suspend.
qinohe wrote:
progandy wrote:Yes, it is easier, but my laptop should react differently depending on the power source. With AC power lid-switch locks the screen, in battery mode it suspends. That is impossible with systemd.
Yes you need something like laptop-mode-tools for that, I know systemd will not do that, for now.
But that is not the issue here!, the issue here is that the llid-switch-button' shouldn't be used at all.
For as far as possible I would still recommend systemd to handle your events!, but it's your decision finally!
You need acpid for that not laptop-mode-tools. This is exactly what apcid is for --- running user scripts on ACPI events.
Anyway, I finally have this fixed though I still have no idea what the problem was. I ran out of ideas on how to fix it and #archlinux didn't know either so I went the painful but sure route. I did full reinstall and reinstalled all programs. logind was still behaving as this point (not ignoring it's logind.conf file as it seemed to be before the reinstall) after this so I concluded that the packages installed were not the problem at least with their default configs. After that, I gradually restored the config files I cared about while testing to see if logind still worked correctly. Contrary, to what I expected it never broke and I was able to restore all modified configs and get correct behavior.
I suspect there was some old out of date config file somewhere that was causing the problem but it's hard to say which one it was. I could probably figure it out with a bit more experimentation but have already spent enough time fixing this...
In case anyone else needs a similar configuration, the relevant files are as follows. This sets up the system to lock whenever systemd executes a suspend action. It also sets up acpid to suspend on lid close.
Make sure you have installed acpid and enabled it to run at startup.
/etc/systemd/logind.conf
# This file is part of systemd.
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
# See logind.conf(5) for details
[Login]
/etc/systemd/logind.conf
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#Controllers=
#ResetControllers=cpu
#InhibitDelayMaxSec=5
HandlePowerKey=ignore
HandleSuspendKey=ignore
HandleHibernateKey=ignore
HandleLidSwitch=ignore
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
#IdleAction=ignore
#IdleActionSec=30min
/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'
/usr/bin/systemctl poweroff
logger "ACPI action undefined: $2"
esac
button/sleep)
case "$2" in
SLPB|SBTN)
logger 'SleepButton pressed'
/usr/bin/systemctl suspend
logger "ACPI action undefined: $2"
esac
ac_adapter)
case "$2" in
AC|ACAD|ADP0)
case "$4" in
00000000)
logger 'AC unpluged'
/usr/sbin/laptop_mode auto
00000001)
logger 'AC pluged'
/usr/sbin/laptop_mode auto
esac
logger "ACPI action undefined: $2"
esac
battery)
case "$2" in
BAT0)
case "$4" in
00000000)
logger 'Battery online'
/usr/sbin/laptop_mode auto
00000001)
logger 'Battery offline'
/usr/sbin/laptop_mode auto
esac
CPU0)
*) logger "ACPI action undefined: $2" ;;
esac
button/lid)
case "$3" in
close)
logger 'LID closed'
/usr/sbin/laptop_mode auto
if [ $(cat /sys/class/power_supply/ADP0/online) -eq 0 ]; then
/usr/bin/systemctl suspend
fi
open)
logger 'LID opened'
/usr/sbin/laptop_mode auto
logger "ACPI action undefined: $3"
esac
logger "ACPI group/action undefined: $1 / $2"
esac
# vim:set ts=4 sw=4 ft=sh et:
Last edited by Superposition (2013-02-23 23:15:54)

T420 - delete key gets pressed when screen/lid is closed

Anyone run into this?
I work at a large company and so far we have recieved a bunch of laptops where the delete key gets pressed if the lid is closed.
I have tried replacing the KB but issue persists.
Upon closer investigation, the DEL key does seem a bit raised when compared to other keys on the KB.

ColonelONeill wrote:
Strange, the DEL key is level for me.
Have you updated your BIOS and drivers? I believe there was a change made where the keyboard will be deactivated when the lid is closed.
Problem: On the listed ThinkPad systems, the delete key might be pressed and activated when the LCD is closed and the system is held tightly when carried..
Affected Systems: ThinkPad T420, T420i, T420s, T520, W520, X220, X220t.
Solution: Please update the BIOS to the version listed below, or newer. The BIOS can be downloaded from:
T420/T420 (ver. 1.33): http://support.lenovo.com/en_US/downloads/detail.page?LegacyDocID=MIGR-77071 .
T420s/T420si (ver. 1.29): http://support.lenovo.com/en_US/downloads/detail.page?LegacyDocID=MIGR-77010
T520/T520i (ver. 1.32): http://support.lenovo.com/en_US/downloads/detail.page?LegacyDocID=MIGR-77001
W520 (ver. 1.30): http://support.lenovo.com/en_US/downloads/detail.page?LegacyDocID=MIGR-77033
X220/X220i/X220T (ver. 1.22) http://support.lenovo.com/en_US/downloads/detail.page?LegacyDocID=MIGR-77150:
As noted previsouly in another post, if the wireless antenna wires are not routed neatly underneath, the keyboard will stick up just enough for the screen to press on those keys.

T540p will not go to sleep when the lid is closed

I recently got a T540p and all settings in Windows 8.1 are set to "sleep" when either the power button or lid is closed. Neither of these work, the screen stays on when the lid is closed. If I let the computer idle long enough, the computer will enter sleep. I've used Lenovo System Update to get the latest drivers and there is nothing outstanding. Could someone please advise if there is anything else to check?

Hi Adamstirtan,
Welcome to Lenovo Community!
As per the query we understood that you are facing issue with system not going to sleep mode on your ThinkPad T500.
Go to Control Panel\All Control Panel Items\Power Options\Choose what closing the lid dose – When close the lid – On battery sleep – Plugged in sleep.
To prevent programs from waking your computer:
Open Power Options by clicking the Start button Picture of the Start button, clicking Control Panel, clicking System and Security, and then clicking Power Options.
On the Select a power plan page, click Change plan settings for the plan that you want to change.
On the Change settings for the plan page, click Change advanced power settings.
On the Advanced settings tab, expand Sleep, expand Allow wake timers, choose Disable for both when your computer is running on battery and when it's plugged in, and then click OK.
Hope this helps.
Best regards,
Hemanth Kumar

External display - maximum resolution only works in safe mode on MBP

I'm having an issue with an external display connected to a 2012 non-retina MacbookPro 15" i7 running 10.9. Monitor is Dell U2713HM, which has a maximum resolution of 2560x1440, and is connected via a Mini-Dipslayport to Displayport cord.
My setup has been working great for over a year, where while at my office I use the macbook closed in "clamshell mode" with the Dell monitor being the only display in use, running at 2560x1440. However today when I came into my office and connected to the dispay as usual, the resolution on the Dell was noticably scaled. System preferences is showing it running Scaled at 1080p, and when I select Best for Display it stretches to a very wide and distorted resolution. I can hold alt and click the Scaled button to display additional resolutions, however the maximum resolution listed is 1600x1200. Same problem regardless of clamshell, mirror, or extended desktop modes.
I've been trying to track down the problem, and have run though the usual procedures: restart, shutdown, reset PRAM, reset SMC, check cord connections, verify disk, repair disk permissions - all to no avail. However when I boot in safe mode the display runs as it should at 2560x1440 without issue, which lets me know its not a problem with the cord or connectioin, but rather something on the OS / GPU side.
I can't for the life of me figure out what is causing the issue. Considering its been working fine for quite some time, and I've made no unusual changes to the MBP in the past 48 hours when the display was working properly, I'm not really sure where to go from here. Hoping to not have to migrate to a new user or repartion my HDD.
Any suggestions on possible solutions?
Thanks.

I stumbled upon a fix. Still not sure what caused the issue in the first place, but for anyone having the same issue, the display override script contained on the site below seems to have fixed the issue.
http://embdev.net/topic/284710

MBP still thinks external display is connected when it's not

I have my MBP connected via DVI to an external LCD (HP w2007). Whenever I disconnect the DVI plug from my MBP, my MBP thinks the external monitor is still connected. I can go to Sysprefs > Displays > Gather Windows and it'll clearly have the HP's display pref window showing up.
This is a huge issue since any programs that were previously shown on the external display continue to think the display is still there and then I can't access them.

Had posted here because I figured the hold time for Apple support would be long because of Leopard's release. Hold times were not too bad. Problem is solved by resetting PRAM.

Unable to use external display native resolution

Dear all,
Here is the current setup I'm using :
MacbookPro 15", hi res, Mid 2010 with Mac OS 10.6.6, software up-to-date
Apple MiniDisplayPort to VGA Adapter Firmware 1.03
IIYAMA Prolite E2607WSD, a 26" monitor with native resolution of 1920x1200 @ 60Hz
When connecting the MiniDisplayPort to VGA adapter to the VGA cable, the MBP doesn't enable me to set the external native monitor resolution of 1920x1200 with extended desktop. The maximum available resolution the macbookpro is able to diaply is 1920x1080.
What I tried :
-using high performance graphics in the energy saver settings
-using clamshell mode
-using mirroring mode
-reset PRAM
-reset SCM
-delete com.windowserver.plist
-use SwitchResX.app and DisplayConfigX.app to force the native resolution
To make sure that the monitor was correctly behaving, I tried with a PC with WinXP, and I was able to get max resolution of 1920x1200 without an issue. I also tried with a Macbook 2008 with 10.5.6, and with it's own DisplayPort to VGA adapter (the "normal size" one, not the "mini" one I'm using with the MBP), and it worked as well with the native resolution of 1920x1200.
I 'm coming to the conclusion that either the minidisplayport to vga adapter doesn't accept any resolution higher than 1920x1080 or that the one I bought from Apple is not properly working, or that I should use the minidisplay port to DVI adapter (no HDMI here as an input for the monitor)...
I also browsed the forum and found a lot of similar issues, so I guess it's pretty common, but no workaround seems possible.
Does anybody in the community had the same issue and know how to solve it ?
Thanks in advance.
PolCls

Hello BSteely,
I actually tried to get the EDID information and to replicate them as much as possible but everytime I tried a custom resolution, after reboot, SRX will say " the system didn't accept this setup"... and the proper resolution is not available..
See below the data :
DDC block report generated by SwitchResX version 4.2 for display
PLE2607WSD
------------------- RAW DATA ------------------------
0 1 2 3 4 5 6 7 8 9 A B C D E F
0 | 00 FF FF FF FF FF FF 00 26 CD 03 66 21 02 00 00
1 | 0C 14 01 03 68 37 22 78 2A 7B 65 A5 55 48 99 26
2 | 12 50 54 BD EF 80 71 4F 81 80 81 8F 95 00 95 0F
3 | A9 40 B3 00 D1 C0 7D 4B 80 A0 72 B0 2D 40 88 C8
4 | 36 00 26 58 21 00 00 1C 00 00 00 FF 00 31 31 30
5 | 35 36 30 31 32 30 30 35 34 35 00 00 00 FD 00 37
6 | 4C 1D 51 14 00 0A 20 20 20 20 20 20 00 00 00 FC
7 | 00 50 4C 45 32 36 30 37 57 53 44 0A 20 20 00 11
< 00FFFFFF FFFFFF00 26CD0366 21020000 0C140103 68372278 2A7B65A5 55489926 125054BD EF80714F 8180818F 9500950F A940B300 D1C07D4B 80A072B0 2D4088C8 36002658 2100001C 000000FF 00313130 35363031 32303035 34350000 00FD0037 4C1D5114 000A2020 20202020 000000FC 00504C45 32363037 5753440A 20200011 >
{ 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0x26, 0xCD, 0x03, 0x66, 0x21, 0x02, 0x00, 0x00, 0x0C, 0x14, 0x01, 0x03, 0x68, 0x37, 0x22, 0x78, 0x2A, 0x7B, 0x65, 0xA5, 0x55, 0x48, 0x99, 0x26, 0x12, 0x50, 0x54, 0xBD, 0xEF, 0x80, 0x71, 0x4F, 0x81, 0x80, 0x81, 0x8F, 0x95, 0x00, 0x95, 0x0F, 0xA9, 0x40, 0xB3, 0x00, 0xD1, 0xC0, 0x7D, 0x4B, 0x80, 0xA0, 0x72, 0xB0, 0x2D, 0x40, 0x88, 0xC8, 0x36, 0x00, 0x26, 0x58, 0x21, 0x00, 0x00, 0x1C, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x31, 0x31, 0x30, 0x35, 0x36, 0x30, 0x31, 0x32, 0x30, 0x30, 0x35, 0x34, 0x35, 0x00, 0x00, 0x00, 0xFD, 0x00, 0x37, 0x4C, 0x1D, 0x51, 0x14, 0x00, 0x0A, 0x20, 0x20, 0x20, 0x20, 0x20, 0x20, 0x00, 0x00, 0x00, 0xFC, 0x00, 0x50, 0x4C, 0x45, 0x32, 0x36, 0x30, 0x37, 0x57, 0x53, 0x44, 0x0A, 0x20, 0x20, 0x00, 0x11, }
Valid EDID block: checksum passed
------------------- MAIN EDID BLOCK -----------------
EDID Version........1.3
Manufacturer........IVM
Product Code........870 (0366) (6603)
Serial Number.......00000221
Manufactured........Week 12 of year 2010
Max H Size..........55 cm
Max V Size..........34 cm
Gamma...............2,20
Display Supported Features:
Power Management: Active off
Display type:
RGB color display
Display is non continuous frequency
Default color space is not sRGB standard
Preferred timing mode includes Native Pixel Format
Input signal & sync:
Analog input with: 0.700V / 0.000V
Composite Sync
Color info:
Red x = 0,646 Green x = 0,283 Blue x = 0,149 White x = 0,313
Red y = 0,335 Green y = 0,601 Blue y = 0,072 White y = 0,329
Established Timings:
720 x 400 @ 70Hz
640 x 480 @ 60Hz
640 x 480 @ 67Hz
640 x 480 @ 72Hz
640 x 480 @ 75Hz
800 x 600 @ 60Hz
800 x 600 @ 72Hz
800 x 600 @ 75Hz
832 x 624 @ 75Hz
1024 x 768 @ 60Hz
1024 x 768 @ 70Hz
1024 x 768 @ 75Hz
1280 x 1024 @ 75Hz
Manufacturer Reserved Timings:
1152 x 870 @ 75Hz
Standard Timing Identification:
#0: 1152 x 864 @ 75Hz (714F)
#1: 1280 x 1024 @ 60Hz (8180)
#2: 1280 x 1024 @ 75Hz (818F)
#3: 1440 x 900 @ 60Hz (9500)
#4: 1440 x 900 @ 75Hz (950F)
#5: 1600 x 1200 @ 60Hz (A940)
#6: 1680 x 1050 @ 60Hz (B300)
#7: 1920 x 1080 @ 60Hz (D1C0)
Monitor Description blocks:
Descriptor #0 - Timing definition:
Mode = 1920 x 1200 @ 59,885Hz
Pixel Clock............. 193,25 MHz Non-Interlaced
Horizontal Vertical
Active.................. 1920 pixels 1200 lines
Front Porch............. 136 pixels 3 lines
Sync Width.............. 200 pixels 6 lines
Back Porch.............. 336 pixels 36 lines
Blanking................ 672 pixels 45 lines
Total................... 2592 pixels 1245 lines
Scan Rate............... 74,556 kHz 59,885 Hz
Image Size.............. 550 mm 344 mm
Border.................. 0 pixels 0 lines
Sync: Digital separate with
* Positive vertical polarity
* Negative horizontal polarity
Descriptor #1 - Serial number:
1105601200545
Descriptor #2 - Monitor limits:
Horizontal frequency range.......29-81 kHz
Vertical frequency range.........55-76 Hz
Maximum bandwidth unspecified
Descriptor #3 - Monitor name:
PLE2607WSD
What do you think are the parameters I should use ?
Thanks in advance;
Paul

External display incorrect resolution when MBP lid is closed

Similar Messages

Maybe you are looking for