PINE64
[Archived] Initial Linux release from ayufan (0.6.XX) - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: ROCKPRO64 (https://forum.pine64.org/forumdisplay.php?fid=98)
+--- Forum: Linux on RockPro64 (https://forum.pine64.org/forumdisplay.php?fid=101)
+--- Thread: [Archived] Initial Linux release from ayufan (0.6.XX) (/showthread.php?tid=6085)

Pages: 1 2 3 4 5

RE: Initial Linux release from ayufan (0.7.X) - pfeerick - 05-28-2018

(05-27-2018, 11:14 AM)Bullet64 Wrote: For me bionic-minimal-rockpro64-0.6.43-238-arm64.img works stable. 234 was unstable!

Yeah, the 0.7.x series has been axed as the rockpro64 images are being generated side by side with the rock64 images, so at the time of writing 0.6.44 is the latest image for both the rock64 and rockpro64.

RE: Initial Linux release from ayufan (0.6.XX) - deeproot - 05-31-2018

I am only able to get to where the kernel complains about the memory and just shuts down. Is there anything extra todo besides just burning the images to sdcard with etcher? I was able to get android up and running with no problem.

RE: Initial Linux release from ayufan (0.6.XX) - pfeerick - 05-31-2018

(05-31-2018, 01:09 PM)deeproot Wrote: I am only able to get to where the kernel complains about the memory and just shuts down. Is there anything extra todo besides just burning the images to sdcard with etcher? I was able to get android up and running with no problem.

As the rockpro64 is still brand spanking new (you can till smell the plastic), there will be problems. If you are using the right image (note the rockpro64/rock64 filenames), and it doesn't work, report the issue on github (mark it clearly as a rockpro64 issue) or here on the forum, and give whatever logs you can. For me, 0.6.44 just booted up and is running fine so far on a 4GB rockpro64. Running bionic-containers atm, but haven't had time to play around with it much other to get it booting and do a quick stress test on the cpu to see how the thermals, check the leds works, and see if docker could at least run the hello world container.

You should no needed to do anything more than burn the image to a SD card (with etcher, etc). If you have a different brand of card, try that, as it could be

RE: Initial Linux release from ayufan (0.6.XX) - deeproot - 05-31-2018

(05-31-2018, 05:08 PM)pfeerick Wrote:
(05-31-2018, 01:09 PM)deeproot Wrote: I am only able to get to where the kernel complains about the memory and just shuts down. Is there anything extra todo besides just burning the images to sdcard with etcher? I was able to get android up and running with no problem.

As the rockpro64 is still brand spanking new (you can till smell the plastic), there will be problems. If you are using the right image (note the rockpro64/rock64 filenames), and it doesn't work, report the issue on github (mark it clearly as a rockpro64 issue) or here on the forum, and give whatever logs you can. For me, 0.6.44 just booted up and is running fine so far on a 4GB rockpro64. Running bionic-containers atm, but haven't had time to play around with it much other to get it booting and do a quick stress test on the cpu to see how the thermals, check the leds works, and see if docker could at least run the hello world container.

You should no needed to do anything more than burn the image to a SD card (with etcher, etc). If you have a different brand of card, try that, as it could be


How can I dump logs somewhere to show them?
https://i.imgur.com/J6CIneM.jpg

Archlinux laptop
etcher 1.44
official psu from pine64
passive heatsink from pine64


images used: 
stretch-minimal-rockpro64-0.6.44-239-arm64.img
bionic-minimal-rockpro64-0.6.43-238-arm64.img
bionic-containers-rockpro64-0.6.44-239-arm64.img

sdcards used
sandisk ultra plus 16gb microsd hc(red / grey)
I did use the sandisk to boot the android image from pine64.

samsung evo 32 microsd hc(orange / white)

tried another laptop with windows and w32disk imager...same thing.

Problems with Initial Linux release from ayufan (0.6.XX) - superpat - 06-01-2018

Hi,

I am having problems with ayufan's distros from  git hub. trying to write the sd card with my Linux Mint system, which has always written  successfully hundreds of times in the past.

1. Git hub appears crippled, keeps dropping d/l transfer, I installed a Linux file downloader and have to keep restarting, but still takes forever to get a complete download.


2. After writing  bionic minimal .img to a fresh fat32 formatted SD card , I can mount the boot partition on my Linux Mint pc, and look at the files, HOWEVER the root-fs partition is formatted to ext4, and for some reason will not mount.

If look at the card with gparted it looks like the partitioning is most unusual, if not incorrect.

I see 5  unknown partitions about 3-4 MiB in length, The first unknown is at block 64.
then partition 6 the Boot partition, fat16, 112Mib, starting at 32768
partition 7 is the linux-root partion formatted to ext4 2GiB in size starting at 262144


I have tried a dozen good sd cards and linux dd, etcher and Mint usb stick writer, all of which normally work

When trying to boot the rockpro board, I see a second or so of leds flashing in the ethernet connector but nothing else happens.

I have tried  bionic minimal and bionic lxde, same problem  DEFINITELY writing the distro for the rockpro!

any advice gratefully received

Patrick

RE: Initial Linux release from ayufan (0.6.XX) - mikeD - 06-01-2018

This is exactly what I see when I use Windows system to image the SD. I get 5 partitions and a Boot partition.
When I try and run the image on the RockPro. You see an inital startup of linux booting with some messages, Then what looks like empty blocks of zeros going up the screen. Then finally either finishing with a message that says restart in 10 secs. followed by blank screen.
Occasionally it will go further and then hit the memory error reported earlier, and then hangs.
This is what led me a few others to conclude we are missing a step, and that the system is not fully built.

RE: Initial Linux release from ayufan (0.6.XX) - superpat - 06-01-2018

(06-01-2018, 07:10 AM)mikeD Wrote: This is exactly what I see when I use Windows system to image the SD. I get 5 partitions and a Boot partition.
When I try and run the image on the RockPro. You see an inital startup of linux booting with some messages, Then what looks like empty blocks of zeros going up the screen. Then finally either finishing with a message that says restart in 10 secs. followed by blank screen.
Occasionally it will go further and then hit the memory error reported earlier, and then hangs.
This is what led me a few others to conclude we are missing a step, and that the system is not fully built.

Hi Mike

You appear to have we'd up a serial console,  I need to do the same.  What pins are youusing to connect the uart rx and tx?

Thanks Patrick

RE: Initial Linux release from ayufan (0.6.XX) - Bullet64 - 06-01-2018

Pin 6,8,10

[Image: Rockpro64%20Pi-2%20Connector%20ver0.2.png]

RE: Initial Linux release from ayufan (0.6.XX) - superpat - 06-01-2018

(06-01-2018, 02:31 PM)Bullet64 Wrote: Pin 6,8,10

[Image: Rockpro64%20Pi-2%20Connector%20ver0.2.png]

Hi
That is what I thought, but I have tried two usb to uart adaptors I had with no success, wired to those pins.
Do these cheap adaptors work at 1500000 baud, is that the correct speed?
Cheers Patrick

RE: Initial Linux release from ayufan (0.6.XX) - pfeerick - 06-01-2018

(06-01-2018, 03:23 PM)superpat Wrote: Do these cheap adaptors work at 1500000 baud, is that the correct speed?

Yeah, 1.5M or 1500000 is the correct speed. My USB to serial console cables (ch341 based) work fine, but do seem a bit more temperamental with the rockpro64 output, so it looks like it might be pushing some slightly off-spec output at times when booting.

Also, with regards to the partition layout, that sounds correct. When booting directly from the SD card, the card needs to be laid out in format in order for it to be able to find what it needs to start booting.

Code:
Device          Start      End  Sectors  Size Type
/dev/mmcblk0p1     64     8063     8000  3.9M Linux filesystem
/dev/mmcblk0p2   8064     8191      128   64K Linux filesystem
/dev/mmcblk0p3   8192    16383     8192    4M Linux filesystem
/dev/mmcblk0p4  16384    24575     8192    4M Linux filesystem
/dev/mmcblk0p5  24576    32767     8192    4M Linux filesystem
/dev/mmcblk0p6  32768   262143   229376  112M Microsoft basic data
/dev/mmcblk0p7 262144 31225822 30963679 14.8G Linux filesystem

Code:
Number  Start (sector)    End (sector)  Size       Code  Name
   1              64            8063   3.9 MiB     8300  loader1
   2            8064            8191   64.0 KiB    8300  reserved1
   3            8192           16383   4.0 MiB     8300  reserved2
   4           16384           24575   4.0 MiB     8300  loader2
   5           24576           32767   4.0 MiB     8300  atf
   6           32768          262143   112.0 MiB   0700  boot
   7          262144        31225822   14.8 GiB    8300  root