New Driver for Realtek RTL8111

[Mieze]

Here is the next development version 2.5.0d4. As there are only changes in the kext's unload related code, you won't notice any differences in normal operation because network drivers normally aren't unloaded by the OS. Good luck testing!

 

Mieze 😽

RealtekRTL8111-V2.5.0d4.zip

[iaihc]

Download test thanks!

[kaoskinkae]

12 hours ago, Mieze said:

Aquí está la próxima versión de desarrollo 2.5.0d4. Como solo hay cambios en el código relacionado con la descarga de kext, no notará ninguna diferencia en el funcionamiento normal porque el sistema operativo normalmente no descarga los controladores de red. ¡Buena suerte con las pruebas!

 

Mieze  😽

RealtekRTL8111-V2.5.0d4.zip 149,85 kB · 2 descargas

 

Let's try and wait for the official version

[kaoskinkae]

I have tested both my devices on the New one: perfect but on the Old one: no network connection, see the device specifications below.

Also in my Spanish groups I have been told about signal loss or delay in the internet connection.

[Mieze]

@kaoskinkae Well, the driver now is compatible with AppleVTD but this doesn't mean that the mainboard also is. On some boards enabling AppleVTD causes network drivers so cycle up and down, work very slow or the system might even become unstable and produce KPs or simply reboot unexpected. Sometimes patching the DMAR helps to solve this problem, Basically, it boils down to the fact that this is not a driver issue and there is nothing which can be done to solve this problem inside the driver.

If your mainboard isn't compatible with AppleVTD, the only way to get a stable system is to disable it in UEFI setup or OC. My Gigabyte Z490 Gaming X is one of these boards. While AppleVTD is enabled, all network drivers including the ones provided by Apple keep cycling up and down, or work very slow. Under load, the system might reboot suddenly.

In case you are affected, trying to patch your DMAR might help, but there is no guarantee that this solves the problem.

[kaoskinkae]

19 minutes ago, Mieze said:

@kaoskinkae Bueno, el controlador ahora es compatible con AppleVTD, pero esto no significa que la placa base también lo sea. En algunas placas, habilitar AppleVTD hace que los controladores de red se activen y desactiven, funcionen muy lento o el sistema incluso puede volverse inestable y producir KP o simplemente reiniciarse inesperadamente. A veces, aplicar un parche al DMAR ayuda a resolver este problema. Básicamente, se reduce al hecho de que no se trata de un problema del controlador y no hay nada que se pueda hacer para resolver este problema dentro del controlador.

Si tu placa base no es compatible con AppleVTD, la única forma de conseguir un sistema estable es desactivarlo en la configuración UEFI o en OC. Mi Gigabyte Z490 Gaming X es una de estas placas. Mientras AppleVTD está activado, todos los controladores de red, incluidos los proporcionados por Apple, siguen funcionando de forma intermitente o funcionan muy lento. Bajo carga, el sistema puede reiniciarse de repente.

En caso de que esté afectado, intentar parchear su DMAR podría ayudar, pero no hay garantía de que esto resuelva el problema.

Thanks for the clarification on my YouTube channel. I prepared a video in Spanish related to this topic. With your contribution of the new kext, it gave me the option to comment on the topic. Thanks for the answer.

[daemon17]

Hi.
After updating the driver from v.2.4.2 to v.2.5.0d4, the cable connection was no longer detected.
Cleaning the DMAR table did not help.
Setting the OpenCore option DisableIoMapper = true, DisableIoMapperMapping = true or one of the two also does not work.
The problem can only be solved by manually setting the speed to 100 baseTX
I rolled back to version v.2.4.2 for now. It works without problems.

Edited February 14, 2025 by daemon17

[Mieze]

@daemon17 As already mentioned before, the driver is now compatible with AppleVTD but this doesn't mean that the mainboard also is! If your mainboard is not compatible with AppleVTD and patching the DMAR doesn't help, there is no way to make it work with AppleVTD and you'll have to keep it disabled.

[daemon17]

47 minutes ago, Mieze said:

 

@Mieze  I can't disable VT-d in BIOS. This option is enabled and blocked. That's why I enabled Quirk in OC DisableIoMapper. 
In macOS AppleVTD is disabled.  But driver v.2.5.0 still doesn't work for link detection.


 

[Mieze]

@daemon17 You still don't get it: AppleVTD needs two things to work properly, drivers which are AppleVTD compatible and mainboards which are compatible too. If any of the involved components is incompatible with AppleVTD, you simply can't use it and have to disable VT-d in UEFI or use DisableIOMapper in OC.

I did my share and made the driver compatible with AppleVTD but if your mainboard isn't (My Gigabyte Z490 Gaming X is also affected), and patching the DMAR doesn't help, there is nothing I can do and you have to use DisableIOMapper. It's not my fault! 🤷‍♀️

 

[daemon17]

10 hours ago, Mieze said:

and have to disable VT-d in UEFI or use DisableIOMapper in OC.

I disabled AppleVTD, it is not in ioreg (see screenshot). But it still does not work. The new driver does not work with AppleVTD enabled and also does not work with AppleVT-d disabled. What is the point of this driver? It supports AppleVTD but does not work with AppleVTD enabled or disabled.
This driver needs a working AppleVTD. That is, it needs real Apple hardware. Did I understand you correctly?

Edited February 15, 2025 by daemon17

[kaoskinkae]

20 hours ago, daemon17 said:

Hi.
After updating the driver from v.2.4.2 to v.2.5.0d4, the cable connection was no longer detected.
Cleaning the DMAR table did not help.
Setting the OpenCore option DisableIoMapper = true, DisableIoMapperMapping = true or one of the two also does not work.
The problem can only be solved by manually setting the speed to 100 baseTX
I rolled back to version v.2.4.2 for now. It works without problems.

The problem can only be solved by manually setting the speed to 100 baseTX
Indeed, that's how it works and you've made me remember my previous computer, a Sandy Brique that already died, poor thing, with an external card that I put in it, it was necessary to use it with the kext now in progress 2.4.2

[Mieze]

@daemon17 If you are too lazy to read or not smart enough to make it work, don't blame me. Version 2.5.0 works almost in the same way as previous versions, but it adds support for AppleVTD, provided the mainboard also is compatible with AppleVTD but there are many boards which aren't. I explained this more than once before and I also explained that there are limitations which are beyond my reach. Is that so hard to understand?

[daemon17]

@Mieze Many things are not clear to us not because our concepts are weak, but because these things are not included in the circle of our concepts. You also do not know everything, do not delude yourself.

[iaihc]

The latest 2.5.0 driver has caused many users to experience network connectivity issues after upgrading

[Mieze]

@iaihc Where are the bug reports? And I mean real bug reports that may help to track down any real issue, not these kind of users just complaining that it doesn't work without giving any information. I'm a developer, not a clairvoyant and I'm not responsible for problems which exist between keyboard and chair.

 

Besides that, I explicitly mentioned that there are limitations with regard to AppleVTD and that I can't resolve those issues related to the mainboard being incompatible with AppleVTD. What else should I do? To be as explicit as possible: Version 2.5.0 is a benefit for those users which are lucky to have a board which is compatible wth AppleVTD. Besides that there aren't any changes. If you don't know what you are doing or if you already know that AppleVTD doesn't work with your board, just leave it disabled and version 2.5.0 will work fine for you in the same way as previous versions used to work.

 

I consider enabling AppleVTD on a mainboard which is incompatible as improper use and I'm not responsible for it. 🤷‍♀️

Edited February 20, 2025 by Mieze

[LockDown]

20 minutes ago, Mieze said:

 just leave it disabled and version 2.5.0 will work fine for you in the same way as previous versions used to work.

Simple isnt it 🤔 Guess not 👎

Have a nice day ✌️

[Mieze]

@LockDown The only thing I changed is mapping of DMA buffers as this is a requirement for AppleVTD compatibility. Anything else works in the same way as it used to work in previous version because I haven't touched the code.

 

By the way, I'm upset about users who expect full service like they are used to with original Apple devices. Anybody who expects full service is advised to go to the next Apple Store and should be willing to pay for it. With my limited resources I'm unable to provide that kind of service and anybody who is asking for support should at least be willing to provide a proper bug report and run some tests on his own. It is frustrating to spend a lot of time with writing the code, testing it and providing support to ungrateful users who are not willing to contribute at least a proper bug report. 😾

[mnfesq]

Hi.  I see that you have received less than grateful feedback from some of the users of your kext and for that, I feel badly for you.  I also had problems when I updated to version 2.5.0 on my Chromebox 3-N7068U, which has an 8th Gen. Intel CPU/chipset.  Specifically, when I look at the MAC address for the device, it reports all 0's, which precludes network connectivity, although the computer can detect when the network cable is unplugged or not.  When the network cable is plugged in, it only gets a self-assigned IP address.  Because this is a Chromebox conversion, the firmware/BIOS is not configurable at all.  I am lucky to be able to select the .efi file it uses to boot, and that is enough to enable me to run macOS on it.  Therefore, there is no way to disable AppleVTD.  Might it be possible to have a boot flag for your kext that disables or ignores the changes you made to support AppleVTD?  That way, I can continue to use the most recent version of your kext since future updates may provide features or improvements that my network adapter can use.  Thanks for any help you can offer and again, sorry for the ungrateful users you have had to deal with.

[Mieze]

@mnfesq In case you can't disable VT-d in UEFI-Setup, use OpenCore to disable AppleVTD on your machine. That should do the job! Otherwise stay with the previous version.

[mnfesq]

3 hours ago, Mieze said:

@mnfesq In case you can't disable VT-d in UEFI-Setup, use OpenCore to disable AppleVTD on your machine. That should do the job! Otherwise stay with the previous version.

 

DisableIOMapper was enabled.  It did nothing.  I'm stuck on version 2.4.2 but that's nothing to complain about since it works fine.  If I get daring, I could try to modify SeaBIOS, the bios used with coreboot to make the Chromebox fully UEFI compatible, to enable VT-d.

[ZHIDR MI]

I used this driver, but macos does not recognize RTL8168. I can't figure out what the problem is. Please help.

Mac Pro (13950hx).ioreg

[Mieze]

@ZHDI You are using an old version of the driver which is incompatible with AppleVTD. Upgrade to the latest version and let's see if it helps.

[LockDown]

Hi @Mieze

May i know why you didn't include the WOL feature in info.plist. would be great to have this

[ZHIDR MI]

24 minutes ago, verdazil said:

@ZHIDR MI，根据我的经验，kext 2.4.2d 版本效果最佳。（机器 1）

所有新版本的工作都不稳定，连接经常中断......

 

 

I think this has nothing to do with AppleVTD