Contribute
Register

New Realtek Driver Development

Status
Not open for further replies.
Attention SandyBridge users... New Lnx2Mac RTL81xx available

Wow nice, wake works on my system! Although the kernel notifies "Wake reason: power-button (User)" in the console. Now i can say my board is fully supported :) Thanks Mieze!

Some logs:

Feb 23 14:06:40 kernel[0]: Ethernet [RealtekRTL8111]: PME# from D3 (cold) supported.
Feb 23 14:06:40 kernel[0]: Ethernet [RealtekRTL8111]: RTL8168E-VL/8111E-VL: (Chipset 16) at 0xffffff81cf966000, xx:xx...
Feb 23 14:06:46 kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 1-Gigabit, Full-duplex, flow-control
 
Attention SandyBridge users... New Lnx2Mac RTL81xx available

Hello VM,

thank you for figuring that out. Soon there will be no need to change sysctl.conf anymore. In your first post you send me the NIC's subsystem vendor ID and subsystem ID which uniquely identify the MSI Z77MA-G45's onboard NIC making it almost trivial to blacklist it in the driver so that it disables rx checksum offload for that board automatically.

I don't think that the NIC itself is broken because the RTL8111E-VL is one of the most frequently used onboard NIC on the market today and it works perfectly on my MSI B75MA-P45 with checksum offload. As an electronics engineer I rather think that those guys at MSI have messed up the board design or tried to save costs at the expend of reliability.

In a certain way you saved me twice. I was just one hair away from buying a MSI Z77MA-G45 for a development system. Imagine what would have happened in case I used that board as the main development platform for my driver. ;-)

Regards,

Mieze

Glad to help. Maybe it is a faulty revision on my board. Anyway because of your port now a lot of boards are supported. Working perfect under heavy load. Good job!

Best regards,
VM
 
Attention SandyBridge users... New Lnx2Mac RTL81xx available

Wake problem happened again:

syslog:
Feb 24 11:30:58 kernel[0]: Ethernet [RealtekRTL8111]: Resolving Tx deadlock.
[Level 5] [com.apple.message.domain com.apple.afpfs.sleepState] [com.apple.message.signature awake] [com.apple.message.success 1] [com.apple.message.value 1361705471] [Message AFPSleepWakeHandler: waking up]

ifconfig:
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=68<VLAN_HWTAGGING,TSO4,TSO6>
ether 8c:89:a5:de:13:3c
media: autoselect (<unknown type>)
status: inactive

System preferences: Not Connected (Cable Unplugged)

After restart all ok:

Feb 24 11:37:09 kernel[0]: Ethernet [RealtekRTL8111]: PME# from D3 (cold) supported.
Feb 24 11:37:09 kernel[0]: Ethernet [RealtekRTL8111]: RTL8168E-VL/8111E-VL: (Chipset 16) at 0xffffff81cf29d000, 8c:89:a5:de:13:3c
Feb 24 11:37:12 kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 1-Gigabit, Full-duplex, flow-control

en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=68<VLAN_HWTAGGING,TSO4,TSO6>
ether 8c:89:a5:de:13:3c
inet6 fe80::8e89:a5ff:fede:133c%en0 prefixlen 64 scopeid 0x4
inet 192.168.0.17 netmask 0xffffff00 broadcast 192.168.0.255
media: autoselect (1000baseT <full-duplex>)
status: active


Best regards,
VM
 
Attention SandyBridge users... New Lnx2Mac RTL81xx available

I don't experience any problems with the MSI Z77A-G45 rev1.0. I tested just five times in a row sleep/wake and had always a working connection in less than one second after wake. I will report if errors occur.

What bios are you using? I'm on the newest 2.9 and really no problems. Package losts are also ok. Haven't messed with apple_hwcksum_rx.
Router is a Fritz!Box 7390.

EDIT: Oh ok you talk about Z77->M<-A sorry... My chip is different I have subsystem-id: 0x7752


tcp:
30976 packets sent
3100 data packets (1743763 bytes)
9 data packets (5324 bytes) retransmitted
0 resends initiated by MTU discovery
22050 ack-only packets (18 delayed)
0 URG only packets
0 window probe packets
3547 window update packets
2273 control packets
0 data packets sent after flow control
46596 packets received
5017 acks (for 1739369 bytes)
795 duplicate acks
0 acks for unsent data
38102 packets (50505683 bytes) received in-sequence
24 completely duplicate packets (14949 bytes)
0 old duplicate packets
0 packets with some dup. data (0 bytes duped)
4147 out-of-order packets (6001239 bytes)
0 packets (0 bytes) of data after window
0 window probes
4 window update packets
69 packets received after close
0 bad resets
0 discarded for bad checksums
0 discarded for bad header offset fields
0 discarded because packet too short
1189 connection requests
0 connection accepts
0 bad connection attempts
0 listen queue overflows
1133 connections established (including accepts)
1206 connections closed (including 41 drops)
4 connections updated cached RTT on close
4 connections updated cached RTT variance on close
0 connections updated cached ssthresh on close
0 embryonic connections dropped
4905 segments updated rtt (of 4965 attempts)
22 retransmit timeouts
0 connections dropped by rexmit timeout
0 connections dropped after retransmitting FIN
0 persist timeouts
0 connections dropped by persist timeout
0 keepalive timeouts
0 keepalive probes sent
0 connections dropped by keepalive
1 correct ACK header prediction
35995 correct data packet header predictions
1 SACK recovery episode
1 segment rexmit in SACK recovery episodes
267 byte rexmits in SACK recovery episodes
71 SACK options (SACK blocks) received
4087 SACK options (SACK blocks) sent
0 SACK scoreboard overflow
udp:
1767 datagrams received
0 with incomplete header
0 with bad data length field
0 with bad checksum
34 dropped due to no socket
177 broadcast/multicast datagrams dropped due to no socket
1113 dropped due to full socket buffers
0 not for hashed pcb
443 delivered
1732 datagrams output
ip:
48489 total packets received
0 bad header checksums
0 with size smaller than minimum
0 with data size < data length
0 with ip length > max ip packet size
0 with header length < data size
0 with data length < header length
0 with bad options
0 with incorrect version number
0 fragments received
0 fragments dropped (dup or out of space)
0 fragments dropped after timeout
0 packets reassembled ok
48229 packets for this host
14 packets for unknown/unsupported protocol
0 packets forwarded (0 packets fast forwarded)
77 packets not forwardable
169 packets received for unknown multicast group
0 redirects sent
32960 packets sent from this host
0 packets sent with fabricated ip header
0 output packets dropped due to no bufs, etc.
14 output packets discarded due to no route
0 output datagrams fragmented
0 fragments created
0 datagrams that can't be fragmented
0 tunneling packets that can't find gif
7 datagrams with bad address in header
0 packets dropped due to no bufs for control data
 
Attention SandyBridge users... New Lnx2Mac RTL81xx available

Yes it's a mini-atx board. I have two machines with the same board bought from two different suppliers. I have the same behaviour on both.
Regardless this is a big improvement as I have a lot of backups daily and with lnx2mac driver I have experienced generic ip on the interface after 60-70GB of transfer.

Best regards,
VM
 
Attention SandyBridge users... New Lnx2Mac RTL81xx available

Why don't you disable onboard LAN and add a PCIe Ethernet adapter. Those cards with Realtek chip are dirt cheap. In case you don't trust Realtek anymore Intel's EXPI9301CTBLK only costs a few bucks more and it works with Apple's Intel82574L.kext. You'll only have to put the card's id into the driver's Info.plist.

Mieze

Yes if I'll get into more troubles with this one I'll change it.


Best regards,
VM
 
Status
Not open for further replies.
Back
Top