PINE64
Rock64 doesn't boot - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: ROCK64 (https://forum.pine64.org/forumdisplay.php?fid=85)
+--- Forum: Linux on Rock64 (https://forum.pine64.org/forumdisplay.php?fid=88)
+--- Thread: Rock64 doesn't boot (/showthread.php?tid=5455)

Pages: 1 2


RE: Rock64 doesn't boot - xalius - 12-19-2017

If you are not a developer and encounter problems with 0.6.x pre-release images, please stick with the last stable release for now...


RE: Rock64 doesn't boot - artocignus - 12-20-2017

(12-15-2017, 09:59 AM)eloranta Wrote: Hi,

I am not able to boot any of the newer images (0.6.x). Try the 0.5.x series of the images - those seem to work for me.

Jussi

Hi Jussi, Thanks for the advice. I've now downloaded and flashed the following image to my micro sd card:
xenial-mate-rock64-0.5.15-136-arm64
Now my Rock64 starts booting (progress!) and I'm getting the text screen with boot messages on the HDMI screen. However, the desktop doesn't load and it gets stuck on this error:
"mmc1; tried to reset card
blk_update_request: I/O error, dev mmcblk1, sector 30252928
mmcblk1: error -84 sending status command, retrying
mmcblk1: error -84 sending status command, aborting"
The last two lines repeat over and over.


Another bit of information that might or might not be useful: I wasn't able to flash the image with Pine64 Installer. It gave me a long error, which I can't copy and paste, but it starts: "Couldn't elevate, exit code 3221225781..." I then tried with Etcher and this time it completed the flashing process with successful verification, but it keeps creating what seems to be superfluous partitions: 

 Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Unknown           4000 KB    32 KB
  Partition 2    Unknown           64 KB       4032 KB
  Partition 3    Unknown           4096 KB    4096 KB
  Partition 4    Unknown           4096 KB    8 MB
  Partition 5    Unknown           4096 KB    12 MB
  Partition 6    Primary             112 MB     16 MB
  Partition 7    Unknown           5120 MB   128 MB

At first I thought some of these were leftover partitions from previous attempts at flashing the OS, but I manually deleted everything in Diskpart, but still get this same list of partitions after flashing the image from scratch.

(12-16-2017, 09:43 AM)eloranta Wrote:
(12-15-2017, 08:25 PM)sparklerchen Wrote: When I power the board "ROCK64 4GB" with the SD card image "xenial-mate-rock64-0.6.1-141-arm64.img.xz" that download from url "https://github.com/ayufan-rock64/linux-build/releases"

, and all 3 leds light up and remains on, nothing else happens.

It is need to reconnect the power for several times to finally boot successfully

Exactly - this is the behavior I get with all 0.6.x images. The last working one is 0.5.10.

Sorry, I missed this reply! I tried 0.5.15. I should have gone further back it seems... I'll try with 0.5.10 and report back


RE: Rock64 doesn't boot - artocignus - 12-21-2017

(12-20-2017, 04:48 AM)artocignus Wrote:
(12-15-2017, 09:59 AM)eloranta Wrote: Hi,

I am not able to boot any of the newer images (0.6.x). Try the 0.5.x series of the images - those seem to work for me.

Jussi

Hi Jussi, Thanks for the advice. I've now downloaded and flashed the following image to my micro sd card:
xenial-mate-rock64-0.5.15-136-arm64
Now my Rock64 starts booting (progress!) and I'm getting the text screen with boot messages on the HDMI screen. However, the desktop doesn't load and it gets stuck on this error:
"mmc1; tried to reset card
blk_update_request: I/O error, dev mmcblk1, sector 30252928
mmcblk1: error -84 sending status command, retrying
mmcblk1: error -84 sending status command, aborting"
The last two lines repeat over and over.


Another bit of information that might or might not be useful: I wasn't able to flash the image with Pine64 Installer. It gave me a long error, which I can't copy and paste, but it starts: "Couldn't elevate, exit code 3221225781..." I then tried with Etcher and this time it completed the flashing process with successful verification, but it keeps creating what seems to be superfluous partitions: 

 Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Unknown           4000 KB    32 KB
  Partition 2    Unknown           64 KB       4032 KB
  Partition 3    Unknown           4096 KB    4096 KB
  Partition 4    Unknown           4096 KB    8 MB
  Partition 5    Unknown           4096 KB    12 MB
  Partition 6    Primary             112 MB     16 MB
  Partition 7    Unknown           5120 MB   128 MB

At first I thought some of these were leftover partitions from previous attempts at flashing the OS, but I manually deleted everything in Diskpart, but still get this same list of partitions after flashing the image from scratch.

(12-16-2017, 09:43 AM)eloranta Wrote:
(12-15-2017, 08:25 PM)sparklerchen Wrote: When I power the board "ROCK64 4GB" with the SD card image "xenial-mate-rock64-0.6.1-141-arm64.img.xz" that download from url "https://github.com/ayufan-rock64/linux-build/releases"

, and all 3 leds light up and remains on, nothing else happens.

It is need to reconnect the power for several times to finally boot successfully

Exactly - this is the behavior I get with all 0.6.x images. The last working one is 0.5.10.

Sorry, I missed this reply! I tried 0.5.15. I should have gone further back it seems... I'll try with 0.5.10 and report back

Okay, so I tried again with 0.5.10, and get the same behaviour as with 0.5.15! In other words, the same scrolling error as set out above. What could be causing this? And I still get the same number of partitions shown above. Is this normal with a Linux installation? Sorry, as mentioned before, I'm a noob with Linux and Rock64


RE: Rock64 doesn't boot - valdiks - 02-10-2018

I have the same issue.
When the u-boot is installed on Rock64 and connected to the TV I'm unable to boot from USB SSD any 0.6.20 and 0.5.15 images - nothing happens and TV shows that the device is not connected.
Only removing u-boot I'm able to boot 0.5.15 images.
0.6.20 images I will check later.