AnVAL (ACPI Loader)

[Azimutz]

Hum... finally i found why the Asere booter wouldn't give me memory detection... thanks Blackosx

That RC4 topic is full of nice info; all Chameleon recent history is there and i still didn't gone through it all.

I tested the booter compiled from source and didn't noticed the missing code.. damn noob! The pre-compiled version reads my RAM info very precisely, just the RAM speed is reported as 666MHz (it's missing 1MHz ). Anyway...

 

@valv, very pleased with what i've been reading here lately collaboration, both from you and from the guys testing. Props for all!

 

@00diabolic, still don't have anything new to help you so, i'm following the progress here and we'll see were it goes.

Just so you don't think i ditched helping you! I really need to look at the code to be able to do it and atm i have other priorities...

Hope you understand.

 

By the way, RestartFix defaults to "Yes" on all Intel cpu's. I have it defaulting to "No" on my test booter as i don't need it, restart works fine on my Intel.

[valv]

Hi Azimutz,

happy to see u again, please forgive me for what u know: time is really too short these days.

 

@00Diabolic ~~,

I was looking at the link u 've been posting earlier to efi-x. do u have those dumps? or maybe if someone is already registered there, he could get them for me. thanks,

[00diabolic]

@00diabolic, still don't have anything new to help you so, i'm following the progression here and we'll see were it goes.

Just so you don't think i ditched helping you! I really need to look at the code to be able to do it and atm i have other priorities...

Hope you understand.

 

By the way, RestartFix defaults to "Yes" on all Intel cpu's. I have it defaulting to "No" on my test booter as i don't need it, restart works fine on my Intel.

 

No Prob Azimutz.. I appreciate the help.. :-)

 

I think valv is close here.. alpha 4 almost had it nailed.. However I am seeing more issues as I run that one.. So looking for his next release..

[Aivarz]

...

u can verify if speed-step is working by typing this on terminal sudo ioreg -lw0 | grep CSTInfo if it outputs something like

" | | | | "CSTInfo" = 19147885"

c-states are ok, then if by typing this ioreg -lw0 | grep PerformanceStateArray it outputs some strings like this

" | | | "PerformanceStateArray" = (<00000000000000000a0000000a0000002b0b...)"

u can conclude speed-step is working.

...

 

And I just started to wonder where my c-states has gone. After a quick test I can confirm that I lost them with alpha5

[valv]

And I just started to wonder where my c-states has gone. After a quick test I can confirm that I lost them with alpha5

not good at all. please to confirm, revert back to 06/04 release and see if it is back.

[Aivarz]

That was exactly what I did to test.

[valv]

That was exactly what I did to test.

and what about alpha4, did it honor c-states?

[kizwan]

Ok gonna try this next. Also just FYI.. I do not need the system-type=2 flag at all. I just booted without it and my systemtype is detected as type 2 automatically. So thats good news :-)

My Dell Studio also don't need SystemType flag at all. system-type (value is 2) exist on my Dell Studio's ioreg with standard PC EFI 10.6 & Chameleon 2 RC4 boot file, even though "PM Profile" value is 00 in FADT/FACP table.

 

On Aspire 9420; however, I need to set "PM Profile=02" to get the system-type with value 2 visible in ioreg, therefore the battery will be properly recognized.

 

hey kizwan, I was waiting for your feedback, thank u for testing

No problem. Thank you for your work. I really appreciate it.

[valv]

My Dell Studio also don't need SystemType flag at all. system-type (value is 2) exist on my Dell Studio's ioreg with standard PC EFI 10.6 & Chameleon 2 RC4 boot file, even though "PM Profile" value is 00 in FADT/FACP table.

The system-type could then be injected from some kext maybe (or the bootloader's key is 2 by default).

btw, did you try alpha5 on your Dell Studio? If u do, look if your i7 is fully recognized (especially the fsb value)

[00diabolic]

@00Diabolic ~~,

I was looking at the link u 've been posting earlier to efi-x. do u have those dumps? or maybe if someone is already registered there, he could get them for me. thanks,

 

I'll try.. You mean the dumps posted by Siobhan right? I msged him or who I think he is on insanelymac (same name).. I'd hate to have to register for another forum I wont ever use but Ill do it if I dont hear from him.

 

Ill keep you posted.. It does seem that a lot of the work that AsereBLN has done is the same stuff your looking at now..

[Aivarz]

and what about alpha4, did it honor c-states?

 

Yes, c-states are in place with alpha4. Speedstep is working as it should.

[kizwan]

The system-type could then be injected from some kext maybe (or the bootloader's key is 2 by default).

btw, did you try alpha5 on your Dell Studio? If u do, look if your i7 is fully recognized (especially the fsb value)

Maybe but I'm unable to replicate the result on Aspire 9420 though. Both use standard Chameleon bootloader at that time & almost similar Extra kexts.

 

My test HDD (external HDD) which I use to test Mac OS X on Dell Studio is damaged, so I'm not able to test it for now.

[BuXb]

i have this message

 

unable to determine bios type

 

please run the program 'dump_bios' as root and email the file 'vbios.dmp' to stomljen@yahoo.com.

 

chipset:965gm

 

mode table offset : $c000 + $4307

same issue here with a Nvidia Geforce Go 7600 256MB on a board with a 945PM Express chipset, mode table offset : $C0000 + $40b4. Accdg. to the list on the first page the card is supported. Mine even has the same IDs 0x10DE0398. I still do have slight graphics issues even in 10.6.4 no matter with which EFI injector kext or plist device ID, so I would be very interested in having your bootloader detect my card and inject the correct EFI string.

 

'dump_bios' seems to be a Linux command because it does not exist in X. gpu-z saves the VGA BIOS as a bin file, Everest as text. I attached both to this posting. Shall I also send the dumps to stomljen@yahoo.com? Is he directly involved in your bootloader project, or are you just using his video rom computing module for the loader?

 

Thanks for your insights ,

Bugs.

EVEREST.Video.dmp.txt

gpu_z.zip

[valv]

@00Diabolic ~~,

don't stress your self for this, I was just wondering what info could be gathered from there as he seems to have the same cpu as yours.

 

Yes, c-states are in place with alpha4. Speedstep is working as it should.

Ok, it seems like the older code (alpha4) did it better.

 

Maybe but I'm unable to replicate the result on Aspire 9420 though.

 

My test HDD (external HDD) which I use to test Mac OS X on Dell Studio is damaged, so I'm not able to test it for now.

no problem.

[00diabolic]

My Dell Studio also don't need SystemType flag at all. system-type (value is 2) exist on my Dell Studio's ioreg with standard PC EFI 10.6 & Chameleon 2 RC4 boot file, even though "PM Profile" value is 00 in FADT/FACP table.

 

On Aspire 9420; however, I need to set "PM Profile=02" to get the system-type with value 2 visible in ioreg, therefore the battery will be properly recognized.

 

Ok cool.. One more question for you or valv..

 

I set RestartFix=no in boot.plist and my restart problems are gone. My question can I get rid of evoreboot.kext and possibly use RestartFix instead (if they do the same thing)?

 

I know I can not shutdown without evoreboot.kext and thats why I have it in the first place. If having RestartFix automatically applied caused me to have reboot problems but could that be because I also have evoreboot.kext? Or is that impossible?

 

I'm guessing there separate fixes and I only need one of them.

 

Thx

[rednous]

valv, just to report my C states, i was reading 2-3 pages back and saw the terminal command.

so my C states are working in one word alpha5 honors the SpeedStep (mine is implemented in the DSDT)

[Siobhan]

This might also be of interest valv. Guy has my problem but AsereBLN never looked into it. http://www.efixusers.com/showthread.php?t=...bln&page=32

 

Hey Diabolic - 'guy' is a girl, btw.

 

Anyway, I'm joining this thread at your request. Yes, I was having the 184MHz FSB issue with asere's bootloader, but at some point I fixed it somehow. I'll get involved with this bootloader variant in the next week or so when I'm less busy to see if I can help you verify/diagnose.

[kizwan]

I set RestartFix=no in boot.plist and my restart problems are gone. My question can I get rid of evoreboot.kext and possibly use RestartFix instead (if they do the same thing)?

 

I know I can not shutdown without evoreboot.kext and thats why I have it in the first place. If having RestartFix automatically applied caused me to have reboot problems but could that be because I also have evoreboot.kext? Or is that impossible?

I don't think shutdown fix is being implemented in AnVAL boot file but I might be wrong. Can you shutdown & restart with RestartFix=No + evoreboot.kext? If yes, keep it like this. Also can you shutdown & restart with only RestartFix=Yes or No (without evoreboot.kext)? If yes with either one, you can safely removed evoreboot.kext.

 

It is possible RestartFix=Yes (applied by default if you have Intel CPU) conflict with evoreboot.kext. When RestartFix=Yes, AnVAL boot file will patched the FADT/FACP table for restart fix. (My theory) I think when this happen it "panicked" the evoreboot where instead it fix restart/shutdown issue, it caused restart problem. (My theory) Since RestartFix=Yes & evoreboot.kext provide restart fix, it maybe conflicting with each other. This is the only explanation I can think off.

[00diabolic]

Hey Diabolic - 'guy' is a girl, btw.

 

Anyway, I'm joining this thread at your request. Yes, I was having the 184MHz FSB issue with asere's bootloader, but at some point I fixed it somehow. I'll get involved with this bootloader variant in the next week or so when I'm less busy to see if I can help you verify/diagnose.

 

Hey.. Sweet.. Thanks for checking this out.. Opps... Sorry for the mix up.. Girls are always welcome in this OSX madness.. :-)

 

I am really curious how you fixed your fsb issue. If you have some time and can tell me what steps you remember taking that would be great. i hope you did not just use smbios.plist as a solution. You may notice that all it does is simply cover over the problem. If you use a tool like voodoo monitor or run a few commands youl see that the speed is actually just as you left it. Smbios.plist at least for fsb is just a superficial fix.

 

THX

 

I don't think shutdown fix is being implemented in AnVAL boot file but I might be wrong. Can you shutdown & restart with RestartFix=No + evoreboot.kext? If yes, keep it like this. Also can you shutdown & restart with only RestartFix=Yes or No (without evoreboot.kext)? If yes with either one, you can safely removed evoreboot.kext.

 

It is possible RestartFix=Yes (applied by default if you have Intel CPU) conflict with evoreboot.kext. When RestartFix=Yes, AnVAL boot file will patched the FADT/FACP table for restart fix. (My theory) I think when this happen it "panicked" the evoreboot where instead it fix restart/shutdown issue, it caused restart problem. (My theory) Since RestartFix=Yes & evoreboot.kext provide restart fix, it maybe conflicting with each other. This is the only explanation I can think off.

 

Exactly what I was thinking.. I can restart now and shutdown with restartfix=no and evoreboot installed. I guess Ill have to try it the other way to see what happens and see if I can get rid of evoreboot.kext...

 

ThX

[Azimutz]

@valv,

no problem, i understand priorities and that stuff is still not completely stable.. taking care of it.

About the fsb thing, how about a override key? I tried to implement it but failed.. i know now at least one of the

reasons why it didn't worked (i'm noob! ), but i didn't tried it again. Since this 00diabolic problem seems to be very restrict,

maybe that would be a easier solution... just a thought...

[nobb1x]

my speedstep is working with alpha 5, as Valv suggested

 

bash-3.2# ioreg -lw0 | grep CSTInfo
| |   | |   "CSTInfo" = 19136773
bash-3.2# ioreg -lw0 | grep PerformanceStateArray
| |   | |   "PerformanceStateArray" = (<d0070000b88800000a0000000a000000230a0000230a0000>,<40060000a86100000a0000000a0000001a0800001a080000>,<b0040000983a00000a0000000a0000001106000011060000>)

 

i can see it working with voodoomonitor too,with the cpu sitted at the slowest step for the most of the time.

oh yes, my T6400 is detected runnning at 1.990 mhz, not the 2ghz as expected.

 

As offtopic note, i got an Asus laptop with the nvidia mcp79 chipset, on it the shutdown never work, the laptop hang

with dark screen but fan and power led turned on. Restart works only using evoreboot, i tried all the revisions of the loader and restartfix yes or no without any change, just evoreboot make it to restart.

[valv]

'dump_bios' seems to be a Linux command because it does not exist in X. gpu-z saves the VGA BIOS as a bin file, Everest as text.

hey Bugs,

try dumping with Diebuche's AnalyseVBios2

 

valv, just to report my C states, i was reading 2-3 pages back and saw the terminal command.

so my C states are working in one word alpha5 honors the SpeedStep (mine is implemented in the DSDT)

my speedstep is working with alpha 5, as Valve suggested

 

i can see it working with voodoomonitor too,with the cpu sitted at the slowest step for the most of the time.

oh yes, my T6400 is detected runnning at 1.990 mhz, not the 2ghz as expected.

Thank u for the reliable info. Somehow, the intel 23 (core 2 duo) models do not interact the same way with the actual detection algo. Thus and during the last two days I've managed to add some logic for those models into the code. It was hard to get rid of all the compile errors and warnings for someone with as little knowledge about asm as me. and finally I came up with this

Edit: link removed. boot not working

Ladies and Gentlemen, this one is almost a guess work. It'd help to know if that works for you.

Greetz

 

About the fsb thing, how about a override key?

not a bad idea at all. It'd be probably helpful to get it as a last resort after a detection failure.

[valv]

Exactly what I was thinking.. I can restart now and shutdown with restartfix=no and evoreboot installed. I guess Ill have to try it the other way to see what happens and see if I can get rid of evoreboot.kext...

would u mind posting your dsdt file ? I'd like to have a look into.

[00diabolic]

would u mind posting your dsdt file ? I'd like to have a look into.

 

Here you go..

dsdt.zip

[DariosF]

valv, with your last work (alpha6), i take black screen and no boot.