Jump to content

AnV XNU Kernel V1.4

Andy Vandijck

By Andy Vandijck,
in OSx86 10.5 (Leopard)

 Share

AnV Kernel reliable  

211 members have voted

  1. 1. Does the kernel work fine for you?

    • Yes
      133
    • Reasonable
      47
    • No
      31

  2. 2. Did the installer work fine for you?

    • Yes
      146
    • No, fixed it manually
      40
    • No
      25

  3. 3. Which cpu do you use?

    • Intel with HPET and SSE3
      83
    • Intel with SSE3
      37
    • Older Intel
      22
    • AMD with SSE3
      66
    • Older AMD
      3

383 posts in this topic

Recommended Posts

Arial
Arial
Posted
Posted
I've done some thorough tests on Rosetta.

On my system everything works great.

On my friends AMD machine also.

Seems to be related only to certain computers...

Research continues...

many thanks for your hard work, Andy.

let me know if you need more data on my PC, I'll post/PM it.

Link to comment
Share on other sites
Andy Vandijck
Andy Vandijck
Posted
  • Author
Posted
ANDY! I feel like shouting at you. LOL. ;)

 

9.6 kernel has NO hpet — everything got removed. WHY are you still shoving it back in the kernel and asking people to do all sorts of gymnastics to get going?

LOL

Well, for 1 reason really...

I have no HPET and I use HPET emulation through the kernel.

This only works with old HPET driver (it linked it through code in the kernel).

With no HPET + HPET table the probe for HPET will obviously fail in the new version of AppleHPET.

That's why...

You can still use the newer driver if you have HPET available, however, if you do not have it like me it is beneficial to emulate it... (my opinion anyway...).

It is no disadvantage to have those little bits of extra code in so...

 

Ok.. i found most of the answers i was looking for.

-Remembered to run "TSC stability" test, from Voodoo's beta Test Plan, on "old" HPET and got the "old" 1 sec difference. No difference with the kext unloaded.

-The "new" HPET breaks my network.

Given this, i only find reasons to not use HPET. Until someone gives one good reason to use it, will leave it alone. Plus, Voodoo team already had droped this.

 



So Andy, as "kind of" a conclusion i have two suggestions:

-Make us a "real" port of the Voodoo kernel, i mean, without your mods :) and keep your version, of course. That would be really helping the community and at the same time, do things your own way.

 

-If not in the mood, at least can you remove the "macmodel" thing!? It's the only thing that really bugs me. We can set it with your SMBIOS, Chameleonsm and on the future Chameleon.

It overrides Chameleonsm so, will it override the future Chameleon?

I tested "MacPro2,1" with Chameleonsm (using Voodoo kernel) and it works fine.. still fools GeekBench.

 

I don't have what it takes to do it my self and i still have that error when trying to compile via voodoobuild.sh.

 

As for your work in general, polemics apart, you did a nice job at porting to 9.6.0!

Works fine in my system, installing only the kernel or with the rest of the files.

The installer needs some work, though the last one works fine. I think most of the problems people are having is because of installing problems!? I found i don't have problems if i extract the files and install them with e.g. OSx86Tools but, i saw that many people are installing with Pacifist.. so, i installed the kernel,dyld and system.kext with Pacifist and got a real mess!! Kp at normal boot and even my rescue DVD (INSTAHackintosh made) wouldn't boot the system (hang). Had to boot the DVD, repair permissions on the system and then managed to boot the system with the DVD (took forever).. installed everything with OSx86Tools and it was fixed.

A suggestion.. try to build the installer with old PackageMaker 2.1.. maybe it helps.

Next release will have a "nomacmodeloverride=1" style option...

Link to comment
Share on other sites
Azimutz
Azimutz
Posted
Posted
Next release will have a "nomacmodeloverride=1" style option...

 

Ok.. it's a solution ;)

Link to comment
Share on other sites
Xess666
Xess666
Posted
Posted

found bug when open Mplayer OSX Rev.8

 

Process: MPlayer OSX Extended [193]

Path: /Applications/MPlayer OSX Extended.app/Contents/MacOS/MPlayer OSX Extended

Identifier: hu.mplayerhq.mplayerosx.extended

Version: ??? (???)

Code Type: X86 (Native)

Parent Process: launchd [118]

 

Date/Time: 2009-03-07 18:15:18.753 +0700

OS Version: Mac OS X 10.5.6 (9G55)

Report Version: 6

 

Exception Type: EXC_BAD_ACCESS (SIGBUS)

Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000

Crashed Thread: Unknown

 

Error Formulating Crash Report:

Called memoryAtAddress: 0xd404158b, which is in an unmappable portion of [0x0 -> 0xffffffffffffffff] in PID# 193.

0x0089f10b

0x00bdce3b

0x000b8864

0x000b246b

0x000b1b78

0x000b1ae3

0x000c71ae

0x000c6ec2

0x000c2556

0x00002e74

0x000094a2

0x0000b5d4

0x0000b121

0x00a3b03b

0x0000a828

0x00a0f095

0x00a0ef52

 

Backtrace not available

 

Unknown thread crashed with X86 Thread State (32-bit):

eax: 0x00000000 ebx: 0xbffff450 ecx: 0x8fe3886c edx: 0x063de9c0

edi: 0x0025546d esi: 0x8fe0a00e ebp: 0xbffff488 esp: 0xbffff450

ss: 0x0000001f efl: 0x00010286 eip: 0x8fe0a227 cs: 0x00000017

ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

cr2: 0x00000000

 

Binary images description not available

Link to comment
Share on other sites
Andy Vandijck
Andy Vandijck
Posted
  • Author
Posted
what would the problem be for this crash? I was using VooDoo 9.5.0 v1 and occasionally bump into one of these panic. Now I switched to AnV with the same problem...

IMG_1874.JPG

In this case it is an allocation (zalloc) related to the graphics card driver that fails and next causes the panic...

Link to comment
Share on other sites
Andy Vandijck
Andy Vandijck
Posted
  • Author
Posted
found bug when open Mplayer OSX Rev.8

 

Process: MPlayer OSX Extended [193]

Path: /Applications/MPlayer OSX Extended.app/Contents/MacOS/MPlayer OSX Extended

Identifier: hu.mplayerhq.mplayerosx.extended

Version: ??? (???)

Code Type: X86 (Native)

Parent Process: launchd [118]

 

Date/Time: 2009-03-07 18:15:18.753 +0700

OS Version: Mac OS X 10.5.6 (9G55)

Report Version: 6

 

Exception Type: EXC_BAD_ACCESS (SIGBUS)

Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000

Crashed Thread: Unknown

 

Error Formulating Crash Report:

Called memoryAtAddress: 0xd404158b, which is in an unmappable portion of [0x0 -> 0xffffffffffffffff] in PID# 193.

0x0089f10b

0x00bdce3b

0x000b8864

0x000b246b

0x000b1b78

0x000b1ae3

0x000c71ae

0x000c6ec2

0x000c2556

0x00002e74

0x000094a2

0x0000b5d4

0x0000b121

0x00a3b03b

0x0000a828

0x00a0f095

0x00a0ef52

 

Backtrace not available

 

Unknown thread crashed with X86 Thread State (32-bit):

eax: 0x00000000 ebx: 0xbffff450 ecx: 0x8fe3886c edx: 0x063de9c0

edi: 0x0025546d esi: 0x8fe0a00e ebp: 0xbffff488 esp: 0xbffff450

ss: 0x0000001f efl: 0x00010286 eip: 0x8fe0a227 cs: 0x00000017

ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

cr2: 0x00000000

 

Binary images description not available

I'm testing this on my Intel Lappy right now... If there's trouble I'll be able to devise a fix...

Working on this too thus...

Link to comment
Share on other sites
Andy Vandijck
Andy Vandijck
Posted
  • Author
Posted
found bug when open Mplayer OSX Rev.8

 

Process: MPlayer OSX Extended [193]

Path: /Applications/MPlayer OSX Extended.app/Contents/MacOS/MPlayer OSX Extended

Identifier: hu.mplayerhq.mplayerosx.extended

Version: ??? (???)

Code Type: X86 (Native)

Parent Process: launchd [118]

 

Date/Time: 2009-03-07 18:15:18.753 +0700

OS Version: Mac OS X 10.5.6 (9G55)

Report Version: 6

 

Exception Type: EXC_BAD_ACCESS (SIGBUS)

Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000

Crashed Thread: Unknown

 

Error Formulating Crash Report:

Called memoryAtAddress: 0xd404158b, which is in an unmappable portion of [0x0 -> 0xffffffffffffffff] in PID# 193.

0x0089f10b

0x00bdce3b

0x000b8864

0x000b246b

0x000b1b78

0x000b1ae3

0x000c71ae

0x000c6ec2

0x000c2556

0x00002e74

0x000094a2

0x0000b5d4

0x0000b121

0x00a3b03b

0x0000a828

0x00a0f095

0x00a0ef52

 

Backtrace not available

 

Unknown thread crashed with X86 Thread State (32-bit):

eax: 0x00000000 ebx: 0xbffff450 ecx: 0x8fe3886c edx: 0x063de9c0

edi: 0x0025546d esi: 0x8fe0a00e ebp: 0xbffff488 esp: 0xbffff450

ss: 0x0000001f efl: 0x00010286 eip: 0x8fe0a227 cs: 0x00000017

ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

cr2: 0x00000000

 

Binary images description not available

I fixed this up amongst other things...

The proof is below.

post-100023-1237032627_thumb.png

post-100023-1237032644_thumb.png

post-100023-1237032662_thumb.png

post-100023-1237032675_thumb.png

post-100023-1237032688_thumb.png

post-100023-1237032696_thumb.png

post-100023-1237032703_thumb.png

post-100023-1237032710_thumb.png

post-100023-1237032731_thumb.png

post-100023-1237032746_thumb.png

Link to comment
Share on other sites
mitch_de
mitch_de
Posted
Posted

KP with new 1.4, on very compatible (Vanilla) INTEL C2D, 10.5.6. System

Installed kernel+ dydl + update_dydl... + system.kext+AppleACPIPlatform.kext - not more.

 

Why Intel crash with that Version and Amd not ?! :rolleyes:

S1050077.jpg

Link to comment
Share on other sites
Konami®
Konami®
Posted
Posted
KP with new 1.4, on very compatible (Vanilla) INTEL C2D, 10.5.6. System

Installed kernel+ dydl + update_dydl... + system.kext+AppleACPIPlatform.kext - not more.

 

Why Intel crash with that Version and Amd not ?! ;)

 

I am not the expert here, but i am using AnV XNU Kernel V1.3 and works like a charm in Intel C2D

Link to comment
Share on other sites
Andy Vandijck
Andy Vandijck
Posted
  • Author
Posted
Thanks, your new kernel works fine for me! I still got the only issue that when I set model override to "MacPro3,1", Geekbench recognizes my machine as Hackintosh. When I set it to "MacPro2,1" it works perfectly and is recognized as Mac Pro.

If you use use only my AppleSMBIOS (latest) and boot with -nomacmodeloverride it should work now...

Even on my Intel Celeron M 420 based lappy it reports "MacBookPro5,1" as "Macbook Pro".

 

KP with new 1.4, on very compatible (Vanilla) INTEL C2D, 10.5.6. System

Installed kernel+ dydl + update_dydl... + system.kext+AppleACPIPlatform.kext - not more.

 

Why Intel crash with that Version and Amd not ?! :lol:

Hmmm... weird... try with stock AppleACPIPlatform.kext.

I have Intel myself and it works great (no issues yet so...).

Also fully repair everything (permission repair etc...).

Then report back please cause it should work great (especially that CPU...).

Link to comment
Share on other sites
hnak
hnak
Posted
Posted

Hi Andy,

 

I am glad that system and kernel versions are now synchronized, thanks.

VoodooPower (AMD) also works (still testing), thanks for incorporating RTC fix.

 

By the way, I tried to build from source, but got the error below.

[1] Processing boostrap_cmds (bootstrap_cmds-60.1)
 Extracting (bootstrap_cmds-60.1.tar.gz)...
 Patching (bootstrap_cmds-60.1-AnV.diff)...
 Building...
Makefile:11: //Developer/Makefiles/CoreOS/ReleaseControl/BSDCommon.make: No such file or directory
make: *** No rule to make target `//Developer/Makefiles/CoreOS/ReleaseControl/BSDCommon.make'.  Stop.
ERROR

 

I tried to build on System 10.5.6 (iPC+new kernel) and xcode 3.1.2 ( gcc = 4.0.1 ).

What is the requirement to build ?

Link to comment
Share on other sites
Andy Vandijck
Andy Vandijck
Posted
  • Author
Posted
Hi Andy,

 

I am glad that system and kernel versions are now synchronized, thanks.

VoodooPower (AMD) also works (still testing), thanks for incorporating RTC fix.

 

By the way, I tried to build from source, but got the error below.

[1] Processing boostrap_cmds (bootstrap_cmds-60.1)
 Extracting (bootstrap_cmds-60.1.tar.gz)...
 Patching (bootstrap_cmds-60.1-AnV.diff)...
 Building...
Makefile:11: //Developer/Makefiles/CoreOS/ReleaseControl/BSDCommon.make: No such file or directory
make: *** No rule to make target `//Developer/Makefiles/CoreOS/ReleaseControl/BSDCommon.make'.  Stop.
ERROR

 

I tried to build on System 10.5.6 (iPC+new kernel) and xcode 3.1.2 ( gcc = 4.0.1 ).

What is the requirement to build ?

Well, I had XCode 3.0 which I updated to XCode 3.1.2...

Probably those files are there... (3.0)

I'll mod it slightly and try to build with that script... (done that... try this voodoobuild.sh... might work for you...).

 

Hi Andy,

 

Just a quick question...

 

What is dydl & update_dydl in the pkg for?

 

Is it really needed to replace the vanilla one with those 2 binaries?

 

 

Thanks.

No, you can use stock vanilla too...

voodoobuild.zip

Link to comment
Share on other sites
popophobia
popophobia
Posted
Posted

I got kernel panic using this kernel.

img1891.jpg

 

I'm using EFIString for my graphic card. I tried NVinject with no luck. Still kernel panic but with different output.

 

Is it the kernel issue of something is wrong with my set up? I used to have KP using VooDoo also (a few posts back). Please help

Link to comment
Share on other sites
Andy Vandijck
Andy Vandijck
Posted
  • Author
Posted
I got kernel panic using this kernel.

img1891.jpg

 

I'm using EFIString for my graphic card. I tried NVinject with no luck. Still kernel panic but with different output.

 

Is it the kernel issue of something is wrong with my set up? I used to have KP using VooDoo also (a few posts back). Please help

Did you try setting your card ID into those kernel modules (NV parts + geforce kmods...).

I've heard from someone that might fix this...

Link to comment
Share on other sites
mitch_de
mitch_de
Posted
Posted

I am near sure taht your KP has nothing to do with the kernels (vanilla, Vooddo, AnV).

KP tells last things was with the geforce driver !

I would first fix this before i would test new beta kernels !

Can you boot in SAFE MODE (kernel flag -x) ?

Link to comment
Share on other sites
Andy Vandijck
Andy Vandijck
Posted
  • Author
Posted
I am near sure taht your KP has nothing to do with the kernels (vanilla, Vooddo, AnV).

KP tells last things was with the geforce driver !

I would first fix this before i would test new beta kernels !

Can you boot in SAFE MODE (kernel flag -x) ?

Yeah, I would do that too...

BTW: Does the new version work for you now mitch?

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...