ATI HD 3870 and gaming video corruption after 10.5.6 update

I have an early 2006 MacPro 8 core in which I replaced the factory ATI X1900 graphics card with the highly recommended ATI HD 3870 card. The upgrade went smoothly and now I can play Call of Duty 2 for Mac on my 1920 x 1200 display at the highest quality of detail and shading with no problems.
After upgrading my OSX to 10.5.6, I started having random video corruption while playing COD2. It appears as random magenta, cyan or green flashes with a screen-like texture in various parts of the display. It seems totally random. After speaking with ATI tech support and the great guys at Other World Computing where I bought the card, the determination was that the card was the problem. I sent it into ATI for a warranty repair or replacement. While waiting, I borrowed the same card from a friend and installed it. The same problem occurred.
I think the issue now tracks back to the 10.5.6 upgrade which according to Apple provided updates to the video drivers for ATI cards. Now I don't know how to go back to the previous drivers. I checked ATI's web site and there are no drivers available for download for Leopard.
Any suggestions?
Thanks.
Bud James

Backup - always - before you apply updates. Start using SuperDuper.
Wait for 10.5.7.
The first 8-core was 3GHz and came in March 2007. But you had the X1900 so that says it is pre-2008 (most that say "early 200x" mean Early 2008 Mac Pro).
Drivers are part of OS X bundle, there is no discreet driver package.
If you don't have a backup, make one, and then you are faced with fresh install or archive and install, and you may need 10.5.2 DVD (with the 8800 you can't boot from a system w/o getting a panic if it is lower than 10.5.2).

Similar Messages

Portable Wireless Server WG-C10 doesn't stream any audio and some video content after updating phone to Android Lollipop 5.x

The Portable Wireless Server WG-C10 I purchased in 2014 doesn't stream any audio and some video content after updating phone to Android Lollipop 5.x.
The WG-C10 firmware is the last version which is available and the PWS Manager software is the last version available in Google Play Store.
There are no updates for the WG-C10 firmware nor PWS Manager software since 2013 or for Android 5.x (Lollipop) and I don't know if the WG-C10 firmware is the problem or if the PWS Manager software is the problem.
BTW, I am still able to stream this content on my tablet which is on KitKat (4.4.x) so the files are not corrupted. The only problem is with Lollipop.
PWS Manager in the Google Play Store says it supports Android 4.0+ which is no longer true.
The audio file formats which fail to stream are: mp3 and wav
The video file formats which fail to stream are: mp4, avi and 3gp
JPEG Images appear to work fine, but I haven't tried other formats.
I purchased the WG-C10 to stream audio and video primarily to my phone and now that this no longer works, the WG-C10 is useless to me.
Any ideas?

Hi juicespeare1,
Welcome to the Sony Community!
Upon checking your inquiry, the best division to respond to your concern is our Sony Mobile department.
You can reach them at this site: http://www.sonymobile.com/global-en/support/contact-us/contact-info/.
If my post answers your question, please mark it as "Accept as Solution"

Using Adobe Media Encoder to create H.264, MPEG-2, and WMV videos from After Effects - 6/23/14

Very disappointed with this choice. I will definitely be seeking to uninstall this version and go back a version or two. Two many extra steps to export an mp4 now. And now we also have to wait longer for a mp4 to render and can't take advantage of the machine's hardware? You guys fighting mp4 as a standard, forcing us to an additional product, or what? I'll be sharing my extreme disappoint with this 'upgrade' with the rest of the developers at work and who just had it installed. I'm not seeing this being too popular opn social media either. Seems like you only did what was best for you.Thanks for showing us who's boss.

Frank VA wrote:
And now we also have to wait longer for a mp4 to render and can't take advantage of the machine's hardware?
Not necessarily. You can render an intermediate codec with AE's render queue (thus using all of AE's power to render) and then drop that file into the Adobe Media Encoder.
This was the workflow I've always used - even when AE could encode with MP4. Why? Well, because AE sucked at MP4 encoding. You couldn't even do multipass endoding with it!
This is a useful workflow in a few ways:
1. You have an archive-quality file to come back to in the future.
2. You can use AE's full power to render.
3. You can use AME's superior encoding capabilities.
4. You can tweak your compression settings and try various encoding parameters to improve the quality while decreasing the bitrate of your product WITHOUT having to re-render the AE comp every time you try since you're working off of the intermediate file. I mean, imagine a comp with several 3d layers, depth of field, shadows from multiple lights, and 250,000 particles from Particular. What if you made an MP4 and then the client needed a smaller file size or the MP4 you made was too heavily compressed and you needed higher quality? I don't know about you, but I'd much rather only render that 18-hour monster once.
This workflow actually saves time for many people.
And, in any workflow, this produces a better product.
Again, this is what I did even when AE could encode MP4's.
Frank VA wrote:
You guys fighting mp4 as a standard, forcing us to an additional product, or what?
They aren't fighting MP4 as a standard, in fact, when Adobe folks pop in here and answer questions, that's often their recommendation for delivery codec.
Frank VA wrote:
Seems like you only did what was best for you. Thanks for showing us who's boss.
Listen, I understand your frustration. Knocking out a quick compressed file from AE for client review is handy.
However, maintaining the h.264 encoding in AE took up development time. There are only so many person-hours per week for the (relatively tiny) AE team to spend on building each version of AE.
I never liked AE's h.264 encoding - AME has always done a superior job. Since we have AME to do our encoding, I would rather the AE team focus their effort on improving AE as a compositing and motion graphics tool rather than as an encoding tool.
Again, I get the frustration. I can see where it feels like they are doing what's good for them and not us, but I think, in the long run, this way is better for us. Right now, the majority of the AE team is working on making AE faster to work with and faster to render. The sooner we get a relatively bug-free version of that, the better! (Especially for folks on Mac OSX Yosemite who can't RAM preview smoothly in any version of AE).
And at least the After Effects team has been very transparent about things - for example, this blog post talks about their reasoning: using Adobe Media Encoder to create H.264, MPEG-2, and WMV videos from After Effects

My MacBook will not play videos. No sound and the video stops after a few seconds.

My Mac book pro will not play videos. No sound and the video stops after a few seconds.

Hello GrahamBIOM,
I understand while viewing a video or listening to some different content, you lose audio, is that correct? I will do all I can to assist you with this issue.
Does the issue occur when you have headphones inserted? If you are not sure, if you have a set of headphones available could you test that please?
Please respond back at your earliest convenience with results.
Thanks
Clicking the White Kudos star on the left is a way to say Thanks!
Clicking the 'Accept as Solution' button is a way to let others know which steps helped solve the problem!

HT1222 Last week my iPhone 5 would only be down 5-10% in 24 hours. I mostly text and e-mail. After the 6.1 update yesterday it has been 20 hours since the last charge and it is down 60%. Something is up

Last week my iPhone 5 would only be down 5-10% in 24 hours. I mostly text and e-mail. After the 6.1 update yesterday it has been 20 hours since the last charge and it is down 60%. Something is up

Sounds like all the settings that you may have adjusted to save power (screen brightness etc etc) have been defaulted back to factory.
If you jump into all the settings and turn off what you dont need and turn down what you do need it will be the same as before.
Worked for me
Cheers!

Macbook Pro Retina and Yosemite Video Corruption?

So I have a Macbook Pro Retina (mid 2012), 2.7ghz i7, 16gb ram, which has the NVIDIA GeForce GT 650M 1024 MB video card and integrated video. I am running Mac OS X Yosemite 10.10
I have been experiencing a lot of video corruption in different applications, it doesn't seem to be limited to just one application or two -- it is happening in Safari, Mail, Photoshop, and others.
I am attaching screen shots to show:
Here is a video when it decides to flash weird video garble:
Link to video: https://www.youtube.com/watch?v=j8RAyj9L_nQ
Has anyone experienced this same problem? is there an official name or description for what is going on? Is there a fix? It is quite frustrating.

I have the same problem with my older white Apple Wireless Extended Keyboard, which had been working fine with my 2009 iMac. But I experience the issue sporadically with my new Mac Mini. I've read reports of people resolving some BT issues by turning off "Allow Bluetooth devices to wake this computer" in the Advanced pane of the Bluetooth System Preferenes Pane.
There are also people having the issue on iOS devices using various Apple BT keyboards. No help, but interesting to note that it's happening across various devices, keyboard models, and OSs.

Hi, my itune U and podcast videos disappeared after ios 6 upgrade. where can i find them?

hi my itune U videos and podcast can no longer be viewed by "video" app after iOS 6 upgrade. they are there when i search for them. but just won't start. there is a new podcast app but i can't see my old podcast video from its library.
does anyone know how to access them?
i am using a ipad 2.

ok i found the solution. i need a new app "itunes U"
http://itunes.apple.com/us/app/itunes-u/id490217893?mt=8

Video Playback After 3.1.2 Update

I have recently updated to 3.1.2 and now find that some videos, that played perfectly well before the update, are now pixelated and of a considerably lesser standard.
Is anyone else aware of this issue and is there any way around it?
Thanks in advance.

Your suggestion to reset and restore is much appreciated.
However, I wouldn't have labelled the video playback issue a bug before trying something so basic.
To review, just like to person who began this thread, when playing back videos on my 2G iPod touch using OS 3.1.2, any attempt to summon the video controls, after about the first 10 seconds of playback, does not work. The iPod offers no response to any gestures on the screen.
That the iPod's behavior (a) was not observed before the current OS, (b) has been experienced by other users with the same hardware and firmware combination, and (c) continues no matter how many times I reset and restore the device, sounds very much like a bug to me.
My apologies if I offended anyone with the question I posed at the end of my previous post, but it does seem that, in their rush to get stuff out to us, high-visibility glitches like this are becoming more frequent. Perhaps, with our ridiculously high expectations of Apple, we are in part to blame.

Video jumping after 1.1.3 update

Has anyone noticed that the video has started to stutter/jump when feeding video from the iTouch to a TV since the 1.1.3 update. It played perfectly fine using 1.1.2. I would flash it back to 1.1.2 if I could, but apple seems to be restricting this since they don't want people Jailbreaking iPods. Yes, I have tried the methods mentioned time & time again to restore the iPod to a firmware version older than 1.1.3, but so far no luck. I even tried it on several different computers and still no luck. Also it does this with videos purchased from iTunes as well as ones that I converted myself. Does anyone know of another way to restore an older firmware version?
APPLE - Please note that not everyone is trying to jailbreak their iPods. I am just trying to get it working like it was before.

I was using 1.1.3 and playing video on my TV and YES, I did get the stutter that you speak of. Since I hated this new BUG, I decided to downgrade to 1.1.2 again and I will tell you how to do it the easy way and it DOES work. I did it to mine and it was very simple.
1. Plug in your iPod touch and let it finish syncing in iTunes
2. Hold down POWER and HOME
3. Wait until the iPod disappears from your source list, then let go of POWER but, keep holding HOME
4. Then let go of HOME when the iPod appears back in your source list
5. iTunes should now detect an iPod in recovery mode
6. Hold down OPTION and click the "Restore" button and navigate to the 1.1.2 firmware on your hard drive. If you've downloaded it through iTunes, you'll find it in ~/Library/iTunes/iPod Software Updates
7. Choose the 1.1.2 file and restore your iPod to 1.1.2.
8. The bad news is, you can't use the Mail, Notes, Weather, Stock and Maps apps on 1.1.2 but, the video will play nicely.
Hope this helps.
I've sent a bug report about 1.1.3 and watching video on the TV. I hope they fix this VERY soon because I WANT 1.1.3 again but, I DON'T want stuttering video. By the way, you're the only other person that I've seen post about this bug... nobody else much watch video on their TVs from the iPod touch.

Video problems after 10.0.5 update

Ever since I updated to Final Cut Pro X 10.0.5, all of my video has a green tinge at various places during the playback. Not sure how to correct it. It happens on my existing projects and new video I import. Here is an image of what I'm seeing, but it changes constantly upon movement within the clips. Any help would be appreciated. I tried transhing preferences, but this didn't help.
Thanks,
Steve

Thanks Tom. that was it. I had my display calibrated to match my photo prints, so switching it back to default solved the issue.
Thanks again!
Steve

I cannot play videos anymore after last adobe flash update

I cannot play videos anymore after the last adobe flash update. The screen shows "plug-in failure".

What system are you running? There's a problem with current Flash 13 version. You can download an earlier 12 version here: Archived Flash Player versions
OT

ATI driver issues and slow video playback

I just reinstalled Arch and I installed the ATI drivers, at first I couldn't get them working but when I did, video in full screen was amazingly slow, so I tried installing ati-drivers-arch, as someone in the boards suggested but after that each time I start X, it would crash my computer, so right now I am using the standard vesa driver to even start X.
Also when trying to resize mplayer (while using -vo gl) it says my computer is too slow. And VLC has no speed issues but the quality of the picture is very poor.
I am running:
AMD Athlon 64 3200+
ATI Radeon X800 GTO
1.5 gb of DDR RAM
# File generated by xorgconfig.
# Copyright 2004 The X.Org Foundation
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
# Refer to the xorg.conf(5x) man page for details about the format of
# this file.
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
# This loads the font modules
# Load "type1"
# Load "speedo"
Load "freetype"
# Load "xtt"
# This loads the GLX module
Load "glx"
# This loads the DRI module
# Load "dri"
EndSection
# Files section. This allows default font and rgb paths to be set
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
RgbPath "/usr/share/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
# FontPath "/usr/lib/X11/fonts/local/"
# FontPath "/usr/lib/X11/fonts/misc/"
# FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/Speedo/"
# FontPath "/usr/lib/X11/fonts/Type1/"
# FontPath "/usr/lib/X11/fonts/TrueType/"
# FontPath "/usr/lib/X11/fonts/freefont/"
# FontPath "/usr/lib/X11/fonts/75dpi/"
# FontPath "/usr/lib/X11/fonts/100dpi/"
# The module search path. The default path is shown here.
# ModulePath "/usr/lib/modules"
EndSection
# Server flags section.
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
# Option "NoTrapSignals"
# Uncomment this to disable the <Ctrl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.
# Option "DontVTSwitch"
# Uncomment this to disable the <Ctrl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Ctrl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
# Option "Dont Zoom"
# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
# Option "DisableVidModeExtension"
# Uncomment this to enable the use of a non-local xvidtune client.
# Option "AllowNonLocalXvidtune"
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
# Option "DisableModInDev"
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
# Option "AllowNonLocalModInDev"
EndSection
# Input devices
# Core keyboard's InputDevice section
Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbRules" "xorg"
Option "XkbModel" "dell101"
Option "XkbLayout" "us"
EndSection
# Core Pointer's InputDevice section
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "PS/2" # PS/2 Mouse
Option "Device" "/dev/psaux"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Mouse wheel mapping. Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7. Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.
Option "ZAxisMapping" "4 5 6 7"
# Emulate3Buttons is an option for 2-button mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
EndSection
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the xorg.conf man page for a description of the options.
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Monitor section
# Any number of monitor sections may be present
Section "Monitor"
Identifier "ati"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
HorizSync 31.5 - 48.5
# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
VertRefresh 50-70
EndSection
# Graphics device section
# Any number of graphics device sections may be present
# Standard VGA Device:
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# Device configured by xorgconfig:
Section "Device"
Identifier "ati1"
Driver "vesa"
# unsupported card
VideoRam 262144
# Insert Clocks lines here if appropriate
EndSection
# Screen sections
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "ati1"
Monitor "ati"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
# ServerLayout sections.
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
Section "ServerLayout"
# The Identifier line must be present
Identifier "Simple Layout"
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
Screen "Screen 1"
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
# Section "DRI"
# Mode 0666
# EndSection
A big thank you to anyone who can help!

It doesn't look like xorg 7 has been installed. The latest kernel 2.6.15 needs xorg 7, udev, and initrd .
I may be wrong but my xorg is much smaller in size and fonts are handled differently in the latest kernels.
Please see the blogs concerning the upgrades to the xorg 7 changes.

System lockups/video corruption after adding hard drive

I have a first generation MacPro with an ATI video board. I recently added a 1 TB Western Digital "Black" hard drive, and I used Carbon Copy Cloner to duplicate the first drive onto the Black HD, which is now my new boot drive.
Ever since I did that, my system has become quite unstable and locks up frequently. What typically happens is I'll get a garbled single row of pixels in random places on the screen, and then within a few minutes it will lock up if I try to do anything that is graphics intensive such as using Expose's active screen corders to show my desktop, or opening a folder with dozens of different icons (like the Apps folder). It /seems/ like the problem is compounded when I am using FireFox, but that may simply be because I use it alot.
After the lockup the only way to regain control of the machine is to hold in the power button.
I've even gone as far as removing the original drive thinking that perhaps the system might be confused and is pulling drivers or whatever from the old drive. That didn't help.
Any thoughts as to what is happening here? It's seriously driving me nuts (not to mention wasting a lot of my time constantly having to restart the system).

Did you run Disk Warrior before and after cloning?
Repaired permissions?
Re-ran 10.5.7 combo update?
I'd even look in system profile - memory and see if there are errors showing (doesn't show errors from prior system boots though).
Cleaned out the X1900; add copper cooling kit $29, or look into another ATI card.
Before using any new drive, zero it. And if you have Windows and the drive is backed up or before you put files on it --- do a complete and thorough zero and extended test in Windows using WD's own Diagnostic utility - much better, reliable, and does map out bad blocks while Disk Utility and other OS X tools rarely do. But any new drive... I've had 3 out of 6 need such treatment.
As a test, reboot back on your original why not? I'd have done that just to narrow down the possibilities.

Audio and (sometimes) video issue after Win 10 Upgrade - Split X2 laptop 64-bit

Any solution to the Audio and Video issues on Split X2 laptop after Windows 10 FREE Upgrade?? I'm sure others are have the same Audio/video problems: - very slow, Repeating audio and video on YouTube and Netflix playback....totally unwatchable- speakers work fine- everything was working great on Windows 8.1 there must be some kind of driver upgrade for IDT High Definition CODEC BEATS audio... is there a work-around until the real problem is fixed? Regards - VK

I have downloaded and installed the HP recommended IDT Audio Driver using the HP Assistant. The current installed IDT High Definition Audio CODEC driver is: STWRT64.sys 6.10.6498.0 The laptop was rebooted but the problem still the same.....Audio is garbeled and impossible to understand the words...video seems ok when playing Youtube videos. My Split 13 X2 product id is: E2S66AV BIOS F.27

After effects and Premier pro corrupted after dynamiclinkserver crash CS6

Hi guys,
The title says it all really.
I was trying to render an after effects file in CS6
I opened Premier Pro and created a dynamic link. this crashed after a while and both programs now fail to start up.
I have tried most of the suggested fixes to no avail.
For information: I also have CC installed and it runs fine. If i log in as another user with a clean profile then they run fine. So im guessing its a common user based issue.
premier pro just stops working on launch
After effects freezes on the mediacore loading. It then gives a message saying Quicktime is not installed on this computer (It is). If i click okay it then proceeds to crash with a dialogue box which refers to the dynamiclinkserve.exe
Becasue it seems to be profile based im thinking a reinstall wont make any difference here.
All help greatly appreciated
all the best
chris

FIXED!
if you have this issue the best way to see if the dynamiclink server is in a crash loop. It will intermittently freeze your machine. On the task manager you will see it starting and quitting.
see http://forums.adobe.com/message/3196845#3196845
post 15. Solved it for me (the prefs in dynamiclinkmanager)
cheers
chris

ATI HD 3870 and gaming video corruption after 10.5.6 update

Similar Messages

Maybe you are looking for