• Become a Premium Member for $25/year with no ads to improve your community experience. Upgrade to Pro Account for faster response and no wait times!

Monterey - "Dragon 2.5gb" LAN nonfunctional

jtb

New member
Joined
Mar 23, 2022
Messages
4
Motherboard
AsRock B460 Steel Legend
CPU
Intel i5-10400 (6-core, 10th gen, comet lake)
Graphics
Radeon RX 560 4gb
OS X/macOS
13.x
Bootloader
  1. OpenCore (UEFI)
Mobile Phone
  1. Android
  2. iOS
Hello. I have an AsRock B460 Steel Legend board here that says it has something called Dragon 2.5g for the LAN card. I looked it up and received conflicting information, some saying it's a Realtek 8125 driver and others saying it's not (with no indication of what it is).

Anyway, I used the LucyRTL8125Ethernet kext and it never worked during installation (had to use Horndis and a phone to download), and still nonfunctional ethernet and neither of my two wifi dongles are recognized.

Just wondering if anyone has any insight here - is my mysterious Dragon 2.5 card requiring some other kext? Is the wifi dongle recognition another matter?

Thanks
 
Hello. I have an AsRock B460 Steel Legend board here that says it has something called Dragon 2.5g for the LAN card. I looked it up and received conflicting information, some saying it's a Realtek 8125 driver and others saying it's not (with no indication of what it is).

Anyway, I used the LucyRTL8125Ethernet kext and it never worked during installation (had to use Horndis and a phone to download), and still nonfunctional ethernet and neither of my two wifi dongles are recognized.

Just wondering if anyone has any insight here - is my mysterious Dragon 2.5 card requiring some other kext? Is the wifi dongle recognition another matter?

Thanks
LucyRTL8125Ethernet.kext will work for sure on this Motherboard and it's working on Z690 too. To fix the Ethernet issue, do the following.

System Preferences>Network>Ethernet>Advanced>Hardware

Set the following

Configure: Manually
Speed: 1000baseT
Duplex: full-duplex, flow-control
MTU: Standard (1500)

Once done, click on OK and then click on Apply. Ethernet should be up.
 
LucyRTL8125Ethernet.kext will work for sure on this Motherboard and it's working on Z690 too. To fix the Ethernet issue, do the following.

System Preferences>Network>Ethernet>Advanced>Hardware

Set the following

Configure: Manually
Speed: 1000baseT
Duplex: full-duplex, flow-control
MTU: Standard (1500)

Once done, click on OK and then click on Apply. Ethernet should be up.
I just did that configuration and it doesn't recognize that there's an ethernet cable plugged in after that. I tried with and without the flow control, and restarted each time just to ensure it wasn't some sort of boot process thing not applying the settings.

With the ethernet plugged in normally, there's a light right on the cable connection - when set manually and forced to 1000baseT, that light just goes out and it thinks there's no cable. It says "Status: Cable Unplugged"

edit: maybe it's of no consequence, but I'll mention that this ethernet cable runs to a TP-Link hub that picks up a wireless signal. It's worked before, I don't think it's a matter of not acquiring an IP in this case - it's just convinced there's no connection.

As soon as I switch from forcing 1000baseT to Auto Select, the light comes on and it recognizes a cable is present - it assigns an IP address and subnet mask, but the router IP remains unfound.
 
Last edited:
I think it may be a limitation of my little wireless hub. How bout these dongles? I have a TP-Link TL-WN821N and a generic thing that just says "WiFi N - 300m etc)
 
I just did that configuration and it doesn't recognize that there's an ethernet cable plugged in after that. I tried with and without the flow control, and restarted each time just to ensure it wasn't some sort of boot process thing not applying the settings.

With the ethernet plugged in normally, there's a light right on the cable connection - when set manually and forced to 1000baseT, that light just goes out and it thinks there's no cable. It says "Status: Cable Unplugged"

edit: maybe it's of no consequence, but I'll mention that this ethernet cable runs to a TP-Link hub that picks up a wireless signal. It's worked before, I don't think it's a matter of not acquiring an IP in this case - it's just convinced there's no connection.

As soon as I switch from forcing 1000baseT to Auto Select, the light comes on and it recognizes a cable is present - it assigns an IP address and subnet mask, but the router IP remains unfound.
Maybe your ISP requires a manual IP and DNS configuration?
 
I think it may be a limitation of my little wireless hub. How bout these dongles? I have a TP-Link TL-WN821N and a generic thing that just says "WiFi N - 300m etc)
No, that shouldn't be the case at all. Are you using the latest kext? These Wireless Adapters require additional drivers, which can be also obtained from the manufacturer's site.
 

Latest posts

Forum statistics

Threads
2,084
Messages
19,462
Members
29,585
Latest member
OhCamargo