- Free Download ECS 945GCT-M (V1.0) Realtek LAN Driver 6.87 (Network Card). - Integrated Intel Graphics Media Accelerator 950 ( GMA950 ) - Max Dynamic Video Memory up to 224MB(System Memory greater than or equal to 512MB). - 2 x USB 2.0 headers support additional 4 USB 2.0 Ports - 1 x Clear CMOS header.
- Secure the metal bracket of the intel 945gct-m motherboard to the system case with a screw. Sign up to get insider deals first, exclusive promotions and more delivered to your inbox each week. Table Of Contents Integrated Peripherals The total memory capacity is 2 GB.
Much to my surprise I got a PM from another user with this rickety old board that wants to get it up and running. This won't be an extensive guide cause quite honestly- there's just not much to it especially if you already had Leo or SL running on it before (which means you've already tweaked the bios)- Assuming you've done that- here was my vague remembrance of what was done.
Note: I am not using the on board video- rather an old GF 6600 which I had pretty much zero confidence would come up and work (I was wrong). The proc used here is a Intel E2200 (not a true core 2- but gets the job done). Make unibeast usb stick and follow tony's directions throughout the Lion install.
Drivers; Audio and Multimedia; ECS 945GCT-M(V2.0) Audio Driver 9.1.0.1014. IDT High Definition Audio Driver for the ECS 945GCT-M(V2.0) motherboard which comes with 945GC and ICH7 chipsets.
Install mbeast (I used 4.0.3 which has since been upgraded)- I used the options for easybeast, latest voodoo for sound, - I did not touch network stuff at this time as it was already working after first boot. Video resolution was stuck at 1024x768.
I did not install anything for vid nor a custom dsdt as I couldn't find one. After boot- Vid came up in full 1080 and tested qe/ci w/ chess and widgets ripple. Still no sound, and now network was gone. Ran MB again and chose the realtek nic drivers, and went back to voodoo 0.2.2.
Rebooted again w/ sound, 1080 res, and nic working. I haven't messed with sleep, but I've read it can be achieved with some jumper settings on the motherboard. I don't care about that as this machine runs 24/7 w/ only monitor and hd sleep enabled.
Thank you UB! Glad to hear of your success. One thing to watch out for- let me know if you see intermittent internet drops. It hasn't happened that often but a couple of times when using google chrome the internet connection (and possibly overall network/lan) just drops for a minute or two.
Then it comes back fine w/o rebooting or anything. It hasn't happened nearly enough to be considered a major problem but it's a little concerning. If anyone else knows anything about this from other builds please chime in. Maybe it's realtek related, maybe it's just Lion.
This project is dedicated to the memory of Mausi, the cat I loved more than anybody else. A few days before Christmas I started my latest project, a new driver for recent Intel onboard LAN controllers.
My intention was not to replace hnak's AppleIntelE1000e.kext completely but to deliver best performance and stability on recent hardware. That's why I dropped support for a number of older NICs. Currently the driver supports: 5 Series. 82578LM.
82578LC. 82578DM. 82578DC 6 and 7 Series. 82579LM. 82579V 8 and 9 Series.
I217LM. I217V.
I218LM. I218V. I218LM2. I218V2. I218LM3 100 Series (since V2.1.0d0).
I219LM. I219V 200 Series (since V2.3.0d0). I219LM. I219V 300 Series (since V2.4.0d0). I219LM. I219V Key Features of the Driver.
Support for multisegment packets relieving the network stack of unnecessary copy operations when assembling packets for transmission. No-copy receive and transmit.
Only small packets are copied on reception because creating a copy is more efficient than allocating a new buffer. TCP, UDP and IPv4 checksum offload (receive and transmit). Support for TCP/IPv6 and UDP/IPv6 checksum offload. Makes use of the chip's TCP Segmentation Offload (TSO) feature with IPv4 and IPv6 in order to reduce CPU load while sending large amounts of data (disabled).
Fully optimized for Sierra (64bit architecture) but should work with older 64bit versions of macOS too, provided you build from source with the appropriate SDK for the target OS. Support for Energy Efficient Ethernet (EEE). VLAN support is implemented but untested as I have no need for it. The driver is published under GPLv2. Current Status. The driver has been tested successfully with I217V, I218V and 82579V under 10.9.5 and above.
The attached archive includes source code as well as a prebuilt binary (debug version) for Mavericks and Yosemite. Known Issues. There seem to be problems while using VMware with version 1.x.x of the driver. In case you are affected use version 2.0.0 or newer. FAQ. Could you add support of for.? Well, you are probably asking me to add support for one of the older NICs like the 82571/2/3/4L or 82583 and the answer will be no as I dropped support for these chips intentionally.
They are broken and I lost more than 2 weeks trying to make it work on the 82574L without success. I was asked to add support for I210, I211 and I350 but as these chips have a completely different architecture, which isn't supported by the underlying Linux driver, this is impossible, sorry.
Does it work with Snow Leopard or 32 bit kernels? No and I have no plans to make a version for 32 bit kernels or anything older than Lion. WoL from S5 doesn't work with this driver but under Windows it's working. Is this a driver bug? No it isn't, the driver is working as it should because OS X doesn't support WoL from S5. Installation. Goto /S/L/E and delete AppleIntelE1000e.kext.
Recreate the kernel cache. Open System Preferences and delete the corresponding network interface, e. Install the new driver and recreate the kernel cache.
I recommend to use Kext Wizard or a similar utility for the installation. Reboot. Open System Preferences again, select Network and check if the new network interface has been created automatically or create it manually now. Configure the interface. Troubleshooting. Make sure you have followed the installation instructions especially when you have issues with certain domains while the others are working fine.
Use the debug version to collect log data when trying to track down problems. The kernel log messages can be retrieved with 'grep kernel /var/log/system.log' in Terminal. Starting from Sierra use ' log show -predicate 'processID 0' -debug' in order to retrieve kernel logs. Include the log data when asking for support or giving feedback. I'm an engineer, not a clairvoyant. Don't copy and paste large amounts of log data to your post. Create an archive with the log data and attach it to your post.
In case you don't want to make your log data publicly accessible, contact me via PM and I will provide you a mail address to send it directly to me. Check your BIOS settings. You might want to disable Network Boot and the UEFI Network Stack as these can interfere with the driver. Double check that you have removed any AppleIntelE1000e.kext from your system because it could prevent the driver from working properly. Delete the following files:.
/Library/Preferences/SystemConfiguration/NetworkInterfaces.plist. /Library/Preferences/SystemConfiguration/preferences.plist. Verify your bootloader configuration, in particular the kernel flags. Avoid using npci=0x2000 or npci=0x3000. In Terminal run netstat -s in order to display network statistics.
Carefully examine the data for any unusual activity like a high number of packets with bad IP header checksums, etc. In case auto-configuration of the link layer connection doesn't work it might be necessary to select the medium manually in System Preferences under Network for the interface.
Use Wireshark to create a packet dump in order to collect diagnostic information. Keep in mind that there are many manufacturers of network equipment. Although Ethernet is an IEEE standard, different implementations may show different behavior causing incompatibilities. In case you are having trouble try a different switch or a different cable. Changelog.
Version 2.4.0 (2018-04-14). Added support for 300 series versions of I219LM and I219V. Updated underlying Linux source code. Version 2.3.0 (2017-06-20).
Added support for 200 series versions of I219LM and I219V. Version 2.2.0 (2016-09-23). Disabled TSO to work around a hardware bug.
Version 2.1.0 (2016-05-24). Added support for I219LM and I219V. Version 2.0.0 (2015-04-22). First official release which is identical to 2.0.0d2 (only the version number has been changed). Version 2.0.0d2 (2015-04-04). Changed the tx descriptor write back policy for 82579, I217 and I218 to prevent random tx deadlocks.
Version 2.0.0d1 (2015-03-14). Uses Apple's private driver interface introduced with 10.8. Supports packet scheduling with QFQ. Solves the VMware issue. Version 1.0.0d6 (2015-03-04).
Reworked TSO6 support to avoid problems with VMware. Wake-on-LAN now working. Version 1.0.0d5 (2015-02-27). Reworked TSO4 support to eliminate the bug of 1.0.0d4. Added some debug code in order to collect information about the VMware related issue. Version 1.0.0d4 (2015-02-25).
Set total length field of the IP-header to zero for TSO4 operations. Report EEE activation state in kernel log message when the link has been established. Version 1.0.0d3 (2015-02-11).
Reworked media selection and EEE support (EEE is now activated when both link partners support it. It can be disabled selecting the medium manually). Duplex setting for 10/100 MBit connections is now reported correctly. The number of tx descriptors has been reduced from 2048 to 1024.
The code has been cleaned up and obsolete files have been removed. Version 1.0.0d2 (2015-01-31). First development release. Getting the Driver. The source code can be found on GitHub:.
There is also a prebuilt binary for 10.11 and above in the download section: Build from Source for 10.8. Register as a developer on Apple's developer website.
A free membership is sufficient. Download a copy of Xcode 5.1.1 and install it on your machine. In the project select 10.8 as the 'Base SDK' and the 'Deployment Target'.
Call 'Archive' from the menu 'Product' and save the built driver. Credits. Thanks to RehabMan and Yung Raj for running tests and pointing me in the right direction while I was trying to fix TSO. Special thanks to Yung Raj for motivating me when I was about to give up. Edited April 16 by Mieze. Use iperf for basic speed tests. For real world tests you could use Blackmagic Disk Speed Test over an AFP or SMB connection to a fileserver.
Mieze Thanks for the tip regarding Blackmagic Disk Speed Test. I was just copying a 700gb folder over to a linux box via AFP, starting a stopwatch and looking at the 'about 2 hours' as a guide, then trying to catch it at the end to stop the stopwatch. Granted I was also trying to test stability of large transfers at the same time, but I do I feel rather silly now. So far after 12 hours of the driver being in place, and a complete/new time machine backup to test it out a bit more, its still solid. Things are looking good. Thanks for your incredible work Meize. Also understood about the jumbo frames.
I think its more psychological on my end more than anything, seeing almost all my equipment/switches etc support jumbo frames, it feels a little sad when the old hackintoshes are left out. But if its a major bit of work to implement, then its totally understandable - I'm just glad to have a driver for the i217V thats this stable so far. Hi, Please help me to enable and use hd 3000 with Mojave. I know that I can install some.bundle or.kext files to make it can be enable.
But it always show an err msg up. 'IOConsoleUsers gIOScreenLockState 3.' I have tried to reinstall the refi drivers and kexts. But still not solved this issue. I will upload my EFI partition as a zip file below (Google Drive, Because It's bigger than 10 mb). Thanks for helping. For the details about my hardwares, please see my 'About Me' page-Brian's Budget Hackintosh.
Cheers, Brian. So apple has presented a new and updated mac mini a few days ago, and the great news seems to be the use of desktop processors in it, in fact, all the specs seems to match a typical desktop socket 1151 v2 coffeelake system without a dedicated gpu, so i am wondering if the smbios of this machine could be our new smbios of preference for coffeelake desktop machines.
So i have created this new topic to discuss about it. Of course we will have to wait to do tests using the first public version of mac os which integrates this smbios, because when every new mac is released it's smbios is available initialy just in a purpose made mac os build and then it's added for all the os builds in the following releases. So what do you think about the possibility of using this new smbios for desktop coffeelake machines instead of the imac 18.3/18.2 ones?
My Intel HD 630 isn’t functioning on MacOS Mojave (or High Sierra) It only shows 5MB of VRAM. This is bothering me for a long time now: Why does Apple deliberately disables the the RX4xx, RX5xx capabilities to hardware encode HEVC and is using Intel Quicksync instead? Is it to make the iMacPro look better than it is?
I stumbled over a thread at tony-mac where people are going a totally different road for Radeon graphics. Instead of hassling around with getting Quicksync to work, they proposed to activate the AMD hardware renderer for Polaris GPU's. I tried it out and it works.somewhat I used a dummy kext from that tomato thread and edited it, so that it enables the AMDU7V4 IOGVACodec like on Vega cards, switched to iMacPro1,1 SMBIOS from iMac18,3, disabled the IGPU and the results were astonishing: My 3:34min 4k50p film was rendered by FCP with HEVC in 2:34 minutes. Nearly half the time than with Quicksync! With the iMac18 SMBIOS and the 'help' of Intel Quicksync it took FCP 4:41 minutes to get it done! The problem is: As soon as the 'wrong' IOGVACodec is enabled H.264 encoding leads to Mojave crashing at once (be it FCP, QuickTime or Videoproc). Watching H264 material is fine, though.
Intel 945gct-m 2.0 Drivers For Mac
If anyone has any idea how to handle this, I would be very grateful. I would even accept Mojave using software encoding for H264 if I could keep this amazing speeds on HEVC! BTW: Without IGPU on iMacPro1,1 SMBIOS no problem with DRM or iTunes, no need for Whatevergreen or Shiki. That is a bonus Ellesmere.kext.zip. Due to Apple's QA, an update to Mojave will come when Mojave reaches its second 2nd point release (aka.2) Introduction The H370 chipset powers 8th generation Intel Core-i CPUs. Even though the name H370 rings comparable to Z370, the H370 is based on newer silicon.
This it also requires some new approaches compared to the Z370. An example would be on-die USB 3.1 and WiFi support.