Intel GM965 & TPFanContr​ol

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.

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

  • 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)

  • TV-OUT Intel GM965/GL960

    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)

  • 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)

  • 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.

  • 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.

  • [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

  • Xf86-video-intel 2.4.2-1 has "spontaneous" lockups

    I've been quite happy with my Arch installation on my Dell XPS M1330, which I purchased about a month ago.  I have used Arch quite a bit before for servers and virtual machines, but this is my first time using it as a "regular" desktop system.
    Anyways, I have had lots of problems with the integrated Intel GM965 graphics chipset.  It seems as though no matter what driver version I'm using, EXA has lots of graphical glitches (e.g. the system tray in KDE 4 is not viewable because there are seemingly random pieces of the screen splotched over it) and 3D support under both EXA and XAA seems to be minimal ("Failed to initialize TTM buffer manager.  Falling back to classic." on everything, low FPS in glxgears, absurdly poor performance on 3D games, etc.).  Right now, I'm using XAA and RandR to support my dual-screen setup (the included laptop monitor runs at 1280x800 and my external monitor runs at 1280x1024).
    But none of that seems important right now compared to the fact that the xf86-video-intel driver is causing seemingly arbitrary lockups.  Most of the time, after the X server crashes, my whole system proceeds to crash as well and I need to manually shut off the power, which makes me very worried about data corruption.
    I put spontaneous in quotes in the subject because I have a theory as to why this is happening.  The KDM log tells me this:
    http://pastebin.com/f2019f021
    (that's one X session; don't mind the stuff about the input devices--I haven't quite set those up yet)
    I searched for errors with I830WaitLpRing() and came up with a very large number of results, which suggests that it could be just a blanket problem.  One interesting note was that someone had mentioned lockups occurring while using Xfig.  Interestingly enough, I was using Xfig when my system last locked up as well.  However, I've also had lockups when running virtual machines (VirtualBox and/or VMWare) and sometimes when just browsing sites with a lot of Flash content.  It's always this same error, with some minor variations with respect to the "wanted line":
    [j@jwcxz ~]$ cat /var/log/kdm.log | grep wanted
    space: 130984 wanted 131064
    space: 130976 wanted 131064
    space: 125216 wanted 131064
    space: 125208 wanted 131064
    space: 130744 wanted 131064
    space: 130736 wanted 131064
    space: 125248 wanted 131064
    space: 125240 wanted 131064
    space: 125264 wanted 131064
    space: 125256 wanted 131064
    space: 125216 wanted 131064
    space: 125208 wanted 131064
    space: 125264 wanted 131064
    space: 125256 wanted 131064
    What I find most interesting is the fact that all of these bug reports have been noted in very old versions of Xorg and the Intel driver (all the way back to 2006).  Yet, I'm running the very latest release that's in the testing repository.  I can also say that I have tried the release in the regular repositories and have experienced the same problems on those.
    Is this a problem due to the inability to pull more Video RAM?  Can anyone give me any suggestions as to how to make my system stable?
    Thanks for your help.
    ...  This is not the kind of frustration I need two weeks before a paper is due.  I'm thoroughly regretting my being too cheap to buy the nVidia upgrade.

    patroclo7 wrote:
    All the problems mentioned are quite well known with the versions of stuff in the testing repo, and everything should be related to DRI (basically TTF has been removed and GEM is not yet there). There is no easy solution (GEM requires hard kernel patches, and anyway the driver for i965 is not ready to use them).
    But if you downgrade everything (the server, the drivers mesa, etc) to extra these problems should not happen.
    Okay.  Thank you for this information.  Based on (apparently) misinformation that I had read here, I had assumed that the stuff in testing was better.  So, I'll revert back tonight and post back to describe my experiences.

  • T61 and the Intel Graphics Card error - external monitor not detected

    T61 with Vista 32 bit, Mobile Intel® GM965 Express Chipset and an Advanced Mini Dock.
    I am trying to use the DVI port and an external monitor. The driver does not detect the external monitor.
    Uninstalling the Intel driver the Generic profile will work on the external monitor, but is overly fuzzy, how do I get the T61 to recognize my external monitor with the right drivers?
    I am currently running the Intel Driver Ver. - 7.14.10.1329, which provides the message under Multiple Display:
    Two displays must be connected to the computer before you can use this feature. Please connect another display.
    Of course my 22" monitor is connected.  That is the frustrating part.  I have also uninstalled Presentation Director, just in case, but then re-installed after it seemed that wasn't the problem.
    There is a newer driver from Intel but it is not Lenovo approved yet I guess. Though I highly doubt this is the problem. What can I do?
    ~~
    I did post a thread on the thinkpads.com too, but so far haven't had any luck.

    Well the new dock came but didn't fix the problem.  Now my nice new T61 is packed up in a depot box, waiting for DHL to come pick it up.
    dkaufman1 -- I guess we do have different problems.  If I set my T61 to display to the DVI port in the bios I get a blank screens on both the DVI connectd monitor and the laptop screen until the OS boots when I have the laptop in the dock.  The only way I can see the bios screen to set it back to the ThinkPad LCD setting is to boot it disconnected from the dock.
    I really hope that this problem is resolved, as I really like the T61 otherwise.  I was even using it with the VGA cable connected to my 22" monitor, but it was pretty hard to take.   I'm now back to my old desktop hooked up to the same monitor via DVI and it is quite the relief, even if it isn't as zippy as the T61.

  • 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.

  • Thinkpad's and N100's w/ 945PM chipset can't address 3G Ram but Dell Can

    Since I am a programmer, I am particularly interested in having the maximum amount of Ram available under 32 bit Windows.
    Unfortunately,  I have to buy a T61p to enable me to use 4GB.
    From a reply to a NoteBook review Forum:
    http://forum.notebookreview.com/archive/index.php/t-136639.html
    At work, we have both Dell XPS and IBM/Lenovo Thinkpad laptops. We choose the T60 models for their compactness/weight and reliability, while we choose the XPS M1710 and M2010 for their 17 and 20-inch screens and somewhat faster graphics chips. The ThinkPad T60 computers have problems accessing over 3GB RAM, and that is NOT because of the chipset or the OS that we use, but, it is only because of the incompetent designers/engineers at IBM or Lenovo; let me explain:
    We have tried to install both 32-bit and 64-bit version of Vista, Windows Server 2003 R2 STD, Win XP and different dists of LINUX on T60, T60p, Z61, Z61p, Z61m, (X60 and T43) and Lenovo 3000 series, but they simply can NOT access memory over 3GB (X60 and T43 can not support that since their chipset seem to have accessing issues over the magic 3GB, but we tried anyway)
    We also tried the same thing on Dell XPS M1710 and M2010, and they could access almost the ENTIRE 4 GB installed even with 32-bit version of Windows Vista (BTW, 32-bit Vista can access 16 GB RAM with the right chipset so...). Of course, now you can guess that it was no problem with the 64-bit version of the OS:es we tried.
    The Dell XPS M1710 and M2010 use exactly the same chipset found in T60 and Z60 series (Mobile Intel 945PM Express Chipset). In December 2006, we even opened a T60p (model 2007 8JG) and compared the chipset with the Dell XPS M1710, and well, I suppose that you have already guessed that it was the same chipset in both machines.
    Honestly, I hoped that we would find the Mobile Intel 945 GM or GMS chipset in the T60 laptops (those chipsets seem to have this 3GB limit), since we had a BIG argue with the support guys at Lenovo, and they came with totally silly answers why the computers can not access over 3GB RAM. They even asked me what I need 4GB RAM for!! Can you imagine that?! You can ask ANY programmer/developer who works with virtual machines (both VPC and VMWare or even Parallels) and everyone will tell you that you can not have too much RAM!!! And it IS A BIG difference between 3GB and 4GB. However...
    Now, we have heard rumors that HP NX94xx also can access 4GB RAM installed, but I can not confirm it myself, since I have not seen it myself.
    And now, regarding to your post about mixing 2GB SO-DIMM with 1GB SO-DIMM, I would not recommend it. The 2GB SO-DIMM memory modules are pretty cheap now, and besides, you will lose a lot of speed mixing 2GB with 1GB memory modules. Just try different benchmarking programs and you will see. If you want to see quick results without a lot of installations, try Memtest86+
    However, I think that it is very rotten that IBM/Lenovo does not care about their customers and lets a lot of incompetent technicians answer the phone. I have tried to come in contact with higher bosses and engineers, but they are simply unavailable. But it must be a way that we customers can make them hear us.. I only do not know how! :-/
    And so, here ends my first (and long) post in here!
    From the thinkpad forum, there is another confirmation, but the author is not aware that Dell did a better job with the P chipset:
    T60/T61/p memory limitations -- the definitive answer [pics]  
    http://forum.thinkpads.com/viewtopic.php?t=49703
    update 10/25/2007:   now includes T60/p information.
    T60 and T60p:
    the T60 and T60p are based off of the intel socket M processors.   no matter how much memory you install in these thinkpads, only 3GB will be addressable regardless of operating system used.   this is a physical limitation and there is absolutely no workaround.   if you have a T60/p then installing 4GB total system memory is a waste.   save your money, stop at 3GB, and put the savings either in the bank or toward a T61/p if you want 4GB.
    quoted from official lenovo documentation:
    Quote: Maximum memory capacity may require the replacement of standard component with largest supported component available. On ThinkPad systems with an Intel 945GM, 945PM, GM965, or PM965 chipset, even though it is possible to physically install 4GB of memory, the actual amount of memory addressable by an operating system will be limited to 3GB. This limitation does not exist with the Intel GM965 and PM965 with the 64-bit operating systems Windows XP Professional 64-bit and Windows Vista 64-bit Editions.
    the key point to take away from this quote:   the T60 and T60p are based off of the 945GM and 945PM chipsets and therefore fall under the 3GB physical limitation as stated above.   even with 4GB total system memory and a capable OS, you still can't see or use more 3GB no matter what you do.
    T61 and T61p:
    the T61 and T61p are based off of the intel socket P processors.   these systems are capable of using up to 4GB total system memory as long as you use the proper OS.   below are the results from the four most popular microsoft OSes tested on my T61p.

    i wrote the article over at TPF regarding T60/1/p memory limitations.
    while i've read that certain dell models can supposedly access all 4GB, i have yet to see definitive proof backing this up.   from my understanding, dell wrote their BIOSes to report the maximum installed memory but the systems still cannot utilize more than 3GB regardless of what is reported.   dell is the only manufacturer with a 945-based system which claims to use all 4GB so it leads me to think that something fishy is going on.   if the 945 could use more than 3GB then you'd think lenovo, apple, HP, etc. would have been able to pull it off as well.
    before buying my T61p i performed weeks of research on the subject of 3GB/4GB limitations in chipsets.   i have yet to find definitive evidence showing that a merom-based system can truly access more than 3GB because of the chipset's lack of memory hoisting capability.   santa rosa seems to be the first mobile chipset supporting memory hoisting (which is necessary for moving memory addresses above the 4GB mark so that all 4GB of physical memory can be addressed by the OS).
    the simple solution is to buy a T61p.   while the T60p did have optional IPS displays, the T61/p is better in absolutely every aspect except display quality.   i've had my hands on numerous T60/p systems of friends/family/colleagues and wouldn't trade my T61p for any of them.   my next upgrade won't happen until intel makes a mobile chipset able to address 8GB+ system memory (which santa rosa very well may be able to do but we won't know for sure until 4GB SODIMMs are released for public consumption).
    ThinkStation C20
    ThinkPad X1C · X220 · X60T · s30 · 600

  • T61 NVIDIA driver not working?

    Hello!
    I have a really old T61 (Type 8895) and I updated it to Windows 7 Ultimate 32 Bit from it's original Windows Vista Home Premium recently, which means all the drivers are gone.
    So, I went to Lenovo Support and searched for it's drivers, and one of them was a NVIDIA Quadro NVS 140M (v296.88) driver.
    Each time I try to install it, it tells me: This graphics driver could not find compatible graphics hardware.
    I decided to get a newer driver. So, I went to NVIDIA's website, got the newest driver (v320.00) and still, it would give me the same error.
    So, I googled the problem, still couldn't find the problem I am having.
    What is going on? (I need the laptop for some testing before I decide to get a new laptop and waste money)
    Thanks!
    Sincerly,
    Majid or Mayood00
    Solved!
    Go to Solution.

    Your model 8895 doesn't have nVidia graphics, it has integrated Intel graphics but this is a good thing since the nVidia chips sometimes fail on similar equipped models. You want to install the graphic drivers for the Intel GM965 that matches your windows version.
    If you want a more detailed explanation, the nVidia chips used in T61 series built before August 2008 sometimes fail resulting an need to replace the motherboard. Your system is a 14.1" with standard 4:3 screen. This size was phased out starting in the end of 2007 and general production stopped about May or June. We've never seen any of this size manufactured in August 2008 so the only way to get a board with a Good nVidia chip on one of these is an extremely rare new replacement board. The supply of these boards has been exhausted for years but there were recently a few found still sealed in the original IBM boxes. These rare boards generally cost about what the used laptop is worth, but are still a good investment considering this is the last and best Thinkpad made before the switch to the widescreen format, it's also the only standard screen model that supports 8gb of ram. Many users retrofit these T61 boards into T60 models too since they had better screen options. 
    ThinkPad W-510 i7-820QM(1.73-3.06GHz) Quad Core... ThinkPad T500, T9900, 8gb SSD...FrankNpad T-60p/61p (X9000 2.8ghz) 8gb SSD ips FlexView...ThinkPad T-61p (T9300 2.5ghz) 8gb ram...Thinkpad X-61 Tablet 4gb ram...ThinkPad A-31 (1.9ghz P4 1.5gb ram)

  • Xorg Cpu Usage

    I'm getting weird constant cpu usage from Xorg (100% of one of my cores). It started after a recent update of the system.
    Here's my xorg.conf (a bit messy)
    Section "ServerLayout"
    Identifier "Xorg Configured"
    Screen 0 "Screen0" 0 0
    InputDevice "Keyboard0" "CoreKeyboard"
    # PS/2 Mouse not detected
    # Serial Mouse not detected
    InputDevice "USB Mouse" "CorePointer"
    InputDevice "SynapticsTouchpad" "SendCoreEvents"
    InputDevice "UltraNav TrackPoint" "CorePointer"
    EndSection
    Section "ServerFlags"
    Option "AllowMouseOpenFail" "true"
    Option "AutoAddDevices" "False"
    EndSection
    Section "Files"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc:unscaled"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/100dpi"
    FontPath "/usr/share/fonts/PEX"
    # Additional fonts: Locale, Gimp, TTF...
    FontPath "/usr/share/fonts/cyrillic"
    # FontPath "/usr/share/lib/X11/fonts/latin2/75dpi"
    # FontPath "/usr/share/lib/X11/fonts/latin2/100dpi"
    # True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
    FontPath "/usr/share/fonts/Type1"
    FontPath "/usr/share/fonts/ttf/western"
    FontPath "/usr/share/fonts/ttf/decoratives"
    FontPath "/usr/share/fonts/truetype"
    FontPath "/usr/share/fonts/truetype/openoffice"
    FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
    FontPath "/usr/share/fonts/latex-ttf-fonts"
    FontPath "/usr/share/fonts/defoma/CID"
    FontPath "/usr/share/fonts/defoma/TrueType"
    EndSection
    Section "Module"
    Load "ddc" # ddc probing of monitor
    Load "dbe"
    Load "dri"
    Load "extmod"
    Load "glx"
    Load "bitmap" # bitmap-fonts
    Load "type1"
    Load "freetype"
    Load "record"
    Load "synaptics"
    Load "evdev"
    Load "psmouse"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "keyboard"
    Option "CoreKeyboard"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc105"
    Option "XkbLayout" "us"
    Option "XkbVariant" ""
    EndSection
    Section "InputDevice"
    Identifier "UltraNav Trackpoint"
    Driver "mouse"
    Option "CorePointer"
    Option "Device" "/dev/input/mice"
    Option "Protocol" "ImPS/2"
    Option "Emulate3Buttons" "off"
    Option "EmulateWheel" "on"
    Option "EmulateWheelTimeOut" "250"
    Option "EmulateWheelButton" "2"
    Option "YAxisMapping" "4 5"
    Option "XAxisMapping" "6 7"
    Option "ZAxisMapping" "4 5"
    EndSection
    Section "InputDevice"
    Identifier "SynapticsTouchpad"
    Driver "synaptics"
    Option "AlwaysCore" "true" # send events to CorePointer
    Option "Device" "/dev/psaux"
    Option "Protocol" "auto-dev"
    Option "SHMConfig" "true" # configurable at runtime? security risk
    Option "LeftEdge" "1700" # x coord left
    Option "RightEdge" "5600" # x coord right
    Option "TopEdge" "1700" # y coord top
    Option "BottomEdge" "4800" # y coord bottom
    #Option "FingerLow" "25" # pressure below this level triggers release
    #Option "FingerHigh" "30" # pressure above this level triggers touch
    Option "MaxTapTime" "120" # max time in ms for detecting tap
    Option "VertEdgeScroll" "true" # enable vertical scroll zone
    Option "HorizEdgeScroll" "true" # enable horizontal scroll zone
    Option "CornerCoasting" "true" # enable continuous scroll with finger in corner
    Option "CoastingSpeed" "0.30" # corner coasting speed
    #Option "HorizScrollDelta" "0"
    #Option "MaxTapMove" "0"
    #Option "VertScrollDelta" "0"
    Option "VertScrollDelta" "140" # edge-to-edge scroll distance of the vertical scroll
    Option "HorizScrollDelta" "100" # edge-to-edge scroll distance of the horizontal scroll
    Option "MinSpeed" "0.20" # speed factor for low pointer movement
    Option "MaxSpeed" "0.80" # maximum speed factor for fast pointer movement
    Option "AccelFactor" "0.0020" # acceleration factor for normal pointer movements
    #Option "SendCoreEvents" "true"
    Option "TapButton1" "1"
    Option "TapButton2" "2"
    Option "TapButton3" "3"
    EndSection
    Section "InputDevice"
    Identifier "Serial Mouse"
    Driver "mouse"
    Option "Protocol" "Microsoft"
    Option "Device" "/dev/ttyS0"
    Option "Emulate3Buttons" "true"
    Option "Emulate3Timeout" "70"
    Option "SendCoreEvents" "true"
    EndSection
    Section "InputDevice"
    Identifier "PS/2 Mouse"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "ZAxisMapping" "4 5"
    Option "Device" "/dev/psaux"
    Option "Emulate3Buttons" "true"
    Option "Emulate3Timeout" "70"
    Option "SendCoreEvents" "true"
    EndSection
    Section "InputDevice"
    Identifier "USB Mouse"
    Driver "mouse"
    Option "Device" "/dev/input/mice"
    Option "SendCoreEvents" "true"
    Option "Protocol" "IMPS/2"
    Option "ZAxisMapping" "4 5"
    Option "Buttons" "5"
    EndSection
    # Auto-generated by Archie mkxcfg
    Section "Monitor"
    Identifier "Monitor0"
    Option "DPMS" "true"
    # HorizSync 28.0 - 78.0 # Warning: This may fry very old Monitors
    HorizSync 28.0 - 96.0 # Warning: This may fry old Monitors
    VertRefresh 50.0 - 75.0 # Very conservative. May flicker.
    # VertRefresh 50.0 - 62.0 # Extreme conservative. Will flicker. TFT default.
    # Default modes distilled from
    # "VESA and Industry Standards and Guide for Computer Display Monitor
    # Timing", version 1.0, revision 0.8, adopted September 17, 1998.
    # $XFree86: xc/programs/Xserver/hw/xfree86/etc/vesamodes,v 1.4 1999/11/18 16:52:17 tsi Exp $
    # 640x350 @ 85Hz (VESA) hsync: 37.9kHz
    ModeLine "640x350" 31.5 640 672 736 832 350 382 385 445 +hsync -vsync
    # 640x400 @ 85Hz (VESA) hsync: 37.9kHz
    ModeLine "640x400" 31.5 640 672 736 832 400 401 404 445 -hsync +vsync
    # 720x400 @ 85Hz (VESA) hsync: 37.9kHz
    ModeLine "720x400" 35.5 720 756 828 936 400 401 404 446 -hsync +vsync
    # 640x480 @ 60Hz (Industry standard) hsync: 31.5kHz
    ModeLine "640x480" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync
    # 640x480 @ 72Hz (VESA) hsync: 37.9kHz
    ModeLine "640x480" 31.5 640 664 704 832 480 489 491 520 -hsync -vsync
    # 640x480 @ 75Hz (VESA) hsync: 37.5kHz
    ModeLine "640x480" 31.5 640 656 720 840 480 481 484 500 -hsync -vsync
    # 640x480 @ 85Hz (VESA) hsync: 43.3kHz
    ModeLine "640x480" 36.0 640 696 752 832 480 481 484 509 -hsync -vsync
    # 800x600 @ 56Hz (VESA) hsync: 35.2kHz
    ModeLine "800x600" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
    # 800x600 @ 60Hz (VESA) hsync: 37.9kHz
    ModeLine "800x600" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
    # 800x600 @ 72Hz (VESA) hsync: 48.1kHz
    ModeLine "800x600" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync
    # 800x600 @ 75Hz (VESA) hsync: 46.9kHz
    ModeLine "800x600" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync
    # 800x600 @ 85Hz (VESA) hsync: 53.7kHz
    ModeLine "800x600" 56.3 800 832 896 1048 600 601 604 631 +hsync +vsync
    # 1024x768i @ 43Hz (industry standard) hsync: 35.5kHz
    ModeLine "1024x768" 44.9 1024 1032 1208 1264 768 768 776 817 +hsync +vsync Interlace
    # 1024x768 @ 60Hz (VESA) hsync: 48.4kHz
    ModeLine "1024x768" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
    # 1024x768 @ 70Hz (VESA) hsync: 56.5kHz
    ModeLine "1024x768" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
    # 1024x768 @ 75Hz (VESA) hsync: 60.0kHz
    ModeLine "1024x768" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
    # 1024x768 @ 85Hz (VESA) hsync: 68.7kHz
    ModeLine "1024x768" 94.5 1024 1072 1168 1376 768 769 772 808 +hsync +vsync
    # 1152x864 @ 75Hz (VESA) hsync: 67.5kHz
    ModeLine "1152x864" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
    # 1280x960 @ 60Hz (VESA) hsync: 60.0kHz
    ModeLine "1280x960" 108.0 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync
    # 1280x960 @ 85Hz (VESA) hsync: 85.9kHz
    ModeLine "1280x960" 148.5 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync
    # 1280x1024 @ 60Hz (VESA) hsync: 64.0kHz
    ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
    # 1280x1024 @ 75Hz (VESA) hsync: 80.0kHz
    ModeLine "1280x1024" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
    # 1280x1024 @ 85Hz (VESA) hsync: 91.1kHz
    ModeLine "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
    # 1600x1200 @ 60Hz (VESA) hsync: 75.0kHz
    ModeLine "1600x1200" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    # 1600x1200 @ 65Hz (VESA) hsync: 81.3kHz
    ModeLine "1600x1200" 175.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    # 1600x1200 @ 70Hz (VESA) hsync: 87.5kHz
    ModeLine "1600x1200" 189.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    # 1600x1200 @ 75Hz (VESA) hsync: 93.8kHz
    ModeLine "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    # 1600x1200 @ 85Hz (VESA) hsync: 106.3kHz
    ModeLine "1600x1200" 229.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    # 1792x1344 @ 60Hz (VESA) hsync: 83.6kHz
    ModeLine "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
    # 1792x1344 @ 75Hz (VESA) hsync: 106.3kHz
    ModeLine "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
    # 1856x1392 @ 60Hz (VESA) hsync: 86.3kHz
    ModeLine "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
    # 1856x1392 @ 75Hz (VESA) hsync: 112.5kHz
    ModeLine "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
    # 1920x1440 @ 60Hz (VESA) hsync: 90.0kHz
    ModeLine "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
    # 1920x1440 @ 75Hz (VESA) hsync: 112.5kHz
    ModeLine "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
    # Additional modelines
    ModeLine "1800x1440" 230 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
    ModeLine "1800x1440" 250 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
    # Extended modelines with GTF timings
    # 640x480 @ 100.00 Hz (GTF) hsync: 50.90 kHz; pclk: 43.16 MHz
    ModeLine "640x480" 43.16 640 680 744 848 480 481 484 509 -HSync +Vsync
    # 768x576 @ 60.00 Hz (GTF) hsync: 35.82 kHz; pclk: 34.96 MHz
    ModeLine "768x576" 34.96 768 792 872 976 576 577 580 597 -HSync +Vsync
    # 768x576 @ 72.00 Hz (GTF) hsync: 43.27 kHz; pclk: 42.93 MHz
    ModeLine "768x576" 42.93 768 800 880 992 576 577 580 601 -HSync +Vsync
    # 768x576 @ 75.00 Hz (GTF) hsync: 45.15 kHz; pclk: 45.51 MHz
    ModeLine "768x576" 45.51 768 808 888 1008 576 577 580 602 -HSync +Vsync
    # 768x576 @ 85.00 Hz (GTF) hsync: 51.42 kHz; pclk: 51.84 MHz
    ModeLine "768x576" 51.84 768 808 888 1008 576 577 580 605 -HSync +Vsync
    # 768x576 @ 100.00 Hz (GTF) hsync: 61.10 kHz; pclk: 62.57 MHz
    ModeLine "768x576" 62.57 768 816 896 1024 576 577 580 611 -HSync +Vsync
    # 800x600 @ 100.00 Hz (GTF) hsync: 63.60 kHz; pclk: 68.18 MHz
    ModeLine "800x600" 68.18 800 848 936 1072 600 601 604 636 -HSync +Vsync
    # 1024x768 @ 100.00 Hz (GTF) hsync: 81.40 kHz; pclk: 113.31 MHz
    ModeLine "1024x768" 113.31 1024 1096 1208 1392 768 769 772 814 -HSync +Vsync
    # 1152x864 @ 60.00 Hz (GTF) hsync: 53.70 kHz; pclk: 81.62 MHz
    ModeLine "1152x864" 81.62 1152 1216 1336 1520 864 865 868 895 -HSync +Vsync
    # 1152x864 @ 85.00 Hz (GTF) hsync: 77.10 kHz; pclk: 119.65 MHz
    ModeLine "1152x864" 119.65 1152 1224 1352 1552 864 865 868 907 -HSync +Vsync
    # 1152x864 @ 100.00 Hz (GTF) hsync: 91.50 kHz; pclk: 143.47 MHz
    ModeLine "1152x864" 143.47 1152 1232 1360 1568 864 865 868 915 -HSync +Vsync
    # 1280x960 @ 72.00 Hz (GTF) hsync: 72.07 kHz; pclk: 124.54 MHz
    ModeLine "1280x960" 124.54 1280 1368 1504 1728 960 961 964 1001 -HSync +Vsync
    # 1280x960 @ 75.00 Hz (GTF) hsync: 75.15 kHz; pclk: 129.86 MHz
    ModeLine "1280x960" 129.86 1280 1368 1504 1728 960 961 964 1002 -HSync +Vsync
    # 1280x960 @ 100.00 Hz (GTF) hsync: 101.70 kHz; pclk: 178.99 MHz
    ModeLine "1280x960" 178.99 1280 1376 1520 1760 960 961 964 1017 -HSync +Vsync
    # 1280x1024 @ 100.00 Hz (GTF) hsync: 108.50 kHz; pclk: 190.96 MHz
    ModeLine "1280x1024" 190.96 1280 1376 1520 1760 1024 1025 1028 1085 -HSync +Vsync
    # 1400x1050 @ 60.00 Hz (GTF) hsync: 65.22 kHz; pclk: 122.61 MHz
    ModeLine "1400x1050" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -HSync +Vsync
    # 1400x1050 @ 72.00 Hz (GTF) hsync: 78.77 kHz; pclk: 149.34 MHz
    ModeLine "1400x1050" 149.34 1400 1496 1648 1896 1050 1051 1054 1094 -HSync +Vsync
    # 1400x1050 @ 75.00 Hz (GTF) hsync: 82.20 kHz; pclk: 155.85 MHz
    ModeLine "1400x1050" 155.85 1400 1496 1648 1896 1050 1051 1054 1096 -HSync +Vsync
    # 1400x1050 @ 85.00 Hz (GTF) hsync: 93.76 kHz; pclk: 179.26 MHz
    ModeLine "1400x1050" 179.26 1400 1504 1656 1912 1050 1051 1054 1103 -HSync +Vsync
    # 1400x1050 @ 100.00 Hz (GTF) hsync: 111.20 kHz; pclk: 214.39 MHz
    ModeLine "1400x1050" 214.39 1400 1512 1664 1928 1050 1051 1054 1112 -HSync +Vsync
    # 1600x1200 @ 100.00 Hz (GTF) hsync: 127.10 kHz; pclk: 280.64 MHz
    ModeLine "1600x1200" 280.64 1600 1728 1904 2208 1200 1201 1204 1271 -HSync +Vsync
    EndSection
    # Auto-generated by Archie mkxcfg
    Section "Device"
    Identifier "Card0"
    Driver "intel"
    VendorName "All"
    BoardName "All"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "Monitor0"
    DefaultColorDepth 24
    SubSection "Display"
    Depth 24
    Modes "1280x800"
    EndSubSection
    EndSection
    Section "DRI"
    Mode 0666
    EndSection
    Here's the Xorg0 log
    X.Org X Server 1.5.3
    Release Date: 5 November 2008
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 2.6.27-ARCH x86_64
    Current Operating System: Linux nandesuka 2.6.28-ARCH #1 SMP PREEMPT Tue Mar 17 07:22:53 CET 2009 x86_64
    Build Date: 17 December 2008 10:46:49PM
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr 4 15:34:31 2009
    (==) Using config file: "/etc/X11/xorg.conf"
    (==) ServerLayout "Xorg Configured"
    (**) |-->Screen "Screen0" (0)
    (**) | |-->Monitor "Monitor0"
    (**) | |-->Device "Card0"
    (**) |-->Input Device "Keyboard0"
    (**) |-->Input Device "USB Mouse"
    (**) |-->Input Device "SynapticsTouchpad"
    (**) |-->Input Device "UltraNav Trackpoint"
    (**) Option "AllowMouseOpenFail" "true"
    (**) Option "AutoAddDevices" "False"
    (**) Not automatically adding devices
    (==) Automatically enabling devices
    (WW) The directory "/usr/share/fonts/PEX" does not exist.
    Entry deleted from font path.
    (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/cyrillic".
    Entry deleted from font path.
    (Run 'mkfontdir' on "/usr/share/fonts/cyrillic").
    (WW) The directory "/usr/share/fonts/ttf/western" does not exist.
    Entry deleted from font path.
    (WW) The directory "/usr/share/fonts/ttf/decoratives" does not exist.
    Entry deleted from font path.
    (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/truetype".
    Entry deleted from font path.
    (Run 'mkfontdir' on "/usr/share/fonts/truetype").
    (WW) The directory "/usr/share/fonts/truetype/openoffice" does not exist.
    Entry deleted from font path.
    (WW) The directory "/usr/share/fonts/truetype/ttf-bitstream-vera" does not exist.
    Entry deleted from font path.
    (WW) The directory "/usr/share/fonts/latex-ttf-fonts" does not exist.
    Entry deleted from font path.
    (WW) The directory "/usr/share/fonts/defoma/CID" does not exist.
    Entry deleted from font path.
    (WW) The directory "/usr/share/fonts/defoma/TrueType" does not exist.
    Entry deleted from font path.
    (==) Including the default font path /usr/share/fonts/misc,/usr/share/fonts/100dpi:unscaled,/usr/share/fonts/75dpi:unscaled,/usr/share/fonts/TTF,/usr/share/fonts/Type1.
    (**) FontPath set to:
    /usr/share/fonts/misc:unscaled,
    /usr/share/fonts/misc,
    /usr/share/fonts/75dpi:unscaled,
    /usr/share/fonts/75dpi,
    /usr/share/fonts/100dpi:unscaled,
    /usr/share/fonts/100dpi,
    /usr/share/fonts/Type1,
    /usr/share/fonts/misc,
    /usr/share/fonts/100dpi:unscaled,
    /usr/share/fonts/75dpi:unscaled,
    /usr/share/fonts/TTF,
    /usr/share/fonts/Type1
    (**) ModulePath set to "/usr/lib/xorg/modules"
    (WW) Duplicate core pointer devices. Removing core pointer attribute from "UltraNav Trackpoint"
    (II) Open ACPI successful (/var/run/acpid.socket)
    (II) Loader magic: 0x7b54e0
    (II) Module ABI versions:
    X.Org ANSI C Emulation: 0.4
    X.Org Video Driver: 4.1
    X.Org XInput driver : 2.1
    X.Org Server Extension : 1.1
    X.Org Font Renderer : 0.6
    (II) Loader running on linux
    (++) using VT number 7
    (--) PCI:*(0@0:2:0) Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller rev 12, Mem @ 0xf8100000/1048576, 0xe0000000/268435456, I/O @ 0x00001800/8
    (--) PCI: (0@0:2:1) Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller rev 12, Mem @ 0xf8200000/1048576
    (II) System resource ranges:
    [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    (II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
    (II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
    (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
    (II) "freetype" will be loaded. This was enabled by default and also specified in the config file.
    (II) "dri" will be loaded. This was enabled by default and also specified in the config file.
    (II) LoadModule: "ddc"
    (II) Module "ddc" already built-in
    (II) LoadModule: "dbe"
    (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
    (II) Module dbe: vendor="X.Org Foundation"
    compiled for 1.5.3, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 1.1
    (II) Loading extension DOUBLE-BUFFER
    (II) LoadModule: "dri"
    (II) Loading /usr/lib/xorg/modules/extensions//libdri.so
    (II) Module dri: vendor="X.Org Foundation"
    compiled for 1.5.3, module version = 1.0.0
    ABI class: X.Org Server Extension, version 1.1
    (II) Loading extension XFree86-DRI
    (II) LoadModule: "extmod"
    (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
    (II) Module extmod: vendor="X.Org Foundation"
    compiled for 1.5.3, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 1.1
    (II) Loading extension SHAPE
    (II) Loading extension MIT-SUNDRY-NONSTANDARD
    (II) Loading extension BIG-REQUESTS
    (II) Loading extension SYNC
    (II) Loading extension MIT-SCREEN-SAVER
    (II) Loading extension XC-MISC
    (II) Loading extension XFree86-VidModeExtension
    (II) Loading extension XFree86-Misc
    (II) Loading extension XFree86-DGA
    (II) Loading extension DPMS
    (II) Loading extension TOG-CUP
    (II) Loading extension Extended-Visual-Information
    (II) Loading extension XVideo
    (II) Loading extension XVideo-MotionCompensation
    (II) Loading extension X-Resource
    (II) LoadModule: "glx"
    (II) Loading /usr/lib/xorg/modules/extensions//libglx.so
    (II) Module glx: vendor="X.Org Foundation"
    compiled for 1.5.3, module version = 1.0.0
    ABI class: X.Org Server Extension, version 1.1
    (==) AIGLX enabled
    (==) Exporting typical set of GLX visuals
    (II) Loading extension GLX
    (II) LoadModule: "type1"
    (WW) Warning, couldn't open module type1
    (II) UnloadModule: "type1"
    (EE) Failed to load module "type1" (module does not exist, 0)
    (II) LoadModule: "freetype"
    (II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so
    (II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
    compiled for 1.5.3, module version = 2.1.0
    Module class: X.Org Font Renderer
    ABI class: X.Org Font Renderer, version 0.6
    (II) Loading font FreeType
    (II) LoadModule: "record"
    (WW) Warning, couldn't open module record
    (II) UnloadModule: "record"
    (EE) Failed to load module "record" (module does not exist, 0)
    (II) LoadModule: "synaptics"
    (II) Loading /usr/lib/xorg/modules/input//synaptics_drv.so
    (II) Module synaptics: vendor="X.Org Foundation"
    compiled for 1.5.3, module version = 1.0.0
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 2.1
    (II) LoadModule: "evdev"
    (II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
    (II) Module evdev: vendor="X.Org Foundation"
    compiled for 1.5.3, module version = 2.1.2
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 2.1
    (II) LoadModule: "psmouse"
    (WW) Warning, couldn't open module psmouse
    (II) UnloadModule: "psmouse"
    (EE) Failed to load module "psmouse" (module does not exist, 0)
    (II) LoadModule: "intel"
    (II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so
    (II) Module intel: vendor="X.Org Foundation"
    compiled for 1.5.3, module version = 2.4.3
    Module class: X.Org Video Driver
    ABI class: X.Org Video Driver, version 4.1
    (II) LoadModule: "kbd"
    (II) Loading /usr/lib/xorg/modules/input//kbd_drv.so
    (II) Module kbd: vendor="X.Org Foundation"
    compiled for 1.5.3, module version = 1.3.2
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 2.1
    (II) LoadModule: "mouse"
    (II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
    (II) Module mouse: vendor="X.Org Foundation"
    compiled for 1.4.2, module version = 1.3.0
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 2.0
    (II) LoadModule: "synaptics"
    (II) Reloading /usr/lib/xorg/modules/input//synaptics_drv.so
    (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
    i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
    E7221 (i915), 915GM, 945G, 945GM, 945GME, 965G, G35, 965Q, 946GZ,
    965GM, 965GME/GLE, G33, Q35, Q33,
    Mobile Intel® GM45 Express Chipset,
    Intel Integrated Graphics Device, G45/G43, Q45/Q43
    (II) Primary Device is: PCI 00@00:02:0
    (II) resource ranges after xf86ClaimFixedResources() call:
    [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    (II) resource ranges after probing:
    [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
    [5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
    [6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
    [7] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [8] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    [9] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
    [10] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
    (II) Loading sub module "int10"
    (II) LoadModule: "int10"
    (II) Loading /usr/lib/xorg/modules//libint10.so
    (II) Module int10: vendor="X.Org Foundation"
    compiled for 1.5.3, module version = 1.0.0
    ABI class: X.Org Video Driver, version 4.1
    (II) Loading sub module "vbe"
    (II) LoadModule: "vbe"
    (II) Loading /usr/lib/xorg/modules//libvbe.so
    (II) Module vbe: vendor="X.Org Foundation"
    compiled for 1.5.3, module version = 1.1.0
    ABI class: X.Org Video Driver, version 4.1
    (II) Loading sub module "vgahw"
    (II) LoadModule: "vgahw"
    (II) Loading /usr/lib/xorg/modules//libvgahw.so
    (II) Module vgahw: vendor="X.Org Foundation"
    compiled for 1.5.3, module version = 0.1.0
    ABI class: X.Org Video Driver, version 4.1
    (**) intel(0): Depth 24, (--) framebuffer bpp 32
    (==) intel(0): RGB weight 888
    (==) intel(0): Default visual is TrueColor
    (II) intel(0): Integrated Graphics Chipset: Intel(R) 965GM
    (--) intel(0): Chipset: "965GM"
    (--) intel(0): Linear framebuffer at 0xE0000000
    (--) intel(0): IO registers at addr 0xF8100000
    (II) intel(0): 2 display pipes available.
    (==) intel(0): Using EXA for acceleration
    (II) Loading sub module "int10"
    (II) LoadModule: "int10"
    (II) Reloading /usr/lib/xorg/modules//libint10.so
    (II) intel(0): initializing int10
    (WW) intel(0): Bad V_BIOS checksum
    (II) intel(0): Primary V_BIOS segment is: 0xc000
    (II) intel(0): VESA BIOS detected
    (II) intel(0): VESA VBE Version 3.0
    (II) intel(0): VESA VBE Total Mem: 7616 kB
    (II) intel(0): VESA VBE OEM: Intel(r)GM965/PM965/GL960 Graphics Chip Accelerated VGA BIOS
    (II) intel(0): VESA VBE OEM Software Rev: 1.0
    (II) intel(0): VESA VBE OEM Vendor: Intel Corporation
    (II) intel(0): VESA VBE OEM Product: Intel(r)GM965/PM965/GL960 Graphics Controller
    (II) intel(0): VESA VBE OEM Product Rev: Hardware Version 0.0
    (II) Loading sub module "ddc"
    (II) LoadModule: "ddc"
    (II) Module "ddc" already built-in
    (II) Loading sub module "i2c"
    (II) LoadModule: "i2c"
    (II) Module "i2c" already built-in
    (II) intel(0): Output VGA using monitor section Monitor0
    (II) intel(0): I2C bus "CRTDDC_A" initialized.
    (II) intel(0): Output LVDS has no monitor section
    (II) intel(0): I2C bus "LVDSDDC_C" initialized.
    (II) intel(0): Attempting to determine panel fixed mode.
    (II) intel(0): I2C device "LVDSDDC_C:ddc2" registered at address 0xA0.
    (II) intel(0): EDID vendor "LEN", prod id 16433
    (II) intel(0): found backlight control method /sys/class/backlight/acpi_video0
    (II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" initialized.
    (II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" registered at address 0x70.
    (II) intel(0): I2C bus "SDVOB DDC Bus" initialized.
    (II) intel(0): Output TMDS-1 has no monitor section
    (II) intel(0): SDVOB: device VID/DID: 02:3C.06, clock range 25.0MHz - 200.0MHz
    (II) intel(0): SDVOB: 1 input channel
    (II) intel(0): SDVOB: TMDS0 output reported
    (II) intel(0): Current clock rate multiplier: 1
    (II) intel(0): EDID vendor "LEN", prod id 16433
    (II) intel(0): Output VGA disconnected
    (II) intel(0): Output LVDS connected
    (II) intel(0): Output TMDS-1 disconnected
    (II) intel(0): Using user preference for initial modes
    (II) intel(0): Output LVDS using initial mode 1280x800
    (II) intel(0): Monitoring connected displays enabled
    (II) intel(0): detected 512 kB GTT.
    (II) intel(0): detected 7676 kB stolen memory.
    (==) intel(0): video overlay key set to 0x101fe
    (==) intel(0): Will not try to enable page flipping
    (==) intel(0): Triple buffering disabled
    (==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
    (==) intel(0): DPI set to (96, 96)
    (II) Loading sub module "fb"
    (II) LoadModule: "fb"
    (II) Loading /usr/lib/xorg/modules//libfb.so
    (II) Module fb: vendor="X.Org Foundation"
    compiled for 1.5.3, module version = 1.0.0
    ABI class: X.Org ANSI C Emulation, version 0.4
    (II) Loading sub module "exa"
    (II) LoadModule: "exa"
    (II) Loading /usr/lib/xorg/modules//libexa.so
    (II) Module exa: vendor="X.Org Foundation"
    compiled for 1.5.3, module version = 2.4.0
    ABI class: X.Org Video Driver, version 4.1
    (II) Loading sub module "ramdac"
    (II) LoadModule: "ramdac"
    (II) Module "ramdac" already built-in
    (II) intel(0): Comparing regs from server start up to After PreInit
    (WW) intel(0): Register 0x61200 (PP_STATUS) changed from 0xc0000008 to 0xd0000009
    (WW) intel(0): PP_STATUS before: on, ready, sequencing idle
    (WW) intel(0): PP_STATUS after: on, ready, sequencing on
    (WW) intel(0): Register 0x70024 (PIPEASTAT) changed from 0x80000207 to 0x00000000
    (WW) intel(0): PIPEASTAT before: status: FIFO_UNDERRUN VSYNC_INT_STATUS SVBLANK_INT_STATUS VBLANK_INT_STATUS OREG_UPDATE_STATUS
    (WW) intel(0): PIPEASTAT after: status:
    (==) Depth 24 pixmap format is 32 bpp
    (II) do I need RAC? No, I don't.
    (II) resource ranges after preInit:
    [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b](OprD)
    [5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b](OprD)
    [6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b](OprD)
    [7] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [8] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    [9] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b](OprU)
    [10] 0 0 0x000003c0 - 0x000003df (0x20) IS[b](OprU)
    (II) intel(0): Kernel reported 1248000 total, 1 used
    (II) intel(0): I830CheckAvailableMemory: 4991996 kB available
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is -1, (No such device or address)
    drmOpenDevice: open result is -1, (No such device or address)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is -1, (No such device or address)
    drmOpenDevice: open result is -1, (No such device or address)
    drmOpenDevice: Open failed
    drmOpenByBusid: Searching for BusID pci:0000:00:02.0
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 11, (OK)
    drmOpenByBusid: drmOpenMinor returns 11
    drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
    (II) [drm] loaded kernel module for "i915" driver.
    (II) [drm] DRM interface version 1.3
    (II) [drm] DRM open master succeeded.
    (II) intel(0): [drm] Using the DRM lock SAREA also for drawables.
    (II) intel(0): [drm] framebuffer mapped by ddx driver
    (II) intel(0): [drm] added 1 reserved context for kernel
    (II) intel(0): X context handle = 0x1
    (II) intel(0): [drm] installed DRM signal handler
    (**) intel(0): Framebuffer compression disabled
    (**) intel(0): Tiling enabled
    (==) intel(0): VideoRam: 262144 KB
    (II) intel(0): Attempting memory allocation with tiled buffers.
    (II) intel(0): Tiled allocation successful.
    (II) intel(0): [drm] Registers = 0xf8100000
    (II) intel(0): [drm] ring buffer = 0xe0000000
    (II) intel(0): [drm] mapped front buffer at 0xe0100000, handle = 0xe0100000
    (II) intel(0): [drm] mapped back buffer at 0xe1a00000, handle = 0xe1a00000
    (II) intel(0): [drm] mapped depth buffer at 0xe2040000, handle = 0xe2040000
    (II) intel(0): [drm] mapped classic textures at 0xe2680000, handle = 0xe2680000
    (II) intel(0): [drm] Initialized kernel agp heap manager, 33554432
    (II) intel(0): [dri] visual configs initialized
    (II) intel(0): Page Flipping disabled
    (II) intel(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
    (II) EXA(0): Offscreen pixmap area of 19660800 bytes
    (II) EXA(0): Driver registered support for the following operations:
    (II) Solid
    (II) Copy
    (II) Composite (RENDER acceleration)
    (==) intel(0): Backing store disabled
    (==) intel(0): Silken mouse enabled
    (II) intel(0): Initializing HW Cursor
    (II) intel(0): [DRI] installation complete
    (II) intel(0): Current clock rate multiplier: 1
    (II) intel(0): xf86BindGARTMemory: bind key 0 at 0x0077f000 (pgoffset 1919)
    (II) intel(0): xf86BindGARTMemory: bind key 1 at 0x01a00000 (pgoffset 6656)
    (II) intel(0): xf86BindGARTMemory: bind key 2 at 0x02040000 (pgoffset 8256)
    (II) intel(0): xf86BindGARTMemory: bind key 3 at 0x02680000 (pgoffset 9856)
    (II) intel(0): Fixed memory allocation layout:
    (II) intel(0): 0x00000000-0x0001ffff: ring buffer (128 kB)
    (II) intel(0): 0x00020000-0x00029fff: HW cursors (40 kB)
    (II) intel(0): 0x0002a000-0x00031fff: logical 3D context (32 kB)
    (II) intel(0): 0x00032000-0x00043fff: exa G965 state buffer (72 kB)
    (II) intel(0): 0x00044000-0x00044fff: overlay registers (4 kB)
    (II) intel(0): 0x00045000-0x00045fff: power context (4 kB)
    (II) intel(0): 0x00100000-0x0073ffff: front buffer (6400 kB) X tiled
    (II) intel(0): 0x00740000-0x019fffff: exa offscreen (19200 kB)
    (II) intel(0): 0x0077f000: end of stolen memory
    (II) intel(0): 0x01a00000-0x0203ffff: back buffer (6400 kB) X tiled
    (II) intel(0): 0x02040000-0x0267ffff: depth buffer (6400 kB) Y tiled
    (II) intel(0): 0x02680000-0x0467ffff: classic textures (32768 kB)
    (II) intel(0): 0x10000000: end of aperture
    (II) intel(0): using SSC reference clock of 100 MHz
    (II) intel(0): Selecting standard 18 bit TMDS pixel format.
    (II) intel(0): Output configuration:
    (II) intel(0): Pipe A is off
    (II) intel(0): Display plane A is now disabled and connected to pipe A.
    (II) intel(0): Pipe B is on
    (II) intel(0): Display plane B is now enabled and connected to pipe B.
    (II) intel(0): Output VGA is connected to pipe none
    (II) intel(0): Output LVDS is connected to pipe B
    (II) intel(0): Output TMDS-1 is connected to pipe none
    (II) intel(0): [drm] dma control initialized, using IRQ 760
    (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    (II) intel(0): using SSC reference clock of 100 MHz
    (II) intel(0): Selecting standard 18 bit TMDS pixel format.
    (**) Option "dpms" "true"
    (**) intel(0): DPMS enabled
    (II) intel(0): Set up textured video
    (II) intel(0): Set up overlay video
    (II) intel(0): direct rendering: Enabled
    (--) RandR disabled
    (II) Initializing built-in extension MIT-SHM
    (II) Initializing built-in extension XInputExtension
    (II) Initializing built-in extension XTEST
    (II) Initializing built-in extension XKEYBOARD
    (II) Initializing built-in extension XC-APPGROUP
    (II) Initializing built-in extension SECURITY
    (II) Initializing built-in extension XINERAMA
    (II) Initializing built-in extension XFIXES
    (II) Initializing built-in extension RENDER
    (II) Initializing built-in extension RANDR
    (II) Initializing built-in extension COMPOSITE
    (II) Initializing built-in extension DAMAGE
    (II) Initializing built-in extension XEVIE
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 12, (OK)
    drmOpenByBusid: Searching for BusID pci:0000:00:02.0
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 12, (OK)
    drmOpenByBusid: drmOpenMinor returns 12
    drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
    (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    (II) AIGLX: enabled GLX_texture_from_pixmap with driver support
    (II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/i965_dri.so
    (II) GLX: Initialized DRI GL provider for screen 0
    (II) intel(0): Setting screen physical size to 304 x 190
    (**) Option "CoreKeyboard"
    (**) Keyboard0: always reports core events
    (**) Option "Protocol" "standard"
    (**) Keyboard0: Protocol: standard
    (**) Option "AutoRepeat" "500 30"
    (**) Option "XkbRules" "xorg"
    (**) Keyboard0: XkbRules: "xorg"
    (**) Option "XkbModel" "pc105"
    (**) Keyboard0: XkbModel: "pc105"
    (**) Option "XkbLayout" "us"
    (**) Keyboard0: XkbLayout: "us"
    (WW) Option "XkbVariant" requires an string value
    (**) Option "CustomKeycodes" "off"
    (**) Keyboard0: CustomKeycodes disabled
    (**) Option "Protocol" "IMPS/2"
    (**) USB Mouse: Device: "/dev/input/mice"
    (**) USB Mouse: Protocol: "IMPS/2"
    (**) Option "SendCoreEvents" "true"
    (**) Option "CorePointer"
    (**) USB Mouse: always reports core events
    (**) Option "Device" "/dev/input/mice"
    (**) Option "Buttons" "5"
    (==) USB Mouse: Emulate3Buttons, Emulate3Timeout: 50
    (**) Option "ZAxisMapping" "4 5"
    (**) USB Mouse: ZAxisMapping: buttons 4 and 5
    (**) USB Mouse: Buttons: 9
    (**) USB Mouse: Sensitivity: 1
    (II) Synaptics touchpad driver version 1.0.0
    (--) SynapticsTouchpad auto-dev sets device to /dev/input/event7
    (**) Option "Device" "/dev/input/event7"
    (II) SynapticsTouchpad: x-axis range 1472 - 5472
    (II) SynapticsTouchpad: y-axis range 1408 - 4448
    (II) SynapticsTouchpad: pressure range 0 - 255
    (II) SynapticsTouchpad: finger width range 0 - 0
    (II) SynapticsTouchpad: buttons: left right middle double triple
    (**) Option "SHMConfig" "true"
    (**) Option "LeftEdge" "1700"
    (**) Option "RightEdge" "5600"
    (**) Option "TopEdge" "1700"
    (**) Option "BottomEdge" "4800"
    (**) Option "MaxTapTime" "120"
    (**) Option "VertScrollDelta" "140"
    (**) Option "HorizScrollDelta" "100"
    (**) Option "VertEdgeScroll" "true"
    (**) Option "HorizEdgeScroll" "true"
    (**) Option "CornerCoasting" "true"
    (**) Option "TapButton1" "1"
    (**) Option "TapButton2" "2"
    (**) Option "TapButton3" "3"
    (--) SynapticsTouchpad touchpad found
    (**) Option "AlwaysCore" "true"
    (**) Option "SendCoreEvents"
    (**) SynapticsTouchpad: always reports core events
    (**) Option "Protocol" "ImPS/2"
    (**) UltraNav Trackpoint: Device: "/dev/input/mice"
    (**) UltraNav Trackpoint: Protocol: "ImPS/2"
    (**) Option "CorePointer" "False"
    (**) UltraNav Trackpoint: doesn't report core events
    (**) Option "Device" "/dev/input/mice"
    (**) Option "Emulate3Buttons" "off"
    (**) Option "ZAxisMapping" "4 5"
    (**) UltraNav Trackpoint: ZAxisMapping: buttons 4 and 5
    (**) Option "EmulateWheel" "on"
    (**) Option "EmulateWheelButton" "2"
    (**) Option "EmulateWheelTimeout" "250"
    (**) Option "XAxisMapping" "6 7"
    (**) UltraNav Trackpoint: XAxisMapping: buttons 6 and 7
    (**) Option "YAxisMapping" "4 5"
    (**) UltraNav Trackpoint: YAxisMapping: buttons 4 and 5
    (**) UltraNav Trackpoint: EmulateWheel, EmulateWheelButton: 2, EmulateWheelInertia: 10, EmulateWheelTimeout: 250
    (**) UltraNav Trackpoint: Buttons: 11
    (**) UltraNav Trackpoint: Sensitivity: 1
    (II) evaluating device (Keyboard0)
    (II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
    (II) evaluating device (USB Mouse)
    (II) XINPUT: Adding extended input device "USB Mouse" (type: MOUSE)
    (II) evaluating device (SynapticsTouchpad)
    (II) XINPUT: Adding extended input device "SynapticsTouchpad" (type: TOUCHPAD)
    (II) evaluating device (UltraNav Trackpoint)
    (II) XINPUT: Adding extended input device "UltraNav Trackpoint" (type: MOUSE)
    (II) USB Mouse: ps2EnableDataReporting: succeeded
    (--) SynapticsTouchpad touchpad found
    (II) UltraNav Trackpoint: ps2EnableDataReporting: succeeded
    (II) config/hal: Adding input device ThinkPad HDAPS joystick emulation
    (EE) config/hal: NewInputDeviceRequest failed
    (II) config/hal: Adding input device ThinkPad Extra Buttons
    (EE) config/hal: NewInputDeviceRequest failed
    (II) config/hal: Adding input device ThinkPad HDAPS accelerometer data
    (EE) config/hal: NewInputDeviceRequest failed
    (II) config/hal: Adding input device Macintosh mouse button emulation
    (EE) config/hal: NewInputDeviceRequest failed
    (II) config/hal: Adding input device TPPS/2 IBM TrackPoint
    (EE) config/hal: NewInputDeviceRequest failed
    (II) config/hal: Adding input device SynPS/2 Synaptics TouchPad
    (EE) config/hal: NewInputDeviceRequest failed
    (II) config/hal: Adding input device AT Translated Set 2 keyboard
    (EE) config/hal: NewInputDeviceRequest failed
    (II) config/hal: Adding input device Video Bus
    (EE) config/hal: NewInputDeviceRequest failed
    (II) intel(0): EDID vendor "LEN", prod id 16433
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1328 1360 1405 800 803 809 822 -hsync -vsync (49.3 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 57.75 1280 1328 1360 1405 800 803 809 822 -hsync -vsync (41.1 kHz)
    (II) intel(0): EDID vendor "LEN", prod id 16433
    (II) intel(0): EDID vendor "LEN", prod id 16433
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1328 1360 1405 800 803 809 822 -hsync -vsync (49.3 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 57.75 1280 1328 1360 1405 800 803 809 822 -hsync -vsync (41.1 kHz)
    (II) intel(0): EDID vendor "LEN", prod id 16433
    (II) intel(0): EDID vendor "LEN", prod id 16433
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1328 1360 1405 800 803 809 822 -hsync -vsync (49.3 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 57.75 1280 1328 1360 1405 800 803 809 822 -hsync -vsync (41.1 kHz)
    (II) intel(0): EDID vendor "LEN", prod id 16433
    (II) intel(0): EDID vendor "LEN", prod id 16433
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1328 1360 1405 800 803 809 822 -hsync -vsync (49.3 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 57.75 1280 1328 1360 1405 800 803 809 822 -hsync -vsync (41.1 kHz)
    (II) intel(0): EDID vendor "LEN", prod id 16433
    (II) intel(0): EDID vendor "LEN", prod id 16433
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1328 1360 1405 800 803 809 822 -hsync -vsync (49.3 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 57.75 1280 1328 1360 1405 800 803 809 822 -hsync -vsync (41.1 kHz)
    (II) intel(0): EDID vendor "LEN", prod id 16433
    (II) intel(0): EDID vendor "LEN", prod id 16433
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1328 1360 1405 800 803 809 822 -hsync -vsync (49.3 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 57.75 1280 1328 1360 1405 800 803 809 822 -hsync -vsync (41.1 kHz)
    (II) intel(0): EDID vendor "LEN", prod id 16433
    (II) intel(0): EDID vendor "LEN", prod id 16433
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1328 1360 1405 800 803 809 822 -hsync -vsync (49.3 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 57.75 1280 1328 1360 1405 800 803 809 822 -hsync -vsync (41.1 kHz)
    (II) intel(0): EDID vendor "LEN", prod id 16433
    (II) intel(0): EDID vendor "LEN", prod id 16433
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1328 1360 1405 800 803 809 822 -hsync -vsync (49.3 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 57.75 1280 1328 1360 1405 800 803 809 822 -hsync -vsync (41.1 kHz)
    (II) intel(0): EDID vendor "LEN", prod id 16433

    pendor wrote:Helpful hint:
    downgrading gnome-session to 2.24.1 (keeping xorg 1.5.3) seems to correct the high CPU usage problem. This  tip comes from the gnome thread. It appears to break gnome screensaver, but I can live with that. Hardware: MSI VR340 laptop with Intel GM965 video.
    Hope it helps.
    Yes this solution works! Thx for the hint! For everybody who forgot how to downgrade packages here the solution:
    I downgraded like this: sudo pacman -U gnome-session-2.24.3-1-i686.pkg.tar.gz
    Maybe you have another gnome-session in your pacman cache. More information about downgrading packages:
    http://wiki.archlinux.org/index.php/Downgrade_packages
    Still hope that xorg 1.6 will come soon to the official repository

  • [solved] Xorg 1.6 segfault

    Since xorg-server 1.6 was released, X has been dying on me... I believe I can always reproduce this by switching to a virtual console and back to X.  Once X dies, it's pretty much over; computer won't respond to anything except magic sysreqs.
    Apr 13 21:33:32 ivy kernel: Xorg[4287]: segfault at 20 ip 00007f880243c980 sp 00007fff0e120898 error 4 in libdrm_intel.so.1.0.0[7f880243b000+9000]
    Apr 13 21:33:32 ivy kernel: Xorg:4287 freeing invalid memtype d0000000-e0000000
    Apr 13 21:33:32 ivy gdm-binary[4283]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
    Apr 13 21:33:32 bonobo-activation-server (mindless-27023): could not associate with desktop session: Failed to connect to socket /tmp/dbus-LE2w6IiDqW: Connection refused
    Apr 13 21:33:33 ivy acpid: client connected from 27053[0:0]
    Apr 13 21:33:33 ivy acpid: 1 client rule loaded
    Apr 13 21:33:35 ivy kernel: [drm:i915_setparam] *ERROR* unknown parameter 4
    Apr 13 21:33:36 ivy kernel: Xorg:27053 conflicting memory types d0000000-e0000000 write-combining<->uncached-minus
    Apr 13 21:33:36 ivy kernel: reserve_memtype failed 0xd0000000-0xe0000000, track write-combining, req write-combining
    Apr 13 21:33:36 ivy kernel: Xorg:27053 conflicting memory types d0000000-e0000000 write-combining<->uncached-minus
    Apr 13 21:33:36 ivy kernel: reserve_memtype failed 0xd0000000-0xe0000000, track write-combining, req write-combining
    Apr 13 21:33:36 ivy kernel: Xorg:27053 conflicting memory types d0000000-e0000000 write-combining<->uncached-minus
    Apr 13 21:33:36 ivy kernel: reserve_memtype failed 0xd0000000-0xe0000000, track write-combining, req write-combining
    Apr 13 21:33:36 ivy kernel: Xorg:27061 freeing invalid memtype d0000000-e0000000
    Apr 13 21:33:36 ivy kernel: Xorg:27053 conflicting memory types d0000000-e0000000 write-combining<->uncached-minus
    Apr 13 21:33:36 ivy kernel: reserve_memtype failed 0xd0000000-0xe0000000, track write-combining, req write-combining
    Apr 13 21:33:36 ivy kernel: Xorg:27062 freeing invalid memtype d0000000-e0000000
    Apr 13 21:33:37 ivy kernel: Xorg:27053 conflicting memory types d0000000-e0000000 write-combining<->uncached-minus
    Apr 13 21:33:37 ivy kernel: reserve_memtype failed 0xd0000000-0xe0000000, track write-combining, req write-combining
    Apr 13 21:33:37 ivy kernel: Xorg:27063 freeing invalid memtype d0000000-e0000000
    Apr 13 21:33:37 bonobo-activation-server (mindless-27071): could not associate with desktop session: Failed to connect to socket /tmp/dbus-LE2w6IiDqW: Connection refused
    Apr 13 21:34:54 ivy kernel: Xorg:27053 freeing invalid memtype d0000000-e0000000
    Apr 13 21:34:59 ivy acpid: client 4287[0:0] has disconnected
    Apr 13 21:34:59 ivy acpid: client 27053[0:0] has disconnected
    Apr 13 21:35:11 ivy ddclient[4237]: WARNING: cannot connect to checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname 'checkip.dyndns.org'
    Apr 13 21:35:47 ivy kernel: SysRq : Keyboard mode set to system default
    Apr 13 21:35:48 ivy kernel: SysRq : Terminate All Tasks
    Apr 13 21:35:48 ivy acpid: exiting
    Apr 13 21:35:48 ivy ntpd[4215]: ntpd exiting on signal 15
    Apr 13 21:35:48 ivy ntpd_initres[4221]: ntpd exiting on signal 15
    Apr 13 21:35:48 ivy dhcpcd[4311]: eth0: received SIGTERM, stopping
    Apr 13 21:35:48 ivy syslog-ng[3773]: Termination requested via signal, terminating;
    Last edited by MindlessXD (2009-04-14 06:50:05)

    Intel GM965 with the "intel" driver
    I have an external monitor connected in case that makes any difference (this is a laptop)
    xorg.conf
    Section "Module"
    Load "synaptics"
    EndSection
    Section "ServerFlags"
    Option "DontVTSwitch" "false"
    Option "DontZap" "false"
    Option "DontZoom" "false"
    Option "AllowDeactivateGrabs" "true"
    Option "AllowClosedownGrabs" "true"
    EndSection
    Section "ServerLayout"
    Identifier "X.org Configured"
    Screen 0 "Screen0" 0 0
    InputDevice "Mouse0" "CorePointer"
    EndSection
    Section "InputDevice"
    <snip>
    EndSection
    Section "Monitor"
    # DisplaySize 330 210 # mm
    Identifier "LVDS"
    EndSection
    Section "Monitor"
    Identifier "VGA"
    EndSection
    Section "Monitor"
    Identifier "TV"
    Option "Ignore" "true"
    EndSection
    Section "Device"
    Identifier "Card0"
    Driver "intel"
    VendorName "Intel Corporation"
    BoardName "Mobile GM965/GL960 Integrated Graphics Controller"
    BusID "PCI:0:2:0"
    Option "DRI" "true"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "LVDS"
    SubSection "Display"
    Virtual 2960 1050
    EndSubSection
    EndSection
    Section "Extensions"
    Option "Composite" "Enable"
    EndSection
    Section "DRI"
    Mode 0666
    EndSection
    lspci
    00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
    00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
    00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
    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.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03)
    00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (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)
    06:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)
    07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
    08:05.0 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev 02)
    08:05.2 SD Host controller: O2 Micro, Inc. Integrated MMC/SD Controller (rev 02)
    08:05.3 Mass storage controller: O2 Micro, Inc. Integrated MS/xD Controller (rev 01)
    Last edited by MindlessXD (2009-04-14 03:35:41)

Maybe you are looking for

  • How do i Delete an email address on my computer

    I have an email account on my linux based computer. No longer a valid email address. and would like to remove it.

  • How to set GPRS on iphone 4 with ATT ?

    i need to get my internet work by gprs on my iphone , i'm using ATT carrier , anyone show me how to set it thanks ...............

  • N80 phone recovery

    Every time i try to update my n80 with nsu the phone recovery message comes up. I take out the battery and charger, put them back in and select pc suite on the phone, then click retry in nsu. The same problem then happens again. How can i update the

  • +filter +ID +CAN +XNET

    In the XNET Bus Monitor there is an option to "Filter-ID's". How is it working in the code? Is there any setting for the session to get only specific frames, or the bus monitor gets all the frames and ignores those which are not in the list? A second

  • Upgrade our 8.0.3 CUCM to version 9.1.X

                       Hi All, We are planning to  upgrade the our cucm 8.0.3 to 9.1.x Can anyone  tell us the steps for the upgradation. We are using the extension mobility. Prior to upgrade we already upgraded the router IOS to c2900-universalk9-mz.SPA