As long as you have dsmos v2, that is probably gfx related.

Trying to google some info on dsmos v2. Not getting much. How do I tell what version I have? My install:

iATKOS s3 v2 10.6.3: (all unchecked except following

chameleon RC4

fakesmc

/extras

kernel 10.3 qoopz

Booted great to that... then did combo update to 10.6.6 and installed legacy 10.6 prior to reboot from pkg file. After reboot I hang like the image I posted.

Thanks for any additional info you can give.

ok your mention of graphics mad me try a older pcie nvidia card and boom it booted.

Soo... my ATI 5850 that I want to use... how can I use it? It did boot with 10.6.3 but I didn't try and get a driver working for it. I think apple added support for this card natively in 10.6.5 or 10.6.6... is that correct? If so what kext/hack do I need to get it working?

Thx

What did you already do?
Is qe/ci already working?
My graphicscard also does not work when i installed the kexts which are needed togheter.
Maybe you have to delete the kexts and add first the atisupport, ati5000controller and atiframebuffer kexts.
If you installed those kexts i would inject the right framebuffer with an bootloader like AnVAL or Kabyls bootloader.
After you´ve done this install the other 3 ATIRadeonX3000.kexts to enable qe/ci......

also noticing this in activity monitor...normal?

Attached Images

100% cpu usage.jpg (15.5 KB, 23 views)

I actually meant smc v2 not dsmos. but nevermind.

and did you make any modifacations to your system to make it work in 10.6.3?

hi...came over from insanelymac...trying out the kernel now on a P4 Northwood sse2 using boot arg -VoodooSSE3emu to avoid double kernel panic at boot System 10.6.6 ...i have issues with dmg files....installers...date and time... but l think all fixable...

Haha hey! I like this forum because I can actually post.... and those problems are all because the sse3emulation is broken. When you don't boot with -VoodooSSE3emu, what does your kernel panic say?

the kernel needs patched for this to work, and luckily, andy is helping us with that!

hmmm..".bad kernel ip won't attempt to handle trap... " where in the logs can i find this ?

I don't know that you can. That's the same error I get, I just wanted to make sure you had the same one.