291 replies to this topic

[Vlad]

does anyone have problems with pppoe connection when using this kext?

can you post the sourcecode please ? i'm interested in contributing to this kext development cause i am affected by it's functionality

[hnak]

 Vlad, on 13 April 2012 - 08:57 AM, said:

does anyone have problems with pppoe connection when using this kext?

can you post the sourcecode please ? i'm interested in contributing to this kext development cause i am affected by it's functionality

I have just uploaded 1.10.6.
Have you read the readme.txt ? The code is availabe at osx86drivers.sourceforge.net from the beginning.
PPPoE does nothing special and there is no API/framework entries for it.

[xbb]

 hnak, on 14 April 2012 - 01:53 PM, said:

I have just uploaded 1.10.6.
Have you read the readme.txt ? The code is availabe at osx86drivers.sourceforge.net from the beginning.
PPPoE does nothing special and there is no API/framework entries for it.

Thanks, I'm going to test if jumbo frames work again later

[hnak]

They released 1.11.3, so did I.

[brycv]

A few of us are seeing some errors with the latest 1.11.3 but they don't appear to be there on the previous version. The errors are all with 82579V Ethernet on Z68 and Z77 systems. This is the output in kernel.log. Apparently this prevents sleep for some. I didn't notice any problems until I checked my kernel.log.


4/25/12 8:23:02.000 AM kernel: AppleIntelE1000e(Err): Detected Hardware Unit Hang:
4/25/12 8:23:02.000 AM kernel: TDH                  <b0>
4/25/12 8:23:02.000 AM kernel: TDT                  <b0>
4/25/12 8:23:02.000 AM kernel: next_to_use          <b0>
4/25/12 8:23:02.000 AM kernel: next_to_clean        <b0>
4/25/12 8:23:02.000 AM kernel: buffer_info[next_to_clean]:
4/25/12 8:23:02.000 AM kernel: time_stamp           <0>
4/25/12 8:23:02.000 AM kernel: next_to_watch        <b0>
4/25/12 8:23:02.000 AM kernel: next_to_watch.status <0>
4/25/12 8:23:02.000 AM kernel: MAC Status             <40080083>
4/25/12 8:23:02.000 AM kernel: PHY Status             <796d>
4/25/12 8:23:02.000 AM kernel: PHY 1000BASE-T Status  <3800>
4/25/12 8:23:02.000 AM kernel: PHY Extended Status    <3000>
4/25/12 8:23:02.000 AM kernel: PCI Status             <10>

[Klonkrieger2]

same entries here with a 82579LM. Sleep is working anyway

[hnak]

The driver hangs correctly when it is about to stop. So the orignial code to report hang checks if it is in terminating process. I just removed the check as I thought it would never bother users. It seems untrue for sleep/resume users.
Though it is a normal operation, I will add some check in the next version.

[brycv]

 hnak, on 26 April 2012 - 12:08 AM, said:

The driver hangs correctly when it is about to stop. So the orignial code to report hang checks if it is in terminating process. I just removed the check as I thought it would never bother users. It seems untrue for sleep/resume users.
Though it is a normal operation, I will add some check in the next version.

Thank you. I appreciate it.

[ayuayu129]

Hi hnak
I have 0x1503 device on P8Z68-V/GEN3.
As Cipolippo said in this topic, the driver seems not to work correctly on this board.

First I connected LAN to Intel port, IP was not assigned (yellow icon in Network PrefPane).
Then I set it "Manually" or "Using DHCP with manual address", the icon is turned green, but no internet connection.
Browser and other applications show that request is timed out.
I tried all version supporting 10.7, and got same result.
Could you tell me how to solve this?

[hethwt]

 brycv, on 25 April 2012 - 03:24 PM, said:

A few of us are seeing some errors with the latest 1.11.3 but they don't appear to be there on the previous version. The errors are all with 82579V Ethernet on Z68 and Z77 systems. This is the output in kernel.log. Apparently this prevents sleep for some. I didn't notice any problems until I checked my kernel.log.


4/25/12 8:23:02.000 AM kernel: AppleIntelE1000e(Err): Detected Hardware Unit Hang:
4/25/12 8:23:02.000 AM kernel: TDH   <b0>
4/25/12 8:23:02.000 AM kernel: TDT   <b0>
4/25/12 8:23:02.000 AM kernel: next_to_use   <b0>
4/25/12 8:23:02.000 AM kernel: next_to_clean <b0>
4/25/12 8:23:02.000 AM kernel: buffer_info[next_to_clean]:
4/25/12 8:23:02.000 AM kernel: time_stamp    <0>
4/25/12 8:23:02.000 AM kernel: next_to_watch <b0>
4/25/12 8:23:02.000 AM kernel: next_to_watch.status <0>
4/25/12 8:23:02.000 AM kernel: MAC Status <40080083>
4/25/12 8:23:02.000 AM kernel: PHY Status <796d>
4/25/12 8:23:02.000 AM kernel: PHY 1000BASE-T Status  <3800>
4/25/12 8:23:02.000 AM kernel: PHY Extended Status <3000>
4/25/12 8:23:02.000 AM kernel: PCI Status <10>

I'm getting the same, but I can't sleep either. I don't know if something else is going on or not, but the only thing I changed was off of the realtek nic to the intel PCI-E nic.

[hnak]

 hethwt, on 28 April 2012 - 01:00 PM, said:

I'm getting the same, but I can't sleep either. I don't know if something else is going on or not, but the only thing I changed was off of the realtek nic to the intel PCI-E nic.

Does sleep work with previous versions - for example, 1.10.6 ?

 ayuayu129, on 28 April 2012 - 10:50 AM, said:

Hi hnak
I have 0x1503 device on P8Z68-V/GEN3.
As Cipolippo said in this topic, the driver seems not to work correctly on this board.

First I connected LAN to Intel port, IP was not assigned (yellow icon in Network PrefPane).
Then I set it "Manually" or "Using DHCP with manual address", the icon is turned green, but no internet connection.
Browser and other applications show that request is timed out.
I tried all version supporting 10.7, and got same result.
Could you tell me how to solve this?

Unfortunately, I cannot fix a problem which is not reproducible with my own hardware. I hope someone who has the same problem as well as programming skill fix it...

[brycv]

I can confirm that with 1.10.6 and the Intel 82579V chip on both the Gigabyte G1.Sniper M3 and Asus Sabertooth Z77 manual sleep works fine. Energy Saver sleep is not working on the G1.Sniper M3 but I don't think that is related.

[hnak]

I have uploaded a version which just suppresses TxHung warnings.

[brycv]

Thanks hnak. The updated version works perfectly and I have confirmation from another user that it works 100% with sleep and all. Thank you!

[hnak]

They released 2.0.0 on e1000.sourceforge.net and I incorporated the changes.
I also enabled VLAN.

[Ikky Phoenix]

Hello,

I can't get this network card to work. Can someone help??

kernel.log:

May 24 16:29:46 MacBook-Pro-de-Luciano-3 kernel[0]: AppleIntelE1000e(Info): changing MTU from 0 to 1500
May 24 16:29:46 MacBook-Pro-de-Luciano-3 kernel[0]: AppleIntelE1000e(Err): The NVM Checksum Is Not Valid


Device ID: 8086;Intel Corporation;104b;82566DC Gigabit Network Connection;Network controller;Ethernet controller


Thanks

[hnak]

 Ikky Phoenix, on 24 May 2012 - 07:39 PM, said:

May 24 16:29:46 MacBook-Pro-de-Luciano-3 kernel[0]: AppleIntelE1000e(Err): The NVM Checksum Is Not Valid

The message indicates that your NVM (non-volatile-memory on board or BIOS) is corrupted. You might need a vendor's tool to fix it.

[brycv]

 hnak, on 19 May 2012 - 02:08 PM, said:

They released 2.0.0 on e1000.sourceforge.net and I incorporated the changes.
I also enabled VLAN.

Thanks so much! That was the only real lack in the previous versions of the driver. I can confirm that VLANs work great with VMware Fusion and almost ten bridged VMs to VLANs. Now I don't have to add another natively supported NIC or stick with only 82574L NICs.

[Ikky Phoenix]

 hnak, on 25 May 2012 - 01:32 AM, said:

The message indicates that your NVM (non-volatile-memory on board or BIOS) is corrupted. You might need a vendor's tool to fix it.

I fixed it with Intel® Ethernet Connections Boot Utility.
Download the software, create a bootable DOS usb stick and put bootutil utility in it.
Execute: bootutil -nic=1 -defcfg

It needs PXE boot on Bios to be enable.

Hope solve someone problens too...

Thanks hnak

[howmany]

Is this kext supposed to provide WoL functionality?  I have an Intel 82579LM NIC on an Optiplex 990, running 10.7.4.  In the energy pref I do have the option to "wake for ethernet network access," and I have it set in BIOS too.  But I can't get the system to wake with a magic packet.  Any thoughts?