Qoopz AnV xnu 10.4.0 Rel4

[andyvand]

I'm releasing a patch that will also patch the libSystem sysenter traps (pre-patched).
That should clear some of these issues...
I'll continue the work on the kernel

[$The-King$]

good work andy hope new one will be the best kernel for AMD

[scififan68]

With -force64 (and syscenter fix) it now loads 32bit and 64bit apps, nice work!

[gorg]

Thanks Andy. I can now run both 32bit and 64bit apps in my AMD PhenomII X6 1090T using AnV_Qoopz_xnu_10.4.0_Rel4.zip, AMD_sysenter_10.6.4_patcher.zip, latest Chameleon2RC5 (rev411) and booting with

arch=i386 busratio=16 cpus=6 maxmem=4096 patcher_opts=2 -force64

For some reason the combination

arch=x86_64 -force64

does not work (instant reboot) and I have not tested yet if 8GB RAM is possible.

[cynargo]

OK, I've applied your patch, and now I can run x86 applications while in x64 mode ( so I can also use more than 4 GB of RAM ).



The weird thing is that the kernel doesn't identify itself as x64 if you boot with "-force64" (eg. in System Profiler), but that seems to be only cosmetic stuff.

Thanks for your work, Andy

[RayFlower]

Thanks again for the quick fix, there are some improvements over the last that I've identified, for instance i can now use Logic with the 32bit audio unit bridge in 64bit mode, that is very nice! however some plugins still crashes the audiounit validation and i still can't play games in steam, this is not an issue on 10.5.8.



My boot flags now are:

arch=i386 -force64 cpus=3 patcher_opts=2

I have to use cpus=3 because if i don't i get glitchy audio with my presonus firebox fw interface, this was not an issue until i did a clean install a few weeks ago when i had a HD failure, but this is irrelevant to this fix never the less.

This fix patches the sytem dyld, not the one thats injected in the kernel right, should i use std_dyld=Yes ?

Oh, and about the steam issue, am i the only one experiencing this?

[bltz]

First, big thanks to Andy for his great work on this, it is really amazing!

I could boot a fresh (unpatched) 10.6.4 install (10.6.0 + combo update) with this kernel on an AMD Athlon64 3200+ and it mostly works (even iTunes started) but there are some small problems:
- booting in 64bit (without arch=i386 or -x32 options) results in instant reboot (this is not a big problem for me as I have less than 4G RAM)
- booting without patcher_opts=2 results in kernel panic as others noted
- when it boots I saw some crashes and freezes randomly but generally it's very promissing.

I was trying to make power management working (OK, maybe that's too much for a start but I'd like my system run cooler). While installing the VoodooPower package I got a kernel panic during the finishing kextcache -update-volume / step (screenshot attached).

After resetting I got another kernel panic, looks like VoodooPower does not work for my system? (another screenshot attached).

I also have a strange problem with missing dates and times almost everywhere in the GUI (dates show right in the Terminal) and some graphics artifacts in some buttons. The video card is an Nvidia gForce 7600 GS, QE/CI works with Chameleon's GraphicsEnabler option after fixed _UID, One->Zero in DSDT (Gigabyte MB with nForce4 chipset). Third screenshot attached, circles show missing dates, arrows show graphics artifacts. It may have to do with the bootloader because Chameleon also seems to ignore the com.apple.Boot.plist in /Extra folder (I have to type boot options, but it reads DSDT.aml and smbios.plist from the same place). I have Chameleon v2.0-RC4_PCEFI-10.5_AsereBLN. Any ideas anyone about any of these?

[cynargo]

@bltz : I think they've dropped support for AMD processors in VoodooPower some time ago. And even when they did support AMD it wasn't always working good. If you want to boot in 64-bit mode use "-force64" flag (without "arch=...").

[bltz]

@cynargo: Thanks for the reply. I think the VoodooPower I was trying should have some support for AMD based on this:

strings VoodooPower | grep -i amd
AuthenticAMD
__Z9amd_probeP28AppleIntelCPUPowerManagement
__ZL11AmdK10WritePv
__ZL10AmdK10ReadPv
__ZL9AmdK8ReadPv
__ZL10AmdK8WritePv
__ZL9AmdK8InfoPv
__ZL10AmdK10InfoPv
__ZL10AmdK11InfoPv

The -force64 option does the same (instant reboot while booting) like any other way trying to boot 64bit on my system (but as I said it's not important to me). Sadly it panics randomly even in 32bit so I think I have to wait for some improved version.

[fxwizrd]

Thank you Andy for providing the new kernel and patches.
I Installed the kernel + AMD sysenter trap patch and added the following kernel flags to the boot string:
arch=i386 patcher_opts=2 -force64

Everything now seems to be working fine. Although I noticed I am still getting cs_invalid_page errors. Here are some of them:

CODE SIGNING: cs_invalid_page(0x1000): p=47[loginwindow] clearing CS_VALID
CODE SIGNING: cs_invalid_page(0x1000): p=46[mds] clearing CS_VALID
CODE SIGNING: cs_invalid_page(0x1000): p=88[fontd] clearing CS_VALID
CODE SIGNING: cs_invalid_page(0x1000): p=110[Dock] clearing CS_VALID
CODE SIGNING: cs_invalid_page(0x1000): p=111[SystemUIServer] clearing CS_VALID
CODE SIGNING: cs_invalid_page(0x1000): p=112[Finder] clearing CS_VALID
CODE SIGNING: cs_invalid_page(0x1000): p=115[fontd] clearing CS_VALID

Is there a way to get rid of them?

Thank you!
FX