Open Fa3l opened 2 years ago
Same problem but with FreeHD Boot, no modchip SCPH-30003R. wLe build 76200f51387fcdff8acaeef7c75e1386529a9336
the screen flickers once and then just black screen indefinitely
Same problem, black screen after trying start from OPL USB or from memory card.
wLe build 76200f5
SCPH-75001
Black screen after run POPS game on USB disk (XX.*.elf)
wLe build https://github.com/ps2homebrew/wLaunchELF/commit/76200f51387fcdff8acaeef7c75e1386529a9336
BLACK SCREEN!! on build 76200f5 :( SCPH-90010
Same here, SCPH-77004, using latest pre-release build.
The black screen still continue on commit e5a6c35 :(
SCPH-75001
Started working again on commit bb89871. Thanks 👍 😁
The boot.elf from 27 October merge with freedvdboot VTS_02_0.IFO play, but the latest boot.elf merge with the same again not working only a flicker and after a black screen, the October boot.elf stop at sector 00069AD0 but the new stop at 00069B30
Console model SCPH-77004_BIOS_VX_PAL_220
@skelletR if you run new wle.elf from usb, does it black screen too?
@skelletR if you run new wle.elf from usb, does it black screen too?
No, I run the freedvdboot with October boot.elf merge, after go to USB and run the latest boot.elf and is open all good, only if merge the new with freedvdboot
@skelletR if you run new wle.elf from usb, does it black screen too?
No, I run the freedvdboot with October boot.elf merge, after go to USB and run the latest boot.elf and is open all good, only if merge the new with freedvdboot
Then, it is not actually a wle issue, but a FreeDVDBoot issue. Moving there>
According to this you need a specially prepared elf file for injecting.
so it requires that the ELF you load doesn't overwrite those functions I use (those are around 0x84000 - 0x85fff and 0x250000 - 0x29ffff)
You can run readelf -l to verify your executable satisfies this requirement. For example, this Tetris homebrew just uses 0x00100000 - 0x0017a940:
According to this you need a specially prepared elf file for injecting.
so it requires that the ELF you load doesn't overwrite those functions I use (those are around 0x84000 - 0x85fff and 0x250000 - 0x29ffff)
You can run readelf -l to verify your executable satisfies this requirement. For example, this Tetris homebrew just uses 0x00100000 - 0x0017a940:
Yeah, this guide this I use, for that say the October boot.elf stop at sector 00069AD0 but the new stop at 00069B30
In the guide is said that not all elf files are accepted. I pointed to necessary elf requirements. This is not wlaunchelf fault, but freedvdboot fault, feedvdboot should be modified to accept specific elf.
In the guide is said that not all elf files are accepted. I pointed to necessary elf requirements. This is not wlaunchelf fault, but freedvdboot fault, feedvdboot should be modified to accept specific elf.
Oh, understand thanks you
Checks
Describe the issue
When I try to start uLaunchelf from Opl or from boot via modchip it stays on a black screen infinitely. In the old version it didn't have this bug
Console model
SCPH-90010