[Volunteer needed]Too high DRAM clock speed MAY be causing you random crashes/freezes - Printable Version +- PINE64 (https://forum.pine64.org) +-- Forum: PinePhone (https://forum.pine64.org/forumdisplay.php?fid=120) +--- Forum: PinePhone Hardware (https://forum.pine64.org/forumdisplay.php?fid=122) +--- Thread: [Volunteer needed]Too high DRAM clock speed MAY be causing you random crashes/freezes (/showthread.php?tid=9832) |
RE: [Volunteer needed]Too high DRAM clock speed MAY be causing you random crashes/freezes - devrtz - 05-15-2020 (05-14-2020, 03:21 PM)Boern Wrote: I went to 552 because I just can't wake up properly from standby, I get just a black screen. But I get that even with 552. Is the stock u-boot somewhere in the filesystem? If not, I'll reflash to mobian soon anyways. I have the same problem in the latest image. I think this is a separate issue with suspend right now (it did work for me on an older release though), which is being looked into. For now I would suggest disabling suspend. RE: [Volunteer needed]Too high DRAM clock speed MAY be causing you random crashes/freezes - Djhg2000 - 05-16-2020 I haven't received my PinePhone yet, but I found this hint at a memtest facility built into Linux we might be able to use: https://github.com/raspberrypi/linux/commit/822bf4833ecc8ea63c69f3ed894c13b4509c9e85 Not sure if this would work on a PinePhone as I have no way to test it but I thought I'd let you know anyway. RE: [Volunteer needed]Too high DRAM clock speed MAY be causing you random crashes/freezes - devrtz - 05-16-2020 Thanks, I will have a look into this! RE: [Volunteer needed]Too high DRAM clock speed MAY be causing you random crashes/freezes - Djhg2000 - 05-17-2020 Actually, the more I read about memtest in the Linux kernel the more I think we want it in the regular images. Combined with a boot option to use it I think it will help extend the service life of our devices towards the end, in addition to serving as a fast way to check RAM for trivial bit pattern errors. The results are readable in the kernel log and could easily be read with a script, or probably an app with a graphical representation of the bad memory. Actually, this sounds like an easy enough project to get started with for learning how to develop apps for the PinePhone. I'll have a look around and see what I can come up with. RE: [Volunteer needed]Too high DRAM clock speed MAY be causing you random crashes/freezes - 33YN2 - 05-17-2020 Would this uboot binary work with ubuntu touch? RE: [Volunteer needed]Too high DRAM clock speed MAY be causing you random crashes/freezes - devrtz - 05-17-2020 (05-17-2020, 01:55 PM)Aberts10 Wrote: Would this uboot binary work with ubuntu touch? It should work with any distribution. But to be sure you can make a backup of the existing uboot by doing the "reverse" dd. Code: # dd if=/dev/sdX of=uboot-backup.bin bs=8k seek=1 @Djhg2000 I haven't yet looked into how to specify kernel commandline arguments from uboot, but it should be relatively simple. I will have a look this week and post an update here. RE: [Volunteer needed]Too high DRAM clock speed MAY be causing you random crashes/freezes - kenigan - 05-17-2020 Thank you Devrtz, I too was suffering random crashes on the latest mobian image as well as ubports. I could not figure what was going on with my pinephone until I read your post. 576MHz has been working for me well. RE: [Volunteer needed]Too high DRAM clock speed MAY be causing you random crashes/freezes - miaegaal - 05-18-2020 567MHz here too. RE: [Volunteer needed]Too high DRAM clock speed MAY be causing you random crashes/freezes - devrtz - 05-18-2020 (05-17-2020, 08:15 PM)kenigan Wrote: Thank you Devrtz, I too was suffering random crashes on the latest mobian image as well as ubports. I could not figure what was going on with my pinephone until I read your post. You are very welcome, glad I could help you RE: [Volunteer needed]Too high DRAM clock speed MAY be causing you random crashes/freezes - dukla2000 - 05-18-2020 Didn't realize the immediacy of this thread: as soon as I brewed my first Mobian install had a torrid time, couldn't get Firefox or Web to load 2 pages in a row without crashing (either themselves or phosh). Backed off to 552 and have a usable phone. |