Intel GM965 TV out
Hi !
I am desperatly trying to use my laptop Acer Aspire 5315 s-video TV-Out, but I can't make it work.
Here's lspci output :
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 03)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) (rev 03)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
05:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5906M Fast Ethernet PCI Express (rev 02)
06:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)
My xorg.conf is here http://pastebin.com/pTjgmGTQ and here is Xorg log : http://pastebin.com/dU1Qj5AA
I have tried the following commands, but none worked :
xrandr -display :0 --output TV1 --set TV_FORMAT PAL; xrandr --output TV1 --mode 1024x768
xrandr -display :0 --output TV1 --set TV_FORMAT PAL; xrandr --output TV1 --mode 640x480
xrandr -display :0 --output LVDS1 --auto --output TV1 --auto --same-as LVDS1
TV screen blinks during one half second, but doesn't display anything. VGA output works fine.
Does anybody get this working ?
Thanks in advance, and forgive my poor english.
Last time I did this on my TM 5320 it worked fine (a year ago maybe?), and that was after xf86-vide-intel 2.3.2 was released (previous versions had this broken):
xrandr --output TV --set TV_FORMAT PAL
xrandr --output TV --mode 1024x768 --right-of LVDS
You can see my article for more information, and an xorg.conf with some settings that could help you further:
http://sysphere.org/~anrxc/local/Travel … -5320.html
Edit:
I remembered another detail. I think the tv-out had a weird number of pins (6 maybe?) and all the cables I could find were different... finally when I found the right cable it didn't work, TV just blinked. I tried the usual cable with 4 and that worked.
Last edited by anrxc (2011-03-08 23:57:22)
Similar Messages
-
XBMC, OpenGL and intel GM965 TV-Out
Hi !
I'm trying to set up an XBMC media center based on Arch, and I have some problem to get XBMC working with tv-out.
The media center PC is a laptop with broken LCD screen, so I'm using TV out as main display.
Xorg works fine, so as Chrome browser and other apps, but apps which uses OpenGL only gives me a black screen. I have tested with XBMC and Mednafen OpenGL output, and screen gets black for both. If I use Mednafen standard SDL video output, it works fine.
Hardware is an Intel GM965 chip, here's the lcpi output :
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 03)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) (rev 03)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
05:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5906M Fast Ethernet PCI Express (rev 02)
06:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)
Here is my Xorg log file
I'm using Archlinux LTS kernel :
$ uname -a
Linux myhost 2.6.32-lts #1 SMP Tue Mar 15 09:48:41 CET 2011 x86_64 Intel(R) Celeron(R) CPU 550 @ 2.00GHz GenuineIntel GNU/Linux
The XBMC version is 10.1-1, it's the the one packaged for Arch, from the community repository. I also tried xbmc-git package, but I had the same problem, so I get back to community package.
Is there someone here using this kind of video chip with XBMC on TV-Out ?
Is there a way to tell XBMC to use standard SDL video out instead of using OpenGL (like mednafen does) ?
Is there any options missing at xorg level ?
Thanks in advance for your help.Hi !
glxinfo output :
$ glxinfo | grep OpenGL
OpenGL vendor string: Tungsten Graphics, Inc
OpenGL renderer string: Mesa DRI Intel(R) 965GM
OpenGL version string: 2.1 Mesa 7.10.1
OpenGL shading language version string: 1.20
OpenGL extensions:
I don't have xorg.conf, I just have 3 files under /etc/X11/xorg.conf.d :
The two default files 10-evdev.conf and 10-quirks.conf :
$ cat /etc/X11/xorg.conf.d/10-evdev.conf
# Catch-all evdev loader for udev-based systems
# We don't simply match on any device since that also adds accelerometers
# and other devices that we don't really want to use. The list below
# matches everything but joysticks.
Section "InputClass"
Identifier "evdev pointer catchall"
MatchIsPointer "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev keyboard catchall"
MatchIsKeyboard "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
Option "XkbLayout" "fr"
EndSection
Section "InputClass"
Identifier "evdev touchpad catchall"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev tablet catchall"
MatchIsTablet "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev touchscreen catchall"
MatchIsTouchscreen "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
# Collection of quirks and blacklist/whitelists for specific devices.
# Accelerometer device, posts data through ABS_X/ABS_Y, making X unusable
# http://bugs.freedesktop.org/show_bug.cgi?id=22442
Section "InputClass"
Identifier "ThinkPad HDAPS accelerometer blacklist"
MatchProduct "ThinkPad HDAPS accelerometer data"
Option "Ignore" "on"
EndSection
And I have added a file named 10-monitor.conf to force 640x480 resolution to display on old TV CRT monitor :
Section "Monitor"
Identifier "TV"
HorizSync 30-50
VertRefresh 50
EndSection
Section "Screen"
Identifier "Screen_TV"
Device "Card0"
Monitor "TV"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "640x480"
EndSubSection
EndSection
Section "Device"
Identifier "Card0"
Driver "intel"
Option "AccelMethod" "uxa"
Option "Tiling" "true"
EndSection
Section "DRI"
Mode 0666
EndSection
I tried with and without "DRI" section, but it doesn't change anything -
Hi all,
Recently "upgraded" my T61p motherboard from a Nvidia gpu to the Intel GM965 gpu. Everything looks fine so far but one item. CPU T7800 is running usually below 50 deg but there is no gpu temp showing up under TPFC. Shows up as "4 gpu n/a (0x7b)"
Tried a number of temperator sensor software programs in addition to TPFC and still no indication of gpu temp. And, I read a great deal and searched the forum but can not find the answer to the question of the 965 temp monitoring. I did see one post that suggested you can sometimes lose a sensor.
So, for those using the gm 965, do you have a gpu temp sensing capability.....or, is this always missing in the 965 gpu? Or, is there some other way to measure the gpu temp? Or, is the gpu temp so low it doesn't have to be measured?
Many thanks for any advice.
Bob
EDIT: Additional info. BIOS is LENOVO 7LETC1WW (2.21), 7/1/2008. And, the new motherboard is 42W7875. O/s is Win 7 Ultimate x32.
Solved!
Go to Solution.Welcome to the forum!
There is no GPU sensor per se on a T61 board with integrated graphics, that's why you're not seeing any results in TPFC. I wouldn't be concerned about it whatsoever.
Cheers,
George
In daily use: R60F, R500F, T61, T410
Collecting dust: T60
Enjoying retirement: A31p, T42p,
Non-ThinkPads: Panasonic CF-31 & CF-52, HP 8760W
Starting Thursday, 08/14/2014 I'll be away from the forums until further notice. Please do NOT send private messages since I won't be able to read them. Thank you. -
Hi guys,
Has anybody get TV-OUT to work with this video card?
After googling for a while I can't find anything useful that let me know how to configure the TV OUT. I've tried some xrandr magick but nothing works.
Can anyone point me to a good documentation or let me know if it can be done?
This is my lspci -v output for what a display controller concerns:
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. Device 3ff3
Flags: bus master, fast devsel, latency 0, IRQ 764
Memory at fde00000 (64-bit, non-prefetchable) [size=1M]
Memory at d0000000 (64-bit, prefetchable) [size=256M]
I/O ports at c080 [size=8]
Capabilities: [90] MSI: Mask- 64bit- Count=1/1 Enable+
Capabilities: [d0] Power Management version 3
Kernel modules: intelfb
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)
Subsystem: Micro-Star International Co., Ltd. Device 3ff3
Flags: bus master, fast devsel, latency 0
Memory at fdf00000 (64-bit, non-prefetchable) [size=1M]
Capabilities: [d0] Power Management version 3
Thanx a lot in advance.Hi people,
I hope this will be useful to you. I have packaged a chroot live system to use my TV-OUT without rebooting.
Xorg 1.4 + the old i810 driver (v1.7.2) are inside, with perfectly compiling
sources (so if you want to fix the driver for the latest Xorg, you can begin from this ready system :-) ) .
This should work for all i8xx/i9xx chipsets which worked with the old i810 driver.
http://sourceforge.net/projects/i810tvout/
All feedback is welcome (on the SF.net project please) -
What do I need to make 32bit games play on x86-64 with intel gm965?
I have been trying to get a bunch of 32bit games to play on x86-64 with no luck.
Ive tried quake4, prey, and now doom3 and all seem to have the same issues. They start to work and the screen goes black, then it just goes right back to the desktop.
I have installed the entire lib32 group, and still no luck. I even tried install lib32-intel-dri from aur but still no luck.
Do I still use lib32-nvidia-utils with an intel chipset, because thats what gets installed by default when i install the lib32 group?
Here is the output from doom3 (quake4, and prey had a very similar output where they all said idRenderSystem::Shutdown() but I already removed the packages out of frustration so I dont have the outputs from them, Im pretty sure its probably the same exact problem with all of them though)
[tj@arch ~]$ doom3
DOOM 1.3.1.1304 linux-x86 Jan 16 2007 21:58:02
found interface lo - loopback
found interface wlan0 - 192.168.1.50/255.255.255.0
------ Initializing File System ------
Loaded pk4 /opt/doom3/base/game01.pk4 with checksum 0x51c6981f
Loaded pk4 /opt/doom3/base/game02.pk4 with checksum 0xf3ec6f7
Loaded pk4 /opt/doom3/base/game03.pk4 with checksum 0x5d4230ea
Loaded pk4 /opt/doom3/base/pak000.pk4 with checksum 0x28d208f1
Loaded pk4 /opt/doom3/base/pak001.pk4 with checksum 0x40244be0
Loaded pk4 /opt/doom3/base/pak002.pk4 with checksum 0xc51ecdcd
Loaded pk4 /opt/doom3/base/pak003.pk4 with checksum 0xcd79d028
Loaded pk4 /opt/doom3/base/pak004.pk4 with checksum 0x765e4f8b
Loaded pk4 /opt/doom3/base/pak005.pk4 with checksum 0x8ffc3621
Loaded pk4 /opt/doom3/base/pak006.pk4 with checksum 0x95b65ab
Loaded pk4 /opt/doom3/base/pak007.pk4 with checksum 0x666bdb3c
Loaded pk4 /opt/doom3/base/pak008.pk4 with checksum 0x23ae5993
Current search path:
/home/tj/.doom3/base
/opt/doom3/base
/opt/doom3/base/pak008.pk4 (3 files)
/opt/doom3/base/pak007.pk4 (38 files)
/opt/doom3/base/pak006.pk4 (48 files)
/opt/doom3/base/pak005.pk4 (63 files)
/opt/doom3/base/pak004.pk4 (5137 files)
/opt/doom3/base/pak003.pk4 (4676 files)
/opt/doom3/base/pak002.pk4 (6120 files)
/opt/doom3/base/pak001.pk4 (8972 files)
/opt/doom3/base/pak000.pk4 (2698 files)
/opt/doom3/base/game03.pk4 (2 files)
/opt/doom3/base/game02.pk4 (2 files)
/opt/doom3/base/game01.pk4 (2 files)
game DLL: 0x0 in pak: 0x0
Addon pk4s:
file system initialized.
----- Initializing Decls -----
------- Initializing renderSystem --------
using ARB renderSystem
renderSystem initialized.
5206 strings read from strings/english.lang
----- Initializing Sound System ------
sound system initialized.
----- R_InitOpenGL -----
Setup X display connection
dlopen(libGL.so.1)
Initializing OpenGL display
Using XFree86-VidModeExtension Version 2.2
DGA DirectVideo Mouse (Version 2.0) initialized
Free86-VidModeExtension Activated at 640x480
Using 8/8/8 Color bits, 8 Alpha bits, 24 depth, 8 stencil display.
GL_RENDERER: Mesa DRI Intel(R) 965GM GEM 20090712 2009Q2 RC3
GL_EXTENSIONS: GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_shadow GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_mirrored_repeat GL_ARB_texture_non_power_of_two GL_ARB_vertex_program GL_ARB_window_pos GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_draw_range_elements GL_EXT_framebuffer_object GL_EXT_fog_coord GL_EXT_multi_draw_arrays GL_EXT_packed_pixels GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_edge_clamp GL_EXT_texture_env_add GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_lod_bias GL_EXT_texture_object GL_EXT_vertex_array GL_IBM_texture_mirrored_repeat GL_NV_blend_square GL_NV_light_max_exponent GL_NV_texture_env_combine4 GL_NV_texture_rectangle GL_NV_texgen_reflection GL_NV_vertex_program1_1 GL_SGIS_generate_mipmap GL_SGIS_texture_lod
------- Input Initialization -------
XKB extension: compile time 0x1:0x0, runtime 0x1:0x0: OK
XKB extension present on server ( 0x1:0x0 )
dlopen(libasound.so.2)
asoundlib version: 1.0.21a
Alsa is available
------ Alsa Sound Initialization -----
opened Alsa PCM device default for playback
device buffer size: 5644 frames ( 22576 bytes )
allocated a mix buffer of 16384 bytes
...using GL_ARB_multitexture
...using GL_ARB_texture_env_combine
...using GL_ARB_texture_cube_map
...using GL_ARB_texture_env_dot3
...using GL_ARB_texture_env_add
...using GL_ARB_texture_non_power_of_two
...using GL_ARB_texture_compression
X..GL_EXT_texture_compression_s3tc not found
...using GL_EXT_texture_filter_anisotropic
maxTextureAnisotropy: 16.000000
...using GL_EXT_texture_lod
...using GL_1.4_texture_lod_bias
X..GL_EXT_shared_texture_palette not found
...using GL_EXT_texture3D
...using GL_EXT_stencil_wrap
X..GL_NV_register_combiners not found
X..GL_EXT_stencil_two_side not found
X..GL_ATI_separate_stencil not found
X..GL_ATI_fragment_shader not found
X..GL_ATI_text_fragment_shader not found
X..GL_ARB_vertex_buffer_object not found
...using GL_ARB_vertex_program
...using GL_ARB_fragment_program
X..EXT_depth_bounds_test not found
---------- R_NV20_Init ----------
Not available.
----------- R200_Init -----------
Not available.
---------- R_ARB2_Init ----------
Available.
----- R_ReloadARBPrograms -----
glprogs/test.vfp
glprogs/test.vfp
glprogs/interaction.vfp
glprogs/interaction.vfp
glprogs/bumpyEnvironment.vfp
glprogs/bumpyEnvironment.vfp
glprogs/ambientLight.vfp
glprogs/ambientLight.vfp
glprogs/shadow.vp
glprogs/R200_interaction.vp
glprogs/nv20_bumpAndLight.vp
glprogs/nv20_diffuseColor.vp
glprogs/nv20_specularColor.vp
glprogs/nv20_diffuseAndSpecularColor.vp
glprogs/environment.vfp
glprogs/environment.vfp
glprogs/arbVP_glasswarp.txt: File not found
glprogs/arbFP_glasswarp.txt: File not found
WARNING: vertex array range in virtual memory (SLOW)
signal caught: Segmentation fault
si_code 1
Trying to exit gracefully..
Shutting down sound hardware
----------- Alsa Shutdown ------------
close pcm
dlclose
idRenderSystem::Shutdown()
double fault Segmentation fault, bailing out
*** glibc detected *** ./doom.x86: double free or corruption (!prev): 0x0c3a5560 ***
======= Backtrace: =========
/opt/lib32/lib/libc.so.6[0xf73ea5e1]
/opt/lib32/lib/libc.so.6[0xf73ebce2]
/opt/lib32/lib/libc.so.6(cfree+0x6d)[0xf73eedad]
/opt/lib32/usr/lib/libGLcore.so.1[0xf4c96c97]
/opt/lib32/lib/libc.so.6[0xf73ac36f]
/opt/lib32/lib/libc.so.6[0xf73ac3df]
./doom.x86[0x829e225]
/lib/ld-linux.so.2[0xf7759517]
/opt/lib32/lib/libdl.so.2[0xf7727c84]
/lib/ld-linux.so.2[0xf7753a96]
/opt/lib32/lib/libdl.so.2[0xf772807c]
/opt/lib32/lib/libdl.so.2(dlclose+0x2a)[0xf7727cba]
./doom.x86[0x835e008]
======= Memory map: ========
08048000-0842e000 r-xp 00000000 08:03 391681 /opt/doom3/doom.x86
0842e000-08448000 rwxp 003e6000 08:03 391681 /opt/doom3/doom.x86
08448000-0a613000 rwxp 00000000 00:00 0
0be99000-0c4e0000 rwxp 00000000 00:00 0 [heap]
f46b7000-f48b8000 rwxp 00000000 00:00 0
f48b8000-f497b000 r-xp 00000000 08:03 269600 /opt/lib32/usr/lib/libasound.so.2.0.0
f497b000-f497f000 rwxp 000c3000 08:03 269600 /opt/lib32/usr/lib/libasound.so.2.0.0
f497f000-f5999000 r-xp 00000000 08:03 270117 /opt/lib32/usr/lib/libGLcore.so.190.42
f5999000-f59df000 rwxp 01019000 08:03 270117 /opt/lib32/usr/lib/libGLcore.so.190.42
f59df000-f59ed000 rwxp 00000000 00:00 0
f59ed000-f5a84000 r-xp 00000000 08:03 270127 /opt/lib32/usr/lib/libGL.so.190.42
f5a84000-f5a9d000 rwxp 00097000 08:03 270127 /opt/lib32/usr/lib/libGL.so.190.42
f5a9d000-f5aac000 rwxp 00000000 00:00 0
f6600000-f6621000 rwxp 00000000 00:00 0
f6621000-f6700000 ---p 00000000 00:00 0
f67d7000-f67e1000 r-xp 00000000 08:03 269298 /opt/lib32/lib/libnss_files-2.10.1.so
f67e1000-f67e2000 r-xp 00009000 08:03 269298 /opt/lib32/lib/libnss_files-2.10.1.so
f67e2000-f67e3000 rwxp 0000a000 08:03 269298 /opt/lib32/lib/libnss_files-2.10.1.so
f682c000-f6833000 r-xp 00000000 08:03 269301 /opt/lib32/lib/librt-2.10.1.so
f6833000-f6834000 r-xp 00006000 08:03 269301 /opt/lib32/lib/librt-2.10.1.so
f6834000-f6835000 rwxp 00007000 08:03 269301 /opt/lib32/lib/librt-2.10.1.so
f6835000-f6839000 r-xp 00000000 08:03 269915 /opt/lib32/usr/lib/libXfixes.so.3.1.0
f6839000-f683a000 rwxp 00003000 08:03 269915 /opt/lib32/usr/lib/libXfixes.so.3.1.0
f683a000-f6842000 r-xp 00000000 08:03 269710 /opt/lib32/usr/lib/libXrender.so.1.3.0
f6842000-f6843000 rwxp 00007000 08:03 269710 /opt/lib32/usr/lib/libXrender.so.1.3.0
f6843000-f684b000 r-xp 00000000 08:03 269917 /opt/lib32/usr/lib/libXcursor.so.1.0.2
f684b000-f684c000 rwxp 00007000 08:03 269917 /opt/lib32/usr/lib/libXcursor.so.1.0.2
f684c000-f684d000 rwxp 00000000 00:00 0
f684d000-f684f000 rwxp 00000000 00:0c 1497 /dev/zero
f684f000-f6850000 r-xp 00000000 08:03 270124 /opt/lib32/usr/lib/libnvidia-tls.so.190.42
f6850000-f6851000 rwxp 00000000 08:03 270124 /opt/lib32/usr/lib/libnvidia-tls.so.190.42
f6851000-f6852000 ---p 00000000 00:00 0
f6852000-f7056000 rwxp 00000000 00:00 0
f7097000-f70cb000 rwxp 00000000 00:00 0
f710c000-f713b000 rwxp 00000000 00:00 0
f71bd000-f71fa000 rwxp 00000000 00:00 0
f72bd000-f731b000 rwxp 00000000 00:00 0
f735c000-f735d000 rwxp 00000000 00:00 0
f735d000-f7361000 r-xp 00000000 08:03 269698 /opt/lib32/usr/lib/libXdmcp.so.6.0.0f7361000-f7362000 rwxp 00003000 08:03 269698 /opt/lib32/usr/lib/libXdmcp.so.6.0.0
f7362000-f7363000 rwxp 00000000 00:00 0
f7363000-f7365000 r-xp 00000000 08:03 269696 /opt/lib32/usr/lib/libXau.so.6.0.0
f7365000-f7366000 rwxp 00001000 08:03 269696 /opt/lib32/usr/lib/libXau.so.6.0.0
f7366000-f737e000 r-xp 00000000 08:03 269664 /opt/lib32/usr/lib/libxcb.so.1.1.0
f737e000-f737f000 rwxp 00017000 08:03 269664 /opt/lib32/usr/lib/libxcb.so.1.1.0
f737f000-f74bf000 r-xp 00000000 08:03 269303 /opt/lib32/lib/libc-2.10.1.so
f74bf000-f74c1000 r-xp 00140000 08:03 269303 /opt/lib32/lib/libc-2.10.1.so
f74c1000-f74c2000 rwxp 00142000 08:03 269303 /opt/lib32/lib/libc-2.10.1.so
f74c2000-f74c5000 rwxp 00000000 00:00 0
f74c5000-f74e2000 r-xp 00000000 08:03 269791 /opt/lib32/usr/lib/libgcc_s.so.1
f74e2000-f74e3000 rwxp 0001c000 08:03 269791 /opt/lib32/usr/lib/libgcc_s.so.1
f74e3000-f7507000 r-xp 00000000 08:03 269299 /opt/lib32/lib/libm-2.10.1.so
f7507000-f7508000 r-xp 00023000 08:03 269299 /opt/lib32/lib/libm-2.10.1.so
f7508000-f7509000 rwxp 00024000 08:03 269299 /opt/lib32/lib/libm-2.10.1.so
f7509000-f750a000 rwxp 00000000 00:00 0
f750a000-f75f2000 r-xp 00000000 08:03 269783 /opt/lib32/usr/lib/libstdc++.so.6.0.13
f75f2000-f75f3000 ---p 000e8000 08:03 269783 /opt/lib32/usr/lib/libstdc++.so.6.0.13
f75f3000-f75f7000 r-xp 000e8000 08:03 269783 /opt/lib32/usr/lib/libstdc++.so.6.0.13
f75f7000-f75f8000 rwxp 000ec000 08:03 269783 /opt/lib32/usr/lib/libstdc++.so.6.0.13
f75f8000-f75ff000 rwxp 00000000 00:00 0
f75ff000-f760c000 r-xp 00000000 08:03 269921 /opt/lib32/usr/lib/libXext.so.6.4.0
f760c000-f760d000 rwxp 0000d000 08:03 269921 /opt/lib32/usr/lib/libXext.so.6.4.0
f760d000-f7723000 r-xp 00000000 08:03 269704 /opt/lib32/usr/lib/libX11.so.6.3.0
f7723000-f7727000 rwxp 00115000 08:03 269704 /opt/lib32/usr/lib/libX11.so.6.3.0
f7727000-f7729000 r-xp 00000000 08:03 269311 /opt/lib32/lib/libdl-2.10.1.so
f7729000-f772a000 r-xp 00001000 08:03 269311 /opt/lib32/lib/libdl-2.10.1.so
f772a000-f772b000 rwxp 00002000 08:03 269311 /opt/lib32/lib/libdl-2.10.1.so
f772b000-f773f000 r-xp 00000000 08:03 269308 /opt/lib32/lib/libpthread-2.10.1.so
f773f000-f7740000 ---p 00014000 08:03 269308 /opt/lib32/lib/libpthread-2.10.1.so
f7740000-f7741000 r-xp 00014000 08:03 269308 /opt/lib32/lib/libpthread-2.10.1.so
f7741000-f7742000 rwxp 00015000 08:03 269308 /opt/lib32/lib/libpthread-2.10.1.so
f7742000-f7745000 rwxp 00000000 00:00 0 /usr/bin/doom3: line 5: 10177 Aborted linux32 ./doom.x86 $*
[tj@arch ~]$
Last edited by tjwoosta (2009-11-12 21:19:35)Dump lib32, get a 32-bit chroot, and run with schroot -p "your game"
Within your chroot you'd need to have the intel drivers installed in a version exactly matching your main system's. It takes a bit more HD space (less than 1 GB), but you get a much easier system since you're using the packages maintained in the repos by devs/TUs instead of lib32 packages maintained (primarily) by volunteers for their own specific system. -
Intel imac line out hifi trouble
Hello all, i just tried an unsucessful search and decided to just post my question. I bought an imac intel duo a month or so ago. I was not impressed with the speakers so i bought the apple hifi to go with my ipod and also plug into my imac. Everything worked fine for about 3 days. Then any audio output coming from the computer is messed up. It is just garbage coming over the line. I unplugged the hifi and it plays fine with the ipod and the internal speakers for the imac work fine. Also when i plug in a pair of head phones the imac line out sounds the same garbage as the hifi. Can the line out jack break on its own. Also i live in north louisiana and the closest apple store in 3 hours away in dallas. I have the apple card plan for 3 years, but i really don't want to drive all the way to dallas. If anyone has heard of this or has a fix please email me at [email protected] I can't guarantee you i can find this thread again to read the response if i get any.
bye and up till now i have loved my imac
rolandI bought the applecare package, and they are sending someone out to take a look. I removed parallels and windows xp virtual computer, Although, i would like them back, if they caused the problem, it didn't correct it when parallels when bye bye.
Anyway, hopefully this applecare rep, will be a smart fellow and know his stuff, and not rip apart my machine. I am kinda worried. Anyone had any experiences with applecare outcall tech's. Let me know, i always prefered the incalls better myself, but this is my first time again.
Don't know if anyone got my lame pun, but any feedback about applecare would be apprecieted... And i will update the result and if the problem is solved, i will change the status of my question to answered. -
Xorg-server 1.6 and Intel GM965 video card[SOLVED]
Hi,
Because of gtk2/libxi upgrade issue / keyboard layout issue I had to upgrade to xorg-server 1.6 from testing. It won't configure: "Missing output drivers. Configuration failed". Any ideas?
Last edited by Llama (2009-04-02 05:21:07)Thanks!
xf86-video-intel
xf86-input-synaptics
from testing is the solution - more or less .
testing disabled again:
# pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
kdemod-core is up to date
kdemod-extragear is up to date
archlinuxfr is up to date
:: Starting full system upgrade...
warning: intel-dri: local (7.3-1) is newer than extra (7.2-2)
warning: libgl: local (7.3-1) is newer than extra (7.2-1)
warning: xf86-input-evdev: local (2.2.0-1) is newer than extra (2.1.2-1)
warning: xf86-input-synaptics: local (1.1.0-1) is newer than extra (1.0.0-1)
warning: xorg-server: local (1.6.0-1) is newer than extra (1.5.3-4)
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: intel-dri: requires libdrm>=2.4.4
:: libgl: requires libdrm>=2.4.5
Any ideas?
Last edited by Llama (2009-03-31 19:15:25) -
Intel Xserve Lights Out Management Config Question
When setting up my Intel Xserve I was confused and still am about the way LOM is set up.
Ethernet port 1 uses IP XXX.XXX.XXX.50 for web
Then LOM asked for another IP address on port 1 so I gave it XXX.XXX.XXX.51
How can one port have 2 different IP addresses?
Server monitor connects to XXX.XXX.XXX.51 and all of the other server tools connect to XXX.XXX.XXX.50
Is this correct?
I use port 2 for internal use. Should I use port 2 for LOM?>Thank you and I did read it before. So what I doing is correct?
What you did is valid, yes. correct? maybe not.
Specifically, I'm concerned by the statement:
>Then LOM asked for another IP address on port 1 so I gave it XXX.XXX.XXX.51
I use port 2 for internal use. Should I use port 2 for LOM?
From your description it sounds like ethernet 1 is used for your public network. This means you've configured LOM in your public network, meaning (firewall aside) anyone can hit your LOM from outside the network, shutdown your machine etc., etc.
I would only ever configure LOM on an private/internal network. There should be no reason to manage LOM from the public network. -
New Intel Xserve Lights Out Management dies
Have a new Xserve with LOM. Problem is that after about 1/2 an hour of monitoring with the Server Monitor application from my desktop MacPro the Xserve stops responding via Server Monitor. The only way to get it to work again is to reboot the server. Not good. Anyone else seeing this behavior? Anyone have a fix or can someone from Apple confirm this is a known problem?
Thanks!Ok, Having fought with this for the last 2 days, lack of solid documentation, etc, here's my results:
First set dns and reversedns (obviously)
EN0 set to 10.0.1.51
EN1 Disabled
ILO1 set to 10.0.1.52
ILO2 set to 0.0.0.0
This configuration worked, occasionally, but had numerous "Failed to contact server", and remote ipmitool was SLOW.
EN0 set to 10.0.1.51
EN1 Disabled
ILO1 set to 0.0.0.0
ILO2 set to 10.0.1.52
This configuration worked, even less than the first, and remote ipmitool acted slow, but returned nothing.
EN0 set to 10.0.1.51
EN1 set to 10.0.1.52
ILO1 set to 0.0.0.0
ILO2 set to 10.0.1.52
This configuration worked, occasionally, but had numerous "Failed to contact server", and remote ipmitool was SLOW.
EN0 set to 10.0.1.51
EN1 set to 0.0.0.0 (Static IP, and all fields cleared)
ILO1 set to 0.0.0.0
ILO2 set to 10.0.1.52
This configuration works, consistanly and remote ipmitool was very fast.
The command I was using to test ipmitool was:
$ ipmitool -H 10.0.1.52 -U USERNAME -P PASSWORD chassis status
In addition, I found that ANY changes to the IP for EN1 or ILO1/2 caused the ILO module to get lost, and require a reboot. (unplug method)
Thus, this is the method I found to get it working, after setting DNS and RDNS for the 2 IP addresses I was to use:
1) Unplug the power from the XServe for 10 seconds at least (others recommend 30, but I believe that as soon as all lights are off, that's sufficient)
2) In Network Preferences, set up Built-in Ethernet 1 as you'd like for whatever network access you will need.
3) In Network Preferences, enable (if off) Built-in Ethernet 2, and clear all fields. IP address will default to 0.0.0.0, Subnet Mask will default to 255.255.255.0, and all other fields will be blank.
4) In server admin, use "Configure local Machine" to default all values on Port 1 so that IP and gateway are 0.0.0.0 and subnet mask is 255.255.255.0, then switch to Port 2, configure the settings you want the ILO port to use. (do not use the same IP as EN0 obviously).
5) Set the username and password for the ILO user. (I had NO problems whatsoever with usernames less than 8 characters contrary to reports to this extent) You MUST enter a password again, regardless if it's been set in the past, then apply the settings (authenticate if necessary).
6) Shutdown, and disconnect the power once more to shutdown ILO.
7) Boot, make sure the XServe can login to itself at localhost with the ILO login name and password.
8) On another system on the same subnet, run:
$ ipmitool -H IPADDRESS -U USERNAME -P PASSWORD chassis status
(replacing IPADDRESS with the ILO's IP address and USERNAME and PASSWORD with the ones you set in step 5)
9) if you see something like:
System Power : on
Power Overload : false
Power Interlock : inactive
Main Power Fault : false
Power Control Fault : false
Power Restore Policy : always-on
Last Power Event : ac-failed
Chassis Intrusion : inactive
Front-Panel Lockout : inactive
Drive Fault : false
Cooling/Fan Fault : false
you should be fine, and Server Monitor on the remote system should connect fine.
The conclusion is that the key to getting this running is in enabling EN1, yet not giving it any TCP configuration.
Hope this helps someone out there... -
Internet connection on Intel iMac cuts out after screensaver.
Hello. First, I need to point out that the issue I'm having is specific to this machine; other computers in our home network running a myriad of operating systems have no trouble whatsoever sustaining their internet connection, including a MacBook. Whatever's going wrong is going wrong with this machine only.
We have a DSL connection from Verizon, being split through a NetGear router. We have tested this connection wired and wirelessly, and there is no flaw with it. The only problem is the iMac; the problem persists when it's connected to the router using an ethernet cable AND when it connects wirelessly through AirPort.
The problem is this: Whenever this iMac goes to screensaver or goes to sleep, its internet connection stops working after it wakes up. I don't mean to say that the connection gets interrupted, rather that it stops working entirely. I cannot ping any address from the terminal, not even the router. Safari and Firefox both stop recognizing the internet connection. The computer has to be restarted before the iMac will realize it has an internet connection again.
What can cause this, and what is the solution? Thanks.I should also point out that the issue is specific to Mac OSX. This computer has a Windows XP partition. I just tested the issue on the Windows partition, both with screen saver and standby, and it was able to sustain its internet connection with no issues whatsoever. To clarify, multiple computers with Mac OSX have not had this problem, and this computer, using a different operating system, has not had this problem. The issue is totally isolated to this one specific machine, using one specific operating system.
-
Talkin' Bout My Generations: A Brief History of Intel-based Portable Macs
During my first four years here at Discussions, I came across a fairly common problem while trying to help folks using Windows on a Mac: very few people I responded to could tell mewhat kind of system they were using. Many were users of portable Macs, so to try and help them out identifying the machines they used, I thought of making a guide to portableidentification. But as I was writing this article two years ago, I got thinking about a more detailed history of the MacBook family from 2006 to 2010. I’ve taken many of the news snippets I’ve read from Macworld magazine and other sources to provide the historical content in this guide and combinedthem with my personal opinions on each model. Specifications where used have been verified by Brock Kyle’s EveryMac.com and by Apple support documents as well as keynote speeches from Apple execs. The opinions provided are those of the author and are independent of Apple, Inc, so in other words, if you feel differently about these machines…
DON’T SHOOT THE MESSENGER!
And now, the guide. Enjoy!
First generation (1G):
These are the only 32-bit Intel Mac portables in the field, sporting Intel Core Duo (“Yonah”) processors from 1.83-2.16 GHz (Early '06, including Glossy)
MacBook
This long-awaited upgrade of the iBook has a port setup comparable to the Mid-'05 iBook--2 USB 2.0, 1 FW400, audi oout, mini video. Also uses an inset keyboard, which drew some groans from the community-at-large when it first launched. Internally, uses an Intel GMA950 graphics system that borrows up to 64 MB as video RAM and adds 16 MB overhead.
Case type: Solid white or black polycarbonate shell
Chipset: Intel 945GM
Standard RAM: 512 MB (432 MB usable)
Maximum RAM: 2.00 GB PC2-5300 DDR2 SDRAM(1968 MB usable)
Pros: Solid performance vs. iBook, goodbasic machine for the Web, hard drive is user-serviceable.
Cons: Poor graphics make this unit ascratch for mid-level business work, games or creative apps; limited RAM, no64-bit support
MacBook Pro
This was Apple's Intel debut, along withthe iMac (Core Duo). Apple flashed a1.67 GHz prototype at Macworld Expo ‘06 that was scratched in production for a1.83 GHz model. Supply chain economicsresulted in an optical drive downgrade to a standard single-layer drive fromthe double-layer drives in the late '05 PowerBooks. It's also the only model in the MacBook Procontinuum not to bear a FireWire 800 port. Although functionally similar to the MacBookthat followed it, this line has discrete graphics by way of AMD's RADEONX1600--up to 256 MB. Slightly revisedversions, rolled in by mid-year, included a glossy display and improved videoRAM.
Case type: Anodized aluminum compositewith plastic edging.
Chipset: Intel 945GM
Standard RAM: 1 GB
Maximum RAM: 2.00 GB PC2-5300 DDR2 SDRAM
Pros: Good step up from PB '05, can runpro apps and games with ease
Cons: limited RAM, no 64-bit support, no DVD±DL support, lack of FW800 abother for some
Second generation (2G):
The 2G portables (“Late 2006” in Applespeak) were a mild speed bump of the 1G lines, replacing the 32-bit Core with the 64-bit Core2 (“Merom”). Processor speeds ranged from 2.0 GHz-2.33 GHz. Apple fixed many 1G shortcomings here, but retained the 945 family chipsets until well into 2007. As aresult of the 945 family’s addressing limitations, usable RAM is limited to 3GB, even when 4 GB can be installed. (See http://www.everymac.com/systems/apple/macbook_pro/faq/macbook-pro-core-2-duo-3-g b-memory-limitation-details.html) Further, Apple has chosen to limitWindows support on these units to Vista; anything else is “use at own risk”.
On the plus side, these 2G portables arethe absolute earliest qualifiers for Mac OS X Lion, albeit with a significantlylimited user experience—that is, many features of note simply are not possible given the nature of the 2G internals.
MacBook
No visible markers set these units apart from the 1G models, and all internals are the same save for the Core2 CPU. These units were slightly revised in 2007 toenable draft 802.11n support; those models shipped in October 2006 and onward could download an update to enable 802.11n. The only way to confirm a 2G MacBook is via software; the Model ID iseither ”2,1” or “2,2”
Case type: Solid white or blackpolycarbonate shell
Chipset: Intel 945GM
Standard RAM: 1 GB (944 MB usable)
Maximum RAM: 3.00 GB PC2-5300 DDR2 SDRAM (2992 MB usable)
Pros: Core2 offers 64-bit support and modest speed boost, max RAM up
Cons: Still comes up short forhigh-demand applications.
MacBook Pro
Functionally similar to its predecessor while retaining the AMD X1600 graphics, the 2G Pro had three notable differences. This line marks the permanent return of the FireWire 800 port—this one’s on the right side. Also back for an encore is the double-layer SuperDrive; Apple’s suppliers finally had the size of optical drive that Apple needed. Like the MacBook, it also gets a lift from the new Core2 CPUs with twice as much L2 cache as their predecessors and their trendier plastic-clad siblings.
Case type: Anodized aluminum composite with plastic edging.
Chipset: Intel 945GM
Standard RAM: 1 GB
Maximum RAM: 3.00 GB PC2-5300 DDR2 SDRAM
Pros: FW800 is back, as is DVD±DL; max RAM up, graphics still strong
Cons: Speed improvement only nominal, Windows Vista support still lacking inspots (X1000-series chips are not DX10 qualified)
Third generation (3G):
The “Mid/Late 2007” portables were somewhat of a redesign from the inside, though they remained similar to 2G models when viewed from without. Common to both lines is the Intel 965 chipset family, best known by its Intel codename, “Santa Rosa”; with it, the system bus got ramped to 800 MT/s while the memory bus remained at 667 MT/s. Here, the Core2 gets another modest speed bump, with standard frequencies ranging from 2.1 GHz-2.4 GHz. At this time, the RAM ceiling was lifted, allowing 4 GB to be used in all models and making theseMacs capable 64-bit machines. Windows x64 variants will run on this class, but it requires Boot Camp 2.1 or higher and some finesse with installing individual software packages since Apple’s installer places a soft block on these units.
Also of note: 3G and 4G MacBook Pros were particularly susceptible to a defect in the NVIDIA graphics chip, which left unchecked would cause these units not to display video, or to show scrambled video. Apple has a current repair program to fixthis issue if you should run across it, but time is running out. Unless you are aware that the defect has been repaired, these models are best avoided
MacBook
By the time the 3G models surfaced, the2G models were dealing with heavy criticism for not being refreshed in sync with the Pro models. Apple had three convincing reasons for such a delay. First came the iPhone EDGE, for which development was a top priority. The delay actually bought some time for Apple to reveal the other two reasons; Intel was providing the GMA X3100 as a companion to the GM965, which in itself was a modest improvement over the GMA 950 used in the first two iterations; and Apple had been working on its latest flagship OS, “Leopard”, released just days before the new MacBook surfaced on All Saints’ Day (11/1). One might say that waiting does indeed payoff, judging from Macworld’s bench scores of the 3G MacBooks, 2007 was a good year to upgrade the old iBook to something better.
Case type: Solid white or black polycarbonate shell
Chipset: Intel GM965
Standard RAM: 1 GB (880 MB usable)
Maximum RAM: 4.00 GB PC2-5300 DDR2 SDRAM (3952 MB usable)
Pros: Better graphics, potentially faster WLAN support, improved speed, conservative energy usage
Cons: Poor graphics in Windows, game support on both platforms limited to casual titles (many FPS/RTS/MMO games not supported)
MacBook Pro
The 3G Pro underwent a massive interior overhaul in June 2007, sporting NVIDIA GeForce 8600M GT graphics and—for the first time in an Apple portable—an option to build a Core2 Extreme into the unit at 2.6 GHz. These were the first portables to carry 802.11n as a standard option, as well as the first Apple portables touse an LED-backlit display. The 3G Pro also meets or exceeds all Windows Vista operating requirements, and was one of the best performing computers to run Vista, according to PC World.
Unfortunately for longtime notebook users, the 3G lines of the MacBook Pro also mark some “lasts”. The line of 3G Pros was the last line of portables to have officially shipped with Tiger, the last portables to includean Apple Remote as standard equipment, and, perhaps more notably, the last tobear a traditional numeric keypad.
Case type: Anodized aluminum composite with plastic edging.
Chipset: Intel GM965
Standard RAM: 2 GB
Maximum RAM: 4.00 GB PC2-5300 DDR2 SDRAM
Pros: Significantly improved graphics, greater energy efficiency over 2G units due to chipset and display upgrades, fastest unit of its time for current OSes, solid all-around performance, potentially faster WLAN support.
Cons: Not quite “future-proof”
Fourth generation (4G)
The “Early 2008” portables were met with fervent anticipation, as Apple hinted about “something in the air” at what would be CEO Steve Jobs’ final Macworld Expo address. Notebooks were all the rage, as was the upcoming iPhone software upgrade that gave rise to application development and the App Store. Exciting news indeed, it was. Yet, as was the norm in Jobsian monologues, he had “one more thing” to show off. Inter-office memos? Nope, but it did arrive in the classic manila envelope used for such. It was the first-generation MacBook Air, partof a 4G lineup that saw revamped Core2 CPUs ranging from 1.6 GHz all the way upt o 2.6 GHz depending on model and build options.
The new CPUs were based on Intel’s latest “Penryn” cores, some of which received a drop in L2 cache versus the “Merom” cores used in 2G and 3G units. However, the drop in cache did little to impact performance; the new CPUs were actually faster by a slight margin at the same speeds as prior Core2’s, per Macworld’s bench scores. As there were few changes in case designapart from removing the keypad from the MacBook Pro, only software can separate a 4G unit from a 3G unit.
The 4G units, and all units following, officially support x64-native Windows via Boot Camp 2.1 as included on their Install Discs, or ondiscs with future versions of OS X and Boot Camp.
MacBook
The 4G MacBook saw the processor upgrade and little else,but the bump was likely enough to convince any but the hard-core 12” PowerBookenthusiasts to cross over to Intel. Because it’s still based on the Santa Rosa (GM965) platform, the 20-pluspercentage point improvements touted by tech-savvy bloggers and enthusiastsites are never realized. Rather, some sources have documented a roughimprovement of between three percent and ten percent over the 3G units.
Sadly for some, this model is the last MacBook to bear anysize and speed of FireWire port.
Case type: Solid white or black polycarbonate shell (as of late 2008, white only)
Chipset: Intel GM965
Standard RAM: 2 GB (1904 MB usable)
Maximum RAM: 4.00 GB PC2-5300 DDR2 SDRAM (3952 MB usable)
Pros: Still a solid machine for light work, cheap, fast for its price
Cons: It’s the only cheap way to make your FireWire gear work
MacBook Air
The new kid on the block this go-around;the MacBook Air is Apple’s first sub-notebook since the PowerBook Duo of the early 1990’s. Classified as a “thin and light”, the Air is a very strikingdefinition of that term. At three pounds weight and 0.16” to 0.76” thickness, and with logic circuitry the length of a standard No. 2 pencil, Apple could crow about making “the world’s thinnest notebook” and still pack more punch into a space of 14 inches at a time when other sub-note vendors were still trying to shrink their wares. These vendors, according to Jobs, started shrinking items that shouldn’t be shrunk. Where most sub-notes had 11” or 12” screens, for example, the Air packed in a 13-incher; and when a keyboard was needed for the Air, Apple went with a full-size board identical to the then one-and-a-half-year-old MacBook design, complete with inset keys. From the MacBook Pro, the Air gained an aluminum finish as well as a backlit keyboard. On its own, the Air introduced solid-state storage (colloquially “flash drives”) as hard drives for the Mac. However, this option added $1,000 to the Air’s asking price and dropped its already limited storage capacity from80 GB to 64 GB. To add insult to injuryin some minds, the Air also dropped common expansion options and an internal optical drive to acquire its legendary dimensions. Left after shrinkage: a single USB port, an audio jack, and a “micro-DVI” video port. Despite these sacrifices, the 1G MacBook Air still outclasses other sub-notes where it counts because its chipset is the same GM965 used in the 3G and 4G MacBook offerings in addition to having the fastest low-voltage CPU’s of the day in custom quarter-sized packages. Its performance in comparison to full-featured notebooks is lower by way of processor speed being lower, and yet normal for a portable of its class.
Case type: Anodized aluminum
Chipset: Intel GM965
Standard RAM: 2 GB onboard (1904 MB usable)
Pros: Size and weight offer maximumportability, big screen and keyboard offer comfort for travelers, multi-gesturetrackpad has large surface for easy usability, and price is on par for class.
Cons: Limited expansion options, limited storage, and service-removable battery ,costly add-ons required for use in environments where WLAN isn’t an option, not well suited to Windows variants beyond XP.
MacBook Pro
Not much new here from the 3G lines, save for the absentkeypad. Base specs were upped by small increments, and dedicated VRAM doubled for all models. Nonetheless, the 4G Pro can make a capable,if not solid gaming unit (as if the 3G unit wasn’t competent in its own right). Like the 3G unit, it is also well suited to Vista and its 64-bit variant, and it can easily run Windows 7 in its many forms as well.
Case type: Anodized aluminum composite with plastic edging.
Chipset: Intel GM965
Standard RAM: 2 GB
Maximum RAM: 4.00 GB PC2-5300 DDR2 SDRAM
Pros: Robust graphics, flexible options,and multi-gesture trackpad
Cons: What’s not to like? If you liveor die crunching numbers, it’s tougher, but doable.
Fifth generation (5G)
As is done in every odd generation, Apple reworked the entire line of notebooks from within for the “Late 2008/Early 2009” cycle. In addition, Apple was hard at work on atotally new and totally trend-setting casing process for its portables. The result: an extreme makeover not seen in Apple’s portable lines since the 68K-to-PowerPC transitions of the early 1990’s. To rework the interior of the MacBook family, Apple went to NVIDIA—not Intel—for a high-performance logicsolution to be used in notebooks. NVIDIAwas working on a desktop chipset at the time; but if Steve Jobs’ statement at Apple’s October ‘08 notebook event is to be believed, Apple designers asked NVIDIA to make it mobile, and the company delivered an MCP logic set dubbed“GeForce 9400M” unto Apple. All linesthus benefited from markedly faster graphics and the adoption of ultra-fas tDDR3 memory. Here, the 5G MacBook and 2G MacBook Air became passable all-around units, with the 5G MacBook Pro sportingdynamically switchable graphics engines.
For the exterior makeover, Apple Senior Designer Jon Iverevealed that Apple’s latest process created a “unibody” enclosure that waslighter and required fewer parts to produce, for it was milled entirely fromone sheet of aluminum. To complete themakeover, Apple drew on its experience with the Aluminum line of iMac desktopsand fused all-glass displays into the new assemblies.
For some models, the fifth generation held well into 2010,and so received only incremental upgrades to the CPU, GPU, and system RAM
All models from this generation, save for the whiteMacBook, include a button-less, customizable multi-gesture trackpad.
MacBook and MacBookPro (15”)
Because the two lines had converged in this iteration, only subtle visual differences kept them apart. Both lines dropped the FireWire 400 port and exchanged their respectivevideo outputs for a common Mini DisplayPort, based on an emerging standard. The loss of certain status quofeatures on both lines (FW400 on theMacBook, traditional keyboard on the Pro) drew some whining in certain circles,but such things happen when Apple does this sort of retooling.
With the 5G notebooks, Apple further blurred the line thatonce separated MacBook from MacBook Pro, allowing the former a backlit keyboardin its fullest build. Apple hoped that thiswould swing “fence people” toward the MacBook instead of a low-cost Windows PC since these are folks that would be forced to spend $2,000 on a MacBook Probecause they want to play games in either Mac OS or Windows, casually orotherwise.
Case type: Anodized aluminum unibody
Chipset: NVIDIA GeForce 9400M MCP (withGeForce 9600M GT GPU in Pro models)
Standard RAM: 2 GB (1792 MB usable)
Maximum RAM: 8.00 GB PC3-8500 DDR3 SDRAM( 7936 MB usable)
Pros: Fast graphics, lighter, moredurable, energy efficient, hard drive is user-serviceable, wealth of optionsavailable
Cons: Changes in port makeup require conversion adapters; may frustrate some
MacBook Pro (17”)
At MacWorld Expo ’09, Apple SeniorVice-President Phil Schiller spent more than 90 minutes touting the company’slatest software offerings. In typical Apple style, however, Schiller couldn’t let Apple make what would be its finalcurtain call without a fantastic final act. The 5G-notebook lineup would be rounded out with a stunning revision to one of Apple’s crown jewels: the 17-inch MacBook Pro. Though it’s fundamentally similar to its smaller siblings and received the same makeover from its 4G incarnation that the others received, its battery puts it in a class of its own; Apple claimed not only that the battery will last an unheard-of 8 hours, but also that it would continue to function at nearly 100% potential after 300charge cycles and drop to 80% potential after 1000 cycles, thereby lastingthree times longer than most conventional notebook batteries, including itsown. The reason for this is thebattery’s adaptive charging circuitry, which requests that charge be directedonly to the cells that require it instead of the system charging the battery uniformly across all cells. Real world testing of Apple’s claims yielded figures closer to 5 hours. Still, the fact that the battery is fixed inplace seemed irrelevant. Fixed batteries have been a source of worry for many gadget lovers since the original iPoddebuted in 2001.
Nonetheless, Apple’s flagship retained manyof thee same advantages and disadvantages of its 5G fellows, and yet it remaineda solid machine for those fortunate enough to afford its nearly $3,000 base sticker price. Build-to-order modelsnearly eclipsed the 3 GHz mark—but as Don Adams would have said, missed it by that much.
Case type: Anodized aluminum unibody
Chipset: NVIDIA GeForce 9400M MCP with GeForce 9600M GT GPU
Standard RAM: 2 GB (1792 MB usable)
Maximum RAM: 8.00 GB PC3-8500 DDR3 SDRAM (7936 MB usable)
Pros: Powerful, lighter, more durable,energy efficient, hard drive is user-serviceable, wealth of options available
Cons: Changes in port makeup require conversion adapters; may frustrate some ,expensive entry price, fixed battery
MacBook Air (Second Generation and Third Generation)
How do you improve on the world’s most eye-catching notebook? Apparently, you improve uponit from within, as CEO Jobs outlined during the October event introducing the5G-notebook architecture. Like itsfull-sized siblings, the 2G Air ships with an NVIDIA 9400M MCP and 2 GB of fast DDR3 RAM onboard even as the ultra-low voltage Core2 CPU at its heart has seenonly miniscule improvements in overall clock speed. Hard drive options have seen more modest gains, with the standard drive adding 50% more space than its predecessor and the SSD option doubling to 128 GB. With these adjustments, the Air becomes more palatable to travelers willing toaccept certain tradeoffs in exchange for size and weight. For Windows users under Boot Camp, the Air also becomes a more capable, if still underpowered, Vista unit, albeit one that won’t gain much from an x64-based variant thereof.
Case type: Anodized aluminum unibody
Chipset: NVIDIA GeForce 9400M MCP
Standard RAM: 2 GB onboard (1792 MB usable)
Pros: Size and weight offer maximumportability, big screen and keyboard offer comfort for travelers, multi-gesturetrack pad has large surface for easy usability, and price is on par for class,better storage options than previous model.
Cons: No change in onboard RAM to offset new hardware overhead, add-ons still required where WLAN isn’t available, adapter required for new Mini DisplayPort with most displays
MacBook (’09 White)
A surprise refresh in early 2009 brought an entry-level MacBook under $1,000 with most of the 5G features above. To keep it that affordable, Apple ended up blending a third-gen polycarbonate MacBook exterior with a modified 5G-logicassembly. Users of this model got the same fast graphics engine as the one in the mainstream aluminum MacBooks, all the while keeping the single and now scarce FW400 port; but they also gave up niceties such as the multitouch track pad and the slightly quicker DDR3 RAM. Nonetheless, this 5G model was mostlikely aimed at those looking to start with a Mac and get a full-fledged computer.
Case type: Polycarbonate unibody shell
Chipset: NVIDIA GeForce 9400M MCP
Standard RAM: 2 GB (1792 MB usable)
Maximum RAM: 4 GB (3840 MB usable)
Pros: Solid construction, cheaper than prior models, few if any changes from previous model
Cons: Limited trackpad motion support, RAM capped at 4 GB, looks less classy
Sixth generation (6G)
Perhaps the only generation not to offer a significant step up from the previous one, the sixth generation opened with a minor redesign of the white MacBook, which at long last had caught up with the earliest 5G models and therefore offered a better value than its previousmodel. MacBook Airs also see but a minorspeed bump. True improvement is not achieved until the arrival of the first mobile processors to use the emerging “Nehalem”microarchitecture and to see the return of multithreading support. The processor’s redesign also affords the ability to shut down inactive processor cores whilst boosting the clock speed of those that remain active. Unfortunately, MacBook Pros are the only models to receive this welcome upgrade, even if it only comes in a dual-core package to start with. All other models run on the last knownreleases of the “Penryn” core—a harbinger of things to come, maybe?
MacBook
From Mid 2009 onward, MacBooks continued to shadow their upper-crust siblings, but in the process, they ultimately catch up—to 2008’s lineup. It’s from here that these modelstake a multitouch glass-backed trackpad, a fixed battery, and the Mini DisplayPort monitor connection. A remolded unibody design gives this model a curved front. FireWire finally drops, as does the IR receiver; Apple found that many consumers buying the MacBook just didn’t care for either add-on. Still, subtle bumpsin CPU speed and battery life may have been enough to justify an upgrade from previous generation models.
Case type: Polycarbonate unibody shell
Chipset: NVIDIA GeForce 9400M MCP
Standard RAM: 2 GB (1792 MB usable)
Maximum RAM: 4 GB (3840 MB usable)
Pros: Long battery life, sleeker and slimmer design,slightly lighter
Cons: Almost no change from 5G setup; ports dropped
MacBook Pro (15” and17”)
As mentioned above, the 6G Pro offered little in the way of improvements over the 5G lineup—or so it might seem at first glance. Externally, they appear very much like the 5Gmodels, except that Apple has added an SD card slot to the port array—a big upgrade for camera buffs whom usually resorted to carrying cheap and oft-clunky card readers to dangle from a USB port.
Internally, these two flagship units make several changes to accommodate the Intel “Nehalem” architecture mentioned above. No longer could a third-party chipset be used—the direct result of a protracted battle between Intel and NVIDIA over the terms of the deal that allowed the Core2 to run on a non-Intel logic set. In its place, Intel supplied the “Arrandale” Core i-series multipurpose processors along with the then-new 5 series logic sets. Arrandale brought with it a completely new bus known as QuickPath Interconnect, which in theory was much improved over the traditional front-side bus. Also making their debut were Turbo Boost, which shut down one core and turned up the other based on demand, and the Intel HD Graphics core, a welcome boost over previous Intel offerings that for their part lacked muscle; this new engine could render 720p HD where 2007’s X3100 had to feign it. Last but certainly not least, Hyper Threading Technology, absent since the last of the Pentium 4 600 series CPU’s were cas tin 2006, returns to little fanfare but grants users twice the effective coresduring heavy workload.
Flash storage, introduced on MacBook Airs, makes its way into the mainstream lines with this generation and all that will follow it, though the drives’ expense and potential loss of storage space were not always justifiable, even though flash storage delivers on the promise of improved read/write access speeds.
Despite these huge gains, users anticipating quad-core chips on Macs when high-end Windows notebooks already had such were at the very least disappointed
For the discrete graphics engine, Apple again turned to NVIDIA for its 300-series chips, these being significantly more powerful than the 9-series previously used. Video RAM remained unchanged.
Case type: Anodized aluminum unibody
Chipset: Intel 5 Series/HD Graphics with NVIDIA GT 330M
Standard RAM: 4 GB (3840 MB usable inlow-energy modes)
Maximum RAM: 8.00 GB PC3-8500 DDR3 SDRAM (7936 MB usable in low-energy modes)
Pros: Big lift from i-Series CPU’s, SD cards now usablewithout extra hardware, more starting RAM, SSD options for better performance
Cons: Low-energy modes use a graphics engine that is a drag on gaming for some (per user reports), still dual-core.
Seventh generation (7G)
There may be some discussion as to whether a seventh generation of Mac portables exists, or whether this line should be part of the sixth generation instead. Apple’s internal naming schemes for the mainstream models did indeed point to a seventh generation, so on that basis, here’s a definition: Seventh-gen models were, as the sixth-gen models, a mild refresh. This time, though, the refresh targeted only those models not receivingthe Arrandale i-Series upgrade. All models received the final upgrade of the Penryn Core2’s, as well as replacing NVIDIA’s 9400M MCP with a more robust version in the 320M.
With Windows XP in decline from 2009’s release of Windows 7, this became the last iteration of Mac portables to run the nearly-decade-old platform. Vista, too, would meet its end here, though Microsoft still considers it in mainstream support untilmid-2012. Perhaps Apple wished to streamline their Windows support to a single version—or perhaps it realized what so many others outside of itself knew from experience: Vista was a disaster, and it was best left to rot with its distant ancestor, Windows Me, inthe depths of history’s sewers.
MacBook
The trusty steed of many a cheapskate since its 2006 intro received what would be its last upgrade ever in mid 2010. The Penryn processor gets a slight bump from 2.1 GHz to 2.4 GHz, and NVIDIA 320M graphics round out the package. Otherwise, there’s not much new, for its reign as King of Value would quickly come to a close.
Case type: Polycarbonate unibody shell
Chipset: NVIDIA GeForce 320M MCP
Standard RAM: 2 GB (1792 MB usable)
Maximum RAM: 4 GB (3840 MB usable)
Pros: Modest gains for CPU and GPU—but that’s it
Cons: Still cheap looking with a plastic shell—and you paid WHAT?
MacBook Pro (13”)
Now firmly rebranded as a Pro model, Apple’s 13” aluminum notebook was poised to gain clout with “prosumers” and other types that loved the aluminum look but did not want to pay extra for the new CPU’s of the 15” and 17” models. Still, these units made big gains from the new NVIDIA MCP and Penryn chips up to 2.66 GHz. All in all, this seemed a very well-balanced unit for one a full generation behind its peers, and one that was well worth its $1,200 entry fee
Case type: Anodized aluminum unibody
Chipset: NVIDIA GeForce 320M MCP
Standard RAM: 4 GB (3840 MB usable)
Maximum RAM: 8.00 GB PC3-8500 DDR3 SDRAM (7936 MB usable)
Pros: Full featured for the size, hits a“sweet spot” for the price
Cons: Aging architecture now at limit, no i-Series chips to be found
MacBook Air (Fourth Generation)
The head-turning Air gets a late 2010 all-around makeoverwhile expanding the family of portables to include Apple’s smallest notebook since the 12” PowerBook made a splash in 2003. Even at the new 11.6” size, the Air gets a slightly thicker body than its previous two models. The extra thickness isn’t enough to keep it from being the thinnest, but it is enough to add a much-requested second USB port and to eliminate the clumsy door covering the initial USB port and the video port in addition to exposing the MagSafe connector, making the once-awkward connection more accessible. This also gives it a more rectangular profile in line with Apple’s other models.
The upgraded 13” model doubles onboard flash storage andadds the SD card slot from the MacBook Pros.
Both models now feature factory upgrades to storage andRAM—up to 256 GB and 4GB respectively-- as well as new options from theultra-low-voltage Penryn Core2’s. Bothmodels also benefitted from NVIDIA’s 320M MCP Starting at 1.4 GHz with 64 GB ofstorage and 2 GB RAM for $999, the MacBook Air slowly began to earn its place as the value leader, costing just as much as the venerable white MacBook. Even so, with so many options for this model,there was something to fit every budget.
These models are the first to carry a specific OS requirement when running Boot Camp, despite running Snow Leopard as previous models can. Windows 7 is a must, though one would be hard-pressed trying to squeeze it into a minimally configured 11” unit
Case type: Anodized aluminum unibody
Chipset: NVIDIA GeForce 320M MCP
Standard RAM: 2 GB (1792 MB usable)
Maximum RAM: 4 GB (3840 MB usable)
Pros: Still thin and light, wealth of options available,extra USB port, ports much more accessible
Cons: Options fixed at time of order, Boot Camp needs toospecific for some users
What About Sandy Bridge?
As of February 2011, Apple was one of the first manufacturers to introduce Intel’s Sandy Bridge platform to the world, ushering in the eighth and current generation of portable Macs. With this generation, quad-core, eight-thread i-Series CPU’s are a staple of the 15” and 17” high end, while dual-core ,quad-thread models still populate the lower end. Nonetheless, all models now benefit from the same new technology with none fully ahead of or behind the others.
All models also feature a breakthrough in peripheralconnectivity that combines bandwidths of both PCI Express and DisplayPort intoa bus markedly faster than any bus presently in use. Christened “Thunderbolt”, the new interface offers enormous potential with its theoretical 10 gigabit-per-second bandwidth. However, devices using Thunderbolt are only beginning to emerge on the market,thus it is still too early to offer any concrete opinion regarding thistechnology.
As these models are currently on sale (and have recentlybeen updated) at the Apple Store and Apple Authorized Resellers worldwide, to proffer any opinion of current models defeats the purpose of this, anhistorical document of Mac portable evolution.
Conclusion and Final Thoughts
To have witnessed and tracked the evolution of Apple’snotebook lines from 2006 to the present is no small feat. One could say that doing so is in fact opening a window on the history of Apple itself, for it is in Apple’s notebooks that we have seen the greatest innovations both from the company and in computing itself. From their inceptionin 2006, Apple’s Intel notebooks have evolved into some of the best and mostreliable notebooks on the market today. To be able to run Windows as well asthe Mac OS only solidifies that position.
Yet, with each stage of their evolution, the MacBook, MacBookPro and MacBook Air, while they have made significant forward progress, havehad to sacrifice features that some users find essential. Still, while the complaints roll in with each generation of notebooks, time must march on. Apple is a computer company after all, and must continually update its wares if it is to remain in its current position near the top of the industryat large.
The stark realities of Apple’s business, however, should never be used as an excuse to buy the latest and greatest hardware even if yours seems less capable than someone else’s. Holding onto older Apple hardware may actually put you at an advantage, since you may still be able to work with hardware that newer models don’tsupport. This is one of many reasons Macs tend to stick around longer than most Windows PCs.
I certainly hope you have enjoyed this look back at Apple’s Intel notebook lines. As a proudmember of the Mac community for almost eight years and a volunteer whose role connects him to computing past, I find this knowledge of the past fascinating; and yet it is vital to maintain such a background, as it can give us as users an idea of where the industry will be in the months and years to come.Due to a copy/paste glitch, some necessary spaces have inadvertently been removed. If I could fix this, I would.
-
Using Dell Latitude D630 with Intel 965 Express Chipset with Adobe CS6 Photoshop 3D features
Hello,
Here is my configuration:
- I am using Windows 7, 4-bit OS
- Dell Latitude D630, which comes with Intel Mobile 965 Express Chipset and Accelleration Drivers.
- If I press CTRL-ALT-F12, I can see the Intel Graphics Media Acccelerator Driver GUI. There are 3D settings
configuration, which are labelled with OpenGL, and a bunch of values that can flipped on and off. So, I have some
warm fuzzy that OpenGL is enabled on my systme.
- When I look at the details of the driver, it says 9/23/2009, driver version 8.15.10.1930. If I attempt to update
driver, and select search automatically, "Windows determined the driver software for your device is up to date".
So, this gives me some warm fuzzy that I'm on the latest driver.
When I open up PhotoShop CS6, and click on Edit->Preferences->Performance, Detected Graphics processor
is grayed out and I am told that I need to upgrade either my driver or my card. Well, I'm on a laptop so that might
be an issue.
My driver seems to support OpenGL, so is there some configuration thing I can do to get Photoshop to recognize my
video accelerator to make this work? Or am I out of luck with using 3D and accelerated features with this laptop?I did try to go through the Intel driver upgrade process.
Visited http://www.intel.com/p/en_US/support/detect?iid=dc_iduu (Intel Driver update Utility) with IE.
Detected my graphics drivers and indicated that:
Product Detected
Intel® GM965
Current Driver Installed
8.15.10.1930
Your driver is current.
So, nothing useful there. What I find puzzling is the when I hit CTRL-ALT-F12 and click on 3D settings, there
are plenty of configuraiton choices for OpenGL, with many settings being Off. So, I was hoping that either (a)
there is some combination of choices with these OpenGL options to enable enough of it so that Photoshop CS6 3D features
would work, or (b) maybe registry settings to hack at to "enable" OpenGL or some way of getting Adobe software to try to
rediscover the accelleration support once I change the settings. -
Locked out of my user account - can anyone help please!?
Hi all
I have a rather annoying issue that only happened a few hours ago and I have come here to ask for help if I may because I do not have the experience to resolve it on my own.
Here goes.. Using my 2009 mbp, running snow leopard 10.6, computer hangs with spinning ball, try to shutdown and it just hangs. So I shutdown with the power button and when I power up I find I cannot access my standard user account with everything in it - I get a message saying " cannot access account at this time due to an error" .
The mbp I'm using has two drives : one intel ssd for osx and program's and a hitachi hdd for storage. The hitachi drive is in a caddy in the place of the SuperDrive and the SuperDrive is now in an external enclosure and the intel ssd in the hard drive bay.
Things I have tried :
I have booted in safe mode - same error message.
Cleared PRAM - same error message.
Booted from system disc and tried to reset password - same error message.
Ran disc utility from cd and I see that the hitachi hdd is not mounted - it will not let me mount the volume, first aid sees that it's still alive but that's all it will do.
The intel ssd checks out just fine in disc utility first aid - I repaired permissions.
I suspect the hitachi hdd is at fault but would really like someone's educated opinion if that's ok? As all my data is on it and stupidly I have not backed all of it up.
I am having to send this from my iPhone !
Many thanks
DavidIt sounds like the Hitachi with your home folder may have died or become problematic, in one way or another. This won't solve that problem, but it may help to get you to be able to at least log in. These instructions are for resetting a password with a CD, not your issue, but it will allow you to create a new admin account, so at least you will be able to login. Not sure what will solve the problem with the Hitachi, if it won't mount because, for all intents and purposes, it's dead. If that's the case--and can't be certain it is--you might need some kind of recovery software. (Google that for Mac. There are many available programs.) That booting in Safe Mode doesn't fix the issue is not a good sign.
Make certain you give this new account admin privileges.
Reset Mac Password – without a CD or Boot Drive
reset mac password Using a pretty nifty trick you can reset a forgotten Mac password without a Mac OS X installer CD/DVD or any kind of boot drive or recovery partiton, and without having an Apple ID. This is basically the be-all-end-all approach if nothing else works, because it’s guaranteed to get you back into a Mac when the other options are available, and it works in literally all versions of OS X. The steps may seem a little intimidating at first but I assure you it’s easy if you follow them exactly, here is exactly how to do this in three stages:
Stage 1) Boot into Single User Mode and remove a setup file
Restart the Mac holding down the Command+S keys, this will take you into Single User Mode and it’s Terminal interface
You’ll need to check the filesystem first:
fsck -fy
Next, you must mount the root drive as writeable so that changes will save:
mount -uw /
Now, type the following command exactly, followed by the enter key:
rm /var/db/.applesetupdone
reset forgot mac password
After removing the applesetupdone file, you need to reboot, type ‘reboot’ and hit enter
Stage 2) Create a New User Account upon System Boot
You aren’t finished, but the hard part is now over – no more command lines, you’ll now be in the familiar Mac OS X GUI to finish the password reset process. In this step we just create a new user account as if you just got a new Mac:
Upon reboot, you will be presented with the traditional “Welcome Wizard” startup screen just like when you first get a Mac
Follow the welcome wizard and create a new user account – making the account name different from the account whose password you want to recover
Continue on and boot into Mac OS X with this newly created user account, this new user account is an Administrator and has administrative access
http://osxdaily.com/2010/08/10/forgot-mac-password-how-to-reset-mac-password/ -
Problem with 3 monitors Intel HD Graphics and GeForce GTX 560
I would like to attach 3 monitors to my box -- 1 to integrated Intel card and 2 to discreet Nvidia. I've tried different configs but I failed to make monitors connected to different cards to work at the same time. I have system with stock kernel, latest updates and the following configuration:
$ lspci | egrep "VGA|Disp"
00:02.0 Display controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1)
$ pacman -Qi xorg-server xf86-video-intel nvidia awesome-git linux | egrep "Name|Version"
Name : xorg-server
Version : 1.17.1-3
Name : xf86-video-intel
Version : 2.99.917-3
Name : nvidia
Version : 346.47-3
Name : awesome-git
Version : 3.5.2.397.gdde5b1b-1
Name : linux
Version : 3.18.6-1
$ lsmod | egrep 'i915|nvidia'
nvidia 8335766 46
i915 946695 2
button 12953 1 i915
i2c_algo_bit 12744 1 i915
video 18043 2 i915,asus_wmi
drm_kms_helper 80985 1 i915
drm 263481 7 i915,drm_kms_helper,nvidia
i2c_core 50152 6
drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,nvidia
intel_gtt 17848 2 i915,intel_agp
I've tried different xorg configs. Here is the best one. All 3 monitors are active with it (I could drag cursor over them) but only 2 (which connected to nvidia card) display DE.
Section "DRI"
Mode 0666
EndSection
Section "Monitor"
Identifier "SAM"
ModelName "Samsung SMS27A850"
HorizSync 30.0 - 90.0
VertRefresh 56.0 - 75.0
Option "DPMS"
DisplaySize 597 336 # In millimeters
EndSection
Section "Monitor"
Identifier "VS"
ModelName "ViewSonic VG1930wm"
Option "DPMS"
Option "RightOf" "SAM"
Option "Rotate" "left"
EndSection
Section "Monitor"
Identifier "BNQ"
ModelName "BenQ FP737s"
Option "DPMS"
Option "LeftOf" "SAM"
Option "Rotate" "left"
EndSection
Section "Device"
Identifier "nvidia"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 560 Ti"
BusID "01:00:0"
Option "Monitor-DVI-I-1" "SAM"
Option "Monitor-DVI-I-2" "VS"
EndSection
Section "Device"
Identifier "intel"
Driver "intel"
Option "AccelMethod" "none"
VendorName "Intel"
BoardName "Intel Integrated Graphic Controller"
BusID "00:02:0"
Option "Monitor-VGA-0" "BNQ"
EndSection
Section "Screen"
Identifier "SAM-Screen"
Device "nvidia"
Monitor "SAM"
EndSection
Section "Screen"
Identifier "VS-Screen"
Device "nvidia"
Monitor "VS"
EndSection
Section "Screen"
Identifier "BNQ-Screen"
Device "intel"
Monitor "BNQ"
EndSection
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "SAM-Screen"
Screen 1 "VS-Screen" RightOf "SAM-Screen"
Screen 2 "BNQ-Screen" LeftOf "SAM-Screen"
Option "Xinerama" "0"
EndSection
Also, xrandr shows last monitor (VGA-0, it plugged into Intel card) as disconnected
$ xrandr
Screen 0: minimum 8 x 8, current 3460 x 1440, maximum 16384 x 16384
DVI-I-0 disconnected primary (normal left inverted right x axis y axis)
VGA-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 518mm x 324mm
2560x1440 59.95*+
1920x1200 59.88
1920x1080 60.00 50.00
1680x1050 59.95
1600x1200 60.00
1440x900 59.89
1280x1024 75.02 60.02
1280x960 60.00
1280x800 59.81
1280x720 60.00 50.00
1152x864 75.00
1024x768 75.03 70.07 60.00
800x600 75.00 72.19 60.32 56.25
720x576 50.00
720x480 59.94
640x480 75.00 72.81 59.94
HDMI-0 disconnected (normal left inverted right x axis y axis)
DVI-I-2 connected 900x1440+2560+0 left (normal left inverted right x axis y axis) 410mm x 256mm
1440x900 59.89*+ 74.98
1280x1024 75.02 60.02
1280x960 60.00
1152x864 75.00
1024x768 75.03 70.07 60.00
800x600 75.00 72.19 60.32 56.25
640x480 75.00 72.81 59.94
640x400 70.10
But it's still posible to start application on last monitor with 'env DISPLAY:=0.1 urxvt'
Here is full Xorg log file and highlights:
[ 4789.920] (EE) intel(1): Cannot position output VGA1 relative to unknown output SAM
[ 4792.053] (EE) intel(G0): [drm] failed to set drm interface version: Permission denied [13].
[ 4792.053] (II) intel(G0): [drm] Contents of '/sys/kernel/debug/dri/0/clients':
[ 4792.053] (II) intel(G0): [drm] command pid dev master a uid magic
[ 4792.053] (II) intel(G0): [drm] Xorg 10086 0 y y 0 0
[ 4792.053] (II) intel(G0): [drm] Xorg 10086 0 n y 0 0
[ 4792.053] (EE) intel(G0): Failed to claim DRM device.
[ 4792.053] (II) UnloadModule: "intel"
[ 4789.342]
X.Org X Server 1.17.1
Release Date: 2015-02-10
[ 4789.342] X Protocol Version 11, Revision 0
[ 4789.342] Build Operating System: Linux 3.18.6-1-ARCH x86_64
[ 4789.342] Current Operating System: Linux earth 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015 x86_64
[ 4789.342] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=dc49b07c-e67c-4b6f-91f7-7c1adc050e21 rw quiet ipv6.disable=1 init=/usr/lib/systemd/systemd security=tomoyo TOMOYO_trigger=/usr/lib/systemd/systemd
[ 4789.342] Build Date: 22 February 2015 12:50:32PM
[ 4789.342]
[ 4789.342] Current version of pixman: 0.32.6
[ 4789.342] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 4789.342] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 4789.342] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Mar 1 14:43:55 2015
[ 4789.342] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 4789.342] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 4789.342] (==) ServerLayout "Layout0"
[ 4789.342] (**) |-->Screen "SAM-Screen" (0)
[ 4789.342] (**) | |-->Monitor "SAM"
[ 4789.343] (**) | |-->Device "nvidia"
[ 4789.343] (**) |-->Screen "VS-Screen" (1)
[ 4789.343] (**) | |-->Monitor "VS"
[ 4789.343] (**) | |-->Device "nvidia"
[ 4789.343] (**) |-->Screen "BNQ-Screen" (2)
[ 4789.343] (**) | |-->Monitor "BNQ"
[ 4789.343] (**) | |-->Device "intel"
[ 4789.343] (**) Option "Xinerama" "0"
[ 4789.343] (==) Automatically adding devices
[ 4789.343] (==) Automatically enabling devices
[ 4789.343] (==) Automatically adding GPU devices
[ 4789.343] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 4789.343] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 4789.343] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 4789.343] (II) Loader magic: 0x815d80
[ 4789.343] (II) Module ABI versions:
[ 4789.343] X.Org ANSI C Emulation: 0.4
[ 4789.343] X.Org Video Driver: 19.0
[ 4789.343] X.Org XInput driver : 21.0
[ 4789.343] X.Org Server Extension : 9.0
[ 4789.344] (EE) systemd-logind: failed to get session: PID 10086 does not belong to any known session
[ 4789.345] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 4789.345] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 4789.347] (--) PCI: (0:0:2:0) 8086:0102:1043:84ca rev 9, Mem @ 0xf6400000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64
[ 4789.347] (--) PCI:*(0:1:0:0) 10de:1200:10b0:0401 rev 161, Mem @ 0xf4000000/33554432, 0xe0000000/134217728, 0xe8000000/67108864, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 4789.347] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 4789.347] (II) LoadModule: "glx"
[ 4789.347] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 4789.359] (II) Module glx: vendor="NVIDIA Corporation"
[ 4789.359] compiled for 4.0.2, module version = 1.0.0
[ 4789.359] Module class: X.Org Server Extension
[ 4789.359] (II) NVIDIA GLX Module 346.47 Thu Feb 19 18:09:07 PST 2015
[ 4789.359] (II) LoadModule: "nvidia"
[ 4789.359] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 4789.360] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 4789.360] compiled for 4.0.2, module version = 1.0.0
[ 4789.360] Module class: X.Org Video Driver
[ 4789.360] (II) LoadModule: "intel"
[ 4789.360] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 4789.360] (II) Module intel: vendor="X.Org Foundation"
[ 4789.360] compiled for 1.17.1, module version = 2.99.917
[ 4789.360] Module class: X.Org Video Driver
[ 4789.360] ABI class: X.Org Video Driver, version 19.0
[ 4789.360] (II) NVIDIA dlloader X Driver 346.47 Thu Feb 19 17:47:18 PST 2015
[ 4789.360] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 4789.360] (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
[ 4789.360] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
[ 4789.360] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
[ 4789.360] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300
[ 4789.360] (++) using VT number 7
[ 4789.471] (II) Loading sub module "fb"
[ 4789.471] (II) LoadModule: "fb"
[ 4789.471] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 4789.471] (II) Module fb: vendor="X.Org Foundation"
[ 4789.471] compiled for 1.17.1, module version = 1.0.0
[ 4789.471] ABI class: X.Org ANSI C Emulation, version 0.4
[ 4789.472] (II) Loading sub module "wfb"
[ 4789.472] (II) LoadModule: "wfb"
[ 4789.472] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 4789.472] (II) Module wfb: vendor="X.Org Foundation"
[ 4789.472] compiled for 1.17.1, module version = 1.0.0
[ 4789.472] ABI class: X.Org ANSI C Emulation, version 0.4
[ 4789.472] (II) Loading sub module "ramdac"
[ 4789.472] (II) LoadModule: "ramdac"
[ 4789.472] (II) Module "ramdac" already built-in
[ 4789.473] (II) intel(1): Using Kernel Mode Setting driver: i915, version 1.6.0 20140905
[ 4789.474] (II) intel(G0): Using Kernel Mode Setting driver: i915, version 1.6.0 20140905
[ 4789.474] (II) NVIDIA(0): Creating default Display subsection in Screen section
"SAM-Screen" for depth/fbbpp 24/32
[ 4789.474] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 4789.474] (==) NVIDIA(0): RGB weight 888
[ 4789.474] (==) NVIDIA(0): Default visual is TrueColor
[ 4789.474] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 4789.474] (**) NVIDIA(0): Enabling 2D acceleration
[ 4789.841] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20150116)
[ 4789.842] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 560 Ti (GF114) at PCI:1:0:0 (GPU-0)
[ 4789.842] (--) NVIDIA(0): Memory: 1048576 kBytes
[ 4789.842] (--) NVIDIA(0): VideoBIOS: 70.24.21.00.00
[ 4789.842] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 4789.875] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 560 Ti at PCI:1:0:0
[ 4789.875] (--) NVIDIA(0): CRT-0
[ 4789.875] (--) NVIDIA(0): CRT-1
[ 4789.875] (--) NVIDIA(0): Samsung SMS27A850 (DFP-0) (boot, connected)
[ 4789.875] (--) NVIDIA(0): DFP-1
[ 4789.875] (--) NVIDIA(0): ViewSonic VG1930wm (DFP-2) (connected)
[ 4789.875] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[ 4789.875] (--) NVIDIA(GPU-0): CRT-1: 400.0 MHz maximum pixel clock
[ 4789.875] (--) NVIDIA(0): Samsung SMS27A850 (DFP-0): Internal TMDS
[ 4789.875] (--) NVIDIA(GPU-0): Samsung SMS27A850 (DFP-0): 330.0 MHz maximum pixel clock
[ 4789.875] (--) NVIDIA(0): DFP-1: Internal TMDS
[ 4789.875] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[ 4789.875] (--) NVIDIA(0): ViewSonic VG1930wm (DFP-2): Internal TMDS
[ 4789.875] (--) NVIDIA(GPU-0): ViewSonic VG1930wm (DFP-2): 330.0 MHz maximum pixel clock
[ 4789.875] (**) NVIDIA(0): Option "Rotate" "left"
[ 4789.875] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4789.875] (**) NVIDIA(0): device Samsung SMS27A850 (DFP-0) (Using EDID frequencies
[ 4789.875] (**) NVIDIA(0): has been enabled on all display devices.)
[ 4789.875] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4789.875] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
[ 4789.875] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4789.875] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4789.875] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
[ 4789.876] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4789.876] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
[ 4789.876] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4789.876] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4789.876] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
[ 4789.876] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4789.876] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
[ 4789.876] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4789.876] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4789.876] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
[ 4789.877] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4789.877] (**) NVIDIA(0): device ViewSonic VG1930wm (DFP-2) (Using EDID frequencies
[ 4789.877] (**) NVIDIA(0): has been enabled on all display devices.)
[ 4789.878] (==) NVIDIA(0):
[ 4789.878] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 4789.878] (==) NVIDIA(0): will be used as the requested mode.
[ 4789.878] (==) NVIDIA(0):
[ 4789.878] (II) NVIDIA(0): Validated MetaModes:
[ 4789.878] (II) NVIDIA(0):
[ 4789.878] (II) NVIDIA(0): "DFP-0:nvidia-auto-select,DFP-2:nvidia-auto-select{Rotation=90}"
[ 4789.878] (II) NVIDIA(0): Virtual screen size determined to be 3460 x 1440
[ 4789.905] (--) NVIDIA(0): DPI set to (125, 114); computed from "UseEdidDpi" X config
[ 4789.905] (--) NVIDIA(0): option
[ 4789.906] (--) intel(1): Integrated Graphics Chipset: Intel(R) HD Graphics 2000
[ 4789.906] (--) intel(1): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx
[ 4789.906] (II) intel(1): Creating default Display subsection in Screen section
"BNQ-Screen" for depth/fbbpp 24/32
[ 4789.906] (==) intel(1): Depth 24, (--) framebuffer bpp 32
[ 4789.906] (==) intel(1): RGB weight 888
[ 4789.906] (==) intel(1): Default visual is TrueColor
[ 4789.906] (**) intel(1): Option "AccelMethod" "none"
[ 4789.906] (II) intel(1): Output VGA1 using monitor section BNQ
[ 4789.906] (**) intel(1): Option "LeftOf" "SAM"
[ 4789.906] (**) intel(1): Option "Rotate" "left"
[ 4789.906] (II) intel(1): Enabled output VGA1
[ 4789.906] (II) intel(1): Output HDMI1 has no monitor section
[ 4789.906] (II) intel(1): Enabled output HDMI1
[ 4789.906] (II) intel(1): Output DP1 has no monitor section
[ 4789.906] (II) intel(1): Enabled output DP1
[ 4789.906] (II) intel(1): Output HDMI2 has no monitor section
[ 4789.906] (II) intel(1): Enabled output HDMI2
[ 4789.906] (II) intel(1): Output HDMI3 has no monitor section
[ 4789.906] (II) intel(1): Enabled output HDMI3
[ 4789.906] (II) intel(1): Output DP2 has no monitor section
[ 4789.906] (II) intel(1): Enabled output DP2
[ 4789.906] (II) intel(1): Output DP3 has no monitor section
[ 4789.906] (II) intel(1): Enabled output DP3
[ 4789.906] (--) intel(1): Using a maximum size of 256x256 for hardware cursors
[ 4789.906] (II) intel(1): Output VIRTUAL1 has no monitor section
[ 4789.906] (II) intel(1): Enabled output VIRTUAL1
[ 4789.906] (II) intel(1): EDID for output DP1
[ 4789.906] (II) intel(1): EDID for output DP2
[ 4789.906] (II) intel(1): EDID for output DP3
[ 4789.906] (II) intel(1): EDID for output HDMI1
[ 4789.906] (II) intel(1): EDID for output HDMI2
[ 4789.907] (II) intel(1): EDID for output HDMI3
[ 4789.920] (II) intel(1): EDID for output VGA1
[ 4789.920] (II) intel(1): Manufacturer: BNQ Model: 7659 Serial#: 28
[ 4789.920] (II) intel(1): Year: 2003 Week: 39
[ 4789.920] (II) intel(1): EDID Version: 1.3
[ 4789.920] (II) intel(1): Analog Display Input, Input Voltage Level: 0.700/0.700 V
[ 4789.920] (II) intel(1): Sync: Separate Composite
[ 4789.920] (II) intel(1): Max Image Size [cm]: horiz.: 34 vert.: 27
[ 4789.920] (II) intel(1): Gamma: 2.20
[ 4789.920] (II) intel(1): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
[ 4789.920] (II) intel(1): First detailed timing is preferred mode
[ 4789.920] (II) intel(1): redX: 0.640 redY: 0.340 greenX: 0.290 greenY: 0.611
[ 4789.920] (II) intel(1): blueX: 0.140 blueY: 0.069 whiteX: 0.310 whiteY: 0.330
[ 4789.920] (II) intel(1): Supported established timings:
[ 4789.920] (II) intel(1): 720x400@70Hz
[ 4789.920] (II) intel(1): 640x480@60Hz
[ 4789.920] (II) intel(1): 640x480@67Hz
[ 4789.920] (II) intel(1): 640x480@72Hz
[ 4789.920] (II) intel(1): 640x480@75Hz
[ 4789.920] (II) intel(1): 800x600@56Hz
[ 4789.920] (II) intel(1): 800x600@60Hz
[ 4789.920] (II) intel(1): 800x600@72Hz
[ 4789.920] (II) intel(1): 800x600@75Hz
[ 4789.920] (II) intel(1): 832x624@75Hz
[ 4789.920] (II) intel(1): 1024x768@60Hz
[ 4789.920] (II) intel(1): 1024x768@70Hz
[ 4789.920] (II) intel(1): 1024x768@75Hz
[ 4789.920] (II) intel(1): 1280x1024@75Hz
[ 4789.920] (II) intel(1): 1152x864@75Hz
[ 4789.920] (II) intel(1): Manufacturer's mask: 0
[ 4789.920] (II) intel(1): Supported standard timings:
[ 4789.920] (II) intel(1): #0: hsize: 1152 vsize 864 refresh: 75 vid: 20337
[ 4789.920] (II) intel(1): #1: hsize: 1280 vsize 1024 refresh: 76 vid: 36993
[ 4789.920] (II) intel(1): #2: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 4789.920] (II) intel(1): #3: hsize: 1280 vsize 1024 refresh: 72 vid: 35969
[ 4789.920] (II) intel(1): Supported detailed timing:
[ 4789.920] (II) intel(1): clock: 108.0 MHz Image Size: 338 x 270 mm
[ 4789.920] (II) intel(1): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0
[ 4789.920] (II) intel(1): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0
[ 4789.920] (II) intel(1): Supported detailed timing:
[ 4789.920] (II) intel(1): clock: 25.2 MHz Image Size: 304 x 228 mm
[ 4789.920] (II) intel(1): h_active: 640 h_sync: 656 h_sync_end 752 h_blank_end 800 h_border: 0
[ 4789.920] (II) intel(1): v_active: 350 v_sync: 387 v_sync_end 389 v_blanking: 449 v_border: 0
[ 4789.920] (II) intel(1): Ranges: V min: 56 V max: 75 Hz, H min: 31 H max: 81 kHz, PixClock max 145 MHz
[ 4789.920] (II) intel(1): Monitor name: BenQ FP737s
[ 4789.920] (II) intel(1): EDID (in hex):
[ 4789.920] (II) intel(1): 00ffffffffffff0009d159761c000000
[ 4789.920] (II) intel(1): 270d01036c221b78eac6f6a3574a9c23
[ 4789.920] (II) intel(1): 114f54bfef80714f81908180818c0101
[ 4789.920] (II) intel(1): 010101010101302a009851002a403070
[ 4789.920] (II) intel(1): 1300520e1100001ed50980a0205e6310
[ 4789.920] (II) intel(1): 1060520830e41000001a000000fd0038
[ 4789.920] (II) intel(1): 4b1f510e000a202020202020000000fc
[ 4789.920] (II) intel(1): 0042656e51204650373337730a200072
[ 4789.920] (II) intel(1): Printing probed modes for output VGA1
[ 4789.920] (II) intel(1): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
[ 4789.920] (II) intel(1): Modeline "1280x1024"x76.0 141.81 1280 1376 1512 1744 1024 1025 1028 1070 -hsync +vsync (81.3 kHz)
[ 4789.920] (II) intel(1): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 4789.920] (II) intel(1): Modeline "1280x1024"x72.0 132.84 1280 1368 1504 1728 1024 1025 1028 1067 -hsync +vsync (76.9 kHz)
[ 4789.920] (II) intel(1): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 4789.920] (II) intel(1): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[ 4789.920] (II) intel(1): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 4789.920] (II) intel(1): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 4789.920] (II) intel(1): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 4789.920] (II) intel(1): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 4789.920] (II) intel(1): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 4789.920] (II) intel(1): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 4789.920] (II) intel(1): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 4789.920] (II) intel(1): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 4789.920] (II) intel(1): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
[ 4789.920] (II) intel(1): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
[ 4789.920] (II) intel(1): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 4789.920] (II) intel(1): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 4789.920] (II) intel(1): Modeline "640x350"x70.1 25.17 640 656 752 800 350 387 389 449 +hsync -vsync (31.5 kHz e)
[ 4789.920] (II) intel(1): EDID for output VIRTUAL1
[ 4789.920] (II) intel(1): Output DP1 disconnected
[ 4789.920] (II) intel(1): Output DP2 disconnected
[ 4789.920] (II) intel(1): Output DP3 disconnected
[ 4789.920] (II) intel(1): Output HDMI1 disconnected
[ 4789.920] (II) intel(1): Output HDMI2 disconnected
[ 4789.920] (II) intel(1): Output HDMI3 disconnected
[ 4789.920] (II) intel(1): Output VGA1 connected
[ 4789.920] (II) intel(1): Output VIRTUAL1 disconnected
[ 4789.920] (II) intel(1): Using user preference for initial modes
[ 4789.920] (II) intel(1): Output VGA1 using initial mode 1280x1024
[ 4789.920] (EE) intel(1): Cannot position output VGA1 relative to unknown output SAM
[ 4789.920] (II) intel(1): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 4789.920] (==) intel(1): TearFree disabled
[ 4789.920] (==) intel(1): DPI set to (96, 96)
[ 4789.920] (II) Loading sub module "dri2"
[ 4789.920] (II) LoadModule: "dri2"
[ 4789.920] (II) Module "dri2" already built-in
[ 4789.920] (II) Loading sub module "present"
[ 4789.920] (II) LoadModule: "present"
[ 4789.920] (II) Module "present" already built-in
[ 4792.053] (EE) intel(G0): [drm] failed to set drm interface version: Permission denied [13].
[ 4792.053] (II) intel(G0): [drm] Contents of '/sys/kernel/debug/dri/0/clients':
[ 4792.053] (II) intel(G0): [drm] command pid dev master a uid magic
[ 4792.053] (II) intel(G0): [drm] Xorg 10086 0 y y 0 0
[ 4792.053] (II) intel(G0): [drm] Xorg 10086 0 n y 0 0
[ 4792.053] (EE) intel(G0): Failed to claim DRM device.
[ 4792.053] (II) UnloadModule: "intel"
[ 4792.053] (--) Depth 24 pixmap format is 32 bpp
[ 4792.053] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 4792.053] (II) NVIDIA: access.
[ 4792.057] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 4792.057] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 4792.057] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 4792.057] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 4792.057] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 4792.057] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 4792.057] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 4792.057] (II) NVIDIA(0): Config Options in the README.
[ 4792.091] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select,DFP-2:nvidia-auto-select{Rotation=90}"
[ 4792.264] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 4792.264] (==) NVIDIA(0): Backing store enabled
[ 4792.264] (==) NVIDIA(0): Silken mouse enabled
[ 4792.264] (**) NVIDIA(0): DPMS enabled
[ 4792.264] (II) Loading sub module "dri2"
[ 4792.264] (II) LoadModule: "dri2"
[ 4792.264] (II) Module "dri2" already built-in
[ 4792.264] (II) NVIDIA(0): [DRI2] Setup complete
[ 4792.264] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 4792.264] (--) RandR disabled
[ 4792.264] (II) intel(1): SNA initialized with disabled backend
[ 4792.264] (==) intel(1): Backing store enabled
[ 4792.264] (==) intel(1): Silken mouse enabled
[ 4792.264] (II) intel(1): HW Cursor enabled
[ 4792.264] (II) intel(1): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 4792.264] (**) intel(1): DPMS enabled
[ 4792.264] (==) intel(1): display hotplug detection enabled
[ 4792.264] (II) intel(1): Textured video not supported on this hardware
[ 4792.264] (WW) intel(1): loading DRI2 whilst the GPU is wedged.
[ 4792.264] (II) intel(1): [DRI2] Setup complete
[ 4792.264] (II) intel(1): [DRI2] DRI driver: i965
[ 4792.264] (II) intel(1): [DRI2] VDPAU driver: i965
[ 4792.264] (II) intel(1): direct rendering: DRI2 enabled
[ 4792.265] (II) intel(1): hardware support for Present enabled
[ 4792.265] (WW) intel(1): Option "Monitor-VGA-0" is not used
[ 4792.265] (WW) intel(1): Option "LeftOf" is not used
[ 4792.265] (WW) intel(1): Option "Rotate" is not used
[ 4792.265] (--) RandR disabled
[ 4792.268] (II) Initializing extension GLX
[ 4792.268] (II) Indirect GLX disabled.(II) intel(1): switch to mode [email protected] on VGA1 using pipe 0, position (0, 0), rotation left, reflection none
[ 4792.332] (II) intel(1): Setting screen physical size to 270 x 338
[ 4792.386] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 4792.386] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 4792.386] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[ 4792.386] (**) Power Button: Applying InputClass "system-keyboard"
[ 4792.386] (II) LoadModule: "libinput"
[ 4792.386] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[ 4792.387] (II) Module libinput: vendor="X.Org Foundation"
[ 4792.387] compiled for 1.17.1, module version = 0.7.0
[ 4792.387] Module class: X.Org XInput Driver
[ 4792.387] ABI class: X.Org XInput driver, version 21.0
[ 4792.387] (II) Using input driver 'libinput' for 'Power Button'
[ 4792.387] (**) Power Button: always reports core events
[ 4792.387] (**) Option "Device" "/dev/input/event2"
[ 4792.387] (II) input device 'Power Button', /dev/input/event2 is tagged by udev as: Keyboard
[ 4792.387] (II) input device 'Power Button', /dev/input/event2 is a keyboard
[ 4792.399] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
[ 4792.399] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 4792.399] (**) Option "xkb_model" "pc104"
[ 4792.399] (**) Option "xkb_layout" "us,ru"
[ 4792.399] (**) Option "xkb_options" "caps:swapescape,grp:toggle"
[ 4792.432] (II) input device 'Power Button', /dev/input/event2 is tagged by udev as: Keyboard
[ 4792.432] (II) input device 'Power Button', /dev/input/event2 is a keyboard
[ 4792.432] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 4792.432] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 4792.432] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[ 4792.432] (**) Power Button: Applying InputClass "system-keyboard"
[ 4792.432] (II) Using input driver 'libinput' for 'Power Button'
[ 4792.432] (**) Power Button: always reports core events
[ 4792.432] (**) Option "Device" "/dev/input/event1"
[ 4792.433] (II) input device 'Power Button', /dev/input/event1 is tagged by udev as: Keyboard
[ 4792.433] (II) input device 'Power Button', /dev/input/event1 is a keyboard
[ 4792.489] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1/event1"
[ 4792.489] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 4792.489] (**) Option "xkb_model" "pc104"
[ 4792.489] (**) Option "xkb_layout" "us,ru"
[ 4792.489] (**) Option "xkb_options" "caps:swapescape,grp:toggle"
[ 4792.490] (II) input device 'Power Button', /dev/input/event1 is tagged by udev as: Keyboard
[ 4792.490] (II) input device 'Power Button', /dev/input/event1 is a keyboard
[ 4792.490] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event0)
[ 4792.490] (II) No input driver specified, ignoring this device.
[ 4792.490] (II) This device may have been added with another device file.
[ 4792.490] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event17)
[ 4792.490] (II) No input driver specified, ignoring this device.
[ 4792.490] (II) This device may have been added with another device file.
[ 4792.490] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event18)
[ 4792.490] (II) No input driver specified, ignoring this device.
[ 4792.490] (II) This device may have been added with another device file.
[ 4792.491] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event19)
[ 4792.491] (II) No input driver specified, ignoring this device.
[ 4792.491] (II) This device may have been added with another device file.
[ 4792.491] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/event3)
[ 4792.491] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "evdev keyboard catchall"
[ 4792.491] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "libinput keyboard catchall"
[ 4792.491] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "system-keyboard"
[ 4792.491] (II) Using input driver 'libinput' for 'Microsoft Microsoft® 2.4GHz Transceiver v8.0'
[ 4792.491] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: always reports core events
[ 4792.491] (**) Option "Device" "/dev/input/event3"
[ 4792.491] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event3 is tagged by udev as: Keyboard
[ 4792.491] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event3 is a keyboard
[ 4792.554] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:045E:07B2.0004/input/input24/event3"
[ 4792.554] (II) XINPUT: Adding extended input device "Microsoft Microsoft® 2.4GHz Transceiver v8.0" (type: KEYBOARD, id 8)
[ 4792.554] (**) Option "xkb_model" "pc104"
[ 4792.554] (**) Option "xkb_layout" "us,ru"
[ 4792.554] (**) Option "xkb_options" "caps:swapescape,grp:toggle"
[ 4792.554] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event3 is tagged by udev as: Keyboard
[ 4792.554] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event3 is a keyboard
[ 4792.555] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/event4)
[ 4792.555] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "evdev pointer catchall"
[ 4792.555] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "libinput pointer catchall"
[ 4792.555] (II) Using input driver 'libinput' for 'Microsoft Microsoft® 2.4GHz Transceiver v8.0'
[ 4792.555] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: always reports core events
[ 4792.555] (**) Option "Device" "/dev/input/event4"
[ 4792.555] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event4 is tagged by udev as: Mouse
[ 4792.555] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event4 is a pointer caps
[ 4792.609] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.1/0003:045E:07B2.0005/input/input25/event4"
[ 4792.610] (II) XINPUT: Adding extended input device "Microsoft Microsoft® 2.4GHz Transceiver v8.0" (type: MOUSE, id 9)
[ 4792.610] (**) Option "AccelerationScheme" "none"
[ 4792.610] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: (accel) selected scheme none/0
[ 4792.610] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: (accel) acceleration factor: 2.000
[ 4792.610] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: (accel) acceleration threshold: 4
[ 4792.610] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event4 is tagged by udev as: Mouse
[ 4792.610] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event4 is a pointer caps
[ 4792.610] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/mouse0)
[ 4792.610] (II) No input driver specified, ignoring this device.
[ 4792.610] (II) This device may have been added with another device file.
[ 4792.611] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/event5)
[ 4792.611] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "evdev keyboard catchall"
[ 4792.611] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "joystick catchall"
[ 4792.611] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "libinput keyboard catchall"
[ 4792.611] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "system-keyboard"
[ 4792.611] (II) Using input driver 'libinput' for 'Microsoft Microsoft® 2.4GHz Transceiver v8.0'
[ 4792.611] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: always reports core events
[ 4792.611] (**) Option "Device" "/dev/input/event5"
[ 4792.611] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event5 is tagged by udev as: Keyboard Joystick
[ 4792.611] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event5 is a keyboard
[ 4792.676] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.2/0003:045E:07B2.0006/input/input26/event5"
[ 4792.676] (II) XINPUT: Adding extended input device "Microsoft Microsoft® 2.4GHz Transceiver v8.0" (type: KEYBOARD, id 10)
[ 4792.676] (**) Option "xkb_model" "pc104"
[ 4792.676] (**) Option "xkb_layout" "us,ru"
[ 4792.676] (**) Option "xkb_options" "caps:swapescape,grp:toggle"
[ 4792.676] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event5 is tagged by udev as: Keyboard Joystick
[ 4792.676] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event5 is a keyboard
[ 4792.677] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/js0)
[ 4792.677] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "system-keyboard"
[ 4792.677] (II) No input driver specified, ignoring this device.
[ 4792.677] (II) This device may have been added with another device file.
[ 4792.677] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event7)
[ 4792.677] (II) No input driver specified, ignoring this device.
[ 4792.677] (II) This device may have been added with another device file.
[ 4792.677] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event8)
[ 4792.677] (II) No input driver specified, ignoring this device.
[ 4792.677] (II) This device may have been added with another device file.
[ 4792.677] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event9)
[ 4792.677] (II) No input driver specified, ignoring this device.
[ 4792.677] (II) This device may have been added with another device file.
[ 4792.678] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event10)
[ 4792.678] (II) No input driver specified, ignoring this device.
[ 4792.678] (II) This device may have been added with another device file.
[ 4792.678] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event11)
[ 4792.678] (II) No input driver specified, ignoring this device.
[ 4792.678] (II) This device may have been added with another device file.
[ 4792.678] (II) config/udev: Adding input device HDA Intel PCH Line Out Side (/dev/input/event12)
[ 4792.678] (II) No input driver specified, ignoring this device.
[ 4792.678] (II) This device may have been added with another device file.
[ 4792.678] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event13)
[ 4792.678] (II) No input driver specified, ignoring this device.
[ 4792.678] (II) This device may have been added with another device file.
[ 4792.678] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7 (/dev/input/event14)
[ 4792.678] (II) No input driver specified, ignoring this device.
[ 4792.678] (II) This device may have been added with another device file.
[ 4792.679] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=8 (/dev/input/event15)
[ 4792.679] (II) No input driver specified, ignoring this device.
[ 4792.679] (II) This device may have been added with another device file.
[ 4792.679] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event6)
[ 4792.679] (II) No input driver specified, ignoring this device.
[ 4792.679] (II) This device may have been added with another device file.
[ 4792.679] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event16)
[ 4792.679] (**) Eee PC WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[ 4792.679] (**) Eee PC WMI hotkeys: Applying InputClass "libinput keyboard catchall"
[ 4792.679] (**) Eee PC WMI hotkeys: Applying InputClass "system-keyboard"
[ 4792.679] (II) Using input driver 'libinput' for 'Eee PC WMI hotkeys'
[ 4792.679] (**) Eee PC WMI hotkeys: always reports core events
[ 4792.679] (**) Option "Device" "/dev/input/event16"
[ 4792.679] (II) input device 'Eee PC WMI hotkeys', /dev/input/event16 is tagged by udev as: Keyboard
[ 4792.679] (II) input device 'Eee PC WMI hotkeys', /dev/input/event16 is a keyboard
[ 4792.712] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input19/event16"
[ 4792.712] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 11)
[ 4792.712] (**) Option "xkb_model" "pc104"
[ 4792.713] (**) Option "xkb_layout" "us,ru"
[ 4792.713] (**) Option "xkb_options" "caps:swapescape,grp:toggle"
[ 4792.713] (II) input device 'Eee PC WMI hotkeys', /dev/input/event16 is tagged by udev as: Keyboard
[ 4792.713] (II) input device 'Eee PC WMI hotkeys', /dev/input/event16 is a keyboard
[ 4793.050] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4793.050] (**) NVIDIA(0): device ViewSonic VG1930wm (DFP-2) (Using EDID frequencies
[ 4793.050] (**) NVIDIA(0): has been enabled on all display devices.)
[ 4793.081] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4793.081] (**) NVIDIA(0): device Samsung SMS27A850 (DFP-0) (Using EDID frequencies
[ 4793.081] (**) NVIDIA(0): has been enabled on all display devices.)
[ 4793.081] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4793.081] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
[ 4793.081] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4793.081] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4793.081] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
[ 4793.081] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4793.081] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
[ 4793.081] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4793.081] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4793.081] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
[ 4793.081] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4793.081] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
[ 4793.081] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4793.081] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4793.081] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
[ 4793.129] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4793.129] (**) NVIDIA(0): device ViewSonic VG1930wm (DFP-2) (Using EDID frequencies
[ 4793.129] (**) NVIDIA(0): has been enabled on all display devices.)
[ 4793.160] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4793.160] (**) NVIDIA(0): device Samsung SMS27A850 (DFP-0) (Using EDID frequencies
[ 4793.160] (**) NVIDIA(0): has been enabled on all display devices.)
[ 4793.160] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4793.160] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
[ 4793.160] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4793.160] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4793.160] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
[ 4793.160] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4793.160] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
[ 4793.160] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4793.160] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4793.160] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
[ 4793.160] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4793.160] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
[ 4793.160] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4793.160] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4793.160] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
[ 4793.229] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4793.229] (**) NVIDIA(0): device ViewSonic VG1930wm (DFP-2) (Using EDID frequencies
[ 4793.229] (**) NVIDIA(0): has been enabled on all display devices.)
[ 4793.259] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4793.259] (**) NVIDIA(0): device Samsung SMS27A850 (DFP-0) (Using EDID frequencies
[ 4793.259] (**) NVIDIA(0): has been enabled on all display devices.)
[ 4793.259] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4793.259] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
[ 4793.259] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4793.259] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4793.259] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
[ 4793.259] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4793.259] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
[ 4793.259] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4793.259] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4793.259] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
[ 4793.259] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4793.259] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
[ 4793.259] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4793.259] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4793.259] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
[ 4849.763] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4849.763] (**) NVIDIA(0): device ViewSonic VG1930wm (DFP-2) (Using EDID frequencies
[ 4849.763] (**) NVIDIA(0): has been enabled on all display devices.)
[ 4849.794] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4849.794] (**) NVIDIA(0): device Samsung SMS27A850 (DFP-0) (Using EDID frequencies
[ 4849.794] (**) NVIDIA(0): has been enabled on all display devices.)
[ 4849.794] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4849.794] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
[ 4849.794] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4849.794] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4849.794] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
[ 4849.795] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4849.795] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
[ 4849.795] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4849.795] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4849.795] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
[ 4849.795] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4849.795] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
[ 4849.795] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4849.795] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4849.795] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
I also tried other configs, but neither of them made me happy:
Section "DRI"
Mode 0666
EndSection
Section "Monitor"
Identifier "SAM"
ModelName "Samsung SMS27A850"
HorizSync 30.0 - 90.0
VertRefresh 56.0 - 75.0
Option "DPMS"
DisplaySize 597 336 # In millimeters
EndSection
Section "Monitor"
Identifier "VS"
ModelName "ViewSonic VG1930wm"
Option "DPMS"
Option "RightOf" "SAM"
Option "Rotate" "left"
EndSection
Section "Monitor"
Identifier "BNQ"
ModelName "BenQ FP737s"
Option "DPMS"
Option "LeftOf" "SAM"
Option "Rotate" "left"
EndSection
Section "Device"
Identifier "nvidia-sam"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 560 Ti"
BusID "01:00:0"
Option "Monitor-DVI-I-1" "SAM"
Screen 0
EndSection
Section "Device"
Identifier "nvidia-vs"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 560 Ti"
BusID "01:00:0"
Option "Monitor-DVI-I-2" "VS"
Screen 1
EndSection
Section "Device"
Identifier "intel"
Driver "modesetting"
Option "AccelMethod" "none"
VendorName "Intel"
BoardName "Intel Integrated Graphic Controller"
BusID "00:02:0"
Option "Monitor-VGA-0" "BNQ"
Screen 2
EndSection
Section "Screen"
Identifier "SAM-Screen"
Device "nvidia-sam"
Monitor "SAM"
#DefaultDepth 24
# Option "Stereo" "0"
# Option "SLI" "Off"
# Option "MultiGPU" "Off"
# Option "BaseMosaic" "off"
#Option "AllowEmptyInitialConfiguration"
# SubSection "Display"
# Depth 24
# EndSubSection
EndSection
Section "Screen"
Identifier "VS-Screen"
Device "nvidia-vs"
Monitor "VS"
#DefaultDepth 24
# Option "Stereo" "0"
# Option "SLI" "Off"
# Option "MultiGPU" "Off"
# Option "BaseMosaic" "off"
#Option "AllowEmptyInitialConfiguration"
# SubSection "Display"
# Depth 24
# EndSubSection
EndSection
Section "Screen"
Identifier "BNQ-Screen"
Device "intel"
Monitor "BNQ"
EndSection
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "SAM-Screen"
Screen 1 "VS-Screen" RightOf "SAM-Screen"
Screen 2 "BNQ-Screen" LeftOf "SAM-Screen"
Option "Xinerama" "0"
EndSection
[ 4488.527]
X.Org X Server 1.17.1
Release Date: 2015-02-10
[ 4488.527] X Protocol Version 11, Revision 0
[ 4488.527] Build Operating System: Linux 3.18.6-1-ARCH x86_64
[ 4488.527] Current Operating System: Linux earth 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015 x86_64
[ 4488.527] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=dc49b07c-e67c-4b6f-91f7-7c1adc050e21 rw quiet ipv6.disable=1 init=/usr/lib/systemd/systemd security=tomoyo TOMOYO_trigger=/usr/lib/systemd/systemd
[ 4488.527] Build Date: 22 February 2015 12:50:32PM
[ 4488.527]
[ 4488.527] Current version of pixman: 0.32.6
[ 4488.527] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 4488.527] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 4488.527] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Mar 1 14:38:54 2015
[ 4488.527] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 4488.527] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 4488.528] (==) ServerLayout "Layout0"
[ 4488.528] (**) |-->Screen "SAM-Screen" (0)
[ 4488.528] (**) | |-->Monitor "SAM"
[ 4488.528] (**) | |-->Device "nvidia-sam"
[ 4488.528] (**) |-->Screen "VS-Screen" (1)
[ 4488.528] (**) | |-->Monitor "VS"
[ 4488.528] (**) | |-->Device "nvidia-vs"
[ 4488.528] (**) |-->Screen "BNQ-Screen" (2)
[ 4488.528] (**) | |-->Monitor "BNQ"
[ 4488.528] (**) | |-->Device "intel"
[ 4488.528] (**) Option "Xinerama" "0"
[ 4488.528] (==) Automatically adding devices
[ 4488.528] (==) Automatically enabling devices
[ 4488.528] (==) Automatically adding GPU devices
[ 4488.528] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 4488.528] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 4488.528] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 4488.528] (II) Loader magic: 0x815d80
[ 4488.528] (II) Module ABI versions:
[ 4488.528] X.Org ANSI C Emulation: 0.4
[ 4488.528] X.Org Video Driver: 19.0
[ 4488.528] X.Org XInput driver : 21.0
[ 4488.528] X.Org Server Extension : 9.0
[ 4488.529] (EE) systemd-logind: failed to get session: PID 32224 does not belong to any known session
[ 4488.530] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 4488.530] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 4488.531] (--) PCI: (0:0:2:0) 8086:0102:1043:84ca rev 9, Mem @ 0xf6400000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64
[ 4488.531] (--) PCI:*(0:1:0:0) 10de:1200:10b0:0401 rev 161, Mem @ 0xf4000000/33554432, 0xe0000000/134217728, 0xe8000000/67108864, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 4488.531] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 4488.531] (II) LoadModule: "glx"
[ 4488.531] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 4488.542] (II) Module glx: vendor="NVIDIA Corporation"
[ 4488.542] compiled for 4.0.2, module version = 1.0.0
[ 4488.542] Module class: X.Org Server Extension
[ 4488.542] (II) NVIDIA GLX Module 346.47 Thu Feb 19 18:09:07 PST 2015
[ 4488.542] (II) LoadModule: "nvidia"
[ 4488.542] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 4488.543] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 4488.543] compiled for 4.0.2, module version = 1.0.0
[ 4488.543] Module class: X.Org Video Driver
[ 4488.543] (II) LoadModule: "modesetting"
[ 4488.543] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 4488.543] (II) Module modesetting: vendor="X.Org Foundation"
[ 4488.543] compiled for 1.17.1, module version = 1.17.1
[ 4488.543] Module class: X.Org Video Driver
[ 4488.543] ABI class: X.Org Video Driver, version 19.0
[ 4488.543] (II) NVIDIA dlloader X Driver 346.47 Thu Feb 19 17:47:18 PST 2015
[ 4488.543] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 4488.543] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 4488.543] (++) using VT number 7
[ 4488.645] (II) Loading sub module "fb"
[ 4488.645] (II) LoadModule: "fb"
[ 4488.645] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 4488.645] (II) Module fb: vendor="X.Org Foundation"
[ 4488.646] compiled for 1.17.1, module version = 1.0.0
[ 4488.646] ABI class: X.Org ANSI C Emulation, version 0.4
[ 4488.646] (II) Loading sub module "wfb"
[ 4488.646] (II) LoadModule: "wfb"
[ 4488.646] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 4488.646] (II) Module wfb: vendor="X.Org Foundation"
[ 4488.646] compiled for 1.17.1, module version = 1.0.0
[ 4488.646] ABI class: X.Org ANSI C Emulation, version 0.4
[ 4488.646] (II) Loading sub module "ramdac"
[ 4488.646] (II) LoadModule: "ramdac"
[ 4488.646] (II) Module "ramdac" already built-in
[ 4488.647] (II) modeset(2): using drv /dev/dri/card0
[ 4488.647] (II) modeset(G0): using drv /dev/dri/card0
[ 4488.647] (EE) Screen 2 deleted because of no matching config section.
[ 4488.647] (II) UnloadModule: "modesetting"
[ 4488.647] (II) NVIDIA(0): Creating default Display subsection in Screen section
"SAM-Screen" for depth/fbbpp 24/32
[ 4488.647] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 4488.647] (==) NVIDIA(0): RGB weight 888
[ 4488.647] (==) NVIDIA(0): Default visual is TrueColor
[ 4488.647] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 4488.648] (II) NVIDIA(1): Creating default Display subsection in Screen section
"VS-Screen" for depth/fbbpp 24/32
[ 4488.648] (**) NVIDIA(0): Enabling 2D acceleration
[ 4489.049] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20150116)
[ 4489.050] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 560 Ti (GF114) at PCI:1:0:0 (GPU-0)
[ 4489.050] (--) NVIDIA(0): Memory: 1048576 kBytes
[ 4489.050] (--) NVIDIA(0): VideoBIOS: 70.24.21.00.00
[ 4489.050] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 4489.082] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 560 Ti at PCI:1:0:0
[ 4489.082] (--) NVIDIA(0): CRT-0
[ 4489.082] (--) NVIDIA(0): CRT-1
[ 4489.082] (--) NVIDIA(0): Samsung SMS27A850 (DFP-0) (boot, connected)
[ 4489.082] (--) NVIDIA(0): DFP-1
[ 4489.082] (--) NVIDIA(0): ViewSonic VG1930wm (DFP-2) (connected)
[ 4489.082] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[ 4489.082] (--) NVIDIA(GPU-0): CRT-1: 400.0 MHz maximum pixel clock
[ 4489.082] (--) NVIDIA(0): Samsung SMS27A850 (DFP-0): Internal TMDS
[ 4489.082] (--) NVIDIA(GPU-0): Samsung SMS27A850 (DFP-0): 330.0 MHz maximum pixel clock
[ 4489.082] (--) NVIDIA(0): DFP-1: Internal TMDS
[ 4489.082] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[ 4489.082] (--) NVIDIA(0): ViewSonic VG1930wm (DFP-2): Internal TMDS
[ 4489.082] (--) NVIDIA(GPU-0): ViewSonic VG1930wm (DFP-2): 330.0 MHz maximum pixel clock
[ 4489.083] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4489.083] (**) NVIDIA(0): device Samsung SMS27A850 (DFP-0) (Using EDID frequencies
[ 4489.083] (**) NVIDIA(0): has been enabled on all display devices.)
[ 4489.083] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4489.083] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
[ 4489.083] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4489.083] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4489.083] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
[ 4489.083] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4489.083] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
[ 4489.083] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4489.083] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4489.083] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
[ 4489.083] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4489.083] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
[ 4489.083] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4489.083] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4489.083] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
[ 4489.084] (==) NVIDIA(0):
[ 4489.084] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 4489.084] (==) NVIDIA(0): will be used as the requested mode.
[ 4489.084] (==) NVIDIA(0):
[ 4489.084] (II) NVIDIA(0): Validated MetaModes:
[ 4489.084] (II) NVIDIA(0): "DFP-0:nvidia-auto-select"
[ 4489.084] (II) NVIDIA(0): Virtual screen size determined to be 2560 x 1440
[ 4489.113] (--) NVIDIA(0): DPI set to (125, 114); computed from "UseEdidDpi" X config
[ 4489.113] (--) NVIDIA(0): option
[ 4489.114] (==) NVIDIA(1): Depth 24, (==) framebuffer bpp 32
[ 4489.114] (==) NVIDIA(1): RGB weight 888
[ 4489.114] (==) NVIDIA(1): Default visual is TrueColor
[ 4489.114] (==) NVIDIA(1): Using gamma correction (1.0, 1.0, 1.0)
[ 4489.114] (II) NVIDIA(1): NVIDIA GPU GeForce GTX 560 Ti (GF114) at PCI:1:0:0 (GPU-0)
[ 4489.114] (--) NVIDIA(1): Memory: 1048576 kBytes
[ 4489.114] (--) NVIDIA(1): VideoBIOS: 70.24.21.00.00
[ 4489.114] (II) NVIDIA(1): Detected PCI Express Link width: 16X
[ 4489.146] (--) NVIDIA(1): Valid display device(s) on GeForce GTX 560 Ti at PCI:1:0:0
[ 4489.146] (--) NVIDIA(1): CRT-0
[ 4489.146] (--) NVIDIA(1): CRT-1
[ 4489.146] (--) NVIDIA(1): Samsung SMS27A850 (DFP-0) (boot, connected)
[ 4489.146] (--) NVIDIA(1): DFP-1
[ 4489.146] (--) NVIDIA(1): ViewSonic VG1930wm (DFP-2) (connected)
[ 4489.146] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[ 4489.146] (--) NVIDIA(GPU-0): CRT-1: 400.0 MHz maximum pixel clock
[ 4489.146] (--) NVIDIA(1): Samsung SMS27A850 (DFP-0): Internal TMDS
[ 4489.146] (--) NVIDIA(GPU-0): Samsung SMS27A850 (DFP-0): 330.0 MHz maximum pixel clock
[ 4489.146] (--) NVIDIA(1): DFP-1: Internal TMDS
[ 4489.146] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[ 4489.146] (--) NVIDIA(1): ViewSonic VG1930wm (DFP-2): Internal TMDS
[ 4489.146] (--) NVIDIA(GPU-0): ViewSonic VG1930wm (DFP-2): 330.0 MHz maximum pixel clock
[ 4489.146] (**) NVIDIA(1): Option "Rotate" "left"
[ 4489.146] (**) NVIDIA(1): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4489.146] (**) NVIDIA(1): device ViewSonic VG1930wm (DFP-2) (Using EDID frequencies
[ 4489.146] (**) NVIDIA(1): has been enabled on all display devices.)
[ 4489.147] (==) NVIDIA(1):
[ 4489.147] (==) NVIDIA(1): No modes were requested; the default mode "nvidia-auto-select"
[ 4489.147] (==) NVIDIA(1): will be used as the requested mode.
[ 4489.147] (==) NVIDIA(1):
[ 4489.147] (II) NVIDIA(1): Validated MetaModes:
[ 4489.147] (II) NVIDIA(1): "DFP-2:nvidia-auto-select{Rotation=90}"
[ 4489.147] (II) NVIDIA(1): Virtual screen size determined to be 900 x 1440
[ 4489.150] (--) NVIDIA(1): DPI set to (55, 140); computed from "UseEdidDpi" X config
[ 4489.150] (--) NVIDIA(1): option
[ 4489.150] (EE)
[ 4489.150] (EE) Backtrace:
[ 4489.151] (EE) 0: /usr/lib/xorg-server/Xorg (OsLookupColor+0x119) [0x5949c9]
[ 4489.151] (EE) 1: /usr/lib/libc.so.6 (__restore_rt+0x0) [0x7f64dd88653f]
[ 4489.151] (EE) 2: /usr/lib/xorg-server/Xorg (xf86nameCompare+0x19) [0x4a9159]
[ 4489.151] (EE) 3: /usr/lib/xorg-server/Xorg (xf86findOption+0x2c) [0x4a2c6c]
[ 4489.151] (EE) 4: /usr/lib/xorg-server/Xorg (xf86SetDepthBpp+0x430) [0x4828d0]
[ 4489.151] (EE) 5: /usr/lib/xorg/modules/drivers/modesetting_drv.so (_init+0x25e1) [0x7f64d695aab1]
[ 4489.151] (EE) 6: /usr/lib/xorg-server/Xorg (InitOutput+0xbcc) [0x47b63c]
[ 4489.151] (EE) 7: /usr/lib/xorg-server/Xorg (remove_fs_handlers+0x22a) [0x43c9da]
[ 4489.152] (EE) 8: /usr/lib/libc.so.6 (__libc_start_main+0xf0) [0x7f64dd873800]
[ 4489.152] (EE) 9: /usr/lib/xorg-server/Xorg (_start+0x29) [0x427039]
[ 4489.152] (EE) 10: ? (?+0x29) [0x29]
[ 4489.152] (EE)
[ 4489.152] (EE) Segmentation fault at address 0x231
[ 4489.152] (EE)
Fatal server error:
[ 4489.152] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 4489.152] (EE)
[ 4489.152] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 4489.152] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 4489.152] (EE)
[ 4489.295] (EE) Server terminated with error (1). Closing log file.
Section "DRI"
Mode 0666
EndSection
Section "Monitor"
Identifier "SAM"
ModelName "Samsung SMS27A850"
HorizSync 30.0 - 90.0
VertRefresh 56.0 - 75.0
Option "DPMS"
DisplaySize 597 336 # In millimeters
EndSection
Section "Monitor"
Identifier "VS"
ModelName "ViewSonic VG1930wm"
Option "DPMS"
Option "RightOf" "SAM"
Option "Rotate" "left"
EndSection
Section "Monitor"
Identifier "BNQ"
ModelName "BenQ FP737s"
Option "DPMS"
Option "LeftOf" "SAM"
Option "Rotate" "left"
EndSection
Section "Device"
Identifier "nvidia-sam"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 560 Ti"
BusID "01:00:0"
Option "Monitor-DVI-I-1" "SAM"
Screen 0
EndSection
Section "Device"
Identifier "nvidia-vs"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 560 Ti"
BusID "01:00:0"
Option "Monitor-DVI-I-2" "VS"
Screen 1
EndSection
Section "Device"
Identifier "intel"
Driver "intel"
Option "AccelMethod" "none"
VendorName "Intel"
BoardName "Intel Integrated Graphic Controller"
BusID "00:02:0"
Option "Monitor-VGA-0" "BNQ"
Screen 2
EndSection
Section "Screen"
Identifier "SAM-Screen"
Device "nvidia-sam"
Monitor "SAM"
#DefaultDepth 24
# Option "Stereo" "0"
# Option "SLI" "Off"
# Option "MultiGPU" "Off"
# Option "BaseMosaic" "off"
#Option "AllowEmptyInitialConfiguration"
# SubSection "Display"
# Depth 24
# EndSubSection
EndSection
Section "Screen"
Identifier "VS-Screen"
Device "nvidia-vs"
Monitor "VS"
#DefaultDepth 24
# Option "Stereo" "0"
# Option "SLI" "Off"
# Option "MultiGPU" "Off"
# Option "BaseMosaic" "off"
#Option "AllowEmptyInitialConfiguration"
# SubSection "Display"
# Depth 24
# EndSubSection
EndSection
Section "Screen"
Identifier "BNQ-Screen"
Device "intel"
Monitor "BNQ"
EndSection
SectionHi:
There is a specific order you need to install the graphics drivers for the notebooks with the nvidia/intel graphics.
1. Install the Intel chipset installation utility and reboot. If the one on your notebook's support page doesn't work, use this one.
https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=20775&lang=eng&ProdId=816
2. Install the Intel HD graphics driver and reboot. If the one on your notebook's suport page doesn't work, try this one.
https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=24348
3. Install the nVidia HD graphics driver and reboot. If the one on your notebook's support page doesn't work, try this one.
http://www.nvidia.com/download/driverResults.aspx/81879/en-us -
[SOLVED]Xf86-video-intel 2.7.0-1 problem.
Iḿ using xf86-video-intel with xorg-server 1.6.1 and when i use a kms-enabled kernel my video gets all messed up. It' s like it can't find the correct sync with video.
no kms is ok, but as usual , i get no direct rendering with compiz.
does anyone is experiencing the same problem?
intel gm965 here
Last edited by lycaeum (2009-04-17 10:50:22)Bogart wrote:
The problem is that tiling was enabled to solve the performance problems with KMS. So disabling it will have the performance problems again.
How does gtkperf run as compared with EXA when using KMS and tiling off? Could anyone test? (I'll test myself later when I have the chance).
Don't know how it compares, but here are the UXA/kms results with tiling off:
GtkPerf 0.40 - Starting testing: Fri Apr 17 12:10:03 2009
GtkEntry - time: 0.00
GtkComboBox - time: 3.09
GtkComboBoxEntry - time: 1.87
GtkSpinButton - time: 0.89
GtkProgressBar - time: 1.03
GtkToggleButton - time: 0.61
GtkCheckButton - time: 0.53
GtkRadioButton - time: 0.71
GtkTextView - Add text - time: 0.91
GtkTextView - Scroll - time: 0.88
GtkDrawingArea - Lines - time: 1.23
GtkDrawingArea - Circles - time: 2.42
GtkDrawingArea - Text - time: 2.37
GtkDrawingArea - Pixbufs - time: 0.27
Total time: 16.84
Maybe you are looking for
-
My iPHONE 5 wifi is NOT working when am 3 feet away from router while my iPhone 4s has full signal all the time.Please help.
-
Win 7 Pro (via Parallels 6), Snow Leopard, and a USB thumb drive
This is probably a simple fix... When I plug in a thumb drive, Snow Leopard recognizes it. When I tell Parallels to "share" the same thumb drive, Win 7 Pro installs the driver and it recognizes the thumb drive under "Devices." But Win 7 Pro does no
-
I opened and edited a pic from my Olympus camera onto my mac (not in iPhoto). I zoomed in
I opened and edited a pic from my Olympus camera onto my mac (not in iPhoto). I zoomed in and rotated the pictures and when I tried to click out of them, I got a message that the file was locked because I hadn't used it recently and "If you want to
-
How am I able to add and remove people from a group message?
How am I able to add and remove people from a group message?
-
How to incorporate File name and timestamp automatically into select and save file dialog box?
Hello, i am trying to incorporate the file name which is inputed by the user along with the timestamp into the selected and save file dialog box. Can you help? Thanks Solved! Go to Solution.