Pine64+ and Pine64+2GB have a Gigabit NIC. To actually test the speed of the network interface a few things need to be considered. If you want to test the NIC performance of your Pine64, this thread is for you.

To do any meaningful testing, you need another device which is well known and capable to deliver over 900MBit/s with the cable and switch it is connected to. Also make sure that the network cable you use for the Pine64 is working with Gigabit Network (8 wires twisted pair, Cat5e or Cat6).

It is important to understand that you should test network speed only. If you copy a file to the Pine or something you are testing something completely different.

Furthermore it is important to know the settings of the whole stack involved and always use same / good settings. I added a platform-script at https://github.com/longsleep/build-pine6...network.sh to help with that. Make sure to run this or similar before any testing.

- Make sure you use the latest Kernel. `uname -a`

Hi I have recently received my package containing the pine a64 mother board, with lcd display, package is missing the shutdown button, and also the abs case at the Moment.Anyway I received also the 7" LCD Display, I have connected the cables as it was documented in this Forum guide. I did not do any OS upgrade yet, but when I start the os boot up, Display does not light up. I tried to move the ribbon cables attached on the dsi port, and if moved, starts flashing like it was going to start, but then nothing.
I think that the Motherboard or the ribbon cable is defected. Any suggestions?
Thanks

I have been playing around with the pine for a week now.  Under android it is only showing 2 cores.  I have other apps showing the same.  Is there a way to unlock them? I'm new to these boards and I know there is much development to do.  But can anyone give me solution to this.

The BSP Linux Kernel does automatically generate a locally administered MAC address for the Ethernet (eth0) interface.

Some networks might not be able to handle those correctly. The recommended solution is to manually set the MAC address to the one which is printed on the back of the Pine64 by adding it to /boot/uEnv.txt with a line like ethaddr=xx:xx:xx:xx:xx:xx.

The MAC address is the lower number on the barcode label on the back of your Pine board. Start from the left and add a colon every two chars. So far they all seem to start with 00:06:dc making this the vendor prefix.

Hi, I hope someone can help me out.

I am trying to get a Prolific 2303 usb to serial adapter to work with the latest debian Base release (pine64-image-debianbase-310102bsp-2). The adapter works on a RPI but on the Pine you can see the plugged in adapter but it does not get linked to a tty-usb port. Other usb to serial adapters of a different make do get attached to a tty-usb port.

Is the driver included in the build?

Regards,
Jelle

Trying to get Guitarix to run on the Pine64 and it needs me to set up and configure jackd.  I've never had good luck with that.  Anyone here manage to get it configured / working?

I figure if I can get it to work, I can salvage an old amp into a pretty spiffy Pine64 powered multi-effects practice amp.

Create a minimal Ubuntu rootfs from Longsleep's Ubuntu image using pine64-debootstrap. This is if you want to create a minimal server image (the way you want to roll it) with wifi instructions. Just a couple easy scripts and some interactive prompts to answer and you will have a rootfs archive ready to write to SD.

Hello!

I have installed the Ubuntu release a long time ago on my Pine, and everything worked fine. Main use was with an DVB-C stick and tvheadend as a Videoecorder.

I updated the Ubuntu software regularly and the system worked fine.

With the last updated Ubuntu told me to reboot the system, and from that moment on, startup did not complete.

I get an error "[VFE_ERR]Error registering ve412 subdevice No such device!" and "[VFE_ERR]vfe_register check error at input_num = 0 " (and later 1).

My Pine is connected via eth0 - and as I said before this configuration worked for a very long time..."

Help plz!

Thanks!

Is possible to use two wires as Power and Reset Bottons? If so, in which holes I have to solder them? The more distant or closest?

I ran into a very frustrating yet interesting problem last night when I tried to place two of my PineA64 boards on the same ethernet switch in preparation for the GbE testing I plan to do tomorrow.

Both of my machines had a VERY persistently stubborn mac address ( which belongs to longsleep ):
36:c9:e3:f1:b8:05

I am wondering now how many folks having ethernet problems don't really have an ethernet problem, they just don't have unique mac addresses on their network from the Pine Boards ??  (arp cache nightmare)

Anyway, I tried repeatedly to change the mac addresses of both machines... and they would NOT change... neither of them... for almost four hours.

I changed the mac address in  /boot/uEnv.txt  , powered off and then did a cold boot.  (this on both machines)  but when the boot finished  both machines still had address  36:c9:e3:f1:b8:05

Believe it or not what I did to correct this was just be persistent... I started waiting longer between poweroff and cold boot...  eventually the new address finally 'took' on both machines.  When the address finally 'took' on both machines, both machines finally had the correct address in all four primary places:
/boot/uEnv.txt
/proc/cmdline
/sys/class/net/eth0/address
ifconfig

I really feel strongly that this needs to be changed. All Pine Boards need to have an automatic persistent unique mac address on the ethernet port;  like any other IP machine interface. Or, there needs to be a very consistent way to set the persistent mac address easily so that multiple Pine Boards on the same switch are guaranteed to have unique mac addys;  essential for Pine-Nut  clusters !

edit: PS. I suspect that the mac address of choice has something to do with this as well... it may be that I just happened upon a prefix that would work... but took some trial and guessing. But, its looking like the mac address can not be fully ransomized.