InfiniteMac OSx86 - AnVAL (ACPI Loader)

InfiniteMac OSx86 (http://infinitemac.com/forum.php)

- 10.X (http://infinitemac.com/forumdisplay.php?f=36)

- - AnVAL (ACPI Loader) (http://infinitemac.com/showthread.php?t=6798)

5.1.1 is now available (on first post)

Quote:

Originally Posted by valv (Post 52196)

5.1.1 is now available (on first post)

Hum, when i upgraded to this version i experienced heavy audio glitches with my presonus firebox(fw audio interface), reverted to the previous version and it works again.
Does this have anything to do with the amd fix?

I must add, even with the previous version i am experiencing glitches if i don't limit my quadcore with cpus=3, i have ordered a LaCie Firewire 400 PCI Card which will hopefully issues I'm having with my built in fw.
http://www.tonymacx86.com/viewtopic.php?f=7&t=8558

Can you get an bdmesg ? It'd be helpful for seeing what's wrong if you also post your capb & smbios.plist

Uhm, what do you mean by capb? it's not in /us/bin and i can't "locate" it either

Smbios http://pastebin.com/EuTJpzmF
Bdmesg http://pastebin.com/0ULEmNuA

I also got [MSR] detected invalid rdmsr(00000017) at 0x6ec81978 when I boot my system, i get that with both versions though, but I'm wondering if this is relevant to the issues I'm experiencing?

I see,
your cpu is an amd phenom. Nice to find guyz like you ;)
I say this because I need some beta-testers for the next release (amd aware partly / phenom aware fully(probably):))
So if interested, I can give you a link for testing.

btw, capb: com.apple.boot.plist; sorry, my fault

Quote:

Originally Posted by valv (Post 52276)

Sure, I would love to test out the next release!

oh and here is my boot.plist

Code:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

        <key>Graphics Mode</key>

        <string>1920x1200@32</string>

        <key>GraphicsEnabler</key>

        <string>yes</string>

        <key>Kernel</key>

        <string>mach_kernel</string>

        <key>Kernel Flags</key>

        <string>arch=i386 -force64 -v cpus=3</string>

</dict>

</plist>

I must confess,
I have no idea about the sound issue. we'll see if it got fixed with the version I pm'ed you.
If you have any questions/requests, I'd be glad to help

Thanks for the links!

I'm unable to boot your kernels, with this and with other boot loaders:
I get "addr=0x42746375, Size=0x8272ae0, File=free, Line=0"
Chameleonrc4 said something about a bad mach-o magic number.

However, I did test this out with the latest nawcom kernel:

I do experience the audio glitches with this version of anval too, but it's not as bad as it was with the last one:)
However as a DAW user it wont cut it for low latency audio recording and sequencing, I'm still puzzled why I'm having these issues though.
The load in logic is insanely high, same issues i have when i use cpus=4 :

Code:

1/13/11 10:15:42 PM        kernel        IOAudioStream[0x8f9b300]::clipIfNecessary() - Error: attempting to clip to a position more than one buffer ahead of last clip position (2d,221)->(2e,c3b).

1/13/11 10:15:42 PM        kernel        IOAudioStream[0x8f9b300]::clipIfNecessary() - adjusting clipped position to (2e,221)

Removing voodoPowerMini.kext didn't do anything as well.

Here is the bdmesg:
http://pastebin.com/d0yYwz0r

As for the settings in my bios:
Cpu clock ratio 3000mhz
Cpu Northbridge Freq. 2000mhz
Cpu frequency 200mhz
HT link freq 2000
Memoryclock 4x 800

Most of this is set to auto, I've tried a fixed the clock ratio before but didn't make any difference.

Just out of curiosity? i see p-states in the bdmesg now, does this mean we get some sort of power management?
And is there a way i can turn it off too check if thats the culprit?

I guess my first priority would be to get those kernels working though as the fsb fix might be causing me trouble as well.

am sorry about sound.
regarding the kernel I just realize the hassle, as other testers never complained about.
The boot-loader is also acting strangely

Code:

P-State 2: Frequency: 400, Multiplier: 2, vid: 32

P-State 3: Frequency: 800, Multiplier: 4, vid: 44

Just to let u know, p-states were not enabled. I just dumped the possible values to see their correctness and if it would be doable or not.
Thank you for testing. It doesn't seem to be mature enough for a new release.

Quote:

Originally Posted by valv (Post 52283)

am sorry about sound.
regarding the kernel I just realize the hassle, as other testers never complained about.
The boot-loader is also acting strangely

Code:

P-State 2: Frequency: 400, Multiplier: 2, vid: 32

P-State 3: Frequency: 800, Multiplier: 4, vid: 44

Ah okay, I'll see what FreeBSD or windows reports on those states later.
I guess getting cool and quiet working would be rather complex?

Always nice to test new things, I'd love to test out new versions in the future:)