Tmbinc Xbox 360 GPU Linux Library Update and Info Posted by XanTium | March 28 15:50 EST | News Category: Xbox360

From Tmbinc on his blog: [QUOTE] First, here are the promised slides for my Breakpoint 2008 presentation about "Gaming Consoles for demosceners": breakpoint-2008-slides.pdf Then, I've updated my GPU library a bit. The biggest thing was a rewrite of the interface, so now it's all encapsulated into a nice API. I've also added some features (stencil buffer ops, drawing with index buffers), and fixed a LOT of bugs (for example vfetch patches on more complex shaders). The updated GPU library, included the mentioned "spinning cube" example, is available here: gpu-0.0.5.tar.gz. Also, I've ported some existing code to my library. A simple test scene looks like this: This is a per-pixel lighting shader with stencil-based shadow volumes - and obviously 3 cubes. I thought it looked nice enough to put it here. [/QUOTE] Full Story: debugmo.de

nice

Nice for the 5 people interested.

How I wish the 360 homebrew scene would take off. Where are the affordable modchips??

Somehow I feel the easy dvd hacks have stifiled the desire for full mods. As a consequence homebrew will never flurish on the platform.

yes possibly, or people are just waiting for a full modchip solution

full modchip solution will never happen i think. all the ingredients for succesfull homebrew are there, we can get an alternative OS installed, we have gfx librarys and sound. people were spoilt i think by how easy the xbox1 made it

Why do people act like this isn't another step in the right direction.
Yeah, the homebrew scene on the 360 is hardly existant at all, but come on... It's a snowball effect. The more the homebrew scene begins to offer, the more people will be involved in the scene.

You all should be shitting lucky charms-o-joy for the fact that there IS a scene and it IS making progress thanks to people like Tmbinc.

Plus, you all remember how much we cared for xbox live with our original xboxes. It was hardly something to worry about losing because you modded it. But the 360 is VERY live-centric and because of this fact I would expect the 360 homebrew scene to never get as big as it was on the original xbox.
Plus the fact that Joe Stupidass wont be able to mod his 360 and pick his nose, ass, and croch all at the same time is bonus. Nobody wants those people flooding the forums with stupidity (like it was *still is* for the original xbox), seasoned x-scene members know exactly what I mean.

- Illumi.Naughty

i hope thats a new forum account then

I think these forums need some more software modders, so they can tell me what this means .

Xbox1 homebrew took off not only because it was so easy to mod, but because it was a worthwhile device. Rock solid media center, and ripping your games to the HD is waay more convenient than DVDs. The 360 is a noisy, barely functional piece of crap to begin with. You can get a basic Dell with more power, and once you factor in the lifetime electric bill the Dell comes out cheaper.

BUT - Hopefully tmbinc et al will come up with some killer app for 360 homebrew! I'm just saying it's not here today.

More than 5 people want to see XBMC, emus, and other things ported to the 360.



You're right, I probably wouldn't want to spend so much effort setting up something on the 360 if it's going to break down 2 months later and now I can't get it fixed under warranty. (on my 3rd 360 here)



True enough but they don't all have the same config, so nobody's going to package an installer disc with all the cool media/emu/game applications all on one disc that work perfectly with your hardware as-is, and you just put it in and everything's installed and configured and ready for your TV.

What!? Are you joking? The 360 has a 3 core 3.32 Ghz CPU and an R600 based GPU along with 512MB DDR3 RAM. The way I figure it, you'd have to have a Q6600 quad core and at least a 512MB 3850 graphics card to match the 360's power. You show me a cheap, basic Dell with parts at least as powerful as those while using less than 120 watts (falcon motherboard).

WOW. People commenting on 360 homebrew must have done NO research.

The reason it's not "taking off" with hacked dashes and modchips etc, is because it currently CAN'T. 360 security hasn't been hacked far enough to install ANY boot mods.

The reason fewer people do 360 linux is because it can't be rigged to boot on startup. It (and all other 360 homebrew) depends on a mod that can't be installed and must be run from a king kong disk. It is a temporary piece of memory that disappears as soon as the 360 is turned off.

Most strong parts of the security have still NOT been hacked, including parts that prevent anything from running hacked BIOS. (Including mod chips) That's why there are no modchips, for the guy that asked. Do your research.

People (and homebrew designers) dream of 360 homebrew that runs at startup like xbox 1.

It's not a matter of popularity. It's just not here.

a few months ago I heard that some dude was working on a dash board for the 360, he said that he was gonna work on a dual boot kind of dash, are you aware of it ?

Either that's a hoax or he wasn't saying he's working on a "dashboard".

He's definitely not working on a modded dashboard. (Which would currently be impossible)

Maybe you mean the "dual boot" mod that lets you store 2 different non-modded kernels (aka dashes). This isn't a modded dash. It just lets you switch between 2 different official 360 dashes. (An older one that still allows the king kong trick, or a newer one that will play the latest games)

You won't see a modded dash on 360 until it is hacked far enough to START into unsigned code. With security SO powerful this gen, that may never happen. The hacker(s) would virtually have to be super geniuses with quantum powers.

Please correct me if I am wrong as its been awhile since I have checked in around here but doesnt infectus have a chip that can run an exploit to downgrade the kernel and if so couldnt some thing be added on to store a boot loader...

I actually gave up on the hb scene this last boxing day. I actually didnt upgrade my 360 for a full year to keep an exploitable kernel(laugh if you like I deserve it). I had the hacked firmware and I just had to sit down and get to it with the exploit. I never did it I dont know why I certainly took on more difficult projects b4. I think it was the pay off... a sort of crippled linux install that required running the exploit everytime u wanted to boot it. So I picked up a ps3 during the boxing day sales and upgraded the kernel on the 360 the same day so I could play the neat new cheap 360 games I picked up also during the sales. Sigh, I could here the cpu keys calling out for me as the efuses blew, but who cares I can run linux without an exploit on the ps3 .... lol which is also crippled in my opinion... I havent done that either...maybe I am just getting lazy

This is definitely an excellent step in the right direction. Somebody's actually taking the time to make a graphics API for the 360. Now homebrew can ACTUALLY make use of some 3D RENDERING. That's building a basis for the homebrew to come beginning 2009.

AND, _YES_ the Xbox360 is "Hacked" or "Cracked" already, but the modifications are still rudimentary. I own an Infectus2 that I'm looking at now (I can type and look at stuff at the same time), but it doesn't really do anything. Oooh, I can use some old kernel, but then I cannot play any game past mid-2006. The current generation of Xbox360 modchips are the kinda stuff that's really geared toward developers.

This is the same way other modchips for other videogame systems developed. Xbox360 is barely at its first generation of modchips. AND, with the miracles of the Timing Attack, I have no doubt there will be fully functional modchips by late 2008, early 2009, with automatic region-patching and security sectors, without being lame and modding the DVD.

Worst-case, just more "emulating" of circuitry will have to be moved into the chip during the next few months. Just more re-routing of internal components or whatever.

Don't say that the Xbox 360 will "NEVER" get hacked. That's just not true. Why? Human error -- the hypervisor idea may be flawless, but not the engineering around it.

[*EDIT]I had to remove ONE word for semantical purposes.

This is just another way of asking the same question the last guy asked.

The answer hasn't changed.

The exploitable kernel is still an official kernel, and won't directly load any code except retail games.
It just has a flaw that you can open with shaders INSIDE loaded retail games.



Yes



Like I said before. No. (Not one that you can launch, anyway)

The 360

and by that I also mean the exploitable kernel

has not been hacked far enough to boot an exploit off anything BUT the King Kong disk.

More correctly, the hack has just not been streamlined so it is feasible for the end-user, nor robust enough to apply to more than just exactly 1 console revision. Yet...

Classically stated throughout the computer world in various forms, if you throw everything you got at a hack, they're gonna defeat everything you got, then you'll have to work harder in the future. The vicious cycle.

I think it's more a matter of intelligence this stuff isn't going any faster.

sorry i can't help myself

Hopeful.. your full of a load of....

What.. He said was right PERIOD.

They are working on trying to 'reboot' into the same dash without restriction.

When they are able to do that they can load ANY dash they created.

so a dash that would for example allow unsigned code to run.

If you want to know more about it and not just blow out steam

look up the rebooter project.

There are things for 360 CALLED "mod chips", but they're NOT the same thing past consoles had, and have nothing to do with progressing towards it. Those mod chips were BIOS mod chips.

What the 360 has are DVD firmware chips. There are flasher/testers like what you have, which let hackers examine everything on the flash, but that's not a BIOS modchip.

Cracking the 360 for homebrew proved to be SO different, and SO much harder than past consoles, that they had to push aside BIOS modchips and focus on simpler hacks. It's nothing like past consoles.

The timing attack has NOTHING to do with working towards hacked BIOS. It's just a peripheral hack that finds your downgrade info. None of which has anything to do with breaking BIOS security.

A homebrew modchip wouldn't need region patching, because it would kill region locking.

Emulating circuitry?

I'll say it again. The 360 BIOS/Kernel/Dash have security that even the hackers will tell you isn't like anything they've seen on a console before. It's not just the hypervisor. It's layers of things you wouldn't imagine. The encryption alone is the same stuff they use in BANKS. You REALLY can't talk about how 'human error' comes into play until you research and understand what's going on.

Currently, the only way to unsigned code is using a King Kong disk on EVERY boot. There is no way to boot a hacked kernel, which means there's no way to install one, which means no modded dashes etc. If you look at how many talented hackers are working on this, and what they're saying, you get a better idea of the probability. There is currently no way to start up in homebrew, and as tight as the security is, there may never be.

WOW that's ignorant.

First of all, research the rebooter project better. Go back into arenezami's thread and read it slowly, and study similar XBH threads. Learn what a dash is. Learn what a kernel is.

A ) They're trying to reboot into a different kernel/hypervisor.
B ) THEN the dash loads
C ) The new dash doesn't RUN the unsigned code. It IS the unsigned code.
D ) The project still doesn't reboot fully, because of all the challenges. Even though Arnezami is obviously VERY talented, even he would probably admit he's up against a NIGHTMARE of a security challenge.
E) The rebooter project ISN'T A DASHBOARD.


Secondly, what he said was THIS.



A ) It's impossible to build a dash when there is no hacked Kernel/HV to run it on. And the rebooter is not a dash.
B ) He specifies a "dual boot type mod". I believe dual boot means the ability to boot between 2 different kernels. http://www.xboxhacker.net/index.php?topic=7683.120

I doubt he's talking about the rebooter.

Also what I said was "You won't see a modded dash on 360 until it is hacked far enough to START into unsigned code." Which is completely true. The rebooter is NOT a dash. It's something that would start into unsigned code. I doubt it will ever completely work, but that's just me.

ok I was talking about this thing here http://www.xboxscene.com/xbox1data/news-ar...e-7-10-2007.php

Ok then I was ABSOLUTELY right when I said He's definitely not working on a modded dashboard. (Which would currently be impossible)

This is not a dashboard.

It's a Kernel/Hypervisor loader. (And still has a lot of obstacles in its way. Like he said, the final product is still a theory.)

Like I said: You won't see a modded dash on 360 until it is hacked far enough to START into unsigned code.

The rebooter would (theoretically) do just that, and ALLOW a modded dash, but it itself is NOT a dash. And you still need the King Kong disk every time you use it. (Or any dash you install with it) But there's no point even bringing this up until we see it in action.

Is it an AWESOME project? Definitely.

Would it kick ASS to play real emulation instead of that cheesy no-emulator, pay-per-rom, stand alone rom shit? You bet!

Would it be good to finally see powerful apps specifically for 360 linux, that take full advantage of tmbinc's API? It would rock.

Will they actually get it working? We'll see. Let's not get our hopes up.