whats the benifets? is it like 9.6.0 Vanillia? does this mean we can boot retail? im very confused lol

It's just like Voodoo but with improvements...
For more info look at the download site...

Did it happen only once or did it happen each time Firefox was running?

Fortunately only once.

OK then I doubt it is a kernel bug...
It may just have been "bad luck"...
Lets hope it doesn't happen again...

yea i went to the google code web page but it there wasn't any info about it... it said the newest version was 9.5.0 not 9.6.0

Yeah I know... they still haven't completed their port to 9.6.0...
I'll beat them to the punch too with 9.7.0 if I get the chance ;)
It is a matter of honour since some of the Voodoo team didn't threat me very well...
You fix up the warnings in the VoodooPS2 sources and give them the diffs (actually first the sources but next they nagged for the diffs...) and all they did was criticize...
They also argued that one big project over 6 smaller ones was "harder to debug"...
Man are you devs or not is the question I tend to have then...
It makes no difference as one can switch the target etc...

Before I start, I want you to know that I wouldn't reply if the drama wasn't started by the above poster, but I couldn't just let this go unanswered.
I'm really wondering as to what level you can lower yourself to, to say what you say, and release stuff the way you do.

Voodoo didn't complete the port to 9.6.0 because it takes "time" and "effort" (which isn't available) to do it "properly", you think after the work they did, they can't just go and make the fast dirty port you did? Are you going to say "Man are you devs or not is the question I tend to have then..." because of that too?

What is this attitude of "beat to the punch" from you? Is it all about that for you? /shame

I see people doing "real" work, the Voodoo kernel, VoodooPower..., the IOPCIFamily/IOUSBFamily.. kext mods, and I see you take that, fix warnings (most of the time unproperly), retag/rebrand, increment the version, and make it look like an update to the official releases. /shame

You never replied to direct technical questions concerning your additions to the voodoo kernel/projects, and the explanation is obviously because you have no idea. You would have answered otherwise, wouldn't you?

The Voodoo group (specifically, Dense here on this post) contacted you (twice if not more) and invited you to join us on IRC to have a little chat about how to get working together, as we did with few others which are with us now, joined the efforts together, and you already have seen the fruits of it, but you didn't accept to come (IIRC you didn't even reply).

Why? my guess is you don't want to join a group of people, you prefer to be on your own, because all you care about is some childish fame which you obviously have got it on the InsanelyMac forum (and apparently, here too).

About your "stripped" version of the VPS2 story, why not post the link to the real source, so people know what happens?
http://forum.voodooprojects.org/inde...pic,168.0.html

I read that this forum isn't like InsanelyMac, so I'm sure this post will be here when I check back.

I'm going to ask the people who read this not to reply (except AnV, if he wants), so the drama doesn't grow, and the flaming doesn't start, please?

First of all last release is more than proper...
The technical questions about my port?
Ask away... I've never seen any message directed at me with any questions nor have I ever received a mail stating any q's about it...
My point is not a "beat to the puch" attitude... it is to make something better with more features...
Retagging and rebranding only occurs if it is either something I made or it isn't desired to keep that name (like with the kernel after integration of the decrypter...)
And it is my thought that fixing warnings up and perfecting code will result in a faster and better product (I've seen this proven many times...) also I find it important to use the latest toolset and some updated libraries from the kernel...
Next the IOPCIFamily and IOUSBFamily releases are slightly different from the others and in case of the IOUSBFamily parts it does state for PCGenUSBEHCI the proper copyrights (me and the other author...)
You are wrong stating that I don't want to join a group of people and you are wrong stating that I don't allready work togheter with some...
Also fast and dirty port? the first two ones: yes... the last 2: absolutely not...

I've never even noticed the posts... how could I have replied then?

If I click that link I do not even get a request or anything...
Just the main page and page 3 selected below...

But I don't want there to be any further future misunderstandings between us though...
If you should have any questions you should mail me for them...

If you let the post I linked to finish loading, you'll see it, and actually the are questions asked in that same page, and you ignored them, questions about adding HPET back (no proper answer from you), I even asked you about the "proper" Apple ID you added to Chameleon 1.0.11 (I've not seen anything in the first sources you released as 1.0.12 that is worthy of adding your copyright). which made many people who understand what programming is think of it as re-tagging.

Since you like the proper way of things, there is a proper way of expressing your point, but it happens that people reveal what they really think and have inside.

I agree that fixing and perfecting code is wanted, but anyone who knows the basics of coding will agree that in many (not all), of what you've released, lacks any real improvements, and I have yet to see a real proof of that, and what you claim to be faster.
I've checked some of the first mods you posted for IOPCIFamily, maybe that was your first "work", I was disappointed.

And what shows that you usually have no idea what you're doing is something like this; (quoting you):
If you did modify the sources and know what you did, you wouldn't ask for patches, because you already have them, /dang

It's an assumption anyone would make, because all your releases don't mention that you've worked with others, and don't tell about any group.

It's just your regular way of releasing;
NEW (lack of info..) works a lot better (no info..)
Enjoy (a smiley showing confidence)
Edit: fixed more issue (no idea what..)

You get asked each time what's new, what improvements does it bring, and then there is the usual kind of replies;
fixed warnings, perfecting the code, proper Apple IDs, and then something that may look useful (but unfortunately, not after checking the code...)
You, now, need to do much more to get your stuff working with this solution..

I think there is big misunderstanding from your side, specially what happened with VPS2 (you didn't comment about it)
Is there anything to misunderstand from that?

And I have to say that you can do better than this.

It is for supplemental patches which someone claims to have...
I would gladly check them and improve the IOUSBFamily if they really are good...

Also did I not make a new PPF generation and applying tool?
That one is fully mine... so...

Also the point of putting the HPET code back in the kernel is simple...
It also has emulation of HPET code added which allows the standard timers and so on to be used for people without HPET...
In essence thus emulating HPET with an older (V1.1 max) AppleHPET.kext...

You've just confirmed you have no idea what it is.

That's why I was fair and used words like "most" and "not all", is there anything else? anything "new" you brought to the scene? any issues you've fixed that were not fixed before? I would be glad to hear about that.

I give up on getting any "proper" answers from you. If you expect me to understand the "..." (dots), I'm sorry, It's over my head and level of knowledge.

I give up on trying to reply to you.

Useability
 

A propper manual/description of your works Andy would improve a lot.

To my disapointment (for the better or worse) I must say I stopped checking out your developments, cos I am really left in the dark
and only can figur some out when I read the next 10 or 20 experiances testers post.

I liked the fact that your 9.6 kernel (back on AMD) saved me the 9.5 system.kext/seatbelt,
but I then really lost track. Version here, version there. What's this for? What's that for?

I simply switched back to the original and ignored all else you done. Shame really.
Maybe some stuff would have improved something. I'll never know...

Well I've included full description of the kernels features lately...
You can read them and get the latest release here:
http://laptopneeds.forumotion.co.uk/...el-v14-t10.htm

Thats nice, but there is a slight misunderstanding here. It is really about how you release.
One might be interested to try someting, but on a reasonable efford basesis.

Remember OS X is very much liked cos of it's useabillity, even if we are putting our selfs there through hackintoshes.

Great products allways have a great useabillity and not just 1 million features.

Like I said, me personally: I won't be looking into things anymore, even when they might be beneficial, cos I been put off by this release policy and don't know what's next. Others might feel the same.

Due to my switch to an Intel machine, there is really no need for another kernel for me personally. But I surely will try the original new Voodoo kernel when(ever) it comes out, cos even though it's not here now, I already know what I'll be getting.


(Also, manual link: one might not want to become a member of another forum, to get a manual of something he or she gets from the "release" forum)

hmm its so easy to answer any question. Anyone can put the question in " " and then give an answer. In this thread here.. I have seen questions being asked yet a very clear reply of not wanting to answer the questions. If it was me maybe I lets say start to get a little pissed and would say.. fine .. this is what I have done.. blah blah blah.. yet here I am still trying to guess at what has really been changed. I know less about all this yet even I can tell you what has and has not been changed... anyway.

ME.. I feel ANYONE that came before and started something, deserves credit. But is not coming out with a 9.7 kernel nothing more than ADDING something to what was already there? Now ME I would have to rewrite something and then say .. its mine.. but thats just me. If I added to something that I had nothing to do with makeing I would ALWAYS give credit to those 1ST!.

Andy, ur kernel is working nice here, never crashed like 9.5.0 that crashed when I was browsing the net, but its crashing on Chess

Im using ur v1.1

thanks. Any suggestions.

Latest version is 1.4, so you may want to upgrade before asking and see if problem is gone. :-)

Andy, thankfully you've finally provided an answer, about which I have asked you at least 3 times before.

Now, my assessment of your answer: if you had any kind of understanding of the Voodoo kernel changes, or even the xnu kernel only, you would know that we expressly got rid of HPET emulation of the PIT because it added to the complexity, was very poorly written, and most importantly: was completely unnecessary. Are you aware of the fact that the HPET is not used for anything at all since 10.5.6? What then, is the point of emulating it?

I don't mean to sound rude or arrogant, but your reason for putting HPET back is simply wrong. Had you discussed this with us beforehand, you'd have avoided having to add several new bootflags and asking people to use your customized AppleHPET.kext and what not.

Andy: You said you'd like to end any misunderstandings and start contributing as a team player. For starters, you can try to fix this problem with Chess. As a hint: it is an almost trivial fix which requires changing barely 4-5 lines. Sadly I've not had time to actually test it (but Turbo has verified the fix should work). You are welcome to try it and send a patch.

What is "Kernel: Voodoo Kernel Beta C"

I've posted here in the past when I used AnV's 10.5.6 (9.6.0) beta kernel from this thread because Voodoo only had 9.5.0 kernel (Version 1), and it did not work with dual core processor. (Get the wait queue deadlock)

comes time again for 10.5.7 update, and (9.7.0) gives me the same problem, so I look back at this thread and find things have change for the worse. (crying)

Since Anv file was in a pkg format, I could not extract the mach_kernel (still newbie)
So I used my 'safe/backup retail install partition', boot it, used the qoopz mach_kernel for 10.5.7 to the "just upgraded 10.5.7" one, then reboot, (It seems OSX can detect the mach_kernel change and automatically update my softraid/Boot OSX partitions..) Anyway, reboot and 10.5.7 works.

It seems this guy don't like Anv also..

But I agree that Voodoo official kernel is a bit "slow", if it wasn't for Anv's 10.5.6 beta kernel in the first place I would not have gotten dual core to work.

Thanks AnV.

its running amazingly :)

only one problem(so far, SMBIOS isn't working anymore... Its calling my comp a MacBookPro 5,1, when I have it set to be a MacPro 3,1 any idea's?

how to compile custom kernel via source? ive done it with Linux via the libcurses method and menuconfig, however i dont think that will work here lol. any ideas? try to keep concise im wayyy to ADD as it is already lol.

Much thanks.

The Paradox