No internal speakers after EFI- and thunderbolt updates

i got no sound in my internal speakers after the updates.
rebooted and repaired permissions, problem persists

Is there a red light shining in the headphone port ?
If so, some solutions to be found in this threadhttps://discussions.apple.com/message/10384803#10384803
Stefan

Similar Messages

HDCP problems after firmware and thunderbolt update

I just finished installing the recent Macbook Pro EFI Firmware update (version 2.2) as well as the recent Thunderbolt Software Update (version 1.0).
I am now unable to play an HD movie that I purchased through iTunes on the screen of my Macbook Pro. I was watching this movie last night before updating my computer with no problems.
So...it seems likely that this is related to the updates.
Anyone else have this problem or know a solution?
Thanks!
-Jon

I shutdown and restarted my computer and this is no longer a problem.

When I unplug Apple headphones from my MacBook Pro sond from internal speakers not work, and system soud preferences displayed: Output: optical digital out port only

When I unplug Apple headphones from my MacBook Pro sond from internal speakers not work, and system soud preferences displayed: Output: optical digital out port only

If you see a red light in the audio output port, then the internal switch is stuck. Insert the earphone plug a few times and see if you can trip the switch. If that fails, insert a cocktail stirrer and the like and jiggle it around inside. If that fails, take it to an Apple store and have the technicians at the genius bar do it for you.
Ciao.

No sound from internal speakers after using audacity 2.02?

No sound from internal speakers after using Audacity 2.02 ?

Hey iberlin12,
I would check out the article containing recommended troubleshooting steps for when you don't hear audio from a Mac's built-in speakers:
Troubleshooting issues with no audio from built-in speakers on Macs
http://support.apple.com/kb/TS1574
Best,
Delgadoh

Sound 'out' is reset to "Internal speakers" after any restart.

I'd prefer it would stay assigned to "line out" but this won't happen. Has anyone experience with this mystery?

Sound out reverts to internal speakers at every shut down
Sound output reverting to internal speakers after restart

Late 2013 Keyboard / Trackpad still unresponsive AFTER EFI 1.3 update

I thought I would start a new thread / discussion since the previous thread here seems to be riddled with "install the update" suggestions and off topic assistance such as battery life questions. I have also logged detailed information regarding this issue on my professional blog here.
Anyway, here is a short, condensed version of my story. I have had two brand new late 2013 Retina MacBook Pro's with the 2.4/16GB/256 configuration. Since the config I chose is a CTO, this problem has been going on since the day the first model arrived (December 10th, 2013). The EFI update was preinstalled on both systems and I can verify that because the boot ROM version is MBP111.0138.B03 (the boot rom prior to the update ended in B00 or B01). I am also an AASP and an ACMT meaning that I am certified and employed with a company that allows me to fix all Apple hardware under warranty. I am well-versed in technology and Apple hardware and I have never seen anything quite like this.
Here is the quick summary of things I have attempted and I have been able to re-recreate the issue:
The system will not mount the root device when I boot via a known good external hard drive running 10.9.1. Verbose mode and Single user mode reports a still waiting for root device error.
The system (rMBP) will not boot from another system (late 2011 MacBook Pro 13") when said system (late 2011 MacBook Pro) pushed into target disk mode via thunderbolt.
My system, rMBP, will boot up with the internal SSD but will not allow the keyboard and track pad to function. The caps lock key will not illuminate. The keyboard and track pad will work OUTSIDE of 10.9.1, however. I have installed a clean internet recovery version of Mavericks over 4 times.
If I put my system, rMBP, into target disk mode and connect to any other computer via thunderbolt and boot it on the other Apple systems, the operating system running on the internal SSD of the rMBP will work just fine -- keyboard and mouse included (again, as a target disk mode thunderbolt connection to another host).
If I use a remote agent to connect to my rMBP such as LogMeIn or vnc, the keyboard and mouse will work just fine from the remote system which leaves me to beleive that this is not a software issue nor is it fully a hardware issue since the keyboard and mouse work outside of mavericks.
I believe we are still dealing with a firmware issue here. It took several tries to create a bootable device for the late 2013 rMBP since NONE of my other up-to-date and verified working external drives will boot but I finally created a bootable USB stick. When I run the system from the USB stick, the keyboard and trackpad will work but if I touch the keyboard and / or trackpad in 5 second intervals, I will receive the following error:
1/4/14 4:44:41.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:45:00.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:45:43.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:49:03.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:50:20.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:51:24.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:52:49.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:53:00.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:53:10.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:55:25.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:56:07.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:57:06.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:58:40.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:59:45.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
I had actually created a system log query to search for the above. The search string includes "the USB " and any entry after 1/1/2014. The above error should only present itself when waking an Apple system from sleep and instead it happens on every touch after, at least, a 5 second period of non-use.
When I remote into the system using LogMeIn, VNC or even use an application called ShareMouse which shares the keyboard and mouse of my Windows system with any other computer on the network presuming they have ShareMouse also installed, I can use the system as I would expect, without continuous error in the console log. When I check the system information, Bluetooth is completely disabled and the USB hub does not report address information. Since the keyboard, track pad, Bluetooth peripheral and USB ports all sit on the same USB stack / hub this leads me to think there is a firmware / driver failure occurring after Mavericks loads. The only two errors I see when I am using a remote keyboard and mouse via a remote service is as follows:
1/5/14 6:58:16.000 PM kernel[0]: The USB device HubDevice (Port 1 of Hub at 0xfa000000) may have caused a wake by issuing a remote wakeup (2)
1/5/14 6:58:16.000 PM kernel[0]: The USB device Apple Internal Keyboard / Track pad (Port 2 of Hub at 0xfa100000) may have caused a wake by issuing a remote wakeup (3)
Bottom line: Even for those of you who have installed the EFI 1.3 update and have verified that your freezing issues have ceased, for the most part, could you check your console log for the above error. My guess is, you will still see the error repeated there in 5 second intervals if you touch the keyboard, put your hands up for 5 seconds, touch the keyboard and / or track pad again. My concerns is that this is a product line issue since it has occurred on two brand new systems and the log errors appeared on another model on display in an Apple store. (The display model was logged into an Admin account so I took the liberty of checking the console log.)

I'm tired of this message. Bought a Mac 13" retina from bestbuy that was shipped to me on December 24th. The finder took a long time to load 'All My Files' with three to five second delay. My older macbook unibody (late 2009)was instantaneous. My wife's macbook aluminum (2011) also loaded the files instantaneously. Sorry I digressed but while I was trying to research that issue, I was caught up in the console and multiple of these,'The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)' kept showing up whenever I touched the trackpad in intervals of 6-7 seconds.
Called up apple, used screen sharing and after spending an hour was transferred to the second tier tech. The second tier rep troubleshooted and told me it WAS an issue and asked me to go to apple store to run diagnostics and that most likely I'll receive another notebook in exchange since it fell within 14 day period. I told him the internet was filled with this discussion and asked if it was prevalent. He said it was the first time he has come across this issue and most forums on the internet may not be addressing my specific issue. I wasn't convinced and simply returned it at best buy.
The unfortunate thing is I sold my macbook unibody and having owned 2 macbooks for last eight years I caved and ordered another 13". After a week and a half I received it today and guess what, I see the same message filling up my console.
I noted the following,
* Use guest account and you'll never see the message,'The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)'. All admin accounts created will throw that error.
Though off topic I'd like to state what happened with the Finder's 'All my files' issue:
1. Once I upgraded my older macbook unibody to mavericks, the 'All my files' took longer to load as the new macbook pro.
2. I was able to replicate the same slow load times with macbook aluminium(2011) when I upgraded it to mavericks.
Oh, I also showed the slowness to the representatives and all they tried doing was reindex spotlight which did no good.
So much for 1799$ notebook and the "free" OS. Very disappointed.

Mac Book fails to boot properly after EFI Firmware 27 update

hi
I have a strange boot issue having (tried) to install EFI 2.7 update.
When I restart the laptop, it 'chimes', displays a grey screen ... then chimes, displays a grey screen , ... for ever
I hit the bower (off) button for 5 secs or thereabouts, and restart ... same thing
I do this 4 times and finally it reboots.
But the EFI update still appears as needing to be installed (software update tells me it is not installed). Update history shows however that it IS installed.
I can go through this process any number of times ... I now have Software Update history showing quite a few installs opf the EFI 2.7 update.
If I just do a restart WITHOUT installing, I also go through the same fail to restart / fail to start / ... / eventually restart sequence.
So it seems now that the laptop will only start after 4 failed restarts and finally it starts ...
After starting it all appears to be perfectly fine.
Nothing strange in the console logs that I can see. The failed reboots don't seem to register in the console logs - I suspect that the failure to restart is pretty early on in the boot sequence, well before it tries to load any semblance of the OSX kernel. It is almost as if it is trying to boot from someplace other than the disk ... until eventually it gives up and tries the disk. (I have tried booting with and without network cable - no difference) I don't know enough about mac bootup sequences to know if there is some config/setting that is screwed up causing this odd behaviour. I sirt of feel it must be setup/software related, but could be wrong.
Odd.
Any ideas?
- chris

I have a MC721LL/A early 2011 15.4" MacBook Pro i7. After I installed this firmware update my Mail would not load saying the version I was trying to start was not compatible with the OSX version (not sure whether this was an OSX update issue which I think I did at the same time). But the biggest problem I have is that I cannot boot my machine. It boots to the Apple logo and then emits 3 beeps repeatedly. I am on vacation in Osaka, Japan and the Apple Store here told me after running some analytics that the logic board is not seeing the RAM. After reseating the RAM multiple times (both original and replacement DIMMS), it still won't boot. The Genius Bar guy said very nicely that it is out of warranty and needs a new logic board, costing over $500 and taking a week at the factory. He recommended spending the money on a new MacBook instead. Since my machine is 15 months old, I am not very happy about this. The machine was absolutely fine before the firmware upgrade. I will wait till I get back to the US and get a second opinion from my local Apple Store. I can't accept that a 15 month old MacBook Pro very lightly used can develop such a catastrophic failure.

Can not start up with internal HD after 10.9.4 update

After installing 10.9.4 update, can no longer startup from internal HD on late 2012 iMac, 2.9 ghz, 8 gb ram, 1 TB internal
Used Disk Utility to starup from external 10.9.3 drive and that works fine.
Loaded the manual 10.9.4 update onto external, and tried updating the 10.9.4 internal. No luck.
Attempting internal startup with 10.9.4 results in black screen, followed by several seconds of lit screen and spinning icon, then back to black screen.
After starting up on 10.9.3 external, 10.9.4 internal shows mounted, files appear fine, and can copy back and forth. Just can't start with that drive, and can't risk updating external 10.9.3 to 10.9.4 until I find out and fix the problem.
Thank you

This was reported by another user:
I had the same issue with my 2008 iMac and Apple support walked me through the fix yesterday...
1. Shut the computer down by holding the power button for 10 seconds
2. Restart the computer and press shift at the same time until you see the progress bar start moving
3. Once you reach the point where your screen goes dark and you see the cursor, type the first letter of the username for your computer, then hit Enter, then type your password, then hit Enter.
4. After a moment, you should see the spinning beach ball
5. Your screen should then move on to something along the lines of "Completing OSX Installation" (I can't remember the exact wording). Let it finish. After that it should go to your normal desktop and the issue should be fixed. (If your screen goes pitch black during this process, hit the space bar. I thought it wasn't working, but the screen was just sleeping).
Apparently it's an issue with an automatic update that never quite got past the login screen.
If the above doesn't help, then move on to these:
Try these in order testing your system after each to see if it's back to normal:
1. a. Resetting your Mac's PRAM and NVRAM
    b. Intel-based Macs: Resetting the System Management Controller (SMC)
2. Restart the computer in Safe Mode, then restart again, normally. If this doesn't help, then:
     Boot to the Recovery HD: Restart the computer and after the chime press and hold down the
     COMMAND and R keys until the Utilities menu screen appears. Alternatively, restart the
     computer and after the chime press and hold down the OPTION key until the boot manager
     screen appears. Select the Recovery HD and click on the downward pointing arrow button.
3. Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the Utilities menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu. Select Restart from the Apple menu.
     Reinstall the 10.9.4 update: OS X Mavericks 10.9.4 Update (Combo).
4. Reinstall Lion/Mountain Lion, Mavericks: Reboot from the Recovery HD. Select Reinstall Lion/Mountain Lion, Mavericks from the Utilities menu, and click on the Continue button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
     Reinstall the 10.9.4 update: OS X Mavericks 10.9.4 Update (Combo).

Upper part screen darkens after EFI 1.1 update

After the EFI 1.1 update I am experiencing some problems with the screen of my iMac core duo 20". In OSX, after my mac turns back on from sleep-mode, after a few seconds the upper part of my screen darkens. It looks like the backlite panel dims slightly on the upper part.
The strange thing is it doesn't happen when I boot in Windows XP with bootcamp. I thought I was experiencing hardware problems. But this can't be the case because it works fine in XP... Anyone

Nope, didn't work.
Strange thing is: I've worked on my machine the whole day without any problem. But... when my iMac goes to sleep and wakes up, the problem appears in a few seconds. The whole screen darkens a few tints, and the upper part of the screen darkens a bit more.
If anyone knows a way to undo the 1.1 update. I can't find the 1.0 version anywhere on the apple site...

My sound from Internal Speakers stop working and the icon get grey

Hello,
Yesterday I use my headphones to listen music from my mac. Today after I turn on my notebook I saw that my sound icon is grey and when I try to change the level of the sound nothing happens. When I put again my headphones the sound works.
I also saw that I have no option to choose Internal Speakers in Sound menu.
Can you help me pls.

I got the solution !
The problem was at the Headphone's port. I reconnected my headphones several times till the problem disappeared. There was some red light inside the port.

No Audio from Internal Speakers after a fresh install of Windows 7 Pro

T400S - after a fresh install of Windows 7, theres no audio from the Internal speakers. When I plug an external speakers there's audio. I also install the audio drivers from the Lenovo site. Thanks

Does your sound bar in the Sound Windows go up and down when you play music?
Regards,
Jin Li
May this year, be the year of 'DO'!
I am a volunteer, and not a paid staff of Lenovo or Microsoft

Connection to my AEBS (802.11n) stops after EFI 1.3 update

I just updated my 20" iMac to EFI 1.3 this evening. Upon reboot and login I found that connection to my Airport Extreme Base Station (802.11n) stops completely. As a matter of fact all the wireless basestations in my vicinity are no longer visible to me from my iMac. Before upgrading I've had few, if any, problems with my 20" iMac connecting to the Airport.
The only way I could see the basestation was by attaching an Ethernet cable from the iMac to the base station.
My AEBS is at the fireware revision of 7.3.1, my iMac is running 10.5.2, and the EFI has been updated to 1.3.
Anyone else had problems after upgrading to EFI 1.3?
Bob

Additional information as I have had two kernel panics trying to connect to my AEBSn. Connecting to the AEBSn via an Ethernet cable does work, just not wireless.
Wed Apr 9 08:08:27 2008
panic(cpu 1 caller 0x0039A8F1): "m_free: freeing an already freed mbuf"@/SourceCache/xnu/xnu-1228.4.31/bsd/kern/uipc_mbuf.c:3574
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x2e7d3d58 : 0x12b0f7 (0x4581f4 0x2e7d3d8c 0x133230 0x0)
0x2e7d3da8 : 0x39a8f1 (0x48fb60 0x0 0x0 0x20)
0x2e7d3e28 : 0x93f124 (0x302ef400 0x302ef400 0x0 0x302d88e0)
0x2e7d3e68 : 0x925800 (0x3ffa800 0x302ef400 0x403c800 0x41e94e)
0x2e7d3e88 : 0x5de186 (0x403c800 0x302ef400 0x0 0x41f18d)
0x2e7d3eb8 : 0x42004a (0x4041d80 0x4041d80 0x40336f0 0x2e7d3f3c)
0x2e7d3ee8 : 0x5de22b (0x40397c0 0x5de13a 0x4041d80 0x40336f0)
0x2e7d3f18 : 0x5de4c4 (0x4041d80 0x40336f0 0x2e7d3f3c 0x4033871)
0x2e7d3f58 : 0x5de5d2 (0x4041d80 0x23ac6252 0x2e7d3f78 0x1a236f)
0x2e7d3f78 : 0x13ea4a (0x4041d80 0x0 0x0 0x0)
0x2e7d3fc8 : 0x19eadc (0x0 0x0 0x1a20b5 0x4877b58)
Backtrace terminated-invalid frame pointer 0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPortBrcm43xx(312.46.51)@0x93c000->0xa60fff
dependency: com.apple.iokit.IO80211Family(211.1)@0x91d000
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x5bf000
dependency: com.apple.iokit.IONetworkingFamily(1.6.0)@0x5cf000
com.apple.iokit.IO80211Family(211.1)@0x91d000->0x93bfff
dependency: com.apple.iokit.IONetworkingFamily(1.6.0)@0x5cf000
com.apple.iokit.IONetworkingFamily(1.6.0)@0x5cf000->0x5e4fff
BSD process name corresponding to current thread: kernel_task
Mac OS version:
9C7010
Kernel version:
Darwin Kernel Version 9.2.2: Tue Mar 4 21:17:34 PST 2008; root:xnu-1228.4.31~1/RELEASE_I386
System model name: iMac7,1 (Mac-F4238CC8)
System Configuration
Model: iMac7,1, BootROM IM71.007A.B03, 2 processors, Intel Core 2 Duo, 2.4 GHz, 2 GB
Graphics: kHW_ATIr600M76Item, ATI,RadeonHD2600, spdisplayspciedevice, 256 MB
Memory Module: BANK 0/DIMM0, 1 GB, DDR2 SDRAM, 667 MHz
Memory Module: BANK 1/DIMM1, 1 GB, DDR2 SDRAM, 667 MHz
AirPort: spairportwireless_card_type_airportextreme (0x14E4, 0x88), Broadcom BCM43xx 1.0 (4.170.46.5)
Bluetooth: Version 2.1.0f14, 2 service, 1 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Network Service: Parallels Host-Guest, Ethernet, en2
Network Service: Parallels NAT, Ethernet, en3
Serial ATA Device: WDC WD3200AAJS-40RYA0, 298.09 GB
Parallel ATA Device: PIONEER DVD-RW DVR-K06A
USB Device: Keyboard Hub, Apple, Inc., high_speed, 500 mA
USB Device: Apple Optical USB Mouse, Primax Electronics, low_speed, 100 mA
USB Device: Apple Keyboard, Apple, Inc, low_speed, 100 mA
USB Device: Built-in iSight, Apple Inc., high_speed, 500 mA
USB Device: IR Receiver, Apple Computer, Inc., low_speed, 500 mA
USB Device: Bluetooth USB Host Controller, Apple, Inc., full_speed, 500 mA
Second Crash
Wed Apr 9 11:53:19 2008
panic(cpu 0 caller 0x0039A8F1): "m_free: freeing an already freed mbuf"@/SourceCache/xnu/xnu-1228.4.31/bsd/kern/uipc_mbuf.c:3574
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x345cfd58 : 0x12b0f7 (0x4581f4 0x345cfd8c 0x133230 0x0)
0x345cfda8 : 0x39a8f1 (0x48fb60 0x0 0x0 0x20)
0x345cfe28 : 0x93f124 (0x302dfb00 0x302dfb00 0x0 0x3028b0e0)
0x345cfe68 : 0x925800 (0x3fe3000 0x302dfb00 0x4095a00 0x41e94e)
0x345cfe88 : 0x5de186 (0x4095a00 0x302dfb00 0x0 0x41f18d)
0x345cfeb8 : 0x42004a (0x4093000 0x4093000 0x3ff9330 0x345cff3c)
0x345cfee8 : 0x5de22b (0x4088800 0x5de13a 0x4093000 0x3ff9330)
0x345cff18 : 0x5de4c4 (0x4093000 0x3ff9330 0x345cff3c 0x3ff9633)
0x345cff58 : 0x5de5d2 (0x4093000 0x23ac6252 0x345cff78 0x1a236f)
0x345cff78 : 0x13ea4a (0x4093000 0x0 0x0 0x0)
0x345cffc8 : 0x19eadc (0x0 0x0 0x1a20b5 0x49c12e8)
Backtrace terminated-invalid frame pointer 0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPortBrcm43xx(312.46.51)@0x93c000->0xa60fff
dependency: com.apple.iokit.IO80211Family(211.1)@0x91d000
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x5bf000
dependency: com.apple.iokit.IONetworkingFamily(1.6.0)@0x5cf000
com.apple.iokit.IO80211Family(211.1)@0x91d000->0x93bfff
dependency: com.apple.iokit.IONetworkingFamily(1.6.0)@0x5cf000
com.apple.iokit.IONetworkingFamily(1.6.0)@0x5cf000->0x5e4fff
BSD process name corresponding to current thread: kernel_task
Mac OS version:
9C7010
Kernel version:
Darwin Kernel Version 9.2.2: Tue Mar 4 21:17:34 PST 2008; root:xnu-1228.4.31~1/RELEASE_I386
System model name: iMac7,1 (Mac-F4238CC8)

Sound from internal speakers keeps coming and going.

My internal speakers aren't working consistently. One second I hear sound and then the next I hear nothing. I checked "System Preferences > Sound > Output" and can see that the selected device keeps randomly switching from Internal Speakers to Digital Out to Headphones. Why is this happening, and how do I fix it?
Thx

1. Reset PRAM. http://support.apple.com/kb/PH14222
    Do this twice
2. Reset SMC.     http://support.apple.com/kb/HT3964
    Choose the appropriate method.

Text disappear after flash and windows update

Hi,
I'm living a strange exprerience from the last windows software update (after i update even flash, to ensure that there was not a compatibility problem) , i can't display some fonts if I choose the option "anti-alias for reliability" , for example for the joeHand 2 , but the text came out again if I choose "bitmap" or "use device fonts" as display option.
This seams a problem with this particular font, but appears only after an automatic windows update, and is not valid for every font.
Someone resolve/had a similar problem?
Thank you
Riccardo

Hello everyone,
Please read this TechNote for information on how this issue can be fixed.
Regards,
Suhas Yogin

Pavilion no audio after windows and HP updates

A good Memorial Day to all.
I have an HP Pavilion G7. Four days ago Windows pushed out an update and audio worked afterward. Next day (three days ago), HP had an "important" update that kept popping up so my wife downloaded that update and installed. Since then, no audio from the PC or working on my external speaker.
I did a system restore rolling back one week - no change.
I reinstalled the HP audio driver - no change.
No audio now, totally DOA. BTW, the slider bars do show audio being processed but not heard.
I'm guessing the Windows update or the HP update (whatever they were) directly caused this.
Any help appreciated.
Noiseless in St Pete...

I would check the Windows updates and HP updates.
You can see when tMicrosoft Windows updates were installed by accessing Programs and Features and then selecting view installed features. Uninstall them one at a time.
You can check on the HP updates by accessing the log that is in the HP Support Assistant to see what was installed.
Best regards,
erico
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

No internal speakers after EFI- and thunderbolt updates

Similar Messages

Maybe you are looking for