Meaning of Red Apple during boot

Since I upgraded to Mavericks 10.9.3 on my Retina MBP I've intermittently gotten a red apple for a brief instant during boot! It then switches back to the normal gray. Is this an Easter egg, a bug or does anyone even know?!? This does not happen every time, but has happened several times...
Thanks!

Reset PRAM.  http://support.apple.com/kb/PH4405
    Screen Resolution settings are stored in PRAM.
   What is stored in PRAM?
Speaker volume
Screen resolution
Startup disk selection
Recent kernel panic information, if any
http://support.apple.com/kb/HT1379

Similar Messages

  • Motorola Droid Razr M stops a red eye during boot

    Was updating apps and the phone restarted on it's own. ever since it stops at red eye screen during boot. Tried factory reset - doesn't help - same behavior. I can get to the boot menu but none of the options offer anything useful. Verizon support guys - Any ideas?
    based on other posts, it looks like I may need to try a reflash of the phone. Does Verizon support officially offer any suggestions for that process? is there a legit source for the flash roms? what utility is suggested we use for this? There is no 'official' Verizon store in or near my town.
    -Trevor Jones

    I regret to hear of the issues with your device! I understand the need of a reliable device and I want to make sure that yours works as it should. It seems like you completed your fair share of troubleshooting. I need additional information so that I can better assist. I will send you a private message so that I can assist!
    LenaA_VZW
    Follow us on Twitter @VZWSupport
    If my response answered your question please click the "Correct Answer" button under my response. This ensures others can benefit from our conversation. Thanks in advance for your help with this!!

  • Red screen during boot up in Windows 7

    My Laptop is a Satellite L655D-S5159RD. During and when the booting process starts, the screen displays red color with several vertical lines all through out  the usage. It creates blurry and shaky color while using it. All applications, windows 7 OS and internet browsing are all working properly on top of  that red color layer.  Because of that, all applications that are being used have a distorted color. Any ideas about this problem will be much appreciated. Thank.

    To be clear, this is happening during the boot process, even before Windows finishes loading? Unfortunately, that usually indicates a hardware failure that would require servicing. I'm sorry.
    - Peter

  • VIA Raid 0: Red screen of Death - fatal error during boot sequence

    I have been using two Maxtor 120GB SATA drives in a RAID 0 array on my Athlon 64 MSI MB.  I have occasionally had messages saying "Hard disk error. Can't find drive 0".  I've assumed that this has been a driver issue because if I power down, wait a while I can reboot and continue without issue (other than chkdsk running during boot up).  However after the last such error, when I next tried to reboot I got an error message as the RAID was initialising.  The error message was in a red box on a black screen and stated that there was a fatal error and that the raid relationship and all HHD would be destroyed if I continued.  Naturally I switched off at this point, but on rebooting got exactly the same message.  Eventually, as I have backups, I continued past this point and sure enough the RAID had gone.  So I rebuilt the raid array and everything seems to be OK.
    However, I'd forgotten that my MSI DVD burner was incapacitated due to a failed firmware update so had temporaril;y replace it with a DVD rom drive to get access to my backups.  BUT the drive won't read all my backup discs, in particular it won't read the Drive C backups .
    Has anyone else had this RAID erro.  Is it a driver error or is it a dsik failing (even though they were new at Christmas).
    I am using a Superflower power supply which has 22A on the 12V rail
    1GB PC3200 ram by A-Data (CAS 2.5)
    Elderly HP 9100 CDRW
    MSI DR-8 DVD RW
    Ethernet card
    Radeon 9600 128MB
    AMD64 3000 processor
    Freeflow

    Raids do not really help benchmarks unless you considure hard drive benchmarks. Most games and benchmark proggies load everything they need prior to running. So unless you have a low memory condition that forces the game or benchmark to use the swap file the only place that you would typically see any gain in speed is during the loading of the game or benchmark. That is hard to quantify other than through experience.
    Where a raid shines is in file tranfer situations. When you create and save large files such as movies, Reading or copying large files, defragging, or any other massive file effort. Overall the gains can be very small compaired to the rest of what you do with your system. However that is not to belittle what a Raid does. It does give a finer sheen to the overall computers operations and will make sluggish file transfers seem much more bearable overall.

  • I have an Imac 2.8 GHZ Intel core duo, a month ago during booting instead of the apple, appear a world picture, since Is this normal?? also i feel the computer much slower since then, does any body know what is this?

    I have an Imac 2.8 GHZ Intel core duo, a month ago during booting instead of the apple picture appears a world picture and takes a lot of time to start, Is this normal?? also I feel the computer much slower since then, does any body know what is this?  How can I fix this?  Thanks

    Gomtomsyetm preferencs and make sure that you HDD is selected as the start up disk. Then start up using your install disc and run disk utility and repair the drive just in case something has gotten corrupt.

  • During boot Yosemite shows a grey screen with the Apple logo and a progress bar - is this normal?

    During boot Yosemite shows a grey screen with the Apple logo and a progress bar - is this normal?

    Same here after upgrade yesterday. 
    I can get OS utilities up using CMD R or holding the shift key (eventually), but if I simply then reinstall the OS will it not loose everything on my drive? I do have it backed up on Time Machine? What a nightmare - Apple Support does suck.  I am not paying £25 for them to call me to tell me how to fix a bug in their OS software upgrade.  Any help
    Also does anyone know if it is possible to use time machine to go back to Snow Leopard? I have wasted much of the day on this now
    Cheers
    Simon

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

  • My Imac is showing gray screen with red line when booting and restarts again

    My Imac is showing gray screen with red line when booting and restart again, I can load it in windows 7 safe mode with red lines across the display, pls help

    The graphic card is damaged. You can't do anything more than taking your computer to an Apple Store or reseller and getting your graphic card replaced.
    Sometimes, when the graphic card is damaged, operating systems can't start. That's caused because the drivers that make the graphic card work detect an error, telling the operating system that the graphic card is unusable, so the operating system can't start and it restarts. However, you can start in safe mode because operating systems use a basic driver in this startup mode

  • 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

  • How to diagnose NTP server problem during boot-up?

    We're having a problem on our campus network where Macs aren't able to use the time.apple.com NTP server to correct the time during boot-up. Once the user logs in, open the Date & Time pref pane causes the time to be corrected.
    I've noticed this problem for quite a while but it's really been just a minor inconvenience. Then some users started using Boot Camp and it became a bigger inconvenience because their Mac time is wrong by 4 hours when they return to OS X from Windows XP. It has now become something that we need to address because we have set up a lab with iMacs all configured with Boot Camp and set up to authenticate off of our Active Directory server, which requires that the time be correct on the iMacs when the user tries to log in.
    We'd like to monitor the network traffic on Mac during boot-up to see if we can figure out why this is happening. My person theory is that something that the network admins have the network configured to do when it first sees a new computer is causing enough of a delay in the DHCP process that the Mac doesn't have a network connection when the NTP server call would normally be made. The college has a DSL line that is not part of our network and NTP server time correction works correctly on it.
    We're looking for the best way to capture the activity on the Mac and the network traffic at boot-up. Here are the things that we're looking into.
    1) Verbose mode - Interesting looking but it goes by pretty quickly and I don't have time to read all of that info. Is this recorded in a log automatically somewhere or is there a way to capture this info?
    2) Single user mode - I haven't been able to determine whether the NTP server call should have occurred by the time I get a prompt in Single User Mode. If so, is there a command I could use here that would give me a dump of activity and network traffic up to this point?
    3) I have Interarchy which will let me record network traffic but as far as I can tell there's isn't a way to use this feature during boot-up. Am I wrong about that?
    4) Someone suggested using Ethereal which appears to require Fink when installed. I can't tell if this will work during boot for if it's an app that I can only run after logging in (like Interarchy). Does anyone know how this works?
    Any suggestions would be welcomed.
    -McD-

    Turns out it was a network timing issue. The DHCP server wasn't providing the IP address quick enough (never figured out why, though).

  • After 10.6.2 update system halts during boot

    After having installed the 10.6.2 update via software update my Mac halts during boot. It boots right up to the grey screening displaying the Apple logo and the grey status wheel but doesn't go on from there. It just keeps displaying that screen forever with the status wheel still moving but not hard disk activity anymore after a few minutes.
    I've already tried (via booting from the Snow Leopard DVD), to no avail:
    - repairing permissions
    - repairing the drive
    - resetting the SMC

    You could try [these grey sceen, etc., troubleshooting steps|http://support.apple.com/kb/TS2570] ignoring any duplicaion of what you already have don. And, you could try [these general troubleshooting steps|http://support.apple.com/kb/TS1394] again ignoring duplication.
    If all above fails, then I suggest you do a repair install of Sno by installing Sno over Sno as in an upgrade install. Such an install, while usually very safe, still is an install so be appropriated backed up if you proceed.

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

  • Computer sometimes shuts down during boot, help please.

    Hey guys,
    My specs:
    2500K @ 4.5 GHz 1.37V (12 Hours P95 stable + 10 IBT passes)
    MSI Z77A-GD65
    8GB DDR3-1600 Corsair Vengeance (2x4GB)
    EVGA GTX680 Superclocked
    Crucial M4 SSD 128GB
    WD 1TB Caviar Blue
    Seasonic X-650 PSU
    The PC is roughly 1 year old and I built it.
    Problem is, and this has been ongoing since I built it, sometimes, when I turn on the PC, it will start booting and then power itself off, after that it turns itself back on and Windows 7 loads, exactly what happens when you apple new OC settings for example.
    There is never more than 1 shutdown when this happens and it never happens when the PC is on and working, just during boot.
    I ruled out heating issues, everything is well ventilated in my Corsair 650D case, all fans are working and the CPU temps are good (Using Zalman CNPS10X cooler)
    I think we can also rule out any PSU issues since I recently tested my PC with P95 again after updating my BIOS for more than 12 hours and it was rock solid. I've also never had a shutdown during gaming since I got the PC.
    My Overclock is raw, I have disabled, EuP 2013, C1E, EIST, Overspeed Protection, Intel C-State.
    Is there any BIOS setting which could be causing this? I noticed that there's a setting under EuP 2013 called "Restore after AC Power Loss" and you can choose Power Off/Power On/Last State. But I think it only related to occasions where the PC gets shut down due to a power outage?
    I am inclined to think that this issue is more related to a MB BIOS setting than to the PSU since I never had any stability issues with the PC during OC testing or when gaming.
    Which leaves me with the Power outlet. I am using an outlet splitter and currently there are 7 products connected to 1 socket:
    1. PC
    2. Yamaha RXV-471 Receiver
    3. Morel Sub-8 Subwoofer
    4. PS3 (Off 99% of the time)
    5. Internet Modem/Router
    6. TV Box
    7. 42" LED TV Screen
    The only thing I can think of is that maybe when booting up, not enough power is provided to the PSU and it turns off?
    I have 1 other clear outlet next to the one being used and I'm fairly certain they both go to the same place in the panel because they are adjacent.
    I can also try to replace the power cord, however, I replaced it once and I do recall it was happening prior to replacing the cord several months ago.
    Any suggestions? Thanks

    Quote from: xmad on 27-March-13, 01:37:42
    That's normal, the memory you have is 1333 with an overclock profile of 1600. (XMP) The double cold boot has been an issue for ages on the z77a-gd65 although I thought it was corrected by the latest bios's.
    Oh so true. When it is really cold in the morning, not always, at first start of the machine, I will get a double boot behavior on a Z68 G3. No big deal, as xmad stated, this double boot behavior has been a trait of Intel for a long time. Usually disable of EuP 2013 cures it, but the OC and particular frequency combinations play a part in it, and mysteriously, cold mornings once in awhile.

  • MacBook Air shuts down during boot

    My Macbook Air (OS X Yosemite - Early 2014) automatically shuts down during boot, with the screen flashes during the loading bar at 40% and then shuts down. I've tried to reboot many times but it wouldn't get past the 40% on the loading bar.
    I've also tried the following but none worked:
    The Apple Hardware Test shows that "There may be an issue with a memory module." (PPM002, PPM003, PPM004) - though I've checked that the reference code and the definition doesn't match, as "There may be an issue with a memory module." should be PPM001, and PPM002-PPM015 should be "There may be an issue with the onboard memory.". I've sent this message to Apple and they'd only provided the option to visit their retail store.
    Also, the Recovery Mode isn't much help either. As do not have a backup of my HD, I'm not able to restore from Time Machine Backup.
    So, I've tried to reinstall OS X Yosemite, but it says "Unavailable to install OS X". A website online says that you can resolve this issue by correcting the date through terminal, but the basic menu bar won't appear, in which I'm not able to access Terminal during the Recovery Mode.
    Therefore, I've also tried the Disk Utility, which it shows it can't be repaired, with the following messages: Invalid Node Structure (4, 57963), and 2 messages regarding the Invalid Extent Entry (4, 47013) and (4, 40808). The Single User Mode with the command fsck -fy yields the same message.
    Is there any other options then to visit the Apple Retail Store?

      Invalid node structure
    I'm pretty sure you need more then Disk Utility to repair the drive.
    http://www.alsoft.com/diskwarrior/index.html
    Assuming you have Snow Leopard installed, you can try reinstalling the Mac OS but you'll have to do this from another Mac.
    http://support.apple.com/kb/HT3910
    "Important: For MacBook Air, a MacBook Air SuperDrive, or MacBook Air Software Reinstall Drive is required to complete this procedure."

  • Macbook Pro 17" restarting during boot screen

    This seems to be an on going problem for people. From the threads I've read I could not get a solution.
    My Macbook is turing on and plating the chime, but the screen has been covered in loads of  square patches of purple dots. The Apple logo appears on the grey screen and the wheel starts to turn. What happens is it will do this for a minute or so and then freeze or more often restart and do the same thing again until i force it to turn off.
    I have tried all of the below already
         - Safe Mode (fails and restarts)
         - Single user mode (disk repair command as I could not do it through the graphical interface)
         - Reset using cmd+option+r+p
         - Recovery by holding Option during boot (again freezes or restarts)
    I would use a disc to a reinstall but my optical drive is broken and I do not have access to an external one. I realise I can use a Bootable USB but I only have access to a Windows for the time being. Its probably worth mentioning that was watching a video on Youtube when the whole laptop froze and starting repeating and jerking and then shut down. It has not worked since!
    Can anyone suggest any other posible solutions please?
    Thank you

    My Macbook is turing on and plating the chime, but the screen has been
    covered in loads of  square patches of purple dots. The Apple logo
    appears on the grey screen and the wheel starts to turn. What happens is
    it will do this for a minute or so and then freeze or more often
    restart and do the same thing again until i force it to turn off.
    This seems like a hardware issue.
    All we can suggest is run a #3 Hardware Test, write down what it says and take it into Apple for a free eval.
    ..Step by Step to fix your Mac
    5 year old machine? I'd say it's the video card going because the cooling fins behind the fans haven't been cleaned, heat damage is irreversible.
    Not worth fixing, buy a new machine.
    You can extract the drive and use a SATA to USB adatpter and Migration Assistant to a new Mac.
    My computer is not working, is my personal data lost?

Maybe you are looking for