Thunderbolt Ethernet update fail to boot?

Curious if anyone else applied todays updates to Thunderbolt and are now frozen at the gray boot screen with the apple logo and swirly circle?
I'm on an early 2011 MBP running Lion with all the latest patches/software except for the Thunderbolt update. The laptop has an SSD with whole disk encryption enabled.
I installed the patch, came back a few minutes later, there was an error saying it wasn't able to apply it.. and the machine was frozen at that point, nothin else to do. I hard rebooted, and it's in thise frozen state since.
Safe boot does not boot.
Clearing PRAM does not help.
Booting safe with verbose (shift-command-v after apple boot tone) ends with:
AppleThunderboltNHI::enablePower - turn power off, status = 0x0, result_value = 0x0
Have let it sit for 45 minutes and no change in the logs.
There is a mention a few lines prior about IOKit framework not loading due to "image not found", but unclear if that's related at all. 3 lines prior Thunderbolt mention it also says "The System bootstrapper has crashed: Trace/BPT trap: 5

michaelab wrote:
The new adapter is only compatible with MacBook Air with Thunderbolt (mid-2011 onwards) and the new Retina MacBook Pro, so why have you all installed the update on your MBPs?
See Compatibility section: http://store.apple.com/us/product/MD463ZM/A
I've installed the update on my mid-2011 13" MBA and have had no problems at all.
Because it came up in Software Update, so we all assumed it applied to our version of OS X running on our hardware platform - nowhere did it say that it only applied to MBAs and new MBPs. If you're right about that, and I dare say you are, then I guess there's an erroneous record in an Apple database somewhere that says also apply it to systems that are not supported and that it shouldn't be applied to.

Similar Messages

Thunderbolt firmware update failed!

My config: Early 2011 MB Pro 13" 2.7 GHz i7 / OSX 10.7.1 Build 11B26
Last week I installed "Thunderbold Firmware Update version 1.0" on my brand new MB Pro.
It was connected to power, the update started, rebooted and showed the progress dialog while installing.So far so good. Almost at 100%, the progressbar stoped moving for at least an hour!!
At that point i discovered that a mobile HD was still connected to my MB (stupid off course during FW updates) and I disconnected it in the hope it would solve the pause. I waited again for at least half an hour and finally decided (was forced, against all advise) to reboot my MB.
The next boot, was a scary one :-). While everything seemed to work at first glace, I discoverd that my external displays did not work anymore. When using my minidisplay->VGA converter, no displays are detected. When using my minidisplay->HDMI displays are detected but giving "no signal". I've tried at three diverent screens that are all working on my (older) mac mini using the same adapters + cables.
Anybody experienced the same problem so far? I called with Apple Care but they "only" could advise me the SMC and PRAM/NVRAM resets. None of them helped. I also tried to install the thunderbolt fw-update by hand but a "Your computer's thunderbold port does not need this update" message is shown. The software updater shows that the system is fully up to date.
When looking at my system report the following is shown for my thunderbolt:
====
MacBook Pro:
Vendor Name:    Apple, Inc.
Device Name:    MacBook Pro
UID:    0x0001000A1B402220
Firmware Version:    22.1
Port:
Status:    No devices connected
Link Status:    7
Port Micro Firmware Version:    FFFF.FF.FF
====
The FFFF.FF.FF worries me a bit. Anyone knows what is shown after a successful update? Any known tricks maybe to force the FW-update again or skip back to the previous version?
I desperately need my external big screen again for software-dev.
Thanks in advance.
Kind regards, David (Netherlands)
Message was edited by: vaartmbpro

vaartmbpro wrote:
When i booted my mb (with new mobo) and scanned for updates, several popped up, under which "Thunderbold firmware update 1". Im scarred as **** to run the update again.... since i don't realy need it, i decided to skip it for the time beeing ;-)
I did it on my 2011 MBPro on Aug. 24.
It normally causes no problems to run a FW update if you check first, that there are NO external devices connected during FW update and the charger is connected and powered.
If it fails under this circumstances, it's mostly a hardware fault causing that. For that do it while your system is still under warranty.
Anyway, you can also try to roll back a failed firmware update.
See: http://support.apple.com/kb/HT2213
Sooner or later you must have it as a precondition for a upgrade or to get different hardware to work.
Note also that the next Thunderbolt FW update is rolled out now.
Lupunus

HT6093 Thunderbolt Display Update fail

I continue to get notices of a Thunderbolt Display update but it fails each time before loading. What should I do?

Same.
I have three thunderbolt displays connected to a Mac Pro. I got the error message, then read that no more than two displays could be connected during the update. I disconnected one of them and restarted. Then connected the other and disconnected the first and restarted again.
I'm not sure any of that worked and have no "active" notification that they were updated. I checked the firmware version following that update per the instructions and they match the version, but I'm still getting the random flicker.

Yosemite 10.10.1 update fails to boot

This update installed properly on my 2011 mini, but it bricked my 2010 MBP.
When I clicked restart, the MBP started to reboot, but need with the prohibitory sign (do not enter sign). I cannot boot into safe mode, and I am presently repairing the volume via recovery partition.
Has anyone else experienced this?
The only thing I can think of is that I used a third party piece of software to enable TRIM on the Samsung SSD I installed in the MBP 6 months ago, but this was not an issue through three or four OS upgrades and updates.
Thanks!

Here are the errors in the installer log. The ones from 7:30 to 7:32 are associated with the update process.
Nov 18 07:30:21 localhost opendirectoryd[123]: opendirectoryd (build 382.0) launched - installer mode
Nov 18 07:30:21 localhost opendirectoryd[123]: Logging level limit changed to 'notice'
Nov 18 07:30:22 localhost opendirectoryd[123]: Initialize trigger support
Nov 18 07:30:22 localhost opendirectoryd[123]: created endpoint for mach service 'com.apple.private.opendirectoryd.rpc'
Nov 18 07:30:22 localhost opendirectoryd[123]: set default handler for RPC 'reset_cache'
Nov 18 07:30:23 localhost opendirectoryd[123]: set default handler for RPC 'reset_statistics'
Nov 18 07:30:23 localhost opendirectoryd[123]: set default handler for RPC 'show'
Nov 18 07:30:23 localhost opendirectoryd[123]: starting endpoint for service 'com.apple.private.opendirectoryd.rpc'
Nov 18 07:30:23 localhost opendirectoryd[123]: no dynamic data found at '/System/Library/OpenDirectory/DynamicData/Configure.plist'
Nov 18 07:30:23 localhost opendirectoryd[123]: Registered node with name '/Configure' as hidden
Nov 18 07:30:23 localhost opendirectoryd[123]: no dynamic data found at '/System/Library/OpenDirectory/DynamicData/Local.plist'
Nov 18 07:30:23 localhost opendirectoryd[123]: Registered node with name '/Local' as hidden
Nov 18 07:30:23 localhost configd[113]: adding com.apple.SystemConfiguration.InterfaceNamer
Nov 18 07:30:23 localhost configd[113]: adding com.apple.SystemConfiguration.SCNetworkReachability
Nov 18 07:30:23 localhost configd[113]: loading com.apple.SystemConfiguration.ISPreference
Nov 18 07:30:31 localhost configd[113]: com.apple.SystemConfiguration.ISPreference load failed
Nov 18 07:30:31 localhost configd[113]: dlopen_preflight(/System/Library/SystemConfiguration/InternetSharingPreference. bundle/Contents/MacOS/InternetSharingPreference): Library not loaded: /System/Library/PrivateFrameworks/Netrb.framework/Versions/A/Netrb
Nov 18 07:30:31 localhost configd[113]: Referenced from: /System/Library/SystemConfiguration/InternetSharingPreference.bundle/Contents/M acOS/InternetSharingPreference
Nov 18 07:30:31 localhost configd[113]: Reason: image not found
Nov 18 07:30:31 localhost configd[113]: loading com.apple.SystemConfiguration.ApplicationFirewall
Nov 18 07:30:31 localhost configd[113]: adding com.apple.SystemConfiguration.KernelEventMonitor
Nov 18 07:30:31 localhost configd[113]: adding com.apple.SystemConfiguration.LinkConfiguration
Nov 18 07:30:31 localhost configd[113]: adding com.apple.SystemConfiguration.PreferencesMonitor
Nov 18 07:30:31 localhost configd[113]: loading com.apple.SystemConfiguration.EAPOLController
Nov 18 07:30:31 localhost configd[113]: loading com.apple.SystemConfiguration.IPConfiguration
Nov 18 07:30:31 localhost configd[113]: adding com.apple.SystemConfiguration.IPMonitor
Nov 18 07:30:31 localhost configd[113]: skipped com.apple.SystemConfiguration.Logger (disabled)
Nov 18 07:30:32 localhost configd[113]: updateConfiguration(): no preferences.
Nov 18 07:30:34 localhost configd[113]: LSExceptions [0x7fbed964eee0] loaded
Nov 18 07:30:36 localhost opendirectoryd[123]: 125.1 - Client: apsd, UID: 0, EUID: 0, GID: 0, EGID: 0
Nov 18 07:30:36 localhost opendirectoryd[123]: 125.1 - ODNodeCreateWithNameAndOptions request, SessionID: 00000000-0000-0000-0000-000000000000, Name: /Search, Options: 0x0
Nov 18 07:30:36 localhost opendirectoryd[123]: 125.1 - ODNodeCreateWithNameAndOptions failed with error 'Unknown node name' (2000)
Nov 18 07:30:37 localhost configd[113]: network changed.
Nov 18 07:30:40 localhost Unknown[373]: kern.boottime: { sec = 1416324602, usec = 0 } Tue Nov 18 07:30:02 2014
Nov 18 07:30:40 localhost Unknown[382]: Launching the Language Chooser for an OS Install
Nov 18 07:30:48 localhost configd[113]: LSExceptions [0x7fbed964eee0] unloaded
Nov 18 07:30:50 localhost configd[113]: InterfaceNamer: No current set
Nov 18 07:30:51 localhost configd[113]: New network configuration saved
Nov 18 07:30:51 localhost configd[113]: network changed.
Nov 18 07:30:55 localhost opendirectoryd[123]: 125 - Client: 'apsd', exited with 0 session(s), 0 node(s) and 0 active request(s)
Nov 18 07:31:05 localhost Language Chooser[383]: Setting system to install/recovery mode.
Nov 18 07:31:07 localhost Unknown[384]: Setting boot completed.
Nov 18 07:31:07 localhost Language Chooser[383]: Waiting for prepaired devices to appear
Nov 18 07:31:08 localhost Language Chooser[383]: All prepaired devices have connected. Continuing.
Nov 18 07:31:08 localhost Language Chooser[383]: Prepaired wait done.
Nov 18 07:31:08 localhost Language Chooser[383]: Could not read prev-lang:kbd to set keyboard.
Nov 18 07:31:13 localhost Language Chooser[383]: Ordering out cinematic windows.
Nov 18 07:31:13 localhost Language Chooser[383]: Not hiding Language Chooser in progress callback
Nov 18 07:31:48 localhost Language Chooser[383]: Launching the Springboard using language code "en"
Nov 18 07:31:49 localhost OSIESpringboard[399]: LSExceptions [0x7f9608d15910] loaded
Nov 18 07:31:49 localhost OSIESpringboard[399]: Can not connect to /var/run/systemkeychaincheck.socket: No such file or directory
Nov 18 07:31:49 localhost OSIESpringboard[399]: Failed to unlock login keychain.
Nov 18 07:31:53 localhost Language Chooser[383]: Hiding Language Chooser in window counter
Nov 18 07:32:00 localhost OSIESpringboard[399]: LSExceptions [0x7f9608d15910] unloaded
Nov 18 07:32:09 localhost Unknown[384]: 2014-11-18 07:32:09.540 Disk Utility[403:13989] Failed to connect (cancelRecreate) outlet from (DUWindowController) to (NSButton): missing setter or instance variable
Nov 18 07:32:09 localhost Unknown[384]: 2014-11-18 07:32:09.541 Disk Utility[403:13989] Failed to connect (repairSheetInfo) outlet from (DUWindowController) to (NSTextField): missing setter or instance variable
Nov 18 07:32:10 localhost Unknown[384]: 2014-11-18 07:32:10.608 Disk Utility[403:13989] 10.4-style NSNumberFormatter method called on a 10.0-style formatter, which doesn't work. Break on _NSNumberFormatter_Log_New_Methods_On_Old_Formatters to debug. This message will only be logged once.
Nov 18 07:32:20 localhost Unknown[384]: Keyboard Layouts: duplicate keyboard layout identifier -16899.
Nov 18 07:32:20 localhost Unknown[384]: Keyboard Layouts: keyboard layout identifier -16899 has been replaced with -28673.
Nov 18 07:32:20 localhost Unknown[384]: Keyboard Layouts: duplicate keyboard layout identifier -16900.
Nov 18 07:32:20 localhost Unknown[384]: Keyboard Layouts: keyboard layout identifier -16900 has been replaced with -28674.
Nov 18 07:50:43 localhost OSIESpringboard[399]: GetDYLDEntryPointWithImage(/System/Library/PrivateFrameworks/CacheDelete.framew ork/CacheDelete,CacheDeleteCopyPurgeableSpaceWithInfo) failed.
Nov 18 07:50:43 localhost Unknown[384]: 2014-11-18 07:50 OS X Utilities[399] (FSEvents.framework) FSEventStreamStart: ERROR: FSEvents_connect() => Unknown service name (1102)
Nov 18 07:50:51 localhost OSIESpringboard[399]: Connection to sharingd became invalid
Nov 18 07:50:51 localhost OSIESpringboard[399]: Folder Manager is being asked to create a folder (docs) while running as uid 0
Nov 18 07:50:51 localhost OSIESpringboard[399]: CoreServices logging is enabled,
Nov 18 07:50:51 localhost OSIESpringboard[399]: SFL Favorites initialized.
Nov 18 07:52:14 localhost Unknown[384]: 2014-11-18 07:52 OS X Utilities[399] (FSEvents.framework) FSEventStreamStart: ERROR: FSEvents_connect() => Unknown service name (1102)
Nov 18 07:52:14 localhost OSIESpringboard[399]: Folder Manager is being asked to create a folder (docs) while running as uid 0
Nov 18 07:52:14 localhost OSIESpringboard[399]: Connection to sharingd became invalid

Bios update failed causes booting problem

hello,
trying to update my bios to the latest version, the installation was not successful, as a result, i can not start my laptop since. it can not find an existing bios.
what should i do ? any suggestion ?
Thinks

Try doing a power cycle, if that doesn't help then contact support.
*Non Lenovo employee*
I have a Y2P (i5) ... Feel free to ping me if you want me to test some applications with your Y2P if you have the same model. I don't mind keep doing recovery on it if needed .... =)

MacBook Pro Retina Thunderbolt Ethernet issues

hi Folks
I have a macbook Pro Retina 15" here, using the thunderbolt ethernet adaptor.
if i boot the machine into windows 7 with the ethernet thunderbolt adaptor plugged in, it works fine.
however if i remove it while windows 7 is loaded , and then plug it back in, it wont work until i reboot , back into windows 7.
this is using the drivers as supplied in the boot camp installation package.
I have tried this with numerous mac machines and the thunderbolt adaptor, and they all perform the same.
ie if you remove the thunderbolt adaptor , and then plug it back in, you will have to reboot the mac back into windows 7, before it works properly again.
does anyone know why this is? and is there any way around having to reboot?
thanks

So I've noticed similar behaviour on my Macbook Air. It's a slightly different set of kit, since it's connected to a Belkin Thunderbolt Express Dock (http://www.belkin.com/uk/p/P-F4U055/). I'm on my second one of these because first one went back because it kept on dropping the internet connection (sounds familiar?) - and it *might* have been occurring when waking the system from sleep (I didn't make a mental note).
Anyway the replacement was working perfectly, until today - when it's started to drop it's internet connection again, and this time I'm pretty certain that it's related to waking from sleep. The main difference now is that I *just* upgraded to Mavericks, and I wonder if the sleep problem has reared its ugly head again in the latest version of MacOS?
All in all I have to say I'm pretty disappointed with the reliability of thunderbolt & the Belkin Dock thingie. Although it should be said that a single lead from my Macbook Air to the Express Dock is simultaneously carrying: video (1920x1200), Firewire800, 3xUSB3, gigabit ethernet and sound, so I'm not that surprised this technology is prone to the odd glitch, and the cables get really warm too!
It would be great to have some solid information from Apple/Belkin about this.
Cheers, Jon

Macbook Air thunderbolt ethernet not working after 10.8.3 update

Hi,
Thunderbolt Ethernet for my Macbook Air (11-inch, Mid 2012) stopped working after installing 10.8.3 update. I am unable to conect to my router via thunderbolt Ethernet connection port.
Anyone else having the same issue? Any recommendations?

Unplug your thunderbolt adapter. Restart the router.
Go to your Mac and go to System Preferences >> Network
Use the - button in the lower left corner to delete your Thunderbolt to Ethernet adapter.
Now plug your thunderbolt adapter back in and use the + button to add "Ethernet Thunderbolt" to your list of connections. Move it back up in the order of network preference you want.
Your network access should now be reset.

IMac G5 failed 10.5 update - won't boot now, spinning wheel

Please help, I bought my mom an iPad because she broke both ankles and is gonna be bed ridden for several weeks, and needed some way to get email, etc.
She has an iMac g5 2ghz non iSight. The iPad needs to be plugged into iTunes to work the first time, but her iMac had 10.4 on it. Well, iTunes requires 10.5 or higher. So i upgraded it and somewhere in the middle the update failed (I suspect a bad DVD). The computer wanted to restart, and since then, it will not boot, just a gray screen with apple logo, and the forever spinning wheel of frustration. I ran through the 10.5 installer again (this time using a different disk and it seemed to complete, and when it restarted at the end, same thing - spinning wheel, not happy.
So I boot off the OS x install DVD, run disk utilities, repair disk finds no errors, repair permissions says one minute remaining but never finishes, it ran all night long and I finally just gave up and turned it off this morning.
I have come to the conclusion that I will be formatting the HD tonight after work. But I need to get all her pictures, emails, and contact list off that drive first. I figure I'll use my old G4 (10.4 I think?) and put her iMac into target disk mode, and hopefully mount the drive to the G4 with the FireWire cable (I pray this works otherwise... Cry)
My main question, please help me out in locating her address book / contact list. She uses the Mac mail app for email. What files and/or folders do I need to copy so that once I format, I can (hopefully) just copy those folders back to the freshly installed OS 10.5, and theoretically make it seem like nothing happened.
Also, any suggestions anyone can offer me that don't involve formatting would be appreciated... But mostly, just need to figure what I need to backup.
Thanks so much, it's been a very difficult few days, and the added stress of this computer is just no good for the entire situation.

Copy her User (home) folder and Applications folder and you should have everything she needs.

After update mac os x lion 10.7 to 10.7.4 the os fail to boot ??

i just installed mac os x lion 10.7 on virtual machine ( vmware workestation 8) for some reasons,, after that I start the software update to update 10.7.4
after updating the os fail to boot ( changing tha Apple logo to another logo )..
what can i do to fix this problem ??

mohammad207 wrote:
i just installed mac os x lion 10.7 on virtual machine ( vmware workestation 8) for some reasons,, after that I start the software update to update 10.7.4
after updating the os fail to boot ( changing tha Apple logo to another logo )..
what can i do to fix this problem ??
10.7 client or server?

Satellite L300-03C - BIOS Update to V2.2 then Fail to boot on XP

L300-03C BIOS Update to V2.2 then Fail to boot on XP
Model:PSLB8C-03C01X
Please help
My OS is WinXP SP3 , BIOS was v1.4
using the latest BIOS V2.2 windows file to upgrade(from v1.4)
The progress is normally finished , however it fail to boot up.
I still can enter BIOS Setup , but can not run Windows XP to login screen.
So , what I can do?
Thank you

Hello
Did you load the default settings in BIOS after update?
So press F9 key in BIOS setup and save the settings.
Does it work?

Thunderbolt 1.2 update fails

Hi All my Mac book air wont accept the update and fails to restart and shuts down forcing me to restart manually any ideas Many thanks.

Hello X29JET,
Welcome to the Apple Support Communities. If you are having issues with the Thunderbolt Update, the next step would be to download the update directly from the website instead of going through the software update.
Thunderbolt Firmware Update v1.2
http://support.apple.com/kb/DL1653
Regards,
-Norm G.

Thunderbolt firmware update 1.2 continues to fail on MBP

For months I have been repeatedly asked via software update to run the Thunderbolt Firmware Update 1.2. The update gray screen shows up, but before the status bar can complete, the computer restarts. Other users have gotten relief with unplugging their usb and thunderbolt devices but I have no such devices attached to my computer. Anyone else?

Hello there terrie_808,
If the update still seems to not be taking for your Thunderbolt Display, I would like to recommend the troubleshooting in the following article to help you get that resolved, named:
Thunderbolt Firmware Update 1.2: Keeps reappearing and Thunderbolt ports and Target Display Mode may not work
After installing Thunderbolt Firmware Update 1.2:
Thunderbolt ports may not work.
Target Display Mode may no longer work.
The update may keep reappearing as available for download.
This occurs when a self-powered Thunderbolt device (other than a directly-connected Thunderbolt display) is connected to a Thunderbolt port while installing the update.
To resolve this issue:
Shutdown your computer.
Disconnect all Thunderbolt devices.
Wait 10 seconds.
If you are using a Mac mini with a Thunderbolt display, reconnect the Thunderbolt display directly to your computer via the Thunderbolt port. Do not connect other Thunderbolt devices at this time.
Restart your computer.
If the Thunderbolt Firmware Update 1.2 is offered, download and install it and restart your computer when asked. If the Thunderbolt Update is not offered, the update has installed correctly.
Reconnect all Thunderbolt devices.
Thank you for using Apple Support Communities.
Take care,
Sterling

Updater fails on MacBookPro2,2, Snow Leopard 10.6.2

I had Acrobat Professional 8.1.6 working on my MacBookPro2,2, Snow Leopard 10.6.2. When I tried updating to 8.1.7 the updater failed, saying the installation has been changed. So I removed the installation and reinstalled from DVD. It started as 8.1.3 and successive updaters brought it up to 8.1.5. Now the updater to 8.1.6 fails with the same symptom. What shall I do?

I answered a Possible way in another thread that you posted to it involves the use of Target disk, you want to copy an application from one computer to another. Here they are in case you missed it.
   1. Turn off both Machines.
   2. Connect same Ethernet Cable to both machines.
   3. Start up the one that has the defective install in Target Disk Mode (hold down Command Key and press T while starting up) You should see a Y shape icon bouncing around the screen.
   4. Start up your Machine that has the good copy.
   5. When booted up if connection is right, you should see you computer with bad install shown as an addition Hard Drive.
   6. Double click on drive wit defective install go to applications folder and remove Acrobat to Trash (Do not empty at this time)
   7. now Drag copy from good machine to machine you removed acrobat from application. (you want to copy from good copy machine to the other).
   8. Now shut down Main machine Down First. Then one designated as Target Disk.
   9. now Disconnect ethernet cable.
10. Finally Restart Computer you copied to (one that was setup as Target Disk) normally.
11. Try Acrobat. You may have to remove preferences.
This applies to anything you need to copy from one machine to another.
PS: Originally Target disk was setup for ethernet to ethernet. There was talk of changing the specs so that it would work on USB2.

Thunderbolt ethernet en3 interface not appearing on MacBook Pro Retina

2012 retina MBP, with a Thunderbolt ethernet adapter. Fully up to date, including this week's Thunderbolt firmware update. Plug the Thunderbolt ethernet adapter into any port -- the kernel sort of sees it, but nothing ever provides a network interface.
Infuriatingly, I got it to work once after weeks of failure, but have never been to reproduce that fleeting success.
I've seen and tried the comments in three seemingly-relevant threads:
https://discussions.apple.com/message/19550825
https://discussions.apple.com/message/21335473
https://discussions.apple.com/message/17909404
Like other reporters of similar problems, it's visible just fine in the system info:
Thunderbolt to Gigabit Ethernet Adapter:
Vendor Name:    Apple Inc.
Device Name:    Thunderbolt to Gigabit Ethernet Adapter
Vendor ID:    0x1
Device ID:    0x8003
Device Revision:    0x1
UID:    0x000100020014E9B0
Apple Serial Number:    DTN22060026DWKHAR
Route String:    3
Firmware Version:    5.5
Port:
Status:    Device connected
Link Status:    0x2
Port Micro Firmware Version:    0.0.8
It's getting power, at least, because the switch link light comes on when a cable's plugged in.
And the kernel recognises it in either Thunderbolt port, at least to some degree:
IOThunderboltSwitch(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 1 unplug = 0
[ PCI configuration begin ]
PCI configuration changed (bridge=58 device=5 cardbus=0)
[ PCI configuration end, bridges 14 devices 16 ]
But no driver ever gets loaded, and the en3 device never appears.
I've tried installing AppleBCM5701Ethernet.kext manually, which does nothing apparent. Unloading and reloading produces:
AppleBCM5701Ethernet:     ffff     ffff getAdapterInfo - Vendor is unknown
AppleBCM5701Ethernet:        0        0 start - getAdapterInfo failed, giving up
It's unclear if any of that is relevant or related to this adapter.
I've borrowed another physical adapter and tried that; it gives the same result.
https://discussions.apple.com/message/21335473 suggests creating a new Network Location. When I do that, the Thunderbolt Ethernet device (which does exist in my "Automatic" location) doesn't even appear in the new location. Clicking the [+] does not list it as an option to add.
https://discussions.apple.com/message/17909404 suggests resetting the SMC, which I've done in theory -- although I can find no documented way to know that the SMC reset actually occurred. Certainly there was no indication that I could see. So I'm not convinced that it did anything at all.
I'm out of ideas. This seems to me much more likely to be a software issue than hardware, at this point. Almost like it just can't figure out which driver it needs to load.
I humbly throw myself upon your mercy and wisdom.

I had this problem, too, and an Apple Support call and Genius Bar visit later, I had the answer: if you're using Network Locations that preexist your Thunderbolt display, it doesn't seem to auto-add the possibility of "Display Ethernet" to your available network ports. To solve this, either:
Create a new Location in your Network system preferences. It will finally detect the "Display Ethernet" and use it. It'll slowly change from disconnected to No IP to green-is-for-go.
or
Fix an existing Location by clicking the + to add a port and choosing Display Ethernet. It'll slowly change from disconnected to No IP to green-is-for-go.

Dhcpcd-based network fails during boot

Hi,
My fully updated Arch_X86-64/KDE is connected to the Internet router via (on-board wired) eth1, and is configured to get an auto IP address.
This has worked flawlessly for years till two days ago.
Ever since, eth1 service fails during boot, and requires several manual dhcpcd command to finally kick in. The same applies after waking from sleep mode. (see terminal output below)
As can be seen the system is configured to load the (correct) r8169 mode.
Please advise.
Thanks
Miki Badt
---------copy of respective commands---------------
# journalctl -b | grep eth
Sep 15 15:50:17 Miki_Arch systemd[1]: Expecting device sys-subsystem-net-devices-eth1.device...
Sep 15 15:50:17 Miki_Arch systemd[1]: Expecting device sys-subsystem-net-devices-eth0.device...
Sep 15 15:50:17 Miki_Arch kernel: r8169 0000:05:00.0 eth0: RTL8168d/8111d at 0xffffc900119d2000, 6c:f0:49:ed:b3:e9, XID 083000c0 IRQ 49
Sep 15 15:50:17 Miki_Arch kernel: r8169 0000:05:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
Sep 15 15:50:17 Miki_Arch kernel: r8169 0000:06:00.0 eth1: RTL8168d/8111d at 0xffffc900119e6000, 6c:f0:49:ed:b3:eb, XID 083000c0 IRQ 50
Sep 15 15:50:17 Miki_Arch kernel: r8169 0000:06:00.0 eth1: jumbo features [frames: 9200 bytes, tx checksumming: ko]
Sep 15 15:50:23 Miki_Arch dhcpcd[339]: eth1: waiting for carrier
Sep 15 15:50:23 Miki_Arch dhcpcd[336]: eth0: waiting for carrier
Sep 15 15:50:29 Miki_Arch kernel: r8169 0000:06:00.0 eth1: link down
Sep 15 15:50:29 Miki_Arch kernel: r8169 0000:06:00.0 eth1: link down
Sep 15 15:50:29 Miki_Arch kernel: IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 15 15:50:29 Miki_Arch kernel: r8169 0000:05:00.0 eth0: link down
Sep 15 15:50:29 Miki_Arch kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 15 15:50:53 Miki_Arch systemd[1]: [email protected]: control process exited, code=exited status=1
Sep 15 15:50:53 Miki_Arch systemd[1]: Failed to start dhcpcd on eth0.
Sep 15 15:50:53 Miki_Arch systemd[1]: Unit [email protected] entered failed state.
Sep 15 15:50:53 Miki_Arch systemd[1]: [email protected]: control process exited, code=exited status=1
Sep 15 15:50:53 Miki_Arch systemd[1]: Failed to start dhcpcd on eth1.
Sep 15 15:50:53 Miki_Arch systemd[1]: Unit [email protected] entered failed state.
#manual commands
[root@Miki_Arch miki]# dhcpcd eth1
dhcpcd[1039]: version 6.0.5 starting
dhcpcd[1039]: eth1: waiting for carrier
dhcpcd[1039]: timed out
dhcpcd[1039]: exited
[root@Miki_Arch miki]# ping www.ynet.co.il
ping: unknown host www.ynet.co.il
[root@Miki_Arch miki]# dhcpcd eth1
dhcpcd[1046]: version 6.0.5 starting
dhcpcd[1046]: eth1: soliciting an IPv6 router
dhcpcd[1046]: eth1: rebinding lease of 192.168.1.13
dhcpcd[1046]: eth1: leased 192.168.1.13 for 3600 seconds
dhcpcd[1046]: eth1: adding host route to 192.168.1.13 via 127.0.0.1
dhcpcd[1046]: eth1: adding route to 192.168.1.0/24
dhcpcd[1046]: eth1: adding default route via 192.168.1.1
lspci -v | grep Ethernet
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 03)
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 03)
lspci -k
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 03)
Subsystem: Gigabyte Technology Co., Ltd Motherboard
Kernel driver in use: r8169
Kernel modules: r8169
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 03)
Subsystem: Gigabyte Technology Co., Ltd Motherboard
Kernel driver in use: r8169
Kernel modules: r8169
cat /etc/modules-load.d/realtek.conf
r8169
Last edited by mibadt (2013-09-15 13:29:25)

Hi,
I've some errors with the new dhcpcd, you should downgrade.
https://wiki.archlinux.org/index.php/Do … g_Packages

Thunderbolt Ethernet update fail to boot?

Similar Messages

Maybe you are looking for