(01-19-2018, 03:38 AM)a1w.ca Wrote: It's definitely a strange problem, however I'm certain it's _not_ the images, since I'm also using stretch-minimal-rock64-0.5.15-136-arm64.
Can you compare the SHA256 hash of your image with the one I have?
shasum -a 256 stretch-minimal-rock64-0.5.15-136-arm64.img.xz
54186f3eb2f2a0b2447f4be6ce57e1a334154b899c3160af105afd7c484be579 stretch-minimal-rock64-0.5.15-136-arm64.img.xz
If the hashes match, then I would think there's a hardware issue somewhere..
shasum -a 256 stretch-minimal-rock64-0.5.15-136-arm64.img.xz
54186f3eb2f2a0b2447f4be6ce57e1a334154b899c3160af105afd7c484be579 stretch-minimal-rock64-0.5.15-136-arm64.img.xz
looks identical.
I have the usb keyboard, ethernet cable and mouse connected when I boot, should these not be connected at boot?
Have tried adding keyboard, mouse and ethernet cable after boot, but same result. It recognizes the devices but goes no further.
Perhaps its the 4GB RAM which causes problem with the images? Don't most Rock64s have 1 or 2GB?
