Jump to content

nawcom

Retired Developers
  • Content Count

    265
  • Joined

  • Last visited

  • Days Won

    3

Reputation Activity

  1. Like
    nawcom got a reaction from fantomas in Just a small introduction   
    Heh agreed, he definitely has a major misunderstanding there. InsanelyMac predates TM by what, 5 years?
  2. Like
    nawcom got a reaction from MaLd0n in Dell Precision 5520   
    According to that guide it's referring to the XPS 9550 which uses a Skylake processor. 7820HQ is a Kaby Lake processor which isn't even supported in OS X until Apple releases a Mac that uses a Kaby Lake processor. Here's a clover config.plist which uses a Skylake CPUID to skip the kernel CPUID check and adds the possibility of getting graphics working https://github.com/RehabMan/OS-X-Clover-Laptop-Config/blob/master/config_HD620.plist
     
    According to posts on another forum that I shall not mention, someone got laptop HD620 working with this config.plist plus FakePCIID.kext and FakePCIID_Intel_HD_Graphics.kext from the latest here: https://bitbucket.org/RehabMan/os-x-fake-pci-id/downloads
     
    Looks like the difference between Skylake and Kaby Lake graphics isn't as much as expected. Any issues you run into in between getting it booting and getting graphics working is something I can't help with since I haven't dealt with a Kaby Lake laptop myself. Now also note that I'm assuming that you have Nvidia Optimus enabled by default on that laptop. If it's something you can turn off in the BIOS then as a result you will use your Quadro M1200 will be your primary graphics card which is apparently based on the Maxwell GM107 chip which Nvidia's Web Drivers support instead of the newer Pascal series, then you could provide support for that instead of Kaby Lake graphics.
     
    Like I said, I'm totally unfamiliar with any of this but this is the information I could find regarding it.
     
    Also something to note is your wireless ac/bt card that your laptop comes with is Intel which isn't supported (Intel 8265 apparently). You'll have to replace it with a supported Broadcom one in order for it to work in OS X.
  3. Like
    nawcom reacted to nvflash in High Sierra success on some ancient hardware.   
    Dell Vostro 220( ICH10 ) with 4 GB Ram and a T7200 core 2 duo, PCI-E Apple 802.11ac and Bluetooth, Bluetooth sound via Vizio 5.1 sound system.
     
    Everything works, but graphics card does not wake from sleep. 
     
     


     
    nVidia MCP79A( GF9300 ) Core 2 Quad Q9550 6 GB Ram, Apple original FW400 iSight, USB Wifi, HDMI Audio. Everything seems to work, had one random shutdown, wake from sleep works for the first time under the macOS, been running every OS from 10.6.8 on this Motherboard and wake from sleep never worked. Custom DSDT I edited years ago to try and get sleep to work proper, Custom SSDT for HDMI Audio.
  4. Like
    nawcom got a reaction from chris1111 in Installing MAC OS on AMD A6 6400k. Currently i am a WINDOWS 10 user.   
    Looking at the CPU specs, it does support SSE4.1 instructions which is needed to run 10.12 Sierra.
     
    You can get premade image for AMD CPUs where you can use Transmac in Windows to image it onto USB: https://forum.amd-osx.com/bbdownloads/sierra.html
     
    If you want to or need to create the USB install media yourself, you'll need access to an existing computer or virtual machine running OS X. If that is your case, then you can take a look at this: http://www.insanelymac.com/forum/topic/310098-el-capitan-install-preparation/ making Sierra install media is more or less the same, you just need to use the provided Extra folder and USB fixes for Sierra that you can get from amd-osx.com.
     
    With your question regarding installing the new kernel, you are simply replacing the vanilla kernel file with the one you want to use. Take a look at this page: http://www.insanelymac.com/forum/topic/312049-amd-post-install-preparation/. You would do the same thing with your install media if the one that comes on the premade image doesn't work, or if you are making your install media  from scratch.
     
    (side note to Shaneee: there's no need to use -R (recursive) when you're copying a file or multiple files by themselves separate from a folder, the kernel file in this case. yours truly, nawcom the unix shell syntax nazi :-P)
     
    APU graphics aren't supported so you need to get a supported graphics card. And running macOS without a supported graphics card pretty much makes it worthless. You can still boot up the OS and get into the desktop though, it's just that graphics will generally be choppy. A number of macOS programs need Core Image / Quartz Extreme support (graphics acceleration) in order to work correctly. After all, there's really no such thing as a real Mac that comes with an unsupported graphics card.
     
    For your wireless card, you need to be specific about the model if you are asking if it is supported.
  5. Like
    nawcom reacted to bankkopf in GT630 2GB Sierra OS X driver acceleration   
    There are Kepler and Fermi variants. Kepler works oob, for Fermi you need inject nvidia.
  6. Like
    nawcom got a reaction from irrbloss in Can't boot without HDMI-cable connected to internal graphics card?   
    Ouch. What I understand about this situation is with some motherboard's firmware, it requires you to have an actual monitor plugged into the primary display port that you have selected in the BIOS/UEFI firmware, which in your case it's IGFX. I have personally not had to deal with this problem as I've always used Nvidia which does not have this requirement of setting your primary display in the BIOS/UEFI to IGFX or IGPU, but from what I understand this is a thing with AMD graphics.
     
    I think it has mainly been those small Intel NUC boxes that had a display plug in requirement in the UEFI which people would get around by using some kind of loopback device. Though, what was commonly used was either upgrading or rolling back the UEFI firmware to a version that no longer required a display to be plugged in. Since you haven't mentioned your motherboard model (other than being Gigabyte) I cannot search for that, so if you're up to it you can see what you can find.
     
    There are also various HDMI display emulators plug ins that you can buy for under 10 USD but I have never used them myself. Google "CompuLab Display Emulator" for one. I have never used it so I cannot promise you anything.
     
    As you can see I'm a retired developer and have no experience with dealing with present day AMD graphics cards, but I felt like telling you what I think regardless. Good luck on getting past this challenge.
  7. Like
    nawcom got a reaction from ellaosx in [pre-release] macOS High Sierra   
    Something I found interesting in this 10.13 beta install - the installer's OS lacked HD3000 kexts in BaseSystem.dmg's /S/L/E as well as in its kernelcache, yet looking inside its Core.pkg contents that it installs, the updated HD3000 kexts are there.
     
    As a result i followed the BaseSystem.dmg technique of making the install media so I could add those HD3000 drivers. Not sure if it looked at a checksum but as I started going forward with the install, it ended up forcing itself to go down a process of redownloading BaseSystem.dmg and copying to the partition I wanted to install 10.13 to for it to boot by itself and continue with the main install process. Needing an internet connection and redownloading the dmg appeared to be an unskippable process. Trying to boot that up resulted in a screwed up display as it was booting from the vanilla BaseSystem.dmg it downloaded.
     
    I decided to try installing the 10.13 pkgs from 10.12 install media which just requires you to delete the previous pkgs in the Packages folder and replace them with the 10.13 ones, and that went completely smooth. No 10.13 firmware checks or any other new issues you run into, however it meant you're installing it to HFS+ only and I was planning on doing that anyway. This is an old laptop and it boots best in legacy mode, so getting this new OS version running is good enough.
     

     
    After booting up 10.13, I noticed that by using 10.12 install media it seemed to have preserved some of the older 10.12 kexts in /System/Library/Extensions on the 10.13 partition post-install, so I just deleted all the kexts in there and extracted the Extensions folder from 10.13 Core.pkg that I used to put those in place so I could make sure I was using all 10.13 kexts as shown in the pic above, then made sure that kernelcache and prelinkedkernel was rebuilt.
     
    Well that's my story on getting it running on my Dell Latitude E6420 craptop
     
    e: I haven't found any issues on the installed OS so far but I wouldn't necessarily recommend following this technique just yet
  8. Like
    nawcom got a reaction from ellaosx in [pre-release] macOS High Sierra   
    Something I found interesting in this 10.13 beta install - the installer's OS lacked HD3000 kexts in BaseSystem.dmg's /S/L/E as well as in its kernelcache, yet looking inside its Core.pkg contents that it installs, the updated HD3000 kexts are there.
     
    As a result i followed the BaseSystem.dmg technique of making the install media so I could add those HD3000 drivers. Not sure if it looked at a checksum but as I started going forward with the install, it ended up forcing itself to go down a process of redownloading BaseSystem.dmg and copying to the partition I wanted to install 10.13 to for it to boot by itself and continue with the main install process. Needing an internet connection and redownloading the dmg appeared to be an unskippable process. Trying to boot that up resulted in a screwed up display as it was booting from the vanilla BaseSystem.dmg it downloaded.
     
    I decided to try installing the 10.13 pkgs from 10.12 install media which just requires you to delete the previous pkgs in the Packages folder and replace them with the 10.13 ones, and that went completely smooth. No 10.13 firmware checks or any other new issues you run into, however it meant you're installing it to HFS+ only and I was planning on doing that anyway. This is an old laptop and it boots best in legacy mode, so getting this new OS version running is good enough.
     

     
    After booting up 10.13, I noticed that by using 10.12 install media it seemed to have preserved some of the older 10.12 kexts in /System/Library/Extensions on the 10.13 partition post-install, so I just deleted all the kexts in there and extracted the Extensions folder from 10.13 Core.pkg that I used to put those in place so I could make sure I was using all 10.13 kexts as shown in the pic above, then made sure that kernelcache and prelinkedkernel was rebuilt.
     
    Well that's my story on getting it running on my Dell Latitude E6420 craptop
     
    e: I haven't found any issues on the installed OS so far but I wouldn't necessarily recommend following this technique just yet
  9. Like
    nawcom got a reaction from ellaosx in [pre-release] macOS High Sierra   
    Something I found interesting in this 10.13 beta install - the installer's OS lacked HD3000 kexts in BaseSystem.dmg's /S/L/E as well as in its kernelcache, yet looking inside its Core.pkg contents that it installs, the updated HD3000 kexts are there.
     
    As a result i followed the BaseSystem.dmg technique of making the install media so I could add those HD3000 drivers. Not sure if it looked at a checksum but as I started going forward with the install, it ended up forcing itself to go down a process of redownloading BaseSystem.dmg and copying to the partition I wanted to install 10.13 to for it to boot by itself and continue with the main install process. Needing an internet connection and redownloading the dmg appeared to be an unskippable process. Trying to boot that up resulted in a screwed up display as it was booting from the vanilla BaseSystem.dmg it downloaded.
     
    I decided to try installing the 10.13 pkgs from 10.12 install media which just requires you to delete the previous pkgs in the Packages folder and replace them with the 10.13 ones, and that went completely smooth. No 10.13 firmware checks or any other new issues you run into, however it meant you're installing it to HFS+ only and I was planning on doing that anyway. This is an old laptop and it boots best in legacy mode, so getting this new OS version running is good enough.
     

     
    After booting up 10.13, I noticed that by using 10.12 install media it seemed to have preserved some of the older 10.12 kexts in /System/Library/Extensions on the 10.13 partition post-install, so I just deleted all the kexts in there and extracted the Extensions folder from 10.13 Core.pkg that I used to put those in place so I could make sure I was using all 10.13 kexts as shown in the pic above, then made sure that kernelcache and prelinkedkernel was rebuilt.
     
    Well that's my story on getting it running on my Dell Latitude E6420 craptop
     
    e: I haven't found any issues on the installed OS so far but I wouldn't necessarily recommend following this technique just yet
  10. Like
    nawcom got a reaction from ellaosx in [pre-release] macOS High Sierra   
    Something I found interesting in this 10.13 beta install - the installer's OS lacked HD3000 kexts in BaseSystem.dmg's /S/L/E as well as in its kernelcache, yet looking inside its Core.pkg contents that it installs, the updated HD3000 kexts are there.
     
    As a result i followed the BaseSystem.dmg technique of making the install media so I could add those HD3000 drivers. Not sure if it looked at a checksum but as I started going forward with the install, it ended up forcing itself to go down a process of redownloading BaseSystem.dmg and copying to the partition I wanted to install 10.13 to for it to boot by itself and continue with the main install process. Needing an internet connection and redownloading the dmg appeared to be an unskippable process. Trying to boot that up resulted in a screwed up display as it was booting from the vanilla BaseSystem.dmg it downloaded.
     
    I decided to try installing the 10.13 pkgs from 10.12 install media which just requires you to delete the previous pkgs in the Packages folder and replace them with the 10.13 ones, and that went completely smooth. No 10.13 firmware checks or any other new issues you run into, however it meant you're installing it to HFS+ only and I was planning on doing that anyway. This is an old laptop and it boots best in legacy mode, so getting this new OS version running is good enough.
     

     
    After booting up 10.13, I noticed that by using 10.12 install media it seemed to have preserved some of the older 10.12 kexts in /System/Library/Extensions on the 10.13 partition post-install, so I just deleted all the kexts in there and extracted the Extensions folder from 10.13 Core.pkg that I used to put those in place so I could make sure I was using all 10.13 kexts as shown in the pic above, then made sure that kernelcache and prelinkedkernel was rebuilt.
     
    Well that's my story on getting it running on my Dell Latitude E6420 craptop
     
    e: I haven't found any issues on the installed OS so far but I wouldn't necessarily recommend following this technique just yet
  11. Like
    nawcom got a reaction from cuthead in why CMOS RESET bug exists?   
    http://netkas.org/?p=114
     
    Apple writes their drivers to work with only their own computers' firmware. The bug exists because standard PC motherboard makers don't design their own firmware to match Mac firmware. Not sure what you're expecting.
  12. Like
    nawcom got a reaction from defar in WiFi USB card for Sierra   
    Here's one I've used with the latest version of Sierra and I haven't run into any issues with it. I just bought it a month ago: TP-Link TL-WN725N https://www.amazon.com/TP-Link-N150-Wireless-Adapter-TL-WN725N/dp/B008IFXQFU
     
    Looks like it uses the same or similar Realtek chip as the Edimax EW-7811UN as the drivers given for them are the same. Feel free to go with Edimax if you want to save $0.50.
     
    Driver and Utility app: http://static.tp-link.com/TL-WN725N(EU)_V2_160822_Mac_1475908525444s.zip
  13. Like
    nawcom got a reaction from MaLd0n in HP/Compaq WIFI Error 104 (whitelist)   
    I took a quick look at your BIOS file and it has these cards listed in the whitelist that I'm seeing:
     
    8086:1043 subvendor 8086:2527, 8086:2522 - PRO/Wireless LAN 2100 3B Mini PCI Adapter
     
    8086:4220 subvendor 103c:12f5, 103c:12f6, 8086:2701 - Intel® PRO/Wireless 2200BG
     
    14e4:4320 subvendor 103c:12f4, 103c:12f6, 103c:12f8, 103c:12fa, 103c:12fb  - Broadcom BCM4306 802.11b/g Wireless LAN Controller
     
    I replaced the device and subdevice ids for the 2100 3B with the 2915 model info you provided in BIOSCOD1.ROM where they're referenced. Included is the WinPhlash app for flashing with the modded BIOS named MODDED.WPH and also includes the original.
     
    I am not responsible for anything that goes wrong with this.
     
    If it flashes fine but you still are getting the error 104 then let me know. According to the page some 2915ABG models use device id 8086:4223 subvendor id 8086:1000-1003 which I didn't add to this whitelist. I can add those as well.
    nx9020.zip
  14. Like
    nawcom got a reaction from Badruzeus in The macOS 10.13 is coming...   
    Are we keeping the URL a secret or something? here it is: https://swscan.apple.com/content/catalogs/others/index-10.13seed-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog.gz let me know if you want it removed. Nothing too exciting about what's on it other than it existing
  15. Like
    nawcom got a reaction from Badruzeus in The macOS 10.13 is coming...   
    Are we keeping the URL a secret or something? here it is: https://swscan.apple.com/content/catalogs/others/index-10.13seed-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog.gz let me know if you want it removed. Nothing too exciting about what's on it other than it existing
  16. Like
    nawcom got a reaction from BadWolfAlfa in ASUS K50IN Sierra -Kernel Panic- --Help -El Capitan- :) ♥   
    I patched it based off of the DSDT in a MacBookPro5,2 so let me know if it fixes USB or not.
     
    Also I didn't see if you found this already in chat: http://olarila.com/files/SMBIOS/MacBookPro5.2.plist you can use for smbios.plist
    DSDT.aml.zip
  17. Like
    nawcom got a reaction from PsychoKoopa in Yosemite Zone won't boot without install USB   
    You'll have to be specific about the error so I can tell if it's a bootloader error or a BIOS error, though it's sounding like a BIOS error to me. Your motherboard can understand GUID partition tables on hard drives just fine so that has nothing to do with it.
     
    edit: MC605 uses UEFI firmware so make sure you're booting the specific hard drive in legacy CSM mode for Chameleon/Chimera and Clover if you installed for legacy mode, or UEFI mode for Clover if you installed it in UEFI mode.
  18. Like
    nawcom got a reaction from BadWolfAlfa in ASUS K50IN Sierra -Kernel Panic- --Help -El Capitan- :) ♥   
    First off, it looks like you don't have a Core 2 Duo CPU - you have a Pentium CPU assuming T4300 is the correct model. That's just what Intel calls their lower performing CPUs these days. Regardless, it doesn't support SSE4.1/4.2 instructions that Sierra requires so you cannot run Sierra on this laptop. Sorry  No kernel has been made yet that can emulate these instructions.
  19. Like
    nawcom got a reaction from PMheart in Sierra 10.12.3 Asus GTX 650 show 0 Ram how to fix   
    Do you have some Nvidia injector enabled in Clover or Enoch? Turn it off. Nvidia cards that use Kepler or Maxwell architecture chips (mid range 600 series to 900 series) do not need injectors in order to work and can mess things up, like what you're seeing.
  20. Like
    nawcom got a reaction from artur_pt in why Linux is much slower than OS X?   
    Yep, it is your delusion.
  21. Like
    nawcom got a reaction from MaLd0n in Seems to have problems in my kernel logs, can anybody help?   
    the "Family specific matching fails" error is from the kernel regarding IOService and refers to a property matching issue with kexts. AppleUSBInterface is from IOUSBFamily and if you aren't having issues with USB ports then you should just ignore it. Your laptop uses Intel 8 series USB and you can look up fixes for it if you need to. My assumption is it's probably linked to your BisonCam NB Pro which connects through the USB bus and as far as I know it's not supported.
     
    As for your ACPI errors - it is common to see these in 10.12 with this new version of AppleACPIPlatform.kext. Older versions of OS X didn't do checks like this. AE_NOT_FOUND means the referred ACPI Entity is missing - in your case, \_SB_.PCI0.PEG0 which includes \_SB_.PCI0.PEG0.PEGP which is referring to PCI Express Graphics. If you're just using Intel graphics due to forced Optimus and it's working fine then I wouldn't worry about it as it's referring to the Nvidia card's device in ACPI.
  22. Like
    nawcom got a reaction from Iperzampem0 in rebooting kernel panic screen for installing Sierra   
    Here's a version that should be older than the one I previously uploaded. See if you run into the same issues.
    NVDAStartup.kext.310.42.25f01.zip
  23. Like
    nawcom got a reaction from Iperzampem0 in rebooting kernel panic screen for installing Sierra   
    Just letting you know nv_display=1 isn't a valid boot flag for anything so feel free to get rid of that.

    I've read that this is a common issue with these series of cards in Sierra and it seems the solution is to use NVDAStartup.kext from 10.11.6 and replace the Sierra version with it. Usually it's installed into /System/Library/Extensions, but you can try putting it in /EFI/CLOVER/kexts/10.12. If you go the /System/Library/Extensions route then sure to rebuild the kernel cache and prelinkedkernel on whatever you install it on. I'll attach the kext to this post.

    If you want to try and get Sierra installed before fixing this issue, you can try booting with nv_disable=1 until you have everything installed and booting from the hard disk.
    NVDAStartup.kext.zip
  24. Like
    nawcom got a reaction from artur_pt in why Linux is much slower than OS X?   
    Yep, it is your delusion.
  25. Like
    nawcom got a reaction from PMheart in FakeSMC help   
    You can put FakeSMC.kext into /Extra/Extensions (Chameleon) or /EFI/CLOVER/kexts/10.10 (Clover) using Transmac if it's on HFS+ in Windows if you want and there are other ways of accessing it from Windows if you are using an EFI system partition, but that's not what's causing your PCI configuration begin problem. You haven't mentioned your hardware specs so I can't tell what could be causing it. If you aren't booting with boot flag npci=0x2000 or npci=0x3000 you can try those. Some computers need a DSDT patch in order to fix a known issue with Device (PCI0) in which they need to remove Name (_ADR, Zero) and replace it with Name (_UID, Zero) which will cause that same error. There are also other possible causes.
     
    It could be multiple things but FakeSMC isn't causing it.
×