-
-
Notifications
You must be signed in to change notification settings - Fork 188
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
Proper way to run memtest from heads? #535
Comments
@agent509 : what have you tried? |
I have tried every combination I could think of kexec. I found the latest version of memtest86+, v5.31b, works with kexec -f -t elf-x86 memtest works. It seems like it works at least because as soon as it starts, it overwrites the frame buffer, and all I can see is different colors in the screen as it tests patterns. Is there a way to avoid that? |
I confirm Heads not being able to kexec into QubesOS memtest from ISO boot, not recognising format. Seems like the path would be to have the standalone binary dropped onto a usb dongle and launch the application from there.
|
Depending on board config, coreboot might not be responsible to init graphics nor framebuffer, which is most often initialized by the linux (i915 gpu driver or others) while most boards initialize graphics first by coreboot then linux driver initializes the framebuffer (boards with FBWHIPTAIL support.) The kexec appended magic happens at this line, appending arguments (ADDED or REMOVED per board config) prior of attemtping to kexec the passed kernel. In the case of QubesOS ISO memtest kexec, I have not investigated the issue myself, while elf-x86 seems to need to be explicited. Let us know your findings. |
I have just run into this as well running Heads v0.2.0-977-ga81ae6e on an x230, have made several attempts and all fail to kexec with the message "Cannot determine the file type of "
i even tried all the types kexec supports, just to see if it makes a difference, but no, same result each time. i'm not sure what else to try, i thought maybe i was mistaken about the file type i had downloaded, so in desperation after running this:
i just did a |
Got new RAM. need to test. Ran into this. I haven't found any posts of people successfully running memtest86 from kexec--just posts of people having problems. Most people don't have to run from kexec but since heads is the first thing run from the BIOS we are in a minority who cannot reboot and have bios launch memtest for us. This means we have very few options to test RAM on this hardware. Some people get the error listed above and others get a screen that looks like it is doing something but they cannot read any useful information. I get the error. If anyone reading this has been able to run memtest86 from kexec and/or heads please post as an FYI. |
Have spmeone tried with the new merged kexec version from master? Also. As opposed to past comprehension, IT IS POSSIBLE to kexec to BSD |
Finally! @ryanbarry @sildur @jtmoree-github-com @agent509 @MrChromebox
|
i can confirm this works with latest Heads firmware! |
I have been unable to run memtest from heads. Every attempt to kexec the memtest kernel has simply left the system frozen at "Starting new kernel." Is it possible to run memtest from within heads? What is the best way to do this? Thanks
The text was updated successfully, but these errors were encountered: