173w ago - Today
GeoHot has released sample PS3 Linux isolated SPU loader code for those with OtherOS to experiment with.
To quote: "Right now, I'm playing with the isolated SPEs, trying to get metldr to load from OtherOS. Interesting thing, I am not using the exploit. I always assumed the enable isolation mode register was hypervisor privileged.
It's not, it's kernel privileged, which means using hypervisor calls you can all get to it. So, get to hacking.
Here is the code I am playing with.
I'm not that opposed to releasing the exploit, but I think the majority of you are going to be disappointed, even if you do get it working. Unless you have pushed the HV to it's limits, this exploit really isn't going to do much for you... yet.
So install OtherOS and start playing around. If people start coming up with convincing reasons why they need the exploit to go further, I'll release it. It's just a waste to release if people can't make use of it.
As far as the GPU goes, I have full access to the GPU memory space 0x2800... But without a driver, it's useless. 3D video card drivers are notoriously hard to write, look at the ATI and NVIDIA ones for linux. The best are still the closed source manufacturer ones.
I'm not even sure I believe that the HV restricts video card access, just that the OtherOS driver is 2D. If someone skilled in video card driver development comes forward, and they can explain in detail what the HV is restricting, I'll send them the exploit."
i played on rebug 4.21.2....flawlessly with no problem...fast loading btw...
I think, you're right, just wait, it will be better than RUIN my PS3.
well, as matter of fact, I'll wait 'till sony stop making the f/w and release the PS4
i think I'll wait 'till someone release a nice tutorial
You don't want to use geohot's exploit. Not even with a nice tutorial. You want to wait until there is a CFW or something else that's more end-user friendly.
i think I'll wait 'till someone release a nice tutorial
i am nearly sure that 90% of the people who wanna try it getting stucked on compiling it ^^
Yeah, that's me. When I try to compile it, I get 35 errors. I guess I need the correct header files? When you compile it, can you upload the executable?
I reopened this thread for those seeking help with the kernel module, but to follow-up on the above quote from earlier today...
We ran out of time, so I never ended up posting it in the news and we're still waiting for an answer from someone on it but for those curious, this is the leak I was referring to, roughly translated: elotrolado.net/hilo_edit-otheros-se-ejecuta-p-otheros-self-en-ps3-slim_1348709_s140
sys_init: get PsCode sys_init: get PsCode
entering stand-alone mode. entering stand-alone mode.
sys_init: get ProductMode sys_init: get ProductMode
entering factory model entering factory model
get system paramater get system Paramater
sys/external sys / external
CP is available. CP is available.
DEX: long-push-power-on: going to system-sotware mode. DEX: long-push-power-on: going to system-Sotware mode.
DEX: long-push-power-on: XXXXXXXXXXXXXXXXXXXXXXX DEX: long-push-power-on: XXXXXXXXXXXXXXXXXXXXXXX
DEX: non-stand-alone mode: DebugAgent will be invoked. DEX: non-stand-alone mode: DebugAgent will be invoked.
DEX: entering stand-alone mode. DEX: entering stand-alone mode.
system software: PS3 console mode system software: PS3 console mode
special execution mode special execution mode
system software debugger system software debugger
system software: s mode (memsize=%ldMB) system software: s mode (memsize =% ldMB)
internal mode (XXXXXXXXXXXXXXXXXXXXXX) internal mode (XXXXXXXXXXXXXXXXXXXXXX)
usb mass file system mounted. usb mass mounted file system.
/dev_usb000 / dev_usb000
2nd_image_writer.self 2nd_image_writer.self
image writer: process has been launched. image writer: process has been launched.
cellftp.self cellftp.self
setmonitor.self setmonitor.self
monitor.conf monitor.conf
lv2diag2.self lv2diag2.self
creating the system software process : XXXXXXXXXXXXXXXX, going to XXXXXXXXX mode. creating the system software process: XXXXXXXXXXXXXXXX, going to XXXXXXXXX mode.
OK OK
sys_init: system software process set-up done. sys_init: system set-up software process done.
sys_init: sys_mutex_create something wrong: 0 sys_init: sys_mutex_create something wrong: 0
sys/internal sys / internal
XXX program has been launched from USBMass storage. XXX program has been launched from USBMass storage.
uinit_app.elf uinit_app.elf
creating the first user process : XXXXXXXXXXXXXX creating the first user process: XXXXXXXXXXXXXX
creating the debug agent : XXXXXXXXXXXXXXXXX creating the debug agent: XXXXXXXXXXXXXXXXX
This part was new to the Devs from it: 2nd_image_writer.self
It appears to be a mix of data between an internal mode tool, and a PS3 in service mode. I'm sure when time permits we'll follow-up on it though!
Until then, let's get back on topic with discussion of the sample PS3 Linux isolated SPU loader code!