Jump to content

HELP TOPIC - for help in OS X Yosemite (10.10) and below


Deltac0
 Share

2,805 posts in this topic

Recommended Posts

that flexibility is coupled with the added complexity though

 

May be complex, but I'm used, in fact after much sweat in learning how to edit my DSDT, hardly use many options of Clover at most a patch here, an adjustment there and good.

Link to comment
Share on other sites

here are the 2 files in zip format. thanks again! :)

hi mrjayviper, here is a modified DSDT.aml for your system. 
 
In addition, "rampagedev" has already created the most SSDT.aml for many motherboard in a collection "AMD.DMG". 
 
Furthermore you can find here more information to the emergence of the "AMD.dmg" : http://www.insanelymac.com/forum/topic/297774-amd-dmg-development/
 
(Sorry, I've forgotten to mention)

DSDT.aml.zip

  • Like 1
Link to comment
Share on other sites

Which ones work best? Clover, Chameleon, Chimera (ie. a version of Chameleon), etc. Just curious what people are using with sucess. I'm using Chameleon.

 
The set up of the "config.plist"- file for "Clover bootloader", requires more knowledge about the built-in hardware specifications,
so it is for hackintosh beginners with a little difficulty - but solvable !
For Hackintosh beginners it is in my opinion, easier to use Chameleon bootloader.
I have made the best installation experience with Enoch bootloader:
^_^
  • Like 1
Link to comment
Share on other sites

You are not beginner, you just accustomed to use Chameleon.

Clover's config.plist is not needed to be filled by user. There are default settings.

I may agree that Clover has many features that not used by AMD users.

  • Like 1
Link to comment
Share on other sites

Well... Been using the same kexts and kernel since 10.10.3 all the way up to 10.10.5 14F6a and everything has been running smoothly. However.... Doesn't seem to work anymore with 10.10.5 14F19a. Just throwing a heads up for everybody/if anybody has got it to work.... PLEASE SHARE!!!  :)

Link to comment
Share on other sites

Well... Been using the same kexts and kernel since 10.10.3 all the way up to 10.10.5 14F6a and everything has been running smoothly. However.... Doesn't seem to work anymore with 10.10.5 14F19a. Just throwing a heads up for everybody/if anybody has got it to work.... PLEASE SHARE!!!  :)

no , bug for me 14F19a no work for me :(

  • Like 1
Link to comment
Share on other sites

@Gogeta5026:

Can you be a little more specific? What's not working? What happens? What error messages if any at all? Did you try and/or manage boot without cache after the update and kernel replacement to, then, rebuild the cache?

Tried all of that (repair, without, kernel replacement, EVERYTHING) and nothing. Hangs on missing Bluetooth adapter and does nothing. Left it running for about 30 minutes and just hangs.

Link to comment
Share on other sites

If System stuck at Missing Bluetooth Controller Transport!

 

 

Then boot with: kext-dev-mode=1 npci=x3000 usekernelcache=no -x. After you have started the system in Safe Mode, then run Kext Wizzard, so fix the permissions and refresh the cache. After that start your system normally. Then remove with myhack tool the problematic extensions.

 

Edit:

I have all my drivers for my hardware in /Extra/ Extensions/ *

Link to comment
Share on other sites

I disassembled an old GT210 and I installed it temporarily on A4-3400 .. now boot, it not stops at "System uptime in nanoseconds," but it gives me an error "PCI Parity ERROR" Press f1 or f2.. Keyboard freezed.

 

How do I fix it?

Link to comment
Share on other sites

I can't disable AGP, but I can select PCIe Graphics (PEG)..

 

Edit:

 

I use a USB flash disk with OS X Install version, hdd is on Sata0 (i tried the other Sata1, sata2, sata3..)

 

 

3097-SystemInfoWin.zip don't work..

 

jk7xqc.png

Link to comment
Share on other sites

You have fixed the problem with your BIOS settings?
 
unfortunately i can give you a only just few assistance to their system, due to lack of experience with their BIOS settings etc…
 
Here are my experiences with my APU system (I use AMD APU E1 2500) were as follows:
 
1.) 
 
the correct BIOS settings for OS X! 
AHCI Enabled
placing the OS X - HDD at the first boot sequence, etc
 
2.)
use on Windows operating system AIDA64 (free demo version) to export the VGA_BIOS gpu.rom file, then use the Systeminfo.app for Windows operating system, find the Vendor ID and Device ID of your APU Graphics (see the image of my SystemInfo), then renamed the exported vgabios gpu.rom (from AIDA64) in my case is the vga.rom  „1002_9838.rom“
 
3.)
install the DSDT Editor tool (for Windows operating system) create a DSDT, and fix all the bugs!
 
4.)
Place the DSDT.aml and the ROM file into the folder /Extra/ on your USB-flash Disk or your OS X HDD
into the folder /Extra/Extensions/ should be installed these drivers:
AppleACPIPS2Nub.kext, ApplePS2Controller.kext, FakeSMC.kext, Nullpowermanagement.kext
 
your org.chameleon.boot.plist should look something like this:
 
 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>DSDT</key>
	<string>/Extra/DSDT.aml</string>
	<key>EHCIacquire</key>
	<string>Yes</string>
	<key>EthernetBuiltIn</key>
	<string>Yes</string>
	<key>ForceHPET</key>
	<string>Yes</string>
	<key>GUI</key>
	<string>No</string>
	<key>GenerateCStates</key>
	<string>Yes</string>
	<key>GeneratePStates</key>
	<string>Yes</string>
	<key>Graphics Mode</key>
	<string>1680x1050x32</string>
    <key>GraphicsEnabler</key>
	<string>Yes</string>
	<key>Legacy Logo</key>
	<string>no</string>
    <key>UseKernelCache</key>
	<string>No</string>
	<key>Kernel</key>
    <string>kernel</string>
	<key>Kernel Flags</key>
	<string>-v kext-dev-mode=1 npci=0x3000 busratio=14 arch=x86_64 fsb=100 Mhz cpus=1 maxmem=2048</string>
	<key>Legacy Logo</key>
	<string>Yes</string>
	<key>SMBIOS</key>
	<string>/Extra/SMBios.plist</string>
	<key>Timeout</key>
	<string>2</string>
	<key>USBBusFix</key>
	<string>Yes</string>
	<key>UseAtiROM</key>
	<string>Yes</string>
	<key>VBIOS</key>
	<string>Yes</string>
	<key>device-properties</key>
	<string>640200000100000001000000580200000d00000002010c00d041030a000000000101060000020101060000007fff04001e00000072006f006d002d007200650076006900730069006f006e0000002a000000414d4420526164656f6e2048442038323430204f70656e474c20456e67696e65205b4546495d22000000400030002c006400650076006900630065005f00740079007000650000000b000000646973706c6179100000004e00560043004100500000001800000004000000000001000600000000000000000000000e0000006e0061006d00650000000b000000646973706c617914000000400030002c006e0061006d0065000000120000004e5644412c446973706c61792d41100000006d006f00640065006c00000016000000414d4420526164656f6e20484420383234300e0000004e00560050004d000000200000000100000000000000000000000000000000000000000000000000000014000000400031002c006e0061006d0065000000120000004e5644412c446973706c61792d4220000000400031002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d6163220000005600520041004d002c0074006f00740061006c00730069007a0065000000080000000000002020000000400030002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d616322000000400031002c006400650076006900630065005f00740079007000650000000b000000646973706c61791c0000006400650076006900630065005f00740079007000650000000f0000004e5644412c506172656e74</string>
</dict>
</plist>

 
the lower "device-properties-string" is for my APU! yours must be different ... the string you can export later and paste it into your org.chameleon.boot.plist !!
the bootargs in org.chameleon.boot.plist you should be determine of your system such as the details of: busratio and FSB.
 
good luck

SystemInfo 1-2.PNG

Edited by spakk
  • Like 1
Link to comment
Share on other sites

then boot the system with this bootarg:  -s kext-dev-mode=1 npci=0x3000 usekernelcache=no

 

then give the following:

 

fsck -fy (enter) and wait until the process is complete.

 

then

 

mount -uw /

 

Repeat this process until everything is repaired ...

then type

 

exit (enter)

  • Like 2
Link to comment
Share on other sites

or boot with os x install usb drive and repair disk and permissions with Disk Utility  

which is also a good alternative to resolve such problems.

 

 

Edit:

 

the problem with "System Stuck at Missing Bluetooth Controller transport!"
 
Can through the freeze of the graphics card which is caused during the operation, and when the system is turned off thereafter. then at the next boot, the problem occurs. In my opinion.

 

you have to find and remedy the cause.
 
look here, might it can help you, to resolve the problem:   https://m.youtube.co...h?v=sYLTcd5TwGk
Edited by spakk
  • Like 1
Link to comment
Share on other sites

You have fixed the problem with your BIOS settings?

 

1.) 

 the correct BIOS settings for OS X! 

AHCI Enabled

placing the OS X - HDD at the first boot sequence, etc

 

2.)

use on Windows operating system AIDA64 (free demo version) to export the VGA_BIOS gpu.rom file, then use the Systeminfo.app for Windows operating system, find the Vendor ID and Device ID of your APU Graphics (see the image of my SystemInfo), then renamed the exported vgabios gpu.rom (from AIDA64) in my case is the vga.rom  „1002_9838.rom“

 

3.)

install the DSDT Editor tool (for Windows operating system) create a DSDT, and fix all the bugs!

 

4.)

Place the DSDT.aml and the ROM file into the folder /Extra/ on your USB-flash Disk or your OS X HDD

into the folder /Extra/Extensions/ should be installed these drivers:

AppleACPIPS2Nub.kext, ApplePS2Controller.kext, FakeSMC.kext, Nullpowermanagement.kext

 

I've fixed Bios Settings..

AHCI enabled and HDD at first boot sequence and first sata..

 

2) I've got vgabios.bin, renamed "1002_9644.rom"

 

3) I'm trying to fix DSDT.... :\

 

 

EDIT: I don't know how fix PCI Parity Error in DSDT...

EDIT 2:

 

the lower "device-properties-string" is for my APU! yours must be different ... the string you can export later and paste it into your org.chameleon.boot.plist !!

 

from?

  • Like 1
Link to comment
Share on other sites

PCI Parity Error

I can not tell you with 100%, which is the cause of your problem, since I have not had a problem until today. One possible cause may be the hardware, such as. motherboard or graphics card? Please open your case and check the connections, may take the graphics card out, cleanliness of terminal strips, then insert the graphics card into the PCI slot.

Should not the act, then install the latest BIOS for your board. ---> I hope that the issue is resolved by a BIOS update.

"device-properties" string for your org.chameleon.boot.plist

Device Properties-string, is first of all secondary, as long as your computer does not start

 

Edit:

is the problem with "PCI Parity Error" occurred after you've connected the other graphics card? or only, since you changed the BIOS settings for OS X?

 

you may also like to read here if you can find a solution : https://www.google.de/search?client=firefox-a&hs=69K&rls=org.mozilla:de:official&channel=sb&q=pci+parity+error+gigabyte&revid=1705438068&sa=X&ved=0CIcBENUCKABqFQoTCNzN5u_hiMcCFYYFLAodT58FMA

 

 

I suspected something like this is posted:

 

 

"...Hello it sounds like the BIOS is causing the issue PCI parity error Means That it is having trouble Detecting what the PCI bus interface Onto Compared To What it has stored in CMOS.

 

This will cause major issue with any device on the PCI IDE controller level Including soundcards etc.

 

See if you can remove the CMOS battery inside and reseat it, to clear the BIOS. If not then try removing any expansion cards on the PCI channel and reboot. You can always add it later whichwill Either work or identify the device causing the issue. I'm thinking maybe its your ram as some RAM has parity checking. Take out your RAM and try just one stick. If it works you know you have a problem with a stick of RAM !! If it does not work, try the same stick in a different DIMM slot. With the price of RAM at present, this will be a cheap problem !!

 

When you get the motherboard running again, please update the BIOS to the latest version.

A BIOS upgrade, sometimes solves hardware problems.

You just have to make sure it`s the right motherboard...."

 

here the complete article:

  http://www.fixya.com/support/t16357056-pci_parity_error

Edited by spakk
  • Like 1
Link to comment
Share on other sites

PCI Parity Error appears when I start any OS X that exceeds the "System uptime in nanoseconds" (ie with mckay_kernel 10.9 and 10.8 Bronya's kernel, -v cpus=1); with both the APU 6410D with both the GT210 ..

 

some bios settings wrong?

 

Virtualization Enabled

AHCI Enabled

AMD C6 support Enabled

COOL'n'QUIET Auto

Usb Controller Enabled

Usb Legacy FunctionEnabled

Usb Storage Function Enabled

Onboard LAN Function Disabled

HPET Support Enabled

---(no 64bit selection)

 

the bios has the latest version..

 

 

EDIT:

 

I did check the motherboard by a technician who has complete control with a pci card (a more elaborate version of memtest from what I understand, screen very similar) and did not detect any damage ..

 

Now I try to restore the CMOS..

 

EDIT 2: CMOS restored, no changes..

Edited by lfmg
Link to comment
Share on other sites

1. Set the BIOS settings to default, then save the Bios settings with "Yes" , then restart your system.
2. then boot into the BIOS , then make the BIOS settings as described below, then save settings with "Yes"
 

AHCI Enabled
COOL'n'QUIET Auto !!!
Usb Controller Enabled
Usb Legacy FunctionEnabled
Usb Storage Function Enabled
HPET Support Enabled

Advenced BIOS Features section:
Load Line Control: Auto
AMD C6 Support: Disabled
Virtualization: Enabled
EFI CD/DVD Boot Option: NON-EFI
First Boot Device: USB-FDD
Away Mode: Disabled
Init display first: PEG(PCI, not onchip)

Integrated Peripherals section:
OnChip SATA: Enabled
OnChip SATA Type: AHCI

 

these are my Gigabyte BIOS settings, this is only as an example. However, for another AMD CPU!  ( my BIOS Settings )

 

if you do not have all the settings, that I have described, then just use the find in your BIOS. ^_^

Edited by spakk
  • Like 1
Link to comment
Share on other sites

Please proceed as described above before. Set the BIOS settings to "default"! and so on .... This is just to make sure that did not perhaps made to overclock the CPU etc. .... Please proceed step by step to locate the cause.

 

The correct BIOS settings can be the path to the goal. if something is not set correctly, then OS X will not run

 

Edit:

 

you have wrote, that you have created a dsdt. then uploade this here, then I can check, if I can edit it.

Edited by spakk
  • Like 1
Link to comment
Share on other sites

Please proceed as described above before. Set the BIOS settings to "default"! and so on .... This is just to make sure that did not perhaps made to overclock the CPU etc. .... Please proceed step by step to locate the cause.

 

The correct BIOS settings can be the path to the goal. if something is not set correctly, then OS X will not run

 

Ok, restored Default Bios' settings..

I'm not overclocked the CPU, and I enabled all as thou hast suggested.

 

ehm.. I'm really confused..

 

I tried:

mckay_kernel -v cpus=1    => PCI Parity Error

mckay_kernel -v cpus=2 busratio=27      => stuck at PCI Configuration Begin

 

then

 

mckay_kernel -v cpus=2 busratio=27 npci=0x3000      => stuck at System uptime in nanoseconds..

mckay_kernel -v cpus=2 busratio=27 npci=0x2000      => stuck at System uptime in nanoseconds..

Link to comment
Share on other sites

mckay_kernel -v cpus=2 busratio=27      => stuck at PCI Configuration Begin

then boot with npci=0x2000 or npci=0x3000

 

(...es wird schon gelingen :-)), nicht ärgern)

 

 

Edit:

 

I suspect that the information for busratio are too high! check this information! probably > 20

 

information about the correct settings for busratio

Edited by spakk
  • Like 1
Link to comment
Share on other sites

 Share

×
×
  • Create New...