AnVAL (ACPI Loader)

[Time2Retire]

@valc: Why don't you read the EDID to set the resolution? Less code and much easier this way.

[kizwan]

@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).

My source is Wikipedia.

- List of Turbo Ratios

- Calculation of Turbo Boost

I'm using Chameleon 2 RC5 right now & my i7-720QM & i5-450M speed is correct (normal operating frequency, not the maximum Turbo Boost frequency). I think in the DariosF's case, I think there is no problem with the detection of processor frequency. Since DariosF overclocked the processor, the boot loader instead detecting the normal operating frequency, it detect & report back the current processor frequency. Basically, his processor performed as it should be (Speedstep & Turbo Boost). This is just my theory though. Maybe DariosF can confirm whether the processor under-performed or not. Yes, you have a point there about stick with one core.

 

I'm going to try yours & post the bdmesg here.

 

P/S: Just if someone confused with normal operating frequency & maximum Turbo Boost frequency:-

For example Intel® Core™ i7-920:-

- Normal operating frequency = 2.66 GHz

- maximum Turbo Boost frequency = 2.93 GHz

[kizwan]

@valv

 

I just tested on my Dell Studio with i7-720QM. In the System Profiler, the processor frequency is detected as 933MHz as opposed to 1.6GHz (normal operating frequency) with RC5. I'm using the MSR Tools to monitor the processor frequency & I can see, like with RC5, the processor frequency changes between 0.96GHz - 2.57GHz. So, I think the processor is not under-performed. Going to try with Xbench later. Just for information, my com.apple.Boot.plist is very simple, just arch=i386, SMBIOSDefault, Timeout & Legacy Logo. These are RC5 & AnVAL5.0.3 bdmesg:-

RC5.txt

AnVAL.5.0.3.txt

 

Hope it will helps you in the AnVAL development. Let me know if you need anything else.

[valv]

@kizwan, please try using the one from my last post. it should give some verbosity about the Turbo ratio limit.

Thank u

[kizwan]

@kizwan, please try using the one from my last post. it should give some verbosity about the Turbo ratio limit.

Thank u

Sorry, I got lost earlier. This is bdmesg with boot file from your last post. I hope you don't mind I labeled it AnVAL5.0.3_Beta:-

AnVAL.5.0.3_Beta.txt

With this boot file, the processor frequency also reported as 933MHz in System Profiler. However, the processor is not under-performed (monitored with MSR Tools). Already tested with Xbench, the scores with RC5, AnVAL 5.0.3 & AnVAL 5.0.3_Beta are almost the same.

[valv]

@kizwan, that explains many things; I rely on u to test the next one:[attachment=Archive2.zip]

p.s: do not use busratio key with this one, it'd give wrong values. Also don't rely on the auto-gen pstates. Thank u very much

[FKA]

@valc: Why don't you read the EDID to set the resolution? Less code and much easier this way.

 

I think it does read the EDID?!

[valv]

I think it does read the EDID?!

yep, it does

[kizwan]

@valv,

 

This is new bdmesg with new boot files:-

AnVAL.5.0.3_Beta2.txt

Now, processor frequency in System Profiler is correct which is 1.6GHz (normal operating frequency). Everything as usual.

[Time2Retire]

yep, it does

Oops. Stupid me. I missed the #include "edid.h" (hard to read in a browser).

So how do I pull the source code? I found "How To Get The Code" but that appears to link to the trunk. No?

 

Edit: I think I've got it already.

 

svn co -r HEAD http://forge.voodooprojects.org/svn/chameleon/branches/autoResolution

[audio01]

@Audio01, BootHelp.txt

 

Hi, thank you for your reply. I already read the included BootHelp.txt (this is the first thing I always do) but the information is very scarce. Any other place where I can find about the way this bootloader is working? (in a different way than the Chameleon RC5 from the main trunk). There're a lot of new options and I can't documentation about them.

 

Also I would like to know what are the different Boot1 versions (I already know the usual ones, but there're a few new) and what's the boot.sys file?

 

BTW I'm also very interested in the way you inject the graphics card, specially the display-cfg method. It looks like it works pretty well, at least I can have mirrored displays that I couldn't have even with NVEnabler. I remember asking you in the Voodoo Projects Dev's patches forum about the implementation of this and your answer was that you implemented it but didn't uploaded it to the repository.

 

Thank you! Cheers!

[kizwan]

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.

Actually those files (boot1f32, boot1he, boot1hp, etc) also exist in main Chameleon 2 RC5 release.

[eberts]

rom "characteristics" and "rom-size" smbios injection

 

How do we inject those keys? SMCharacteristics, SMRom-size ?

 

Thx

[valv]

Please help by testing Archive3 on first post

How do we inject those keys? SMCharacteristics, SMRom-size ?

with smbios.plist, e.g:

[audio01]

Hi,

 

Actually those files (boot1f32, boot1he, boot1hp, etc) also exist in main Chameleon 2 RC5 release.

 

Ok, "all" those files aren't in the main Chameleon build but I found them in the official trunk (source). I guess they're deprecated. I undestand that they're different versions of the boot1 stage loader. Anyway, I was looking for a friendly answer just pointing the right direction where I could find more info about those "new" files. Like boot.sys is still a mistery.

 

Also I was looking about the new keys (and their values' format) that can be used in com.apple.Boot.plist. There're a lot and can't find more information than the sole mention in the BootHelp.txt file. If there's any documentation available I would like to know.

 

Thank you very much. Cheers!

[kizwan]

Ok, "all" those files aren't in the main Chameleon build but I found them in the official trunk (source). I guess they're deprecated. I undestand that they're different versions of the boot1 stage loader. Anyway, I was looking for a friendly answer just pointing the right direction where I could find more info about those "new" files. Like boot.sys is still a mistery.

Well, my answer is based on the Chameleon RC5 package from this thread. I have use two files; boot1h & boot1f32. For example on, on GUID/GTP disk, if the EFI partition is FAT32 filesystem, boot1f32 will be used, while if the EFI partition is HFS filesystem, boot1h will be used. So, I don't think, at least boot1f32 is deprecated. My reply strictly about the files you mentioned, not the manual/documentation. I even don't have them. If I understand your words correctly, you found my reply is not "friendly" which I'm very shocked because I do chose my words carefully.

 

Have a nice day!

[valv]

Ok, "all" those files aren't in the main Chameleon build but I found them in the official trunk (source). I guess they're deprecated. I undestand that they're different versions of the boot1 stage loader. Anyway, I was looking for a friendly answer just pointing the right direction where I could find more info about those "new" files. Like boot.sys is still a mistery.

sorry, look here: trunk/i386/boot1 from file headers:

; Partition Boot Loader: boot1f32

;

; This program is designed to reside in sector 0 of a FAT32 partition.

; It expects that the MBR has left the drive number in DL

; and a pointer to the partition entry in SI.

;

; This version of boot1f32 tries to find a stage2 boot file in the root folder.

;

; Written by mackerintel on 2009-01-26

Partition Boot Loader: boot1h extended sectors

;

; This program is designed to reside between sectors 40-47 of a block device.

; It expects that the partition boot loader left the drive number in DL

; and a pointer to the partition entry in SI. Starting sector of this loader

; should be passed in ECX.

;

; This version of boot1he tries to find a stage2 boot file in the root folder.

;

; Written by zef @ 2008-04-17,

; updated with large boot file loading support @ 2008-10-27

;

; NOTE: this is an experimental version with multiple extent support.

; Partition Boot Preloader: boot1hp

;

; This program is designed to reside in sector 0 of an HFS+ partition.

; It expects that the MBR has left the drive number in DL

; and a pointer to the partition entry in SI.

;

; This version of boot1hp tries to find a boot1h extended loader.

; If it fails then uses the traditional method by loading the startupfile.

;

; Written by zef @ 2008-04-17

boot.sys seems the same as the boot file but not usable on an hfs+ partition; other than that extension says it all.

cdboot...name says it all

chain0 is for chainloading with the help of Grub

 

hope this helped. Regarding a more accurate docu about the new keys, I thought the boothelp was expressive, as I explained usage with examples. Doesn't seem to be the case.

 

@Kizwan, take it easy dear, am sure his words wasn't meant to heart u. keep it up , and what about your testing ? I know u're a valuable friend of AnVAL so don't leave us this way

[JBraddock]

Can I use the latest version only by replacing the boot file.

As I have bad experiences with Chameleon installation, I wouldn't want to mess with my installation. I need my SnowKitty to work on

 

Also, @Valv, since you guys brought that boot files up, I would like to mention something else. May be it's been already fixed but I remember while using RC4, I had a weird issue.

 

At the time, I had three partitions on my HDD, one being root, another one being formatted with HFS+ and the last one with NTFS. Since, NTFS is so slow to work on, I reformatted with HFS+. I didn't mess with anything else. Once I rebooted the machine I got "can't find mac_kernel error".

 

Anyone can confirm this?

[valv]

Can I use the latest version only by replacing the boot file.

yep, better would be to test things from an usb boot drive (that's the way I do it), just to avoid any mess.

I didn't mess with anything else. Once I rebooted the machine I got "can't find mac_kernel error".

did u rely on partimage or so for formatting? It is known to change boot flag and break things.

[JBraddock]

Did u rely on partimage or so for formatting? It is known to change boot flag and break things.

Sorry, I didn't understand what you meant by partimage or formatting?

I'd just reformatted the third partition and restarted. That was it. It could be something to do with the installer I'd used. May be, it'd checked and seen that I had a NTFS partition and did something with it. Reinstallation of Chameleon'd solved the problem.

[valv]

I didn't understand what you meant by partimage or formatting?

sorry, I meant partedmagic or any third party tool to format

[JBraddock]

sorry, I meant partedmagic or any third party tool to format

I'd used Disk Utility alongside with NTFS-3G 2010 for NTFS read/write

[mitch_de]

Hi valv !

Great to see version Archive3.

I can see new key PStates= (number of pstates).

Am i right that it would do such way:

I get P6,P7,P8,P9, P10 Pmultiplier, 5 Pstates with normal autogen Pstates

set this key to 4, i will get only first 4 (from low MHZ seen) Pstates

P6,P7,P8,P9 no P10?

[valv]

@mitch_de,

this was already there since 5.0.1 but,

if u specify 5 as value only the first 5 would be taken into account: p0(max frequency)...p4(lesser frequency). so for example if your pstates have the following cpu frequencies:

p0 --> 2500Mhz
p1 --> 2300Mhz
p2 --> 2100Mhz
p3 --> 1900Mhz
p4 --> 1700Mhz
p5 --> 1500Mhz
p6 --> 1300Mhz

by specifying 5 as a value of PStates key u would be provided with p0 to p4, but not p5 neither p6. Hope it is clear now.

[mitch_de]

OK, i thought its other way : Pstates number would limit the highest possible PStates first, not the lowest possible PStates first.

So, in my case, i must disable P0 (fastest,10*), the solution would be to use busratio=9 (which affects also PStates gen) to avoid P0 (=10*FSB) and i dont need Pstates key ?