-
Tuesday, April 20, 2010
Wednesday, April 14, 2010
BLOG MOVED! CARTRI.NET ! (New Bios!)
Hello All, if you are reading this, you have not been redirected or was a nice follower of the RSS feed. This post is to inform that this blog has moved to a new address:
http://cartri.net
Be welcome to the new host - which has many new features and local file hosting, and update your RSS feeds once you get there. It was very nice to be here, and will be even more to be there!
http://cartri.net
Be welcome to the new host - which has many new features and local file hosting, and update your RSS feeds once you get there. It was very nice to be here, and will be even more to be there!
Thursday, April 8, 2010
STATUS UPDATE & FAQ: GIGABYTE MAC EDITION BIOS
A small explanation on this table.
1 - ALL the boards on the table will have a Cartri Mac Edition BIOS.
2 - The Status Order of a board is:
- Checking of Diffs & Grouping (done to all boards except UD3P v1.0/1.1/1.2, which WILL BE DONE AGAIN)
- Code Porting
- Alpha Needed
- Alpha Create / Alpha Paused
- Alpha Running
- RELEASED
And there goes some answers to Frequently asked questions:
4- The table speaks for itself and includes no P41 or P35 boards. This is due to the fact that these boards, indeed applicable to some features on the project, have less chances (almost none) of achieving the project final status objective: A FULL BOOTABLE VANILLA SYSTEM.
5- I'm VERY MUCH interested on increasing what i done until now and what i pretend to do to P55 and X58 boards. AND intel boards. the reasons for that are:
- X58+ICH10 are native MacPro4,1 models. Im drooling to start messing with em.
- P55 are imac11,1
- All these boards have 16Mbit (2MB) Bios Chips, with space left to lots of code, compared to actual 8Mbit chips of P4x. That would open space for some stuff.
- Intel boards have a feature that i want to port to Gigabyte boards: a special module which mekes em different.
6 - Why I don't talk much about what i'm doing before i already done?
- Cat and Rat game.
Gigabyte seems becoming more comprehensive on the fact that they will sell more if they create better bioses, and gives OSX86 users a better experience, since their users are not housekeepers, but IT involved people, who knows what ASL and ACPI means. Looks like Gigabyte Taiwan got the idea, by asking for defining darwin on the bios, but Gigabyte China (where the bios is made) doesnt. They Shall have some reason to use a 5 years old ASL compiler from Microsoft instead of the free and actual intel-ASL (the iASL all hackintosher uses).
On this I would like to directly and openly argument on GB China Bios Team: we are on the same side, i'm not trying to underestimate your job, but you guys need to understand - or make your bosses understand - that new technologies on the soft part must accompany the great tech GB does on the hardware side.
Booting GUID Partition Tables is not a hackintosh thing, is a technology as any other and your boards are completely capable of doing so.You don't need to stop using Award Licensed Bios for that, you only need to add or modify a module just like Intel did on their boards, that shows how you can boot a EFI partition WITHOUT REPLACING THE BIOS WITH AN EFI, again, YOU JUS NEED A MODULE INSIDE THE ACTUAL BIOS! Also if any of your teams or team members from ANYWHERE want to make DIRECT contact with me regarding anything, im offering myself to HELP you, we are NOT ON OPPOSITE SIDES.
On the other side is Apple, which is starting to look bad at hackintoshes, no longer seeing us as "the small fishes who cleans the whale", statistics increasers for safary and OSX usage and future apple-buyers (what we all are, and in fact 3 major reasons that makes us something that increases Apple Market Value and as so something to be untouched) but as something to be vanished or at least frozen where it is as they showed on 10.6.3 update, and I don't want to invent something that could trow the OSX86 community under the same game iphone jail-breakers got. We are not pirates. We like you software, we like your hardware, but we are a kind of public that you are ignoring: NO apple line satisfies people from the called "grey market" which is not grey, but as colored as your 80's logo. We need to have a tower with a normal price that can be configured and changed as fast as the OPEN I.T. Market does. (Mac Pro costs a MINIMUM of 4 to 5 THOUSAND dollars in Brazil, and stop blaming the government: its being cheaper to go to US, buy a Mac Pro, come back to Brazil with it legally paying ALL the SAME taxes you would - in fact higher then you would as we are physical persons - then buying it from you in Brazil with delays and etc. YES YOU ARE OFF MARKET AND NEEDS TO ADAPT)
7 - Where is your source code?
Inside the bios itself, if you don't know how to decompress and decompile a bios, you should not be messing with it. As for the ACPI tables, they can be easily extracted in any of the 3 supported OSs, but id like to make something clear: I DONT USE iASL BUT MS-ASL, so for instance, in 0.7m dsdt where you all read:
Device (PIC)
{
Name (_HID, EisaId ("PNP0000"))
Name (_CRS, ResourceTemplate ()
{
IO (Decode16,
0x0020, // Range Minimum
0x0020, // Range Maximum
0x01, // Alignment
0x02, // Length
)
IO (Decode16,
0x00A0, // Range Minimum
0x00A0, // Range Maximum
0x01, // Alignment
0x02, // Length
)
})
}
i have to work with and write as:
Device(PIC_)
{
Name(_HID, 0xd041)
Name(_CRS, Buffer(0x12)
{
0x47, 0x01, 0x20, 0x00, 0x20, 0x00, 0x01, 0x02, 0x47, 0x01, 0xa0, 0x00,
0xa0, 0x00, 0x01, 0x02, 0x79, 0x00
})
}
or it wont compile. So YES, i know what im doing, and NO, im not "stealing" anyoneelse codes, im just making it COMPILABLE by the very same tools anyone would use, and i have to do it on ms-asl in order to keep bios updatable.
Also, there is a huge public of persons who DONT WANNA KNOW WHAT ALL THAT MEANS, and just want things SIMPLY working WITHOUT BREAKING WINDOWS & LINUX COMPATIBILITY, and in that what i do differ completely from what dsdt replacements by bootloaders does - final dash on this, ok?
8 - I heard of Rio floods, are you fine? Is the Project HD fine? The data is backed up?
Yes, Yes, & Yes
Thanks for everyone who asked about me and my known people, to every early/closer tester who asked about my health before the floods, thanks for every "guy, you should sleep" i received, and to every donator who said thanks to this idea and its manifestation trough this blog.
About the Rio floods, Its still raining, and i'll put some pics of how deep the situation is:
About the hard disk...
it is fine and all data is backed up as well, thanks for asking. Im fine too, just some drips in the room, nothing else.
Saturday, March 20, 2010
STATUS UPDATE: G4 Code Ported. Alpha G2 boots.
Just ported G4 code. Ill work on it when i come back from work.
As the new method works, v0.8 will be delayed as it will use the new method (that breaks the code size limit) and add back everything that was removed on 0.7g (such as UART port). But 0.7h owners can expect refined 0.7 releases (0.7p and so on) before that probably. Is more likely that some 0.8 release will become a complete rewrite, always starting from G1 and going forward other groups.
There goes another updated table on project status:
As the new method works, v0.8 will be delayed as it will use the new method (that breaks the code size limit) and add back everything that was removed on 0.7g (such as UART port). But 0.7h owners can expect refined 0.7 releases (0.7p and so on) before that probably. Is more likely that some 0.8 release will become a complete rewrite, always starting from G1 and going forward other groups.
There goes another updated table on project status:
Friday, March 19, 2010
Code Size limitation broken. Internal tests killing windows7. G2 Stamper-job starting now.
Hello all. If anyone reads this here and wants to post on one of the forums, do so.
Just some news from Whateverland: I Broke the code size limitation of wich i so much talked. with that i discovered many many thing that i have no time to explain, but i can say that my code for ssdt overwritting in bios is useless when used in bios, and is not compatible with windows. this is already a good test result.
Since that light peak my secondary hd where the project was wasnt working very fine and now he decided that he doesnt like AHCI anymore, what makes me have to switch cables everytime i want to switch between windows and mac.
But this time instead of loosing the weekend reformating everything ill leave this all to hell, and accomplish what i promissed, im going IDE windows to stamp the G2 0.7 code right now, and ill only come back to mac os x when the 5 boards are ready to be sent to their owners.
Everything is slower now cause im using a poor-quality USB flash drive as the project source now that my secondary hard disk doesnt work under ahci and cant be seen by mac os.
So, way we go i just wanted to leave these news before i disappear for some time
Just some news from Whateverland: I Broke the code size limitation of wich i so much talked. with that i discovered many many thing that i have no time to explain, but i can say that my code for ssdt overwritting in bios is useless when used in bios, and is not compatible with windows. this is already a good test result.
Since that light peak my secondary hd where the project was wasnt working very fine and now he decided that he doesnt like AHCI anymore, what makes me have to switch cables everytime i want to switch between windows and mac.
But this time instead of loosing the weekend reformating everything ill leave this all to hell, and accomplish what i promissed, im going IDE windows to stamp the G2 0.7 code right now, and ill only come back to mac os x when the 5 boards are ready to be sent to their owners.
Everything is slower now cause im using a poor-quality USB flash drive as the project source now that my secondary hard disk doesnt work under ahci and cant be seen by mac os.
So, way we go i just wanted to leave these news before i disappear for some time
Tuesday, March 16, 2010
STATUS UPDATE: Group 2 Code Ported. Alpha Creation soon.
The code is ported, not its only a pusher job to compile all the group 2 bioses. Its the brainless part of the job, and takes some time and some wrist. I took tomorrow not to work, but people here where i live are trying to bring me elsewhere. Anyhow, good news for all the alphatesters! New status table as it follows:
Subscribe to:
Posts (Atom)
