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. 
micceo

DSDT help with 7xxx Series

35 posts in this topic

Recommended Posts

Hi, you don't need to edit your DSDT. As an alternative you can use your boot manager to inject the video properties. Clover got the GraphicsInjector setting, Chameleon got GraphicsEnabler I think.

The guide you linked to contains a list of all 7000 series framebuffers. Try different framebuffer names. The common ones are: Aji, Dashimaki, Futomaki, Hamachi.

Share this post


Link to post
Share on other sites

Thanks k3nny , i tried with the various framebuffers, the most success i got was with OPM, but the processing got stuck at AMDTahitiGraphicsAcceleration

Share this post


Link to post
Share on other sites

Install the latest Clover bootloader, then just reboot, don't worry about dsdt stuff just boot, that worked for my config in my signature

Share this post


Link to post
Share on other sites

I installed the latest clover on a usb and tried booting with that, it still gets stuck on the same line. Are there any flags or precautions I need to use?

Share this post


Link to post
Share on other sites

Thank you iFIRE your dsdt got me farther :)

Now I get

RadeonMonitor unknown device Id

RadeonMonitor can't initialize driver

 

I think we are quite near, can u help me on this

Share this post


Link to post
Share on other sites

RadeonMonitor causes a lockup with HD 7000 series. Remove it and rebuild kernel cache. It will probably be in the plugin folder of FakeSMC.

Your problem right now might be another one but RadeonMonitor will give you issues sooner or later.

Share this post


Link to post
Share on other sites

I tried looking under FakeSMC plugins directory but could not find RadeonMonitor, any suggestions where can it be located

Share this post


Link to post
Share on other sites

:wallbash:

I guess you have integrated HD 4000. Try to set onboard GPU (sharing memory 32/64mb) as primary while your monitor connected to ATI card. Here you do not need DSDT injection and try available framebuffers mentioned above.

 

The other way around, set PCIe card as primary but do not set sharing memory to Auto. You may test with and without CsmVideo driver.

Share this post


Link to post
Share on other sites

even if i set the integrated graphics as the primary device, the booting gets stuck on radeonmonitor. I dont know why this is the case.

Share this post


Link to post
Share on other sites

lspci -nnvd 0x1002: | grep -B2 Subsystem

 

 

sudo kextstat | grep AMD

 

 

 

ioreg -l | grep -15 "AppleACPIPCI" | grep "_UID"

 

lspci -nn

 

 

 

 

 

 

Install this kexts with Kext Wizard/repairpermissions/reboot , now open app Terminal and put:

sudo -s

pasww your passw

 

and copy and past these line of code in terminal app + enter, one by one line + enter, and post results here in the your topic.

 

lspcidrv.kext.zip

 

 

 

EDIT: send me a full report with app Darwin Dumper

Share this post


Link to post
Share on other sites

even if i set the integrated graphics as the primary device, the booting gets stuck on radeonmonitor. I dont know why this is the case.

Then most likely RadeonMonitor kext causes the problem. It should be somewhere (if not presented in FakeSMC plugins folder). Try ignoring kernelcache (press space bar for Clover).

Share this post


Link to post
Share on other sites

I tried installing the kext you gave me, but it shows lspci command not found. I did fix the permissions and also rebuilt the cache using kext wizard. I tried clover bootloader by ignorning kernel cache. Still stuck on radeon monitor

Share this post


Link to post
Share on other sites

man, if you can not install a kext, forget Mac OS X , install WIN7 is better for you and not have any problem

Share this post


Link to post
Share on other sites

It is not that I cannot install a kext file.

This is the step i followed:

Started kextwizard,

went to installation tab, selected your kext file (after i unzipped it)

clicked on install

clicked on maintainence

selected both repair permissions, rebuild cache

rebooted with -x -v flags

opened terminal and executed lspci , it shows command not found.

 

I understand the use of lspci command, i have used linux and windows, just i dont know why the command is not working

 

according to http://www.osx86.net/downloads.php?do=file&id=1643

compatibility of lspci for 10.8.xx is unknown

Share this post


Link to post
Share on other sites

jejejejejeej!!!!!!, -x -v ? flags!!! you know what is this two flags? man read a bit

 

 

 

02. BootHelp.txt:

 

The boot: prompt waits for you to type advanced startup options.

If you don't type anything, the computer continues starting up normally. It

uses the kernel and configuration files on the startup device, which it also

uses as the root device.

 

Advanced startup options use the following syntax:

 

[device]<kernel> [arguments]

 

Example arguments include

 

device: rd=<BSD device name> (e.g. rd=disk0s2)

rd=*<IODeviceTree path> (e.g. rd=*/PCI0@0/CHN0@0/@0:1)

 

kernel: kernel name (e.g. "mach_kernel" - must be in "/" )

 

flags: -v (verbose) -s (single user mode),

-x (safe mode) -F (ignore boot configuration file)

 

"Graphics Mode"="WIDTHxHEIGHTxDEPTH" (e.g. "1024x768x32")

For VESA 3.0 graphics, you may append a refresh rate

after an "@" character (e.g. "1280x1024x32@75")

 

kernel flags (e.g. debug=0x144)

io=0xffffffff (defined in IOKit/IOKitDebug.h)

 

Example: mach_kernel rd=disk0s1 -v "Graphics Mode"="4096x4096x32@85"

 

If the computer won't start up properly, you may be able to start it up using

safe mode. Type -x to start up in safe mode, which ignores all cached

driver files.

 

Special booter commands:

?memory Displays information about the computer's memory.

?video Displays VESA video modes supported by the computer's BIOS.

?norescan Leaves CD-ROM rescan mode.

 

Additional useful command-line options:

config=<file> Use an alternate Boot.plist file.

 

Options useful in the com.apple.Boot.plist file:

"Boot Graphics"=Yes|No Use graphics mode or text mode when starting.

"Quiet Boot"=Yes|No Use quiet boot mode (no messages or prompt).

Timeout=8 Number of seconds to pause at the boot: prompt.

"Instant Menu"=Yes Force displaying the partition selection menu.

 

"Default Partition" Sets the default boot partition,

=hd(x,y) where 'x' is the disk number, 'y' the partition number.

 

GUI=No Disable the GUI (enabled by default).

 

USBBusFix=Yes Enable the EHCI and UHCI fixes (disabled by default).

EHCIacquire=Yes Enable the EHCI fix (disabled by default).

UHCIreset=Yes Enable the UHCI fix (disabled by default).

 

Wake=No Disable wake up after hibernation (enbaled by default).

ForceWake=Yes Force using the sleepimage (disabled by default).

WakeImage=<file> Use an alternate sleepimage file

(default path is /private/var/vm/sleepimage).

 

DropSSDT=Yes Skip the SSDT tables while relocating the ACPI tables.

DSDT=<file> Use an alternate DSDT.aml file

(default paths are /DSDT.aml or /Extra/DSDT.aml).

 

SMBIOSdefaults=No Don't use the Default values for SMBIOS overriding

if /Extra/smbios.plist doesn't exist, factory

values are kept.

 

Rescan=Yes Enable CD-ROM rescan mode.

"Rescan Prompt"=Yes Prompts for enable CD-ROM rescan mode.

Share this post


Link to post
Share on other sites

-v is for verbose output and -x is for safe mode wherein a limited number of kexts are loaded. But that is the only way my machine loads mac osx, it will not load without the -x, because it gets stuck at radeon monitor

Share this post


Link to post
Share on other sites

man, how you want what yours graphics kexts and your system work with -x ? if with -x the system not load all kexts, only load for the safe mode, you have used my hack for install?

 

 

 

 

EDIT: send me you folder Extensions

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

    • 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
    • @MegaCookie   ok, I have no solution for that Trial 7 good for the release?
      Is this codec good enough for you?
    • @onejay09  - thanks again for your help and advice.  I tried various combinations of Info.plist mods (Adding a new Machine entry with my Board ID and GFX0, adding GFX0 to the MacBookPro6,1 Machine entry and adding a Vendor/Device entry to the Board ID and MacBookPro6,1 Machine entries. I thought these might make a difference, but after comparing GPU temps and frequencies to those reported in Windows 7, I'm not seeing any difference.  It appears as though AGPM is natively detecting and handling power management of the NVidia Quadro NVS 140m without any Info.plist mods.   Thanks again.
    • My rig is not booting without the "XCPM bootstrap patch" and "xcpm_program_msrs (c) Pike R. Alpha" patch. Already tested that.  Booting without the TSCAdjustReset.kex is working great and booth sleep and wake is working. The new bios 0603 has an updated microcode. That might be the reason  for the fact that everything is working as it should without the kext.


×