Jump to content

AnVAL (ACPI Loader)


valv
 Share

1,538 posts in this topic

Recommended Posts

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

oh, sorry for this.

did tried 06/04, alpha4 or alpha5? how did those work?

Link to comment
Share on other sites

valv, with your last work (alpha6), i take black screen and no boot.
black screen and hang for me too with alpha6 (i used an usb bootable stick to try it)

something went wrong! sorry guyz. alpha6 removed.

Link to comment
Share on other sites

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.

u see, am not sure it is "just a superficial fix.", and I did not interfere with that growing >point of few<, simply because I didn't found the best words to convince. till I remembered this: "Apple's code starts off with the assumption that the bootloader (which is typically Apple's own boot.efi) has filled in the FSBFrequency property of the "IODeviceTree:/efi/platform" node."

D.F.E

btw, take a look to mm67's post here, restart fix related.

Link to comment
Share on other sites

I've found another way to do execute the 23 models specific part of the detection algo. hope it works now

Edit: also this one were not good. even dangerous I'd say. alpha7 trashed. sorry

Greetz

Link to comment
Share on other sites

I've found another way to do execute the 23 models specific part of the detection algo. hope it works now

Greetz

 

Sorry, i have a quick n00b question please: If i have AsereBLN 1.1.9 installed, do i have to reinstall the "boot" file only or all the other files too?

 

And another one: the Chameleon installation manual you've posted earlier says about installing 3 files only (boot0, boot1h, and boot) , what should i do with the rest of the files here?

screenshot20100623at023.png

Thanks in advance.

Link to comment
Share on other sites

Sorry, i have a quick n00b question please: If i have AsereBLN 1.1.9 installed, do i have to reinstall the "boot" file only or all the other files too?
too much changes have found there way into files since old versions of chameleon. AsereBLN doesn't have those changes.

U need to replace all the files (like if u were starting a fresh install)

And another one: the Chameleon installation manual you've posted earlier says about installing 3 files only (boot0, boot1h, and boot) , what should i do with the rest of the files here?
those files are for other matters, u don't need them for now (do not remove them though). as of Distemperus's definitions:
  • boot & cdboot - stage2 booters; Chameleon binaries; cdboot is used to boot DVDs
  • boot0 - locates active partition & loads the partition booter for MBR & GUID/MBR hybrids
  • chain0 - loaded by another booter to jump booting yet another booter
  • boot1h - partition booter for HFS+ that loads the stage2 booter
  • boot1f32 - booter for FAT32 partitions on MBR
  • boot1he - booter for extended sectors
  • boot1hp - partition booter for HFS+ that finds a boot1h extended loader

Link to comment
Share on other sites

So basically i'm only installing the 3 files mentioned in Chameleon installation manual?
yep,

 

Does anyone have an insight as to why graphicsenabler doesn't support dual GFX cards?
just for reference,

"You need to consider the following facts

  • either you use NVEnabler (which has it's own issues) or you use a solution in your code base.
  • your code makes a single pass of the PCI bus without enabling all devices and associated configuration space.
  • the current register code is limited in functionality and access.
  • the current code does not work properly with multiple cards.
  • the nvidia code I provided has improved register functions (a quick look should show you this).
  • injecting vbios in most cases seriously damages performance and is not the recommended solution.
  • you do not build and inject NVMT data based on the DCB or PCT.
  • you do not capture or mark the active display port.
  • you do not provide an NVCAP that is NV_40 or NV_50 compliant.
  • you do not extract and inject EDID information for the active primary display port.
  • your current method does not properly configure additional nVidia cards."

BuildSmart

Link to comment
Share on other sites

Thanks Valv! :rolleyes:

 

Does anyone have an insight as to why graphicsenabler doesn't support dual GFX cards?

BTW, should it support both monitor outputs on single graphics cards? For some reason it never recognized the second DVI/VGA port, only the first one that close to motherboard. I've tried graphicsenabler with AsereBLN1.1.9 and Chameleon2RC5pre8 on 8400GS and 9500GT, one port always works fine and the other one usually gives a blue or black screen.

Link to comment
Share on other sites

Holy {censored} batman!

 

After installation of alpha7 - all system animations started running at double speed!

Starting with the startup spinning wheel (now it makes 2 rounds per second instead of one) and all progress bars running like squirrels on steroids, even the shutdown timer runs at double speed. Has anyone experienced anything like this?

Link to comment
Share on other sites

oh, sorry for this.

did tried 06/04, alpha4 or alpha5? how did those work?

 

Valv.. What happened to that DSDT file you posted for me? I never got to download it. What fixes were you thinking I needed?

 

Thanks

00D

Link to comment
Share on other sites

Valv.. What happened to that DSDT file you posted for me? I never got to download it. What fixes were you thinking I needed?
yeah I know, I took it out to avoid driving you into trouble. It is all about mm67's post.

 

After installation of alpha7 - all system animations started running at double speed!

Starting with the startup spinning wheel (now it makes 2 rounds per second instead of one) and all progress bars running like squirrels on steroids, even the shutdown timer runs at double speed. Has anyone experienced anything like this?

With what cpu model is that happening?

Link to comment
Share on other sites

E6500

GA-G41M-ES2L

8400GS/512MB

 

I'm using a generic DSDT from Kakewalk without a CPU section for this particular processor, in Extra i have FakeSMC and Legacy888bHDA only.

Link to comment
Share on other sites

E6500

GA-G41M-ES2L

8400GS/512MB

 

I'm using a generic DSDT from Kakewalk without a CPU section for this particular processor, in Extra i have FakeSMC and Legacy888bHDA only.

Not good at all. for your safety, go replace alpha7 with the one from 06/04. If anyone courageous would confirm this behavior ?

Link to comment
Share on other sites

u see, am not sure it is "just a superficial fix.", and I did not interfere with that growing >point of few<, simply because I didn't found the best words to convince. till I remembered this: "Apple's code starts off with the assumption that the bootloader (which is typically Apple's own boot.efi) has filled in the FSBFrequency property of the "IODeviceTree:/efi/platform" node."

D.F.E

btw, take a look to mm67's post here, restart fix related.

 

yeah I know, I took it out to avoid driving you into trouble. It is all about mm67's post.

 

About smbios So your saying the bootloader is responsible for the fsb being correct? I figure that was right. I know that some if not all of smbios.plist is superficial because I used to use netkas's applesmbios.kext and it use to calculate it the same way for me. It was wrong, then someone else came along with smbiosresolver I think superhai but all it did was clean up the misinformation that was collected simply to fix about this mac crashes. Later people realized this and started asking for locked values in smbios files because they noticed speed decreases if the info was really wrong. That is when a whole lot of people started compiling smbios files, Macnub, superhai, AnV etc. If the bootloader is supposed to fix the issue using all of the values in smbios.plist its not and maybe that part of the bootloader code needs to be updated first. It should force all values listed in that file but it does not. I can prove this through benchmarks. I am certainly losing speed.

 

UPDATE.. I decided to run another benchmark to see how much I'm losing in speed here and to prove that smbios.plist is just superficial.

 

Geekbench Score with 800fsb working full speed 3659

Floating Point Score 5338

Geekbench Score with 736fsb without smbios.plist fsb edits in place 3357

Floating Point Score 4861

Geekbench Score with corrected fsb in smbios.plist 3235

Floating Point Score 4680

 

There you have it. Proof that smbios.plist fsb edits do nothing at all.

 

On the DSDT/Restart fix...

I got it I think last night.. Is your mac user name tmacyunn? Anyway It has 90 optimizations and mine has only 83. I was able to compile it to a aml with DSDTSE. So I may be able to boot with it. Have not tried yet. What could be the problem in trying it? I see mm67 post but it looks like a good fix for shutdown? Is that the only change you made? Whats wrong with trying it out?

 

UPDATE: I tried the DSDT you gave me Valv and no boot. What other fixes were in there besides the restart fix? Can you tell me? It simply goes to a black screen at boot up. By the way I still have evoreboot installed.

 

 

I have tried alpha 7... Interesting results.. It has cut my bus speed in half.

 

CPU Clock: 1350 MHz

FSB Clock: 400 MHz

Bus Clock: 100 MHz

 

I also notice this like hyper icons that XLR is seeing. Its like everything is running faster then it should. The shutdown timer is fast also. The clock is also running faster then it should be. 2 mins just went by in a blink.

 

I have alpha 6 before you pulled it down. Is it completely bad? I was gonna give it a try and noticed alpha 7.

Link to comment
Share on other sites

Not good at all. for your safety, go replace alpha7 with the one from 06/04. If anyone courageous would confirm this behavior ?
The thing is I rely on your feedbacks to go further, because I actually have only one machine, and it is for development needs. I cannot afford losing time if something should happen: blindly coding.

whatever, the blind needs to have some sleep too. see ya later.

 

I have tried alpha 7... Interesting results.. It has cut my bus speed in half.

 

CPU Clock: 1350 MHz

FSB Clock: 400 MHz

Bus Clock: 100 MHz

 

I also notice this like hyper icons that XLR is seeing. Its like everything is running faster then it should. The shutdown timer is fast also. The clock is also running faster then it should be. 2 mins just went by in a blink.

that was what I actually needed to know. We'll se later for a new candidate. don't u mind? it is 5:00 am and I really need to be fit for tomorrow.

btw, I removed alpha7, no more tests needed on that one: confirmed by two users. thanks to them.

Greetz.

Link to comment
Share on other sites

Alright, i've replaced the boot file with 06-04 and everything's back to normal.

The machine i'm using right now has a freshly installed 10.6.3 retail and it's free for any kinds of experiments, so i can test whatever you want on it. Except maybe BIOS patching or board soldering, lol. So give me a shout if you need anything.

 

:)

Link to comment
Share on other sites

Alright, i've replaced the boot file with 06-04 and everything's back to normal.

The machine i'm using right now has a freshly installed 10.6.3 retail and it's free for any kinds of experiments, so i can test whatever you want on it. Except maybe BIOS patching or board soldering, lol. So give me a shout if you need anything.

 

:D

that's fine, here is the next one alpha8.ziptest, test, test

edit: I'll be needing more coffee to wake up :(

Link to comment
Share on other sites

valv, i'm sorry but your last works alpha 7-8 have the same problem with original darwin kernel. --- black screen

 

with legacy kernel no problem.

No, with alpha8 the system animations are still on steroids.

;) am taking it out. thanks for testing.

Could u tell me what values u did get this time: fsb, cpu, tsc?

Link to comment
Share on other sites

 Share

×
×
  • Create New...