Repository navigation
ghostldr v0.6.1
Changelog
PS4
- Compiler system calls on a PS4 now go through each number's own libkernel stub. A PS4 runs a system call only from its own number's stub. Until now ghostldr sent every number through getpid's stub, so on a 12.02 PS4 the diagnostic and the boot both stopped at the compiler's first
clock_gettime(PS4 check 2/4), when the compiler process was killed. ghostldr.lua now passes the compiler's stub for each system call the loader makes there. A number without a stub is refused with a log line, not sent through another number's stub. Details: docs/ps4.md, the third report. - Still experimental: no PS4 has booted a title yet. PS4 owners: please run
run.py probe --diagagain and send the log. Its first lines now list the stubs.
Changed
- Extension check: the runtime extension is checked against the first 24 bytes of its SHA-256, which run.py passes in, as well as its CRC-32.
- USB drives are the recommended way in the README, the guides and the desktop app (no install, faster loads). Installing into SWRR's saved data is still there for setups without a drive.
- Tests build and run on Linux (clang and GCC) as well as macOS.
- PS5: boots are unchanged.
- Dev payloads: unchanged from v0.6.0.
How to use
Using the prebuilt release · USB drives: docs/usb.md · FTP: docs/ftp.md · PS4: docs/ps4.md · in Jak X: docs/jakx.md