Mac OS 10.5 - frozen during boot

I have a macbook with leopard os installed (kernel version: Darwin 9.0). I installed xcode on my mac yesterday. About 2-3 hours later, the system just froze up. (xcode was not running. I was just doing some browsing.) So I did a cold shut down/restart. The system makes the loud chime at the start and then stops at the grey screen. Looks like it doesn’t know where to load the os from.
I inserted the leopard install dvd on startup. When it gets to the installation screen, I get a message box “Mac OS X cannot be upgraded to v10.5 on your computer”,”Mac OS X v 10.4 or later could not be found on your computer’. I said OK and then ran the +disk utility+.
When I try to verify my mac partition, I get the following error:
Verifying volume “diskos2”
Checking journaled HFS plus volume
Catalog file entry not found for extent
Volume check failed
and then the msgbox, +"Filesystem verify or repair failed"+.
And Verify stops there. Any suggestions on how I can fix the problem. It’s been a while since I last backed up my hard drive. So I’d ideally like to recover as much data as possible first. From the Diagnostic utility on the DVD, on the Serial-ATA tab, under the Volumes section I see Windows but not the MAC partition. The S.M.A.R.T status says verified.
Any help is appreciated.

Sounds like time for DiskWarrior.
If your HD was failing, then installing a large amount of data like XTools could have done it in.
Usually flaky HDs crash when new data are written into unused areas that are marginal.
DiskWarrior might help.
If you are also running Windows, that could be the problem if your A/V program writes or checks the bootsector of the drive.
Message was edited by: nerowolfe

Similar Messages

  • My mac book pro has frozen during installation of OS X Yosemite.  What to do?

    my mac book pro has frozen during installation of OS X Yosemite.  What should I do?

    Wait it out for couple of hours.
    Hope you have a backup.
    If you have a backup ready, restart the computer.

  • Q10 frozen during booting on Blackberry screen - is it dead?

    HI i have my Q10 for more then one year and moreless except couple restarts or frozen situation was working fine. Today i have restarted it (due to not responding settings)and during booting in stuck on Blackberry screen and that all.
    I found that more people have faces this situation but i have not found any exact solution.
    I have tried to take out battery and sim form more then one hour and then start it again..  No success
    It is charging on wall charger more then one hour, took out battery put back.. No success.
    Tried to restart via poewer button couple times. No success.
    I am quite furious now as I was strong blackberry fan and now seems that it let me down...
    I have no idea what to do as i am not using Blackberry link, and If i am loosing my contacts or data I will be really considering my stay with BB for future.
    Has anybody real solutiuon what to do please? Thanks

    Hello,
    It sounds like you have tried things close to this, but not quite this. Therefore, please try this sequence...note that, throughout the entire 4h15m process, your BB must remain directly connected to a known-good wall charger (not PC USB, not a cradle):
    With the battery inside, connect your BB to the wall charger
    Leave it alone for 2 hours, no matter what the LED or the display does
    Remove the battery
    Wait 15 minutes
    Insert the battery
    Wait another 2 hours, no matter what the LED or the display does
    This has been known to "kick start" some BBs. If it fails to help, then please retry but increase the wait time in step 4 to 2 hours, and perhaps as long as 4-5 hours.
    It is also possible that your battery or BB has experienced a problem...to test, this sequence is needed:
    Obtain an known good and already fully charged additional battery...use it in your BB and see what happens
    Obtain access to a known good and identical BB...use your battery in it and see what happens
    The results of this will indicate if it's your BB or your battery that has the problem. Note carefully please that "new" and "know good" are not necessarily the same things. While rare, a "new" battery certainly could be defective. Rather, the simplest (and least costly, btw) method to conduct this test is to find someone with an identical BB who has no issues...trade batteries and see what happens.
    brunko wrote:
    I am quite furious now as I was strong blackberry fan and now seems that it let me down...
    I have no idea what to do as i am not using Blackberry link, and If i am loosing my contacts or data I will be really considering my stay with BB for future.
    Really? You ignored the fact that this computing device, like ALL of them, is prone to error and imperfection, and thereby chose not to conduct a backup via any of the FREE methods BB provides? And for this you blame BB? Backups, like insurance, are neither a reactive nor an optional activity.
    A backup would be required in order to proceed via any other recovery methods. But, with the state your BB is in, there is little chance of taking such a backup now. So, if all else fails, I would recommend you reload your OS via AutoLoader and see if it can at least get your BB running again. Without that backup which you chose to never do, you of course will have to start over, taking the hard lesson of migrating from the latter to the former of this old saying:
    There are two kinds of computing device users -- those who have lost data, and those who will
    Good luck and let us know!
    Occam's Razor nearly always applies when troubleshooting technology issues!
    If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
    Join our BBM Channels
    BSCF General Channel
    PIN: C0001B7B4   Display/Scan Bar Code
    Knowledge Base Updates
    PIN: C0005A9AA   Display/Scan Bar Code

  • Frozen during boot

    I am powering on my iMac and it boots only so far as the apple logo--then goes into a holding pattern (the spinning thing indicating something is going on) but nothing else happens.  I am running on Mountain Lion.  What is going on?

    Take each of these steps that you haven't already tried. Stop when the problem is resolved.
    Step 1
    The first step in dealing with a boot failure is to secure your data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since your last backup, you can skip this step.   
    There are several ways to back up a Mac that is unable to boot. You need an external hard drive to hold the backup data.a. Boot into Recovery by holding down the key combination command-R at the startup chime, or from a local Time Machine backup volume (option key at startup.) Release the keys when you see a gray screen with a spinning dial. When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in the support article linked below, under “Instructions for backing up to an external hard disk via Disk Utility.”
    How to back up and restore your files
    b. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, boot the non-working Mac in target disk mode by holding down the key combination command-T at the startup chime. Connect the two Macs with a FireWire or Thunderbolt cable. The internal drive of the machine running in target mode will mount as an external drive on the other machine. Copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
    How to use and troubleshoot FireWire target disk mode
    c. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
    Step 2
    Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to boot, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can boot now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
    If you've booted from an external storage device, make sure that your internal boot volume is selected in the Startup Disk pane of System Preferences.
    Step 3
    Boot in safe mode.* The instructions provided by Apple are as follows:
    Shut down your computer, wait 30 seconds, and then hold down the shift key while pressing the power button.
    When you see the gray Apple logo, release the shift key.
    If you are prompted to log in, type your password, and then hold down the shift key again as you click Log in.
    Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    *Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t boot in safe mode. Post for further instructions.
    When you boot in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, your boot volume is damaged and the drive is probably malfunctioning. In that case, go to step 5.
    If you can boot and log in now, empty the Trash, and then open the Finder Info window on your boot volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then reboot as usual (i.e., not in safe mode.)
    If the boot process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
    Step 4
    Sometimes a boot failure can be resolved by resetting the NVRAM.
    Step 5
    Launch Disk Utility in Recovery mode (see step 1.) Select your startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
    This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then reboot as usual.
    Step 6
    Boot into Recovery again. When the OS X Utilities screen appears, follow the prompts to reinstall the OS. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
    Note: You need an always-on Ethernet or Wi-Fi connection to the Internet to use Recovery. It won’t work with USB or PPPoE modems, or with proxy servers, or with networks that require a certificate for authentication.
    Step 7
    Repeat step 6, but this time erase the boot volume in Disk Utility before installing. The system should automatically reboot into the Setup Assistant. Follow the prompts to transfer your data from a backup.
    Step 8
    A dead logic-board battery in a Mac Pro can cause a gray screen at boot. Typically the boot failure will be preceded by loss of the startup disk and system clock settings. See the user manual for replacement instructions.
    Step 9
    If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store to have the machine tested.

  • Mac Mini G4 shuts down during boot-up

    Hi All,
    Just upgraded a G4 Mac Mini to Leopard, all was going fine until today. I just ran software update to install the very latest Security Update along with MobileMe and now the following happens: the machine starts to boot up as normal - grey screen, dark grey apple, progress spinner for about 30 seconds, then the whole thing just shuts down. Happens every time now.
    I haven't yet had chance to boot from the Leopard DVD but are there any smart bods out there with a similar experience who can give me a clue as to what's happened...? I've just spent the last 24 hours getting Leopard and various bits of software installed!
    Thanks!
    JF

    Sorry to hear about the loss of the iTunes library, though if you had another Mac available you might find the files are recoverable by getting the mini into firewire target disk mode. If Disk Utility found difficulty with the catalog rather than widespread data corruption, much of the data on the drive may be recoverable despite DU's inability to effect a repair.
    I think you are right however to go the erase and install route to get the system back into service. Utilities such as Tech Tools and Disk Warrior can often effect repairs, but there is nothing as good as a reformat and reinstall in terms of reliability, and creating confidence in the system's on-going use.

  • New MacBook frozen during boot

    My friend got a brand new MacBook for Christmas and after slowing down and freezing a bit it finally will not boot past the translucent spiral "Loading" page. It's not clear whether he was running Tiger or Leopard (he wasn't sure). His OS disc has been misplaced but we're assuming we should just do a clean reinstall with the OS. Any ideas what's up?

    Is there any way to reset / reinstall the system without losing the data on my hard drive?
    Boot from the install DVD and do an Archive and Install.
    Mac OS X: About the Archive and Install feature >>
    -Bmer
    Mac Owners Support Group - Join us @ MacOSG.com
      Mac611 Mobile Mac Support - about.Mac611.com
       iTunes:MacOSG Podcast | YouTube.MacOSG.com
                       An Apple User Group 
    Have an iPhone or iPod touch? Enter Mac611.com in Safari on it for 'mobile Mac support.'

  • New Mac Pro 2013 late version USB 3.0 hub issue during boot

    Hi all, I just purchased a new Mac Pro 8 core with 32GB of ram and 1 TB drive. When I connect a USB powered 3.0 hub and turn on my Mac Pro, it gets hung on while booting. (Gray screen before the Apple logo appears on boot). If I pull the USB 3.0 hub out, the Mac Pro proceeds to boot normally. Once I am fully booted on my Mac Pro and I plug the USB 3.0 hub back in, everything seems to work fine. I have an enclosure that works off of lightening connector and the enclosure has a USB 3.0 hub onboard. I plug the USB 3.0 hub in that device and every thing seems to boot up fine on the Mac Pro. Any idea why when I plug in the USB 3.0 directly why the Mac Pro ha issues booting up?
    Thanks in Advance.

    The Driver for the Hub does not get loaded until late in the Boot-up process.
    It is common not to be able to use devices on a Hub during boot-up, as they will not be ready (and therefore not available) until the Login screen appears.
    For devices you need during boot-up, attach directly to a built-in USB port on the chassis, not on a display or any other Hub.
    If your issue is only that the device interferes with Booting in general, ask the guys at OWC. They select their stocked items for trouble-free, and train their support people to resolve remaining problems quickly. If there is a problem, they will help you get is fixed quickly -- often providing an advanced exchange if that seems appropriate.

  • I forgot my passcode, so I was unable to access my phone. I then tried to restore it, but it has frozen during the process. It won't connect to my mac again and I can't stop the process because my lock button is broken. What do I do?

    I forgot my passcode, so I was unable to access my phone. I then tried to restore it, but it has frozen during the process. It won't connect to my mac again and I can't stop the process because my lock button is broken. What do I do?

    My first advice is "Back up the device, then have it replaced."  Second item of advice, "Don't forget your passcode."
    One of the purposes of the lock button is to recover from certain software failures.  Without the lock button, such a recovery is nearly impossible.  My advice would have served you best when the malfuction first developed, not after you forgot your passcode.

  • Mac Mini keeps hanging during boot

    My ~3 year old Mac Mini keeps freezing during booting with the error message "You need to restart your computer. Hold down the Power button...". This happens every time. Booting in safe mode works.
    This happened with Mac OS X Tiger but keeps happening even after I have completely reformatted that hard disk and reinstalled Leopard from scratch. There are no external devices connected to the computer besides the monitor and a bluetooth mouse and keyboard.
    After reading some discussion forums I have already tried starting into Open Bootware and running "reset-nvram" and "reset-all" but to no avail.

    Welcome to Apple Discussions!
    What you are suffering is a Kernel Panic, and given you have reformatted your drive and reinstalled MacOS, it would tend to suggest the issue is hardware related - most common culprit being RAM.
    http://docs.info.apple.com/article.html?artnum=106227 explains what kernel panics are, and http://www.thexlab.com/faqs/kernelpanics.html and http://www.index-site.com/kernelpanic.html may give some assistance in working through the problem to determine the cause.
    The one good thing is that your system appears sufficiently stable to allow you to boot to the Leopard installer and complete a full install. This makes it less likely there is a fundamental issue with the most expensive component of the system, the logic board.

  • My iMac is frozen on boot up screen

    My iMac is frozen on boot up it is stuck in the grey screen with apple logo wheel just keeps spinning for days , help!

    For  Mac OS X 10.4, Mac OS X 10.5, Mac OS X 10.6   Try here >  OS X: Gray screen appears during startup
    If you have Lion v10.7 installed, you can use Lion Recovery to repair the startup disk or reinstall the Mac OS X if necessary.
    It helps to tell us which Mac OS X you have installed. 

  • I am getting frequent lock-ups and blue screens during boot up. The lock ups occur during normal use and I cannot click anything or force quit. The cursor shows something is loading, but never stops. I have to use power button. Ideas?

    I am getting frequent lock-ups and blue screens during boot up on my Mac Pro.  The lock- ups occur sometimes during normal use and I cannot click anything or force quit. The cursor shows something is loading, but never stops. I have to use power button.
    I had the Mac Defender malware and I have used apple jack but still having issues.

    I am getting frequent lock-ups and blue screens during boot up on my Mac Pro.  The lock- ups occur sometimes during normal use and I cannot click anything or force quit. The cursor shows something is loading, but never stops. I have to use power button.
    I had the Mac Defender malware and I have used apple jack but still having issues.

  • Eth0 is being up and down for several time during boot

    My wicd doesn't connect to eth0 on the first attempt after boot up. It is configured to eth0 always have a higher priority to connect.
    My dmesg shows that eth0 being up and down for several time during boot. I have e1000e in my MODULES list.
    Here is my rc.conf
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
    # startup and during the boot process. If set to 'no', the C locale is used.
    # HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
    # in the hardware clock being left untouched (useful for virtualization)
    # Note: Using "localtime" is discouraged, using "" makes hwclock fall back
    # to the value in /var/lib/hwclock/adjfile
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # Note: if unset, the value in /etc/localtime is used unchanged
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="en_US.UTF-8"
    DAEMON_LOCALE="no"
    HARDWARECLOCK=""
    TIMEZONE="Asia/Hong_Kong"
    KEYMAP="us"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
    # Replace every !module by an entry as on the following line in a file in
    # /etc/modprobe.d:
    # blacklist module
    # See "man modprobe.conf" for details.
    MOD_AUTOLOAD="yes"
    MODULES=(acpi-cpufreq fuse tp_smapi vboxdrv e1000e)
    # Udev settle timeout (default to 30)
    UDEV_TIMEOUT=30
    # Scan for FakeRAID (dmraid) Volumes at startup
    USEDMRAID="no"
    # Scan for BTRFS volumes at startup
    USEBTRFS="no"
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="antony-tp"
    # Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
    # Wired network setup
    # - interface: name of device (required)
    # - address: IP address (leave blank for DHCP)
    # - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
    # - broadcast: broadcast address (ignored for DHCP) (optional)
    # - gateway: default route (ignored for DHCP)
    # Static IP example
    # interface=eth0
    # address=192.168.0.2
    # netmask=255.255.255.0
    # broadcast=192.168.0.255
    # gateway=192.168.0.1
    # DHCP example
    # interface=eth0
    # address=
    # netmask=
    # gateway=
    # Setting this to "yes" will skip network shutdown.
    # This is required if your root device is on NFS.
    NETWORK_PERSIST="yes"
    # Enable these netcfg profiles at boot-up. These are useful if you happen to
    # need more advanced network features than the simple network service
    # supports, such as multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up (dialog package required)
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This requires the netcfg package
    #NETWORKS=(main)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    # - prefix a daemon with a ! to disable it
    # - prefix a daemon with a @ to start it up in the background
    # If something other takes care of your hardware clock (ntpd, dual-boot...)
    # you should disable 'hwclock' here.
    DAEMONS=(!hwclock syslog-ng dbus !network !dhcpcd rpcbind acpid @wicd nfs-common netfs @crond cups @laptop-mode @alsa @sensors ntpd @slim bluetooth)
    Here is a segment of my dmesg
    [ 2.759302] e1000e: Intel(R) PRO/1000 Network Driver - 1.5.1-k
    [ 2.759304] e1000e: Copyright(c) 1999 - 2011 Intel Corporation.
    [ 2.759338] e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
    [ 2.759348] e1000e 0000:00:19.0: setting latency timer to 64
    [ 2.759467] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
    [ 2.766107] tpm_tis 00:0a: 1.2 TPM (device-id 0x0, rev-id 78)
    [ 2.766808] ACPI: AC Adapter [AC] (on-line)
    [ 2.776492] wmi: Mapper loaded
    [ 2.777212] mei: module is from the staging directory, the quality is unknown, you have been warned.
    [ 2.777781] thermal LNXTHERM:00: registered as thermal_zone0
    [ 2.777783] ACPI: Thermal Zone [THM0] (66 C)
    [ 2.778291] iTCO_vendor_support: vendor-support=0
    [ 2.780137] ACPI: Battery Slot [BAT0] (battery present)
    [ 2.780958] input: PC Speaker as /devices/platform/pcspkr/input/input4
    [ 2.781462] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07
    [ 2.781547] iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460)
    [ 2.781919] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
    [ 2.783139] cfg80211: Calling CRDA to update world regulatory domain
    [ 2.789182] [drm] Initialized drm 1.1.0 20060810
    [ 2.789538] hub 4-1:1.0: USB hub found
    [ 2.789616] hub 4-1:1.0: 8 ports detected
    [ 2.792925] Non-volatile memory driver v1.3
    [ 2.795877] thinkpad_acpi: ThinkPad ACPI Extras v0.24
    [ 2.795879] thinkpad_acpi: http://ibm-acpi.sf.net/
    [ 2.795881] thinkpad_acpi: ThinkPad BIOS 8DET54WW (1.24 ), EC unknown
    [ 2.795882] thinkpad_acpi: Lenovo ThinkPad X220, model 4290NL5
    [ 2.797236] thinkpad_acpi: detected a 8-level brightness capable ThinkPad
    [ 2.797352] thinkpad_acpi: radio switch found; radios are enabled
    [ 2.797466] thinkpad_acpi: possible tablet mode switch found; ThinkPad in laptop mode
    [ 2.799752] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
    [ 2.800067] Registered led device: tpacpi::thinklight
    [ 2.800091] Registered led device: tpacpi::power
    [ 2.800106] Registered led device: tpacpi::standby
    [ 2.800120] Registered led device: tpacpi::thinkvantage
    [ 2.800192] thinkpad_acpi: Standard ACPI backlight interface available, not loading native one
    [ 2.800254] thinkpad_acpi: Console audio control enabled, mode: monitor (read only)
    [ 2.801077] input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input5
    [ 2.801162] sdhci: Secure Digital Host Controller Interface driver
    [ 2.801164] sdhci: Copyright(c) Pierre Ossman
    [ 2.801707] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
    [ 2.801709] Copyright(c) 2003-2011 Intel Corporation
    [ 2.801744] iwlwifi 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    [ 2.801753] iwlwifi 0000:03:00.0: setting latency timer to 64
    [ 2.801789] iwlwifi 0000:03:00.0: pci_resource_len = 0x00002000
    [ 2.801791] iwlwifi 0000:03:00.0: pci_resource_base = ffffc90005abc000
    [ 2.801793] iwlwifi 0000:03:00.0: HW Revision ID = 0x34
    [ 2.801877] iwlwifi 0000:03:00.0: irq 49 for MSI/MSI-X
    [ 2.801913] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Advanced-N 6205 AGN, REV=0xB0
    [ 2.801962] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
    [ 2.802045] sdhci-pci 0000:0d:00.0: SDHCI controller found [1180:e822] (rev 7)
    [ 2.802067] sdhci-pci 0000:0d:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    [ 2.802107] sdhci-pci 0000:0d:00.0: setting latency timer to 64
    [ 2.802118] _regulator_get: 0000:0d:00.0 supply vmmc not found, using dummy regulator
    [ 2.802188] Registered led device: mmc0::
    [ 2.803329] mmc0: SDHCI controller on PCI [0000:0d:00.0] using DMA
    [ 2.815226] iwlwifi 0000:03:00.0: device EEPROM VER=0x715, CALIB=0x6
    [ 2.815229] iwlwifi 0000:03:00.0: Device SKU: 0X1f0
    [ 2.815231] iwlwifi 0000:03:00.0: Valid Tx ant: 0X3, Valid Rx ant: 0X3
    [ 2.815247] iwlwifi 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
    [ 2.845674] iwlwifi 0000:03:00.0: loaded firmware version 17.168.5.3 build 42301
    [ 2.845820] Registered led device: phy0-led
    [ 2.850630] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
    [ 2.862431] usb 1-1.2: new low-speed USB device number 3 using ehci_hcd
    [ 2.943648] e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) f0:de:f1:92:77:26
    [ 2.943651] e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
    [ 2.943712] e1000e 0000:00:19.0: eth0: MAC: 10, PHY: 11, PBA No: 1000FF-0FF
    [ 2.943734] mei 0000:00:16.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    [ 2.943739] mei 0000:00:16.0: setting latency timer to 64
    [ 2.943817] mei 0000:00:16.0: irq 50 for MSI/MSI-X
    [ 2.944502] agpgart-intel 0000:00:00.0: Intel Sandybridge Chipset
    [ 2.945021] agpgart-intel 0000:00:00.0: detected gtt size: 2097152K total, 262144K mappable
    [ 2.946341] watchdog: INTCAMT: cannot register miscdev on minor=130 (err=-16).
    [ 2.946452] watchdog: error registering /dev/watchdog (err=-16).
    [ 2.946523] mei: unable to register watchdog device.
    [ 2.946598] agpgart-intel 0000:00:00.0: detected 65536K stolen memory
    [ 2.946692] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xe0000000
    [ 2.946734] i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
    [ 2.948359] snd_hda_intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
    [ 2.948422] snd_hda_intel 0000:00:1b.0: irq 51 for MSI/MSI-X
    [ 2.948444] snd_hda_intel 0000:00:1b.0: setting latency timer to 64
    [ 3.022245] usb 1-1.3: new full-speed USB device number 4 using ehci_hcd
    [ 3.172080] usb 1-1.4: new full-speed USB device number 5 using ehci_hcd
    [ 3.274597] Bluetooth: Core ver 2.16
    [ 3.274611] NET: Registered protocol family 31
    [ 3.274612] Bluetooth: HCI device and connection manager initialized
    [ 3.274614] Bluetooth: HCI socket layer initialized
    [ 3.274614] Bluetooth: L2CAP socket layer initialized
    [ 3.274618] Bluetooth: SCO socket layer initialized
    [ 3.275535] Bluetooth: Generic Bluetooth USB driver ver 0.6
    [ 3.276006] usbcore: registered new interface driver btusb
    [ 3.338454] usb 1-1.6: new high-speed USB device number 6 using ehci_hcd
    [ 3.444567] Linux media interface: v0.10
    [ 3.447387] Linux video capture interface: v2.00
    [ 3.448573] input: Logitech Trackball as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input6
    [ 3.448671] generic-usb 0003:046D:C404.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech Trackball] on usb-0000:00:1a.0-1.2/input0
    [ 3.448690] usbcore: registered new interface driver usbhid
    [ 3.448691] usbhid: USB HID core driver
    [ 3.449136] uvcvideo: Found UVC 1.00 device Integrated Camera (04f2:b217)
    [ 3.450945] input: Integrated Camera as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input7
    [ 3.450987] usbcore: registered new interface driver uvcvideo
    [ 3.450988] USB Video Class driver (1.1.1)
    [ 3.484049] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input8
    [ 3.491137] HDMI status: Codec=3 Pin=5 Presence_Detect=0 ELD_Valid=0
    [ 3.491298] HDMI status: Codec=3 Pin=6 Presence_Detect=0 ELD_Valid=0
    [ 3.491486] HDMI status: Codec=3 Pin=7 Presence_Detect=0 ELD_Valid=0
    [ 3.491637] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
    [ 3.491709] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
    [ 3.491765] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
    [ 3.492050] i915 0000:00:02.0: power state changed by ACPI to D0
    [ 3.492053] i915 0000:00:02.0: power state changed by ACPI to D0
    [ 3.492059] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    [ 3.492062] i915 0000:00:02.0: setting latency timer to 64
    [ 3.538056] mtrr: no more MTRRs available
    [ 3.538058] [drm] MTRR allocation failed. Graphics performance may suffer.
    [ 3.538266] i915 0000:00:02.0: irq 52 for MSI/MSI-X
    [ 3.538270] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
    [ 3.538271] [drm] Driver supports precise vblank timestamp query.
    [ 3.538292] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
    [ 3.664501] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.0, id: 0x1e2b1, caps: 0xd001a3/0x940300/0x120c00
    [ 3.664518] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0
    [ 3.716317] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input12
    [ 4.407165] fbcon: inteldrmfb (fb0) is primary device
    [ 4.575259] Console: switching to colour frame buffer device 170x48
    [ 4.577042] fb0: inteldrmfb frame buffer device
    [ 4.577043] drm: registered panic notifier
    [ 4.607860] acpi device:01: registered as cooling_device4
    [ 4.607985] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input13
    [ 4.608039] ACPI: Video Device [VID] (multi-head: yes rom: no post: no)
    [ 4.608122] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
    [ 4.757243] EXT4-fs (sda3): re-mounted. Opts: discard
    [ 4.765917] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: discard
    [ 4.776777] Adding 262140k swap on /dev/sda2. Priority:-1 extents:1 across:262140k SS
    [ 5.099467] NET: Registered protocol family 10
    [ 6.048650] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [ 6.098038] Bluetooth: RFCOMM TTY layer initialized
    [ 6.098055] Bluetooth: RFCOMM socket layer initialized
    [ 6.098057] Bluetooth: RFCOMM ver 1.11
    [ 6.278766] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
    [ 6.278893] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
    [ 6.568639] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
    [ 6.568775] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
    [ 6.684082] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 7.176563] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
    [ 7.226662] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
    [ 7.227110] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 10.229345] IBM TrackPoint firmware: 0x0e, buttons: 3/3
    [ 10.490618] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio2/input/input14
    [ 10.817814] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [ 10.819315] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 11.186166] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
    [ 11.186292] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
    [ 11.313367] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 11.665342] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
    [ 11.717591] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
    [ 11.718042] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 11.964795] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
    [ 12.017213] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
    [ 12.017720] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 13.811264] EXT4-fs (sda3): re-mounted. Opts: discard,commit=0
    [ 13.826031] EXT4-fs (sda4): re-mounted. Opts: discard,commit=0
    [ 15.178905] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [ 15.180472] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 25.663056] eth0: no IPv6 routers present
    Any hint for tracing the root of this problem? Thank you very much!

    Hi ...
    If you have moved the Safari application from the Applications folder, move it back.
    As far as the cache goes, there's a work around for that when you can't empty the Safari cache from the menu bar.
    Go to    ~/Library/Caches/com.aple.Safari.Cache.db.  Move the Cache.db file to the Trash.
    Try Safari.
    Mac OS X (10.7.2)   <  from your profile
    If that is corrrect, you need to update your system software. Click your Apple menu icon top left in your screen. From the drop down menu click Software
    Update ...
    ~ (Tilde) character represents the Home folder.
    For Lion v10.7x:  To find the Home folder in OS X Lion, open the Finder, hold the Option key, and choose Go > Library

  • Mac mini mid 2011 won't boot

    This morning I found my Mac mini mid 2011 frozen. I shut it down by holding the power button.
    Now it does not boot. When I turn it on I don't hear the usual chime sound or any other beeps. I can hear the hard drive powering on and the fan starts to work at full speed. Nothing appears on the monitor. No output signal at all.
    I have tried disconnecting all cables, press power button for five seconds and the. Try to boot again. No luck...
    Any ideas?? I loads of work to do and I am loosing hope. No apple stores in Greece to take it in...

    I've tried everything including SMC rreset. No luck.
    One other clue is that if try to boot up without Ram installed, it recognizes that ram is missing and beeps  
    so to summarize the symptoms:
    1. Computer has power
    2. No chime sound or any other beep when I power the computer on
    3. Fan works at full speed
    4. No output display signal
    5. I can hear the hard drive powering on
    6. The computer recognizes if you try to boot it without ram and beeps

  • HT5313 it seems the comupter is frozen during the update of OS X Lion TO v10.7.5

    it seems the comupter is frozen during the update of OS X Lion TO v10.7

    Antony D&#39;Emanuele wrote:
    Can anyone provide me with a link to the OS X bash Update 1.0 for OS X Lion Server v10.7.5, apparently there is a specific update. I have searched the Apple site without success, I have found the Mavericks, Mountain Lion and Lion version but not the server versions (which do exist, see Apple security updates)
    With Lion and later there is no such thing as a server version of the operating system, this is unlike the previous Mac OS X 10.6 aka. Snow Leopard which did have a specific server version of the operating system.
    So, in reality one only needs Lion, Mountain Lion and Mavericks versions. The server software is merely an application these days.

  • Mac Pro takes more time to boot than average

    Okay, well my Mac Pro (2008) takes anything between 40 and 48 seconds to boot (that's the time between pressing the power button and seeing the desktop with mouse movement). Being a long-time PC user, this boot time is MUCH faster than anything I've used before, but apparently it's longer than it should be. I was recently in a forum where most Mac Pro users had boot times of anything between 25 and 35 seconds.
    As for hardware, I have no peripherals plugged in (except for Apple mouse and keyboard). The major software that I've installed is the Adobe Master Collection (including programs such as Photoshop, After Effects, Encore, Premiere Pro, Illustrator, InDesign, Dreamweaver, Flash, Fireworks, VersionCue, etc.)
    I've looked at my Console messages, and I've noticed that the message "kcdmond cannot retreive the computer's local Hostname, retrying..." is repeated 3 times. This repetition takes up 20 seconds. See all the Console messages during boot-up below:
    18/4/08 1:00:53 PM com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
    18/4/08 1:00:53 PM com.apple.launchd[1] (com.adobe.versioncueCS3) Unknown key: ServiceDescription
    18/4/08 1:00:53 PM com.apple.launchd[1] (org.cups.cups-lpd) Unknown key: SHAuthorizationRight
    18/4/08 1:00:53 PM com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
    18/4/08 1:00:53 PM com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
    18/4/08 1:01:01 PM com.apple.kdcmond[35] kdcmond cannot retreive the computer's local Hostname , retrying ..
    18/4/08 1:01:06 PM com.apple.kdcmond[35] kdcmond cannot retreive the computer's local Hostname , retrying ..
    18/4/08 1:01:16 PM com.apple.kdcmond[35] kdcmond cannot retreive the computer's local Hostname , retrying ..
    18/4/08 1:01:21 PM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[76]) Exited: Terminated
    18/4/08 1:01:21 PM com.apple.launchctl.Aqua[84] launchctl: Please convert the following to launchd: /etc/machinit_peruser.d/com.adobe.versioncueCS3.monitor.plist
    18/4/08 1:01:22 PM com.apple.launchd[71] (0x1010d0.VersionCueCS3monitor) Failed to check-in!
    18/4/08 1:01:25 PM iChatAgent[106] WARNING: AbstractService loginIfAvailable: SCNetworkCheckReachabilityByName failed!
    18/4/08 1:01:26 PM iChatAgent[106] WARNING: AbstractService loginIfAvailable: SCNetworkCheckReachabilityByName failed!
    18/4/08 1:01:31 PM com.apple.SystemStarter[28] Starting Aladdin USB daemon
    18/4/08 1:01:51 PM com.apple.launchctl.System[2] BootCacheControl: could not fetch history: Cannot allocate memory
    18/4/08 1:01:51 PM com.apple.launchctl.System[2] BootCacheControl: could not stop cache/fetch history: Cannot allocate memory
    I have a few questions based on the above:
    1. What is kdcmond, and why can't it find the host name?
    2. Why is the error message "Failed to check-in!" for Adobe VersionCue appearing? (I've already specified in the VersionCue settings that I do not want it to activate anything on start-up.)
    3. What is "Aladdin USB daemon"?
    4. What is BootCacheControl, and what is with the "cannot allocate memory" errors?

    Okay, so after doing all of the above, the computer still takes between 40 seconds and 1 minute or so to boot up, and the VersionCue messages still appear. However I discovered that the "kdcmond cannot retrieve..." messages disappeared after I disabled my ethernet connections. So at least I know that that had nothing to do with the extended boot-up time.
    I have heard that the more RAM you have, the longer it takes to boot due to the RAM count. Since I have 10 GB, maybe this is why?
    I've included the most recent Console messages below:
    22/4/08 9:56:16 AM com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
    22/4/08 9:56:16 AM com.apple.launchd[1] (com.adobe.versioncueCS3) Unknown key: ServiceDescription
    22/4/08 9:56:16 AM com.apple.launchd[1] (org.cups.cups-lpd) Unknown key: SHAuthorizationRight
    22/4/08 9:56:16 AM com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
    22/4/08 9:56:16 AM com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
    22/4/08 9:56:39 AM com.apple.SystemStarter[28] Starting Aladdin USB daemon
    22/4/08 9:56:39 AM org.ntp.ntpd[25] Error : nodename nor servname provided, or not known
    22/4/08 9:56:39 AM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[74]) Exited: Terminated
    22/4/08 9:56:39 AM com.apple.launchctl.Aqua[90] launchctl: Please convert the following to launchd: /etc/machinit_peruser.d/com.adobe.versioncueCS3.monitor.plist
    22/4/08 9:56:42 AM com.apple.launchd[82] (0x1011e0.VersionCueCS3monitor) Failed to check-in!

Maybe you are looking for

  • HT1483 how do I update my ipod touch with windows 7

    I have a used ipod touch, 4th gen, I think and I'm trying to download some apps and get the message "this app requires iOS 4.3."  Is it possible to update my opperating system?

  • Why doesn't the not interested button in genius in the app store do anything?

    I just updated to iOS 6.  One of the first things I tried was the new App Store.  So I checked out Genius. Neat. Except.. when you tap the button to install, the "Install Now" button looks ATTROCIOUS! What were you thinking Apple? With a reputation f

  • 'JS Callback error while executing script' in 4.7

    hello everyone, When I was installing SAP 4.7 after the Database load jobs I am getting an error like ' JS Callback error while ecevuting script'.... Jobs are loading but after thatI was having this error... I tried several times but the error is the

  • How to trigger an SMS after creation of Activity / Interaction Record

    Dear Experts, Our Client requirement is to trigger an SMS immediately after creation of an Interaction Record. I want to define an Action for this. But what processing type should I use for SMS, (like Method Call, Smart Forms Mail / Fax / Print and W

  • No.of.records in a file.

    need your inputs on an issue. In an idoc to file scenario, I have a field "No.of.recs" in file structure. while I am sending this file, I need to populate this also. How can I do it?