Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 03/26/2018 in all areas

  1. As i said in the earlier posts, i have installed high sierra using English from the language chooser, but if the same usb made and didn’t formated, next time when I’ll install high sierra again, no language chooser will be showed, because macOS installer saves some data in the EFI partition of that usb drive, regardless clover! Sent from my iPhone using Tapatalk
    2 points
  2. 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 400 Series (since V2.5.1d1) 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 due to hardware bugs). 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, I219V 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 newer versions of macOS. 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. g. en0. Reboot. 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. Help - I'm getting kernel panics! Well, before you start complaining about bugs after you upgraded macOS and ask me to publish a driver update, you should first try to resolve the issue on your own by cleaning the system caches. As the driver uses macOS's private network driver interface, which is supposed to be used by Apple provided drivers only, you might run into problems after an OS update because the linker may fail to recognize that IONetworking.kext has been updated and that the driver needs to be linked against the new version (Apple provided drivers avoid this problem because they are always updated together with IONetworking.kext). As a result, the linking process produces garbage and the driver may call arbitrary code when trying to call functions from IONetworking.kext. This usually results in unpredicted behavior or a kernel panic. In order to recover from such a situation, you should clean the System Caches forcing the linker to recreate it's caches: Delete all the files in /System/Library/Caches and it's subdirectories but leave the directories and the symbolic links intact. This is very important! Reboot. Recreate the kernel cache. Reboot again. 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.5.0 (2019-10-15) Reworked interrupt throttling code and added new configuration parameters. 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: https://github.com/Mieze/IntelMausiEthernet There is also a prebuilt binary for 10.11 and above in the download section: http://www.insanelymac.com/forum/files/file/396-intelmausiethernet/ 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.
    1 point
  3. Update done! As always and as expected, everything perfect here on the two boys! Nvda Web Patcher did the job and Web 160 works fine here. I think Apple gave up giving us a fight
    1 point
  4. Done Beta 7all is good here Also no issue on Dell Opiplex 790 with GeForce GT 1030 Pascal GPU WebDrivers 161 patch Easy Web Drivers Patcher
    1 point
  5. Yes I do: Name: com.apple.driver.AirPort.Atheros40 Find: 83F837 Replace: 83F821 Comment: Atheros Locale Fix The credit for the patch goes to @Sherlocks and @Badruzeus
    1 point
  6. no...everytime panic i've changed sometime in bios, this is the new sendme i have problems with usb3 and i dont know if i need dsdt or not for PM http://www.terminalstrip.net/FABIO/Sendmenew.zip
    1 point
  7. @jin2k9 Thanks, I'll give the codec to the release. @junoir No, the Platforms13.xml was only for your own experiments with the AppleALC source. One last try: Trial_AppleALC.kext.zip Mic front in the switch with LineIn back blue Mic back separately Under OSX two inputs are already good. Important is the front mic.
    1 point
  8. Should work if there are several outputs with good configs.
    1 point
  9. Hello. Well, on High Sierra, no kext and workout any patch, it's just working. Only patch I use, it's on DSDT to display nvme as internal. And, my drive it's only for system, don't copy so large amount of data...
    1 point
  10. Yeah I will report back tomorrow. I have a Ryzen system and recovery on that is english. I downloaded high sierra on that from app store and used TINU software. It could be nvram i just need to find out how to reset nvram. Sent from my SM-N950F using Tapatalk
    1 point
  11. this issue could also be related to your nvram settings, so reset your nvram and try to boot without the nvram clover driver to see if it does pick up englesh or other languages
    1 point
  12. this is very strange, because tinu did not uses anything to force a specific language for the installer, maybe you have to check your clover options to make sure that into the gui settings the langue is not "it" and instead is your langue or it's blank
    1 point
  13. Front panel connector is defective, pin detect is not working; replace Windows, not relevant. Windows supports AC97, macOS does not; both support HD Audio Workaround is to split front panel green audio device from motherboard green
    1 point
  14. I think i tried that before but thanks a lot i will give a try and tell you
    1 point
  15. OK, like you expected there are now 2 line in inputs. now all inputs responds. rear line in blue connector and rear mic input pink responds on 1 of the line in inputs. the front mic connector now responds on the other line in input. auto switching works great just as before. in manual mode 11 all inputs and outputs are listed. I consider this as good as it can get, every output and input jack responds. why the 2 in the back uses on the same line input is probably self explainatory since my dump didnt have any rear mic for some reason. Anyways, thank you very much for adding the codec.
    1 point
  16. For cosmetic reasons only 1.) Open a terminal and use the following commands: cp /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/Resources/English.lproj/AppleSystemInfo.strings ~/Desktop/ sudo mv /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/Resources/English.lproj/AppleSystemInfo.strings /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/Resources/English.lproj/AppleSystemInfo.strings-Backup 2.) Open "AppleSystemInfo.strings" on your Desktop with TextWrangler and change <key>UnknownCPUKind</key> <string>Unknown</string> to what ever you want. In your case choose: <key>UnknownCPUKind</key> <string>Intel® Core™ i7-7820X</string> Save "AppleSystemInfo.strings" 3.) Run the following terminal commands: sudo codesign -f -s - ~/Desktop/AppleSystemInfo.strings sudo cp ~/Desktop/AppleSystemInfo.strings /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/Resources/English.lproj/ and reboot your system.
    1 point
  17. @amadeusex Thank for your help. I fixed the shutdown problem with clover configurator "shutdown" path. Actually, I fixed pm by follow the way how bilbo listed and finally put your dsdt file and it works. Thank for sharing your file. Glad I have the same cpus as you. @wham17wham Thank for your help. It did work. Another problem, I just find out a very annoying problem, I don't know is it my motherboard is going down. When I am downloading file from Internet the lan port or motherboard make some noise(especially down as high speed like 10MB/per sec, it would be more noise). I didn't realize that problem when I installed my pc with mac 10.11 in my workplace(a more noise environment), but now I moved my pc to my home. The noise is more visible. Anyone is same????? In this problem, I also find out one problem is that the IntelMausiEthernet.kext can't support two lan port even I used the dpci manager to check it can show two network controllers. I can only use the upper lan port. The bottom one can't use. so I replace it with Appleintele1000e.kext and it works. (I also dun know is it my own problem as well, just to mention what I experienced)
    1 point
  18. Hello @Mohamed Mohsen Elnahla, and welcome to InsanelyMac. Try use only this method: Backup your current files, and to a test.
    1 point
  19. For lag issue : You must have VoodooTSCSync.kex and edit "Info.plist" file Right-click with the mouse on the VoodooTSCSync.kex file and select "Show Packet Contents". Double-click with the mouse on /contents/ . After a right-click on the "Info.plist" file, select "Open with /Other". Select the TextEdit.app and edit the "Info.plist" file. Use the "find"-function of TextEdit.app and search for the term "IOCPUNumber" Note that the adequate IOCPUNumber for your particular Skylake-X processor is the number of its threads -1, by always keeping in mind that the number of it's threads is always 2x the number of it's cores. Thus in case of the 8 core i7-7820X, the IOCPUNumber is 15 (16 threads - 1). <key>IOCPUNumber</key> <integer>15</integer> Save and exit. After : You must put VoodooTSCSync.kex in EFI/Clover/Kext/other
    1 point
  20. Far from being done. But this is kinda what I have in mind for a dark theme. As I said, it's faaaar from being ready. There are plenty of things still needing tweaking. I'll let you guys know when I'm close to finish if you wanna take another look. Until then, here's a little preview.
    1 point
  21. If somebody with ESXi 6.5 issues wants to contact me, I'd be willing to work with them to see if I can find what is causing the problems. I've been using the vmkramdisk method for a year or so with no problems, but it had an issue with some specific hardware by what donk said previously. I have nearly the same hardware as the person who had been having the issues and was never able to duplicate the issue. Anyway, I don't want ESXi support gone, I may just maintain a fork with it still in it for adventurous types. I won't promise it won't break anything if you try it
    1 point
  22. Everything is good after updated
    1 point
  23. 10.12.5 (16F73) — Clean installation. Problem with disconnecting the monitor. Had to redo the «sambios» on a Mac Pro (Mid 2010). Everything is fine.
    0 points
×
×
  • Create New...