After some problems with my 0.6.44 install, I decided to go for a fresh installation.

I tried to wipe my 64GB eMMC to carry out a fresh install but whatever I did, it was no longer accessible by Etcher in Win 10 or Linux (Xubuntu 18.04). I tried many things such as deleting partitions in gparted, but gparted could not delete partitions nor set up a new partition table.

Both Win10 and Linux insisted that the eMMC was only 32MB in size, so I was stuck, however I was able to load xenial mate image 0.5.15 onto a SD Card, and use the pin shorting method to get this onto the eMMC card, as described in the wiki article. Pine wiki rock software releases

That ran fine, so I knew that the eMMC card was not faulty, however I also knew that the update would break the OS, which it duly did.

Eventually, out of desperation, I flashed an SD Card with aufan's 0.6.44 image and running that, with the eMMC installed, I managed to do the following on the Rock 64

1. Through gparted, I deleted the main root partition, the one that was over 50gb in size.
   
2. I ran /usr/local/bin/rock64_reset_emmc.sh (sudo ./rock64_reset_emmc.sh) (I took a clue from the wiki - noobs - troubleshooting your device, although the advice was for the Pine64 and was about using /ussr/local/sbin/update_script.sh which was not available for the rock64 - yes I was getting desperate with what appeared to be a dead eMMC card)
   

http://www.raspbsd.org/pine64.html

Thanks to @jmcneill for creating the builds!!!

• Download latest from http://www.invisible.ca/arm/
  
• dd'it to a microsd. In linux:
  

• Plug the microsd into the pine
  
• Boot the pine and wait for a couple of reboots (disk expansion)
  
• Login as root (no password)
  
• Configure password for root user
  

• Create user (in my case, 'edu') and add it to the wheel group
  

• Edit /etc/wpa_supplicant.conf with the appropriate ssid/psk:
  

• Editing /etc/rc.conf to enable wpa_supplicant at boot. Notice my usb wireless adapter is urtwn0 (ifconfig will show you all the adapters):
  

• Start wpa_supplicant service:
  

• Verify it:
  

I've had my Pinebook since July of last year but haven't been using it as much as I thought I would.  

I have a 14" Pinebook with 16 GB eMMC that has seen maybe 15 hours of use since I received it.  The screen has one dead pixel (it arrived like that from the factory) but other than that is in great condition. 

I'm located in the US in Philadelphia and could meet locally or ship.  I can provide pictures upon request as well as proof of purchase.

$90 + Actual Shipping Costs  (Send me a message with your shipping address and I can look up costs)


(I had posted a thread earlier looking for a trade, but didn't get any bites.  If that may interest you check out the original thread here: https://forum.pine64.org/showthread.php?tid=5975)

Running under the Android OS. v7, I think.

My Rock 64 often will not make an ethernet connection to my router during boot up or alternatively it connects initially but then drops its connection randomly, while streaming video, and then will not reconnect on reboot.

Other devices on the network, computers/phones have no problem with their connection, either wired (computers) or wireless(phones only).

I've swapped over cables and wall blocks without any change. These experiments suggest the problem lies with the Rock64 itself as its connective hardware has been substituted for known good items and the problem persists.

Its a bit of a nuisance.

Can anyone suggest a solution before I run off and buy a wireless dongle?

Thanks in advance as always.

Hi, any idea what is the sleep current for Pinebook or other Pine A64 boards?

Is it possible to get sleep current to as low as like <2mA?

Thanks.

Hello,
I am looking for help with setting the Pine64 LTS upper USB port as a USB Device(serial port)

My setup:
Pine64 LTS
Armbian_5.38_Pine64so_Ubuntu_xenial_default_3.10.107( I have also tried Armbian_5.35_Pine64so_Ubuntu_xenial_default_3.10.105 with the same results)
Original kernel configuration: Original kernel configuration
My current configuration: My current configuration
Kernel sources I use are form armbian package linux-source-default-pine64_5.38_all.deb and contain git versioning information with remote repository at https://github.com/ayufan-pine64/linux-pine64

What I tried:
Rebooting without SD card into FEL mode to see if Pine will be enumerated on my PC, this works ok, so the actual connection works and the USB port on the Pine I picked is the correct one.

Armbian seem to be lacking the g_serial driver, so I recompiled the kernel with gadget support + g_serial module.
From what I understand https://www.kernel.org/doc/Documentation...serial.txt, doing :
Code:

I'm able to play some x265 videos but not all.  It seems that it's the ones that are encoded in 10bit are the ones that won't play, but I'll admit I don't know everything about encoding specs. 

I typically use VLC or MX Player.  Would something else be better? 

I assume others are using their Rock64 to play x265 media files.  How's it working?

There are two different "development status types" of OS images available from ayufan on his GitHub; Releases and Pre-Releases (examples in attached pictures).

Releases are end-user and production ready OS images that are deemed stable.
In contrast, Pre-Releases are OS images that are in a not stable, are meant for testing, and frequently may not even boot.

Unless you wish to help with testing and/or development, or accept the risk associated with running an alpha image, please always use OS images lableled Release for your use-case.

Release



Pre-Release

Chào mọi người !
Tôi havent thấy bất kỳ hình ảnh os phát hành được đăng để thử nghiệm hoặc cho những người có ban phát hành trước hoặc cách khác. Tôi đoán im chỉ hỏi hình ảnh os chúng ta sẽ thấy khi lô hàng đầu tiên nếu chúng tôi đặt hàng trước?

Im quan tâm đến debian chủ yếu, nhưng im cũng quan tâm đến những gì els e sẽ có sẵn. Với mức giá này có thể thay thế một số pi cho tôi.