Jump to content
  • Announcements

    • Allan

      Forum Rules   04/13/2018

      Hello folks! As some things are being fixed, we'll keep you updated. Per hour the Forum Rules don't have a dedicated "Tab", so here is the place that we have our Rules back. New Users Lounge > [READ] - InsanelyMac Forum Rules - The InsanelyMac Staff Team. 
oxygenz

Natit hd4870 blank screen after each reboot

7 posts in this topic

Recommended Posts

Symptoms for 10.5.7 with Ati HD4870 (Asus in my case):

-after installing the Natit.pkg everything works fine

-on 2nd reboot you get blank screen

-boot with -x (safemode) and reinstall Natit.pkg

-everything works again...until 2nd reboot when u get blank screen

:hysterical:

 

I know this is happening to other people (from what I read in comments), and they all said they can live with it:)), well...I couldn't.

 

To fix this annoyance I have prepared a startup script which will run with root (or some root equivalent) credentials and automatically and silently install the Natit.pkg on each boot, to fix the blank screen after 2nd boot.

 

-create a folder named ATIFix in /Library/StartupItems

-Copy these attached files in there:

ATIFix

StartupParameters.plist

 

-create a folder ATIFix in /Library

-copy Natit.pkg in there

 

-Install Natit.pkg and reboot to allow OSX to repair permissions on the StartupItems

-reboot twice to test

 

Have fun:)

Archive.zip

Share this post


Link to post
Share on other sites
Symptoms for 10.5.7 with Ati HD4870 (Asus in my case):

-after installing the Natit.pkg everything works fine

-on 2nd reboot you get blank screen

-boot with -x (safemode) and reinstall Natit.pkg

-everything works again...until 2nd reboot when u get blank screen

:)

 

I know this is happening to other people (from what I read in comments), and they all said they can live with it:)), well...I couldn't.

 

To fix this annoyance I have prepared a startup script which will run with root (or some root equivalent) credentials and automatically and silently install the Natit.pkg on each boot, to fix the blank screen after 2nd boot.

 

-create a folder named ATIFix in /Library/StartupItems

-Copy these attached files in there:

ATIFix

StartupParameters.plist

 

-create a folder ATIFix in /Library

-copy Natit.pkg in there

 

-Install Natit.pkg and reboot to allow OSX to repair permissions on the StartupItems

-reboot twice to test

 

Have fun:)

 

Hey, Are you using the DVI2VGA to connect monitor? I also using a Asus 512M 4870 with two DVI and a S-Video. Not sure what's the problem caused it do not work in the second time.

Share this post


Link to post
Share on other sites

Having same problem and it's really annoying, I must admit.

 

I'll try what you posted and feedback later on.

 

Btw, I also have Ati HD 4870 and Asus (P5QL actually)

 

I thought it was something to do with my OSX install so am reinstalling (I just started getting into osx86 yesterday) - but now I read your post it makes sense.

 

Thanks mate!

 

EDIT:

 

Works wonderful - like a charm! Thanks a bunch.

Share this post


Link to post
Share on other sites

@maestro0428

 

 

ATI4800Controller.kext

ATIFramebuffer.kext

ATISupport.kext

LegacyATI4800Controller.kext (this kext injects your cards ID automatically no modifying plist)

video.zip ( 903.47K ) Number of downloads: 127

 

Read through this thread and yes its different depending what version of card you have and what Chameleon your using and what version of OSX

Start at the beginning

 

 

HD48xx use the same kext (drivers).

 

Remember to boot in safe mode (look it up but it should be typing -x on the Chameleon screen selection)

 

Good luck!

Share this post


Link to post
Share on other sites
Hey, Are you using the DVI2VGA to connect monitor? I also using a Asus 512M 4870 with two DVI and a S-Video. Not sure what's the problem caused it do not work in the second time.

 

No. Try the steps above, or search the net on how to refresh the boot caches (I think it could work without the steps above, although I haven't tried it).

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Posts

    • You can try this one here 2.9.0 let me know if its better for you ?   VoodooHDA.kext.zip
    •   Boot option name retrieval 1) Locate the booter image as explained blow. 2) Locate ".contentDetails" in the parent folder 2.1) if unsuccessful, locate ".disk_label.contentDetails" in the parent folder 2.2) if unsuccessful, retrieve the volume's name   HFS Boot 1) Retrieve blessed file via https://github.com/CupertinoNet/EfiPkg/blob/development/Include/Guid/AppleBless.h#L41 1.1) if unsuccessful, retrieve blessed folder via https://github.com/CupertinoNet/EfiPkg/blob/development/Include/Guid/AppleBless.h#L45, append "\\boot.efi". NOTE: This is broken in the latest binary I checked. 1.2) if unsuccessful, use the following hard-coded paths: "\System\Library\CoreServices\boot.efi", "\EFI\APPLE\{ARCH}\BOOT.EFI", <StandardEfiPath>, "\\boot.efi" in this order 2) FV2 Recovery does not follow the usual practice because it is not shown by BootPicker anyway. Determine it via https://github.com/CupertinoNet/EfiPkg/blob/development/Include/Guid/AppleBless.h#L49, verify it does not match 1).   APFS Boot 1) Determine the APFS Volume Info (and hencefor detect whether it is APFS in the first place) via https://github.com/CupertinoNet/EfiPkg/blob/development/Include/Guid/AppleApfsInfo.h#L54 1.1) Determine the APFS Container Info via https://github.com/CupertinoNet/EfiPkg/blob/development/Include/Guid/AppleApfsInfo.h#L36 1.2) Verify the Volume Role via https://github.com/CupertinoNet/EfiPkg/blob/development/Include/Guid/AppleApfsInfo.h#L51 1.3) Retrieve blessed file analoguous to HFS 1). NOTE: This step and 1.3.1) are broken in the binary I checked, hencefor it does not happen, but is probably supposed to. 1.3.1) if unsuccessful, retrieve blessed folder and append the booter name the same way as in HFS 1.2) 1.4) (if unsuccessful,) locate all Volumes that are part of the same container, check whether the current Preboot partition has folders named by the just located Volumes' GUIDs and append the hard-coded paths from HFS 1.2) if existant 2) Recovery detection works the same way as 1.4), just for a Recovery instead of a Preboot volume
    • Got garbled sound in earphone    Notebook Asus X550VX i7 - 7700hq with ALC255 not working with applealc  layout id  3, 13, 17, 18, 27, 28, 99 its is working with VoodooHDA but the new one 2.9.1 it much has low volume, but bad sound in earphone     codec dump linux https://drive.google.com/file/d/1pg2y76WvFYsO8vFY-2B_2OLyKMmkQ8Tg/view     latest debug http://www.mediafire.com/file/2pjny4eq5r64ed8/debug_1383 (1).zip  
    • For F6 Bios, which DSDT is the one i should use? I´m a little confused in the Mass of DSDT here ;-).   Great Thread by the Way.   Another Question: I have 2 960Pro inside my Rig (one with OS X, one with Windows 10). When i try to mount my EFI on OS X NVMe the system freezes... :-(   DWhen i unplug the Windows NVMe everything is fine an it mounts the EFI.   Anybody an idea?   Tried the upper Port on the Board (OS X) & the middle / lower Port, in the Middle it mounts the EFI in the lower it freezes.   But i need the middle Port for an SATA M.2 SSD :-D... Even when i plug the Windows NVMe into an PCIe Adapter Card it freezes at the point i mount the EFI.   I´m mounting with Clover Configurator.     Thank You guys.
    •   Just add "ngfxsubmit=0" to config.plist to disable the fix within nvidiafixup


×