Jump to content

New Driver for Realtek RTL8111


Mieze
1,592 posts in this topic

Recommended Posts

Hah no no.

btsync only has a connection to the folder my other machine, it has nothing to sync, it does not use bandwitdth.

No problems here with btsync and the latest dev version of this driver.  I get my rated internet speed on speedtest.net with btsync running.

Link to comment
Share on other sites

Hah no no.

btsync only has a connection to the folder my other machine, it has nothing to sync, it does not use bandwitdth.

Obviously it does something because closing it resolves the issue. Use Wireshark to inspect your network traffic.

 

Mieze

Link to comment
Share on other sites

having trouble using the newest version on the computer with Realtek 8186E,

 

the osx can recgonize the NIC, but it doesn't work properly. it cannot get the ip address from the DHCP server. And it also cannot detect whether the wire is connected or not.

 

my computer is Acer V5-473g.

 

Thanks for all your contribution. It will be appreciate if you can solve this problem for me :) 

Link to comment
Share on other sites

I've just encountered my first issue with the dev6 driver.  I got home from running some errands and noticed my network connection was down.  I couldn't ping anything or open any web pages.  Ive been running this version since it was released and never had any issues.  Last night I installed 10.9.2 so maybe it's related?  I did have vmware fusion running with a CentOS 6.5 guest running a KVM guest.  That's why the promiscuous mode.

 

 

2014-02-28 3:02:12.000 PM kernel[0]: Ethernet [RealtekRTL8111]: Not enough descriptors. Stalling.
2014-02-28 3:02:12.000 PM kernel[0]: Ethernet [RealtekRTL8111]: Restart stalled queue!
2014-02-28 3:02:18.000 PM kernel[0]: Ethernet [RealtekRTL8111]: Not enough descriptors. Stalling.
2014-02-28 3:02:18.000 PM kernel[0]: Ethernet [RealtekRTL8111]: Restart stalled queue!
2014-02-28 3:02:18.000 PM kernel[0]: Ethernet [RealtekRTL8111]: Not enough descriptors. Stalling.
2014-02-28 4:31:14.000 PM kernel[0]: Ethernet [RealtekRTL8111]: Promiscuous mode disabled.
2014-02-28 4:37:55.000 PM kernel[0]: Ethernet [RealtekRTL8111]: PCI power management capabilities: 0xffc3.
2014-02-28 4:37:55.000 PM kernel[0]: Ethernet [RealtekRTL8111]: PME# from D3 (cold) supported.
2014-02-28 4:37:55.000 PM kernel[0]: Ethernet [RealtekRTL8111]: PCIe link capabilities: 0x00073c11, link control: 0x0000.
2014-02-28 4:37:55.000 PM kernel[0]: Ethernet [RealtekRTL8111]: EEE support enabled.
2014-02-28 4:37:55.000 PM kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv4 segmentation offload enabled.
2014-02-28 4:37:55.000 PM kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv6 checksum offload enabled.
2014-02-28 4:37:55.000 PM kernel[0]: Ethernet [RealtekRTL8111]: Using interrupt mitigate value 0xcf68.
2014-02-28 4:37:55.000 PM kernel[0]: Ethernet [RealtekRTL8111]: RTL8168D/8111D: (Chipset 9) at 0xffffff810f2ae000,  0:26:18:fe:70:ac
2014-02-28 4:37:55.000 PM kernel[0]: Ethernet [RealtekRTL8111]: MSI interrupt index: 1
2014-02-28 4:37:55.000 PM kernel[0]: Ethernet [RealtekRTL8111]: kIOEthernetWakeOnMagicPacket added to filters.
2014-02-28 4:37:55.000 PM kernel[0]: Ethernet [RealtekRTL8111]: Already in power state 1.
2014-02-28 4:37:56.000 PM kernel[0]: Ethernet [RealtekRTL8111]: No medium selected. Falling back to autonegotiation.
2014-02-28 4:37:59.000 PM kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 1-Gigabit, Full-duplex, No flow-control
Link to comment
Share on other sites

 

I've just encountered my first issue with the dev6 driver.  I got home from running some errands and noticed my network connection was down.  I couldn't ping anything or open any web pages.  Ive been running this version since it was released and never had any issues.  Last night I installed 10.9.2 so maybe it's related?  I did have vmware fusion running with a CentOS 6.5 guest running a KVM guest.  That's why the promiscuous mode.

 

Anyway, this is all I found in the logs:

2014-02-28 3:02:12.000 PM kernel[0]: Ethernet [RealtekRTL8111]: Not enough descriptors. Stalling.
2014-02-28 3:02:12.000 PM kernel[0]: Ethernet [RealtekRTL8111]: Restart stalled queue!
2014-02-28 3:02:18.000 PM kernel[0]: Ethernet [RealtekRTL8111]: Not enough descriptors. Stalling.
2014-02-28 3:02:18.000 PM kernel[0]: Ethernet [RealtekRTL8111]: Restart stalled queue!
2014-02-28 3:02:18.000 PM kernel[0]: Ethernet [RealtekRTL8111]: Not enough descriptors. Stalling.
2014-02-28 4:31:14.000 PM kernel[0]: Ethernet [RealtekRTL8111]: Promiscuous mode disabled.

 

No, I don't think it's got to do anything with 10.9.2 but with vmware. I remember that someone reported a similar problem last year with an earlier version of the driver using a virtual machine on his hack. It looks like the virtual machine is flooding the output queue with packets under certain conditions. Unfortunately I don't know if he managed to resolve the issue anyway.

 

The problem is that I don't use virtualization on my machines so that I can't run any tests myself. I can not rule out that there is a general problem with virtualization. On the other hand I doubt that you 2 are the only ones to run a VM on their hacks with this driver so that there should be more error reports in this thread in case of a systematic error. :unsure:

 

It might also be a configuration issue with the VM. Please check!

 

Mieze

Link to comment
Share on other sites

No, I don't think it's got to do anything with 10.9.2 but with vmware. I remember that someone reported a similar problem last year with an earlier version of the driver using a virtual machine on his hack. It looks like the virtual machine is flooding the output queue with packets under certain conditions. Unfortunately I don't know if he managed to resolve the issue anyway.

 

The problem is that I don't use virtualization on my machines so that I can't run any tests myself. I can not rule out that there is a general problem with virtualization. On the other hand I doubt that you 2 are the only ones to run a VM on their hacks with this driver so that there should be more error reports in this thread in case of a systematic error. :unsure:

 

It might also be a configuration issue with the VM. Please check!

 

Mieze

I've ran Windows 7 and Windows XP using Vmware Fusion and never experienced issues.  Lately I've been testing linux KVM (kernel virtulization module) inside of vmware fusion.  I'm using bridged networking in fusion and I am also using bridged networking in KVM (CenOS 6.5 host and FreeNAS guest).  I did have plex server running on my mac and I also had plex server running on the freenas kvm virtual machine.  That may have overloaded something some where.  

 

I'll keep an eye on things and see if it happens again.  My wife was using plex at the time which was streaming off of my hack/mac but I noticed there was also a ton of traffic going in and out of freenas plex.  

 

I'm not going to worry about it too much though.  I'm testing KVM until I get my server hardware then it'll run there.

 

Thank you.  You at least narrowed it down to the virtualization.

Link to comment
Share on other sites

Hello, 

I hope you can help me, I have an Acer V5 471 with a RTL8411 network card, 

but my laptop has no ethernet input, it uses an adapter (see photo below). 

51a2c6b216769_212824n.jpg

I'm using V1.2.0 development6 kext, and the network card is normally recognized, however it only detects if the internet cable is plugged when OS X starts with it plugged, if not, don't recognize.

 

Sorry about my english, i'm using Google Translator.

Link to comment
Share on other sites

Please send me your kernel logs.

 

Mieze

Kernel logs:

# BOOT WITH CABLE
Ethernet [RealtekRTL8111]: Warning: PCIe ASPM enabled.
Ethernet [RealtekRTL8111]: EEE support enabled.
Ethernet [RealtekRTL8111]: TCP/IPv4 segmentation offload enabled.
Ethernet [RealtekRTL8111]: TCP/IPv6 checksum offload enabled.
Ethernet [RealtekRTL8111]: Using interrupt mitigate value 0xcf68.
Ethernet [RealtekRTL8111]: RTL8411: (Chipset 19) at 0xffffff80e9a6d000, 20:6a:8a:f5:29:e2
Ethernet [RealtekRTL8111]: Link up on en0, 100-Megabit, Full-duplex, flow-control
#
# BOOT WITHOUT CABLE
Ethernet [RealtekRTL8111]: Warning: PCIe ASPM enabled.
Ethernet [RealtekRTL8111]: EEE support enabled.
Ethernet [RealtekRTL8111]: TCP/IPv4 segmentation offload enabled.
Ethernet [RealtekRTL8111]: TCP/IPv6 checksum offload enabled.
Ethernet [RealtekRTL8111]: Using interrupt mitigate value 0xcf68.
Ethernet [RealtekRTL8111]: RTL8411: (Chipset 19) at 0xffffff80e9ad6000, 20:6a:8a:f5:29:e2
#

If i plug the ethernet cable with the system running, console shows me nothing

Link to comment
Share on other sites

@thalesog: I guess you'll have to enable the interface manually when you boot without the cable. In Terminal type

sudo ifconfig en0 up

Mieze

Link to comment
Share on other sites

@thalesog: I guess you'll have to enable the interface manually when you boot without the cable. In Terminal type

sudo ifconfig en0 up

Mieze

 
I just tested and didn't work.
The interface is active, just don't recognise when the cable is plugged.
It is as it has disconnected.
Link to comment
Share on other sites

You can also try to unload the driver and reload it manually with kextunload/kextload. As I've never seen such a strange solution before I can not rule out that there is some kind of hardware device which prevents it from working after a boot without cable connected. This would be the worst case scenario making it impossible for me to resolve it.

 

Mieze

Link to comment
Share on other sites

You can also try to unload the driver and reload it manually with kextunload/kextload. As I've never seen such a strange solution before I can not role out that there is some kind of hardware device which prevents it from working after a boot without cable connected. This would be the worst case scenario making it impossible for me to resolve it.

 

Mieze

 

when i try to unload the kext it gives me kernel panic :(

there isn't another solution?

Link to comment
Share on other sites

Unfortunately no, because they must have built something unusual and I have no idea what it is.  :(

 

Mieze

 

I noticed that when booting with the cable plugged the id changes:

# BOOT WITH CABLE
Ethernet [RealtekRTL8111]: RTL8411: (Chipset 19) at 0xffffff80e9"a6d"000, 20:6a:8a:f5:29:e2
# BOOT WITHOUT CABLE
Ethernet [RealtekRTL8111]: RTL8411: (Chipset 19) at 0xffffff80e9"ad6"000, 20:6a:8a:f5:29:e2

(a6d to ad6)

Could be something related to this ID?

Link to comment
Share on other sites

 

I noticed that when booting with the cable plugged the id changes:

# BOOT WITH CABLE
Ethernet [RealtekRTL8111]: RTL8411: (Chipset 19) at 0xffffff80e9"a6d"000, 20:6a:8a:f5:29:e2
# BOOT WITHOUT CABLE
Ethernet [RealtekRTL8111]: RTL8411: (Chipset 19) at 0xffffff80e9"ad6"000, 20:6a:8a:f5:29:e2

(a6d to ad6)

Could be something related to this ID?

 

It's not an ID, it's the base address that gets assigned to the device by the BIOS and it has no influence on the chip's function. It could be located anywhere in the 64bit address space as long as the address is unique.

 

Mieze

Link to comment
Share on other sites

  • 5 weeks later...

Hi

 

I have two network adaptors, the internal board one, and then a PCI-e adaptor. This driver will only allow one to be run at a time. I was using bios 1.7 with a MSI X79A-GD45, but when I upgraded to 2.7, which has UEFI drivers now in the bios, the realtek 2.06 drivers only allow one driver. If I add this driver, It allows me to see the second driver, but then the apple network control panel shows the network alternating between "no cable" status and "no address" status. Both interfaces are needed. Even when I only load this driver but not the realtek 2.06, it alternates between the "no cable" status and "no address" status.

 

Update: Just tried the driver again. It's showing the mac address as FF FF FF FF FF FF etc...

 

Any thoughts?

 

MSI X79A-GD45 bios 7735v27

i7-3820

16gb ram

nVidia 520 gt

10.8.4 OS

Link to comment
Share on other sites

Please report back with your kernel logs, an IOReg dump (use version 2.1 of IORegExplorer because later versions produce corrupted output files) and the output of "ifconfig -a -v" as well as "kextstat".

 

By the way: Which version of the driver do you use?

 

Mieze

Edited by Mieze
Link to comment
Share on other sites

×
×
  • Create New...