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

@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=...").

---

Gone Linux.

@cynargo: Thanks for the reply. I think the VoodooPower I was trying should have some support for AMD based on this:
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.

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

Ignore these, the kernel has a patch integrated which forces CS_VALID after detecting any com.apple.xxx code signature...

Front Row doesn't work
I have patched

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A
/System/Library/Quicktime

Also Marvin's AMD utility doesn't work too and iTunes stops itself the reproduction.

Sorry for my bad english
Anyway, thx!

Only patcher_opts=2 works and all others like patcher_opts=18 or patcher_opts=34 or the no patcher_opts gives me a KP saying:

EDIT: forgot to add that my processor is AMD Athlon X2 4400+

After a few days everything is running as it should, (except for Marvin, crashlog below) although I've noticed that the system seems a bit slow sometimes. Another thing I've noticed is that some soft, like pacifist, won't open with qoopz kernel but it runs fine with yours.
Thanks again for this Andy.

---

CPU: AMD Athlon 64 3000+ @2.3Ghz - Motherboard: ASUS A8N-SLI nForce4 SLI - nForceLAN by eno - SuperNForceATA by Medevil - RAM:2 GB DDR 333Mhz Audio: ALC850 Video: XFX nVidia GeForce 8400GS 256Mb (0x06e4) QE & CI from Chameleon 2 RC4Ethernet: Realtek RTL 8139 Series (working out of the box) OS: Snow Leopard 10.6.4 (aryajuanda's guide) + Windows XP 64bits

agree, system is slower than using nawcom kernel, every benchmark i have tested confirm that, and graphics ar glitchy also, that was not the case using just 32bit system... dont know where is the problem.. but my experience is that

I noticed with -force64 its rather slow myself but without that flag its as efficient as it should be, anyhow this is the first revision of a kernel/dyld that can use 64bit binaries simultaneously as 32 bit on amd so i guess it can take a bit time until its as reliable as it is on a intel cpu

Also, my terminal gets bombarded with:
dyld: shared cached file was build against a different libSystem.dylib, ignoring cache

not a big deal though

I guess I should do some benchmarks myself to confirm the slow downs, working with anything coreaudio with -force64 at the moment is just too glitchy.