Tag Info

Hot answers tagged

2

Something killed your coreaudio drivers, or the sound hardware/motherboard. I would suggest to do following order of investigation (Fixes) Open Activity monitor and look for following: (use sort by "Audio") If found use terminal to reset the coreaudiod sudo killall coreaudiod Copy/paste following in Terminal to find out if the audio drivers are ...


2

1 - I think you need a keyboard to boot holding Alt (Opt) key, to show boot partition and disks. 2 - Yes, if you plug in a USB keyboard it's simply works. Mac OS X has the driver for standard keyboards.


1

To determine if it is your hardware or OS X boot from external drive. If it works it is your OS X, if not, it is your hardware. If it is OS X use Safe mode and: look for non apple drivers loaded using sudo kexstsat in Terminal (enter password)


1

I am pretty sure your MBP always did that. It is something annoying I never really liked about the MBP: They have a "subwoofer" which is situated on the right-hand side of the MacBook. So sounds with a lot of bass always appear to come from the right speaker. Here is what Apple says.


1

In order to diagnose a hardware vs. OS error, try starting from external bootable media. The easiest way to do this is using a Linux Live CD. This allows you to start a totally separate, different and self-sufficient operating system. If you can get sound through that, it means the problem lies within your Mac OS X setup. You can download a disk image here: ...


1

You can try boot your mac in recovery mode (hold command+R while booting), open Terminal, and running fsck to rebuild the btrees that hold the information of your files and directories structure. To rebuild the catalog btree: fsck -d -r /dev/disk0s2 Rebuild extents btree: fsck -d -Re /dev/disk0s2 Rebuild attributes btree: fsck -d -Ra /dev/disk0s2 ...


1

To set the flag to boot in safe mode is the easiest: sudo nvram boot-args="-x" The I guess we have to do something with; rc.boot figures out the type of boot (Multi-User, Safe, CD-ROM, Network etc.). In case of a network boot (the sysctl variable kern.netboot will be set to 1 in which case), it runs /etc/rc.netboot with a start argument. and this; ...


1

These symptoms imply an issue with your GPU. There is actually an ongoing class-action lawsuit against Apple regarding the AMD GPUs in the 2011 Macs (primarily MacBook Pros). I have seen the issue before in person; my sister's MacBook Pro just encountered it. The symptoms were just as you described: boot chime, Apple logo, spinning loader, grey screen, ...



Only top voted, non community-wiki answers of a minimum length are eligible