Works with the newest MacBook/Chromebook Pixel/and other laptop and desktop computers with a USB-C port. Connect to a Gigabit network through the USB Type-C port on your computer. Belkin Network adapter USB Type-C to Gigabit Ethernet.No big surprise cause it looks like they are using same Ethernet chipset like Belkin anyway with Product ID: 0x8153 and Vendor ID: 0x0bda (Realtek Semiconductor Corp.)2018. I tried also another USB-C Hub with Ethernet port by Epico but also with no success. Internet Recovery ⌘+⌥+R starts with spinning globe, but it takes for ever, drops down with errors, etc.
![]() It showed both en0 and en1 as connected. I opened up terminal and executed an ifconfig command. After the initial recovery image was downloaded and initialized, the GUI loaded. It required me to choose a wireless network. Upon booting into the Internet Recovery mode, it did not seem to recognize the adapter. I had the Ethernet plugged in and the power brick into the pass through port. Online terminal emulator macBelkin for faculty, the combo from apple (USB-c to Thunderbolt port then Thunderbolt port to RJ45) for tech staff, seems to work ok even with the 2018 Model.I did some testing with using wireless, and if i remember correctly worked fine using a SPrint MyFy, didn't try using our campus wifi mainly because of needing to authenticate (didnt want that to be a solution for us). I got a 2018 Macbook Pro with Touchbar and it is also showing same issue.I am doing what is doing. So, while it seemed to need the wireless for the initial IR GUI image download, once the recovery module loaded, it recognized the adapter and initialized the kext for the rest of the install.Hi All we are seeing the same issue here for at least a year now, so the 2017 Macbook Pros with Touchpad. I exited the terminal, turned the wireless adapter off, wiped the hard drive, and started the OS reinstall.I pulled up my firewall logs and limited to the wired (en0) IP address and so far it has downloaded 5.47 GB worth of data. The en0 had an IP address from the wired subnet where as the en1 had an IP address from the subnet of the wireless network that I chose. Internet Recovery boots fast and installation is stable.On the other hand it's pretty weird that Apple sells something officially on Apple Store (I'm talking about Belkin USB-C to Gigabit Ethernet Adapter) which doesn't really work for Apple's Key Services what Internet Recovery certainly is!Thunderbolt to Gigabit Ethernet Adapter by Apple have Vendor Name: Apple Inc., Vendor ID: 0x1 and Product ID: 0x8003 instead of Realtek Semiconductor used in Belkin's Adapter which probably makes difference. Here's a paste from the original post to give proper credit:"Thunderbolt 3 (USB-C) to Thunderbolt 2 + Thunderbolt to Gigabit Ethernet Adapters(Both made by Apple)With this combination of connecting Ethernet over two adapters to one of your USB-C port everything works like charm. Lets see if a Apple brnaded adaptor shows up in a few months.SOLUTION: I found this on discussions.apple.com. I guess thats Apples answer, an over prices docking station. I wanted to share my experience in case it helps someone.I tried Wifi and three different ethernet adaptors: Belkin F2CU040, Cisco LINKSYS, and Apple USB Ethernet on a MacBook Pro 15-inch, 2018. Chains is not really a fancy solution.What a mess. This adapter to adapter to adapter. I saw that the other adaptors wouldn't get an IP and the Terminal DHCP commands worked for all adaptors. I also tested on production and non-production network.Once in Recovery Mode with the Belkin adaptor, I followed tips on ipconfig. Company Wifi and other adaptors failed to even load Recovery, leaving me with error code 2003F and 3001F. Oddly enough, the only way I could get to Recovery was to use the Belkin adaptor. Dmg file with the 10.14.6 installer. I created a never booted macOS. On a working Mac, I downloaded the latest macOS Mojave installer, 10.14.6. I left this overnight in one instance as well.Here is what I did to get this MacBook going: I didn't copy the log, but after a long delay, it showed errors and the Mac tried to download the packages again. The logs show that the Mac reached Apple Servers and the packages (6GB+) were downloading. Autotask outlook add inI emailed Apple Enterprise Support about this, and they asked if I used Wifi or if I had "taken" this up with Belkin. I clicked on it and rebooted.After all those steps, it booted and I have a working Mac again. That Mac looped for a bit, but finally it asked to restart because the system needed an update. Hoping to get back into Recovery, I plugged in the Belkin adaptor. At first, the MacBook looked like it was booting into Recovery Mode again, so I thought it didn't take. Dmg file created in step 3. Eventually the traffic slows down to a point where nothing is transmitted for several minutes. Black lines everywhere in the Wireshark console. Retries, retransmits, dupes, etc. I've been able to repeat this over and over again.The problem is as bad as everyone says: when you use third-party gigabit-class USB-C Ethernet adapters (Belkin, Dell, etc.) they all exhibit an absurdly high amount of dropped packets. I used Internet Sharing (Wi-Fi > Ethernet) and Wireshark on another Mac to monitor Internet Recovery's loading performance with several different adapter combos. Belkin Network Adapter Driver Support AndSpace is a valuable commodity in firmware, so all code has to be hyper-optimized and compact. USB has no controller and has always offloaded the processing to the CPU, which requires more robust drivers. Something happens under high speed loads with USB-C that causes the code to freak out, crash a buffer, and stop transmitting.Thunderbolt has a dedicated controller and is unaffected by these issues. When you use Thunderbolt, it's fast as lightning (no pun intended).I'm not an expert at Ethernet protocols or low-level drivers, but If I had to take a guess, Apple's firmware code probably includes only basic USB driver support and was never fully tested with the gigabit-class USB devices, only with Apple's 100Mbit USB adapter. It's too bad that Apple never tests this stuff in real world dirty environments.
0 Comments
Leave a Reply. |
AuthorShannon ArchivesCategories |