5GB VRAM for 6.72 Linux #85
Comments
|
@NoUserNameForYou mining b*tcoins? |
|
LOL. He got me. Everyone, run away while you can! |
|
@NoUserNameForYou Will probably compile a binary payload. Don't think it's worth adding to the host. |
|
You're a gem and you have done so much good for the community during this boring pandemic. Thank you for the joy and smiles. |
|
Is this coming along brother? |
|
Just set the upper limit on VRAM to 5GB and uploaded new payloads to the website. To utilize, create a |
|
happyemoji.jpg Thanks so much! |
|
Hmm, tried three times with the txt in there and it crashed on all three without booting into rescue shell. Gonna try without txt file to see if the payload is still working. Edit: Oops I feel like I f'd myself over LOL. Your payload was the only one working for me, and now it's not working without .txt file either :( |
|
I forgot to specify that I'm on 7116B Pro Baikal. |
|
It outright crashes with every single baikal kernel I used whether with vram.txt file or not . :( |
|
Do you mean that it crashes instantly without trying to shut down? That's weird. Please do the following:
|
|
"without trying to shut down?" Yup. The harddrive clicks, machine hard crashes and restarts with scanning the internal drive. I'll do as you have said, brb. |
|
Hmm maybe you added a new thing? Notification says "failed to check bootargs.txt (in the supported folders)" Do I create that file and type 5 in it and delete the vram.txt file? My files are on mnt/usb0 |
|
Here's the log anyway. (got bootargs.txt message and it stopped there, didn't boot or crash) "PL = 0 <118>[SceShellUI] I/PSM.UI : UI system timer elapsed 00:01:00 <118>SceLoginMgrDialogServer::dialogNotifySessionKilled r10: 00000002007dfe50 r11: 0000000000000051000000083b6a3c91text: 0000000820c28000:0000000820c7c000 r-x<118>[Syscore App] Kill process: 0x39 => 0 <118>[SceShellUI] I/PSM.UI : UI system timer elapsed 00:01:00 |
|
Please post this on a code sharing site like Pastebin or GitHub Gist. This way it is completely unreadable. |
|
Here is the cause: sleirsgoevy/ps4jb-payloads@e066ef6. Will upload fixed binaries tomorrow. |
|
Thanks for the effort mate. Without the vram.txt file Linux 3GB button works, but that 3GB is for the vram since the system shows 5GB ram after linux boots. With the vram.txt file in 3GB button hard crashes with internal hard drive scanning at start up. And with the vram.txt file in, standard linux button is stuck at white light with this putty output: |
|
Were you able to look at the last log brother? |
|
My future children's college savings :( |
|
Brother I just tried 2 in vram.txt file and it works. Standard linux button has 1, 3GB has its own button and standard button works with 2GB vram.txt file. I tried 4 and 5 and they won't work. Stuck at white light. I think your binaries top out at 3. |
|
Am having the same issue, tried the txt file method and the ps4 restarted then nothing showed on the screen. (ps4 slim) |
|
I forgot that I had the txt file with 4 in it was in the folder and got it to boot once with 4gb ram. Tried twice more after that but couldnt again. |
Hey man, thanks for breathing life into this dusty POS with your linux payloader. Yours is the only one working for me.
However if it's possible can you add "5GB" VRAM payload to your site, I'm asking this for a "very specific" thing :P and for a friend.
The text was updated successfully, but these errors were encountered: