Jump to content
InsanelyMac Forum
Mieze

Driver for Realtek's RTL810x Fast Ethernet Series

Recommended Posts

Looks ok! The only thing which makes me wonder is that ASPM is enabled which may cause power management issues on some machines but as DHCP is working, it's obvious that there is inbound and outbound traffic on the interface.

 

Mieze

Share this post


Link to post
Share on other sites
Advertisement

I'm unable to disable ASPM in my BIOS.

May 31 20:47:43 iMac kernel[0]: Ethernet [RealtekRTL8100]: RTL8101E: (Chipset 0) at 0x<ptr>, 70:5a: f:19:94:5c

 

Chipset 0 is correct and  "at 0x<ptr>" is normal?

 

If it's correct, where is the error? I tried every kext related to RTL8101E and only your kext seems to work, but no luck...

 

If I use nullcpupowermanagement.kext, maybe it works?

Share this post


Link to post
Share on other sites

I'm unable to disable ASPM in my BIOS.

May 31 20:47:43 iMac kernel[0]: Ethernet [RealtekRTL8100]: RTL8101E: (Chipset 0) at 0x<ptr>, 70:5a: f:19:94:5c

 

Chipset 0 is correct and  "at 0x<ptr>" is normal?

 

If it's correct, where is the error? I tried every kext related to RTL8101E and only your kext seems to work, but no luck...

There is no indication of a driver issue. In case of an ASPM related failure, the link would constantly go up and down (every few seconds) without ever acquiring an IP address.

 

Mieze

Share this post


Link to post
Share on other sites

Ok, thanks for trying to help me.... good night....

mate, I'm facing the exact same issue. My chipset is RTL8136. This was the only driver that worked. I am also getting IP and everything, but no internet. Were you able to find any solution?

Share this post


Link to post
Share on other sites

Should these driver support an RTL81001/2/6E PCI Express Fast/Gigabit Ethernet Controler as Gigabit?

 

Is up and running for a Capitan Lenogo B50-50 but only at 100 Mbit not Gigabit

Share this post


Link to post
Share on other sites

mate, I'm facing the exact same issue. My chipset is RTL8136. This was the only driver that worked. I am also getting IP and everything, but no internet. Were you able to find any solution?

Did you manage to fix the issue somehow? Same issue over here... 0x<ptr>, IP but no WAN connectivity

Share this post


Link to post
Share on other sites

Hi,

I am facing exactly the same problem. The driver looks to work perfectly, DHCP gives the right IP and the rest of parameters but no connectivity to internet.

My hardware: HP Pavilion 17-g072, i7-5500U @2.4GHz, Intel HD 5500, 12 GB RAM, WiFi on USB Archer_T2U. Working systems:

Win10, Linux Ubuntu, El Capitan and macOS Sierra.

Of course, The Realtek card works perfectly with Win10 and Ubuntu.

 

Is it something with HP laptops, as I can see people with these machines mostly report this issue.

 

Regards to all,

Henryk

Share this post


Link to post
Share on other sites

I've been having a hard time getting this card to work. I installed the lnx2mac driver v 0.90 and nothing is showing under ethernet.

post-1199206-0-14921300-1485795961_thumb.jpg

Share this post


Link to post
Share on other sites

I've been having a hard time getting this card to work. I installed the lnx2mac driver v 0.90 and nothing is showing under ethernet.

Unfortunately I can't help you as this is a PCI card but the driver only supports PCIe devices. Sorry!

 

Mieze

Share this post


Link to post
Share on other sites

No problem man, I won't be needing this pci NIC card anymore since I found a newer kext to support my lan ports on my xw8600 workstation optimized for El Capitan. My issue was when I wake up from sleep, I'd lose Internet access.

Share this post


Link to post
Share on other sites

mate, I'm facing the exact same issue. My chipset is RTL8136. This was the only driver that worked. I am also getting IP and everything, but no internet. Were you able to find any solution?

 

I just wanted to let you know that I'm working on an update of the driver which supports newer hardware and is optimized for Sierra and El Capitan.

 

Mieze  :cat:

 

Hello, I'm also using this with 8136 chipset and have exactly the same issue, everything recognised totally fine and all working except internet! Not a huge deal for me as I seldom use ethernet and mainly wanted it working in order to use the App Store, but I look forward to a new version of this anyway and will test as soon as it's available.

 

Thanks for all the hard work Mieze, much appreciated :)

Share this post


Link to post
Share on other sites

As already announced weeks ago, here is the first development version 2.0.0d3 of the driver. Among several changes I added:

  • Support for Apple's private driver interface in order to resolve stability issues under heavy load and with virtualization software.
  • Support for polled receive mode.
  • Also supports RTL8107E which can be found on a number of new boards/notebooks.

Please take into account that this is new driver which is still under development and might have bugs, cause kernel panics, etc so that you should be prepared to recover from these situations.

 

Special thanks to user p569 for testing the driver on his RTL8107!  :thumbsup_anim:

 

Good luck testing!  :cat:

 

Mieze

 

RealtekRTL8100-V2.0.0d3.zip

Share this post


Link to post
Share on other sites

Thank you, Mieze, for your kind words

and making RTL8107 to work on my laptop

I pay my highest respect for your work on the driver

Great work!

p569

:construction::startreck:

Share this post


Link to post
Share on other sites

Will the new driver work with RTL8101/2/3 Family Ethernet NIC

Vendor Realtek PCIe GBE Family Controller.

This is a laptop

(Cheked by HWiNFO64)

 

On Windows 8.1 x64 I have Driver installed for RealTek PCIe FE Family Controller and it works fine.

 

I want to install El Capitan 10.11.6 on this laptop and want to confirm if the new update resolves the previous issues

Share this post


Link to post
Share on other sites

Thank you very, very much Mieze. The new version of the driver works fantastically.

Fabulous work.

Many thanks, again.

Henryk

 

 

My hardware: HP Pavilion 17-g072, i7-5500U @2.4GHz, Intel HD 5500, 12 GB RAM, WiFi on USB Archer_T2U.

Share this post


Link to post
Share on other sites

As test results have been quite promising, at least here hasn't been any bug report :) , I decided to push the source code to GitHub and also updated the prebuilt binary in the download section.

 

Have fun!

 

Mieze  :cat:

Share this post


Link to post
Share on other sites

Mize

 

When waking up or disconnecting and reconnecting the cable, the dhcp does not work , getting ip 169.254.x.x

 

After this, unloading and loading the kext, everything back normal operation.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PCIe ASPM support disabled.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: EEE support enabled.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: RxPoll support enabled.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: TCP/IPv4 segmentation offload enabled.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: TCP/IPv6 segmentation offload enabled.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: TCP/IPv6 checksum offload enabled.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Version 2.0.0 using interrupt mitigate value 0x0. Please don't support tonymacx86.com!
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PCI power management capabilities: 0xffc3.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PME# from D3 (cold) supported.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PCIe link capabilities: 0x00477c11, link control: 0x0140.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: RTL8106E: (Chipset 15) at 0x0xffffff81170de000, 40:ca:65:01:70:40
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: MSI interrupt index: 1
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: kIOEthernetWakeOnMagicPacket added to filters.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Already in power state 1.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: No medium selected. Falling back to autonegotiation.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: EEE Advertise: 0x2, Link Partner Ability: 0x2
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: pollIntervalTime: 1000us
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Link up on en0, 100-Megabit, Full-duplex, No flow-control, energy-efficient-ethernet
 

Share this post


Link to post
Share on other sites

 

Mize

 

When waking up or disconnecting and reconnecting the cable, the dhcp does not work , getting ip 169.254.x.x

 

After this, unloading and loading the kext, everything back normal operation.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PCIe ASPM support disabled.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: EEE support enabled.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: RxPoll support enabled.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: TCP/IPv4 segmentation offload enabled.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: TCP/IPv6 segmentation offload enabled.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: TCP/IPv6 checksum offload enabled.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Version 2.0.0 using interrupt mitigate value 0x0. Please don't support tonymacx86.com!
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PCI power management capabilities: 0xffc3.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PME# from D3 (cold) supported.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PCIe link capabilities: 0x00477c11, link control: 0x0140.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: RTL8106E: (Chipset 15) at 0x0xffffff81170de000, 40:ca:65:01:70:40
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: MSI interrupt index: 1
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: kIOEthernetWakeOnMagicPacket added to filters.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Already in power state 1.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: No medium selected. Falling back to autonegotiation.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: EEE Advertise: 0x2, Link Partner Ability: 0x2
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: pollIntervalTime: 1000us
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Link up on en0, 100-Megabit, Full-duplex, No flow-control, energy-efficient-ethernet
 

 

Please post a kernel log extract showing a cycle where you unplugged and replugged the cable.

Share this post


Link to post
Share on other sites

Hello mieze, Thanks for your reply

I removed the timestamp from the logs, to make it more readable

 

come on

 

Loading the kext without the cable connected
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PCIe ASPM support disabled.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: EEE support enabled.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: RxPoll support enabled.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: TCP/IPv4 segmentation offload enabled.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: TCP/IPv6 segmentation offload enabled.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: TCP/IPv6 checksum offload enabled.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Version 2.0.0 using interrupt mitigate value 0x0. Please don't support tonymacx86.com!
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PCI power management capabilities: 0xffc3.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PME# from D3 (cold) supported.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PCIe link capabilities: 0x00477c11, link control: 0x0140.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: RTL8106E: (Chipset 15) at 0x0xffffff812e4c7000, 00:6a:9f:01:70:40
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: MSI interrupt index: 1
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: kIOEthernetWakeOnMagicPacket added to filters.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Already in power state 1.
kernel[0]: en0: attached with 6 suspended link-layer multicast membership(s)
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: No medium selected. Falling back to autonegotiation.
kernel[0]: en0: successfully restored 6 suspended link-layer multicast membership(s) (err=0)
Setting the tcpdump (sudo tcpdump -i en0 port 67 or port 68 -e -n or arp) and connecting the cable
 
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: EEE Advertise: 0x2, Link Partner Ability: 0x2
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: pollIntervalTime: 1000us
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Link up on en0, 100-Megabit, Full-duplex, No flow-control, energy-efficient-ethernet

log fom tcpdump

ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
00:6a:9f:01:70:40, ethertype IPv4 (0x0800), length 342: 192.168.1.1.67 > 192.168.1.104.68: BOOTP/DHCP, Reply, length 300
ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
00:6a:9f:01:70:40, ethertype IPv4 (0x0800), length 342: 192.168.1.1.67 > 192.168.1.104.68: BOOTP/DHCP, Reply, length 300
ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 192.168.1.104 tell 192.168.1.1, length 46
ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 192.168.1.104 tell 192.168.1.1, length 46
00:6a:9f:01:70:40, ethertype IPv4 (0x0800), length 342: 192.168.1.1.67 > 192.168.1.104.68: BOOTP/DHCP, Reply, length 300
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Probe 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Probe 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Probe 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Announcement 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Announcement 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Announcement 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
00:6a:9f:01:70:40, ethertype ARP (0x0806), length 60: Reply 192.168.1.1 is-at 3c:1e:04:61:73:dc, length 46
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 169.254.255.255 tell 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
00:6a:9f:01:70:40, ethertype ARP (0x0806), length 60: Reply 192.168.1.1 is-at 3c:1e:04:61:73:dc, length 46
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 169.254.255.255 tell 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 169.254.255.255 tell 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 169.254.255.255 tell 192.168.1.104, length 28
Ok, ip received and working
 
 
Disconnecting the cable  
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Link down on en0

Reconnecting the cable

kernel[0]: (kernel) Ethernet [RealtekRTL8100]: EEE Advertise: 0x2, Link Partner Ability: 0x2
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: pollIntervalTime: 1000us
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Link up on en0, 100-Megabit, Full-duplex, No flow-control, energy-efficient-ethernet

log from tcpdump

3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Probe 169.254.195.12, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Probe 169.254.195.12, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Probe 169.254.195.12, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Announcement 169.254.195.12, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Announcement 169.254.195.12, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Announcement 169.254.195.12, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
The interface can not talk to the dhcp server
 
 

kextunload  kext

kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Link down on en0

kextload kext

kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PCIe ASPM support disabled.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: EEE support enabled.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: RxPoll support enabled.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: TCP/IPv4 segmentation offload enabled.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: TCP/IPv6 segmentation offload enabled.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: TCP/IPv6 checksum offload enabled.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Version 2.0.0 using interrupt mitigate value 0x0. Please don't support tonymacx86.com!
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PCI power management capabilities: 0xffc3.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PME# from D3 (cold) supported.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PCIe link capabilities: 0x00477c11, link control: 0x0140.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: RTL8106E: (Chipset 15) at 0x0xffffff812e4c9000, 00:6a:9f:01:70:40
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: MSI interrupt index: 1
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: kIOEthernetWakeOnMagicPacket added to filters.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Already in power state 1.
kernel[0]: en0: attached with 4 suspended link-layer multicast membership(s)
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: No medium selected. Falling back to autonegotiation.
kernel[0]: en0: successfully restored 4 suspended link-layer multicast membership(s) (err=0)
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: EEE Advertise: 0x2, Link Partner Ability: 0x2
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: pollIntervalTime: 1000us
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Link up on en0, 100-Megabit, Full-duplex, No flow-control, energy-efficient-ethernet

Okay, everything normal again.
 
 
As I did the same procedure in linux and work normally, I discarded performing a better inspection of dhcp traffic with tcpdump.
Haaaa, I performed the tests with and without ipv6
 
Any idea ?
 
 
Tanks

Share this post


Link to post
Share on other sites

@jalves: I've checked the driver's code again and found no evidence for a driver bug. I don't have hardware to test myself but as sleep/wake and link change detection are basic functions of a driver which have been thoroughly tested, it's hard to imagine a scenario in which a driver bug causing this behavior wouldn't have been found much earlier. That's why I'm not willing to believe in a driver bug until some user with the same chip confirms this issue.

 

Please check your BIOS settings and make sure that network boot, the UEFI network stack as well as any LAN related power management functions are disabled (in particular if there is any function to put the NIC into a low power state when the cable is disconnected). 

 

Mieze

Share this post


Link to post
Share on other sites

@Mieze

 

 

I reviewed my settings and also did not find anything strange

 

Just for record

 

I test it on a Ubuntu 14.04LTS , 4.4.0-31 kernel, driver r8169 2.3LK-NAPI .  ( Realtek 8106E - 10EC, 8136 )

 

Tank you for your attention

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.



  • Similar Content

    • By ITzTravelInTime
      KX AUDIO DRIVER MOD
       
      Hi guys i am a small developer, i really like to use my sound blaster cards on my machines and i love also coding, so when i find the source code for the kx audio driver on git hub and then Eugene, the creator of kx audio driver decided to no longer maintain the project, i decided to start working on a mod of this driver. 
       
      With my mod, created starting from the sources of the last version of kx audio driver, and also by using apple developer documentation for pci and audio drivers as reference, i am working to achieve 2 things mainly: get all the cards supported by the driver to work with all the recent versions os macOS and add support for other cards that are not officially supported by the driver that works or could, but needs to be more properly supported.
       
      This driver is made to support cards based on the E-mu 10k1, 10k2 and similars (like what is used by audigy rx and audigy 4 cards).
       
      Supported cards are:
       
       - most of the sound blaster live!, live! 5.1 and live! 5.1 digital series
       - sound blaster 512
       - sound blaster 256
       - other creative and e-mu sound cards based on the 10k1 chip (cards with the ES1370/ES1371/ES1372/ES1373 chips are not supported)
       - sound blaster Audigy series (1 st gen)
       - sound blaster Audigy 2  and audigy 2 zs series
       - E-MU cards based on the 10k2 sound chip
       - Some Audigy 4 cards (SB0610 only) and the audigy 4 pro
       - Sound blaster Audigy RX (sb0155)
       - other creative and e-mu cards based on the (10k2, 10k2,5 and CA10300 based cards)
       
      NOT supported cards:
       
       - Any ISA Sound card
       - ES1370/ES1371/ES1372/ES1373 based sound cards
       - CMI8738/CMI8788 based cards
       - Any CA0106 based card and cards with similar architectures (like sound blaster live! 24 bit, sound blaster audigy SE SB0570, audigy LS and similars, but audigy SA is supported)
       - Any sound blaster x-fi (some of them works on macOS using a modified version of voodoo hda)
       - Any sound blaster recon3D
       - Any sound blaster Z/ZS/ZX and similar series
       - Any sound blaster AE5 series
       
      In the time being the things i have modded or added with this mod are:
       
      - increased the simple buffer frames number with different values for emu10k1 based cards and emu10k2 based cards (including recent audigy 4 and rx) to reduce and all the audio cracking issues and possibly fixing all of them on a lot of cards
       
      - added a more proper support for the pci express sound blaster audigy rx (which basically is an audigy 4 with a pcie bridge chip) 
       
      - added more fancy names for the cards in the settings and other menus (so the name will be, for example, SB live! 5.1 SB0060 instead of kx SB0060 [e880] witch was shown in the original driver)
       
      - added support to sample rate chaning and added lots of sample rates (from 8 khz to 176,4 khz) to accomodate any possible usecase (note that 10k1 sound cards are limited up to 48khz sample rate, and 10k2 based cards for now are limited up to 176,4 khz and because of issues getting 192 khz to work, for now the driver goes up to 176,4 khz for supported cards) 
       
      - added boot args to manage the driver:
       
      Boot args to use with the kx audio driver mod: -kx_disable or -kxdisable or -kxoff This will prevent the driver from doing any initialization work, so the driver is basically disabled, use it to boot your ssytem in case the driver is giving you issues and kernel panics while you are trying to boot/using your system, so you are able to remove this driver or replace it with another version of it or to do some truble shooting. -kx_debug or -kxdebug or -kxspec Will show more debug info about the card, mainly the i/o port address and the kind of bus that it uses -kx_exp_deb or -kx_beta or -kxbeta Will enable experimental and probably not working or unstable features like showing inputs for the card or 192 khz sampling rate, use it only for testing and debug purposes, this may likely cause instability and problems in the everyday usage! Use it at your own risk! -kx_original or -kxoriginal This will basically turn off almost all the mods of this mod, so the driver will come to work as it was before modding it, this can be usefoul as a "safe mode" like feture to have a working driver in case of problems with features of the mod, so using this means no crsking issues improvements, only 48 khz sample rate and only features of the non-modded kx audio driver for mac os x  
      - created a script file to use with the driver for debug and also installer replacement, it can be also used to unload and reload, replacement of the driver without rebooting
       
      What i'd like to implement but i don't know how to do:
       
       - I'd like mainly to add a more proper support to the pci bridge chip of the audigy rx,
       
       - have audio inputs working,
       
       - fix the support when using more than one card, to get all the cards shown in the settings and other menus,
       
       - have the gameport/gameport midi port of older cards to be used in mac os as a midi in/out
       
      If other developers would like to join and help me, you can, and also an hand from other people with testing and feedback will be nice.
       
      link for the kext only (if you have clover put it in [your clover efi folder]/clover/kexts/[your macOS version]/ so it will not be deleted when updating macOS):
               - download from the downloads section:          kX Audio Driver Mod by ITzTravelInTime 1.01                                                                                    - external download:                                      https://dl.dropboxus...Driver.kext.zip   link for the installer pack (the best way to install it, but you have to reinstall it when you upgrade macOS, remeber to fix kext permitions and rebuild the kernelcache if you want to remove the kext from it's install directory without using the unistall feature of the provvided script):              - download:                                                   https://dl.dropboxus...aller pack.zip   Source code from Git Hub:          -  github repo:                                               https://github.com/ITzTravelInTime/kx-audio-driver   NOTE: Some system because of some problems with the HPET may need to use FixHPET in clover and to install the kext in /System/Library/Extensions  






    • By ITzTravelInTime
      This driver is a mod of the popular kx audio driver for mac os x, the project goal is to still maintaining it for the future releases of mac os and to include as much cards as possible and to get all the features of the cards to work.
       
      Currently the only features not supported are audio inputs and integrated midi and synth capabilitues of the cards, and some minor things like creative remote controllers or software controlled volume gears on creative external drives and bays)
       
      It supports most the sound blaster live! series cards, the sound blaster PCI 512, most of the audigy (emu 10k2 based) series, audigy 1, audigy 2, audigy 2 zs, audigy 4 (SB0610), audigy 4 pro, audigy 5 and audigy rx (sb1550) and some e-mu edsp audio cards with all the recent versions of mac os, tested to work with mac os yosemite, el capitan, sierra and high sierra on intel based machines from socket 775 to 1151 (including enthusiast platforms like x58, x79, x99, x299) and also confirmed to work on mac pros.
       
      reference topic:
       
      Kx audio driver mod [sound blaster live!, audigy 1/2/4/RX emu edsp]
    • By ivanagui2
      VMQemuVGA display adapter driver for OSx86 running as a VirtualBox guest. The binary should work on all OSs from Snow Leopard up to Yosemite 10.10. It allows to set different screen resolutions in VirtualBox from System Preferences.   The changes I've made to the fork have been minimal.
      GitHub project page Binary and source releases Special thanks:
      PureDarwin
      probonopd
      rafirafi
      Zenith432
      VMware, Inc


    • By Mieze
      This project is dedicated to the memory of Mausi, the cat I loved more than anybody else.
       

       
      A few days before Christmas I started my latest project, a new driver for recent Intel onboard LAN controllers. My intention was not to replace hnak's AppleIntelE1000e.kext completely but to deliver best performance and stability on recent hardware. That's why I dropped support for a number of older NICs. Currently the driver supports:
       
      5 Series
      82578LM 82578LC 82578DM 82578DC 6 and 7 Series
      82579LM 82579V 8 and 9 Series
      I217LM I217V I218LM I218V I218LM2 I218V2 I218LM3 100 Series (since V2.1.0d0)
      I219LM I219V 200 Series (since V2.3.0d0)
      I219LM I219V 300 Series (since V2.4.0d0)
      I219LM I219V Key Features of the Driver
      Support for multisegment packets relieving the network stack of unnecessary copy operations when assembling packets for transmission. No-copy receive and transmit. Only small packets are copied on reception because creating a copy is more efficient than allocating a new buffer. TCP, UDP and IPv4 checksum offload (receive and transmit). Support for TCP/IPv6 and UDP/IPv6 checksum offload. Makes use of the chip's TCP Segmentation Offload (TSO) feature with IPv4 and IPv6 in order to reduce CPU load while sending large amounts of data (disabled). Fully optimized for Sierra (64bit architecture) but should work with older 64bit versions of macOS too, provided you build from source with the appropriate SDK for the target OS. Support for Energy Efficient Ethernet (EEE). VLAN support is implemented but untested as I have no need for it. The driver is published under GPLv2. Current Status
      The driver has been tested successfully with I217V, I218V and 82579V under 10.9.5 and above. The attached archive includes source code as well as a prebuilt binary (debug version) for Mavericks and Yosemite. Known Issues
      There seem to be problems while using VMware with version 1.x.x of the driver. In case you are affected use version 2.0.0 or newer. FAQ
      Could you add support of for...? Well, you are probably asking me to add support for one of the older NICs like the 82571/2/3/4L or 82583 and the answer will be no as I dropped support for these chips intentionally. They are broken and I lost more than 2 weeks trying to make it work on the 82574L without success. I was asked to add support for I210, I211 and I350 but as these chips have a completely different architecture, which isn't supported by the underlying Linux driver, this is impossible, sorry. Does it work with Snow Leopard or 32 bit kernels? No and I have no plans to make a version for 32 bit kernels or anything older than Lion. WoL from S5 doesn't work with this driver but under Windows it's working. Is this a driver bug? No it isn't, the driver is working as it should because OS X doesn't support WoL from S5. Installation
      Goto /S/L/E and delete AppleIntelE1000e.kext. Recreate the kernel cache. Open System Preferences and delete the corresponding network interface, e. g. en0. Reboot. Install the new driver and recreate the kernel cache. I recommend to use Kext Wizard or a similar utility for the installation. Reboot Open System Preferences again, select Network and check if the new network interface has been created automatically or create it manually now. Configure the interface. Troubleshooting
      Make sure you have followed the installation instructions especially when you have issues with certain domains while the others are working fine. Use the debug version to collect log data when trying to track down problems. The kernel log messages can be retrieved with "grep kernel /var/log/system.log" in Terminal. Starting from Sierra use "log show --predicate "processID == 0" --debug" in order to retrieve kernel logs. Include the log data when asking for support or giving feedback. I'm an engineer, not a clairvoyant. Don't copy and paste large amounts of log data to your post. Create an archive with the log data and attach it to your post. In case you don't want to make your log data publicly accessible, contact me via PM and I will provide you a mail address to send it directly to me.  Check your BIOS settings. You might want to disable Network Boot and the UEFI Network Stack as these can interfere with the driver. Double check that you have removed any AppleIntelE1000e.kext from your system because it could prevent the driver from working properly. Delete the following files: /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/preferences.plist Verify your bootloader configuration, in particular the kernel flags. Avoid using npci=0x2000 or npci=0x3000.  In Terminal run netstat -s in order to display network statistics. Carefully examine the data for any unusual activity like a high number of packets with bad IP header checksums, etc. In case auto-configuration of the link layer connection doesn't work it might be necessary to select the medium manually in System Preferences under Network for the interface. Use Wireshark to create a packet dump in order to collect diagnostic information. Keep in mind that there are many manufacturers of network equipment. Although Ethernet is an IEEE standard, different implementations may show different behavior causing incompatibilities. In case you are having trouble try a different switch or a different cable. Changelog
      Version 2.4.0 (2018-04-14) Added support for 300 series versions of I219LM and I219V. Updated underlying Linux source code. Version 2.3.0 (2017-06-20) Added support for 200 series versions of I219LM and I219V. Version 2.2.0 (2016-09-23) Disabled TSO to work around a hardware bug. Version 2.1.0 (2016-05-24) Added support for I219LM and I219V Version 2.0.0 (2015-04-22) First official release which is identical to 2.0.0d2 (only the version number has been changed). Version 2.0.0d2 (2015-04-04) Changed the tx descriptor write back policy for 82579, I217 and I218 to prevent random tx deadlocks. Version 2.0.0d1 (2015-03-14) Uses Apple's private driver interface introduced with 10.8. Supports packet scheduling with QFQ Solves the VMware issue. Version 1.0.0d6 (2015-03-04) Reworked TSO6 support to avoid problems with VMware. Wake-on-LAN now working. Version 1.0.0d5 (2015-02-27) Reworked TSO4 support to eliminate the bug of 1.0.0d4. Added some debug code in order to collect information about the VMware related issue. Version 1.0.0d4 (2015-02-25) Set total length field of the IP-header to zero for TSO4 operations. Report EEE activation state in kernel log message when the link has been established. Version 1.0.0d3 (2015-02-11) Reworked media selection and EEE support (EEE is now activated when both link partners support it. It can be disabled selecting the medium manually). Duplex setting for 10/100 MBit connections is now reported correctly. The number of tx descriptors has been reduced from 2048 to 1024. The code has been cleaned up and obsolete files have been removed. Version 1.0.0d2 (2015-01-31) First development release. Getting the Driver
      The source code can be found on GitHub: https://github.com/Mieze/IntelMausiEthernet There is also a prebuilt binary for 10.11 and above in the download section: http://www.insanelymac.com/forum/files/file/396-intelmausiethernet/ Build from Source for 10.8
      Register as a developer on Apple's developer website. A free membership is sufficient. Download a copy of Xcode 5.1.1 and install it on your machine. In the project select 10.8 as the "Base SDK" and the "Deployment Target". Call "Archive" from the menu "Product" and save the built driver. Credits
      Thanks to RehabMan and Yung Raj for running tests and pointing me in the right direction while I was trying to fix TSO. Special thanks to Yung Raj for motivating me when I was about to give up.
    • By Mieze
      Driver for recent Intel onboard LAN controllers. Currently the driver supports:
       
      5 Series
      82578LM 82578LC 82578DM 82578DC 6 and 7 Series
      82579LM 82579V 8 and 9 Series
      I217LM I217V I218LM I218V I218LM2 I218V2 I218LM3 100 Series
      I219LM I219V 200 and 300 Series
      I219LM I219V Please see the project's homepage at http://www.insanelymac.com/forum/topic/304235-intelmausiethernetkext-for-intel-onboard-lan/ for a detailed project description.
×