PINE64

Full Version: DOA board?
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Got my board a few weeks ago and no matter what I do, I never get any video output.

I've tried each of these on multiple cards:
Remix OS 2.0 Image Release 20160415 [BETA], PhoenixCard image
Android 5.1.1 Image (HDMI Video Output) Release 20160505, PhoenixCard image
Ubuntu Linux Image [20160530] based on Longsleep work, build by
Pine64, written with Win32 Disk Imager

Each time I've left it for at least 20 minutes, and nothing.
I've also tried 3 different power adapters and USB cables. 5.2V/2A, 5V/2A and 5V/1.8A

Has anyone got any other suggestions?
My money would be on incompatible display for the default settings if the images were flashed correctly. If you take a recent Linux image like https://www.pine64.pro/download.php?opti...ptionid=39 , download that, unzip with 7zip, flash with win32diskimager... do the leds on the ethernet jack light up when you plug in the cable? Do you get a login if you use putty or ssh to connect via the network to the Pine?
Me experience says something is wrong with official releases. I managed to boot from Android 5.1.1 and also Longsleep's Linux images (I personally use latest Debian release). In both situations my board boot up in less than a 2 minutes.
I suggest to try Longsleep's images and to burn them with Win32 Image (I think it is also available on his site www.pine64.pro)
For start use higher amps power supply.
And do unpacking of downloaded file (image is usually packed even it says it is img file) to get proper IMG file.
Alright, I get SSH with Debian MATE, but still no video. I'm using a 1080p HDTV and defaults are 720p60. Now tried 3 different HDMI cables (all work with my laptop, PS3 and Pis), as well as 1080p50/1080p60/720p50/480p, still no video.


Edit:
It seems it is very picky about HDMI cables. I found another cable which works with it, but none of my others do.. but still work with every other HDMI device I've got.
I also tried with a coupler, the cable that didn't work on its own works fine if it is *after* one that does work. Maybe bad port on my board...
Sounds like an oxidation problem... maybe time to clean some connectors.