Thunderbolt 10.8.3/SMC 1.1 broken?
Hi
I notice after updating my system to 10.8.3 including the SMC 1.1 (fan issue) update that my two Thunderbolt ports are not working anymore. I use them to connect via the adapters either Ethernet cable or Firewire HD. This could be a coincidence or I may have an HW issue with my device? Anyone successfully connecting external devices via Thunderbolt adapters?
Thanks Heiko
What happened after you did an smc reset?
http://support.apple.com/kb/HT3964
Similar Messages
-
Thunderbolt display problems using MBP with lid closed
I am experiencing a very reproducible problem since purchasing aThunderbolt display to use with a recent (1 month old) Macbook Pro 13"2.7GHz i7.
I use my MBP with lid closed with myThunderbolt display. If Ithen allow the MBP to sleep and power down, on restarting it the WiFi hasstopped working- the menu bar says I am connected by WiFi but Safari will notconnect to the internet and Time Machine cannot connect to the Airport/TimeCapsule to backup. Nothing I do will fix it (shutting down all programs, turingWiFi off then on) and so I have to shutdown/reboot BUT THEN the MBP freezesduring shutdown (waiting 15, 20, 30 minutes!) and I have to hold down the powerbutton (hard reboot). Once I reboot everything works fine UNTIL I take a breakand the computer goes to sleep again.
Doesn't seem to be a problem with the MBP lid open, but I needto test this a bit more to be sure...
On top of this the Bluetooth trackpad now keeps going on andoff; connected, not connected despite being near or the computer. Veryirritating at best, unusable at worst. This only started to be a major problem(every 10-15 minutes or so) when I started to use the Thunderbolt display.
These problems seems to be in some ways similar to anotherthread:
https://discussions.apple.com/message/16205098#16205098
("Major problemswith Thunderbolt display & MBAir")
I have applied the recent Thunderbolt Firmware update, and SMC& PRAM/NVRAM resets. Interestingly these seemed to work initially but thenafter a prolonged power-down period the problem has recurred. Back to square 1.
Any ideas out there?Just to be clear, have you installed everything that you find on this page?
http://support.apple.com/kb/HT4644
I just talked to Apple Care about Thunderbolt issues in general and even though I already had the Thunderbolt Software Update installed, he had me reinstall it. If you go to this page:
https://discussions.apple.com/message/16889000#16889000
you can read in detail about the issues I was having which have for the most part been remedied (for now at least!)
The Thunderbolt cable definitely transfers heat for some reason even when there isn't a high CPU utilization. The process 'kernel_task' seems to be where the API for thunderbolt is running. But for some reason, the behavior of CPU Utilization to Fan Speed is amplified when connected to the TBD.
Apple Care is researching it. -
MacBook Pro with Retina 13" Late 2013 thunderbolt port broken after 10.9.4 update
One of Thunderbolt Port (near USB port) was broken after 10.9.4 update.
I usually use mini Display Port to Display Port cable to connect my external screen, it works fine before 10.9.4 update. After 10.9.4 update, I tried to connect the external screen with the same cable, and the main screen of my MacBook Pro with Retina Display twinkling once so I'm sure the external screen was identified, but no video signal output.
I went to local Apple Premium Reseller (there is no Apple Store in Taiwan) and the they told me all of Thunderbolt Port was fine, they test with their own 10.9.2 copy and it seems ok. After that, I tried to re-install 10.9.4, downloading directly from Apple, the system re-install progress was complete but the Thunderbolt Port issue still there.
I connect to the broken Thunderbolt Port with Thunderbolt to Ethernet adapter, and it works fine, so I believe the only problem is that there is no video signal output from the Thunderbolt Port (near USB port one).
What should I do now?
Model: MacBook Pro with Retina 13" Late 2013I can confirm that problem, too: Im' working with a Dell U2713HM display, connected via display port. Since 10.9.4 Update i'm experiencing random black screens and/or display going to energy saving mode. Today i've had this issue twice: Display going black and after disconnecting the macbook von all cables screen of the macbook remaining black. Holding Power Button for about 10 s restarts the macbook. After 5 minutes the same problem appeared again.
-
Display broken? Thunderbolt adapter?
My display on my 2011 MacBook Pro is broken. For this reason, I'm curious as to whether or not I can buy a Thunderbolt to HDMI adapter for the time being, until I have the money to replace the laptop? When I plug in the adapter will it automatically switch to the external display? Or is there a hotkey that I could use to make it switch? Again, the display doesn't work AT ALL.
You won't accomplish anything by doing that; except for some iMac models, Macs don't support video-in.
(123537) -
Thunderbolt built-in cable is broken
Hello, i've broken the thunderbolt built-in cable from my Thunderbolt Display (27). Thunderbolt outlet is distorted...
The power one (macsafe) is right but the screen stay black.
Can i change this integred cable ?
Merci...If you aren't daisychaimg anything from the didplay's Thunderbolt port you can use it to connect to the computer with a Thunderbolt cable
<http://store.apple.com/us/product/MD861ZM/A/apple-thunderbolt-cable-20-m> -
Thunderbolt display broken after Mavericks 10.9.2 update
Macbook Pro, 15 inch, non-retina (mid 2012)
Thunderbolt display, 27 inches
I updated from 10.9.1 to 10.9.2 last week. When in 10.9.1, I had no issues with the Thunderbolt display (for approximately a month). However, since updating to 10.9.2 the Thunderbolt display now suffers from these problems
1. Display randomly flickers to black.
2. Display randomly has coloured lines across the screen.
3. Macbook pro slows to a crawl with the Thunderbolt adapter plugged in.
4. (more recently) Thunderbolt display, when plugged in, causes both laptop screen and thunderbolt screen to go black. Checking the Library/ColorSync/Profiles/Displays folder suggests that the Thunderbolt display is recognized as a generic display.
Troubleshooting:
- Condition does not correlate with jiggling of Thunderbolt cord, so I don't think it's a loose contact or faulty cable.
- Resetted PRAM and SMC but symptoms persist.
- Deleted com.apple.windowserver.plist and com.apple.windowserver.plist~orig to let the files rebuild but symptoms persist.
- Interestingly, I can plug in a different Thunderbolt monitor (also 27 inches) and it seems to work fine (albeit with only ~2 mins of testing).
- Other non-Thunderbolt displays seem to work fine as well.
Logged a complain to apple via http://www.apple.com/feedback/
Unfortunately, don't have a time machine backup to 10.9.1. Is there a way to reinstall 10.9.1 without a time machine backup?
Does anyone have suggestions of things to troubleshoot or possible fixes?
Thanks!Hello ahwahk
Start with the first article below to troubleshoot the issue further. Try out those same apps within a new or another user on your Mac. Also try booting it up in Safe Mode to see if it still does the issue with the icons. You may end up just needing to reinstall OS X Mavericks all together.
Mac OS X: How to troubleshoot a software issue
http://support.apple.com/kb/ht1199
OS X Mavericks: Reinstall OS X
http://support.apple.com/kb/ph13871
Regards,
-Norm G. -
Mac pro smc update no thunderbolt
Just updated my Late 2013 Mac Pro with the smc update. I have 2 27" apple thunderbolt displays and 2 Promise Thunderbolt 2 drive enclosures - each enclosure and each display is directly plugged in the the Mac Pro.
After the update, both displays are fine but both enclosures are dead (lights all off, no mounting of drives) All was fine before the update. Restarting was no help.
Not sure where to go from here. Any help would be appreciated.Well, after replugging all the thunderbolt plugs everything seems ok. Strange.
-
Thunderbolt - SMS/MMS Broken up
Howdy,
I am using the Thunderbolt & my friend is using an iPhone (AT&T). My messages, both SMS & MMS if longer than the SMS length of 160 are coming across broken up into multiple messages to her.
Is this Verizon?
AT&T?
4GLTE?
I suspect it is Verizon or the 4GLTE as she receives messages from others & this doesn't happen.
I could not find anything on my phone to force it to not break them up.
Thank you.Thank you Ann154 for the feedback!
I would like to add, SMS (Short Messaging Service) texts are limited to 160 characters with no special characters, graphics, or tones. Once the message character length goes over 160 characters and/or adds special characters or graphics, it is then converted to an EMS (Enhanced Messaging Service) text. Also, depending on the other carrier that the SMS or EMS is being sent from or to, the message may transport as 1 long message or it may be broken up into multiple SMS segments. I was able to confirm the following is true when sending from Verizon Wireless to AT&T: If a Verizon Wireless customer's device supports the sending of messages > 160 characters, the following happens:
Entire message (up to 1120 characters) arrives to recipient as plain text in multiple SMS segments.
Let me know if this answers your question! -
Thunderbolt port broken or faulty cable?
Hello!
I have a 27in 2.7 GHz Intel Core i5 mid-2011 iMac.
I bought a LaCie 1TB rugged thunderbolt drive a while back and when I went to plug it in, the thunderbolt didn't work (for both ports). I called Apple and they walked me through the steps and it still didn't work.
The thought just popped into my head that it could just be the cable. If both ports are not working, is it most likely the cable? I went into System Information and for both ports it just says "No devices connected". Unfortunately, I don't have another cable and at the same time, I'd like to avoid taking it in.
So I'm just wondering if it's unlikely that both ports wouldn't be working and that it's probably the cable.
Cheers!
KrisThe chances of both ports being bad is slim but not zero. It could also be something else in the Mac that is causing this.
It could also be the drive.
The only way to test this is to try a different cable and /or device. If you don't have another cable and can't get one then bringing it into Apple is your best course of action.
regards -
SMC broken after applying patches
Running a freshly installed 11/06 build of solaris 10 x86, I don't have any issues with smc. Immediately after patching, installing all recommended and security patches, smc so longer starts up.
bash-3.00# smc
Warning: Cannot convert string "-monotype-arial-regular-r-normal--*-140-*-*-p-*-iso8859-1" to type FontStruct
Warning: Unable to load any usable ISO8859-1 font
Warning:
Name: FONTLIST_DEFAULT_TAG_STRING
Class: XmRendition
Conversion failed. Cannot load font.
Java Accessibility Bridge for GNOME loaded.
java.lang.InternalError: java/langNullPointerException
at sun.awt.motif.MComponentPeer.pSetFont(Native Method)
at sun.awt.motif.MComponentPeer.setFont(MComponentPeer.java:247)
at sun.awt.motif.MWindowPeer.init(MWindowPeer.java:116)
at sun.awt.motif.MFramePeer.<init>(MFramePeer.java:58)
at sun.awt.motif.MToolkit.createFrame(MToolkit.java:231)
at java.awt.Frame.addNotify(Frame.java:491)
at java.awt.Window.addNotify(Window.java:462)
at java.awt.Window.show(Window.java:514)
at com.sun.management.viper.console.gui.VSplashScreen.show(VSplashScreen.java:166)
at com.sun.management.viperimpl.console.BaseConsoleOptionsManager.openConsole(Base ConsoleOptionsManager.java:746)
at com.sun.management.viperimpl.console.BaseConsoleOptionsManager.redirectToConsol e(BaseConsoleOptionsManager.java:648)
at com.sun.management.viperimpl.console.BaseConsoleOptionsManager.launchConsole(Ba seConsoleOptionsManager.java:173)
at com.sun.management.viperimpl.console.BaseConsoleOptionsManager.main(BaseConsole OptionsManager.java:861)
I'm guessing that something got horked up during patching, however, I'm not really sure which one(s) might have done so. Anyone have any ideas?
-MattHello Sourav,
of course I've asked basis people first. However, they didn't find anything yet.
Regards
Wolfgang -
Spotlight & Find Broken after SMC Firewire Update
I recently upgraded to the latest firmwire, iMac SMC Firewire Update 1.0, and now I have no find functionality on my Intel iMac. Soptlight shows, but doesn't search for anything. File find searches and searches but never finds anything.
I tried restarting and repairing permissions and that didn't do anything. I tried deleting com.apple.spotlight.plist and no luck either.
Any advice is greatly appreciated.I had the same issue, spotlight dead after I installed then de installed BootCamp.
I only had one account so I created another, logged into it and spotlight worked, logged out and in my account spotlight worked again.
Thanks
Mini - Intel Duo Mac OS X (10.4.6) 512mg/80gb/SyncMaster 940MW -
My thunderbolt port seems broken - have to re insert on startup every time
Just bought neew Mac Mini. Using Thunderbolt to VGA adaptor from Apple. But every time I start up, I am getting a 'no input' message on my monitor and only by pulling out the cable from the thunderbolt port and re inserting do I get a resoloution.
Anyone else had simular?Hi Skelbob, I have a similar problem whenever I restart or shut down my Mac Mini using the same adapter. The only difference in my case is that I do get display but it has a slight vertical wavy distortion which goes away if I unplug and re plug the thunderbolt connection. There is no problem using an HDMI connection, but the graphic resolution is not as good as the VGA. I have a very high spec Mini and I am not pleased about this, but have founf no solution to it. Let me know if you have any success.
-
Broken mini dvi connector on thunderbolt monitor, any way to repair?
I found instructions on how to remove the LED panel from the housing, but I could but find where to get a replacement 3 in 1 cable.
Have you tried pricing the repair at an apple athorized service center?
-
On Mountain Lion :
It happens to turn of my monitor in different situations. Sometimes i believe i have my graphic video broken ! In my town i don't have Apple doctors so i dont risk to go to a service non authorized from apple !
For example there was a day when it turns off when a simply pinch with thumb and 3 fingers for launchbad ...and the opperating sistem it should be restart from power button ! That was when i had Mountain lion 10.7.5 update
Other situation was with photoshop cs6, cs5, cs4 30 days trial versions ...i couldn't buy any versions so i decided to test a earlier versions that can match with my sistem requirements. In all of this three situations my display had turned off after opening a image or photo or 3d graphics in photoshop...anyway sadness.
Other situation : One day i was simply relaxing surfing facebook and ...than i've just simply open an advertising link ...and on that page i was waiting to load a video that used another player than flash player of youtube. Even two seconds didn't stayed open and trust me it turned off my display once again !
After Mountain Lion :
I told my story to to someone who holds an MacBook Pro i5 etc. and he told me to test the new mavericks maybe it's something broken in my operating system.... and believe me after 2 days of happiness with OS X MAVERICKS , last night my computer restarted because of a problem, and 2 hours ago again....why ? i don't know ! Maybe Video RAM or maybe Memory RAM or Maybe simple conflicts between Trial Photoshop and OS X or maybe my macbook it's 2 old...or i don't know ....for how much i used this mac it should run as an mustang ! MacBook Pro i7 Mid 2010 HDD 500 , 4 GB of DDR 3 , Intel built in Graphic 288 and an NVIDIA GE FORCE 512 , 15 inch display monitor , 283 real cicle counts ( my mac was used as an iphone while charging and using battery) ...i don't know what to do ! Please help !
The Operating System shoes me everytime this error !
Anonymous UUID: ED4DAC83-9B50-8715-CFC5-73ACA25B60B1
Wed Nov 13 11:03:50 2013
panic(cpu 1 caller 0xffffff7f909f8fac): "GPU Panic: [<None>] 5 3 7f 0 0 0 0 3 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff80adb56000 0x0a5480a2, D0, P3/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.4.12/src/Apple MuxControl/kext/GPUPanic.cpp:127
Backtrace (CPU 1), Frame : Return Address
0xffffff808ad83420 : 0xffffff800e622f69
0xffffff808ad834a0 : 0xffffff7f909f8fac
0xffffff808ad83570 : 0xffffff7f8f0ba53d
0xffffff808ad83630 : 0xffffff7f8f186d9e
0xffffff808ad83670 : 0xffffff7f8f186dfc
0xffffff808ad836e0 : 0xffffff7f8f40b5be
0xffffff808ad83810 : 0xffffff7f8f1aad41
0xffffff808ad83830 : 0xffffff7f8f0c108d
0xffffff808ad838e0 : 0xffffff7f8f0bebae
0xffffff808ad83ae0 : 0xffffff7f8f0c04d7
0xffffff808ad83bb0 : 0xffffff7f90055ffd
0xffffff808ad83d30 : 0xffffff7f90055a03
0xffffff808ad83d40 : 0xffffff7f9001acd0
0xffffff808ad83d50 : 0xffffff7f9001ad45
0xffffff808ad83d60 : 0xffffff7f8fffcb11
0xffffff808ad83da0 : 0xffffff7f8fffb335
0xffffff808ad83dd0 : 0xffffff7f8ffff29d
0xffffff808ad83e00 : 0xffffff7f8fa0c232
0xffffff808ad83e20 : 0xffffff7f8fa0c1c5
0xffffff808ad83e50 : 0xffffff7f9000bcb0
0xffffff808ad83e80 : 0xffffff7f8fffba63
0xffffff808ad83ed0 : 0xffffff7f8fff9441
0xffffff808ad83ef0 : 0xffffff800eaada80
0xffffff808ad83f30 : 0xffffff800eaac522
0xffffff808ad83f80 : 0xffffff800eaac5f7
0xffffff808ad83fb0 : 0xffffff800e6d6aa7
Kernel Extensions in backtrace:
com.apple.driver.AppleMuxControl(3.4.12)[A4934A66-0E30-36E9-984A-650481102449]@ 0xffffff7f909eb000->0xffffff7f909fdfff
dependency: com.apple.driver.AppleGraphicsControl(3.4.12)[661E3C87-5B97-3272-88FF-B9BA9B6E2 4ED]@0xffffff7f909e3000
dependency: com.apple.iokit.IOACPIFamily(1.4)[045D5D6F-AD1E-36DB-A249-A346E2B48E54]@0xfffff f7f8ef24000
dependency: com.apple.iokit.IOPCIFamily(2.8)[447B4896-16FF-3616-95A2-1C516B2A1498]@0xffffff 7f8ecba000
dependency: com.apple.iokit.IOGraphicsFamily(2.3.6)[38E388A5-92D6-3388-B799-F2498E582287]@0 xffffff7f8f016000
dependency: com.apple.driver.AppleBacklightExpert(1.0.4)[E04639C5-D734-3AB3-A682-FE66694C66 53]@0xffffff7f909e6000
com.apple.nvidia.classic.NVDAResmanTesla(8.1.8)[0A1B6F41-168D-307A-BABD-162F3B3 C2786]@0xffffff7f8f069000->0xffffff7f8f2d8fff
dependency: com.apple.iokit.IOPCIFamily(2.8)[447B4896-16FF-3616-95A2-1C516B2A1498]@0xffffff 7f8ecba000
dependency: com.apple.iokit.IONDRVSupport(2.3.6)[86BA68C6-18DD-30A1-ABF6-54597AD6C277]@0xff ffff7f8f059000
dependency: com.apple.iokit.IOGraphicsFamily(2.3.6)[38E388A5-92D6-3388-B799-F2498E582287]@0 xffffff7f8f016000
com.apple.nvidia.classic.NVDANV50HalTesla(8.1.8)[3666E0FC-87C7-3329-BD8C-2F1ADE D100A4]@0xffffff7f8f2e3000->0xffffff7f8f58ffff
dependency: com.apple.nvidia.classic.NVDAResmanTesla(8.1.8)[0A1B6F41-168D-307A-BABD-162F3B3 C2786]@0xffffff7f8f069000
dependency: com.apple.iokit.IOPCIFamily(2.8)[447B4896-16FF-3616-95A2-1C516B2A1498]@0xffffff 7f8ecba000
com.apple.GeForceTesla(8.1.8)[67BAF872-A238-3787-AB74-22297A51FE8F]@0xffffff7f8 fff3000->0xffffff7f900bdfff
dependency: com.apple.iokit.IOPCIFamily(2.8)[447B4896-16FF-3616-95A2-1C516B2A1498]@0xffffff 7f8ecba000
dependency: com.apple.iokit.IONDRVSupport(2.3.6)[86BA68C6-18DD-30A1-ABF6-54597AD6C277]@0xff ffff7f8f059000
dependency: com.apple.iokit.IOGraphicsFamily(2.3.6)[38E388A5-92D6-3388-B799-F2498E582287]@0 xffffff7f8f016000
dependency: com.apple.nvidia.classic.NVDAResmanTesla(8.1.8)[0A1B6F41-168D-307A-BABD-162F3B3 C2786]@0xffffff7f8f069000
com.apple.iokit.IOSurface(91.0)[BC96A900-DD9D-3F36-AFE6-EF88CB4B3607]@0xffffff7 f8fa08000->0xffffff7f8fa19fff
BSD process name corresponding to current thread: kernel_task
Mac OS version:
13A603
Kernel version:
Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64
Kernel UUID: 1D9369E3-D0A5-31B6-8D16-BFFBBB390393
Kernel slide: 0x000000000e400000
Kernel text base: 0xffffff800e600000
System model name: MacBookPro6,2 (Mac-F22586C8)
System uptime in nanoseconds: 1241550929282
last loaded kext at 267897920816: com.apple.filesystems.msdosfs 1.9 (addr 0xffffff7f90afb000, size 65536)
last unloaded kext at 432680682924: com.apple.filesystems.msdosfs 1.9 (addr 0xffffff7f90afb000, size 57344)
loaded kexts:
com.apple.driver.AudioAUUC 1.60
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.driver.AGPM 100.14.11
com.apple.filesystems.autofs 3.0
com.apple.iokit.IOBluetoothSerialManager 4.2.0f6
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.driver.AppleHDA 2.5.2fc2
com.apple.driver.AppleIntelHDGraphics 8.1.8
com.apple.driver.AppleMikeyDriver 2.5.2fc2
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.2.0f6
com.apple.GeForceTesla 8.1.8
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleHWAccess 1
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.AppleIntelHDGraphicsFB 8.1.8
com.apple.driver.AppleLPC 1.7.0
com.apple.driver.AppleSMCLMU 2.0.4d1
com.apple.driver.AppleUpstreamUserClient 3.5.13
com.apple.driver.AppleMuxControl 3.4.12
com.apple.driver.AppleMCCSControl 1.1.12
com.apple.driver.AppleSMCPDRC 1.0.0
com.apple.driver.SMCMotionSensor 3.0.4d1
com.apple.driver.AppleUSBTCButtons 240.2
com.apple.driver.AppleUSBTCKeyboard 240.2
com.apple.driver.AppleIRController 325.7
com.apple.driver.AppleUSBCardReader 3.3.5
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.iokit.SCSITaskUserClient 3.6.0
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.4.0
com.apple.driver.AppleUSBHub 650.4.4
com.apple.driver.AirPort.Brcm4331 700.20.22
com.apple.driver.AppleFWOHCI 4.9.9
com.apple.driver.AppleAHCIPort 2.9.5
com.apple.iokit.AppleBCM5701Ethernet 3.6.9b9
com.apple.driver.AppleUSBEHCI 650.4.1
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleACPIButtons 2.0
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.0
com.apple.driver.AppleACPIEC 2.0
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 216.0.0
com.apple.nke.applicationfirewall 153
com.apple.security.quarantine 3
com.apple.driver.AppleIntelCPUPowerManagement 216.0.0
com.apple.AppleGraphicsDeviceControl 3.4.12
com.apple.kext.triggers 1.0
com.apple.iokit.IOSerialFamily 10.0.7
com.apple.driver.DspFuncLib 2.5.2fc2
com.apple.vecLib.kext 1.0.0
com.apple.iokit.IOAudioFamily 1.9.4fc11
com.apple.kext.OSvKernDSPLib 1.14
com.apple.iokit.IOSurface 91
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.2.0f6
com.apple.iokit.IOBluetoothFamily 4.2.0f6
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.nvidia.classic.NVDANV50HalTesla 8.1.8
com.apple.iokit.IOFireWireIP 2.2.5
com.apple.nvidia.classic.NVDAResmanTesla 8.1.8
com.apple.driver.AppleGraphicsControl 3.4.12
com.apple.driver.AppleBacklightExpert 1.0.4
com.apple.iokit.IONDRVSupport 2.3.6
com.apple.driver.AppleSMBusController 1.0.11d1
com.apple.driver.IOPlatformPluginFamily 5.5.1d27
com.apple.driver.AppleHDAController 2.5.2fc2
com.apple.iokit.IOGraphicsFamily 2.3.6
com.apple.iokit.IOHDAFamily 2.5.2fc2
com.apple.driver.AppleSMBusPCI 1.0.12d1
com.apple.driver.AppleSMC 3.1.6d1
com.apple.driver.AppleUSBMultitouch 240.6
com.apple.iokit.IOUSBHIDDriver 650.4.4
com.apple.iokit.IOSCSIBlockCommandsDevice 3.6.0
com.apple.iokit.IOUSBMassStorageClass 3.6.0
com.apple.driver.AppleUSBMergeNub 650.4.0
com.apple.driver.AppleUSBComposite 650.4.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.6.0
com.apple.iokit.IOBDStorageFamily 1.7
com.apple.iokit.IODVDStorageFamily 1.7.1
com.apple.iokit.IOCDStorageFamily 1.7.1
com.apple.iokit.IOAHCISerialATAPI 2.6.0
com.apple.iokit.IOSCSIArchitectureModelFamily 3.6.0
com.apple.iokit.IOUSBUserClient 650.4.4
com.apple.iokit.IO80211Family 600.34
com.apple.iokit.IOFireWireFamily 4.5.5
com.apple.iokit.IOAHCIFamily 2.6.0
com.apple.iokit.IOEthernetAVBController 1.0.3b3
com.apple.driver.mDNSOffloadUserClient 1.0.1b4
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOUSBFamily 650.4.4
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 278.10
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.AppleKeyStore 2
com.apple.driver.DiskImages 371.1
com.apple.iokit.IOStorageFamily 1.9
com.apple.iokit.IOReportFamily 21
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 2.0
com.apple.iokit.IOPCIFamily 2.8
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.pthread 1
com.apple.kec.corecrypto 1.0
Model: MacBookPro6,2, BootROM MBP61.0057.B0F, 2 processors, Intel Core i7, 2.66 GHz, 4 GB, SMC 1.58f17
Graphics: Intel HD Graphics, Intel HD Graphics, Built-In, 288 MB
Graphics: NVIDIA GeForce GT 330M, NVIDIA GeForce GT 330M, PCIe, 512 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1067 MHz, 0x80AD, 0x484D54313235533654465238432D47372020
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1067 MHz, 0x80AD, 0x484D54313235533654465238432D47372020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.106.98.100.22)
Bluetooth: Version 4.2.0f6 12982, 3 services, 15 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: TOSHIBA MK5055GSXF, 500,11 GB
Serial ATA Device: HL-DT-ST DVDRW GS23N
USB Device: Hub
USB Device: BRCM2070 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Internal Memory Card Reader
USB Device: Apple Internal Keyboard / Trackpad
USB Device: Hub
USB Device: Built-in iSight
USB Device: IR Receiver
Thunderbolt Bus:Mid-2010 15" MacBook Pros - the bad NVIDIA GPU
If you're having frequent kernel panics with your 15" mid-2010, or intermittent screen problems, the problem is, more than likely, the faulty NVIDIA GPU found in a number of those machines.
Here's just a sample of a kernel panic log that points to the faulty NVIDIA card:
Kernel Extensions in backtrace (with dependencies):
com.apple.GeForce(6.4.0)@0x82ac4000->0x82b7afff
dependency: com.apple.NVDAResman(6.4.0)@0x834a0000
dependency: com.apple.iokit.IONDRVSupport(2.2.1)@0x82fd3000
dependency: com.apple.iokit.IOPCIFamily(2.6.5)@0x7a802000
dependency: com.apple.iokit.IOGraphicsFamily(2.2.1)@0x8301b000
com.apple.nvidia.nv50hal(6.4.0)@0x83c05000->0x84019fff
dependency: com.apple.NVDAResman(6.4.0)@0x834a0000
com.apple.NVDAResman(6.4.0)@0x834a0000->0x8378dfff
dependency: com.apple.iokit.IOPCIFamily(2.6.5)@0x7a802000
dependency: com.apple.iokit.IONDRVSupport(2.2.1)@0x82fd3000
dependency: com.apple.iokit.IOGraphicsFamily(2.2.1)@0x8301b000
Here's the "official" Apple take on the issue - but the very real kernel panics need not be preceded by 'Intermittent black screen or loss of video'... in fact, you might not experience any video problems at all. Although video problems can certainly be a portent of things to come…
So what can you do? Print out a copy of your kernel panic and a copy of the Knowledge Base article and take them, along with your machine, to your local Apple Store or an Apple Authorized Service Provider. The unfortunate thing is that many people have passed the “three years from date of purchase” now and Apple is not honoring the free logic board replacement for many users. Some dealers seem to be making some exceptions for those past the three year mark, but don’t count on it…
Good luck,
Clinton -
Thunderbolt port failure on Late 2011 Macbook Pro?
On a daily basis, I use a 1TB Seagate GoFlex external HDD that was originally a USB 3.0 interface until I bought the Thunderbolt sled (replacing the USB 3.0 interface) for things like Time Machine backups, photo management in Aperture and the like. Last night, I was on my Late 2011 15in Macbook Pro running a Time Machine backup and working in Aperture via Thunderbolt while charging the laptop when suddenly the drive was improperly ejected and the LED on the Seagate shut off as if no connection was made. I unplugged the Thunderbolt connections and tried again and the Seagate LED remained off and no drives showed up in Disk Utility. So I tried taking that Seagate and Thunderbolt cable and used it on another Mac, everything worked properly and as expected. So to further drive home the theory that maybe the Thunderbolt port on the laptop was bad, I tried using another Thunderbolt drive/cable on the Macbook Pro and sure enough, nothing happened. To me, this sounds like a bad port.
The reason for this post is that I've not yet seen anything on the interwebz regarding Thunderbolt port failures aside from a few estranged "display issues" via Thunderbolt. Has anyone else heard of this kind of thing happening? I find it a bit odd that with modern technology that tends to prevent overheating issues, this was able to happen. It almost seems like maybe a piece of solder broke off or something? Any thoughts?Have you rebooted the system? Have you tried a SMC and PRAM reset?
If not do all three of those things.
If you still have a problem hopefully you have Applecare as if you don't the fix will be expensive. You will need to have the logic board changed to fix a bad, broken, TB port.
Maybe you are looking for
-
Any good way to access a folder of hmtl files in weblogic server hard disk
I know that I can deploy a .war file containing some html and WEB-INF/web.xml file etc. to weblogic server, and then access the webpages in that .war file. But is there any more convenient way to be able to lift the restriction of having to put those
-
How to get network IP camera of images or media ?
Please tell me how to use jmf to get network IP camera of images or media? if you can provide source code, send me please my e-mail: [email protected] thanks!!⊙ω⊙
-
I can't get voiceover to play back on iMovie. What's going on?
I can't get voiceover to play back on iMovie. It seems to be recording just fine, but when I click to play back, no sound. I'm using the internal mic. Anybody have any idea what's going on?
-
Is the best way to call a perl module to use JNI or just use exec? I haven't seen any examples of calling Perl via JNI nor was I able to get any of the JPL (Java Perl Library) stuff to compile on my machine. Thanks!
-
Differents bt function and subroutine
hi gem's i want 2 know wether the form return's a value r not......