Screen displaying "Negative of usual colors"

kids were playing on iMac and now the screen displays a negative of usual color palette? Any ideas what is causing this?

factor14,
Welcome to Apple Discussions.
System Preferences...>Universal Access>Seeing>Display (Reset Black on White/Use grayscale/Enhance contrast as necessary)
;~)

Similar Messages

My screen displayed flickering of various colors in line.

I have a macbook air 11" almost a year with it now...and it has given me jst a
couple of problems. First was my screen displaying flickering lines of various colors so I didn't
know what to do..so I jst keep pressing certain buttons to stop it, I had to use the power button..and it
didn't work..until a couple of seconds later it shut down. Next was my sound system. There was this
weird sound of some kind of banging sound..like hitting something. I had to shut down my laptop.
I'm not liking this anymore. I don't know if I should return the product before the year is complete.

Return it as meaning getting a service call, yes.
Contact Apple for appt. for in shop diagnostic and likely repair.
vertical or horizontal lines? Do the lines move when you move the monitor?
either damaged LCD feed lines or fault of same at connection with logic board or possible defect at logic with GPU

Screen displaying negative image

My 3 year old was hitting buttons on my laptop, I walked over to remove him and my screen is a complete negative image of what is being displayed. I am sure it was just a combination of buttons hit but I have no idea how to revert it. Anyone??? Anyone???? Tried looking under system preferences but nothing... have no idea how to fix.

I did a little searching. for anyone else who encounters the problem hit Control, Option, Command, then 8. it will switch it back to normal.

How to display the screen in negative?

Hi,
Is it possible to easily toggle the display of the screen in negative?
Someone showed to me that with a Mac he can do that with one shortcut and now I’m jealous, I want the same on my Arch
My graphics card is a Nvidia (proprietary driver) and I use LXDE with OpenBox, but I don’t really know at which level I have to search.
Thank you

You might be able to do this with one of the fancier windows managers (compiz perhaps).
http://www.google.com/search?hl=en&rls= … =&aql=&oq=

The display screen is negative.

The display screen is negative. How can I reset the display positive?

Settings>General>Accessibility>White on Black>Off

How to display negative values in a screen field of a screen

Hi All,
Please let me know how to display negative values in a screen field of a screen.
thanks

Hi Kishore,
You can do this method. In the screen , create a text field of CHAR instead fo creating an INT4 field.
I have created a field of CHAR of name say TEXT.
In the main program,
declare a variable of the same name ie. TEXT.
data: TEXT(5) TYPE C.
In PBO, just assign the negative values.
It will work.Since there is automatic conversion between character and integer data types, it will work for positive values as well.
Regards,
Sylendra.

The screen of my MacBook Pro itself periodically switches the color. That is, with the usual colors, on some blue. What to do? Should be repaired, or you can figure out the most? HELP ME PLEASE!

The screen of my laptop itself periodically switches the color. That is, with the usual colors, on some blue. What to do? Should be repaired, or you can figure out the most? HELP ME PLEASE!

LambChops1,
I’m using Mavericks, and it’s still possible to select text to drag and for cutting and pasting. Left-clicking and right-clicking is still possible, too.
Try opening the Trackpad pane of System Preferences, and select the Point & Click tab. To right-click, ensure that your “Secondary click” checkbox has been checked; the small print under “Secondary click” is a dropdown menu which allows you to select the form of right-clicking that you prefer. (For instance, mine is set to “Click in bottom right corner”.) For left-clicking, is your “Tap to click” checkbox checked, or unchecked? (Mine is unchecked, since I prefer pushing for left-clicking over tapping to do so.)

Screen displaying inverted colors

Ever since I updated to 1.0.2, the iPod Nano refuses to display my stuff correctly. Sometimes, it will display everything in inverted colors, with a little sliver on the left being correctly colored.
Then, it will switch back to normal, and flash a white bar on the right side of the screen. It will stay like this until the screen cuts off, then it will go back to the inverted colors.
I don't know what this is, but if it's from the update, they'd better release a new one soon. I'm tired of having my iPod glitchy.

Have you tried resetting the iPod?
Make sure the hold switch is not locked first (i.e. you can operate the iPod buttons)
The press and hold the Menu and Centre Button down at the same time, keep them both pressed until the Apple Logo appears on the screen, then release.
Ian

Negative screen display?

My 3 year old found a way to change my screen display so that it appears as a negative image. How do I correct this? Command + Shift + 8 didn't work.

Open the Universal Access pane of System Preferences, click on the Seeing tab, turn off White on Black, and drag the Contrast slider all the way to the left.
(69577)

Screen display looks fuzzy using xf86-video-intel on a HP Pavilion 23

Hello,
First off I want to say, thank you for Arch! Been using some distros on and off and I think I found my /home! I made a full plunge into Linux a bit ago after some Windows 8.1 issues, switched to Arch and not looking back. Anyways, So far all my computers are either Arch or Manjaro which I am moving more towards straight arch as Manjaro does have some issues when updating your system (dependency loops). All and all not bad, just liking the full control of a pure system then building from scratch.
Ok, the issue at hand. I have removed Windows 8.1 from my HP All in One Pavilion 23 machine....what a nightmare that was.... Everything was good after turning off secure boot. I installed Arch Linux (3.14.4-1) x86_64, and I am having issues getting the xf86-video-intel driver to play nice with X.
I have taken a screenshot:
Screenshot
I notice this starts right after the choosing the Arch Linux from the boot option menu. It starts the load nice and crisp but after a second the screen flickers with some lines at the top of the screen, random colors, only about the top 3rd of the screen. This modules begin to load but the terminal text looks blocky and horrible.
I am using Openbox 3.5.2-6 with slim 1.3.6-4. Running xorg-server 1.15.1-1 and xorg-server-utils 7.6-3 with all the dependencies of course.
Output from pacman queries for video drivers
xf86-video-intel 2.99.911-2
xf86-video-vesa 2.3.2-4
lspci output
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5)
00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d5)
00:1c.5 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #6 (rev d5)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation H87 Express LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01)
04:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)
my /etc/mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES="i915"
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect block filesystems"
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS="base udev block filesystems"
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev block mdadm encrypt filesystems"
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev block lvm2 filesystems"
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block filesystems keyboard fsck"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
,my /etc/default/grub.conf
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable Hidden Menu, and optionally hide the timeout count
#GRUB_HIDDEN_TIMEOUT=5
#GRUB_HIDDEN_TIMEOUT_QUIET=true
# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
#GRUB_THEME="/path/to/gfxtheme"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
#GRUB_SAVEDEFAULT="true"
And last my /var/log/Xorg.0.log
[ 15.641]
X.Org X Server 1.15.1
Release Date: 2014-04-13
[ 15.641] X Protocol Version 11, Revision 0
[ 15.641] Build Operating System: Linux 3.14.0-4-ARCH x86_64
[ 15.641] Current Operating System: Linux localhost 3.14.4-1-ARCH #1 SMP PREEMPT Tue May 13 16:41:39 CEST 2014 x86_64
[ 15.641] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=0c1916a0-b631-478f-ac6b-aa5d123f75cd rw quiet splash
[ 15.641] Build Date: 14 April 2014 08:39:09AM
[ 15.641]
[ 15.641] Current version of pixman: 0.32.4
[ 15.641] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 15.641] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 15.641] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Jun 1 17:05:15 2014
[ 15.687] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 15.687] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 15.739] (==) No Layout section. Using the first Screen section.
[ 15.739] (==) No screen section available. Using defaults.
[ 15.739] (**) |-->Screen "Default Screen Section" (0)
[ 15.739] (**) | |-->Monitor "<default monitor>"
[ 15.764] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 15.764] (**) | |-->Device "Intel Graphics"
[ 15.764] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 15.764] (==) Automatically adding devices
[ 15.764] (==) Automatically enabling devices
[ 15.764] (==) Automatically adding GPU devices
[ 15.793] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 15.793] Entry deleted from font path.
[ 15.795] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 15.795] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 15.795] (**) Extension "Composite" is enabled
[ 15.795] (**) Extension "RENDER" is enabled
[ 15.795] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 15.795] (II) Loader magic: 0x804c80
[ 15.795] (II) Module ABI versions:
[ 15.795] X.Org ANSI C Emulation: 0.4
[ 15.795] X.Org Video Driver: 15.0
[ 15.795] X.Org XInput driver : 20.0
[ 15.796] X.Org Server Extension : 8.0
[ 15.796] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 15.798] (--) PCI:*(0:0:2:0) 8086:0412:103c:2b0f rev 6, Mem @ 0xf7800000/4194304, 0xe0000000/268435456, I/O @ 0x0000f000/64
[ 15.798] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 15.798] Initializing built-in extension Generic Event Extension
[ 15.798] Initializing built-in extension SHAPE
[ 15.798] Initializing built-in extension MIT-SHM
[ 15.798] Initializing built-in extension XInputExtension
[ 15.798] Initializing built-in extension XTEST
[ 15.798] Initializing built-in extension BIG-REQUESTS
[ 15.798] Initializing built-in extension SYNC
[ 15.798] Initializing built-in extension XKEYBOARD
[ 15.798] Initializing built-in extension XC-MISC
[ 15.798] Initializing built-in extension SECURITY
[ 15.798] Initializing built-in extension XINERAMA
[ 15.798] Initializing built-in extension XFIXES
[ 15.798] Initializing built-in extension RENDER
[ 15.799] Initializing built-in extension RANDR
[ 15.799] Initializing built-in extension COMPOSITE
[ 15.799] Initializing built-in extension DAMAGE
[ 15.799] Initializing built-in extension MIT-SCREEN-SAVER
[ 15.799] Initializing built-in extension DOUBLE-BUFFER
[ 15.799] Initializing built-in extension RECORD
[ 15.799] Initializing built-in extension DPMS
[ 15.799] Initializing built-in extension Present
[ 15.799] Initializing built-in extension DRI3
[ 15.799] Initializing built-in extension X-Resource
[ 15.799] Initializing built-in extension XVideo
[ 15.799] Initializing built-in extension XVideo-MotionCompensation
[ 15.799] Initializing built-in extension XFree86-VidModeExtension
[ 15.799] Initializing built-in extension XFree86-DGA
[ 15.799] Initializing built-in extension XFree86-DRI
[ 15.799] Initializing built-in extension DRI2
[ 15.799] (II) "glx" will be loaded by default.
[ 15.799] (II) LoadModule: "dri2"
[ 15.799] (II) Module "dri2" already built-in
[ 15.799] (II) LoadModule: "glamoregl"
[ 15.808] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[ 15.917] (II) Module glamoregl: vendor="X.Org Foundation"
[ 15.917] compiled for 1.15.0, module version = 0.6.0
[ 15.917] ABI class: X.Org ANSI C Emulation, version 0.4
[ 15.917] (II) LoadModule: "glx"
[ 15.917] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 15.928] (II) Module glx: vendor="X.Org Foundation"
[ 15.929] compiled for 1.15.1, module version = 1.0.0
[ 15.929] ABI class: X.Org Server Extension, version 8.0
[ 15.929] (==) AIGLX enabled
[ 15.929] Loading extension GLX
[ 15.929] (II) LoadModule: "intel"
[ 15.929] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 15.955] (II) Module intel: vendor="X.Org Foundation"
[ 15.955] compiled for 1.15.0, module version = 2.99.911
[ 15.955] Module class: X.Org Video Driver
[ 15.955] ABI class: X.Org Video Driver, version 15.0
[ 15.955] (II) intel: Driver for Intel(R) 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
[ 15.956] (II) intel: Driver for Intel(R) HD Graphics: 2000-5000
[ 15.956] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100
[ 15.956] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200
[ 15.956] (++) using VT number 7
[ 15.971] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 4600
[ 15.971] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx, avx2
[ 15.971] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 15.971] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 15.971] (==) intel(0): RGB weight 888
[ 15.971] (==) intel(0): Default visual is TrueColor
[ 15.971] (**) intel(0): Option "AccelMethod" "sna"
[ 15.971] (**) intel(0): Option "DRI" "true"
[ 15.971] (**) intel(0): Option "TearFree" "true"
[ 15.972] (**) intel(0): Framebuffer tiled
[ 15.972] (**) intel(0): Pixmaps tiled
[ 15.972] (**) intel(0): "Tear free" enabled
[ 15.972] (**) intel(0): Forcing per-crtc-pixmaps? no
[ 15.972] (II) intel(0): Output eDP1 has no monitor section
[ 15.972] (--) intel(0): Found backlight control interface acpi_video0 (type 'firmware') for output eDP1
[ 15.972] (II) intel(0): Output VGA1 has no monitor section
[ 15.972] (II) intel(0): Output DP1 has no monitor section
[ 15.972] (II) intel(0): Output HDMI1 has no monitor section
[ 15.972] (II) intel(0): Output DP2 has no monitor section
[ 15.972] (II) intel(0): Output HDMI2 has no monitor section
[ 15.972] (II) intel(0): Output VIRTUAL1 has no monitor section
[ 15.972] (--) intel(0): Output eDP1 using initial mode 1920x1080 on pipe 0
[ 15.972] (==) intel(0): DPI set to (96, 96)
[ 15.972] (II) Loading sub module "dri2"
[ 15.972] (II) LoadModule: "dri2"
[ 15.972] (II) Module "dri2" already built-in
[ 15.972] (==) Depth 24 pixmap format is 32 bpp
[ 15.986] (II) intel(0): SNA initialized with Haswell (gen7.5, gt2) backend
[ 15.986] (==) intel(0): Backing store enabled
[ 15.986] (==) intel(0): Silken mouse enabled
[ 15.986] (II) intel(0): HW Cursor enabled
[ 15.986] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 15.987] (==) intel(0): DPMS enabled
[ 15.987] (II) intel(0): [DRI2] Setup complete
[ 15.987] (II) intel(0): [DRI2] DRI driver: i965
[ 15.987] (II) intel(0): [DRI2] VDPAU driver: i965
[ 15.987] (II) intel(0): direct rendering: DRI2 Enabled
[ 15.987] (==) intel(0): hotplug detection: "enabled"
[ 15.987] (--) RandR disabled
[ 16.067] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 16.067] (II) AIGLX: enabled GLX_ARB_create_context
[ 16.067] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 16.067] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 16.067] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 16.067] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 16.067] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 16.067] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 16.067] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 16.067] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[ 16.067] (II) AIGLX: Loaded and initialized i965
[ 16.067] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 16.085] (II) intel(0): switch to mode [email protected] on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 16.107] (II) intel(0): Setting screen physical size to 508 x 285
[ 16.375] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 16.375] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 16.375] (II) LoadModule: "evdev"
[ 16.383] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 16.402] (II) Module evdev: vendor="X.Org Foundation"
[ 16.402] compiled for 1.15.1, module version = 2.9.0
[ 16.402] Module class: X.Org XInput Driver
[ 16.402] ABI class: X.Org XInput driver, version 20.0
[ 16.402] (II) Using input driver 'evdev' for 'Power Button'
[ 16.402] (**) Power Button: always reports core events
[ 16.402] (**) evdev: Power Button: Device: "/dev/input/event1"
[ 16.402] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 16.402] (--) evdev: Power Button: Found keys
[ 16.402] (II) evdev: Power Button: Configuring as keyboard
[ 16.402] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[ 16.402] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 16.402] (**) Option "xkb_rules" "evdev"
[ 16.402] (**) Option "xkb_model" "pc104"
[ 16.402] (**) Option "xkb_layout" "us"
[ 16.442] (II) config/udev: Adding input device Video Bus (/dev/input/event2)
[ 16.442] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 16.442] (II) Using input driver 'evdev' for 'Video Bus'
[ 16.442] (**) Video Bus: always reports core events
[ 16.442] (**) evdev: Video Bus: Device: "/dev/input/event2"
[ 16.442] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 16.442] (--) evdev: Video Bus: Found keys
[ 16.442] (II) evdev: Video Bus: Configuring as keyboard
[ 16.442] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input2/event2"
[ 16.442] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 16.442] (**) Option "xkb_rules" "evdev"
[ 16.442] (**) Option "xkb_model" "pc104"
[ 16.442] (**) Option "xkb_layout" "us"
[ 16.443] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[ 16.443] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 16.443] (II) Using input driver 'evdev' for 'Power Button'
[ 16.443] (**) Power Button: always reports core events
[ 16.443] (**) evdev: Power Button: Device: "/dev/input/event0"
[ 16.443] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 16.443] (--) evdev: Power Button: Found keys
[ 16.443] (II) evdev: Power Button: Configuring as keyboard
[ 16.443] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0/event0"
[ 16.443] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[ 16.443] (**) Option "xkb_rules" "evdev"
[ 16.443] (**) Option "xkb_model" "pc104"
[ 16.443] (**) Option "xkb_layout" "us"
[ 16.444] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 16.444] (II) config/udev: Adding input device HP High Definition 1MP Webcam (/dev/input/event8)
[ 16.444] (**) HP High Definition 1MP Webcam: Applying InputClass "evdev keyboard catchall"
[ 16.444] (II) Using input driver 'evdev' for 'HP High Definition 1MP Webcam'
[ 16.444] (**) HP High Definition 1MP Webcam: always reports core events
[ 16.444] (**) evdev: HP High Definition 1MP Webcam: Device: "/dev/input/event8"
[ 16.444] (--) evdev: HP High Definition 1MP Webcam: Vendor 0x4f2 Product 0xb40b
[ 16.444] (--) evdev: HP High Definition 1MP Webcam: Found keys
[ 16.444] (II) evdev: HP High Definition 1MP Webcam: Configuring as keyboard
[ 16.444] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input8/event8"
[ 16.444] (II) XINPUT: Adding extended input device "HP High Definition 1MP Webcam" (type: KEYBOARD, id 9)
[ 16.444] (**) Option "xkb_rules" "evdev"
[ 16.444] (**) Option "xkb_model" "pc104"
[ 16.445] (**) Option "xkb_layout" "us"
[ 16.445] (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/event14)
[ 16.445] (**) NextWindow Touchscreen: Applying InputClass "evdev touchscreen catchall"
[ 16.445] (II) Using input driver 'evdev' for 'NextWindow Touchscreen'
[ 16.445] (**) NextWindow Touchscreen: always reports core events
[ 16.445] (**) evdev: NextWindow Touchscreen: Device: "/dev/input/event14"
[ 16.445] (--) evdev: NextWindow Touchscreen: Vendor 0x1926 Product 0x33e
[ 16.445] (--) evdev: NextWindow Touchscreen: Found absolute axes
[ 16.445] (--) evdev: NextWindow Touchscreen: Found absolute multitouch axes
[ 16.445] (II) evdev: NextWindow Touchscreen: No buttons found, faking one.
[ 16.445] (--) evdev: NextWindow Touchscreen: Found x and y absolute axes
[ 16.445] (--) evdev: NextWindow Touchscreen: Found absolute touchscreen
[ 16.445] (II) evdev: NextWindow Touchscreen: Configuring as touchscreen
[ 16.445] (**) evdev: NextWindow Touchscreen: YAxisMapping: buttons 4 and 5
[ 16.445] (**) evdev: NextWindow Touchscreen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 16.446] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/0003:1926:033E.0001/input/input14/event14"
[ 16.446] (II) XINPUT: Adding extended input device "NextWindow Touchscreen" (type: TOUCHSCREEN, id 10)
[ 16.446] (II) evdev: NextWindow Touchscreen: initialized for absolute axes.
[ 16.446] (**) NextWindow Touchscreen: (accel) keeping acceleration scheme 1
[ 16.446] (**) NextWindow Touchscreen: (accel) acceleration profile 0
[ 16.446] (**) NextWindow Touchscreen: (accel) acceleration factor: 2.000
[ 16.446] (**) NextWindow Touchscreen: (accel) acceleration threshold: 4
[ 16.446] (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/mouse2)
[ 16.446] (II) No input driver specified, ignoring this device.
[ 16.446] (II) This device may have been added with another device file.
[ 16.447] (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/event9)
[ 16.447] (II) No input driver specified, ignoring this device.
[ 16.447] (II) This device may have been added with another device file.
[ 16.447] (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/event10)
[ 16.447] (**) NextWindow Touchscreen: Applying InputClass "evdev pointer catchall"
[ 16.447] (II) Using input driver 'evdev' for 'NextWindow Touchscreen'
[ 16.447] (**) NextWindow Touchscreen: always reports core events
[ 16.447] (**) evdev: NextWindow Touchscreen: Device: "/dev/input/event10"
[ 16.447] (--) evdev: NextWindow Touchscreen: Vendor 0x1926 Product 0x33e
[ 16.447] (--) evdev: NextWindow Touchscreen: Found 3 mouse buttons
[ 16.447] (--) evdev: NextWindow Touchscreen: Found absolute axes
[ 16.447] (--) evdev: NextWindow Touchscreen: Found x and y absolute axes
[ 16.447] (--) evdev: NextWindow Touchscreen: Found absolute touchscreen
[ 16.447] (II) evdev: NextWindow Touchscreen: Configuring as touchscreen
[ 16.447] (**) evdev: NextWindow Touchscreen: YAxisMapping: buttons 4 and 5
[ 16.447] (**) evdev: NextWindow Touchscreen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 16.448] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.2/0003:1926:033E.0003/input/input10/event10"
[ 16.448] (II) XINPUT: Adding extended input device "NextWindow Touchscreen" (type: TOUCHSCREEN, id 11)
[ 16.448] (II) evdev: NextWindow Touchscreen: initialized for absolute axes.
[ 16.448] (**) NextWindow Touchscreen: (accel) keeping acceleration scheme 1
[ 16.448] (**) NextWindow Touchscreen: (accel) acceleration profile 0
[ 16.448] (**) NextWindow Touchscreen: (accel) acceleration factor: 2.000
[ 16.448] (**) NextWindow Touchscreen: (accel) acceleration threshold: 4
[ 16.448] (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/js0)
[ 16.448] (II) No input driver specified, ignoring this device.
[ 16.448] (II) This device may have been added with another device file.
[ 16.449] (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/mouse0)
[ 16.449] (II) No input driver specified, ignoring this device.
[ 16.449] (II) This device may have been added with another device file.
[ 16.449] (II) config/udev: Adding input device Hewlett Packard HP Wireless Keyboard Kit (/dev/input/event11)
[ 16.449] (**) Hewlett Packard HP Wireless Keyboard Kit: Applying InputClass "evdev keyboard catchall"
[ 16.449] (II) Using input driver 'evdev' for 'Hewlett Packard HP Wireless Keyboard Kit'
[ 16.449] (**) Hewlett Packard HP Wireless Keyboard Kit: always reports core events
[ 16.449] (**) evdev: Hewlett Packard HP Wireless Keyboard Kit: Device: "/dev/input/event11"
[ 16.449] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Vendor 0x461 Product 0x4e25
[ 16.449] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found keys
[ 16.449] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: Configuring as keyboard
[ 16.449] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.0/0003:0461:4E25.0004/input/input11/event11"
[ 16.449] (II) XINPUT: Adding extended input device "Hewlett Packard HP Wireless Keyboard Kit" (type: KEYBOARD, id 12)
[ 16.449] (**) Option "xkb_rules" "evdev"
[ 16.449] (**) Option "xkb_model" "pc104"
[ 16.449] (**) Option "xkb_layout" "us"
[ 16.450] (II) config/udev: Adding input device Hewlett Packard HP Wireless Keyboard Kit (/dev/input/event12)
[ 16.450] (**) Hewlett Packard HP Wireless Keyboard Kit: Applying InputClass "evdev keyboard catchall"
[ 16.450] (II) Using input driver 'evdev' for 'Hewlett Packard HP Wireless Keyboard Kit'
[ 16.450] (**) Hewlett Packard HP Wireless Keyboard Kit: always reports core events
[ 16.450] (**) evdev: Hewlett Packard HP Wireless Keyboard Kit: Device: "/dev/input/event12"
[ 16.450] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Vendor 0x461 Product 0x4e25
[ 16.450] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found 1 mouse buttons
[ 16.450] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found scroll wheel(s)
[ 16.450] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found relative axes
[ 16.450] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: Forcing relative x/y axes to exist.
[ 16.450] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found absolute axes
[ 16.450] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: Forcing absolute x/y axes to exist.
[ 16.450] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found keys
[ 16.450] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: Configuring as mouse
[ 16.450] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: Configuring as keyboard
[ 16.450] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: Adding scrollwheel support
[ 16.450] (**) evdev: Hewlett Packard HP Wireless Keyboard Kit: YAxisMapping: buttons 4 and 5
[ 16.450] (**) evdev: Hewlett Packard HP Wireless Keyboard Kit: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 16.450] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.1/0003:0461:4E25.0005/input/input12/event12"
[ 16.450] (II) XINPUT: Adding extended input device "Hewlett Packard HP Wireless Keyboard Kit" (type: KEYBOARD, id 13)
[ 16.450] (**) Option "xkb_rules" "evdev"
[ 16.450] (**) Option "xkb_model" "pc104"
[ 16.450] (**) Option "xkb_layout" "us"
[ 16.451] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: initialized for relative axes.
[ 16.451] (WW) evdev: Hewlett Packard HP Wireless Keyboard Kit: ignoring absolute axes.
[ 16.451] (**) Hewlett Packard HP Wireless Keyboard Kit: (accel) keeping acceleration scheme 1
[ 16.451] (**) Hewlett Packard HP Wireless Keyboard Kit: (accel) acceleration profile 0
[ 16.451] (**) Hewlett Packard HP Wireless Keyboard Kit: (accel) acceleration factor: 2.000
[ 16.451] (**) Hewlett Packard HP Wireless Keyboard Kit: (accel) acceleration threshold: 4
[ 16.451] (II) config/udev: Adding input device Hewlett Packard HP Wireless Keyboard Kit (/dev/input/event13)
[ 16.451] (**) Hewlett Packard HP Wireless Keyboard Kit: Applying InputClass "evdev pointer catchall"
[ 16.451] (II) Using input driver 'evdev' for 'Hewlett Packard HP Wireless Keyboard Kit'
[ 16.451] (**) Hewlett Packard HP Wireless Keyboard Kit: always reports core events
[ 16.451] (**) evdev: Hewlett Packard HP Wireless Keyboard Kit: Device: "/dev/input/event13"
[ 16.452] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Vendor 0x461 Product 0x4e25
[ 16.452] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found 3 mouse buttons
[ 16.452] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found scroll wheel(s)
[ 16.452] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found relative axes
[ 16.452] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found x and y relative axes
[ 16.452] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: Configuring as mouse
[ 16.452] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: Adding scrollwheel support
[ 16.452] (**) evdev: Hewlett Packard HP Wireless Keyboard Kit: YAxisMapping: buttons 4 and 5
[ 16.452] (**) evdev: Hewlett Packard HP Wireless Keyboard Kit: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 16.452] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.2/0003:0461:4E25.0006/input/input13/event13"
[ 16.452] (II) XINPUT: Adding extended input device "Hewlett Packard HP Wireless Keyboard Kit" (type: MOUSE, id 14)
[ 16.452] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: initialized for relative axes.
[ 16.452] (**) Hewlett Packard HP Wireless Keyboard Kit: (accel) keeping acceleration scheme 1
[ 16.452] (**) Hewlett Packard HP Wireless Keyboard Kit: (accel) acceleration profile 0
[ 16.452] (**) Hewlett Packard HP Wireless Keyboard Kit: (accel) acceleration factor: 2.000
[ 16.452] (**) Hewlett Packard HP Wireless Keyboard Kit: (accel) acceleration threshold: 4
[ 16.452] (II) config/udev: Adding input device Hewlett Packard HP Wireless Keyboard Kit (/dev/input/mouse1)
[ 16.452] (II) No input driver specified, ignoring this device.
[ 16.452] (II) This device may have been added with another device file.
[ 16.453] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event6)
[ 16.453] (II) No input driver specified, ignoring this device.
[ 16.453] (II) This device may have been added with another device file.
[ 16.453] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event5)
[ 16.453] (II) No input driver specified, ignoring this device.
[ 16.453] (II) This device may have been added with another device file.
[ 16.453] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event4)
[ 16.453] (II) No input driver specified, ignoring this device.
[ 16.453] (II) This device may have been added with another device file.
[ 16.453] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
[ 16.453] (II) No input driver specified, ignoring this device.
[ 16.453] (II) This device may have been added with another device file.
[ 16.454] (II) config/udev: Adding input device HP WMI hotkeys (/dev/input/event7)
[ 16.454] (**) HP WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[ 16.454] (II) Using input driver 'evdev' for 'HP WMI hotkeys'
[ 16.454] (**) HP WMI hotkeys: always reports core events
[ 16.454] (**) evdev: HP WMI hotkeys: Device: "/dev/input/event7"
[ 16.454] (--) evdev: HP WMI hotkeys: Vendor 0 Product 0
[ 16.454] (--) evdev: HP WMI hotkeys: Found keys
[ 16.454] (II) evdev: HP WMI hotkeys: Configuring as keyboard
[ 16.454] (**) Option "config_info" "udev:/sys/devices/virtual/input/input7/event7"
[ 16.454] (II) XINPUT: Adding extended input device "HP WMI hotkeys" (type: KEYBOARD, id 15)
[ 16.454] (**) Option "xkb_rules" "evdev"
[ 16.454] (**) Option "xkb_model" "pc104"
[ 16.454] (**) Option "xkb_layout" "us"
[ 1192.410] (II) intel(0): switch to mode [email protected] on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 1811.202] (II) intel(0): switch to mode [email protected] on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 5455.421] (II) intel(0): switch to mode [email protected] on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none

I saw your post, and had found it incredulous that you have a 1920x1080 display. A bit of research and I found I was wrong.
So, it appears you are driving the panel at its native resolution. Unfortunately, trying to determine what you mean by "Fuzzy" is probably going to be like trying to nail Jello to a tree. But, let's give it a shot. Is it fuzzy before you start X? Are lines and shapes fuzzy? Or is it just text that is fuzzy?
If it is just fonts, it could be a problem with hinting. Hinting is where the edges of fonts are deliberately fuzzed and feathered to get the kerning correct when the physical pixels of the display don't quite line up. This works well, unless the thing doing the hinting does not understand the geometry of the display. In a color LCD, each pixel is actually made up of smaller sub pixels, generally three -- A red, a green, and a blue. Green is usually in the middle. Some displays have Two greens per pixel, arranged RGBG. Some displays even have yellow subpixels. Sometimes the subpixels are arranged left to right, sometimes they are arranged top to bottom. Long story short, if you have hinting enabled, but the geometry is configured incorrectly, bad things happen. Take a look at this wiki article

Screen is negative

My screen is negative. Black is white, white is black, and all the colors are light a photograph negative. Turning phone on and off does not help and I did not see anything in setting to help.

Look closer... you have one of the Accessibility features turned on. From the manual...
White on Black
Use White on Black to invert the colors on the iPhone display, which may make it easier to read the screen. The screen looks like a photographic negative when White on Black is turned on.
Invert the screen’s colors: In Settings, choose General > Accessibility and tap the “White on Black” switch.

X1 carbon - On screen display (brightness) does not work anymore..

I have an X1 Carbon.
Usually when i raise or decrease the screen brightness i had an on screen indicator showing me how much i decreased ot increasing either of the obove.. Now, when i do the same actions nothing apears.. can any one give me a hand?
thanks
Moderator Note: Edited subject to match content.

Hi Joben,
Welcome to Lenovo Community Forums!
I’m sorry to hear that you are facing the issue with on screen Display on ThinkPad X1 Carbon.
Please check if the you have enabled on-screen display option in graphic properties. Please click here to know the steps for enabling on-screen display.
If the issue still persists then I suggest you to update Power Manager, Power management and Hot key feature applications.
Below is the link to enter the downloads page and download latest application accordingly, please click on "Select Product" then in "QUICK PATH" enter the MTM no. select the exact model.
http://support.lenovo.com/en_US/downloads/default.page#
Hope this helps!
Best regards,
Hemanth Kumar
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

My macbook pro's screen display has suddenly gone into a strange colour setting where everything appears in a kind of infrared colour palette an I can;t seem to change it back. It's the same for all icon and websites, does anyone know how to restore?

My macbook pro's screen display has suddenly gone into a strange colour setting where everything appears in a kind of infrared colour palette an I can;t seem to change it back. It's the same for all icon and websites, does anyone know how to restore?

Wow! I think I had this same issue just last night.
I was cleaning my macbook pro retina on the outside. Then I opened it up and was wiping dust off the monitor and I can't pinpoint exactly when, but the colors changed suddenly. It looked super strange, it was like green halo's and it looked worse when looking at it at an angle. Of course I took no pictures!!! I was freaking out that my 2 grand laptop was busted and I somehow removed a protective film or something.
But I digress... The image looked very green and spacey, it was almost a neat effect. After about 5 minutes it started to look a little more digital though. There were straight lines of this halo effect on the edges and top. After about 10 minutes it turned into a predominate issue with the blacks on screen. I could open a web browser and it was unnoticable on a white background. After about 15 minutes, you could only barely see the green cloud effect if you looked at the monitor from an extreme angle. After about 20 minutes, it was completely back to normal, I almost feel paranoid like I see a halo or something strange. But I believe that might be all in my head now.
So yerp, lemme know what you guys figure out.

Brand New Iphone 5s Home Screen display defect

Here goes my ordeal with my Iphone 5s upgrade
After waiting in line for over an hour I purchased the Iphone 5s yesterday at Best Buy (Stonebriar, Frisco, TX). Later that evening, I noticed that when the time was 5:36, the home screen display was not showing the digit 6. Instead it showed a blur. I then changed the time manually to 6:36 and then to 6:43 and each time there was a digit 6 the display showed a blur instead. I must note that the phone was sitting in the grass which was a little moist (which I believe was the causing the issue). I immediately went back to the Best Buy location where I purchased the phone and requested a replacement after showing the defect. The store manager wanted me to wait in the line and I refused to do so (they sold me a defective phone so I did not see a reason why I had to go in that line all over again when it was just a replacement!). Anyways, after a tiff with the manager I left that store with my defective phone.
Next day, I went to the Apple store (Willowbend mall, Plano). I was greeted by genteleman at the entrance of the store who nicely asked if he could help. The moment I told him I suspected my new Iphone 5s was defective he said 'What!!' and made an expression of disbilief. Funny! I was asked to go to another peson who was standing and waving his hand further inside the store. I go to him and explain to him the problem and when I try to demonstrate it does not happen! Oh dear! Luckily I had enough screenshots in store and I showed them all to the store clerk. He then tells me that he can take the phone in for me and get it 'repaired'! In disbilief I ask him if he meant 'Replaced'? He says no, they will try to repair it first - he further speculates saying they will try a restore or maybe a front glass replacement and that if they still can't fix it, Apple will then replace the phone. In exasperation I tried to explain to him that the problem happened yesterday and then today it can't doesn't seem to happen, while adding that it is a brand NEW phone I purchased less than 24 hours ago and that I still am under the 14 day time-frame. I explain to him kindly that I would not be able to verify the fix (Apple does a restore or even changes the glass and returns me the phone and I must believe that the problem was fixed?? - Hel No!) and its not so nice to hear from Apple that they can't take responsibility for a defective product. He kindly says sorry and explains that it is policy and that they have to try to repair first. Oh how I wish I could've gotten Apple to sign my policy document for my money...sigh..don't work like that! So I left Apple and ran across to Best Buy mobile store asking for a replacement. The guy says Best Buy mother store and Best Buy Mobile store keep there own stock during holidays and he can't help. Sweet! I drive down 10 miles and go to a different Best Buy 'Mother' store and of course I'm asked to stand in the line. I swallow my pride and become a part of the line. My turn comes and again I explain the problem and of course the Best Buy clerk says 'Did you try a restore?' What!! Anyways, after a bit of reasoning (cribbing) with a couple of Best Buy agents, I was able to get them to replace my Iphone 5s (and of course they didn't have a gold color so I had to settle for the space gray..not a big deal though as long as this one is not defective also!)
So anybody had this display issue? Issue with Apple customer service?
Rs,
GH

Well they offered to do everything they could to work with you on the device....You are right in saying that the offered what they 'could'. Unfortunately what they could was tied by company policy.
Just like being human there are times things just go wrong- 2 out 2 IPhones 5s in 2 days! I hope people are doing better :-p
You fought against people at the store level who have /zero/ control over policy and had their hands tied by what theri bosses tell them to do. Agreed. I left instead of fighting. Unfortunately they are the first line of support and a manager maybe as far I'd get. Would love to chat with Steve Jobs but I guess now there is only one way for that :-p
They not only rushed you to get service to repair the device but you didn't even do any troubleshooting of your own to try to repair it. Now what if a restore had fixed your issue, you would have kept your device, your color, and what you paid for... - I disagree. If you read my original post, the problem happened the same evening I bought the phone. When I went to Apple I was not able to reproduce the issue. So you tell me how do I verify that restore fixed it? Wait and watch? After 14 days I can't even return the phone. The other speculation made by the rep was changing the glass. I would not try that for obvious reasons.
Why /wouldn't/ you try to repair something before spending your gas/time to replace it the moment something is amiss.
hmmm..
Now the 2nd new phone makes a rattling sound. Something is loose inside..I'd rather spend gas/time and return it than get them 'repair' it or give me a refurbished phone! Why? Because I can at this point and still get a new one with possibly no defects(fingers crossed) or I could find a company that makes better quality products :-p

Brand new Thinkstation D10 server fails to boot, no beeps or screen display

This server had been working fine for several weeks and today I needed to reboot it. It has been rebooted several times before so so I wasn't trying something new. I hit the Vista Start button and it immediately shut down. I couldn't recall if Vista prompts you to Stand-by/restart/shutdown but I think it does - this time it didn't. :/ Afterwards, it would not boot.
I tried:
Unplugging and replugging it in: it then attempted to boot but shut itself down again after about 30s.
a Power Supply Reset
Reseating the memory cards
Removing one of the 4GB memory cards
Trying the other memory card
Swapping the two memory cards
Inserting a bootable disk (it never gets to the point of reading anything although the drive spins up)
Checking that everything in the system board was plugged in
Making sure none of the wires were hitting anything else (shorting out)
When replacing that annoying cover from over the memory cards, made sure again I was not pinching any wires
The server does not beep and the (directly connected) monitor never comes alive to display anything when I attempt to reboot.
Per the docs, I observed the power supply Diagnostic LEDs and front panel Power LED while attempting to boot and only the green Diagnostic LED on the power supply is ever activated. The table indicated this means replace the system board.
Aack!
Before I head for the support # and an eventual shipment back to Lenovo, would it be worth my while to try and replace the CMOS battery? Or would a failure of that battery still have resulted in some indication of the problem (beeping and/or screen display)? Can anyone think of something else to check?
Just thought I'd ask around before assuming that I'm stuck with the system board diagnosis).
Thanks

The list of things that will make a computer power down on it's own before it can ever get into the OS or initiate a video feed is a short list.
A CPU thermal trip usually occurs within 30 seconds. This can be cause by a loose or improperly seated heat sink or a failure in the thermal grease coverage. If your D10 arrived with one CPU and you recently installed a second CPU, try taking the second CPU out. Should this work, verify the second CPU is the exact match to the first CPU and that the thermal grease is properly applied to the heat sink and the heat sink is securely mounted.
Ambient temperature thermal trip usually takes longer, but can be significantly shorten if the air baffle for the memory is not installed. Computers with high Front Side Bus frequencies result in memory DIMMS that get very hot.
DC power trip. This can happen if too much power is being drawn through any of the PCI ports or through the power supply itself.
When you are using a highend video card, check to see if the video card has it's own power connector(a small six lead box). If it does, there is a power connector, from the power supply, to plug into it. Without that power plugged in, the video card may appear to hum, and the it will draw too much power through the PCI slot.
Should you have added any additional PCI adapters, try removing these for a test. If that works, add one card back in at a time to isolate the offending PCI card.
Disconnect any USB or Firewire devices you may have attached, including the mouse and keyboard. If it comes back up and you have video, power down and reconnect the keyboard and mouse only and try again.
If you have the memory card reader option and kids, check to make certain no one has inserted something into the memory card readers. My kid inserted a quarter into one of the slots on my reader. My workstation powered down pretty fast. Consider moving the workstation to higher ground.
Last by not least, disconnect any additional optical drives you may have added. Some SATA devices have both the standard PC power connector and the SATA power connector. Do not connect both of these power sources to the same drive. The drive will be damaged and your computer will not stay powered on for very long.
Should this all fail to resolve the issue, contact Lenovo support. To make your support experience faster and more pleasurable, send them this list of things you tried. If this list of possible fixes fails, it's probably a power supply or system board issue, and I would start with the power supply.
If an electronic device has a defect it will fail within the first 90 days. Once you get it past the first 90 days, it is generally good for years.
I hope this helps!!!
Digitaloz

Screen displaying "Negative of usual colors"

Similar Messages

Maybe you are looking for