Voodoo Kernel BETA 2 - Available now

[kmikase]

I'm sure it must have been asked in different topics, but how do you install the kernel ?

I've iDeneb 1.3 (Modbin 9.4) on a AMD 64 3400 and i would like to try the Voodoo kernel.

thanks

[mitch_de]

I'm sure it must have been asked in different topics, but how do you install the kernel ?

I've iDeneb 1.3 (Modbin 9.4) on a AMD 64 3400 and i would like to try the Voodoo kernel.

thanks

There is an readme within the Dl i think.

Best way (for testing first time) is NOT to overwrite your mach_kernel (default used kernel). Use bootflag and boot with the other named voodoo_ kernel insted. So you avoid non-bootable problems.

[Nick14]

can't say about the entire team, but me personally: Writing drivers. Specially wireless and (maybe) audio, or enabler/injector-like mini kexts.

Perhaps work on bootloader also.

There's a ton of stuff we can still add to the kernel though so that's not gonna be 'done' for a while

When you start with the Grafics for example will the team make IGP cards supported like ATi X1250,Geforce 6150 becouse many need drivers for these kinds of cards

[Daikatana]

I don't know if this has been already discussed, but there is a program called 'Central Brain Identifier' for Windows that is able to modify the processor name, for example 'AMD Sempron Processor 3000+'. The program doesn't give any option to alter the Vendor Name, but maybe it is possible to alter that also.

[entitas]

I don't know if this has been already discussed, but there is a program called 'Central Brain Identifier' for Windows that is able to modify the processor name, for example 'AMD Sempron Processor 3000+'. The program doesn't give any option to alter the Vendor Name, but maybe it is possible to alter that also.

 

CPU-z is best for checking CPU related information in Windows.

[Daikatana]

CPU-z is best for checking CPU related information in Windows.

 

Maybe, but I'm not talking about checking CPU related information but modifying it.

[entitas]

Well, it seems that Voodoo_9.5.0_Beta2c is working fine with correct boot options here. I have a Northwood P4 (SSE2 only and Model 2, check my signature) and needed to use busratiopath=6 to get kernel working. Everything went fine, I started XBench and Geekbench and got overwhelmed by the speed improvements. There was a 72% increase in Geekbench score and 118% increase in XBench score. I did not believe my eyes.

 

But then came the bloopers, although I've nVidia GeForce FX 5200 (with NVkush, got CE as Hardware Accelerated and QE supported) and it was working fine with last used JaS 10.5.4 release (StageXNU kernel 9.4.0), it now stutters everywhere. Dock icons are bouncing so slow, playback of a .mov file in QuickTime is horribly slow and fumbling and whole animation things across OS X is damn slow, as if I'm using software emulation for graphic card. When I reverted back to StageXNU, everything went fine again with good performance from the card, nothing was stuttering anymore.

 

Are there any known compatibility issues between NVkush and Voodoo_9.5.0_beta2c? Should I use something else like NATIT for my card? Please guide me if I need to change some configurations or install something else in my machine to get graphics card working with Voodoo.

[mercurysquad]

I don't know if this has been already discussed, but there is a program called 'Central Brain Identifier' for Windows that is able to modify the processor name, for example 'AMD Sempron Processor 3000+'. The program doesn't give any option to alter the Vendor Name, but maybe it is possible to alter that also.

The vendor string is hardcoded on the processor. There is no way to change it unless the CPU provides native mechanism to do this (like apparently VIA does, but not AMD).

 

I have a Northwood P4 (SSE2 only and Model 2

[...]

it now stutters everywhere. Dock icons are bouncing so slow, playback of a .mov file in QuickTime is horribly slow and fumbling and whole animation things across OS X is damn slow

The first thing you should do is download and install speedstep kext if your CPU supports speedstep (maybe it doesn't, seeing that it's northwood P4). That has clock recalibration in built.

 

Next: follow the TSC procedure. Perform the Test 5. Collect some logs..

 

When you start with the Grafics for example will the team make IGP cards supported like ATi X1250,Geforce 6150 becouse many need drivers for these kinds of cards

Currently no plans either from me or the rest of the team, to work on any graphic drivers from scratch.

 

------

Note:

NO more bug reports for beta 2c are being accepted.

 

------

[bgrau]

Hi New Team xnu-dev mercurysquad.

Greetings.

I thought to give my feedback as I tend to like do my stuff late, and without too much feedback nowadays.

P4 Prescott here (so with HT, hpet and non NX), and ATI x1600 AGP 512MB using ATIInject + gfxstring .

used your beta2c with my old several upgraded Leo build from 5.1 Kaly (via 5.3 Kaly, then using 5.4 Aitkos4i).

works super.

Everything fine. For first time went to sleep. And can wake up. Use of P/S2 Kbd / Mouse, when awake Kbd not work, and mouse extremely sluggish. I wonder if with combo usb kbd/mouse will work?

Upgraded using Delta 10.5.5 with still your kernel beta2c and still great (&same).

Great work.

Nice to meet you.

Billy.

[newnekton1]

Does that mean beta 3 is nearly released

 

The vendor string is hardcoded on the processor. There is no way to change it unless the CPU provides native mechanism to do this (like apparently VIA does, but not AMD).

The first thing you should do is download and install speedstep kext if your CPU supports speedstep (maybe it doesn't, seeing that it's northwood P4). That has clock recalibration in built.

 

Next: follow the TSC procedure. Perform the Test 5. Collect some logs..

Currently no plans either from me or the rest of the team, to work on any graphic drivers from scratch.

 

------

Note:

NO more bug reports for beta 2c are being accepted.

 

------

[mercurysquad]

Does that mean beta 3 is nearly released

sort of..

details to follow.

[entitas]

The first thing you should do is download and install speedstep kext if your CPU supports speedstep (maybe it doesn't, seeing that it's northwood P4). That has clock recalibration in built.

 

Next: follow the TSC procedure. Perform the Test 5. Collect some logs..

Currently no plans either from me or the rest of the team, to work on any graphic drivers from scratch.

 

I downloaded the SpeedStep kext from xnu-speedstep google code page, but it gave a kernel panic when using it. So now its confirmed that my P4 can't handle SpeedStep. But does that also signifies that there are no other ways to make Voodoo work on my PC? I am a bit confused here with it now. I appreciated the speed enhancement but now it does not give a smooth user experience in Leopard.

 

Please tell us here if Voodoo can handle P4 Northwood Model 2 processors? Or may I have to wait for the next version to come?

[kmikase]

Working fine on my MSI K8N Neo 3 with Athlon 64 3400 +

[mercurysquad]

Please tell us here if Voodoo can handle P4 Northwood Model 2 processors? Or may I have to wait for the next version to come?

Pentium 4 models 1 and 2 are not supported by voodoo kernel directly - you need to use a new version of chameleon bootloader (which is not yet released). For model 2 (and some other models), there is the experimental bus ratio path 6, which should ideally work, but in your case it doesn't. A lot of things can affect it. I recommend waiting until next beta or the final release.

[bgrau]

Hi

now just for fun upgraded again the delta 10.5.5 with apple combo 10.5.5, only needed to replace last ioatafamily.kext and iondrvsupport.kext working, with putting in correct data in atiradeonx1000.kext, atiinject.kext and gfxstring in boot plist.

and bootloader is netkas pc_efi v8 on hfs+ separate (active) partition, with multi-booting xp, vista and DOS 7...

[entitas]

Pentium 4 models 1 and 2 are not supported by voodoo kernel directly - you need to use a new version of chameleon bootloader (which is not yet released). For model 2 (and some other models), there is the experimental bus ratio path 6, which should ideally work, but in your case it doesn't. A lot of things can affect it. I recommend waiting until next beta or the final release.

 

The experimental busratiopath=6 is not actually failing its task, since it can start/shutdown/sleep my PC well but those video and UI related slowdowns are annoying and big letdowns. I hope it'll be fixed with next version of voodoo and chameleon.

[muitommy]

i have tried this kernel b2 ver., kernel panic will happen whenever i try to start my virtual machine (vmware fusion).

i'm using vanilla actually, everything works fine, just report my trials.

[speedracer67]

i have tried this kernel b2 ver., kernel panic will happen whenever i try to start my virtual machine (vmware fusion).

i'm using vanilla actually, everything works fine, just report my trials.

In order to use VMware, your voodoo kernel needs to be named /mach_kernel. VMware, for some reason, references that file directly, and you'll get a kernel panic if it's not there. It needs to be the kernel you are currently running, not just any kernel. Annoying if you use more than one kernel, but it is what it is.

[Jabbawok]

Sorted my timecode issues. Cheers!

[Nick14]

The vendor string is hardcoded on the processor. There is no way to change it unless the CPU provides native mechanism to do this (like apparently VIA does, but not AMD).

 

 

The first thing you should do is download and install speedstep kext if your CPU supports speedstep (maybe it doesn't, seeing that it's northwood P4). That has clock recalibration in built.

 

Next: follow the TSC procedure. Perform the Test 5. Collect some logs..

 

 

Currently no plans either from me or the rest of the team, to work on any graphic drivers from scratch.

 

------

Note:

NO more bug reports for beta 2c are being accepted.

 

------

acually the problem with the x1250 is the Framebuffer becouse the card is a degenerated from X2000 Cards

[muitommy]

In order to use VMware, your voodoo kernel needs to be named /mach_kernel. VMware, for some reason, references that file directly, and you'll get a kernel panic if it's not there. It needs to be the kernel you are currently running, not just any kernel. Annoying if you use more than one kernel, but it is what it is.

oh, thanks for the explanations.

[aliasa_anderson]

sort of..

details to follow.

 

 

Hi Mercurysquad.

I have a question: the vodoo kernel uses SSE2 emulation to provide support for SSE2 processors.

But does this effect the performance on SSE3 processors ?

or does this kernel use SSE3 instructions for SSE3 processors ?

[ohoo]

I dont know if i say that correct, but i think that the emulation concerns sse3 instructions for sse2 processors.Cpus that have both sse2 and sse3 instructions arent affected by the emulation.

[mercurysquad]

I dont know if i say that correct, but i think that the emulation concerns sse3 instructions for sse2 processors.Cpus that have both sse2 and sse3 instructions arent affected by the emulation.

That is correct.

 

The emulation is never turned on on SSE3-capable CPUs, so there is no performance penalty.

[aliasa_anderson]

That is correct.

 

The emulation is never turned on on SSE3-capable CPUs, so there is no performance penalty.

 

 

Mercurysquad,

 

With latest vodoo kernel will I be able to use stock AppleIntelCPUPowermanagement.kext because in my case I have Intel core duo T2050 @1.6GHZ and as far as I know,it is capable of HPET but with vanilla I(and even others) still get "Cannot enable HPET" message whle booting.

 

 

If it does ,then would the IntelEnhancedSpeedStep.kext be useful ?