(05-17-2018, 07:54 AM)joemassimino Wrote: I deleted it, I told you it booted, so the image was right, since all the other files I get when I go to the R18 LTS link for files, don't boot. So Pine has a screwy web site, as it points to files that don't work on the board you get the link for. The Ubuntu I loaded had to be the only Ubuntu they made for the R18, as it was the only one that booted and gave me a login. The problem is that the passwords supplied did not work. So they need to get someone to go over the web site and make sure that the files they link customers to for the board, actually work on the board. As it is now, I have not found a Linx file for the R18 LTS that actually works yet. I wanted to return this board as a piece of junk, but they ignore my request and just ask me more questions. The R18 has terrible support in every way. I would want to load Raspbian on the board, but that is out of the question, and every other linux version i try to load either does not boot, because it is the wrong file, or it works, but the password and username supplied with the file does not work. I program Arduino, I work with Raspberry pi, and I never had so many issues in getting a board to work. The Raspberry pi might not be as powerful, but it can run circles around the Pine R18 just because it has so many operatings systems that work on it. Pine just didn't get it, the support is what makes the board, not necessarily just the hardware. They fell really short on support.
You still have not answered the one question asked - what image did you download? - Tell us where it was on the wiki / website / where it was linked, then once everyone knows what image is being spoken about, the issue of the password may be able to identified. It is possible you have downloaded an image from ayufan's site instead, which documents the username/passwords as being pine64/pine64.
Trace.Call is probably a notification from the kernel that something crashed, and that a call trace log dump has been generated showing the functions called and resulting errors, etc.
As far as working images with the pine64 LTS - have you been downloading the correct images? You need to be using images meant for the sopine, not for the pine64 - or as stated on the wiki in red print above the list of downloads "SOPine OS images are compatible with PINE A64-LTS".
