AnVAL (ACPI Loader)

FKA · November 13, 2010

int mV, e.g.: 1100 --> 1.1 V,
anyway u cannot go with more than 100 mV (compared to oem) for max and 250 for min; else defaults to oem values.

values are injectable from boot.plist, mine looks like this:

thanks - will test for you later this evening

TorqueX86 · November 13, 2010

Hi there,

Good job, something is stirring for us poor ATI/AMD users...

I have met a few problems that might be useful to share. Please look at my configuration in signature to understand what we are talking about:

- GFX wise:

QE/CI are functional. But the framebuffer is erroneously detected: Check my PCI card readout:

ATI Radeon 5800 Series:

Name: ATY,Zonalis

Type: display

Driver Installed: Yes

Bus: PCI

Slot: Slot-1

Vendor ID: 0x1002

Device ID: 0x6899

Subsystem Vendor ID: 0x174b

Subsystem ID: 0xe140

Revision ID: 0x0000

Link Width: x16

Link Speed: 2.5 GT/s

- CPU wise:

Nice job overall, but I have a problem with the speed. The CPU is locked at an awesome 1.8GHz and can't go up. Here's the bdmesg readout:

C1 C3 C6

Voltage: min= 700mV, max= 700mV

P-State: Added [Frequency 1800 MHz, FID 0x9, VID 0x0]

P-State: Added [Frequency 1600 MHz, FID 0x8, VID 0x0]

P-State: Added [Frequency 1400 MHz, FID 0x7, VID 0x0]

P-State: Added [Frequency 1200 MHz, FID 0x6, VID 0x0]

I hope my findings are of any help. RAM was detected perfectly.

Cheers

mitch_de · November 13, 2010

Thanks for the Volts Info + boothelp.txt !

The OC feature is really great - but has some major side effect.

For sure i can avoid KPs if i set MinVolt as high as i need.

BUT: This set all Pstates to that MinVolt - even its fitting only to the highest MHZ step, and the others need less VID - but higher than auto generated.

I use following VIDS in the dsdt:

14, 1A, 1E, 22 (ALL HEX) for my C2D (2.66> 3.0). The autogeneratad are 2-3 VID steps (2-3*32mV) less - KPs after some time.

I could use autogen PStates + MinVolt (which i must set to 22 VID), but all others, which need much less VID, like 14,1A,1E, would be "overvolted". No prob but inefficient.

Much better + maybe even easier to code, would be an VIDplus value , 1...4 which steps up that VIDs generated by the PState gen.

PS: I forgot the formula which can compute VID into mVolts and back - anyone ?

FKA · November 13, 2010

No go with GraphicsEnabler and my ati5770. Otherwise boots fine.

can you add ati.c from Chameleon trunk but with:

{ 0x100268B8, "Vervet"},

Sorry I dont have time to swap around GPUs.

Oh - and from chameleon verbose i can see default generated VID are the same. I assume its the same code as mozodojo?

D

valv · November 14, 2010

@TorqueX86, for the cpu, VIDs zeroing seems to be the big issue; I feel it is only related to i-series. what if u injected the voltage min-max values. Regarding the 1800Mhz maximum for freq, try using the ForceFSB + busratio keys, to see if that would fix things; and please provide me with the bdmesg log (in its entirety), as attachment.

@mitche_de, as u need to over-volt from highest on, have u tried it with MaxVolt key instead? Other than that, it is sure that the suggested feature is interesting: I 'd be adding it asap, don't worry

@FKA and cparm, yes it is mozo's algo but with differences. source code should explain it all (as soon as I get everything in place, and working).

for info, this here is my bdmesg dump:

LoadConfig: [hd(0,1)/Extra/com.apple.Boot.plist] 1896 bytes.
CPU: Mobile Intel® Core2 Duo CPU P8700 @ 2.53GHz

CPU: Sticking with [FSB: 266Mhz, Bus-Ratio: 9.5]

CPU: Tjmax= ~ 105°C Temperature= ~ 29°C

CPU: Vendor/Family/ExtFamily: 0x756e6547/0x6/0x0

CPU: Model/ExtModel/Stepping: 0x17/0x1/0xa

CPU: MaxCoef/CurrCoef: 0x9/0x6

CPU: MaxDiv/CurrDiv: 0x1/0x0

CPU: Multiplier x10: 95

CPU: TSCFreq: 2527MHz

CPU: CPUFreq: 2533MHz

CPU: FSBFreq: 266MHz

CPU: SLFM: 1

CPU: Enhanced SpeedStep: 1

CPU: NoCores/NoThreads: 2/2

CPU: Features: 0x268802a3

Chipset is GM45 (pci id 0x2a408086)

We have an NVIDIA Card

...

Found ACPI CPU: CPU0

Found ACPI CPU: CPU1

Found ACPI CPU: CPU2

Found ACPI CPU: CPU3

C-State: Adding 5 states: C1 C2 C3 C4 C6

Voltage: min= 850mV, max= 1100mV

P-State: Added [Frequency 2527 MHz, FID 0x49, VID 0x1f]

P-State: Added [Frequency 2394 MHz, FID 0x9, VID 0x1d]

P-State: Added [Frequency 2261 MHz, FID 0x48, VID 0x1c]

P-State: Added [Frequency 2128 MHz, FID 0x8, VID 0x1a]

P-State: Added [Frequency 1995 MHz, FID 0x47, VID 0x19]

P-State: Added [Frequency 1862 MHz, FID 0x7, VID 0x17]

P-State: Added [Frequency 1596 MHz, FID 0x6, VID 0x16]

P-State: Added [Frequency 1330 MHz, FID 0x8a, VID 0x13]

P-State: Added [Frequency 1064 MHz, FID 0x88, VID 0x10]

P-State: Added [Frequency 798 MHz, FID 0x86, VID 0xd]

LoadACPI: [hd(0,1)/Extra/FADT.aml] 244 bytes.

FADT: Restart Fix applied !

Patched ACPI version 2 DSDT

Starting Darwin x86_64

Press any key to continue...

@everyone, the idea of editable number of loadable pstates is originally from cparm.

mitch_de · November 14, 2010

Thanks for updating the infos !

valv · November 14, 2010

Thanks for updating the infos !

latest release moved to first post;

@mitch_de, moreVolt & lessVolt should do the trick; untested though

@FKA, sorry, I forgot to add your request

I've got a hard day, I need to rest a little; see you later, sorry

FKA · November 14, 2010

@FKA, sorry, I forgot to add your request

I've got a hard day, I need to rest a little; see you later, sorry

Not a problem - let me know when it's done and I'll test it out. :smoke:

mitch_de · November 14, 2010

latest release moved to first post;
@mitch_de, moreVolt & lessVolt should do the trick; untested though

@FKA, sorry, I forgot to add your request

I've got a hard day, I need to rest a little; see you later, sorry

Great i will try that this evening(next 4 hours!) and report

I´ll be back :unsure: (hope so...)

OK, back and report.

System is normal 9*333 MHZ = 3.0 GHz

For tests (and that was NEEDEDI i set it to 9*300 = 2,7 GHz

1. Pstate Generation works as it should , also VIDs are good (little less than my handmade for OC)

2. MAJOR generell problem - since voodoomonitor (new Chameleon use that code also for autogen Pstates

You see that i OC my system by FSB, BUT also reduced the standard multi from 10* to 9* in BIOS setting, my handmade dsdt Pstate also are from 6*...9*, not up to 10* (10*333=3,33 Ghz = KP)

IN the past, using voodoomonitor (superhai) i set there an PstateLimit 1 (=9*), not using Pstate 0 (=10*) - worked perfect in my case of 9*

Now , with RC5 autogen and also AnVAL new great boot, such an PstateLimit is missed.

Look what it autogernerates 5.0.2, 300 Mhz FSB:

If i had not set back the FSB from 333 to 300, i would got an KP, because 10*333 = 3.33 GHZ to high for the 2.66

Voltage: min= 1037mV, max= 1112mV

P-State: Added [Frequency 3000 MHz, FID 0xa, VID 0x20] // OK with 300 FSB, 333 would KP because BIOS limit 9* multi

P-State: Added [Frequency 2700 MHz, FID 0x9, VID 0x1f]

P-State: Added [Frequency 2400 MHz, FID 0x8, VID 0x1d]

P-State: Added [Frequency 2100 MHz, FID 0x7, VID 0x1c]

P-State: Added [Frequency 1800 MHz, FID 0x6, VID 0x1a]

Patched ACPI version 1 DSDT

Starting Darwin x86_64

I also tried the moreVolt , but wried VIDs were shown (system worked, i think they were not set)

P-State: Added [Frequency 3000 MHz, FID 0xa, VID 0xe8]

P-State: Added [Frequency 2700 MHz, FID 0x9, VID 0xe7]

P-State: Added [Frequency 2400 MHz, FID 0x8, VID 0xe5]

P-State: Added [Frequency 2100 MHz, FID 0x7, VID 0xe4]

P-State: Added [Frequency 1800 MHz, FID 0x6, VID 0xe2]

I first used moreVolt=80 (i remember xee as max, in the list above shown i used =2

If sometime that voodoomonitor key PsateLimit will be build in and i would set it to 1, such Pstates would be generated (OK, like my handmade ones), and even 333 FSB would be possible with 9* max. PState

P-State: Added [Frequency 2700 MHz, FID 0x9, VID 0x1f] /PstateLimit = 1 means no Pstate 0 =10* will be genertated

P-State: Added [Frequency 2400 MHz, FID 0x8, VID 0x1d]

P-State: Added [Frequency 2100 MHz, FID 0x7, VID 0x1c]

P-State: Added [Frequency 1800 MHz, FID 0x6, VID 0x1a]

The good: much informations in that bdmesg

LoadConfig: [hd(0,1)/Extra/com.apple.Boot.plist] 773 bytes.
CPU: Intel® Core(tm)2 Duo CPU     E7300  @ 2.66GHz
max: 10 current: 6
CPU: Tjmax= ~ 104°C           Temperature= ~ 45°C
CPU: Vendor/Family/ExtFamily: 0x756e6547/0x6/0x0
CPU: Model/ExtModel/Stepping: 0x17/0x1/0x6
CPU: MaxCoef/CurrCoef:        0xa/0x6
CPU: MaxDiv/CurrDiv:          0x0/0x0
CPU: Multiplier x10:          100
CPU: TSCFreq:                 3000MHz
CPU: CPUFreq:                 1800MHz
CPU: FSBFreq:                 300MHz
CPU: Enhanced SpeedStep:      1
CPU: NoCores/NoThreads:       2/2
CPU: Features:                0x268802a1
Chipset is G31 (pci id 0x29c08086)
We have an NVIDIA Card
Creating 2 Mode Tables
New table with id : 0
New table with id : 1
First Standard VESA Table at offset 0x7cbb
Second Standard VESA Table at offset 0x4909
Table #0 has 16 modes
Table #1 has 33 modes
Aspect Ratio is 5/4
Patching Table #0 : 
Mode 1024x768 -> 1280x1024 (1047 1183 1343 770 776 805)
Patching Table #1 : 
Mode 640x200 -> 640x512 (664 672 720 520 H- V+)
...
Mode 2048x1536 -> 2048x1638 (2144 2160 2048 1672 H+ V+)
Mode 768x480 -> 768x614 (798 814 864 623 H- V-)
LoadConfig: [hd(0,1)/Extra/Themes/Default/theme.plist] 2699 bytes.
Resolution : 1280x1024 (Graphics Mode key)
LoadConfig: [hd(0,1)/Extra/Themes/Default/theme.plist] 2699 bytes.
Found mode 1280x1024 in VESA Table
LoadConfig: [hd(0,1)/Extra/com.apple.Boot.plist] 773 bytes.
Setting boot-uuid to: 2EAC3377-72E2-358E-81C8-FBA427439D0F
Closing VBios
Table #0 : Freeing backup	[OK]
Table #0 : Freeing		[OK]
Table #1 : Freeing backup	[OK]
Table #1 : Freeing		[OK]
Freeing map			[OK]
LoadConfig: [hd(0,1)/System/Library/CoreServices/SystemVersion.plist] 479 bytes.
Loading Darwin 10.6
Loading kernel mach_kernel
LoadDrivers: /Extra/Extensions.mkext
LoadDrivers: /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext
LoadACPI: [hd(0,1)/DSDT.aml] 11844 bytes.
Using PCI-Root-UID value: 1
nVidia GeForce 9600 GT 512MB NV94 [10de:0622] :: PciRoot(0x1)/Pci(0x1,0x0)/Pci(0x0,0x0)
NVCAP: 04000000-00000300-1c000000-0000000a-00000000
@0,display-cfg: ffffffff
@1,display-cfg: ffffffff
LoadConfig: [hd(0,1)/Extra/SMBIOS.plist] 526 bytes.
Intel P35/G33 DRAM Controller [8086:29c0] at 00:00.0
Frequency detected: 480 MHz (960) Dual Channel 
CAS:5 tRC:5 tRP:5 RAS:16 (5-5-5-16)
Slot: 1 Type 19 2048MB (DDR2 SDRAM) 960MHz Vendor=Kingston
     PartNo=2G-UDIMM SerialNo=BACCBB70
Slot: 3 Type 19 2048MB (DDR2 SDRAM) 960MHz Vendor=Kingston
     PartNo=2G-UDIMM SerialNo=BACCC370
Patched DMI Table
Found SMBIOS System Information Table 1
Customizing SystemID with : 00000000-0000-0000-0000-001d7dd11bf3
LoadACPI: [hd(0,1)/DSDT.aml] 11844 bytes.
FADT: Restart Fix applied !
Found ACPI CPU: CPU0
Found ACPI CPU: CPU1
Found ACPI CPU: CPU2
Found ACPI CPU: CPU3
Voltage: min= 1037mV, max= 1112mV
P-State: Added [Frequency 3000 MHz, FID 0xa, VID 0x20]
P-State: Added [Frequency 2700 MHz, FID 0x9, VID 0x1f]
P-State: Added [Frequency 2400 MHz, FID 0x8, VID 0x1d]
P-State: Added [Frequency 2100 MHz, FID 0x7, VID 0x1c]
P-State: Added [Frequency 1800 MHz, FID 0x6, VID 0x1a]
Patched ACPI version 1 DSDT
Starting Darwin x86_64

What never changed and always shown was

CPU: CPUFreq: 1800MHz = lowest MHz (6*300), same as in Systeminfo and CPU-X

With my dsdt Pstates also never changes , but in this case stays at max MHZ, 3.00 GHz

The 1800 MHZ is a bit ???, because the FSB=300 was detected right !

I tried to use FixFSB=Yes and the FSB was detected WRONG as 266 (without FixFSB OK as 300), BUT the CPU: CPUFreq: rised from 1800 to 2.7 GHz ???

There must somewhere an little bug, perhaps that comment what FixFSB makes: less(wrong) FSB but higher CPUFreq = cant be, may help to find that.

My hint: Can it be you compute that(for my knowledge fixed CPU MHz) wrong, by using lowest Pstate 6*FSB insted of highest Pstate 10*FSB, because FSB was detected right without any Fix or ForceFSB.

THANKS

valv · November 14, 2010

please test it with ForceFSB and busratio keys;

remember: for ForceFSB use 300 and 10 for busratio.

Or 9 for busratio and 333 as ForceFSB

mitch_de · November 14, 2010

OK, i will try. I only tried FixFSB which does more bad (300 MHz was detected as 266)

Also check my last comment (My hint), perhaps the solution for the 1.8 GHz (fixed) CPU MHz.

valv · November 14, 2010

My hint: Can it be you compute that(for my knowledge fixed CPU MHz) wrong, by using lowest Pstate 6*FSB insted of highest Pstate 10*FSB, because FSB was detected right without any Fix or ForceFSB.

THANKS

yeah indeed, I have found that straight as u where righting; gonna correct it now; sorry for this dumb mistake

p.s: also FKA's request about Vervet fb where added

Edit: attachment moved to first post

Mohamed Khairy · November 14, 2010

hi valv

can you replace ati.c with linked one

i want to test your bootloader but cant as framebuffer for my card is vervet

thanks valv

ati.c.txt

valv · November 14, 2010

hi valv
can you replace ati.c with linked one

i want to test your bootloader but cant as framebuffer for my card is vervet

thanks valv

ati.c.txt

hi Mohamed,

taken into account; btw, would u mind trying the 5.0.3 one

Mohamed Khairy · November 14, 2010

hi Mohamed,
taken into account; btw, would u mind trying the 5.0.3 one

sure i will try it

i tested 5.0.3 and card works good with vervet and there are three displays

put appear that you dont support any thing for amd cpus and MB

here bootloader log

LoadConfig: [hd(0,1)/Extra/com.apple.Boot.plist] 507 bytes.
CPU: Vendor/Family/ExtFamily: 0x68747541/0xf/0x1
CPU: Model/ExtModel/Stepping: 0x4/0x0/0x2
CPU: MaxCoef/CurrCoef:		0x0/0x0
CPU: MaxDiv/CurrDiv:		  0x0/0x0
CPU: Multiplier x10:		  0
CPU: TSCFreq:				 3210MHz
CPU: CPUFreq:				 0MHz
CPU: FSBFreq:				 0MHz
CPU: NoCores/NoThreads:	   1/4
CPU: Features:				0x36800221
Chipset is UNKNOWN (pci id 0x96001022)
We have an AtomBios Card
Creating 1 Mode Tables
New table with id : 0
Standard VESA Table at offset * 0x12
Using DTD Format modelines
Aspect Ratio is 16/10
Patching Table #0 : 
Mode 320x200 -> 320x900
LoadConfig: [hd(0,1)/Extra/Themes/Default/theme.plist] 2798 bytes.
Resolution : 1440x900 (Graphics Mode key)
LoadConfig: [hd(0,1)/Extra/Themes/Default/theme.plist] 2798 bytes.
Found mode 1152x864 in VESA Table
LoadConfig: [hd(0,1)/Extra/com.apple.Boot.plist] 507 bytes.
Setting boot-uuid to: FC69FA2C-BC0F-3224-912F-9A17D0BDB9C2
Closing VBios
Table #0 : Freeing backup	[OK]
Table #0 : Freeing		[OK]
Freeing map			[OK]
LoadConfig: [hd(0,1)/System/Library/CoreServices/SystemVersion.plist] 479 bytes.
Loading Darwin 10.6
Loading kernel /Extra/mach_kernel
LoadDrivers: /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext
No DSDT found, using 0 as uid value.
Using PCI-Root-UID value: 0
ATI VGA Controller [1002:68b8] :: PciRoot(0x0)/Pci(0x2,0x0)/Pci(0x0,0x0) 
old pci command - 7
boot display - 0
dumping pci config space, 256 bytes
Found bios image
Adding binimage to card 68b8 from mmio space with size f600
LoadConfig: [hd(0,1)/Extra/SMBIOS.plist] 1077 bytes.
Patched DMI Table
Found SMBIOS System Information Table 1
Customizing SystemID with : e013001e-8c00-01da-754e-00248c85d040
Not an Intel platform: Restart Fix not applied !!!
Not an Intel platform: Restart Fix not applied !!!
Patched ACPI version 2 DSDT
Starting Darwin x86

thanks valv for you work

i hope that you support AMD cpus and chipsets

valv · November 14, 2010

i hope that you support AMD cpus and chipsets

who told u about my todo list

warm...warmer...

Mohamed Khairy · November 14, 2010

who told u about my todo list warm...warmer...

it will be good and all AMD pc owner will give you alot of thanks

thanks valv again

The Edge3000 · November 15, 2010

Could I please get some confirmation that I am installing this correctly?

I followed the EFI installation guide linked in the first post, but the only files it mentioned were boot, boot0, and boot1h?

Were do all the rest go? What about boot.sys?

I ended up placing all the files in the /Volumes/EFI/usr/standalone/i386 folder, and got it to boot up into the GUI - but as soon as it starts to boot verbose it runs through a bunch of text and then boot loops. Without the GUI theme, it hangs at "Starting x86_64"

I've tried it without dsdt, boot.plist, Extra folder entirely, each with a different variation of not booting OS X.

bdmesg yields no readout.

Latest Chameleon 2 RC5 installer package works 100% on my system.

MadMungo · November 15, 2010

Hey Valv.

No go with GraphicsEnabler and my ati5970 instant reboot & 100% fan.

Works properly with Kaybls boot file, can you add support please

{ 0x1002689C, "Uakari"},

Thanks

oSxFr33k · November 15, 2010

@valv,

Thanks for this great release. No more having to bother with DSDTs.

My system reboots right after it reads the memory. So it boots up to the Chameleon level reading the memory and I don't know at which point it just reboots? No Kernel log so it never gets to a kernel boot portion.

I had Mozo's R627 in there and did the manual install using formerlyknownas guide starting with "newfs_hfs -v EFI /dev/disk0s1" I always install manually always no matter what!!

Does it matter that I used fdisk440 instead of just fdisk? I am using the default theme from Mozo's could this be cauing any issue?

Anyhow here is my com.apple.Boot.plist:

        <key>Boot Banner</key>
       <string>No</string>
       <key>GenerateCStates</key>
       <string>Yes</string>
       <key>GeneratePStates</key>
       <string>Yes</string>
       <key>Kernel</key>
       <string>mach_kernel</string>
       <key>Kernel Flags</key>
       <string></string>
       <key>GraphicsEnabler</key>
       <string>yes</string>
       <key>EthernetBuiltIn</key>
       <string>yes</string>
       <key>Timeout</key>
       <string>5</string>
       <key>Rescan</key>
       <string>Yes</string>

I tried -v -x no luck.

What other default settings are there besides HPET which is the most important thing in order to boot without panic.

In other words do I have to enable any more settings than the ones I have already in the com.apple.Boot.plist?

Does Boot.sys and bdmesg need to go into the /volumes/efi as well?

Thanks

EDITED A LITTLE WHILE LATER:

wait=yes is not working in com.apple.Boot.plist so I just hit the shift+Pause to catch the messages. I don't have a DSDT which is what I thought the purpose of this was or am I wrong? It finds everything it needs to find as far as I know? I removed the themes folder. I kept the boot.sys and bdmesg in there but with our without them it reboots still. I even tried my DSDT.aml I was using before and I still get a reboot.

I read over the release notes again and noticed you introduce some injection boot-time temperature plus tjmax injection. I am using Mozo's FakeSMC and Hardware sensor kexts in /efi/extra/extensions/IntelThermal NvClockxx and SuperIo.

I have not tried removing them yet but could that be the problem?

Here are some of the messages toward the end of the Chameleon boot I see before the PC reboots:

It Reads the memory and prints the name Corsair

Patched DMI Table

Smbios Table 1 found

Customizing System ID with (String of Numbers)

Found ACPI CPU 1-4

Right after that I can't catch any final message it reboots

valv · November 15, 2010

@The Edge3000,

try installing with the rc5 installer, and just replace the boot file (only)

@oSxFr33k, if mozo's r-627 worked for you then get it back and only then, replace the boot file (only).

Regarding the default settings, everything is on the boothelp.txt file.

I read over the release notes again and noticed you introduce some injection boot-time temperature plus tjmax injection. I am using Mozo's FakeSMC and Hardware sensor kexts in /efi/extra/extensions/IntelThermal NvClockxx and SuperIo.

I have not tried removing them yet but could that be the problem?

do not remove your kexts. The temperature feature is not an injection: it does take effect only at boot time and then vanishes, without interacting with the system.

@all, do not remove the Themes folder if u need the Gui; and don't forget to give the name of the desired theme on boot.plist.

@MadMungo, will fixed at next release

JBraddock · November 15, 2010

Guys, do you know how to troubleshoot a kernel panic, which happens during the boot. I don't have a camera so I can't take a picture. Is there a way to make it appear on the Console?

mitch_de · November 15, 2010

Depends on your system and what you have done.

First setup BIOS as non OC System (FSB normal, multipiler normal).

Also, if you had dsdt Pstates method running before and now tried autopastates its not good, if you didnt removed any dsdt Pstates injections BEFORE using autogen Pstates(+Cstates)

I would also try to switch of Pstate gen + CstateGen (both no) if removing dsdt pstate didnt helped.

JBraddock · November 15, 2010

Depends on your system and what you have done.
First setup BIOS as non OC System (FSB normal, multipiler normal).

Also, if you had dsdt Pstates method running before and now tried autopastates its not good, if you didnt removed any dsdt Pstates injections BEFORE using autogen Pstates(+Cstates)

I would also try to switch of Pstate gen + CstateGen (both no) if removing dsdt pstate didnt helped.

Thanks mitch_de.

Actually, my KP is not related to any of those. I don't use those method. I am using SSDT tables and Legacy ACPI_SMC_PlatformPlugin. But from time to time, I get KP during the boot and I don't know why it is/was happening.

Today, I noticed that my legacy kext doesn't have OSBundleLibraries in it. I copied this key from the vanilla one and restart the machine. The following error message disappeared from the Console:

Not loading kext com.apple.driver.ACPI_SMC_PlatformPlugin - not found and kextd not available in early boot.

But further testing is needed. I am not sure if this solves the problem or the above-mentioned error is gone completely. (OSBundleRequired is set to Safe Boot, as it is in vanilla one.)

One last question: Should I have OSBundleLibraries for every legacy kext I am using. I know that some of them don't load without them. Any ideas?

mitch_de · November 15, 2010

"Thanks mitch_de.

Actually, my KP is not related to any of those (OCed system?). I don't use those method. I am using SSDT tables and Legacy ACPI_SMC_PlatformPlugin. But from time to time, I get KP during the boot and I don't know why it is/was happening. "

If you get KPs from time to time - without changing any software, its 99% an instable hardware problem(include BIOS update) by OC Problem, RAM, power supply.

So do you have OCed the CPU / RAM clock or not ? If yes fits you shoudl try if the system gets more stabe with less or no OC cpu/RAM clock.

Also some beta BIOS updates may make system instable - even if it worked before with same settings perfect

Example: My GA EP35 gets instable (KPs or even reboots) with BIOS 5b - with BIOS 5a same settings runs well! (last offical was Bios 4)

AnVAL (ACPI Loader)

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites