Display overclocking

So has anyone done this? I am talking about the refresh rate overclocking
i don't own a macbook pro, but if this is possible i'd consider it.
If you are in Windows with the nvidia control panel, you can go open it and go to change resolution > customize > create custom resolution and create a new refresh rate.
On my 6 year old vostro 1310 laptop, I took the display from 1280x800 to 1280x800 at 90hz.
You might be asking why, and the reason is simple, games are way smoother, like quake live. Can't LG like a baws with 60hz (irrelvent to my question but http://www.youtube.com/watch?v=gXwLk08WL98
anyway i also did this on my sager np8130 laptop, and have run it at 95hz at native res 1920x1080 for over 6 months now.
http://forum.notebookreview.com/sager-clevo/660283-you-guys-know-you-can-overclo ck-lcd-8.html
i started a discussion there
so anyone willing to try this? I'd recommend trying 75hz first. Not that I can believe you can even damage your display. I ran my sager np8130 at 140hz, and all that happens is the screen colors are extremely compressed since it's too much for the lcd's controller.
[img]http://dl.dropbox.com/u/46294175/gamespot/macbookpro.png[/img]
EDIT:I don't think you guys can do this, the desktop display is controlled by the intel gpu, and unless you can force the nvidia card to be on at all times, I don't think you can do this ; /

@Shootist-
Please click on my profile and email me. I need to put together a Windows system for a neighbor and I'm long out of the Windows hardware game.
Thanks,
Clinton

Similar Messages

  • Installed Premiere Pro CS4 but video display does not work?

    I just got my copy of CS$. After installing Premiere I found two things that seem very wrong:
    1) video display does not work, not even the little playback viewer next to improted film clips located on the project / sequence window. Audio works fine.
    2) the UI is way too slow for my big beefy system.
    My pc is a dual boot Vista-32 and XP system with 4GB of memory installed and nvidia geforce 280 graphics board with plenty of GPU power. The CS4 is installed on the Vista-32 partition. My windows XP partition on the same PC with Premiere CS2 works great and real fast.
    Any ideas how to solve this CS4 install issue?
    Ron

    I would like to thank Dan, Hunt, and Haram:
    The problem is now very clear to me. The problem only shows up with video footage imported into PP CS4 encoded with "MS Video 1" codec. So this seems to be a bug. The codec is very clearly called out and supported within various menues but video with this codec just will not play in any monitor or preview window. In addition the entire product looks horrible with respect to performance while PP CS4 trys its best to play the video. Audio will start playing after about 30 seconds. And once in awhile part of video shows up at the wrong magnification before blanking out again.
    My suggestion to the Adobe team: fix the bug and add some sample footage to the next release so new installations can test their systems with known footage.
    My PC is brand new with the following "beefy" components:
    Motherboard
    nForce 790i SLI FTW
    Features:
    3x PCI Express x16 graphics support
    PCI Express 2.0
    NVIDIA SLI-Ready (requires multiple NVIDIA GeForce GPUs)
    DDR3-2000 SLI-Ready memory w/ ERP 2.0 (requires select third party system memory)
    Overclocking tools
    NVIDIA MediaSheild w/ 9 SATA 3 Gb/sec ports
    ESA Certified
    NVIDIA DualNet and FirstPacket Ethernet technology
    Registered
    CPU: Intel Core 2 Quad Q9550
    S-Spec: SLAWQ
    Ver: E36105-001
    Product Code: BX80569Q9550
    Made in Malaysia
    Pack Date: 09/04/08
    Features:
    Freq.: 2.83 GHz
    L2 Cache: 12 MHz Cache
    FSB: 1333 MHz (MT/s)
    Core: 45nm
    Code named: Yorkfield
    Power:95W
    Socket: LGA775
    Cooling: Liquid Cooled
    NVIDIAGeForce GTX 280 SC graphics card
    Features:
    1 GB of onboard memory
    Full Microsoft DirectX 10
    NVIDIA 2-way and 3-way SLI Ready
    NVIDIA PureVideo HD technology
    NVIDIA PhysX Ready
    NVIDI CUDA technology
    PCI Express 2.0 support
    Dual-link HDCP
    OpenGL 2.1 Capaple
    Output: DVI (2 dual-link), HDTV
    Western Digital
    2 WD VelociRaptor 300 GB SATA Hard Drives configured as Raid 0
    Features:
    10,000 RPM, 3 Gb/sec transfer rate
    RAM Memory , Corsair 4 GB (2 x 2 GB) 1333 MHz DDR3
    p/n: TW3X4G1333C9DHX G
    product: CM3X2048-1333C9DHX
    Features:
    XMS3 DHX Dual-Path 'heat xchange'
    2048 x 2 MB
    1333 MHz
    Latency 9-9-9-24-2T
    1.6V ver3.2

  • Msi g4 4200 64meg overclocking probs..

        using xp pro as my OS.  When I go into the msi tabs under display properties, and hit the tab to auto adjust the memory clock,  the circle test runs into some kinda failure and therefore i cant adjust my memory clock.  What gives and does anyone know how i can fix this.  When i boot using 98se it works fine...i hate windows.
    any advice would be greatly valued.  i dont think i need to overclock this beast, but not being able to really bothers me
              amd 2100+
              msi k7n2
              512m kingston 2700
              creative 5.1 live
              g4 4200
              broadband cable connection
      ...who wants to smoke and who wants to get smoked.

    scottyrox,
    Download the latest Detonator4 Drivers from the nVidia Website. Install them.
    Delete the file msicpl.dll from your windows directory.
    Use notepad to make a new file and put in it what I quoted below and then save it with the .reg extension.
    quote:
    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINESOFTWARENVIDIA CorporationGlobalNVTweak]
    "Coolbits"=dword:ffffffff
    "NvCplEnableAGPSettingsPage"=dword:00000001
    "NvCplEnableAdditionalInfoPage"=dword:00000001
    "NvCplEnableClearViewPage"=dword:00000001
    That will open all the extra options in the Detonator4 Drivers including the Core and RAM Speeds for your GF4.
    Take Care,
    Richard

  • Recent Conversation with MSI and Neo4 overclocking "thing"

    I had a recent email transaction with MSI if anyone is interested. I tried my best to represent the group, and I know we all experience the problem a little bit different which is why it has been hard to explain and fix. I tried to give them the best info to duplicate the issue in the lab. It seems clear at this point that MSI still isn't duplicating the issue. They are using 166 Mem Clock Index, and the HT freq of 3x and still not understanding the issue, hopefully I have gave them a guide to duplicate what we have been trying to say. Yes I have explained this to MSI before but I really feel I am getting somewhere with my last 2 emails. Once we get them to duplicate the results then I think we will all have our solution shortly. Before anyone says anything negative, at least they aren't saying, oh that's an overclocking problem we don't deal with that. Also remember how long it has taken to get many people to see the issue, this isn't easy to understand so just stay cool, don't say negative sh-t if you reply and we'll see how this pans out. It was actully kind of hard since I am sitting in a hotel room 500 miles away from the motherboard but I was able to use modbin6 to view the BIOS and since I have done this about 7 zillion times I remember the settings LMAO. They have their Venice to 2750, not bad... 
    Hello MSI Engineer,
    The information you requested. The data you sent shows a Venice running at 166 Memclock index value at HT at 3x, the goal is to run at 200 Memclock Index and HT at 4x. In order to duplicate this issue in the lab here is my recommendation. It MUST be tried with a CBBID Winchester RevD CPU and a Venice Rev E CPU and the Gskill memory you have in dual channel. The issue happens everytime with a CBBID Winchester and less often with Venice.
    Starting with the Venice 3500+, Set the following in BIOS
    [Memclock Index] 200
    [CAS# latency (Tcl)] 3
    [Min RAS active] 11
    [RAS to CAS delay] 6
    [Row Precharge] 6
    [User config mode] manual
    [bottom of 32 bit] (default)
    [1T/2T] 1T
    [Read Preamble] 6ns (default)
    [Async Latency] 6ns (default)
    [S/W mem hole] Disable (default)
    [H/W mem hole] Disable (default)
    [MTRR mapping] Continuous (default)
    [High Performance] manual
    [Agreessive timing] Disable
    [Dynamic Overclocking] Disable
    [Adjust CPU FSB Frequency] 200
    [HT Frequncy] 4
    [HT Width] 16 up 16 down
    [CPU Spread] Disable
    [SATA Spread] Disable
    [PCI Spread] Disable
    [PCIe Clock] 101
    [SSE/SSE2] Enable
    [CnQ] Disable
    [CPU Ratio] 11x
    [Adjust CPU VID] 1.45
    [Extra CPU Voltage] your choice for stability
    [Mem Volt] your choice for stability
    [NF4 Volt] your choice for stability
    Now boot into Windows. Using Clockgen, increase HTT to 250. This should be stable based on your screen shot and your RAM modules. Now having a CPU 2750Mhz, RAM at 250Mhz, and a HT of 4x250(1000). Test for stablity with Prime95 or other Stress Testing tool. Now we can say motherboard is stable at 2750Mhz CPU, 250Mhz RAM, and HT 4x250(1000). Now return to the BIOS at set the following
    [Adjust CPU FSB Frequency] 250
    This reults in a no POST condition for me and others. Now install the CBBID, except you will have to set a lower CPU max speed based on CBBID overclocking potential. In the BIOS, Return [Adjust CPU FSB frequency] to 200, Perhaps [CPU ratio] of 10x or 9x but a [Memory Clock Index] 200Mhz. Boot to Windows and use Clockgen to raise HTT to 250 again. Once you find a [CPU Ratio] that will have a STABLE overclock with a 250HTT. Return to the BIOS and set [Adjust CPU FSB Frequency] to 250. Try and POST. Try this experiment with the 3.1, 3.3, and 3.4 BIOS's. For the CBBID and the 3.1 BIOS you should be able to change the [HT Freq] to 3x, 2x or 1x and get a POST with [FSB Freq] 250, [Memclock Index] 200, and a known stable [CPU Ratio] you found in Windows. The 3.3, and 3.4 BIOS have made this work around not possible. Why does [HT Freq] 4x work in windows but not at POST time?
    As a side note. The 1.3 BIOS for the 7125 works with the Venice, and the 1.4 and 1.5 do NOT. So somewhere between the 1.3 and 1.4 MSI created the issue on the Venice. Perhaps that is where you can find the answer and solution to the problem.
    Here are some articles that describe the issue on a ECS and Chaintech board that were remidied by a BIOS update. So the problem is not uncommon and should be able to be fixed.
    http://www.xbitlabs.com/articles/mainboards/display/chaintech-nforce4_6.html
    http://www.xbitlabs.com/articles/mainboards/display/ecs-kn1-extreme_9.html
    Here is some other users data of NF4 SLI and Ultra MSI Neo4's if you want to see some other BIOS settings.
    https://forum-en.msi.com/index.php?topic=81364.0
    Here is a screen shot of my Neo4 Plat SLI (MS-7100) 3.1 BIOS and CBBID Winchester(The Venice will NOT POST at all above [Adj CPU Freq] ~219-229 under any situation but is stable in Windows at HTT 250 with Clockgen). The system is stable and POST's when [HT Freq] is 3x, it will NOT at [HT freq] 4x which is stable in windows but won't POST.
    http://home.comcast.net/~aicjofs/cbbidMSI2501.jpg
    Here is another screenshot of the Asus A8N Plat SLI with all peripherals the same. Only changed the motherboard. This is POSTing at [HT Freq] 4x. This is just as a reference that the components do indeed POST with [Adjust FSB freq] 250, [Memclock Index] 200, and [HT Freq] 4x. This board will POST both my 3200+ Venice and Winchester CBBID at the settings described above.
    http://home.comcast.net/~aicjofs/cbbid250asus1.jpg
    The following are my BIOS settings that will create a non-POST condition, but the board is stable at these settings when ADJUSTED FROM WINDOWS.
    [ADVANCED BIOS]
    [Gate A20] Enable
    [APIC] Enable
    [MPS Table] 1.4
    [Boot OS2] No
    [ADVANCED CHIPSET]
    [System BIOS Cacheable] Disabled
    for newer BIOS
    [SLI Brodcast apeture] Whatever default is.
    [INTEGRATE PERIPHERALS]
    [Onboard IDE 0 and 1] Enabled all channels in Auto
    [IDE DMA] Enabled
    [SATA 1,2,3,4] Enabled
    [IDE PREFETCH] Enabled
    [NVDA RAID] Enabled
    [all IDE raid channels] Disabled
    [all SATA raid channels] Enabled
    [On Chip USB] 1.1-2.0
    [USB KB/Storage] Disabled
    [NVDA LAN] Enabled
    [NVDA ROM] Disabled
    [Onboard VIA 1394] Enabled
    [Marvell Gigabit] Disabled
    [Onboard Creative] Enabled
    [SiI3132] Disabled
    [FDC] Enable
    [Serial Ports] Disabled
    [Parallel Port] Disabled
    [POWER MANAGMENT] all defaults
    [PNP/PCI]
    [Init display] PCIe
    [Resources] Auto
    [PCI Express Max Payload] 4096
    [CELL MENU]
    [Timing mode] manual
    [Memclock index value(MHz)] 200
    [CAS# latency (Tcl)] 3
    [Min RAS active] 8
    [RAS to CAS delay] 4
    [Row Precharge] 4
    [Row cycle time] Auto
    [Row refresh] Auto
    [Row to Row delay] Auto
    [Write Recovery] Auto
    [Write to Read] Auto changing this to known working value will lock system sometimes
    [Read to Write] Auto changing this to known working value will lock system sometimes
    [Refresh] Auto
    [User config mode] manual
    [bottom of 32 bit] whatever it defaults to
    [1T/2T] 1T
    [Read Preamble] 6ns
    [Async Latency] 6ns Attempts to change this to 8ns will lock system
    [S/W mem hole] Disable
    [H/W mem hole] Disable
    [MTRR mapping] Continuous
    [High Performance] manual
    [Agreessive timing] Disable
    [Dynamic Overclocking] Disable
    [Adjust CPU FSB Frequency] 250
    [HT Frequncy] 4 (For 1000Mhz)
    [HT Width] 16 up 16 down
    [CPU Spread] Disable
    [SATA Spread] Disable
    [PCI Spread] Disable
    [PCIe Clock] 101
    [SSE/SSE2] Enable
    [CnQ] Disable
    [CPU Ratio] 10x
    [Adjust CPU VID] 1.45
    [Extra CPU Voltage] +9.9%
    [Mem Volt] 2.7v
    [NF4 Volt] 1.65v
    BIOS Tested 3.0, 3.1, 3.2, 3.3, 3.4. I have not tested 3.51 but forum users are still not getting positive results
    -------------- Original message --------------
    Dear Aicjofs
    This is MSI technical support engineer from Taiwan.
    We receive some message from MSI LA office & Anandtech.com.
    We are sorry for inconvinence experience when you try to Overclock MS-7100.
    We hope to contact with you directly and help you to solve it.
    Depends on related message from others, we know that you have several problem for MS-7100 overclocking.
    According to your info at MSI Forum, Here is your system configuration:
    Neo4 Plat SLI(MS-7100) 3.1 BIOS
    3200+ Venice (8x313) @ 2500Mhz
    Patriot PC4000 (200:133) 2.5-3-3-7
    HT x3
    Aopen 6800GT @ Ultra speed
    AthenaPower 500W 3.3v - 26a 5v - 47a 12v - 28a
    Could you give us more info about what changed item inside your BIOS?
    [Memclock index value(MHz)]
    [CAS# latency (Tcl)]
    [Adjust CPU FSB Frequency]
    [HT Frequncy]
    [Adjust CPU VID]
    [Extra CPU Voltage]¡Kor others
    We try to Overclock MS-7100 with BIOS v3.2 and 3500+ (Venice core).
    CPU ADA3500DAA4BW ABBWE made in Malaysia
    Memory G-skill PC4400 512MB*2 (Dual Channel)
    We only change some item inside BIOS as: (Based on Optimized defaults)
    [Memclock index value (MHz)] à166
    [CAS# latency (Tcl)] à 3
    [Adjust CPU FSB Frequency] à250
    [HT Frequncy] à3x
    [Adjust CPU VID] à 1.450V
    [Extra CPU Voltage] àOver VID 6.6%
    We will try to find similar CPU as yours to test it.
    If possible, please tell us the CPU OPN number like we listed. (ADA3500DAA4BW)
    We also help to know any other info that you can provide.
    If possible, please help to tell us more setting and system info.
    Thanks!
    Waiting for your responding.
    Best Regards!
    Technical Support Engineer
    Technical Support Department
    E-mail: msi.com.tw
    [Post edited by Glenn]

    Quote from: Indigian on 15-June-05, 19:41:43
    Good news and good work guy's
    On a side note to chakkasol....
    are you using coolbits 1 or 2?
    I heard that coolbits2 is the one for our later cards
    Good question - coolbits 2.  I happened to take a chance from this website and downloaded this file...ran it up against my antivirus and antispyware software and it looked clean.  I simply ran the program and viola, coolbits functionality automatically added to the winxp registry.  I cleaned out the msi DOT drivers first before I loaded this program.  Even though I have tweaked on occasion the winxp registry to speed things up and make winxp shut down quicker, this was too complicated for me to do on my own.
    The highest overclock with the MSIs DOT is 11% at 555/1100.  My MSI card is actually very stable at 580/1160 for a 16% overclock.  I have gotten it to 600/1200 but I usually run the coolbits stability program a few times and it has never failed at 580/1160.  I am sure if I had a better cooling system than the stock fan it would probably go to 600/1200 or higher.  At a 3DMark05 of 4133 (and much higher if I could get it stable at 600/1200, I would be bumping up against the stock speeds of the 6800s vid cards.   
    EDIT: Of course, if you download this coolbits 2 program you do so at your own risk...I take no responsibility for the download.
    The coolbits download:
    http://downloads.guru3d.com/download.php?det=815
    The MSI 6600gt card that I purchased:
    http://www.zipzoomfly.com/jsp/ProductDetail.jsp?ProductCode=321916
    btw, I have ordered more stuff from ZZF than newegg...they seem cheaper (but dont always have the stock of newegg) and the stuff gets here 1 day sooner usually (west coast to east coast USA). 

  • Overclocking AMD 64 X2 3800+

    Hello all
    Well, I'm curious on how high up you can clock the AMD x2 3800+ (E4 Stepping) cpu on stock heatsink/fan?
    So far I was able to OC'd my x2 3800+ to 2.48 Ghz on stock heatsink/fan (the stock HSF is from the x2 4400 model, the one that comes with heatpipes).
    So far my CPU OC'd temps are at Idle 25C to Load 35C (with the HSF that came with the X2 3800 stock settings Idle 35C Load 41C)
    System temps goes from 33C to 40C which was the same readings with the old HSF.
    I got the FSB at 248
                 multiplier at 10x
                 CPU Volts 1.48v (went up from 1.36v)
                 DRAM/FSB 5/6 making the XMS RAM run at DDR412 2.0-3-3-7 1T  2.80v
                 HT multiplier ??? since I can't find it in BIOS only the frequencey and Bandwidth, that's HTT I think....
    I think I can go higher but my Corsair XMS memory might cause problems, since it's not known to OC well (stupid me didn't know that until I found this forum ).
    So has anyone was able to OC'd their X2 3800 past the 2.6Ghz mark?
    I'm new to this OC business so any ideas would be much appreciated.
    Oh I'm afraid to give my CPU anymore voltage than what I gave it.  I really don't want to fry it cause I don't have money to buy another one.  I got a case that comes with a temp display and case fans speed displays so I can keep an eye on temps and the Core Center running to check temps  I've tried speedfan but it doesn't show my CPU or System temps only HD0 temp.  Don't know if it's due to having the MSI K8N Diamond Plus board?
    Oh my case does have 3 fans running, one at front, one at back and one at the Side panel.
    Alexander

    The average overclock on the 3800 is about 2.5 Ghz stable.  You can get up to 2.7 which seems to be the max for the 4200 also but it is rare and requires 1.55 volts on the CPU and water cooling or better.  The voltage range for the 90nm CPU is 1.3 to 1.45 volts (Warranty Range), beyond that your taking a risk as your temperatures can run away very quickly and fry your chip.  (Explained below, you can read it or skip it as I tend to ramble on.)  As for temperature monitoring, get a program called MBM5 with a sister program "ShutDown Now!"  this will monitor your MB and CPU temps and do an automatic hard shutdown a the temperature you choose.  High temp for the 90Nm is 53C and 60 begins to damage it. 
    As for your HT, look for something in the Core menu right under FSB that reads 5x and change it to 4x or lower.  (You want to stay around FSB x HT Multi = 800 to 1050)
    Explanation for Temp:
    Since your OCing a dual core, Ill explain a little bit further since it applies to us more.  The silicon your chip is made out of is a semiconductor, sandwiched with a conductor, an insulator, and then another core. (Dual core as explained to me.)  Anyway, as temperatures rise in the core from higher loads, the silicons conductivity changes relative to the temperature on an exponential scale.  On the flip side, as the chip gets hotter, the thermal conductivity decreases on an exponential scale and the chip will cool slower. So when you up the voltage you come closer to the point where your generating more heat than the silicon can disperse, and with an increase in voltage the electron bleeding between paths increases (causing errors) and more heat.  This is more important in Dual Cores because its a further path from the center of the chip to the outside, hence why Dual Cores seem to run cooler but in reality the temperature in the center is most likely higher.  If you overvolt and or let the temp get too high, the chip becomes similar to a nuclear reactor meltdown, where the damage is done before you even see a sign something is wrong, and poof.....off goes the computer.  Because the curve is relatively flat at the bottom, you have alot of leeway between 1.35 and 1.45 volts and in turn can have a large temperature range from 48 - 53 C.  But the curve dramatically rises past 1.45 V and you can quickly get out of control temperatures if you dont have the proper cooler.  This is also why you need to move to water cooling when getting up to 1.55 volts and a freon or colder cooler for just a few more volts on top of that (1.65 V at 3.0 Ghz 4200X2)  Ok thats the end of my ramble.

  • MSI 660 TI PE Display Driver crashes

    First, here is my system.
    i5-2500k Processor (http://www.newegg.com/Product/Product.aspx?Item=N82E16819115072) (Processor is overclocked to 4.3ghz, temp on it never goes over 45-50°C though)
    MSI Geforce GTX 660TI PE Video card (http://www.newegg.com/Product/Product.aspx?Item=N82E16814127696)
    Asus P8Z68-V Pro\Gen 3 Motherboard (http://www.newegg.com/Product/Product.aspx?Item=N82E16813131790)
    Corsair HX series HX650 Power Supply (http://www.newegg.com/Product/Product.aspx?Item=N82E16817139012)
    4x4GB of G.Skill Ram (http://www.newegg.com/Product/Product.aspx?Item=N82E16820231314)
    When my old MSI P67A-GD55 Motherboard bricked a month ago, instead of waiting on RMA I went ahead and got the Asus board, at the same time I went ahead and upgraded my old Asus GTX 560TI card to the MSI GTX 660TI card. Since the upgrade, I am constantly getting display driver crashes "Display driver nvlddmkm stopped responding and has successfully recovered." when playing games. Guild Wars 2 and Starcraft 2 are the only ones I've had time to try, but both consistently give driver crashes after awhile (sometimes as soon as 15-20 mins, sometimes takes several hours of gameplay).
    Here is the list of things I've already tried:
    -First, I tried the most recent Nvidia drivers. Still crashes.
    -Second, I tried running driver sweeper, removing all old drivers and reinstalling. Still crashes.
    -Third, I tried disabling TDR in the Win7 registry. Still crashes.
    -Fourth, I really ramped up the auto fan speeds. So far it hasn't crashed while doing this, but I can't do it for too long because the fans get so loud that it annoys me greatly.
    -Fifth, I thought it might be an old Motherboard driver conflict of some sort, so I completely formated my OS hard drive and reinstalled Windows 7. Still getting crashes.
    -Sixth, I used driver sweeper again and rolled back to the last official MSI drivers (the ones from October). Still getting crashes.
    I really don't think the card is overheating. The most recent crash happened tonight after playing Starcraft 2 for about 20 minutes, and the temperature of the card never got over 60°C. That's why even with the extremely ramped up fan speeds I tried, I think if I used them long enough, the driver would still crash.
    The power supply is the same as what I used with the 560TI and it didn't have these issues. And from my understanding, the 560TI consumed more power than the 660TI.
    At this point, I'm at my wits end. The only thing else I know to try is swapping out the old 560TI in with the new motherboard or waiting for my old motherboard to come back from RMA and trying the 660TI in it. Though that means rebuilding the case, uninstalling the new mobo drivers and installing the old mobo drivers and authenticating Windows. Doing all of that is going to kill most of a day and I really only want to do that if I absolutely have to.
    I've had such limited time for troubleshooting the card, that I'm regrettably past the 30day limit on RMA replacements to Newegg. So unfortunately that means I'm looking at an RMA directly to MSI and that takes about a month. Before I do that, does anyone have any advice on something to try that might be the cuplrit or can help determine the culprit? I can't find any details in the Event Viewer as to what caused the driver crash. Just that it has stopped responding and has recovered. I wish it could tell me if there was a loss of power, or anything. Power Management Mode is set to prefer maximum performance btw.
    Btw, as a brief description of what happens. The screen goes black, and then comes back and the game is running very slowly. There will also usually be a popup above the taskbar saying that the driver had crashed. I keep the MSI Afterburner info window open in my second monitor and Power usage never goes over 80%, GPU Usage is usually around 95-99%. Core Clock and Memory clock drop to about 324mhz (which is what it idles at) temporarily during the crash. GPU Usage of course dips to very low levels while the driver is crashing, as well.
    Oh and in an added twist, I've run Kombuster several times. Burn-in test DirectX 11 1920x1600 8xMSAA as long as five hours, and the display driver has never crashed. I'll probably turn it on, and disable the computer's sleep and display off tonight and let it run for about 8-9 hours and see what happens. That's one thing that throws me off, if it's a hardware defect, wouldn't Kombuster cause it to crash?
    edit-Here is a screenshot of the Afterburner monitor during a crash while playing Starcraft 2. The huge dip in the bars that I have the cursor over is when the crash occured.

    Well with the Power% limited to 75%, I just had another crash in Starcraft 2. Temp was only at 56°C just before the crash.
    Here is a shot of the Afterburner Hardware Monitor when it crashed:
    Unfortunately I do not have another PC to test the card in. And I don't know anyone around here with a system that the card could work in.
    If I swapped out the 660TI with my old 560TI and I do not get any crashes, wouldn't that indicate it's the 660TI's fault and I'd need to RMA since the 560TI is a more power hungry card?

  • Overclocking Guide

    Overclocking Guide
    Disclaimer: Overclock at your own risk!
    Data and information provided in this guide are for informational and educational purposes only, and are not intended for trading purposes. Neither MSI nor any of this thread’s authors shall be liable for any errors or delays in the content or be held responsible for any damage caused by modifying or overclocking your computer. Manufacturers may or may not honor the warranty on any overclocked or modified computer components. Perform any modifications to your systems at your own risk.
    Why Overclock?
    Today, overclocking is not any secret. It has become more popular and almost become an addiction to some people. The definition of Overclocking is simple: it means operating an Integrated Circuit beyond its specified clock speed.
    But why overclock? Some people say to get more out for the same money. “It’s there; why not get more out of it?” However, the best business reason for overclocking is that it can make “out of date” equipments useful again. If the equipment is already out of warranty, the risk is very limited. (I personally suggest any beginners to overclock any out of date PC first just to have some first time experience.)
    Know more about the Central Processing Unit (CPU)
    Processor speed is based on two factors. The first is the interface between the motherboard and the front side bus (FSB). From http://en.wikipedia.org/wiki/Main_Page (Wikipedia, the free encyclopedia), FSB is the speed at which the CPU communicates with RAM (memory). Many system components - including the PCI and AGP buses usually run at speeds derived from the frontside bus' speed. In general, a faster frontside bus means higher processing speeds and a faster computer. The other factor controlling a CPU's speed is the clock multiplier. It defines the ratio of processor speed to the FSB.
    The FSB on new processors ranges from 400 MHz to 800 MHz. These are not straight clock speeds but instead they are quad-clocked speeds. These processors actually transmit data four times per clock cycle, for example, 800 MHz FSB is actually four times the 200MHz clock (200 MHz x 4 = 800 MHz).
    The core speed of the CPU is the product of the front side bus clock and the multiplier. A processor running at 3600MHz (i.e. 3.6 GHz) might be having 800 MHz FSB, this means there is a clock multiplier setting of 4, and thus the CPU is set to run at 4 times the MHz speed of the front side bus.
    But we said earlier that they are quad-clocked speeds, so 3600 MHz actually came from 18 times 200 MHz (200 MHz x 18 = 3600 MHz).
    Please note that not all processors have quad-clocked speed FSB. For example, the Intel Pentium 4 (Northwood core) has quad-clocked speed FSB. But for example, the Intel Pentium III, AMD Athlon XP and AMD Duron have dual-clocked speed FSB only.
    To know more, please read:
    http://www.anandtech.com/cpuchipsets/showdoc.aspx?i=2178
    Let’s lock the clock multiplier
    Few years ago, you could overclock processors by choosing a higher multiplier. This option was eliminated in order to fight CPU remarking. Counterfeit processors have regularly appeared in the market, as the CPU speed was only defined by your setting. Nowadays, the restriction to only one multiplier is both of overclocking and counterfeit prevention.
    As you can see, the only way of overclocking today is choosing a higher front side bus clock and the offer of small increments e.g. 1MHz in today's motherboards give us a great advantage in overclocking.
    However, some CPUs nowadays are still unlocked, for example, the AMD Athlon MP and AMD Athlon64 families. And some motherboard companies offer the chance to unlock the Pentium 4 (Socket 775 CPUs only) overclocking potential by using special bios, for more please read:
    http://www20.tomshardware.com/motherboard/20040916/index.html
    Look at your motherboard
    Before you overclock anything, have a look if your motherboard can overclock CPU. Look at the CPU installation section in the motherboard manual. Normally you will find either BIOS setup options or jumpers on the motherboard that allow you to adjust the FSB, CPU voltage, PCI/AGP ratio etc.
    If you have a computer that came from a major manufacturer like HP, it is likely that your motherboard does not provide any overclocking function although it is very rare nowadays.
    You need more Power!
    This is also the time to check the power supply in your computer. Like a car, speed requires power, and unstable power inevitably leads to unstable processors, so I would recommend the power supply has to be at least 350 Watts. You can find six power supply guides in this forum below:
    A Power Supply Guide
    AND
    Powersupplies(Written by Bas)
    AND
    Choosing The Right Power Supply
    AND
    Powersupply calculation....
    AND
    http://www.extremeoverclocking.com/articles/guides/Power_Supply_Guide_1.html
    Both Intel and AMD processors are power hungry, consuming 40 to 100 watts (e.g. the new Prescott) of power. Also, your graphics card may take another 55 watts of power. Now you are consuming more than 100 watts of power for merely two components in your system.
    You can also voltmod your Power Supply Unit, for more please read:
    http://www.xbitlabs.com/articles/other/display/psu-voltmodding.html
    Using higher voltages
    Today, almost each processor can be run faster than the speed it was labeled for. This applies even more if you raise the core voltage a little bit. This is just like a car running at higher speed requires more power. But this is one of the “riskiest” aspects of overclocking - by using too much power you could burn your CPU. You should always raise the voltage step by step and never go higher than 15% beyond the specification. This way it is quite easy to get a faster system without risking the processor. Apart from raising the voltage of the CPU, similarly you can raise the voltage of memory as well. One problem is of course the increasing chip temperature, so cooling is very important. We will cover that later.
    Memory Speed
    Memory speed is often tied to the FSB. For example, a Double Data Rate (DDR) 400 memory has frequency 200MHz and the module rating is PC3200. Half the performance increase you may see from overclocking a CPU comes from increasing the speed at which the processor can talk to the memory.
    When you buy memory, you may see it has label 2-3-3-7-1T. And you may also hear people saying my memory is a 2-3-3-7 one. But what does it mean? The answer is:
    CAS Latency = 2 clock cycles
    tRCD = RAS to CAS delay = 3 clock cycles
    tRP = RAS Precharge = 3 clock cycles
    tRAS = Active to Precharge = 7 clock cycles
    Command Rate = 1 clock cycle
    Different motherboards may call the above differently and not all of them will appear in the BIOS. You may need to check with your motherboard’s support team and the motherboard manual. If you have any option above in your BIOS, you can also start to adjust them. Obviously, the smaller the number the faster the memory will be.
    To know more about memory please read:
    http://www.corsairmicro.com/corsair/products/tech/memory_basics/153707/index.html
    AND
    Memory Roundup
    AND
    http://www.anandtech.com/memory/showdoc.aspx?i=2223
    Video Card
    To overclock video card, we need a third party utility to overclock the card. Although increasing numbers of manufacturers include utilities to allow customers to overclock their cards in their drivers or through an extra application, most of them do not provide this facility. Simply because overclocking stresses the system and voids manufacturer warranties. Third party utilities tend to be universal that they work on different cards irrespective of manufacturers.
    Some utilities and the places to download included:
    1. OMEGA Drivers
    http://www.omegacorner.com/
    2. StarStorm Drivers (Nvidia cards only)
    http://downloads.guru3d.com/download.php?id=10
    3. RivaTuner
    http://www.guru3d.com/
    4. PowerStrip
    http://www.entechtaiwan.com/
    5. Rage3D Tweak (ATI cards only)
    http://www.rage3d.com/index.php?node=r3dtweak
    6. RadLinker (ATI cards only)
    http://www28.brinkster.com/chrisww1942/
    7. ATITool (ATI cards only)
    http://atitool.ocfaq.com/
    Please read their own manuals in their corresponding web pages. Also, if you want to be able to have the hidden functions in Nvidia card, create a file with notepad and put this in it (thanks for Deathstalker to provide this source):
    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\NVTweak]
    "Coolbits"=dword:ffffffff
    "NvCplEnableHardwarePage"=dword:00000001
    "NvCplEnableAGPSettingsPage"=dword:00000001
    Save it as agpsetting.reg to your desktop or anywhere you like. Then run it and it will give you all the hidden options from Nvidia which include extra resolution settings for your desktop and overclocking for both the memory and core.
    For ATI Radeon X800 Pro softmod, please read (link provided by mopey):
    http://www.ocforums.com/showindex.php?t=312063
    For ATI Radeon X800 Pro voltage mod, please read (link provided by NovJoe):
    http://www.vr-zone.com.sg/?i=817&s=1
    For ATI Radeon 9800 XT voltage mod, please read (link provided by NovJoe):
    http://www.vr-zone.com.sg/?i=760&s=1
    To can change your Radeon 9800 Pro 256MB graphic card to Radeon 9800XT card, please read (in English):
    http://www.rojakpot.com/(jiljtv55hwgq5uabzft0f5re)/default.aspx?location=3&var1=92&var2=0
    To change your GeForceFX 5900 graphic card to GeForceFX 5900 Ultra, please read (in Traditional Chinese):
    http://www.oc.com.tw/article/0403/readocarticle.asp?id=2410
    To change your GeForceFX 5700 Ultra graphic card to QuadroFX 1100, please read (in Traditional Chinese):
    http://www.oc.com.tw/article/0403/readiyarticle.asp?id=2387
    Get the temperature down
    Cooling is probably the most important aspect of overclocking. Overclocking causes circuits to cycle faster, generating more heat. If the CPU is not cooled properly, your CPU will not run reliably and there is a very good chance that you will permanently damage your CPU.
    The heat sink and fan unit that Intel and AMD ship with its CPU are fairy good. However, for maximum stability, we need to get something better than that. For example, for CPU fans, we have Vantec Tornado, Thermaltake volcano 7+, CoolerMaster Aero 4 and Zalman CNPS7000A-AlCu etc.
    Be sure that the cooling solution you choose is specifically designed for your processor. Improperly mounting a heat sink, using the wrong model can damage your processor.
    Also, the airflow in the case is very important. If heat cannot escape the case, the CPU is still at risk. Thus, more case fans are needed apart from the power supply's exhaust fan. Tidying up the cables inside the case can help too. In addition, clearing the dust in the case by using canned compressed air can enhance the airflow but never use vacuum cleaner as it may generate electrostatic and harm the IC components.
    For more about cooling, you can also read these:
    http://www.antec-inc.com/pdf/article/info_DIYArticle3.html
    AND
    http://www.antec-inc.com/pdf/article/info_DIYArticle2.html
    AND
    Cooling guide(Written by J*A*G)
    AND
    http://www.community.tomshardware.com/forum/postlist.m?Cat=&Board=over_cooling
    For more about CPU fan, please read:
    BEST Overclockers CPU cooler????
    For more about Water Cooling, please read:
    Water cooling...
    Keep the Noise Down
    Unless your computer is cooled by a water cooling system, it will be pretty noisy. To keep the noise down, please read this:
    http://www.antec-inc.com/pdf/article/info_DIYArticle_quiet_computing.html
    Overclocking Process
    Essentially, overclocking processors consists of increasing the FSB in the BIOS, booting the computer, and then testing for stability. You repeat the process until you identify the maximum stable speed.
    In case your board offer 1 MHz-increments (which most of your boards do), you have the chance to find out the maximum clock speed by slowly closing in on the final limit MHz for MHz. Of course this cannot be done in an hour, but you will have to spend one or two days just playing with different clock speed settings. In the end you should have your CPU running at the highest possible core speed. The Most important thing to remember is that you must go Slowly!
    Also, you can overclock the processor by using software although it may not be as effective as overclocking using the motherboard BIOS. Such software includes:
    1. ClockGen
    http://www.cpuid.com/
    2. CPUFSB
    http://mitglied.lycos.de/podien/
    3. 8rdavcore
    http://www.hasw.net/8rdavcore/
    Here is a thread that talks about overclocking an Intel Pentium 4 2.4cGHz to 3.0GHz using Intel 865PE chipsets. (You may treat it as an example of overclocking.):
    Best 865PE Overclock for 2.4C to 3.0+
    Changing the FSB is a relatively simple matter of entering the computer's BIOS setup screen, switching from automatic to manual configuration and selecting the FSB speed you want. Here are some utilities that you can check your computer’s setting, especially CPU speed:
    1. CPU-Z
    http://www.cpuid.com
    2. WCPUID (Linux supported)
    http://www.h-oda.com
    3. AIDA32
    http://www.aida32.hu/aida32.php
    http://aumha.org/freeware.htm
    4. PC Wizard
    http://www.cpuid.com/
    5. EVEREST
    http://www.lavalys.com/
    6. Motherboard Monitor
    http://mbm.livewiredev.com/
    7. HWiNFO and HWiNFO32
    http://www.hwinfo.com/
    8. SpeedFan
    http://www.almico.com/
    http://www.almico.com/speedfan.php
    9. Motherboard Monitor
    http://mbm.livewiredev.com/
    http://mbm.livewiredev.com/download.html
    10. Intel Processor Frequency ID Utility (Intel CPU only)
    http://support.intel.com/support/processors/tools/frequencyid/
    11. AMD CPU Information Display Utility (AMD CPU only)
    http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871,00.html
    For more, you can go to the following to have a browse:
    http://www.3degs.net/
    Bear in mind that if the processor is capable of a 20-percent or more speed increase say, it is unlikely that your video card or memory can have the same amount of increase. And the one thing that you must remember to do if you overclock the FSB is to Set (i.e. Lock) your AGP/PCI Buses, to as close to their Default Frequencies as Possible (to PCI bus at 33 MHz and the AGP port at 66 MHz for example), or you will most definitely experience problems across the whole board e.g. your graphics card, onboard sound and IDE channels may start giving you data and other errors.
    Test for Stability and Benchmarking
    The purpose of testing is to apply a heavy workload to every aspect of your system to ensure that there are no hidden problems and stability issue. You can do testing by using special testing suites, software and games. The aim of benchmarking is to measure the performance of your system. In overclocking, benchmarking can tell you how far the system’s performance has increased when you adjust certain settings.
    For a test suite, you may try Winbench, which you can download from:
    http://www.etestinglabs.com/benchmarks/winbench/winbench.asp
    Special software for testing and benchmarking included:
    1. CPU Burn (Linux supported)
    http://users.bigpond.net.au/cpuburn/
    2. PCMark 04
    http://www.futuremark.com/
    3. Aquamark 3
    http://www.aquamark3.com/
    4. SiSoftware Sandra Standard 2004
    http://www.sisoftware.net/
    5. Prime95 (Linux supported)
    http://www.mersenne.org/
    (For more about Prime95, please read: how to use prime 95 properly)
    6. Memtest86 (Linux supported)
    http://www.memtest86.com/
    7. Memtest86+ (Linux supported)
    http://www.memtest.org/
    8. Super PI (Linux supported)
    http://pw1.netcom.com/~hjsmith/Pi/Super_Pi.html (Windows version)
    http://ftp://pi.super-computing.org/Linux/super_pi.tar.gz (Linux version)
    9. ScienceMark
    http://www.sciencemark.org/
    10. SETI @home (Linux supported)
    http://setiathome.ssl.berkeley.edu/
    For testing video card, you can run Games like Quake 3 and Unreal Tournament demo mode and left running in loops. You should be able to run a game in a loop for at least two hours after a reboot without a problem. Also, you can use 3DMark05 from FUTUREMARK (download from http://www.futuremark.com/).
    1. Unreal Tournament (Linux supported)
    http://www.unrealtournament.com/
    2. Wolfenstein: Enemy Territory (Linux supported)
    http://games.activision.com/games/wolfenstein/
    3. Quake (Linux supported)
    http://www.idsoftware.com/games/quake/
    4. Call Of Duty
    http://www.callofduty.com/index.asp
    5. X2 - The Thread
    http://www.egosoft.com/
    6. Colin McRae Rally 4
    http://www.codemasters.co.uk/colinmcraerally04/uk/colinmcraerally04.php
    7. Nascar Thunder 2004
    http://www.easports.com/games/thunder2004/home.jsp
    8. Halo
    http://www.microsoft.com/games/halo/
    9. Farcry
    http://www.farcry.ubi.com/
    10. Half-Life
    http://games.sierra.com/games/half-life/
    11. Doom 3 (Linux supported)
    http://www.doom3.com/
    Tips: The benchmark can be performed by using “demo1” which ships with Doom 3. Open the console (Windows: Ctrl+Alt+~; Linux: ~) and type “timedemo demo1”.
    12. Battlefield Vietnam
    http://www.eagames.com/official/battlefield/vietnam/us/home.jsp
    13. Serious Sam
    http://www.serioussam.com/
    14. Tomb Raider: The Angel of Darkness
    http://www.tombraider.com/
    15. Halo
    http://www.bungie.net/
    16. Tom Clancy's Splinter Cell
    http://www.splintercell.com/
    Conclusion
    I suggest you to read this guide one more time before you overclock to make sure that you have not missed anything. Wish you have a good overclocking experience, have fun!   Here is also another guide to make your have a Happier and Healthier System:
    http://www.antec-inc.com/pdf/article/info_DIYArticle4.html
    The following teaches you how to change an AMD Athlon XP 1700+ to an Athlon MP 1700+ (in Traditional Chinese):
    http://www.oc.com.tw/article/0304/readocarticle.asp?id=1390
    Also, for a Step By Step Overclocking Guide and other overclocking guides, you can go to:
    1. General overclocking tips
    2. more overclocking help
    3. Hardware & Overclocking FAQ in bit-tech
    http://forums.bit-tech.net/showindex.php?t=51323
    4. Overclocking Guide in OC Forums
    http://www.ocforums.com/showindex.php?t=263753
    5. Link Guide for anyone new to Overclocking in PC Perspective
    http://forums.pcper.com/showindex.php?t=173635
    6. Overclocking Guide in Help Overclocking
    http://www.helpoverclocking.com/english/index.htm
    7. AMD Optimal BIOS settings + Overclocking Guide
    http://www.madshrimps.be/?action=gethowto&howtoID=43
    8. Tom's Hardware CPU Overclocking Forum (contains a few overclocking guides)
    http://www.community.tomshardware.com/forum/postlist.m?Cat=&Board=over_cpu (for CPU)
    9. Tom's Hardware Graphic Cards Overclocking Forum (contains a few overclocking guides)
    http://www.community.tomshardware.com/forum/postlist.m?Cat=&Board=over_graphics (for Graphic Cards)
    For a guide on Modding Tools, please read:
    Modding Tools
    Please post any comment and/or suggestion as well as dead link of this guide (Version 1.49) at the following thread:
    Overclocking Guide Suggestion/Comment
    I would like to thank for the help and support from Bas and Wonkanoby as well as advice from Raven_, Slimbooyphat and The Fellow in setting up this guide.

    Quote from: ferohh on 01-March-05, 04:39:20
    I tried to overclock my p4. 2,66ghz to 3.18ghz.
    l increased the cpu fsb only since the multiplier is fixed at 20x.
    l tried to change it but couldn´t.
    l then increased my cpu voltage from 1.525v to 1.732v.
    At 3.2ghz, the computer was on and restarts automatically, so l turned it to 3.18ghz.
    does it mean the cpu will not overclock further or l need a new cooler?
    I did not overclock anything except the fsb.
    any help?
    I have a 2.6C Northwood pentium 4 on an MSI 875P Neo2-FISR mobo.  On air I'm able to get it to about 3.14Ghz stable.  I don't believe it's a good idea to go past 1.6 for the voltage, from what I've read, voltage doesn't help too much with the northwoods.
    I can overclock mine higher without any significant changes in temperatures, but the overclocks aren't stable and the system freezes up from time to time.  I'm using Kingston HyperX PC4000 DDR, which can run at up to 500mhz, so I can do a 1:1 ratio on the overclock.  I'm using a modular 500-watt power supply, Arctic Silver 5 and a huge honking Swiftech heatsink with an 80mm fan.

  • I installed the latest version of iTunes (10.6.3.25) on a new Windows 7 PC.  I can see ahred libraries on Shared but can't import as the line containing the Settings and Import buttons does not display.   Any suggestions?

    To move the iTunes library to this new computer I switched on Home Sharing and can see the other libraries on my home network.  If I select tracks from a Shared library I can't import them as the strip containing "Show: All Items" and the "Settings" and "Import" buttons, does not display at the bottom of the screen.  Goes straight from the list of tracks to the strip with Playlist icons and xxxx items, tttttt total time, yyyy GB. 
    Any suggestions for making the Import button appear?

    I hvae the EXACT same issue
    I built a new computer which is EXTREMELY fast overclocked i7 ect and.. ITUNES DOESNT WORK
    I click on itunes which ive uninstalled and reinstalled and reset the winsock AND seen if there were any errors AAAAAAND ive check the Hkey to make sure bonjur was the only one in there which it is and all that happens is my cpu goes to 25% and i cant do anything except go into the task manager and close it! ANYTHING with itunes (everything else is premium speed).
    what do i do
    windows 7 64 bit

  • BLUE SCREEN OF DEATH 1800+ XP T-Bred Overclock 1.92 GHz

    I get the BSOD in any game while overclocked 166 FSB to 1.92 GHZ. I've uninstalled and reinstalled ATI display drivers and NVIDIA board drivers with the same results. It wasn't this unstable for a week at a 166 FSB setting!
    At the normal 1800+ speed of 1.53 GHz I have no display problems and no blue screen of death speed.
    Why the instability at a 166 FSB?
    Pie~3.14
    K7N2-L
    320 W PSU
    Win XP Pro SP1
    Athlon XP 1800+ T-Bred
    ATI Radeon 7000 64 DDR~Catalyst 3.1 Drivers
    ~Direct X 9.0
    Sound Blaster Audigy PCI
    Pioneer DVD-ROM 16x
    LG 52x24x52
    Maxtor 40Gb 7200 RPM Quiet Drive
    Elixir PC-2700 256Mb x 2
    :::::RAS# to CAS# Delay: 3
    :::::RAS#Precharge: 3
    :::::Cycle Time: 7

    I didn't touch the multiplier, and I won't now and here's why. Last time I did, my board fried when lowered the multiplier and upped the FSB up around 200. I'm not feeling that adventurous.
    I have never adjusted the CPU Vcore. What is a typical adjustment?
    Pie~3.14

  • External Display Flickers (Intel on board)

    Hi,
    I have recently made a fresh installation of Arch Linux and trying to setup it for my work environment. I made a basic installation of xfce4 with slim login manager. I wanted to hook my laptop with an external display. I used xrandr to extend my laptop display with the external display. Everything worked fine but my external display flickers insanely bad. I cannot stare at it for > 30s. I dual boot on windows, so I tested the same setup with windows and it worked just fine, out of the box. I even used one of my friend's laptop who's running ubuntu and has the same h/w. It worked out of the box. I have spent more than 8 hours trying to find out where the issue would be and miserably failed. Below are certain logs and output that might help traingulate my issue.
    Its a Dell Inspiron N4030, with Intel onboard graphics. I have the xf86-video-intel driver installed and the display works perfectly fine with laptops default display.
    Output of xrandr -q
    [joker@lucifer ~]$ xrandr -q
    Screen 0: minimum 320 x 200, current 2732 x 768, maximum 8192 x 8192
    LVDS1 connected 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm
    1366x768 60.0*+
    1024x768 60.0
    800x600 60.3 56.2
    640x480 59.9
    VGA1 connected 1366x768+1366+0 (normal left inverted right x axis y axis) 344mm x 194mm
    1366x768 60.0*+
    1024x768 75.1 72.0 70.1 60.0
    832x624 74.6
    800x600 72.2 75.0 60.3 56.2
    640x480 72.8 75.0 66.7 60.0
    720x400 70.1
    /var/log/Xorg.0.log
    [ 42.854]
    X.Org X Server 1.11.2
    Release Date: 2011-11-04
    [ 42.854] X Protocol Version 11, Revision 0
    [ 42.854] Build Operating System: Linux 3.1.0-3-ARCH x86_64
    [ 42.854] Current Operating System: Linux lucifer 3.1.0-4-ARCH #1 SMP PREEMPT Mon Nov 7 22:47:18 CET 2011 x86_64
    [ 42.854] Kernel command line: root=/dev/sda5 ro
    [ 42.854] Build Date: 07 November 2011 07:53:00AM
    [ 42.854]
    [ 42.854] Current version of pixman: 0.24.0
    [ 42.854] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 42.854] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 42.855] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Nov 10 17:07:34 2011
    [ 42.901] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 42.927] (==) ServerLayout "DualSreen"
    [ 42.927] (**) |-->Screen "Screen0" (0)
    [ 42.927] (**) | |-->Monitor "Monitor0"
    [ 42.945] (**) | |-->Device "Device0"
    [ 42.945] (**) |-->Screen "Screen1" (1)
    [ 42.945] (**) | |-->Monitor "Monitor1"
    [ 42.945] (**) | |-->Device "Device1"
    [ 42.945] (**) Option "Xinerama" "1"
    [ 42.945] (==) Automatically adding devices
    [ 42.945] (==) Automatically enabling devices
    [ 42.945] (**) Xinerama: enabled
    [ 43.004] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 43.004] Entry deleted from font path.
    [ 43.004] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [ 43.004] Entry deleted from font path.
    [ 43.005] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 43.005] Entry deleted from font path.
    [ 43.005] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 43.005] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 43.005] Entry deleted from font path.
    [ 43.005] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 43.005] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/
    [ 43.005] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 43.005] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 43.005] (II) Loader magic: 0x7ccae0
    [ 43.005] (II) Module ABI versions:
    [ 43.005] X.Org ANSI C Emulation: 0.4
    [ 43.005] X.Org Video Driver: 11.0
    [ 43.005] X.Org XInput driver : 13.0
    [ 43.005] X.Org Server Extension : 6.0
    [ 43.006] (--) PCI:*(0:0:2:0) 8086:0046:1028:0466 rev 2, Mem @ 0xfac00000/4194304, 0xc0000000/268435456, I/O @ 0x0000f080/8
    [ 43.006] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 43.006] (II) LoadModule: "extmod"
    [ 43.027] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
    [ 43.043] (II) Module extmod: vendor="X.Org Foundation"
    [ 43.043] compiled for 1.11.2, module version = 1.0.0
    [ 43.043] Module class: X.Org Server Extension
    [ 43.043] ABI class: X.Org Server Extension, version 6.0
    [ 43.043] (II) Loading extension MIT-SCREEN-SAVER
    [ 43.043] (II) Loading extension XFree86-VidModeExtension
    [ 43.043] (II) Loading extension XFree86-DGA
    [ 43.043] (II) Loading extension DPMS
    [ 43.043] (II) Loading extension XVideo
    [ 43.043] (II) Loading extension XVideo-MotionCompensation
    [ 43.043] (II) Loading extension X-Resource
    [ 43.044] (II) LoadModule: "dbe"
    [ 43.044] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
    [ 43.045] (II) Module dbe: vendor="X.Org Foundation"
    [ 43.045] compiled for 1.11.2, module version = 1.0.0
    [ 43.045] Module class: X.Org Server Extension
    [ 43.045] ABI class: X.Org Server Extension, version 6.0
    [ 43.045] (II) Loading extension DOUBLE-BUFFER
    [ 43.045] (II) LoadModule: "glx"
    [ 43.045] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 43.060] (II) Module glx: vendor="X.Org Foundation"
    [ 43.060] compiled for 1.11.2, module version = 1.0.0
    [ 43.060] ABI class: X.Org Server Extension, version 6.0
    [ 43.060] (==) AIGLX enabled
    [ 43.060] (II) Loading extension GLX
    [ 43.060] (II) LoadModule: "record"
    [ 43.060] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
    [ 43.061] (II) Module record: vendor="X.Org Foundation"
    [ 43.061] compiled for 1.11.2, module version = 1.13.0
    [ 43.061] Module class: X.Org Server Extension
    [ 43.061] ABI class: X.Org Server Extension, version 6.0
    [ 43.061] (II) Loading extension RECORD
    [ 43.061] (II) LoadModule: "dri"
    [ 43.061] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 43.063] (II) Module dri: vendor="X.Org Foundation"
    [ 43.063] compiled for 1.11.2, module version = 1.0.0
    [ 43.063] ABI class: X.Org Server Extension, version 6.0
    [ 43.063] (II) Loading extension XFree86-DRI
    [ 43.063] (II) LoadModule: "dri2"
    [ 43.063] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 43.064] (II) Module dri2: vendor="X.Org Foundation"
    [ 43.064] compiled for 1.11.2, module version = 1.2.0
    [ 43.064] ABI class: X.Org Server Extension, version 6.0
    [ 43.064] (II) Loading extension DRI2
    [ 43.064] (II) LoadModule: "intel"
    [ 43.091] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 43.114] (II) Module intel: vendor="X.Org Foundation"
    [ 43.114] compiled for 1.10.99.902, module version = 2.16.0
    [ 43.114] Module class: X.Org Video Driver
    [ 43.114] ABI class: X.Org Video Driver, version 11.0
    [ 43.114] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
    i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
    E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
    965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
    4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
    Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
    Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
    Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
    Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
    Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server
    [ 43.114] (++) using VT number 7
    [ 43.134] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 43.135] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 43.135] Requested Entity already in use!
    [ 43.135] (EE) Screen 1 deleted because of no matching config section.
    [ 43.135] (II) UnloadModule: "intel"
    [ 43.136] (II) Unloading intel
    [ 43.136] drmOpenDevice: node name is /dev/dri/card0
    [ 43.136] drmOpenDevice: open result is 8, (OK)
    [ 43.136] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
    [ 43.136] drmOpenDevice: node name is /dev/dri/card0
    [ 43.136] drmOpenDevice: open result is 8, (OK)
    [ 43.136] drmOpenByBusid: drmOpenMinor returns 8
    [ 43.136] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
    [ 43.136] (**) intel(0): Depth 24, (--) framebuffer bpp 32
    [ 43.136] (==) intel(0): RGB weight 888
    [ 43.136] (==) intel(0): Default visual is TrueColor
    [ 43.136] (II) intel(0): Integrated Graphics Chipset: Intel(R) Arrandale
    [ 43.136] (--) intel(0): Chipset: "Arrandale"
    [ 43.136] (**) intel(0): Relaxed fencing enabled
    [ 43.136] (**) intel(0): Wait on SwapBuffers? enabled
    [ 43.136] (**) intel(0): Triple buffering? enabled
    [ 43.136] (**) intel(0): Framebuffer tiled
    [ 43.136] (**) intel(0): Pixmaps tiled
    [ 43.136] (**) intel(0): 3D buffers tiled
    [ 43.136] (**) intel(0): SwapBuffers wait enabled
    [ 43.136] (==) intel(0): video overlay key set to 0x101fe
    [ 43.136] (II) intel(0): Output LVDS1 using monitor section Monitor0
    [ 43.136] (**) intel(0): Option "Enable" "true"
    [ 43.136] (II) intel(0): found backlight control interface /sys/class/backlight/acpi_video0
    [ 43.196] (II) intel(0): Output VGA1 has no monitor section
    [ 43.196] (II) intel(0): EDID for output LVDS1
    [ 43.196] (II) intel(0): Manufacturer: BOE Model: 58e Serial#: 0
    [ 43.196] (II) intel(0): Year: 2010 Week: 1
    [ 43.196] (II) intel(0): EDID Version: 1.4
    [ 43.196] (II) intel(0): Digital Display Input
    [ 43.196] (II) intel(0): Undefined color depth
    [ 43.196] (II) intel(0): Digital interface is undefined
    [ 43.196] (II) intel(0): Max Image Size [cm]: horiz.: 31 vert.: 17
    [ 43.196] (II) intel(0): Gamma: 2.20
    [ 43.196] (II) intel(0): No DPMS capabilities specified
    [ 43.196] (II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    [ 43.196] (II) intel(0): First detailed timing is preferred mode
    [ 43.196] (II) intel(0): Preferred mode is native pixel format and refresh rate
    [ 43.196] (II) intel(0): redX: 0.574 redY: 0.335 greenX: 0.335 greenY: 0.585
    [ 43.196] (II) intel(0): blueX: 0.154 blueY: 0.119 whiteX: 0.312 whiteY: 0.328
    [ 43.196] (II) intel(0): Manufacturer's mask: 0
    [ 43.196] (II) intel(0): Supported detailed timing:
    [ 43.196] (II) intel(0): clock: 72.3 MHz Image Size: 309 x 173 mm
    [ 43.196] (II) intel(0): h_active: 1366 h_sync: 1414 h_sync_end 1446 h_blank_end 1526 h_border: 0
    [ 43.196] (II) intel(0): v_active: 768 v_sync: 771 v_sync_end 777 v_blanking: 790 v_border: 0
    [ 43.196] (II) intel(0): Supported detailed timing:
    [ 43.196] (II) intel(0): clock: 72.3 MHz Image Size: 309 x 173 mm
    [ 43.196] (II) intel(0): h_active: 1366 h_sync: 1414 h_sync_end 1446 h_blank_end 1526 h_border: 0
    [ 43.196] (II) intel(0): v_active: 768 v_sync: 771 v_sync_end 777 v_blanking: 790 v_border: 0
    [ 43.196] (II) intel(0): KFDV9HT14101
    [ 43.196] (II) intel(0): Unknown vendor-specific block 0
    [ 43.196] (II) intel(0): EDID (in hex):
    [ 43.196] (II) intel(0): 00ffffffffffff0009e58e0500000000
    [ 43.196] (II) intel(0): 01140104801f11780a3fa09355559527
    [ 43.196] (II) intel(0): 1e505400000001010101010101010101
    [ 43.196] (II) intel(0): 010101010101411c56a0500016303020
    [ 43.196] (II) intel(0): 360035ad1000001a411c56a050001630
    [ 43.196] (II) intel(0): 3020360035ad1000001a000000fe004b
    [ 43.196] (II) intel(0): 46445639814854313431303100000000
    [ 43.196] (II) intel(0): 00004101940100000001010a20200000
    [ 43.196] (II) intel(0): EDID vendor "BOE", prod id 1422
    [ 43.196] (II) intel(0): Printing DDC gathered Modelines:
    [ 43.196] (II) intel(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 771 777 790 +hsync -vsync (47.4 kHz)
    [ 43.196] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported)
    [ 43.196] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
    [ 43.196] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
    [ 43.196] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported)
    [ 43.196] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported)
    [ 43.196] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported)
    [ 43.196] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported)
    [ 43.196] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported)
    [ 43.196] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported)
    [ 43.196] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported)
    [ 43.196] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported)
    [ 43.196] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported)
    [ 43.196] (II) intel(0): Printing probed modes for output LVDS1
    [ 43.196] (II) intel(0): Modeline "1366x768"x60.0 72.33 1366 1414 1446 1526 768 771 777 790 +hsync -vsync (47.4 kHz)
    [ 43.196] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
    [ 43.196] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
    [ 43.196] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
    [ 43.196] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
    [ 43.255] (WW) EDID timing clock 85.75 exceeds claimed max 85MHz, fixing
    [ 43.255] (II) intel(0): EDID for output VGA1
    [ 43.255] (II) intel(0): Manufacturer: PHL Model: c02d Serial#: 9740
    [ 43.255] (II) intel(0): Year: 2009 Week: 35
    [ 43.255] (II) intel(0): EDID Version: 1.3
    [ 43.255] (II) intel(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V
    [ 43.255] (II) intel(0): Sync: Separate
    [ 43.255] (II) intel(0): Max Image Size [cm]: horiz.: 34 vert.: 19
    [ 43.255] (II) intel(0): Gamma: 2.20
    [ 43.255] (II) intel(0): DPMS capabilities: Off; RGB/Color Display
    [ 43.255] (II) intel(0): First detailed timing is preferred mode
    [ 43.255] (II) intel(0): redX: 0.635 redY: 0.335 greenX: 0.281 greenY: 0.597
    [ 43.255] (II) intel(0): blueX: 0.153 blueY: 0.085 whiteX: 0.312 whiteY: 0.328
    [ 43.255] (II) intel(0): Supported established timings:
    [ 43.255] (II) intel(0): 720x400@70Hz
    [ 43.255] (II) intel(0): 640x480@60Hz
    [ 43.255] (II) intel(0): 640x480@67Hz
    [ 43.255] (II) intel(0): 640x480@72Hz
    [ 43.255] (II) intel(0): 640x480@75Hz
    [ 43.255] (II) intel(0): 800x600@56Hz
    [ 43.255] (II) intel(0): 800x600@60Hz
    [ 43.255] (II) intel(0): 800x600@72Hz
    [ 43.255] (II) intel(0): 800x600@75Hz
    [ 43.255] (II) intel(0): 832x624@75Hz
    [ 43.255] (II) intel(0): 1024x768@60Hz
    [ 43.255] (II) intel(0): 1024x768@70Hz
    [ 43.255] (II) intel(0): 1024x768@75Hz
    [ 43.255] (II) intel(0): Manufacturer's mask: 0
    [ 43.255] (II) intel(0): Supported standard timings:
    [ 43.255] (II) intel(0): #0: hsize: 640 vsize 400 refresh: 70 vid: 2609
    [ 43.255] (II) intel(0): #1: hsize: 1024 vsize 768 refresh: 72 vid: 19553
    [ 43.255] (II) intel(0): Supported detailed timing:
    [ 43.255] (II) intel(0): clock: 85.8 MHz Image Size: 344 x 194 mm
    [ 43.255] (II) intel(0): h_active: 1366 h_sync: 1436 h_sync_end 1579 h_blank_end 1792 h_border: 0
    [ 43.255] (II) intel(0): v_active: 768 v_sync: 771 v_sync_end 774 v_blanking: 798 v_border: 0
    [ 43.255] (II) intel(0): Serial No: AU50935009740
    [ 43.255] (II) intel(0): Monitor name: Philips 160E
    [ 43.255] (II) intel(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 60 kHz, PixClock max 86 MHz
    [ 43.255] (II) intel(0): EDID (in hex):
    [ 43.255] (II) intel(0): 00ffffffffffff00410c2dc00c260000
    [ 43.255] (II) intel(0): 23130103682213782ab370a255489827
    [ 43.255] (II) intel(0): 155054bfee00310a614c010101010101
    [ 43.255] (II) intel(0): 0101010101017f2156aa51001e30468f
    [ 43.255] (II) intel(0): 330058c21000001e000000ff00415535
    [ 43.255] (II) intel(0): 30393335303039373430000000fc0050
    [ 43.255] (II) intel(0): 68696c69707320313630450a000000fd
    [ 43.255] (II) intel(0): 00384c1e3c08000a20202020202000c0
    [ 43.255] (II) intel(0): Printing probed modes for output VGA1
    [ 43.255] (II) intel(0): Modeline "1366x768"x60.0 85.75 1366 1436 1579 1792 768 771 774 798 +hsync +vsync (47.9 kHz)
    [ 43.255] (II) intel(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz)
    [ 43.255] (II) intel(0): Modeline "1024x768"x72.0 78.44 1024 1080 1192 1360 768 769 772 801 -hsync +vsync (57.7 kHz)
    [ 43.255] (II) intel(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
    [ 43.255] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
    [ 43.255] (II) intel(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
    [ 43.255] (II) intel(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
    [ 43.255] (II) intel(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
    [ 43.255] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
    [ 43.255] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
    [ 43.255] (II) intel(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz)
    [ 43.255] (II) intel(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
    [ 43.255] (II) intel(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz)
    [ 43.255] (II) intel(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
    [ 43.255] (II) intel(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
    [ 43.255] (II) intel(0): Output LVDS1 enabled by config file
    [ 43.255] (II) intel(0): Output VGA1 connected
    [ 43.255] (II) intel(0): Using exact sizes for initial modes
    [ 43.255] (II) intel(0): Output LVDS1 using initial mode 1366x768
    [ 43.255] (II) intel(0): Output VGA1 using initial mode 1366x768
    [ 43.255] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 43.255] (II) intel(0): Kernel page flipping support detected, enabling
    [ 43.255] (**) intel(0): Display dimensions: (310, 170) mm
    [ 43.255] (**) intel(0): DPI set to (111, 114)
    [ 43.255] (II) Loading sub module "fb"
    [ 43.255] (II) LoadModule: "fb"
    [ 43.255] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 43.277] (II) Module fb: vendor="X.Org Foundation"
    [ 43.277] compiled for 1.11.2, module version = 1.0.0
    [ 43.277] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 43.277] (II) Loading sub module "dri2"
    [ 43.277] (II) LoadModule: "dri2"
    [ 43.277] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 43.277] (II) Module dri2: vendor="X.Org Foundation"
    [ 43.277] compiled for 1.11.2, module version = 1.2.0
    [ 43.277] ABI class: X.Org Server Extension, version 6.0
    [ 43.277] (==) Depth 24 pixmap format is 32 bpp
    [ 43.277] (II) intel(0): [DRI2] Setup complete
    [ 43.277] (II) intel(0): [DRI2] DRI driver: i965
    [ 43.277] (II) intel(0): Allocated new frame buffer 1408x768 stride 5632, tiled
    [ 43.339] (II) UXA(0): Driver registered support for the following operations:
    [ 43.339] (II) solid
    [ 43.339] (II) copy
    [ 43.339] (II) composite (RENDER acceleration)
    [ 43.339] (II) put_image
    [ 43.339] (II) get_image
    [ 43.339] (==) intel(0): Backing store disabled
    [ 43.339] (==) intel(0): Silken mouse enabled
    [ 43.339] (II) intel(0): Initializing HW Cursor
    [ 43.456] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 43.466] (==) intel(0): DPMS enabled
    [ 43.466] (==) intel(0): Intel XvMC decoder enabled
    [ 43.466] (II) intel(0): Set up textured video
    [ 43.466] (II) intel(0): [XvMC] xvmc_vld driver initialized.
    [ 43.466] (II) intel(0): direct rendering: DRI2 Enabled
    [ 43.466] (WW) intel(0): Option "Enable" is not used
    [ 43.466] (WW) intel(0): Option "TwinView" is not used
    [ 43.466] (==) intel(0): hotplug detection: "enabled"
    [ 43.466] (--) RandR disabled
    [ 43.466] (II) Initializing built-in extension Generic Event Extension
    [ 43.466] (II) Initializing built-in extension SHAPE
    [ 43.466] (II) Initializing built-in extension MIT-SHM
    [ 43.466] (II) Initializing built-in extension XInputExtension
    [ 43.466] (II) Initializing built-in extension XTEST
    [ 43.466] (II) Initializing built-in extension BIG-REQUESTS
    [ 43.466] (II) Initializing built-in extension SYNC
    [ 43.466] (II) Initializing built-in extension XKEYBOARD
    [ 43.466] (II) Initializing built-in extension XC-MISC
    [ 43.466] (II) Initializing built-in extension SECURITY
    [ 43.466] (II) Initializing built-in extension XINERAMA
    [ 43.466] (II) Initializing built-in extension XFIXES
    [ 43.466] (II) Initializing built-in extension RENDER
    [ 43.466] (II) Initializing built-in extension RANDR
    [ 43.466] (II) Initializing built-in extension COMPOSITE
    [ 43.466] (II) Initializing built-in extension DAMAGE
    [ 43.605] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 43.605] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 43.605] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 43.605] (II) AIGLX: enabled GLX_SGI_make_current_read
    [ 43.605] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 43.605] (II) AIGLX: Loaded and initialized i965
    [ 43.605] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 43.605] (II) intel(0): Setting screen physical size to 361 x 203
    [ 43.909] (II) config/udev: Adding input device Power Button (/dev/input/event7)
    [ 43.910] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 43.910] (II) LoadModule: "evdev"
    [ 43.910] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 43.910] (II) Module evdev: vendor="X.Org Foundation"
    [ 43.910] compiled for 1.10.99.902, module version = 2.6.0
    [ 43.910] Module class: X.Org XInput Driver
    [ 43.910] ABI class: X.Org XInput driver, version 13.0
    [ 43.910] (II) Using input driver 'evdev' for 'Power Button'
    [ 43.910] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 43.911] (**) Power Button: always reports core events
    [ 43.911] (**) Power Button: Device: "/dev/input/event7"
    [ 43.911] (--) Power Button: Found keys
    [ 43.911] (II) Power Button: Configuring as keyboard
    [ 43.911] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input7/event7"
    [ 43.911] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 43.911] (**) Option "xkb_rules" "evdev"
    [ 43.911] (**) Option "xkb_model" "evdev"
    [ 43.911] (**) Option "xkb_layout" "us"
    [ 43.931] (II) config/udev: Adding input device Video Bus (/dev/input/event15)
    [ 43.931] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 43.931] (II) Using input driver 'evdev' for 'Video Bus'
    [ 43.931] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 43.931] (**) Video Bus: always reports core events
    [ 43.931] (**) Video Bus: Device: "/dev/input/event15"
    [ 43.931] (--) Video Bus: Found keys
    [ 43.931] (II) Video Bus: Configuring as keyboard
    [ 43.931] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input15/event15"
    [ 43.931] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
    [ 43.931] (**) Option "xkb_rules" "evdev"
    [ 43.931] (**) Option "xkb_model" "evdev"
    [ 43.931] (**) Option "xkb_layout" "us"
    [ 43.932] (II) config/udev: Adding input device Power Button (/dev/input/event4)
    [ 43.932] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 43.932] (II) Using input driver 'evdev' for 'Power Button'
    [ 43.932] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 43.932] (**) Power Button: always reports core events
    [ 43.932] (**) Power Button: Device: "/dev/input/event4"
    [ 43.932] (--) Power Button: Found keys
    [ 43.932] (II) Power Button: Configuring as keyboard
    [ 43.932] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input4/event4"
    [ 43.932] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
    [ 43.932] (**) Option "xkb_rules" "evdev"
    [ 43.932] (**) Option "xkb_model" "evdev"
    [ 43.932] (**) Option "xkb_layout" "us"
    [ 43.932] (II) config/udev: Adding input device Lid Switch (/dev/input/event5)
    [ 43.932] (II) No input driver/identifier specified (ignoring)
    [ 43.932] (II) config/udev: Adding input device Sleep Button (/dev/input/event6)
    [ 43.932] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
    [ 43.932] (II) Using input driver 'evdev' for 'Sleep Button'
    [ 43.932] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 43.932] (**) Sleep Button: always reports core events
    [ 43.932] (**) Sleep Button: Device: "/dev/input/event6"
    [ 43.932] (--) Sleep Button: Found keys
    [ 43.932] (II) Sleep Button: Configuring as keyboard
    [ 43.932] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input6/event6"
    [ 43.932] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
    [ 43.933] (**) Option "xkb_rules" "evdev"
    [ 43.933] (**) Option "xkb_model" "evdev"
    [ 43.933] (**) Option "xkb_layout" "us"
    [ 43.933] (II) config/udev: Adding input device HID 413c:8161 (/dev/input/event2)
    [ 43.933] (**) HID 413c:8161: Applying InputClass "evdev keyboard catchall"
    [ 43.933] (II) Using input driver 'evdev' for 'HID 413c:8161'
    [ 43.933] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 43.933] (**) HID 413c:8161: always reports core events
    [ 43.933] (**) HID 413c:8161: Device: "/dev/input/event2"
    [ 43.933] (--) HID 413c:8161: Found keys
    [ 43.933] (II) HID 413c:8161: Configuring as keyboard
    [ 43.933] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1:1.0/input/input2/event2"
    [ 43.933] (II) XINPUT: Adding extended input device "HID 413c:8161" (type: KEYBOARD, id 10)
    [ 43.933] (**) Option "xkb_rules" "evdev"
    [ 43.933] (**) Option "xkb_model" "evdev"
    [ 43.933] (**) Option "xkb_layout" "us"
    [ 43.934] (II) config/udev: Adding input device HID 413c:8162 (/dev/input/event3)
    [ 43.934] (**) HID 413c:8162: Applying InputClass "evdev pointer catchall"
    [ 43.934] (II) Using input driver 'evdev' for 'HID 413c:8162'
    [ 43.934] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 43.934] (**) HID 413c:8162: always reports core events
    [ 43.934] (**) HID 413c:8162: Device: "/dev/input/event3"
    [ 43.934] (--) HID 413c:8162: Found 3 mouse buttons
    [ 43.934] (--) HID 413c:8162: Found relative axes
    [ 43.934] (--) HID 413c:8162: Found x and y relative axes
    [ 43.934] (II) HID 413c:8162: Configuring as mouse
    [ 43.934] (**) HID 413c:8162: YAxisMapping: buttons 4 and 5
    [ 43.934] (**) HID 413c:8162: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 43.934] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2:1.0/input/input3/event3"
    [ 43.934] (II) XINPUT: Adding extended input device "HID 413c:8162" (type: MOUSE, id 11)
    [ 43.934] (II) HID 413c:8162: initialized for relative axes.
    [ 43.934] (**) HID 413c:8162: (accel) keeping acceleration scheme 1
    [ 43.934] (**) HID 413c:8162: (accel) acceleration profile 0
    [ 43.934] (**) HID 413c:8162: (accel) acceleration factor: 2.000
    [ 43.934] (**) HID 413c:8162: (accel) acceleration threshold: 4
    [ 43.934] (II) config/udev: Adding input device HID 413c:8162 (/dev/input/mouse1)
    [ 43.934] (II) No input driver/identifier specified (ignoring)
    [ 43.934] (II) config/udev: Adding input device Laptop_Integrated_Webcam_0.3M (/dev/input/event10)
    [ 43.934] (**) Laptop_Integrated_Webcam_0.3M: Applying InputClass "evdev keyboard catchall"
    [ 43.934] (II) Using input driver 'evdev' for 'Laptop_Integrated_Webcam_0.3M'
    [ 43.934] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 43.934] (**) Laptop_Integrated_Webcam_0.3M: always reports core events
    [ 43.934] (**) Laptop_Integrated_Webcam_0.3M: Device: "/dev/input/event10"
    [ 43.934] (--) Laptop_Integrated_Webcam_0.3M: Found keys
    [ 43.934] (II) Laptop_Integrated_Webcam_0.3M: Configuring as keyboard
    [ 43.934] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input10/event10"
    [ 43.934] (II) XINPUT: Adding extended input device "Laptop_Integrated_Webcam_0.3M" (type: KEYBOARD, id 12)
    [ 43.934] (**) Option "xkb_rules" "evdev"
    [ 43.934] (**) Option "xkb_model" "evdev"
    [ 43.934] (**) Option "xkb_layout" "us"
    [ 43.935] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event11)
    [ 43.935] (II) No input driver/identifier specified (ignoring)
    [ 43.935] (II) config/udev: Adding input device HDA Intel Mic at Ext Right Jack (/dev/input/event12)
    [ 43.935] (II) No input driver/identifier specified (ignoring)
    [ 43.935] (II) config/udev: Adding input device HDA Intel HP Out at Ext Right Jack (/dev/input/event13)
    [ 43.935] (II) No input driver/identifier specified (ignoring)
    [ 43.935] (II) config/udev: Adding input device USB OPTICAL MOUSE (/dev/input/event1)
    [ 43.935] (**) USB OPTICAL MOUSE: Applying InputClass "evdev pointer catchall"
    [ 43.935] (II) Using input driver 'evdev' for ' USB OPTICAL MOUSE'
    [ 43.935] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 43.936] (**) USB OPTICAL MOUSE: always reports core events
    [ 43.936] (**) USB OPTICAL MOUSE: Device: "/dev/input/event1"
    [ 43.936] (--) USB OPTICAL MOUSE: Found 3 mouse buttons
    [ 43.936] (--) USB OPTICAL MOUSE: Found scroll wheel(s)
    [ 43.936] (--) USB OPTICAL MOUSE: Found relative axes
    [ 43.936] (--) USB OPTICAL MOUSE: Found x and y relative axes
    [ 43.936] (II) USB OPTICAL MOUSE: Configuring as mouse
    [ 43.936] (II) USB OPTICAL MOUSE: Adding scrollwheel support
    [ 43.936] (**) USB OPTICAL MOUSE: YAxisMapping: buttons 4 and 5
    [ 43.936] (**) USB OPTICAL MOUSE: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 43.936] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/input/input1/event1"
    [ 43.936] (II) XINPUT: Adding extended input device " USB OPTICAL MOUSE" (type: MOUSE, id 13)
    [ 43.936] (II) USB OPTICAL MOUSE: initialized for relative axes.
    [ 43.936] (**) USB OPTICAL MOUSE: (accel) keeping acceleration scheme 1
    [ 43.936] (**) USB OPTICAL MOUSE: (accel) acceleration profile 0
    [ 43.936] (**) USB OPTICAL MOUSE: (accel) acceleration factor: 2.000
    [ 43.936] (**) USB OPTICAL MOUSE: (accel) acceleration threshold: 4
    [ 43.936] (II) config/udev: Adding input device USB OPTICAL MOUSE (/dev/input/mouse0)
    [ 43.936] (II) No input driver/identifier specified (ignoring)
    [ 43.936] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 43.936] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 43.936] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 43.936] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 43.936] (**) AT Translated Set 2 keyboard: always reports core events
    [ 43.936] (**) AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 43.936] (--) AT Translated Set 2 keyboard: Found keys
    [ 43.936] (II) AT Translated Set 2 keyboard: Configuring as keyboard
    [ 43.936] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 43.936] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 14)
    [ 43.936] (**) Option "xkb_rules" "evdev"
    [ 43.936] (**) Option "xkb_model" "evdev"
    [ 43.936] (**) Option "xkb_layout" "us"
    [ 43.937] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/event14)
    [ 43.937] (**) PS/2 Generic Mouse: Applying InputClass "evdev pointer catchall"
    [ 43.937] (II) Using input driver 'evdev' for 'PS/2 Generic Mouse'
    [ 43.937] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 43.937] (**) PS/2 Generic Mouse: always reports core events
    [ 43.937] (**) PS/2 Generic Mouse: Device: "/dev/input/event14"
    [ 43.937] (--) PS/2 Generic Mouse: Found 3 mouse buttons
    [ 43.937] (--) PS/2 Generic Mouse: Found relative axes
    [ 43.937] (--) PS/2 Generic Mouse: Found x and y relative axes
    [ 43.937] (II) PS/2 Generic Mouse: Configuring as mouse
    [ 43.937] (**) PS/2 Generic Mouse: YAxisMapping: buttons 4 and 5
    [ 43.937] (**) PS/2 Generic Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 43.937] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input14/event14"
    [ 43.937] (II) XINPUT: Adding extended input device "PS/2 Generic Mouse" (type: MOUSE, id 15)
    [ 43.937] (II) PS/2 Generic Mouse: initialized for relative axes.
    [ 43.937] (**) PS/2 Generic Mouse: (accel) keeping acceleration scheme 1
    [ 43.937] (**) PS/2 Generic Mouse: (accel) acceleration profile 0
    [ 43.937] (**) PS/2 Generic Mouse: (accel) acceleration factor: 2.000
    [ 43.937] (**) PS/2 Generic Mouse: (accel) acceleration threshold: 4
    [ 43.937] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/mouse2)
    [ 43.937] (II) No input driver/identifier specified (ignoring)
    [ 43.937] (II) config/udev: Adding input device PC Speaker (/dev/input/event8)
    [ 43.937] (II) No input driver/identifier specified (ignoring)
    [ 43.938] (II) config/udev: Adding input device Dell WMI hotkeys (/dev/input/event9)
    [ 43.938] (**) Dell WMI hotkeys: Applying InputClass "evdev keyboard catchall"
    [ 43.938] (II) Using input driver 'evdev' for 'Dell WMI hotkeys'
    [ 43.938] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 43.938] (**) Dell WMI hotkeys: always reports core events
    [ 43.938] (**) Dell WMI hotkeys: Device: "/dev/input/event9"
    [ 43.938] (--) Dell WMI hotkeys: Found keys
    [ 43.938] (II) Dell WMI hotkeys: Configuring as keyboard
    [ 43.938] (**) Option "config_info" "udev:/sys/devices/virtual/input/input9/event9"
    [ 43.938] (II) XINPUT: Adding extended input device "Dell WMI hotkeys" (type: KEYBOARD, id 16)
    [ 43.938] (**) Option "xkb_rules" "evdev"
    [ 43.938] (**) Option "xkb_model" "evdev"
    [ 43.938] (**) Option "xkb_layout" "us"
    [ 48.392] (II) intel(0): EDID vendor "BOE", prod id 1422
    [ 48.392] (II) intel(0): Printing DDC gathered Modelines:
    [ 48.392] (II) intel(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 771 777 790 +hsync -vsync (47.4 kHz)
    [ 48.456] (WW) EDID timing clock 85.75 exceeds claimed max 85MHz, fixing
    [ 48.457] (II) intel(0): EDID vendor "BOE", prod id 1422
    [ 48.457] (II) intel(0): Printing DDC gathered Modelines:
    [ 48.457] (II) intel(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 771 777 790 +hsync -vsync (47.4 kHz)
    [ 48.517] (WW) EDID timing clock 85.75 exceeds claimed max 85MHz, fixing
    [ 49.976] (II) intel(0): EDID vendor "BOE", prod id 1422
    [ 49.976] (II) intel(0): Printing DDC gathered Modelines:
    [ 49.976] (II) intel(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 771 777 790 +hsync -vsync (47.4 kHz)
    [ 50.035] (WW) EDID timing clock 85.75 exceeds claimed max 85MHz, fixing
    [ 213.440] (II) config/udev: removing device USB OPTICAL MOUSE
    [ 213.440] (II) USB OPTICAL MOUSE: Close
    [ 213.440] (II) UnloadModule: "evdev"
    [ 213.440] (II) Unloading evdev
    [ 213.728] (II) config/udev: Adding input device USB OPTICAL MOUSE (/dev/input/event1)
    [ 213.728] (**) USB OPTICAL MOUSE: Applying InputClass "evdev pointer catchall"
    [ 213.728] (II) Using input driver 'evdev' for ' USB OPTICAL MOUSE'
    [ 213.728] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 213.728] (**) USB OPTICAL MOUSE: always reports core events
    [ 213.728] (**) USB OPTICAL MOUSE: Device: "/dev/input/event1"
    [ 213.728] (--) USB OPTICAL MOUSE: Found 3 mouse buttons
    [ 213.728] (--) USB OPTICAL MOUSE: Found scroll wheel(s)
    [ 213.728] (--) USB OPTICAL MOUSE: Found relative axes
    [ 213.728] (--) USB OPTICAL MOUSE: Found x and y relative axes
    [ 213.728] (II) USB OPTICAL MOUSE: Configuring as mouse
    [ 213.728] (II) USB OPTICAL MOUSE: Adding scrollwheel support
    [ 213.728] (**) USB OPTICAL MOUSE: YAxisMapping: buttons 4 and 5
    [ 213.728] (**) USB OPTICAL MOUSE: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 213.728] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/input/input16/event1"
    [ 213.728] (II) XINPUT: Adding extended input device " USB OPTICAL MOUSE" (type: MOUSE, id 13)
    [ 213.728] (II) USB OPTICAL MOUSE: initialized for relative axes.
    [ 213.728] (**) USB OPTICAL MOUSE: (accel) keeping acceleration scheme 1
    [ 213.728] (**) USB OPTICAL MOUSE: (accel) acceleration profile 0
    [ 213.728] (**) USB OPTICAL MOUSE: (accel) acceleration factor: 2.000
    [ 213.728] (**) USB OPTICAL MOUSE: (accel) acceleration threshold: 4
    [ 213.730] (II) config/udev: Adding input device USB OPTICAL MOUSE (/dev/input/mouse0)
    [ 213.730] (II) No input driver/identifier specified (ignoring)
    [ 1627.253] (II) intel(0): EDID vendor "BOE", prod id 1422
    [ 1627.253] (II) intel(0): Printing DDC gathered Modelines:
    [ 1627.253] (II) intel(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 771 777 790 +hsync -vsync (47.4 kHz)
    [ 1627.311] (WW) EDID timing clock 85.75 exceeds claimed max 85MHz, fixing
    [ 1644.964] (II) intel(0): EDID vendor "BOE", prod id 1422
    [ 1644.964] (II) intel(0): Printing DDC gathered Modelines:
    [ 1644.964] (II) intel(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 771 777 790 +hsync -vsync (47.4 kHz)
    [ 1645.027] (WW) EDID timing clock 85.75 exceeds claimed max 85MHz, fixing
    [ 1645.042] (II) intel(0): Allocated new frame buffer 2752x768 stride 11264, tiled
    [ 1645.230] (II) intel(0): EDID vendor "BOE", prod id 1422
    [ 1645.230] (II) intel(0): Printing DDC gathered Modelines:
    [ 1645.230] (II) intel(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 771 777 790 +hsync -vsync (47.4 kHz)
    [ 1645.289] (WW) EDID timing clock 85.75 exceeds claimed max 85MHz, fixing
    [ 1645.307] (II) intel(0): EDID vendor "BOE", prod id 1422
    [ 1645.307] (II) intel(0): Printing DDC gathered Modelines:
    [ 1645.307] (II) intel(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 771 777 790 +hsync -vsync (47.4 kHz)
    [ 1645.365] (WW) EDID timing clock 85.75 exceeds claimed max 85MHz, fixing
    [ 1645.387] (II) intel(0): EDID vendor "BOE", prod id 1422
    [ 1645.387] (II) intel(0): Printing DDC gathered Modelines:
    [ 1645.387] (II) intel(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 771 777 790 +hsync -vsync (47.4 kHz)
    [ 1645.446] (WW) EDID timing clock 85.75 exceeds claimed max 85MHz, fixing
    [ 1645.447] (II) intel(0): EDID vendor "BOE", prod id 1422
    [ 1645.447] (II) intel(0): Printing DDC gathered Modelines:
    [ 1645.447] (II) intel(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 771 777 790 +hsync -vsync (47.4 kHz)
    [ 1645.505] (WW) EDID timing clock 85.75 exceeds claimed max 85MHz, fixing
    [ 2335.972] (II) intel(0): EDID vendor "BOE", prod id 1422
    [ 2335.972] (II) intel(0): Printing DDC gathered Modelines:
    [ 2335.972] (II) intel(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 771 777 790 +hsync -vsync (47.4 kHz)
    [ 2336.030] (WW) EDID timing clock 85.75 exceeds claimed max 85MHz, fixing
    lspci output
    00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
    00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)
    00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
    00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
    00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)
    00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05)
    00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05)
    00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 05)
    00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 (rev 05)
    00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
    00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5)
    00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05)
    00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller (rev 05)
    00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05)
    00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05)
    12:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)
    13:00.0 Ethernet controller: Atheros Communications AR8152 v2.0 Fast Ethernet (rev c1)
    ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
    ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
    ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
    ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
    ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
    ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)

    No one? I have the exact same problem. MSI x360 laptop, intel onboard graphics. I too use xrandr. I've seen elsewhere that windows users have solved this by turning off GPU overclocking. Maybe this can point us in the right direction?

  • VGA to HD cinema display (DVI-D)?

    Please correct me if i'm wrong with any of this..
    I have a G5 with the cinema display that outputs DVI-D. It's the one with no pins above or below the horizontal strip and with a gap inbetween the other pins. If you look at this link it will be the third one. http://cdn.overclock.net/2/21/215b66d1_all-DVI-types.jpeg
    I love this monitor and what I need to know is if I can somehow connect a VGA from my PC to this apple DVI-D monitor. People have told me it's impossible to convert analog signals to digital and others have told me I can do this with an adapter. I've seen all kinds of DVI-D plugs but none of them are the exact type that I have which is supposedly a single link (whatever that means.) I have found two adapters that say they do what I want but I have no clue if they support the DVI-D plug that goes to my monitor.
    This one here looks to do what I want but the DVI-D output has extra pins that I don't have. I have a gap in the middle and I don't have any extra pins above or below the horizontal strip. http://www.networktechinc.com/vga-dvi.html
    This next one also seems to do what I want but I don't even see an DVI-D output. Only an HDMI output which is not what I want... http://www.datapro.net/products/vga-to-dvi-d-hdmi-converter.html
    I'm beyond confused with all this DVI stuff and have no clue what all of it even means. If anyone knows of any other adapters that work or have any suggestions, answers or ANYTHING please let me know!
    Thanks!

    I'm beyond confused with all this DVI stuff and have no clue what all of it even means.
    And you've jumped right into a graduate level use of the Apple Cinema Display with what you propose.
    Convertors may or may not work. The use of the Apple monitor with a PC (what OS?) creates further difficulties.
    I would not spend money on a convertor without expressed guarantee that the 23" Cinema Display is supported.
    The Apple Cinema Displays don't work like "normal" monitors in many cases.
    This is evidenced when choosing KVM switches, as well. Many KVM's don't support the ACD.
    Personally, I would replace the graphics card of the PC with one that is DVI equipped and supports 1920x1200 digital.
    That removes one point of contention and leaves the OS as the last stumbling block.
    Providing the OS is XP and later, the Cinema Display will possibly work without too much hassle (we are talking Windows, however).
    http://sourceforge.net/projects/winacd/
    Vista (64) looks grim, Vista (32) maybe OK.
    Win 7 may be a better bet.
    Spend some time with Google before wasting spending money.

  • R6950 Display Twin Froz II OC 2 GB flickers with multiple displays

    Hi guys,
    This is my situation, I have a 3 monitor setup (27" SA850 PLS) not running on Eyefinity, simply using extended desktop and playing only on one monitor. 2 of the monitors are connected to the card using Display Port and another one using the Dual DVI connector.  My resolution is 2560x1440 on the 3 monitors.
    When I play a game (i.e. SC2) one of the side monitor flickers, If I'm on normal 2D everything works fine.  The one that flickers is connected using the display port. 
    What I have tried:
    * Installing latest Catalyst (12.1).
    * Swapping monitors.
    * Swapping cables.
    What I found out:
    It is only happening on the monitor connected to the second display port on the card.  Disregarding of what cable or monitor I use, If it is connected to the second display port it will suffer flickering when I go into a game.  Remember the one suffering the flickering will not be the one I use to play which is connected on the dual DVI port.
    Even more interesting, flickering WILL STOP, if i reduce the resolution of the monitor connected to that specific display port to 1280x1024.
    I even tried all the following combinations where A, B, C are monitors. Min resolution is 1024x768 and Max Resolution is 2560x1440.  C will be the monitor connected to this specific display port.
    1. A Resolution Max
       B Resolution Max   
       C Resolution Max  =  Flicker
    2. A Resolution Min
       B Resolution Min     
       C Resolution Min  = No flicker
    3. A Resolution Max
       B Resolution Max   
       C Resolution Min    = No Flicker
    4. A Resolution Max
       B Resolution Max
       C Resolution over 1280x1024 = flicker
    5. A Resolution Min
       B Resolution Min
       C Resolution over 1280x1024 = Flicker
    6. A Resolution Max
       B Resolution Max
       C Resolution <= 1280x1024 = No flicker
    I have no idea why is this happening, I really want to avoid sending the card in, I cant be without the card so if someone has some crazy ideas Im all in for trying them.
    Thanks in advance.

    Okay, received my replacement card from Amazon on Monday, finally had a chance to install and test the new card today. So far, no artifacts that I can see. I tested in Kombustor, Amnesia: Dark Descent, a video in VLC, GIMP, and of course my Web browser. Everything looks fine, so I'll just assume that the first card I received was a bad one. Hopefully things won't change with the new card (I do not plan on overclocking it), but I'll be keeping my old Radeon 4870 just in case.
    I did notice one thing that seemed odd in Kombustor though. When it did the combined test at the end for Kmark, there were constantly shifting vertical lines on the screen. Seemed to be part of the test (like old newsreel footage?), and didn't show up anywhere else. Anyway.

  • GF4 Ti4200 won't overclock?

    Hey guys,
    This isn't so much a problem, more of a query. I just purchased an MSI Geforce4 Ti4200 128mb DDR and overall am very happy with it. Although whenever I attempt to take the core clock speed or the memory clock speed up (either using the advanced display properties or the MSI 3D! Turbo Experience) and reboot, the changes have never taken effect. They seem to just default back to the most stable settings (464/250). I know this card can go to 'at least' 510/270 but no matter wot I do it won't let me :-(
    Anyway hope someone can help me out. There's no hurry mind, the default settings are running everything fine atm :-)
    Cheers ppl

    MEMORY  
    128MB high-speed 128-bit DDR (Double Data Rate)
    10.4 GB/sec Memory Bandwidth, 444MHz Memory Clock Rate.
    CHIPSET  256-bit nVIDIA GeForce4 Ti 4400 GPU
    RAMDAC  350 MHz, 250MHz Core Clock
    I could be wrong here but the 64MB version has the 500mhz memory clock rate.
    Below is a link to support the statement.
    http://www.tech-report.com/reviews/2002q2/geforce4-ti4200/index.x?pg=2
    You are in fact OVERCLOCKED by 2mhz!
    Dennis B beat me too it while I was composing.... :D

  • Display artifacts when waking from sleep...

    My G5 runs 24/7, and the display goes to sleep every night when i'm not using it.
    Lately when i wake my computer from sleep in the morning, i get artifacts all over the screen on various graphics... the artifacts are typically a bright teal color and they are about 1 pixel tall x 5 pixels in length.
    I know artifact like this usually appear when the Video Card is overheating, which is odd because the card isn't and has never been overclocked...
    I did just recently upgrade to the Apple 30" display from the Apple 23" display, i'm wondering if this has anything to do with it?
    i've got the NVIDIA GeForce 6600

    I would reseat the video card, clean any dust from the inside of the computer and then run the Apple Hardware Test. Post back and let us know what you find.

  • Memory frequency in overclocking?

    I hope someone is willing to help me out as I am a complete beginner and very much out of my depth... having said that...
    I'm looking to set up a very modest stable overclock... with next to no idea of what i'm doing.
    I have an E4400 ms-7255 with 2 x 1gb RAM which runs at 333Mhz according to cpuz.
    I haven't been able to find anything about 333Mhz RAM (if that IS indeed what i have - since i read it usually runs below its specs)
    How does RAM frequency affect overclocking? Is it still possible/worthwhile or does the bandwidth limit it too much?
    What settings would you recommend me attempting as a very safe attempt without having to flick the switch to reset my motherboard - and could you give me a bit of a run down/how to keeping in mind i'm less than leet.
    Thanks so much
    Samuel

    Hello oscariouss,
    the first basic thing you should try to get sorted before you get into overclocking is the difference between "real clock speeds" and "effective clock speeds" and also the inter-dependencies of different clocks and clock rates on an Intel System.
    CPU-Z for example, shows you the "real" clock speed of your memory.  Now, as we are talking about DDR memory modules, the effective clock speed is always twice the real clock speed.  That is why "333 MHz" actually translates to DDR2-667 Mhz effectively. [DDR stands for "Double Data Rate" and this means that with each clock cycle, two transactions will take place (that is how you get the factor x2)]
    Quote
    I haven't been able to find anything about 333Mhz RAM (if that IS indeed what i have - since i read it usually runs below its specs)
    You probably have DDR2-667 memory modules.  To be absolutely sure about that, open your computer case and have a look at the memory modules themselves.  The brand and model name is usually mentioned on some sort of sticker.
    CPU-Z should also display information about the brand and model name of your memory modules.  Have a look at the "SPD" Tab and see what it says in the top half.  You can also make screenshot and post them here for comparison.
    To overclock the system, the most basic operation is to simply raise the FSB Clock Speed in BIOS.  For your current processor, the default FSB clock speed should be 200 MHz.  CPU Frequency is always the product of FSB Clock Speed x Multiplier and that is why raising the FSB Frequency will automatically result in a higher CPU Frequency.
    Keep in mind, that memory frequency is also tied to FSB Frequency.  The relation between FSB Clock and memory clock is regulated via FSB/Memory Ratios that can be set in BIOS.  If your FSB Clock speed is 200 MHz and memory clock speed (real) is 333 MHz, that means that FSB/Memory Ratio is set to 1:1.66 in BIOS (probably via an AUTO setting).
    Now, if you raise FSB Clock Speed, memory clock speed will rise as well.  If you would increase FSB Frequency to 210 MHz in BIOS and the FSB/Memory Ratio remains @1:1.66, memory clock speed will be forced to:
    210 MHz x 1.66 = 348,6 MHz [or DDR2-697 MHz effectively]
    Please also remember, that your board is a budget model whose VIA Chipset is not really a high-end/high-performance piece of hardware.  Overclocking is not exactly what the designers had in mind here.  That means that the overclocking potential will most likely be limited and the BIOS will probably lack specific OC relevant options that will help to  reach higher clock speeds.  That, of course, does not mean that you should not at least try to check what is possible, but you should not be disappointed when you find out that you are unable to stabilize the system above certain frequencies.
    I don't know which options you have to influence memory clock speed (or more precisely FSB/Memory Ratio) in BIOS.  Just have a look what options you have there and tell us here.

Maybe you are looking for

  • Problem with DNS - ping/Safari cannot resolve, but host/dig work OK

    Hi All, Have a weird problem with DNS which is a bit similar to the following ones: http://discussions.info.apple.com/thread.jspa?threadID=2190208 http://forums.macrumors.com/showthread.php?t=337942 I connect with remote internal network via OpenVPN

  • Why can't I get my icloud email on my computer?

    I cannot get my icloud email on my iMac intel computer - I always get a message to go to "preferences" and see if there is a yellow something there and if so, uncheck the box and then recheck - well this does not work.  The yellow thingy goes away, b

  • Upload file function in a flash form

    Hi, i need to ad a function to upload files in a tipical contact form and receive them by mail. anyone knows how to do it? thanks a lot!

  • How to display Web reports in blackberry

    Hi All, I have to display the web reports avaialable on our portal on the blackberry. How can I achieve it? Should I install anything on my blackberry? Should I develop web applications seperately for displaying on blackberry or can I use the existin

  • Adding other languages in Marketing attributes

    Hi all, Im currently working with marketing attributes and would like to add different languages in the attribute. I guess that you add different languages in the description tab in transaction CRMM_ROUT_PROF_CHAR? But it doesnt seem to work on attri