+- PINE64 (https://forum.pine64.org)
+-- Forum: PINE A64-LTS / SOPINE Compute Module (https://forum.pine64.org/forumdisplay.php?fid=66)
+--- Forum: General Discussion on PINE A64-LTS / SOPINE (https://forum.pine64.org/forumdisplay.php?fid=67)
+--- Thread: Unable to boot up [Solved] (/showthread.php?tid=4479)
Unable to boot up [Solved] - bobpaul - 04-25-2017
Got a couple of the sopine + baseboard + power combos. They just arrived, but neither seems to boot. I've tried several images on the SD-Card including the currated sopine Ubuntu image from the wiki: http://wiki.pine64.org/index.php/Main_Page#Curated_Sopine_OS_Images
I create the sdcard using
Code:
zcat name.img.gz | sudo dd of=/dev/sdg bs=1M oflag=syncPlugged into the baseboard I have an HDMI cable to a monitor, an ethernet cable, and the barrel power cable. The SD-Card is in the SOPINE and when powered there is a green LED on the baseboard and on the SOPINE. The monitor just always says there's no signal and nothing lights up on the ethernet jack.
I'm using a 16GB "Transcend Premium" SD-Card.
RE: Unable to boot up - Luke - 04-25-2017
(04-25-2017, 12:29 PM)bobpaul Wrote: Got a couple of the sopine + baseboard + power combos. They just arrived, but neither seems to boot. I've tried several images on the SD-Card including the currated sopine Ubuntu image from the wiki: http://wiki.pine64.org/index.php/Main_Page#Curated_Sopine_OS_Images
I create the sdcard using
Code:zcat name.img.gz | sudo dd of=/dev/sdg bs=1M oflag=sync
Plugged into the baseboard I have an HDMI cable to a monitor, an ethernet cable, and the barrel power cable. The SD-Card is in the SOPINE and when powered there is a green LED on the baseboard and on the SOPINE. The monitor just always says there's no signal and nothing lights up on the ethernet jack.
I'm using a 16GB "Transcend Premium" SD-Card.
1) what is the resolution of the monitor ?
2) do the ethernet port LEDs blink?
if yes
3) have you tried to ssh into the SoPine ?
RE: Unable to boot up - dkryder - 04-25-2017
there is only one sopine image i'm aware of and it is on the resources tab of the sopine page. xubuntu-xenial-mate-20170306-longsleep-sopine-8GB.img 5,242,880 filesize
RE: Unable to boot up - Luke - 04-25-2017
The ubuntu and android images worked for me just fine ...
RE: Unable to boot up - dkryder - 04-25-2017
i have only used the xenial and it works good. but one thing i did learn is the kernel update process about a month ago, maybe it has been fixed, would update with the pine64 kernel which would not boot and actually behaved just like the description by bobpaul. i also just looked and the image has been removed from the resources tab of the page i mentioned. another thing i wanted to mention about something i do with sodimm cards, mostly memory but also the sopine, is to clean with alcohol and insert/remove several times because there is always a chance for some type of manufacturing coatings on the trace tabs or connectors of the card or the baseboard. also,bobpaul, give etcher a try on writing the image just to eliminate the possibility of your command and/or dd not handling the image properly.
RE: Unable to boot up - bobpaul - 04-26-2017
(04-25-2017, 12:33 PM)Luke Wrote: 1) what is the resolution of the monitor ?
2) do the ethernet port LEDs blink?
if yes
3) have you tried to ssh into the SoPine ?
1. 1080p (it's this monitor http://a.co/fMHyTtx)
2. The ethernet port LEDs did not blink.
I grabbed an 8GB sd-card I had in a RasbPi and flashed that with android and it worked. Then I flashed it with the Xubuntu image and that worked, too.
And now it's working fine with the 16GB Transcend card. I'm not sure what I was doing wrong.
(04-25-2017, 02:35 PM)dkryder Wrote: another thing i wanted to mention about something i do with sodimm cards, mostly memory but also the sopine, is to clean with alcohol and insert/remove several times because there is always a chance for some type of manufacturing coatings on the trace tabs or connectors of the card or the baseboard. also,bobpaul, give etcher a try on writing the image just to eliminate the possibility of your command and/or dd not handling the image properly.
Both of these seems like reasonable explanations for why it didn't work. Etcher looks like a useful tool; I'll try that next time.