Jump to content

Chameleon RC4 is out!

Poco

By Poco,
in Front Page News and Rumors

 Share
1,054 posts in this topic

Recommended Posts

jamonda
jamonda
Posted
Posted
Hi Asere, your modifications are great!

I only had a small issue with resume from hibernation (deep sleep): it worked with RC4 (with rekursor and Duvel's mods) but your version failed to resume with a black screen. After some tests, I figured out that the problem was the "setVideoMode( VGA_TEXT_MODE, 0 );" line in resume.c. After I deleted that, everything worked fine again.

I have an ATI 4850 video card (using GraphicsEnabler to make it work) -_-

 

My system works good with Asere's bootloader. However, waking from hibernation takes 10 times longer than with thiagomorales' modified RC4. And the 'wake kernel!' is a lot bigger!! :D

Link to comment
Share on other sites
Master Chief
Master Chief
Posted
Posted
Agree.

I have no idea why people spend time on something that is not important(The name) instead focusing on what is important....

Chameleon is a registered trademark and as such should not be used.

 

 

As one of the founders of Chameleon, I would still use the already existing repo for public use instead. We have all the necessary infrastructure for doing this.

You cannot ignore the simple fact that many people, like macerintel, intvar, rekursor, aserebln, thiagomorales, blackosx, cparm and I did what we did.. and we did it here. Nowhere else. Now think for a second because why was that?

 

p.s. Using tag / nick names for copyright notations invalidates the claim instantly, because a copyright can only be given / claimed by legal (and traceable) entities like: adults, companies and organizations. And because of this only two people (from the top of my head) in the Chameleon source code actually claim their copyright. Just to let you know that everyone else already lost his / her copyright. Great news isn't it. Not!

 

Note: Adding your name and e-mail address (in the source code) is only required when you want to claim your copyright (people must be able to contact you in case of a legal dispute) otherwise you won't have any [copyright].

Link to comment
Share on other sites
zef
zef
Posted
Posted
I did what we did.. and we did it here. Nowhere else. Now think for a second because why was that?

Why was that?

 

p.s. Using tag / nick names for copyright notations invalidates the claim instantly, because a copyright can only be given / claimed by legal entities like: adults, companies and organizations. And because of this only two people (from the top of my head) in the Chameleon source code actually claim their copyright. Just to let you know that everyone else already lost his / her copyright. Great news isn't it. Not!

 

It has nothing to do with copyright. This is about some respect. That's fine if anybody decides to manage a new project (using a different name) on your own for whatever reason (like prasys' EmpireEFI).

Link to comment
Share on other sites
THe KiNG
THe KiNG
Posted
Posted

@ Master Chief once again you prove that you have zero respect for others work. Go make your team(you*n you) create your revolution and stfu.

 

@ the rest, Zef tried to open an existing infrastructure, if that is not OK fine, but IMHO a new one will not add all branches in one project, and all this became useless... Why? b/c some like drama, others likes to work alone, some like kisses in the a** or some privileges, others donations and {censored} like that...

Link to comment
Share on other sites
blackosx
blackosx
Posted
Posted

We have reached a point where a compromise is going to have to be made somewhere, or we are all going to carry on as before. For that to happen, ego's need to be left outside and common sense must enter.

 

As I see it..

 

The state of OSX86 would not be at the point it is today without the great contribution by the Chameleon team.

 

We all want to see progress and development, that is why the recent modifications to Chameleon have happened.

 

We have some highly skilled developers here who want to have their input and hopefully, with a combined effort, the community as a whole will benefit from it.

 

Voodoolabs has a forum devoted to bug fixes, feature requests and general discussion, it's just that not everyone chooses to use it or maybe just don't know about it.

 

If an environment is required for everyone to get together, and some are already prepared to use a new system, then why not join the existing infrastructure offered by voodoolabs which can accommodate the requested changes?

 

Some people are harder to work with than others, that's life! but everybody has something to contribute if the time is taken to listen.

 

And why are we all here?... because this is our hobby and we want to enjoy it, not squabble.

It's like a relationship.... Only after an argument can the air be cleared and progress be made.

Link to comment
Share on other sites
Master Chief
Master Chief
Posted
Posted
Why was that?

I can't answer this question for other people, and even if I could I still won't answer it for them, but since it was me who asked the question... would you mind answering it first?

 

It has nothing to do with copyright.

Me referring to IP / copyright law here was meant as an educated reminder. That things might look fine, when in fact they are not. Not to claim ownership for anything that I did not write. Of course not.

 

This is about some respect.

You lost me here – I fail to see any relationship between code forks and disrespect. Care to explain this little snafu?

 

That's fine if anybody decides to manage a new project (using a different name) on your own for whatever reason (like prasys' EmpireEFI).

Right. A different name. Check [X] I use Revolution and not Chameleon.

 

@ Master Chief once again you prove that you have zero respect for others work. Go make your team(you*n you) create your revolution and stfu.

And how did I "prove" that? By warning people about possible copyright and trademark issues? Because, really, that's all I did here. Go read this again: "Just to let you know that...". Hello?

 

Now. You may think to see more, but that is not my problem.

Link to comment
Share on other sites
rekursor
rekursor
Posted
Posted

Folks,

 

I am sorry that some of us get nervous about some aspects of collaborative work, but it always a difficult task, even on non-anonymous projects where I currrently contribute as well.

 

I love people that have a real potential and prove it by significantly contributing on a subject of common interest,

So I do love and have respect for MC, Zef, Dr Hurt and about all people that have interesting feedback here and in other forums.

 

That said, I believe that we also need today to gather all talents to be more responsive.

 

I couldn't care less about the name that a unified project could take, my motivation is efficienty, only that.

 

Historically Chameleon, was (with PCEFI) the first crucial advancement in our projects.

This is why I suggested to keep the name, but frankly what really should matter here is IMHO:

Who can provide to us a common repository where technical matters and responsiveness are more important than team/name considerations.

 

If Chameleon is capable to further a reactive (like a responsiveness of a couple of weeks and not months) feedback to our new and former talents, then fine.

 

Otherwise, I would understand that someone should provide a way to respond to our call.

 

Something I really deplore, is when I am on IRC, there is sometimes a childish attitude concerning teams/websites : which one are the best, which one should be avoided and so on.

 

I'm not on a forum to make competition/war,

I'm here to contribute to a great project as best as I can.

 

Please understand that my motivation is no real reproach / judgment here,

just facts, issues and how we could solve them.

 

My two cents.

Link to comment
Share on other sites
Master Chief
Master Chief
Posted
Posted

@rekursor,

 

Spot on. I agree with you on almost everything, except for the name – due to its trademark infringement.

 

Now. Let me try to make something clear:

 

My personal objectives are different – most of the times anyway – because I don't have a need for most of the Chameleon features. What I want is a faster, smaller and mostly smarter boot loader. But there is no free lunch... and thus enter Revolution.

 

That and only that was my reason to start working on Revolution. Not to launch a competing project / product. And I admit that I didn't even knew about 'the' public Chameleon repository, but clearly I wasn't the only one.

 

Not that I think that having several different forks / repositories is a bad thing. I mean the official repository can only gain from it... if they want it. Right?

 

What strikes me as odd is that some people here keep pulling words out of context, to blame other people for something that isn't even there, while others keep quite... but in PM's. Thanks, but it is time to speak out, in public, or to be quiet forever. Thank you.

Link to comment
Share on other sites
zef
zef
Posted
Posted
boot132 source and its derivatives were just not designed for these uses.

 

That's also true. But who has enough knowledge and experience to design a new architecture from scratch?

Without a careful design and specification such initiatives are sentenced to death. Anyway I would go into this direction.

 

A few ideas for an advanced booter:

 

- a valid XML parser with utf8 or with obsolete but easy to handle ucs2 encoding support.

- a runtime node based variable store with a lightweight query/update/insert interface.

 

By combining the two above, we could edit the parsed xml data and populate into a reserved device tree node for a prefpane app for example.

 

Then how about a really simple 'composite engine' for the gfx department? With that we could implement UI controls more easy, like a directory browser.

 

Again, combining the three above we could exclude certain kexts for example.

 

etc etc etc.

Link to comment
Share on other sites
Master Chief
Master Chief
Posted
Posted
tbh a GUI really isnt needed for a booter ... i know i know ;P

This is actually a good example. Most people I presume can't do without the GUI, but I can. After all, I only have one OS on my hack and that works best (quicker) without any additional menu. I 'solved' this by moving certain code blocks into #ifdef GUI. It might not be the best solution, but it works for me.

 

p.s. I also did this for other things I don't need, like hibernate et all.

Link to comment
Share on other sites
FKA
FKA
Posted
Posted
I patched the chameleon 2 RC4 source with Asere's patch 1.1.2 + Master Chief's recommendations.

 

Boot loader is now silent.

Memory type is detected but not manufacturer, serial, or part number

Speed is displayed as 667Mhz which is actually what I use normally :P . I tried changing RAM speed in BIOS, but it did not detect them (at least in OS X).

 

Everything else is working perfectly.

Thanks everyone.

 

source and bin attached below

 

Hola!

 

just tried this ... removed platform UUID kext and UUID form SMBIOS.plist - all good there !

removed all mem entries from SMBIOS.plist

 

Memory manufacturer (Mushkin) not seen and speed seen as 667 - its actually 1008 ATM - 800 unclocked

 

post-275122-1263424548_thumb.png

 

Guys - I almost grabbed for a bowl of popcorn this afternoon reading this thread!

 

Most sincerely, I hope it all works out for the best.

 

Dx

Link to comment
Share on other sites
rocksteady
rocksteady
Posted
Posted

Holly !@#$ batman!

 

Let's talk about weather maybe? or the new HelloKity box? or how come heavy-baby experience requires trash-talking and mental masturbation these days?

 

We're all experts, PhDs, OpenSoars and talk about a comm-unity eh?

 

Anyone prefers to have his very own name on his very own lollipop? That's fine go make your very own lollipop

 

Anyone else prefers to contribute and make the existing lollipop super-fresh? Stop bitching and get your hands dirty in the kitchen

 

Pick whatever you like and stick to it, what cannot be done is have the same lollipop broken into a zillion of pieces and eat it too..

 

or just forget about it, let's all go back behind our internets and start acting like a bunch of monkeys arguing over the banana in the sky

Link to comment
Share on other sites
rekursor
rekursor
Posted
Posted
Keep it civil please!

I believe we have particularly smart people in this thread that do a good job not replying to insults/provocations.

I am confident that it will stay an educated and constructive debate,

 

... and my little finger tells me that Zef has good news to express, again proving that he listens and cares.

 

Won't tell more right now and will let Zef explains,

but I am sure that the future is very promising for our community ...

Link to comment
Share on other sites
Dr. Hurt
Dr. Hurt
Posted
Posted
Hola!

 

just tried this ... removed platform UUID kext and UUID form SMBIOS.plist - all good there !

removed all mem entries from SMBIOS.plist

 

Memory manufacturer (Mushkin) not seen and speed seen as 667 - its actually 1008 ATM - 800 unclocked

 

post-275122-1263424548_thumb.png

 

Guys - I almost grabbed for a bowl of popcorn this afternoon reading this thread!

 

Most sincerely, I hope it all works out for the best.

 

Dx

 

Bowl of pop corn.. LOL

 

I think the patch files released by Asere don't contain the memory detection code. Everything else works fine though. Lucky for me that My default is 667MHz. Also for some reason, when I compile I get a silent boot loader (ie. only boot0/boot1...) only then boot right away. With Asere's compiled version (even after MC patch), I get a blinking cursor, then a spinning cursor, then boot. efi_inject...... message is gone though.

Link to comment
Share on other sites
Master Chief
Master Chief
Posted
Posted
Bowl of pop corn.. LOL

 

I think the patch files released by Asere don't contain the memory detection code. Everything else works fine though. Lucky for me that My default is 667MHz. Also for some reason, when I compile I get a silent boot loader (ie. only boot0/boot1...) only then boot right away. With Asere's compiled version (even after MC patch), I get a blinking cursor, then a spinning cursor, then boot. efi_inject...... message is gone though.

The "spinning cursor" [throbber] can be silenced by searching for: spinActivityIndicator and clearActivityIndicator. Change these into:

 

#ifdef TEXT_SPINNER

spinActivityIndicator / clearActivityIndicator

#endif

 

Or bail out early by checking gVerboseMode (limit it to verbose mode?) in spinActivityIndicator :)

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...