Have you searched the community for related issues?
No similar issues found.
Please describe the problem you’ve encountered in detail:
Description:
Hay there,
I really want to try to install FydeOS on an old Brick-PC. But I don’t know how to proceed further.
First I am not able to create a boot stick.
I tried v.19 and v.18.1 to flash with Balena Etcher
I tried both on MAC and on PC
I tried the compressed and the uncompressed file
I tried 3 different USB sticks (that worked well for all other OS installations)
But every time I flash, I get an error message that something went wrong with the writer - maybe because of an corrupted archive (but it is NOT corrupted).
When I tried to flash with Rufus, there was no error message, but I cannot boot from the stick. The target System is caught in a Boot / Restart loop.
What is going on with FydeOS? EVERY OS I tried could at least be booted or started. This one is not even able to be flashed.
I will try, but it stil doesn’t explain, why I am not even able to create a bootable stick. The systems I download the Image don’t know in which device I want do put my USB stick into (or do they? )
Actually if you read the guide, you won’t ask this question. https://fydeos.io/help/knowledge-base/installation-guides/fydeos-for-pc/install-fydeos-for-pc/
We’ve recently discovered that the latest version of balena Etcher can cause issues when flashing FydeOS. Please use version 1.18.11 of balena Etcher for flashing. Additionally, if you’re using a Windows system, we recommend using Rufus to ensure a successful flash.
If you had read my post carefully, you would have seen that all the necessary information was already included (even though I initially forgot to put it into the template – I acknowledged that and apologized for it).
Instead, you ignored the fact that I had already tried flashing with multiple systems and OSes, gave me generic advice about unsupported CPUs, and, rather than being helpful, seemed more focused on mocking me for not following the exact format of your request.
I also mentioned that I had used Rufus, and it didn’t work.
I have now managed to solve the problem by downloading an older version of Etcher (18.1.1) from a third-party website. The link in your guide does not actually point to this version but instead redirects to the most recent one. That was the root of the issue.
It might be helpful to clarify in the FAQ that using any Etcher version other than 18.1.1 can cause issues (it says just “please use” without any further explanation) and that this specific version is no longer available on the official site but can be found on other sources, such as: https://etcher.de.uptodown.com/windows/versions.
By the way, version 19 works just fine on the N4100 CPU.