05-23-2020, 09:46 PM
(05-23-2020, 05:16 PM)dukla2000 Wrote:(05-23-2020, 04:33 PM)Djhg2000 Wrote: ...
Nice to see my script is working
Let's just hope it still works after encountering an error, I think I managed to figure it out but I want to know for sure before I dare say it's working properly.
Thank you for the script.
OK, set memory speed to 624 and memtest=256. Ran for 13 minutes 45 seconds extra during boot with LED white. then got to clock screen, WiFi icon lit but phone was crashed before I could ssh in!
Need to figure out the simplest way to get my phone usable again from here!
Happy to help!
I'm not sure "memtest=256" has well defined behavior, there's only 17 patterns defined in the struct: https://github.com/torvalds/linux/blob/m...t.c#L9-L25 . However, the pattern selection is done through modulo of the number of available patterns here: https://github.com/torvalds/linux/blob/m...est.c#L110 .
So while "memtest=256" will work (evidently), the benefit of looping through the same patterns over and over is unlikely to find new errors. On the other hand, when the memory fails due to overclocking I think the results will be less consistent because some cells will appear to both pass and fail randomly. It's an interesting experiment but without persistence across reboots I don't think it will yield much of a benefit?
Anyway, just to confirm, did changing "/boot/boot.cmd" and running "mkimage -T script -A arm64 -C none -n pinephone -d /boot/boot.cmd /boot/boot.scr" suffice to get it up and running?
Oh and I almost forgot; put your phone in the freezer to make it boot, the lower temperatures should increase the stability enough to SSH in and disable memtest. From there you can power off and let it cool down again before you flash U-boot with 600 MHz DRAM