Lightning Strike Fried My Modem Router and Ethernet

[archangeliques]

Hi, last week a lightning strike hit the telco box and fried my modem router and ethernet controller in the motherboard. Here I wrote the whole story to reddit. I'm concerned about having an issue with iServices that I set up with ethernet ROM, en0 in SMBIOS section. I have WiFi right now and planning to get a new modem router. I have Dell Ultrasharp which has an ethernet port in its USB hub that is connected to my PC via TypeC cable. macOS sees it as an USB ethernet with en3 BSD. en1 is my BCM WiFi card. I checked from System Info and it doesn't see any ethernet controller, no name, no mac address. Hackintool doesn't show the ethernet kext as loaded as well.

 

Do you think will there be any issues when I plug the new modem router to the monitor and let macOS use the internet via USB ethernet? And any issues with iServices?

 

I'm also holding the new macOS update now, Do you think this will cause any issues during the update? With just WiFi or with new modem router connected to monitor's ethernet?

 

Thanks!

 

[Slice]

I think macOS will not work on fired electronics. First repair it.

[archangeliques]

9 hours ago, Hervé said:

Re: router, no issue at all; such equipment bears no relation to macOS and its behaviour.

I didn't mean if plugging new modem router via ethernet cable to the monitor causes any issues in the OS level but since mainboard's ethernet controller is fried, plugging new modem router and providing internet via en3 cause any issues to iServices?

 

9 hours ago, Hervé said:

Re: Ethernet, if its disappearance due to lightning causes an issue with the services you mentioned, just install the NullEthernet driver/kext that fakes an Ethernet port. But if you have some other Ethernet capabilities at hand, all should be well.

Well, yes, lightning strike hit telcom box, went trough dsl line, fried modem router and kept going through ethernet cable to the pc and fried the controller.

 

Hmm, I've added screenshot to the reddit post, it somehow sees ethernet but in the hardware tab, there is no mac address. Do you think I should install NullEthernet kext anyway? I'm using the PC like that with WiFi for a week, had no issues so far though.

 

As for Ethernet capabilities, like I asked before, Do you think my monitor's usb ethernet does the job?

 

Thanks!

[archangeliques]

21 hours ago, Slice said:

I think macOS will not work on fired electronics. First repair it.

It's too old to be repaired, H97 chipset, probably belongs to 2014/5. I use it with WiFi for a week with no issues so far though but I'm avoiding the macOS update for now. Maybe it works OK for now but may fail during the update?

 

Have you guys checked my reddit post?

 

Edit: Oh it was a joke, cute. Can we get to the part where we help each other? I'm here to get help.

Edited July 28, 2022 by archangeliques

[Guest ricoc90]

Updating macOS with Wifi only / with your monitors ethernet should be fine.

As far as iServices go, I can't be sure. I never experienced issues with iServices myself, so I never really looked into it. I recall that back in the day ethernet had to be en0 (which you can do by just changing the network order in settings), but mine never was.

[archangeliques]

18 hours ago, ricoc90 said:

As far as iServices go, I can't be sure. I never experienced issues with iServices myself, so I never really looked into it. I recall that back in the day ethernet had to be en0 (which you can do by just changing the network order in settings), but mine never was.

 

Same here, Fixing iMessage > Fixing En0 on OpenCore Post Install states lack of En0 may cause issues with App Store and needs to be fixed. I no longer have En0 under Network Interfaces on Hackintool for instance. Not sure if it will cause any issues an hour later or next week or after the update and if I go through the guide to fix it right now... Doing so will introduce other possible issues with all iServices, I might have to regenerate serials and IDs which will create new Hardware UUID, therefore I will have to sign out from iCloud, delete this machine from iCloud, do the cleaning and then sign back in with the new serials and hope nothing goes wrong.

 

I remember the same for en0 too but guide says it can be all.

"Note: en0 can be either Wifi, ethernet or even Thunderbolt."

 

I need someone who have experience on this case but this new users rule of the forum is working against me at the moment. I might be new (technically not though registered in 2020 but didn't participate because of this rule at that time either) in here but I'm not new to hackintosh, I built my first laptop hackintosh with the help of RehabMan back in time for instance and I'm active on another famous forum and Reddit.

 

Is there a way to make more people see this post instead of just the ones interested in checking "New comers" section? More people, more help.

 

Thanks.

[archangeliques]

On 7/29/2022 at 12:13 PM, Hervé said:

No, those rules have been put in place for a reason. Being limited to New Users Lounge does not limit the visibility of your thread in any way.

I've never questioned the necessity of the rules but I stated this particular one working against people like me, already in Hackintoshing for years and active on other forums and Reddit. It actually does, only people who want to look at New Users Lounge are able to be aware of these posts. To justify it, we don't see any post replies except yours.

 

On 7/29/2022 at 12:13 PM, Hervé said:

You were already told to use the NullEthernet kext, can't see why you keep fussing around on the matter; just get on with things and stop asking questions about potential problems you fear but have not materialised .

 

Let's see what RehabMan said about NullEthernet.kext:

 

Quote

Null Ethernet Network Driver by RehabMan

The purpose of this driver is to enable Mac App Store access even if you don’t have a built-in Ethernet port with supporting drivers. The idea is to use a USB WiFi and this “fake ethernet” driver to make the system still allow Mac App Store access.

Note: Having a real Ethernet port with working driver or a real PCIe WiFi device with working AirPort driver is a better idea. This is to be used as only a last resort where getting working built-in WiFi or Ethernet is not possible.

 

Yes, you told me to use NullEthernet.kext but it is not only wrong guidance (by the dev's statement of this kext, quoted above) but also you try to scold me for not listening to you? I already told that I have a working "real PCIe WiFi device", BCM in the first post. Mac App Store is working as well. So, NullEthernet.kext solution doesn't apply to my case.

 

What I don't get is why I'm being treated like this? "Keep fussing around", "stop asking questions", "I simply deleted it" and ignoring my DM. If you don't like helping people, then don't. No one deserves to be treated like this, especially if they are seeking help. I remind you the first sentence of the Forum Rules, again.

 

I appreciate if anyone else (who are really here to help) wants to share their experiences about ethernet failure and how they fixed it or kept using their hackintosh with it.

 

Thanks!