Hangs at boot after 10.5.8 combo update

hi all,
i just updated from 10.5.1 to 10.5.8 with the combo update. it now will just hang at the apple logo. i have a dual boot on the same drive with 10.4.11 thus i am able to post this.. disk utility finds no errors. reinstalling is last resort..
see my sig for computer specs.
thx in advanced

Some general advice on updating:
It is worth noting that it is an extreme rarity for updates to cause upsets to your system, as they have all been extensively beta-tested, but they may well reveal pre-existing ones, particularly those of which you may have been unaware. If you are actually aware of any glitches, make sure they are fixed before proceeding further.
So before you do anything else:
If you can, make a full backup first to an external hard disk. Ideally you should always have a bootable clone of your system that enables you to revert to the previous pre-update state.
Turn off sleep mode for both screen and hard disk.
Disconnect all peripherals except your keyboard and mouse.
1. Repair Permissions (in Disk Utility)
2. Verify the state of your hard disk using Disk Utility. If any faults are reported, restart from your install disk (holding down the C key), go to Disk Utility, and repair your startup disk. Restart again to get back to your startup disk.
At least you can now be reasonably certain that your system does not contain any obvious faults that might cause an update/upgrade to fail.
3. Download the correct version of the COMBO update from the Apple download site.
The Combo updater of Leopard 10.5.8 can be found here:
http://support.apple.com/downloads/MacOS_X_10_5_8_ComboUpdate
If you prefer to download updates via Software Update in the Apple menu (which would ensure that the correct version for your Mac was being downloaded), it is not recommended to allow SU to install major (or even minor) updates automatically. Set Software Update to just download the updater without immediately installing it. There is always the possibility that the combined download and install (which can be a lengthy process) might be interrupted by a power outage or your cat walking across the keyboard, and an interrupted install will almost certainly cause havoc. Once it is downloaded, you can install at a time that suits you. You should make a backup copy of the updater on a CD in case you ever need a reinstall.
Full details about the 10.5.8 update here: http://support.apple.com/kb/HT3606
More information on using Software Updater here:
http://support.apple.com/kb/TA24901?viewlocale=en_US
Using the Combo updater ensures that all system files changed since the original 10.5.0 are included, and any that may have been missed out or subsequently damaged will be repaired. The Delta updater, although a temptingly smaller download, only takes you from the previous version to the new one, i.e. for example from 10.5.7 to 10.5.8. Software Update will generally download the Delta updater only. The preferable Combo updater needs to be downloaded from Apple's download site.
Now proceed as follows:
4. Close all applications and turn off energy saving and screensaver.
5. Unplug all peripherals except your keyboard and mouse.
6. Install the update/upgrade. Do not under any circumstances interrupt this procedure. Do not do anything else on your computer while it is installing. Be patient.
7. When it ask for a restart to complete the installation, click restart. This can take longer than normal, there are probably thousands of files to overwrite and place in the correct location. Do nothing while this is going on.
8. Once your Mac is awake, repair permissions again, and you should be good to go!
If your Mac seems slightly sluggish or ‘different’, perform a second restart. It can’t hurt and is sometimes efficacious! In fact a second restart can be recommended.
9. Open a few of your most used applications and check that all is OK. In this connection please remember that not all manufacturers of third party applications and plug-ins, add-ons, haxies etc, will have had time to do any necessary rewrites to their software to make them compliant with the latest version of your operating system. Give them a week or two while you regularly check their websites for updates. This applies particularly to plug-ins for Safari 4.
N.B. Do not attempt to install two different updates at the same time as each may have different routines and requirements. Follow the above recommendations for each update in turn.
Lastly, Apple's own article on the subject of Software Update may also be useful reading:
http://docs.info.apple.com/article.html?artnum=106695
If you are updating Safari (or just have):
Input Managers from third parties can do as much harm as good. They use a security loophole to reach right into your applications' code and change that code as the application starts up. If you have installed an OS update and Safari is crashing, the very first thing to do is clear out your InputManagers folders (both in your own Library and in the top-level /Library), log out and log back in, and try again.
So, disable all third party add-ons before updating Safari, as they may not have been updated yet for the new version. Add them back one by one. If something goes awry, remove it again and check on the software manufacturer's website for news of an update to match your version of Safari.
Most errors reported here after an update are due to an unrepaired or undetected inherent fault in the system, and/or a third party add-on.
Additional tips on software installation here:
http://docs.info.apple.com/article.html?artnum=106692
To reiterate, Input Managers reach right into an application and alter its code. This puts the behavior of the affected application outside the control and responsibility of its developers: a recipe for problems. That's not to say that issues absolutely will ensue as a result of Input Managers, but you, as a user, must decide. If the functionality of a specific Input Manager or set thereof is really important to you, you may well choose to assume the associated risk.
Again, the advice is to remove all Input Managers from the following directories:
• /Library/InputManagers
• ~/Library/InputManagers
especially prior to system updates (they can always be added back one-by-one later).

Similar Messages

  • Not Booting after 10.5.8 combo update

    Hello
    I have noticed that after i ran the updater for 10.5.8 combo, this machine does not boot. I have target mode this computer to another and all the files/folders are there on the problem machine.
    Any ideas what to do to get it to boot?
    was thinking about running disk util/repair permissions on the problem machine through the use of target mode.
    thanks
    MArk

    Definitely repair the hard drive and permissions via target disk mode. However, if it still does not boot you need to tell us exactly what happens and where it fails. "Does not boot" is not very informative.

  • My MacAir 1st gen. won't boot after latest OS X Lion update.

    My MacAir 1st gen. won't boot after latest OS X Lion update. tried safe boot(didn't work) tried disk repair, said it was successful, but my mac won't start up. Just get white screen.  Also been having trouble with it overheating. Fan seems to work. But when it get too hot whole interface slows down.

    Yikes, I hope you have AppleCare on it still, I think it needs to be taken in, but as a last ditch effort...
    Have you done a PRAM reset, CMD+Option+p+r...
    http://support.apple.com/kb/HT1379
    In fact, do 3 in a row, takes a bit of time.

  • Hangs during boot after upgrading to Kernel 2.6.39

    I have just installed Arch on a new computer. It works fine until I upgrade to Kernel 2.6.39. After that it hangs on boot.
    The end of /var/log/everything.log is posted below.
    Jul 26 23:52:06 localhost kernel: [ 6.036766] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table at offset 0x85F3
    Jul 26 23:52:06 localhost kernel: [ 6.129046] adt7475 1-002e: ADT7473 device, revision 1
    Jul 26 23:52:06 localhost kernel: [ 6.138997] [drm] nouveau 0000:04:00.0: Detected monitoring device: adt7473
    Jul 26 23:52:06 localhost kernel: [ 6.139000] [drm] nouveau 0000:04:00.0: 1 available performance level(s)
    Jul 26 23:52:06 localhost kernel: [ 6.139002] [drm] nouveau 0000:04:00.0: 0: memory 405MHz core 270MHz shader 540MHz
    Jul 26 23:52:06 localhost kernel: [ 6.139233] [TTM] Zone kernel: Available graphics memory: 12371030 kiB.
    Jul 26 23:52:06 localhost kernel: [ 6.139236] [TTM] Zone dma32: Available graphics memory: 2097152 kiB.
    Jul 26 23:52:06 localhost kernel: [ 6.139238] [TTM] Initializing pool allocator.
    Jul 26 23:52:06 localhost kernel: [ 6.139252] [drm] nouveau 0000:04:00.0: Detected 5376MiB VRAM
    Jul 26 23:52:06 localhost kernel: [ 6.139260] mtrr: type mismatch for d0000000,8000000 old: write-back new: write-combining
    Jul 26 23:52:06 localhost kernel: [ 6.150626] [drm] nouveau 0000:04:00.0: 512 MiB GART (aperture)
    Jul 26 23:52:06 localhost kernel: [ 6.152371] [drm] nouveau 0000:04:00.0: failed to load fuc409d
    Jul 26 23:52:06 localhost kernel: [ 6.176193] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
    Jul 26 23:52:06 localhost kernel: [ 6.176195] [drm] No driver support for vblank timestamp query.
    Jul 26 23:52:06 localhost kernel: [ 6.228800] No connectors reported connected with modes
    Jul 26 23:52:06 localhost kernel: [ 6.228802] [drm] Cannot find any crtc or sizes - going 1024x768
    Jul 26 23:52:06 localhost kernel: [ 6.231002] [drm] nouveau 0000:04:00.0: allocated 1024x768 fb: 0x8020000, bo ffff880608d97800
    Jul 26 23:52:06 localhost kernel: [ 6.233786] Console: switching to colour frame buffer device 128x48
    Jul 26 23:52:06 localhost kernel: [ 6.235094] fb0: nouveaufb frame buffer device
    Jul 26 23:52:06 localhost kernel: [ 6.235094] drm: registered panic notifier
    Jul 26 23:52:06 localhost kernel: [ 6.235098] [drm] Initialized nouveau 0.0.16 20090420 for 0000:04:00.0 on minor 0
    Jul 26 23:52:06 localhost kernel: [ 6.255449] HDA Intel 0000:04:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
    Jul 26 23:52:06 localhost kernel: [ 6.255451] hda_intel: Disable MSI for Nvidia chipset
    Jul 26 23:52:06 localhost kernel: [ 6.255599] HDA Intel 0000:04:00.1: setting latency timer to 64
    Jul 26 23:52:06 localhost kernel: [ 7.663482] EXT4-fs (sda3): re-mounted. Opts: (null)
    Jul 26 23:52:06 localhost kernel: [ 7.807508] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
    Jul 26 23:52:06 localhost kernel: [ 7.851401] Adding 265068k swap on /dev/sda2. Priority:-1 extents:1 across:265068k
    Jul 26 23:52:06 localhost kernel: [ 8.569682] r8169 0000:08:00.0: eth0: link down
    Jul 26 23:52:06 localhost kernel: [ 8.569687] r8169 0000:08:00.0: eth0: link down
    Jul 26 23:52:06 localhost dhcpcd[747]: eth0: waiting for carrier
    Jul 26 23:52:08 localhost dhcpcd[747]: eth0: carrier acquired
    Jul 26 23:52:08 localhost kernel: [ 10.301736] r8169 0000:08:00.0: eth0: link up
    Jul 26 23:52:08 localhost dhcpcd[747]: eth0: broadcasting for a lease
    Jul 26 23:52:12 localhost dhcpcd[747]: eth0: offered 131.181.53.42 from 131.181.127.32
    Jul 26 23:52:13 localhost dhcpcd[747]: eth0: acknowledged 131.181.53.42 from 131.181.59.48
    Jul 26 23:52:13 localhost dhcpcd[747]: eth0: checking for 131.181.53.42
    Jul 26 23:52:18 localhost dhcpcd[747]: eth0: leased 131.181.53.42 for 43200 seconds
    Jul 26 23:52:18 localhost dhcpcd[747]: forked to background, child pid 774
    Jul 26 23:52:18 localhost crond[823]: /usr/sbin/crond 4.5 dillon's cron daemon, started with loglevel info
    Jul 26 23:53:01 localhost crond[823]: FILE /etc/cron.d/prune-cronstamps USER root PID 835 job prune-cronstamps
    Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 836 job sys-hourly
    Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 837 job sys-daily
    Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 838 job sys-weekly
    Any help fixing this would be greatly appreciated.

    I have been trying to isolate the problem a little further. I re-installed (with just the base and sudo) and after upgrading pacman rebooted and it worked without fail. Then I installed libusb and libusb-compat which where required when I tried to upgrade just the kernel using
    pacman -S kernel26
    which initially failed because of the missing dependencies libusb and libusb-compat. I then re-booted and that worked without a problem.
    I then upgraded to Kernel 2.6.39 using the above command and then it hung on rebooting. I saved the logs at each stage.
    The additional logs in errors.log in the reboot that failed are as follows.
    ul 26 16:28:39 O313 kernel: [ 5.120698] [drm] nouveau 0000:04:00.0: Pointer to BIT loadval table invalid
    Jul 26 16:28:39 O313 kernel: [ 5.360508] [drm] nouveau 0000:04:00.0: failed to load fuc409d
    Jul 26 16:28:39 O313 kernel: [ 5.808016] sd 20:0:0:0: [sdb] Assuming drive cache: write through
    Jul 26 16:28:39 O313 kernel: [ 5.809960] sd 20:0:0:0: [sdb] Assuming drive cache: write through
    Jul 26 16:28:39 O313 kernel: [ 5.812116] sd 20:0:0:0: [sdb] Assuming drive cache: write through
    Jul 26 16:28:35 O313 udevd[369]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'
    The end of kernel.log is as follows:
    Sat Jul 9 14:57:41 CEST 2011
    Jul 26 16:28:39 O313 kernel: [ 0.000000] Command line: root=/dev/disk/by-uuid/e4733c60-3e54-4001-a83e-415b690dfcb0 ro
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-provided physical RAM map:
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000000100000 - 00000000cfed0000 (usable)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfed0000 - 00000000cfed1000 (ACPI NVS)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfed1000 - 00000000cfee0000 (ACPI data)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfee0000 - 00000000cff00000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000100000000 - 0000000630000000 (usable)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] NX (Execute Disable) protection: active
    Jul 26 16:28:39 O313 kernel: [ 0.000000] DMI 2.4 present.
    Jul 26 16:28:39 O313 kernel: [ 0.000000] DMI: Gigabyte Technology Co., Ltd. X58A-UD5/X58A-UD5, BIOS FD 02/01/2011
    Jul 26 16:28:39 O313 kernel: [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] No AGP bridge found
    Jul 26 16:28:39 O313 kernel: [ 0.000000] last_pfn = 0x630000 max_arch_pfn = 0x400000000
    And this is the end of daemon.log
    Jul 26 16:27:49 O313 init: Switching to runlevel: 6
    Jul 26 16:27:50 O313 dhcpcd: received SIGTERM, stopping
    Jul 26 16:27:50 O313 dhcpcd: eth0: removing interface
    Jul 26 16:28:39 O313 2.352592] udevd[87]: starting version 171
    Jul 26 16:28:39 O313 4.531007] udevd[370]: starting version 171
    Jul 26 16:28:39 O313 dhcpcd: version 5.2.2 starting
    Jul 26 16:28:39 O313 dhcpcd: eth0: waiting for carrier
    Jul 26 16:28:35 O313 udevd[369]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'
    Jul 26 16:28:39 O313 init: Entering runlevel: 3
    Please let me know if any further information would be useful in tracking down this problem. Also ignore any timings in my initial post they were incorrect.
    Last edited by TheStatsMan (2011-07-26 07:40:48)

  • [Solved] UEFI. System hangs on boot after successfully activating swap

    Alright.
    Unnecessary Background:
    I've been using Arch for years. I just bought a stupidly good computer with a bunch of specs that I don't think are relevant, except for the fact that I am using an X99-pro. It has RAID support, but I am not using that currently. I bought all the parts and finished constructing it this morning (I live in Japan, so that was a while ago). Normally, I have no problems with installation; however, I wanted to do this one UEFI mode. After booting into the live disk, I checked to make sure everything was working as it should. Arch recognized my graphics card, most of my ram (one of the cards is a bit finicky for some reason), my SSD and HDD, along with the built-in WiFi (although it is an annoying broadcom one, so I need to install the driver separately later). Now, there are plenty of sources of error in here:
    Problem:
    I got through the arch installation and tried gummiboot. It would hang every time after successfully activating swap. I tried grub, too, but had the same problem. Because gummiboot is much less cumbersome, I switched back to that. Interestingly, systemd will sometimes recognize my drive twice before activating swap, and if I edit my fstab to ignore the swap completely, it hangs on the next step with is mounting the boot partition. I would like to point out that because I am not able to successfully boot my system, I cannot provide the exact messages for you guys, which may pose a problem.
    Solutions I have tried:
    1. Chrooting / mkinitcpio -p linux
    2. modifying fstab / removing swap from it completely
    3. fresh re-install
    Sources of error:
    1. Construction. Everything seems appropriate on the live usb, but maybe there is a problem in which ports I used for the SSD and HDD
    2. UEFI. It could be that UEFI just doesn't like mounting multiple things and freezes up when put on the spot.
    3. Legacy. It could be that this is not a problem with UEFI or my construction, but something I missed in the installation.
    Additional info:
    Partitioning scheme:
    sda1: ~500MiB boot / EFI partition
    sda2: ~4G swap
    sda3: ~110G /
    sdb:   ~2T, untouched (for storage later)
    I apologize for any typos and hope it was readable. I am super exhausted and going to take a nap. I'll check back in on this in the morning.
    Last edited by Leios (2015-02-08 00:16:27)

    Please post the output of:
    # gdisk -l /dev/sda
    lsblk -f
    And the contents of your gummiboot loader.conf and arch.conf (or whatever you've called it).
    Post the output of the commands after you have mounted all your partitions and (arch-)chroot'd into your system.
    You can use wgetpaste to post the outputs, as described by @ewaller here:
    https://bbs.archlinux.org/viewtopic.php … 8#p1500528
    Alternatively, pipe the command output to a text file and export it (using a live distribution or a USB stick).
    You should remove swap from your fstab -- systemd mounts it automatically anyway.

  • Hangs on boot after lion upgrade

    I've upgraded to Lion and since upgrading my macbook pro hangs when booting about 4 out of 10  times.  I get to the desktop and then get a never-ending spinning color wheel.
    2.8 Gb core 2 duo
    8 GB ram
    Summer 2009 model

    When you boot in single user or safe mode, all third party software is prevented from started. So it is possbile one of your third party party applications that are starting at boot is not compatable with the new RAM. I would try turning it all off and then test them all each in turn.
    Allan

  • Unable to boot after failed 10.10.2 update

    Hey all,
    I have an early 2008 24" 2.8GHz iMac with a 120GB Intel 320 SSD and 6GB RAM that I installed myself. I performed a clean install of Yosemite 10.10.0, and with the 10.10.1 update, there were no issues, and the machine ran fine. However, when I attempted to update my Mac to 10.10.2, I ran into a serious problem.
    Like many Yosemite users, it was very difficult to download the update from the Mac App Store update tab when it was first released. The download was occurring at a very slow rate taking well over two hours . I wasn't using my iMac for anything else during this time.
    At some point during this process a family member accidentally unplugged the router. I went back to the Mac to check on it, and although the update was only halfway downloaded according to the App Store, the computer automatically restarted to apply the update before I could stop it.
    I saw the update progress bar and the update seemed to install without any problems. However, when the Mac went to reboot, I was greeted with the prohibitory symbol. I tried restarting several times without success. I also tried to boot into Safe Mode and even single user mode, and neither worked. I also reset the SMC and zapped the PRAM, which didn't help. I also booted into the recovery partition on the drive and ran Disk Utility's repair disk on both the partition as well as the disk itself, and ran a permissions repair. It also didn't work.
    I even hooked up my iMac to a friend's MBP via Firewire Target Disk Mode, and installed the 10.10.2 standalone update to the iMac, but it also didn't work. I was going to attempt the 10.10.2 combo update, but I read that it wasn't working for 10.10.1 systems, and only worked for 10.10.0 installs. I have a copy of the Disk Warrior 4.4 CD, and I booted up from that on the iMac and rebuilt the disk directory, but no luck.
    Fortunately, I do have a Time Machine backup on an external HDD. I also don't exclude anything from the TM backups, which includes the System folder from OS X, so I attempted a restore from from my backup using the recovery partition. I have backups from well before the install began. I first tried earlier in the day before the install began, and when that didn't fix anything I tried a restore from a backup from a few days ago, but that didn't even work either!
    Finally, I was forced to do an in-place reinstall of Yosemite from the recovery partition. The reinstall worked, and I was able to boot successfully into the desktop. Unfortunately, I have some missing files, specifically two months worth of Quicken data entry and part of my documents folder. I do know that I backed everything up via TM, so I'm not sure why those items are missing. Also, my Chameleon SSD Optimizer app won't open, and appears to be corrupted.
    I'm trying to understand what exactly happened, and if there was another method I could have taken to get the Mac working again, other than the laundry list of things I tried. Since I had the iMac fully backed up (including system files) with TM before I tried to download and install the botched update, should I have tried to format the OS X partition with my recovery partition, and then run the TM restore so it could have replaced the corrupted system files with the working backup copy, rather than perform an in-place reinstall of Yosemite? Could I still do that now to get my files back?
    Another thing I don't understand is why the Mac ran the update after it lost Internet connection in the middle of the update, which wasn't even finished downloading. Shouldn't the system have checked the update to ensure the entire bundle was downloaded before executing the install process?

    What is your OS? Database version?
    What is the error you get?
    Can you find any errors in the database/apache log files?
    Thanks,
    Hussein

  • Can't start OS after 10.4.11 combo update (PPC)

    During 10.4.11 combo update it stopped with an error. It didn't look to be a problem since my system was running and I just close the update and continued using my mac.
    However, when I decided to restart my system, it won't stat just showing the gray display with the Apple logo and the spinning wheel.
    Safe boot didn't work. It shutdowns.
    /sbin/fsck -fy doesn't complete successfully.
    I'm traveling overseas and I don't have the system DVD with me nor my external hard drive with my backup.
    What are my options if I have any.

    General advice on updating:
    It is worth noting that it is an extreme rarity for updates to cause upsets to your system, as they have all been extensively beta-tested, but they may well reveal pre-existing ones, particularly those of which you may have been unaware. If you are actually aware of any glitches, make sure they are fixed before proceeding further.
    So before you do anything else:
    If you can, make a full backup first to an external hard disk. Ideally you should always have a bootable clone of your system that enables you to revert to the previous pre-update state.
    Turn off sleep mode for both screen and hard disk.
    Disconnect all peripherals except your keyboard and mouse.
    1. Repair Permissions (in Disk Utility)
    2. Verify the state of your hard disk using Disk Utility. If any faults are reported, restart from your install disk (holding down the C key), go to Disk Utility, and repair your startup disk. Restart again to get back to your startup disk.
    At least you can now be reasonably certain that your system does not contain any obvious faults that might cause an update/upgrade to fail.
    3. Download the correct version of the COMBO update from the Apple download site. If your car runs on gasoline you would not want to fill the tank with diesel, so don’t try to install the PPC updater on an Intel Mac!
    The 10.4.11 Combo Updater for PPC Macs is here: http://support.apple.com/downloads/MacOS_X_10_4_11_Combo_Update__PPC
    And for Intel Macs: http://www.apple.com/downloads/macosx/apple/macosx_updates/macosx10411comboupdat eintel.html
    If you prefer to download updates via Software Update in the Apple menu (which would ensure that the correct version for your Mac was being downloaded), it is not recommended to allow SU to install major (or even minor) updates automatically. Set Software Update to just download the updater without immediately installing it. There is always the possibility that the combined download and install (which can be a lengthy process) might be interrupted by a power outage or your cat walking across the keyboard, and an interrupted install will almost certainly cause havoc. Once it is downloaded, you can install at a time that suits you. You should make a backup copy of the updater on a CD in case you ever need a reinstall.
    Full details about the 10.4.11 update here: http://support.apple.com/kb/TA24901?viewlocale=en_US
    More information on using Software Updater here:
    http://support.apple.com/kb/TA24901?viewlocale=en_US
    Using the Combo updater ensures that all system files changed since the original 10.4.0 are included, and any that may have been missed out or subsequently damaged will be repaired. The Delta updater, although a temptingly smaller download, only takes you from the previous version to the new one, i.e. for example from 10.4.10 to 10.4.11. Software Update will generally download the Delta updater only. The preferable Combo updater needs to be downloaded from Apple's download site.
    Now proceed as follows:
    4. Close all applications and turn off energy saving and screensaver.
    5. Unplug all peripherals except your keyboard and mouse.
    6. Install the update/upgrade. Do not under any circumstances interrupt this procedure. Do not do anything else on your computer while it is installing. Be patient.
    7. When it ask for a restart to complete the installation, click restart. This can take longer than normal, there are probably thousands of files to overwrite and place in the correct location. Do nothing while this is going on.
    8. Once your Mac is awake, repair permissions again, and you should be good to go!
    If your Mac seems slightly sluggish or ‘different’, perform a second restart. It can’t hurt and is sometimes efficacious!
    9. Open a few of your most used applications and check that all is OK. In this connection please remember that not all manufacturers of third party applications and plug-ins, add-ons, haxies etc, will have had time to do any necessary rewrites to their software to make them compliant with the latest version of your operating system. Give them a weeks or two while you regularly check their websites for updates. This applies particularly to plug-ins for Safari 3.
    N.B. Do not attempt to install two different updates at the same time as each may have different routines and requirements. Follow the above recommendations for each update in turn.
    Lastly, Apple's own article on the subject of Software Update may also be useful reading:
    http://docs.info.apple.com/article.html?artnum=106695
    If you are updating Safari (or just have):
    Input Managers from third parties can do as much harm as good. They use a security loophole to reach right into your applications' code and change that code as the application starts up. If you have installed an OS update and Safari is crashing, the very first thing to do is clear out your InputManagers folders (both in your own Library and in the top-level /Library), log out and log back in, and try again.
    So, disable all third party add-ons before updating Safari, as they may not have been updated yet for the new version. Add them back one by one. If something goes awry, remove it again and check on the software manufacturer's website for news of an update to match your version of Safari. Remember: Tiger up to 10.4.10 used Safari 2.0.4 or, if you downloaded it, Safari 3.0.3 beta. Safari 10.4.11 used Safari 3.0.4 which was not a beta. If Safari 3.1.2 on 10.4.11 is not the fastest browser you have ever used, then something is wrong!
    Moreover, trying to revert to Safari 3.0.4 (or worse still, version 2) when running 10.4.11 or 10.5 can have repercussions, as Safari 3.1.1 uses a completely different webkit on which other applications like iChat, Mail and Dashboard Widgets etc also rely, and may entail you having to reinstall an earlier operating system.
    Most errors reported here after an update are due to an unrepaired or undetected inherent fault in the system, and/or a third party ad-on. Two such add-on that have been frequently mentioned here for causing such problems are Piclens and Pithhelmet. If you have them, trash them.
    Additional tips on software installation here:
    http://docs.info.apple.com/article.html?artnum=106692
    To reiterate, Input Managers reach right into an application and alter its code. This puts the behavior of the affected application outside the control and responsibility of its developers: a recipe for problems. That's not to say that issues absolutely will ensue as a result of Input Managers, but you, as a user, must decide. If the functionality of a specific Input Manager or set thereof is really important to you, you may well choose to assume the associated risk.
    Again, the advice is to remove all Input Managers from the following directories:
    • /Library/InputManagers
    • ~/Library/InputManagers
    especially prior to system updates (they can always be added back one-by-one later).

  • Eternal beach ball after 10.8.5 Combo Update

    Just installed the 10.8.5 combo update on my mac mini (2013, i7).
    Everything was, of course, working perfectly with 10.8.4
    Now I get the eternal spinning beach ball just before the login.
    I've already verified the boot hard drive, repaired permissions, cleared the chaches, reset pram, reset smc, etc.
    Pretty much everything I can do just shy of a clean reinstall (which would've taken less time).
    Boots fine in sigle user and safe mode.
    Only workaround has been to remove the physical ethernet connection (using wireless) and ensure the two usb bus powered devices -- a canon lide scanner, and an Asus USB DVD burner -- are disconnected prior to booting the computer. Symptoms that are widespread and linked directly to the .5 update and are not addressed in the supplementals.
    Any other possible solutions or perhaps someone knows if apple is still working on the issue?
    Unplugging USB devices is merely a hassle, but not one i'm going to live with. I will take the time to reinstall and stop with the 10.8.4 update if I have to. I'd rather not, but since there was nothing wrong with the system or hardware I have no problem with stopping there. the .5 update didn't include anything i needed.
    Don't waste your time posting if you are going to advise me that it's something other than the update that borked things. It's the update and I've already confirmed it. It's not my software as i run nothing aside from MS Office and Adobe CS6 beyond what apple preinstalled. Unless you can specifically point to a conflict with the files in the update and either of those two packages, keep your opinions out of this discussion. If you can, i welcome the data.
    Thank you.

    I also encountered this "spinning beach ball of death right when I'm supposed to see the login screen" issue. It happened to three of the laptops I manage (two MacBook Pro 13" retina, and one MacBook Pro 15" retina; all late 2012 models). The "spinning beach ball of death" symptoms started manifesting themselves right after I performed "software update" on them.
    The symptoms: I get the spinning beach ball (or sometimes just stuck with a grey screen) when waking from sleep, when switching users, right after a reboot, right after a cold boot, just as I was trying to get back to work after the screen saver kicked in ... it doesn't happen 100% of the time, but I'd say about 3/4 of the times I expect to see a login screen, I got the spinning beach ball of death (or the grey screen of death).
    This is what I think solved the problem: Rebuilding the Spotlight Search Index.
    (Apple's How-To instruction here: http://support.apple.com/kb/ht2409 )
    Be sure to disable screen saver, set "computer sleep" and "display sleep" timers to infinity before the start the rebuilt process (explanation below).
    I also did other things like resetting PRAM, repairing disk permissions, rebuilding the directories with DiskWarrior, etc. But the best I could tell, it's the rebuilding of the Spotlight Search Index that actually did it. I speculate that the system, while trying to show you the login screen, was also trying to fetch some images or info (the users' login profile pictures, the background wallpaper, whatever), but somehow couldn't find the data and got stuck because of some issue with the Spotlight Search Index. So once the Spotlight Search Index is rebuilt, the "spinning beach ball" problem went away.
    So which software update component broke the system? As counter-intuitive as it may seem, I'm pointing my finger at the component Apple calls the "Digital Camera RAW Compatibility Update" version 5.01. As I mentioned earlier, I observed this problem on three different laptops, and I updated them weeks apart on multiple occasions ... I've gone days and weeks on two of them after the 10.8.5 Supplemental Update without problem, I've gonve days on another laptop after the Safari 6.1, Remote Desktop Client 3.7.0, iTunes 11.1.3 updates without problem. The only constant that applies across all three laptops was that right after the "Digital Camera RAW Compatibility Update" version 5.01 was applied, the "spinning beach ball of death" symptoms started manifesting themselves. That's why I'm pointing my finger at the "Digital Camera RAW Compatibility" version 5.01 update as the prime suspect. (Secondary suspects, if I have to name them, would be the Safari 6.1, Remote Desktop Client 3.7.0, iTunes 11.1.3 updates.)
    On rebuilding the Spotlight Search Index ... this is a long process. It's will likely take hours (depends on how much data you have on your drive). You don't want the screen saver or the display sleep or the computer sleep timer to trigger and lead you right back to the spinning beach ball while you wait for the Spotlight Search Idex to rebuild. That's why the recommendation to disable screen saver and set the sleep timers to "infinity" before starting the index rebuild process. If you try monitor the rebuild process by eyeing at the "mds" and mdworker" CPU utilization ... don't get faked out by the occasional lulls when the system shows you that "mds" and "mdworker" CPU utilizations are zeros. "mds" and "mdworker" appear to take short breaks once in a while, and that starts up in earnest again eating up close to 100% of CPU cycles when they work. Rebuilding the Spotlight Search Index is supposed to take "hours," so best guest, I'd say wait at least one hour, then check if "mds" and "mdworker" CPU utilization figures stay consistently close to zero for a few minutes before calling it done. I do not know of any better way to tell if the system has finished rebuilding the Spotlight Search Index.
    All the above are based on my experience rescueing a grand total of THREE computers back from their software update-induced "spinning beach ball of death" problem. So granted it is a very small sample base. My apologies in advance if it turns out the above does not solve the problem for you. (I'm just going to skip the "Digital Camera RAW Compatibility" version 5.01 update going forward as I have no desire to "recreate the problem" just to test my hypothesis.)
    Good luck!

  • IMac not waking up from sleep after 10.6.6 combo update

    Prior to update everything working fine, permissions repaired, file structures sound, no issues. After update, iMac won't wake up properly from sleep. Moving mouse (either Bluetooth or wired) has no reaction. Hitting key on keyboard (Apple aluminum extended wired keyboard) causes desktop screen to appear, but the spinning gear/pinwheel appears in screen center, and continues to spin. This continues and continues, no reponse from keyboard/mouse. Only work around has been to force quit computer and reboot. Problem repeats next time computer goes to sleep. Repairing permissions has not effect on issue, but now list of permissions getting repaired is very lengthy. Causes? Solutions?

    Macster,
    Try using Disk Utility to do a Disk Repair, as shown in this link, while booted up on your install disk.
    You could have some directory corruption. Let us know what errors Disk Utility reports and if DU was able to repair them. Disk Utility's Disk Repair is not perfect and may not find or repair all directory issues. A stronger utility may be required to finish the job. If you own one, run it first.
    After that Repair Permissions.
    No need to report Permissions errors....we all get them.
    Then, Try downloading the 10.6.6 Combo update, from this site (yours may be corrupt), not Software Update disconnect all firewire + USB devices except keyboard + mouse,Repair Permissions, re-install update, Repair Permissions again + try. 
    DALE

  • Issue after 10.7.5 combo update from 10.7.4

    10.7.5 Combo updater has messed up up all 3 iMac 3.4GHZ i7 SSD 16GB Ram I upgraded from 10.7.4.
    -The worse nightmare of all:
    Spotlight has become DEAD slow to index main boot SSD with only 45gb used 203 free, it shows 3 days with 10.7.4 it was doing it in less than 10 minutes.
    I killed and relaunched spotlight, cleared old index, set only Boot drive marking all other drive including Timemachine with PRIVACY and tried most of the trick, same issue on the 3 computers I can't fix it. (Reset PRAM,Repair Perm run Diskwarrior, Reapplied 1075 combo)
    Therefore Timemachine is also now veryslow when Spotlight is trying to index the main drive (even after excluding all drive and timemachine via Privacy)
    - In the dock all shortcuts for folders and file from my NAS are becoming faceless with a question mark after each restart. Clicking on them re-activate the icon until the next restart. (DiskStation DS212+ Synology connected via AFP), Synology might have to update their software, I guess.
    - Fast User Switching is activated by default top right of menu bar, it can be cleared via User& Group, clicking on Login Option and deslecting Show fast user switching menu.
    Any one having problem with spotlight ? Solution welcome.

    Same here, in my case:
    1. My iTunes works slower than before, it took a while to completely sync my iPhone4s. And try to update the apps, no response after clicking the "download all free updates" as if nothing happens
    2. Safari, Try to open a web site, let say www.apple.com.........it didnt load the full site entirely on the first attempt, i always hit the refresh icon to make the job done
    3. Last but not least, this completed my nightmare, i've upgrade all of my idevices into iOS6(iTouch 4G & iPhone4s), Siri seems having some problems in answering my questions.....or maybe because of my provider connection, and it freeze when i try to update some of my apps direcly from the phone, luckily iOS6 didnt compatible with my 1st Gen iPad, so i can write this issue into this forum.

  • Mac OS won't boot after 2007-009 1.1 update

    Hi all
    Fairly major problem here. Mac OS X won't boot after the 2007-009 1.1 security update.
    What I am left with is the mac boot screen, and not a lot happening. No rotating loading animation.
    Any help would be really appreciated.
    Thanks

    I have been booting up for...2.45 hours now
    Good grief!
    Here are a few hints about what you should have done:
    There are no guarantees, but following this procedure when installing updates and upgrades on your Mac will go a long way towards avoiding unpleasant after effects and ‘post-update stress disorder’.
    It is also worth noting that it is an extreme rarity for updates to cause upsets to your system, but they may well reveal pre-existing ones, particularly those of which you may have been unaware. If you are actually aware of any glitches, make sure they are fixed before proceeding further.
    So before you do anything else:
    If you can, make a full backup first.
    Turn off sleep mode for both screen and hard disk.
    Disconnect all peripherals except your keyboard and mouse.
    1. Repair Permissions (in Disk Utility)
    2. Verify the state of your hard disk using Disk Utility. If any faults are reported, restart from your install disk (holding down the C key), go to Disk Utility, and repair your startup disk. Restart again to get back to your startup disk.
    At least you can now be reasonably certain that your system does not contain any obvious faults that might cause an update/upgrade to fail.
    3. Download the correct version of the COMBO update from the Apple download site. If your car runs on gasoline you would not want to fill the tank with diesel, so don’t try to install the PPC updater on an Intel Mac!
    If you prefer to download updates via Software Update in the Apple menu (which would ensure that the correct version for your Mac was being downloaded), it is not recommended to allow SU to install major (or even minor) updates automatically. Set Software Update to just download the updater without immediately installing it. There is always the possibility that the combined download and install (which can be a lengthy process) might be interrupted by a power outage or your cat walking across the keyboard, and an interrupted install will almost certainly cause havoc. Once it is downloaded, you can install at a time that suits you. You should make a backup copy of the updater on a CD in case you ever need a reinstall.
    Using the Combo updater ensures that all system files changed since the original 10.4.0 are included, and any that may have been missed out or subsequently damaged will be repaired. The Delta updater, although a temptingly smaller download, only takes you from the previous version to the new one, i.e. for example from 10.4.9 to 10.4.10. Software Update will generally download the Delta updater only. The preferable Combo updater needs to be downloaded from Apple's download site.
    Now proceed as follows:
    4. Close all applications.
    5. Unplug all peripherals except your keyboard and mouse.
    6. Install the update/upgrade. Do not under any circumstances interrupt this procedure. Do not do anything else on your computer while it is installing. Be patient.
    7. When it ask for a restart to complete the installation, click restart. This can take longer than normal, there are probably thousands of files to overwrite and place in the correct location. Do nothing while this is going on.
    8. Once your Mac is awake, repair permissions again, and you should be good to go!
    If your Mac seems slightly sluggish or ‘different’, perform a second restart. It can’t hurt and is sometimes efficacious!
    9. Open a few of your most used applications and check that all is OK. In this connection please remember that not all manufacturers of third party applications and plug-ins, add-ons, haxies etc, will have had time to do any necessary rewrites to their software to make them 10.4.10. compliant. Give them a weeks or two while you regularly check their websites for updates. This applies particularly to plug-ins for Safari 3.
    N.B. Do not attempt to install two different updates at the same time as each may have different routines and requirements. Follow the above recommendations for each update in turn.
    Lastly, Apple's own article on the subject of Software Update may also be useful reading:
    http://docs.info.apple.com/article.html?artnum=106695
    If you are updating Safari (or just have):
    Input Managers from third parties can do as much harm as good. They use a security loophole to reach right into your applications' code and change that code as the application starts up. If you have installed 10.4.11 and Safari is crashing, the very first thing to do is clear out your InputManagers folders (both in your own Library and in the top-level /Library), log out and log back in, and try again.
    So, disable all third party add-ons before updating Safari, as they may not have been updated yet for the new version. Add them back one by one. If something goes awry, remove it again and check on the software manufacturer's website for news of an update to match your version of Safari. Remember: Tiger up to 10.4.10 used Safari 2.0.4 or, if you downloaded it, Safari 3.0.3 beta. Safari 10.4.11 uses Safari 3.0.4 which is not a beta. If Safari 3.0.4 on 10.4.11 is not the fastest browser you have ever used, then something is wrong!
    Moreover, trying to revert to Safari 2 when running 10.4.11 can have repercussions, as Safari 3.0.4 uses a completely different webkit on which other applications like iChat, Mail and Dashboard Widgets etc also rely.
    Most errors reported here after an update are due to an unrepaired or undetected inherent fault in the system, and/or a third party ad-on. Two such add-on that have been frequently mentioned here for causing such problems are Piclens and Pithhelmet. If you have them, trash them.
    Additional tips on software installation here:
    http://docs.info.apple.com/article.html?artnum=106692

  • Early 2008 MacBook Pro won't boot after Lion 10.7.1 update

    My 2.4 GHz 4GB RAM Early 2008 MacBook Pro wont boot after downloaded the Lion 10.7.1 upate. Upon restarting the screen went dead and now the system does not boot, as if the bootloader has been wiped out. Screen appears dead but was known to be working before hand. The hard drive spins up but doesn't sound like it is searching for data.
    Can anyone help me?

    Okay, I tried everything I can think of last night. I removed every startup process and every tool or programm that goes deeper into the system (GlimmerBlocker, LittleSnitch, Parallels). Cleaned Up every Cache I could find and refreshed every necessary Cache or Database possible. Took me a couple of hours. But still no luck - the machine doesn't boot, just in safe mode. Right now I copy all my personal stuff to a new external harddrive because TimeMachine doesn't work, after this I will do a clean install of Lion.
    It's not hardware related, it's the 10.7.1 update that doesn't work properly. By the way, the only errors remaining are:
    WindowServer - kCGErrorFailure
    ManagedClient - kCGErrorFailure: CGSPackageGetWorkspaceType: couldn't get workspace type
    SecurityAgent - kCGErrorFailure: CGSPackageGetWorkspaceType: couldn't get workspace type
    and a lot of:
    com.Apple.SecurityAgent.00000000-0000-0000-0000-0000000186A7: CoreAnimation: rendering error 506
    that's also the last one I get before the system hangs…

  • Still cannot open App Store even after 10.6.8 Combo Update

    Any help on this would be most appreciated. Thanks in advance.
    I need to get the App Store working so that I can re-install a Lion upgrade that I already purchased before. I had to replace my HD and now with 10.6.8, the App Store will not open.
    I have installed the 10.6.8 Combo Update and then done the other software updates through the System Preferences.
    This still comes up when I try to open App Store:
    "App store cannot be opened because of a problem.
    Check with the developer to make sure App Store works with this version of Mac OS X. You may need to reinstall the application. Be sure to install any available updates for the application and Mac OS X.
    Click Report to see more detailed information and send a report to Apple."
    This is the "Problem Details and System Configuration":
    Process:         App Store [389]
    Path:            /Applications/App Store.app/Contents/MacOS/App Store
    Identifier:      com.apple.appstore
    Version:         ??? (???)
    Build Info:      Firenze-630100~1
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [149]
    Date/Time:       2012-06-06 18:07:10.498 -0700
    OS Version:      Mac OS X 10.6.8 (10K549)
    Report Version:  6
    Interval Since Last Report:          538 sec
    Crashes Since Last Report:           54
    Per-App Crashes Since Last Report:   3
    Anonymous UUID:                      9639C764-6944-44CC-BD36-A7F304335113
    Exception Type:  EXC_BREAKPOINT (SIGTRAP)
    Exception Codes: 0x0000000000000002, 0x0000000000000000
    Crashed Thread:  0
    Dyld Error Message:
      Library not loaded: /System/Library/PrivateFrameworks/Install.framework/Frameworks/DistributionKit. framework/Versions/A/DistributionKit
      Referenced from: /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/CommerceKit
      Reason: image not found
    Binary Images:
        0x7fff5fc00000 -     0x7fff5fc3be0f  dyld 132.1 (???) <29DECB19-0193-2575-D838-CF743F0400B2> /usr/lib/dyld
    Model: MacBook2,1, BootROM MB21.00A5.B07, 2 processors, Intel Core 2 Duo, 2 GHz, 2 GB, SMC 1.17f0
    Graphics: Intel GMA 950, GMA 950, Built-In, spdisplays_integrated_vram
    Memory Module: global_name
    AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x87), Atheros 5416: 2.1.14.6
    Bluetooth: Version 2.4.5f3, 2 service, 19 devices, 1 incoming serial ports
    Network Service: AirPort, AirPort, en1
    Serial ATA Device: Hitachi HTS727575A9E364, 698.64 GB
    Parallel ATA Device: MATSHITACD-RW  CW-8221
    USB Device: Built-in iSight, 0x05ac  (Apple Inc.), 0x8501, 0xfd400000 / 2
    USB Device: Apple Internal Keyboard / Trackpad, 0x05ac  (Apple Inc.), 0x021a, 0x1d200000 / 2
    USB Device: Bluetooth USB Host Controller, 0x05ac  (Apple Inc.), 0x8205, 0x7d100000 / 2
    USB Device: IR Receiver, 0x05ac  (Apple Inc.), 0x8240, 0x5d200000 / 2

    Try uninstalling the App Store app using this utility >  Download AppCleaner for Mac - Uninstall your apps easily. MacUpdate.com
    Just moving the App Store app to the Trash doesn't delete all the associated files.
    Then try the  Mac OS X 10.6.8 Update Combo
    Restart your Mac after the combo is installed.
    See if that will reinstall the App Store so you can re download Lion.
    At some point, you may need the original install discs even if that works.
    Replacement disc(s) from Apple:   You can get replacement System Install & Restore CD/DVDs from Apple's Customer Support - in the US, (800) 767-2775 - for a nominal S&H fee. You'll need to have the model and/or serial number of your Mac available.

  • Not Booting after recent Security Patch/Java update

    My wife has experienced what many have experienced with the recent update.
    MacBook not booting after update (i.e. - "I have no name!")
    I have tried everything posted on this topic since 2/13/09, but without any success. Does anyone have the fix for this yet?
    Things I have tried:
    * I can boot in safe mode (holding "Shift" while restarting)
    * I cannot boot from an install disk(s) (holding C while restarting) - I have both a black one from purchase, and two gray ones with purchase from MiniMac
    * Booting with verbose - gets stuck at same place as everyone else
    Operating in safe mode:
    * I can run DU and "repair" drive
    * I can see and access the CD/DVD
    * I cannot see drive in target drive mode (doesn't ever connect the 2 systems)
    * I downloaded the update files from apple and reinstalled them individually (via USB ext Drive) with a reboot in between
    * I attempted to update & archive, but I cannot run install CD from any systems disks (see above)
    Has anyone figured out how to fix this yet?

    Same problem than the other guy who is not mentioning the update in the title.
    Powerbook 1.67.
    System log said "No user defined computer name" and "using blah blah name" or so.
    Mac Os X report (for apple) says:
    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000003900FF1C PC=0x00000000008FC020
    Latest crash info for cpu 0:
    Exception state (sv=0x4299D280)
    PC=0x008FC020; MSR=0x00009030; DAR=0x3900FF1C; DSISR=0x40000000; LR=0x008FE348; R1=0x2C47B9F0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x008FE348 0x008E0014 0x002E9A80 0x002EB94C 0x0008C248 0x00029234
    0x000233F8 0x000ABEAC 0xFF9BA29B
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.ATIRadeon9700(4.1.8)@0x8d8000
    dependency: com.apple.iokit.IOPCIFamily(1.7)@0x48d000
    dependency: com.apple.iokit.IOGraphicsFamily(1.4.2)@0x85a000
    dependency: com.apple.iokit.IONDRVSupport(1.4.2)@0x87e000
    Proceeding back via exception chain:
    Exception state (sv=0x4299D280)
    previously dumped as "Latest" state. skipping...
    Exception state (sv=0x43D0D000)
    PC=0x9000AF48; MSR=0x0200F030; DAR=0x0ECA77FE; DSISR=0x42000000; LR=0x9000AE9C; R1=0xBFFFD6C0; XCP=0x00000030 (0xC00 - System call)
    Kernel version:
    Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
    panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
    Latest stack backtrace for cpu 0:
    Backtrace:
    0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
    Proceeding back via exception chain:
    Exception state (sv=0x4299D280)
    PC=0x008FC020; MSR=0x00009030; DAR=0x3900FF1C; DSISR=0x40000000; LR=0x008FE348; R1=0x2C47B9F0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x008FE348 0x008E0014 0x002E9A80 0x002EB94C 0x0008C248 0x00029234
    0x000233F8 0x000ABEAC 0xFF9BA29B
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.ATIRadeon9700(4.1.8)@0x8d8000
    dependency: com.apple.iokit.IOPCIFamily(1.7)@0x48d000
    dependency: com.apple.iokit.IOGraphicsFamily(1.4.2)@0x85a000
    dependency: com.apple.iokit.IONDRVSupport(1.4.2)@0x87e000
    Exception state (sv=0x43D0D000)
    PC=0x9000AF48; MSR=0x0200F030; DAR=0x0ECA77FE; DSISR=0x42000000; LR=0x9000AE9C; R1=0xBFFFD6C0; XCP=0x00000030 (0xC00 - System call)
    Kernel version:
    Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC

Maybe you are looking for

  • Is there a way to send SMS/mms messages on ipad mini

    Is there a way to send SMS/mms messages on ipad mini

  • Move database files from one ASM diskgroup to another

    We are working on 11.2.0.3 RAC environment. We have an activity in which we have to move ASM database files from one diskgroup to another. We have the sufficient downtime for the activity. On checking MOS it says copying datafiles from "rman copy" co

  • Spotify Connect windows client disappearing

    Dear all, Is there any issues with spotify connect dissapearing after a while of inactivity ? I am trying to stream spotify to hifi system via a HTPC ( running windows server 2012 ) .Everything is working fine when the app on the server is freshly ru

  • Replace multiple characters to single character

    Hi friends, I would like to replace multiple characters in a string to a single character. The character may be a pipe (|) or a tilde (~). For example "|||asdf||123|xyz||" should be changed to "asdf|123|xyz". I use Oracle 11g2. Thanks in advance!

  • Making a transparent image

    Hi Everyone, I created a text in Photoshop cs and am trying to superimpose that over a video in FCE 4, how can I make the text background transparent so I don't have to mess with key adjustments in FCE 4? Thank you