I have never used Etcher. For NetBSD, I assume you used this image: "PINE A64 / PINE A64+", from tophneal's link. Does Etcher automatically decompress the file, or do you have to do that manually? The only time I couldn't get my RockPro 64 to boot, I had absent-mindedly forgot to decompress the image before writing.
(12-18-2024, 05:52 AM)KC9UDX Wrote: I have never used Etcher. For NetBSD, I assume you used this image: "PINE A64 / PINE A64+", from tophneal's link. Does Etcher automatically decompress the file, or do you have to do that manually? The only time I couldn't get my RockPro 64 to boot, I had absent-mindedly forgot to decompress the image before writing.
Etcher will automatically decompress it ... I found when you download the for Example android 7.0-pine.a64-v1.13.25-r103.img.gz take it out of your download folder and place it in a clean folder and then start etcher By right mouse clicking the etcher icon and then run as administrator then click on image point the path to where you got the image is stored at (folder you made) and select image it will start and read the file I also found if it don't read that file it is corrupted you must remove that file all the way out of your system and redownload it again I hate win 11 older systems you could allow it to over write that file to fix corruption then tell it where you want the image to be placed
I finally got all this working late last night ( Now for netBSD I couldn't get it to work I'm thinking it had some thing to do with the switch-/arm -Shush command that's in place or just because the file image is NetBSD-10-aarch64--pine64.img.gz not sure if the file name is a reference to a archival copy of the pine64
(12-18-2024, 05:52 AM)KC9UDX Wrote: I have never used Etcher. For NetBSD, I assume you used this image: "PINE A64 / PINE A64+", from tophneal's link. Does Etcher automatically decompress the file, or do you have to do that manually? The only time I couldn't get my RockPro 64 to boot, I had absent-mindedly forgot to decompress the image before writing.
Etcher will automatically decompress it ... I found when you download the for Example android 7.0-pine.a64-v1.13.25-r103.img.gz take it out of your download folder and place it in a clean folder and then start etcher By right mouse clicking the etcher icon and then run as administrator then click on image point the path to where you got the image is stored at (folder you made) and select image it will start and read the file I also found if it don't read that file it is corrupted you must remove that file all the way out of your system and redownload it again I hate win 11 older systems you could allow it to over write that file to fix corruption then tell it where you want the image to be placed
I finally got all this working late last night ( Now for netBSD I couldn't get it to work I'm thinking it had some thing to do with the switch-/arm -Shush command that's in place or just because the file image is NetBSD-10-aarch64--pine64.img.gz not sure if the file name is a reference to a archival copy of the pine64
Again I can't speak for Etcher but the file name should otherwise be okay. Else you could rename it to something else. But anyway, you're already one step towards freedom from widows
