Skip to content
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

Closed
dralley opened this issue Aug 26, 2017 · 10 comments
Closed

Comments

@dralley
Copy link

dralley commented Aug 26, 2017

For instance, getting rid of the ramdisk, freeing up the disk space, etc.

@dralley dralley changed the title Script for cleaning up afterwards (or at least instructions) Could we get a script for cleaning up afterwards? (or at least instructions) Aug 26, 2017
@dralley
Copy link
Author

dralley commented Aug 26, 2017

Thanks for the project, unfortunately my CPU is affected : /

@BuzzBumbleBee
Copy link

If you run in ramdisk mode the following should be all that's needed

  1. Kill all processes started by the script (ps aux can help here)

  2. Unmount and rmmod the zram module

sudo umount /mnt/ramdisk
sudo rmmod zram

@suaefar
Copy link
Owner

suaefar commented Aug 27, 2017

Just reboot and the ramdisk with all its contents will disappear.
Nothing should be written outside the ramdisk apart from installing the build-essential package.
You can remove it with "sudo apt purge build-essential".

@suaefar suaefar closed this as completed Aug 27, 2017
@Nuc1eoN
Copy link

Nuc1eoN commented Jan 3, 2018

Just reboot and the ramdisk with all its contents will disappear.

How do I reboot the RAM disk?

@Oxalin
Copy link
Contributor

Oxalin commented Jan 3, 2018

@Nuc1eoN: He means to reboot your system. The RAM and its content (including the RAMdisk) will be cleared.

@m-r-s
Copy link

m-r-s commented Jan 3, 2018

That's right! Just power down or reboot your system.

@Nuc1eoN
Copy link

Nuc1eoN commented Jan 5, 2018

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.

@Oxalin
Copy link
Contributor

Oxalin commented Jan 5, 2018

@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

@Nuc1eoN
Copy link

Nuc1eoN commented Jan 5, 2018

@Oxalin thanks great work! :)
My main system is a fully updated Archlinux. Will your script work there without issues?
The only reason I've downloaded that Ubuntu crap was to test out the ryzen bug.

@Oxalin
Copy link
Contributor

Oxalin commented Jan 5, 2018

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants