Hi All, I have written a driver based on the original NVidia code and the framework from the Forcedeth drivers that should work on the Marvell 88E1116 controller. It might work for other nic's in the same family as well but the driver has been specificly written just to support the 88E1116. The driver hasn't been tested yet so I expect some bugs. Right now it is not possible to change the MTU size (default 1500) or use Jumbo packets.

Another limitation is that driver will always initialize using auto negotiation. I tested the driver on the following platform: Mainboard: EVGA SLI 680I Controller: MCP55, Marvell 88E1116 Ethernet Controller Device ID: 0x0373 OSx86 version: Skunk2 Intake Manifold Install K20z3. 10.4.11, kernel 8.10.1 HOW TO INSTALL: - Place the kext file on your desktop - Start 'Terminal' and type the following commands: - 'sudo -s' - Type you password.

- 'cp -R ~/desktop/nForceEthernetController.kext /system/library/extensions/' - 'chmod -R 755 /system/library/extensions/nForceEthernetController.kext - 'chown -R root:wheel /system/library/extensions/nForceEthernetController.kext' - 'rm -f /system/library/extensions.*' - 'diskutil repairpermissions /' - 'exit' - Close 'Terminal' - Shutdown the computer and take the power cord off ( IMPORTANT!) - Wait 30 secs. And turn it back on (plug the power cord back in first ) Hopefully it will come back up with your ethernet controller working! IMPORTANT: This goes without saying but I take no responsibility in any way shape or form if something bad happens to your computer or other caused by this driver.

I wrote this driver in my free time and because I don't have a lot of it I won't be able to make changes or updates on a regular basis so if it doesn't work for you, please be patient. Let me know if you had any success! Cheers, Mike.

Before I forget, thanks to the guys how worked on the forcedeth driver, using their framework made things a lot easier! EDIT: This driver will only work stable with Mac OS X 10.4 (Tiger). A driver for Leopard is currently being worked on. NOTE: When you still experiencing problems, turn the computer off, unhook the power cord for about 30secs. And bring in back up (I know it sounds. Strange.) (For some reason the MAC address is 'locked', this should be solved in a new release). It looks like its ALMOST working for me.

Marvell products in these types of equipment or applications. With respect to the products described herein, the user or recipient. This package supports the following driver models:Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller Marvell Yukon 88E8021 PCI-X IPMI Gigabit. Oct 04, 2011 Hi All, I have written a driver based on the original NVidia code and the framework from the Forcedeth drivers that should work on the Marvell 88E1116 controller.

It says both of my ethernet ports have the cable connected (though only one does) and configuring it manually makes it seem like it should connect (green light and all) but no internet. If you have any ideas let me know - is it possible I need to change a plist somewhere in that package I downloaded with specific device IDs or something?

(How would I find my device IDs anyways?) edit: gah, I am on leopard and you're not. I wonder if that makes a difference. It looks like its ALMOST working for me. It says both of my ethernet ports have the cable connected (though only one does) and configuring it manually makes it seem like it should connect (green light and all) but no internet.

If you have any ideas let me know - is it possible I need to change a plist somewhere in that package I downloaded with specific device IDs or something? (How would I find my device IDs anyways?) edit: gah, I am on leopard and you're not. I wonder if that makes a difference. I think you are right, I didn't test in on Leopard, it would be nice if we can get it to work with it though. The fact that it reports that both your ports have a cable connected should be easy to solve. (linkstatus is being reported incorrectly (lazy programming on my side).

Can you let me know if you get a proper MAC and IP address? (no APIPA: 169.254.xxx.xxx), or maybe no IP at all. And in 'terminal' can you type 'ifconfig' and tell me what it reports for media, MAC and IP please.

To figure out your device ID for your phy, you can do the following in Windows Vista (your sig. Says you are running Vista as well): - Go to your device manager (Start->right click 'Computer'->Properties->Device Manager - Click the plus sign next to 'Network adapters' - Right click your networking controller - Click 'Properties' - Click the 'Details' tab - In the 'Property' dropdown box select 'Hardware IDs' - Vendor ID should look like: 'VEN_xxxx' and your hardware ID: DEV_xxxx - If you hardware ID is 0x0373 you don't have to edit the info.plist - If it different then please let me know. When using DHCP I get a 169.254.xxx.xxx IP address, but I wasn't really expecting DHCP to work. When I go in and give it a manual IP of 192.168.1.105, subnet mask of 255.255.255. Spin It Again 2 5 Keygen Crack. 0, router of 192.168.1.1 and the proper DNS servers according to my routers configuration (checked from another computer on my network) it SEEMS to connect. Once I even saw a network printer of mine show up as a network thing in my finder sidebar (it does for all computers as my network as a generic Blue-Screen PC Icon) but that has since gone away.