-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could we get a script for cleaning up afterwards? (or at least instructions) #7
Comments
Thanks for the project, unfortunately my CPU is affected : / |
If you run in ramdisk mode the following should be all that's needed
|
Just reboot and the ramdisk with all its contents will disappear. |
How do I reboot the RAM disk? |
@Nuc1eoN: He means to reboot your system. The RAM and its content (including the RAMdisk) will be cleared. |
That's right! Just power down or reboot your system. |
Yeah but I'm testing on a live CD, so rebooting takes a long time. Is there no faster way? I get some error message about the ram disk when trying to run a second time. |
@Nuc1eoN : I had (have) a patch for that in a fork. However, my branch uses GCC 7.2.0 instead of 7.1.0, because 7.1.0 is broken against many newer Linux distributions that are using glib 2.26 or newer. You could use my branch, but change GCC's version back to 7.1.0. You can find the code here: https://github.com/Oxalin/ryzen-test/commits/master |
@Oxalin thanks great work! :) |
@Nuc1eoN : last I checked, it was working fine. That's how I tested my faulty CPU a few months ago. If you encounter a problem, let me know under my fork. |
For instance, getting rid of the ramdisk, freeing up the disk space, etc.
The text was updated successfully, but these errors were encountered: