Jump to content

Driver for Realtek's RTL810x Fast Ethernet Series

Realtek RTL8105 RTL8101 RTL8102 RTL8106 RTL8103 RTL8401 RTL8402 driver

  • Please log in to reply
69 replies to this topic

#21
Dr. Hurt

Dr. Hurt

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPipPipPip
  • 1,456 posts
  • Gender:Male
  • Location:Cairo, Egypt and NYC, USA
  • Interests:Wandering around on the internet!! Politics, Sci/Tech, Medicine.

Anyone else here who has tested sleep/wake? Does the network connection work properly after wake? Together with Zythyr, I'm currently preparing a new development release and will post it here as soon as he confirms that it works for him.

 

Mieze

 

The connection works perfectly fine after wake on my Inspiron with RTL8105  :)



#22
Mieze

Mieze

    InsanelyMac Sage

  • Coders
  • 447 posts
  • Gender:Female
  • Location:Germany
  • Interests:Cats

The connection works perfectly fine after wake on my Inspiron with RTL8105  :)

Just one more question: which chipset is your RTL8105? You can find the chipset number in the kernel logs.

 

Mieze



#23
Dr. Hurt

Dr. Hurt

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPipPipPip
  • 1,456 posts
  • Gender:Male
  • Location:Cairo, Egypt and NYC, USA
  • Interests:Wandering around on the internet!! Politics, Sci/Tech, Medicine.

Just one more question: which chipset is your RTL8105? You can find the chipset number in the kernel logs.

 

Mieze

 

I'm not at home now. I'll check and tell you tomorrow.



#24
Dr. Hurt

Dr. Hurt

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPipPipPip
  • 1,456 posts
  • Gender:Male
  • Location:Cairo, Egypt and NYC, USA
  • Interests:Wandering around on the internet!! Politics, Sci/Tech, Medicine.
2/26/14 11:12:07.000 AM kernel[0]: Ethernet [RealtekRTL8100]: RTL8105E: (Chipset 11) at 0xffffff8082c85000, xx:xx:xx: ....


#25
Mieze

Mieze

    InsanelyMac Sage

  • Coders
  • 447 posts
  • Gender:Female
  • Location:Germany
  • Interests:Cats

Zythyr and I, we managed to finish the next development release of the driver. I updated the source code and the binaries attached to the first post of this thread a few minutes ago. Everyone is encouraged to test the new release on her/his system.

 

Mieze 



#26
lisai9093

lisai9093

    InsanelyMac Protégé

  • Members
  • PipPip
  • 86 posts
  • Gender:Male

Zythyr and I, we managed to finish the next development release of the driver. I updated the source code and the binaries attached to the first post of this thread a few minutes ago. Everyone is encouraged to test the new release on her/his system.

 

Mieze 

Unfortunately, ethernet failed to work after wake. One thing I notice is that Hurt has ethernet card built-in in system info, but not for mine. Does it matter?



#27
Mieze

Mieze

    InsanelyMac Sage

  • Coders
  • 447 posts
  • Gender:Female
  • Location:Germany
  • Interests:Cats

Unfortunately, ethernet failed to work after wake. One thing I notice is that Hurt has ethernet card built-in in system info, but not for mine. Does it matter?

 

No, I don't think so. Check your BIOS settings. Do you have Network Boot or the UEFI network stack enabled? Please disable it. What happens when you enable/disable the network interface using ifconfig up/down in Terminal? I'm asking because this is almost the same as sleep/wakeup.

 

Mieze



#28
lisai9093

lisai9093

    InsanelyMac Protégé

  • Members
  • PipPip
  • 86 posts
  • Gender:Male

No, I don't think so. Check your BIOS settings. Do you have Network Boot or the UEFI network stack enabled? Please disable it. What happens when you enable/disable the network interface using ifconfig up/down in Terminal? I'm asking because this is almost the same as sleep/wakeup.

 

Mieze

My BIOS supports UEFI, but I cannot disable network boot since there is no option.

 

I tried ifconfig en0 up/down many times, but there seems no difference. Ethernet will continue work before sleep and fail after wake, and ifconfig up/down is not changing anything. So I guess something is different between ifconfig up/down and actual sleep/wake.

 

I also tried to compare ioreg before and after sleep. I found IOPCIPMCSState is different in these two cases. See attached picture, not sure if it helps though:

Attached File  Screen Shot 2014-02-26 at 3.47.32 PM.png   591.21KB   1 downloads



#29
Mieze

Mieze

    InsanelyMac Sage

  • Coders
  • 447 posts
  • Gender:Female
  • Location:Germany
  • Interests:Cats

I tried ifconfig en0 up/down many times, but there seems no difference. Ethernet will continue work before sleep and fail after wake, and ifconfig up/down is not changing anything. So I guess something is different between ifconfig up/down and actual sleep/wake.

 

Sorry, in case my post was inaccurate but this is not what I asked for. Call ifconfig down/up while network is functional and let me know if it resumes operation after ifconfig up.

 

Mieze



#30
lisai9093

lisai9093

    InsanelyMac Protégé

  • Members
  • PipPip
  • 86 posts
  • Gender:Male

Sorry, in case my post was inaccurate but this is not what I asked for. Call ifconfig down/up while network is functional and let me know if it resumes operation after ifconfig up.

 

Mieze

Mac:~ peter$ sudo ifconfig up
ifconfig: interface up does not exist
Mac:~ peter$ sudo ifconfig down
ifconfig: interface down does not exist
Mac:~ peter$ ifconfig up

I don't think it is the right syntax. Then I tried ifconfig en0 down which successfully disabled my ethernet, the LED in ethernet port also stopped blinking. After ifconfig en0 up, ethernet shows "Connected" and everything is normal.



#31
Mieze

Mieze

    InsanelyMac Sage

  • Coders
  • 447 posts
  • Gender:Female
  • Location:Germany
  • Interests:Cats

I don't think it is the right syntax. Then I tried ifconfig en0 down which successfully disabled my ethernet, the LED in ethernet port also stopped blinking. After ifconfig en0 up, ethernet shows "Connected" and everything is normal.

 

 

Ok, at least we know now that the enable() and disabled() routines are working properly.

 

Mieze



#32
hellozx

hellozx

    InsanelyMac Protégé

  • Members
  • Pip
  • 7 posts

Great work!Thank you~

Work perfectly on my RTL8103e Chipest 7(shown in kernel log)

My laptop is dell insprision 15R n5010

Work well afer wake up



#33
Mieze

Mieze

    InsanelyMac Sage

  • Coders
  • 447 posts
  • Gender:Female
  • Location:Germany
  • Interests:Cats

@lisai9093: I tried to find some background information about IOPCIPMCSState but found nothing. Therefore I checked this property of en0 on my 2011 iMac and it shows a similar behavior. IOPCIPMCSState changed from 0x0 before sleep to 0x2108 after wakeup.

 

Mieze



#34
lisai9093

lisai9093

    InsanelyMac Protégé

  • Members
  • PipPip
  • 86 posts
  • Gender:Male

@lisai9093: I tried to find some background information about IOPCIPMCSState but found nothing. Therefore I checked this property of en0 on my 2011 iMac and it shows a similar behavior. IOPCIPMCSState changed from 0x0 before sleep to 0x2108 after wakeup.

 

Mieze

uhmm that's strange. i also did some other test on ethernet setting that might be useful to you:

 

i tried to play with DHCP in ethernet setting. Test after wakeup, if DHCP is enabled, the ethernet card cannot get IP address from my router, there is only self-assigned IP instead. Then I double checked my router site (192.168.0.1), under "device table" section where all devices and their IP listed. My machine's ethernet port is not in the list.

 

So I disabled DHCP and assigned IP address myself in Setting. I put 192.168.0.14 as my IP because it is not used to prevent IP conflict. Then I saw this IP showing up in the "Device List". And the MAC address matches with my ethernet card's MAC address.

 

Here is some log lines for one plug-in and out cycle:

Feb 28 17:15:13 Mac kernel[0]: Ethernet [RealtekRTL8100]: Link up on en0, 100-Megabit, Full-duplex, No flow-control
Feb 28 17:15:16 Mac.local configd[19]: network changed: v4(en0+:192.168.0.14, en1) DNS! Proxy! SMB
Feb 28 17:15:18 Mac.local racoon[320]: failed to bind to address fd00::a9e:1ff:fe2b:b425[500] (Can't assign requested address).
Feb 28 17:15:18 Mac.local racoon[320]: failed to bind to address fd00::a9e:1ff:fe2b:b425[500]: because interface address is/was not ready (flags 42).
Feb 28 17:15:18 Mac.local racoon[320]: failed to bind to address fd00::a9e:1ff:fe2b:b425[4500] (Can't assign requested address).
Feb 28 17:15:18 Mac.local racoon[320]: failed to bind to address fd00::a9e:1ff:fe2b:b425[4500]: because interface address is/was not ready (flags 42).
Feb 28 17:15:18 Mac.local racoon[320]: failed to bind to address fd00::a9e:1ff:fe2b:b425[500] (Can't assign requested address).
Feb 28 17:15:18 Mac.local racoon[320]: failed to bind to address fd00::a9e:1ff:fe2b:b425[500]: because interface address is/was not ready (flags 42).
Feb 28 17:15:18 Mac.local racoon[320]: failed to bind to address fd00::a9e:1ff:fe2b:b425[4500] (Can't assign requested address).
Feb 28 17:15:18 Mac.local racoon[320]: failed to bind to address fd00::a9e:1ff:fe2b:b425[4500]: because interface address is/was not ready (flags 42).
Feb 28 17:15:18 Mac.local configd[19]: network changed: v4(en0:192.168.0.14, en1) DNS* Proxy SMB
Feb 28 17:15:18 Mac.local racoon[320]: failed to bind to address fd00::a9e:1ff:fe2b:b425[500] (Can't assign requested address).
Feb 28 17:15:18 Mac.local racoon[320]: failed to bind to address fd00::a9e:1ff:fe2b:b425[500]: because interface address is/was not ready (flags 42).
Feb 28 17:15:18 Mac.local racoon[320]: failed to bind to address fd00::a9e:1ff:fe2b:b425[4500] (Can't assign requested address).
Feb 28 17:15:18 Mac.local racoon[320]: failed to bind to address fd00::a9e:1ff:fe2b:b425[4500]: because interface address is/was not ready (flags 42).
Feb 28 17:15:19 Mac.local configd[19]: network changed.
Feb 28 17:15:23 Mac.local AirPlayUIAgent[876]: 2014-02-28 05:15:23.988534 PM [AirPlayUIAgent] Changed PIN pairing: no
Feb 28 17:15:24 Mac.local AirPlayUIAgent[876]: 2014-02-28 05:15:24.038392 PM [AirPlayUIAgent] Changed PIN pairing: no
Feb 28 17:15:24 Mac.local com.apple.WebKit.Networking[934]: tcp_connection_destination_prepare_complete 5769 connectx to 192.168.0.1#80 failed: 64 - Host is down
Feb 28 17:15:24 Mac.local com.apple.WebKit.Networking[934]: tcp_connection_handle_destination_prepare_complete 5769 failed to connect
Feb 28 17:15:24 Mac.local com.apple.WebKit.Networking[934]: tcp_connection_destination_prepare_complete 5769 connectx to 192.168.0.1#80 failed: 64 - Host is down
Feb 28 17:15:24 Mac.local com.apple.WebKit.Networking[934]: tcp_connection_handle_destination_prepare_complete 5769 failed to connect
Feb 28 17:15:40 Mac kernel[0]: Ethernet [RealtekRTL8100]: Link down on en0


#35
Mieze

Mieze

    InsanelyMac Sage

  • Coders
  • 447 posts
  • Gender:Female
  • Location:Germany
  • Interests:Cats

 

i tried to play with DHCP in ethernet setting. Test after wakeup, if DHCP is enabled, the ethernet card cannot get IP address from my router, there is only self-assigned IP instead. Then I double checked my router site (192.168.0.1), under "device table" section where all devices and their IP listed. My machine's ethernet port is not in the list.

 

So I disabled DHCP and assigned IP address myself in Setting. I put 192.168.0.14 as my IP because it is not used to prevent IP conflict. Then I saw this IP showing up in the "Device List". And the MAC address matches with my ethernet card's MAC address.

 

In the device table on the router? This would mean that after a wakeup packets are going out, i.e. the transmitter is working but the receiver isn't. Maybe I should check the receiver config for your chipset again. There might be a hidden error?

 

Mieze



#36
ikkoku

ikkoku

    InsanelyMac Protégé

  • Members
  • Pip
  • 5 posts

Just tested this kext on my U310 (with 8105E) and it work great.  

I did have to configure it manually tho.  Automatic did not work for me (it kept switching between connected and disconnected).
My settings were 
100baseTX
full duplex
standard (1500)

I've tested waking from sleep as well as unplugging and re-plugging the ethernet cable and using both methods, I was able to get an IP and internet access.



#37
Mieze

Mieze

    InsanelyMac Sage

  • Coders
  • 447 posts
  • Gender:Female
  • Location:Germany
  • Interests:Cats

Just tested this kext on my U310 (with 8105E) and it work great.  

I did have to configure it manually tho.  Automatic did not work for me (it kept switching between connected and disconnected).
My settings were 
100baseTX
full duplex
standard (1500)

I've tested waking from sleep as well as unplugging and re-plugging the ethernet cable and using both methods, I was able to get an IP and internet access.

 

Which chipset? Please see the kernel logs.

 

Mieze



#38
lisai9093

lisai9093

    InsanelyMac Protégé

  • Members
  • PipPip
  • 86 posts
  • Gender:Male

Just tested this kext on my U310 (with 8105E) and it work great.  

I did have to configure it manually tho.  Automatic did not work for me (it kept switching between connected and disconnected).
My settings were 
100baseTX
full duplex
standard (1500)

I've tested waking from sleep as well as unplugging and re-plugging the ethernet cable and using both methods, I was able to get an IP and internet access.

Can you upload ur DSDT? Just wanna check the ethernet part.



#39
ikkoku

ikkoku

    InsanelyMac Protégé

  • Members
  • Pip
  • 5 posts

Which chipset? Please see the kernel logs.

 

Mieze

 

do you mean this?

2/28/14 8:37:31.000 PM kernel[0]: Ethernet [RealtekRTL8100]: RTL8105E: (Chipset 12) at 0xffffff80dec3d000,  4:7d:7b:b8: 5:b8

Can you upload ur DSDT? Just wanna check the ethernet part.

 

how do I add attachments?



#40
lisai9093

lisai9093

    InsanelyMac Protégé

  • Members
  • PipPip
  • 86 posts
  • Gender:Male

do you mean this?

2/28/14 8:37:31.000 PM kernel[0]: Ethernet [RealtekRTL8100]: RTL8105E: (Chipset 12) at 0xffffff80dec3d000,  4:7d:7b:b8: 5:b8

 

how do I add attachments?

You can click "More Reply Option" at bottom right corner. Then attach your file. Thx in advance.







Also tagged with one or more of these keywords: Realtek, RTL8105, RTL8101, RTL8102, RTL8106, RTL8103, RTL8401, RTL8402, driver


1 user(s) are reading this topic

1 members, 0 guests, 0 anonymous users


© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy