AnVAL (ACPI Loader)

[JBraddock]

"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)

No. I didn't update my bios over a year and neither overclock the cpu. I am using the laptop in my signature and to my observation, KP occurs right before loading "AppleIntelCPUPowerManagement: initialization complete". OSX loads the firewire device and then tries to initiate intel power management and right before AppleIntelCPUPowerManagement, KP occurs. Anyway, I'll test the change I made and see if it makes any difference. Also I'll try to capture a screenshot.

 

Thanks,

[ivik]

Is it possible to disable memory detection? It hangs on acer.

[valv]

@JBraddock, could it be that the last SBUS code below is somehow struggling

                Device (DVL0)
               {
                   Name (_ADR, 0x57)
                   Name (_CID, "diagsvault")
               }

I remember having had bad times with this a time ago.

 

@Ivik, it is up to you. the feature is disabled by default. All u need is remove the UseMemDetect key out of the boot.plist.

[ivik]

Hm... without that key it hanged. If that key is set with No, it boots oke.

 

And after deepsleep i can see Wake kernel message. I don't see this with some older boot.

[JBraddock]

@JBraddock, could it be that the last SBUS code below is somehow struggling

              Device (DVL0)
               {
                   Name (_ADR, 0x57)
                   Name (_CID, "diagsvault")
               }

I remember having had bad times with this a time ago.

I doubt it but again I'll test it as well. By putting OSBundleLibraries in Legacy Kext, now I don't see this error. I tried for a couple of times.

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

After the Firewire device being loaded, the initialisation of power management is way faster than before and I don't see Waiting for DMOS message. It only says DMOS arrived. So, I guess OSBundleLibraries does something here. But it is too early to tell if this is the answer to my problem.

[valv]

So, I guess OSBundleLibraries does something here. But it is too early to tell if this is the answer to my problem.

Then now, we 're on the same boat

[oSxFr33k]

@valv,

 

Still no go with creating EFI with Mozo or Your i386 library. The Asus Rampage just reboots.

 

Two Questions. First one, I am using the themes from Mozo release and no matter what I do it does not show up, with key=themes string=default. With or without the Key and string in the com.apple.Boot.plist. I just see some Intel Logo that has some horizontal white layering and to hit Tab key and thats it. Its difficult to make out the options from that screen.

 

Second Question. With your Chameleon release, is a DSDT still necessary? I apologize if that is a stupid question but with the title "ACPI" I am assuming your release pulls the DSDT table from the ACPI tables and does all the relevant (default) fixes dynamically such as HPET, RTC, TMR etc etc.

 

 

Thanks

[valv]

@oSxFr33k, did any rc5 release work on your system last time ? If not, maybe relying on the (unofficial) installer over there should make things simpler for you.

Second Question. With your Chameleon release, is a DSDT still necessary? I apologize if that is a stupid question but with the title "ACPI" I am assuming your release pulls the DSDT table from the ACPI tables and does all the relevant (default) fixes dynamically such as HPET, RTC, TMR etc etc.

nifty but not true (yet); the loader still needs your edited (patched) tables.

[mitch_de]

to valv:

Sorry for delay testing latest 5.0.3

Q: Does the autogenerate Pstate Code looks after the key busratio ?

I aks because if not (Pstate always gen about what CPU normally has, like 10*...6*) , i must change my BIOS FSB setting from 333*9 to 300*9 to avoid KP if Pstate gen made an 10*333 = 3333 (KP).

Until now (RC5, 5.0.2), the autogen does always use PState 0=10* ...6* insted of 9*....6*.

Would be great if 5.0.3 does this :

if busratio

set Pstate max. multi to busratio // Pstate max = 9

enfd if

In my case i would set busratio=90 (9*) and PStates are now 9*...6* and avoid 10* (KP with my FSB 333)

[oSxFr33k]

@valv,

 

All the RC5's worked for me including the ones Mozo started back several months ago starting thread at ProjectOSX.

 

I also used some of your earlier releases few months ago, then after I had seen they were releasing loaders that supported C and P states, I started using those loaders.

 

I can't figure out exactly why I get an immediate reboot, before the kernel kicks in. If the kernel started to boot I would have kernel logs of it and I don't?

[FKA]

Hay valv

 

Sorry for delay been a bit busy.

 

Working fine here, havent had chance to test much but liking the Auto resolution function.

Will play around a bit more over next few days

 

Cheers

D

[bulier]

Is anybody who can tell me how I can make this play together with the bootthink or Chameleon?

[Maniac10]

@FKA: did you managed to get the graphics enabler to work for your HD5770? I can't boot with GE on. Maybe I need to dump my bios and load it with chameleon.

[Azimutz]

Hm... without that key it hanged. If that key is set with No, it boots oke.

 

And after deepsleep i can see Wake kernel message. I don't see this with some older boot.

Ivik, Valv is just distracted you do have to use UseMemDetect=n.. the detection is enabled by default.

And yeah, it seems you're not alone; some laptops have troubles with memdetect, or the other way around

but most don't hang, just show incorrect or incomplete info.

[FKA]

@FKA: did you managed to get the graphics enabler to work for your HD5770? I can't boot with GE on. Maybe I need to dump my bios and load it with chameleon.

 

Latest version works fine with 5770.

Just using:

 

<key>GraphicsEnabler</key>

<string>Yes</string>

<key>AutoResolution</key>

<string>Yes</string>

 

No need for UseAtiROM. As ever make sure you have Graphics Update 1.0 installed and remove ati_init.kext

 

D

[Maniac10]

Well, I tried with and without AutoResolution but I can't boot, it's just a black screen and the fans go mad, just like with an older chameleon. The only way I can boot is with GE=No, so it's got to be that my video card is not supported, or that chameleon won't load the correct fb. Is there an option to select it? Vervet always worked for me. Right now I'm running 10.6.5 and using kabyl's boot, so I'm sure it's not software-driver related.

[FKA]

Well, I tried with and without AutoResolution but I can't boot, ..............

 

autoresolution wont help it boot - purely cosmetic!

[Mohamed Khairy]

try put rom on extra and you can also update to 10.6.5 it works smooth also

[valv]

Does the autogenerate Pstate Code looks after the key busratio ?

...In my case i would set busratio=90 (9*) and PStates are now 9*...6* and avoid 10* (KP with my FSB 333)

Look carefully: first, the busratio key way of input did change since 5.0.1. Now if for example u need 9.5 u write 9.5

(so no more 95).

And yes, pstates auto-generator looks for that key, if it is present. If not it behaves normally. Try it, and give feedback.

 

Well, I tried with and without AutoResolution but I can't boot, it's just a black screen and the fans go mad, just like with an older chameleon. The only way I can boot is with GE=No, so it's got to be that my video card is not supported, or that chameleon won't load the correct fb. Is there an option to select it? Vervet always worked for me. Right now I'm running 10.6.5 and using kabyl's boot, so I'm sure it's not software-driver related.

am afraid u did not test 5.0.3. Did you?

 

 

Ivik, Valv is just distracted

Thank u

[DariosF]

with your bootloader my pc is recognized as 1.92 ghz instead 3.2 ghz...I've i7 920-

[Maniac10]

@FKA: hehe, thought it was something else

@Mohamed Khairy: Yes, I could do that but I was wondering why it works with kabyl's and not this one

@valv: Yes, I've tried 5.0.3 yesterday with the same result. Maybe there's something different in my setup.

 

This is my graphics card:

01:00.0 VGA compatible controller: ATI Technologies Inc Unknown device 68b8 (prog-if 00 [VGA controller])
Subsystem: XFX Pine Group Inc. Unknown device 2991

[mitch_de]

Look carefully: first, the busratio key way of input did change since 5.0.1. Now if for example u need 9.5 u write 9.5

(so no more 95).

OK, but what use for 9? 9.0 or simple 9 ?

Thanks

[kizwan]

with your bootloader my pc is recognized as 1.92 ghz instead 3.2 ghz...I've i7 920-

To get the maximum processor frequency for Intel Core i3, i5 & i7, I think valv need to implement this calculation in the bootloader (example):-

Core i7-740QM

Turbo 1/1/6/9

first number is the multiple of 133.33 MHz supported when four cores are active, the second number is the multiple for three cores, the third number is for two cores, and the fourth number is for one active core.

Normal operating frequency is 1.73 GHz = 1730 MHz

* With 3 or 4 cores active: to 1.863 GHz —————> 1730 + 1 x 133.33 = 1730 + 133.33 ≃ 1863.33

* With 2 cores active: to 2.529 GHz ———————> 1730 + 6 x 133.33 = 1730 + 799.98 ≃ 2529.98

* With only 1 core active: to 2.929 GHz —————–> 1730 + 9 x 133.33 = 1730 + 1199.97 ≃ 2929.97

So, for the boot loader to report maximum processor frequency, need to calculate the last/maximum turbo ratio, in this example is 9 with the current/overclocked Bus Speed. This way it will report correct maximum processor frequency.

[audio01]

Hi,

 

This Chameleon "branch" project looks very interesting, but it seems I can't find the needed information to understand exactly how it works. I read the first post completely and practically all the 39 pages of the thread, also read its English section of darwinx86.net and still there's a lot of info missing.

 

I would like to know if there's some kind of introduction about this alternative way of injecting the ACPI tables. Or at least a more detailed explanation of each of the com.apple.Boot.plist options (there are many new) and their value format.

 

Also I would like to know what are all those different files in the AnVAL releases that aren't normally in Chameleon releases, like boot1f32, boot1he, boot1hp, etc.

 

Thank you very much!

[valv]

OK, but what use for 9? 9.0 or simple 9 ?

Thanks

simple 9

 

 

@kizwan, the Turbo ratio limit calculation is already there, but not in the way you specified it. Could u tell the sources from where you've got these infos, thanks. Also am afraid that if we permanently stick with the 1 core only max freq, the turbo ratio limit would have no effect anymore (not sure).

I added a couple of verbosity lines to 5.0.3 (Turbo ratio limit related) on the attached archive. Try it and give your bdmesg(S). Thanks

i-series owners can (since 5.0.1) use the ForceFSB and busratio injection keys.

 

@MadMungo, your request has been answered on the above archive

 

@Audio01, BootHelp.txt