Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 30,272
» Latest member: PrinterSolvedTeam
» Forum threads: 16,394
» Forum posts: 117,654

Full Statistics

Latest Threads
Printing from Mobian
Forum: Mobian on PinePhone
Last Post: PrinterSolvedTeam
10-27-2026, 06:01 AM
» Replies: 3
» Views: 4,914
Satellite antenna
Forum: Community and Events
Last Post: biketool
10-26-2026, 02:46 PM
» Replies: 2
» Views: 535
Irradium (based on crux l...
Forum: Linux on Pinebook
Last Post: mara
10-25-2026, 04:11 AM
» Replies: 5
» Views: 14,885
Booting Issues
Forum: PineNote Software
Last Post: vlagged
10-23-2026, 12:14 PM
» Replies: 25
» Views: 26,083
Alpha One - no connectivi...
Forum: Getting Started
Last Post: Dabdarklighter
10-22-2026, 03:51 PM
» Replies: 1
» Views: 1,173
Article: The Advantages o...
Forum: General
Last Post: zetabeta
10-20-2026, 02:38 PM
» Replies: 2
» Views: 399
Star64 Irradium (based on...
Forum: Getting Started
Last Post: mara
10-19-2026, 12:27 PM
» Replies: 22
» Views: 21,477
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
10-19-2026, 10:01 AM
» Replies: 25
» Views: 16,228
Article: Will Linux phone...
Forum: General
Last Post: amosbatto
10-19-2026, 09:52 AM
» Replies: 11
» Views: 1,503
Login issues
Forum: PineTab Hardware
Last Post: Corkonian
10-17-2026, 02:34 AM
» Replies: 2
» Views: 484

 
  pine LTS with openBSD
Posted by: sean - 04-12-2018, 10:56 PM - Forum: General Discussion on PINE A64-LTS / SOPINE - Replies (4)

Hi All,

I received the pine64 LTS board today and would like to load openBSD on to it. I have openBSD current snapshots running on a much older (from February 2016ish) pine64 board without any issues.

I did what I did last week to install openBSD on the working board:


Code:
sudo dd if=miniroot63.fs of=/dev/sdf bs=1M


Hooked up the serial connection, applied power and all I receive in the terminal is this:


Code:
U-Boot SPL 2018.03 (Mar 20 2018 - 04:43:06 -0600) DRAM: 0 MiB ### ERROR ### Please RESET the board ###


So what's it mean? Do I need to have the spi flashed with something? Does openBSD need to add support for this u-boot? Do I need an eMMC thing?
Here's the installation instructions for arm64:
https://ftp.openbsd.org/pub/OpenBSD/snap...TALL.arm64
https://www.openbsd.org/arm64.html

LTS is missing, but I do see this: "Pine64 Pine 64/64+" Is this separate from LTS?

Thanks,
sean


Lightbulb Looking for donor board to replace voltage regulator or any other ideas?
Posted by: ansic - 04-12-2018, 10:57 AM - Forum: Rock64 Hardware and Accessories - Replies (1)

My Rock64 have a faulty voltage regulator.  The breakdown happened from a faulty power supply adapter.  It can still boot up a Linux OS but there are a few complications.. HDMI is not working and Its very slow to execute programs.  The error messages are about voltage regulator not responding to the I2C messages so I figured replacing the RK805 voltage regulator might fix it.

The problem is that I don't have a spare RK805 and Pine64 does not want to sell me one, it's understandable but a bummer since there are is nobody else with these chips.  That is why I am asking here for advice.


  rock64-config ?
Posted by: vincent37 - 04-12-2018, 08:19 AM - Forum: Linux on Rock64 - Replies (4)

Hello,

I do not have the skills to create this interface style yet very handy.

This could be useful... When do you think to personalize it and make it reliable for the rock64 with debian ?

You can test what exists for Asus Tinkerboard

wget https://raw.githubusercontent.com/mikerr...ker-config

sudo sh tinker-config


  I could not start ROCK 64.
Posted by: pine3228 - 04-12-2018, 07:08 AM - Forum: Linux on Rock64 - No Replies

Google Translate : 
axel -a -n 5 https://github.com/ayufan-rock64/linux-b...m64.img.xz && xz - dv bionic - minimal - rock 64 - 0.6.31 - 209 - arm 64. img. xz && sudo dd if = bionic - minimal - rock 64 - 0.6.31 - 209 - arm 64. img of = / dev / sda

I tried starting up ROCK 64 using such a command, but unfortunately I could not start it. (White lamp, green lamp and red lamp are in a state of lighting) I suspected that the image file was damaged, but I will not change how many times. However, writing 0.5.15 xenial and artful images on the micro sd card, I was able to launch it. The same problem occurred in the images of bionic (arm64) of 0.6.25, 0.6.26, and 0.6.27. What should I do?

Also, I have another question.
https://dl.armbian.com/rock64/
Although it is an image of armbian distributed here, it was also impossible to start up here. Apparently, there seems to be no boot partition, but how do you start it?



原文
axel -a -n 5 https://github.com/ayufan-rock64/linux-b...m64.img.xz && xz -dv bionic-minimal-rock64-0.6.31-209-arm64.img.xz && sudo dd if=bionic-minimal-rock64-0.6.31-209-arm64.img of=/dev/sda

私はこのようなコマンドを使い、ROCK64の起動を試しましたが、残念ながら起動することができませんでした。(白のランプと緑のランプと赤のランプが光りっぱなしの状態)私は、イメージファイルの破損を疑いましたが、何度やっても変わりません。しかし、マイクロsdカードに0.5.15のxenialとartfulのイメージを書き込んだところ、起動することができました。この問題は、0.6.25、0.6.26、0.6.27のbionic(arm64)のイメージでも同じことが起きました。どうすればいいのでしょうか?

それと、もう一つ質問があります。
https://dl.armbian.com/rock64/
こちらで配布されてるarmbianのイメージですが、こちらも起動することができませんでした。どうやら、bootパーティションなどが無いようなのですが、どのようにして起動するのですか?


  Clusterboard i2c and Linux
Posted by: jgullickson - 04-11-2018, 09:45 AM - Forum: Clusterboard - Replies (3)

Hello all,

I'm trying to connect an MCP23017 to the i2c bus on one of the Clusterboard's headers (J4) and I'm unable to see it from Linux using i2cdetect:

Code:
jjg@pine64so:~$ sudo i2cdetect -y 0      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f 00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- --                          jjg@pine64so:~$ sudo i2cdetect -y 1      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f 00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- --                    
    

I had the same problem interfacing this same chip to a full-size A64 board and resolved it by adding some pull-up resistors to the i2c pins (connecting them to the 3.3v supply as suggested in this thread: https://forum.pine64.org/showthread.php?tid=2079&page=2).  However the Clusterboard doesn't supply 3.3v at this header.

I'm not sure how best to proceed.  Assuming the pull-ups are required on the Clusterboard as they are on the A64, do I need to provide a 3.3v supply (perhaps stepping the 5v supply down to 3.3v) or is there a better way to achieve the same thing?

It seems weird to me that the header would supply the i2c pins if they couldn't work without external regulation but then again I'm pretty new to working with i2c and maybe this is normal?

Any pointers are appreciated, thanks!


  Help pls~Desktop (xfce4/lxde/gnome/i3) installation problem. Install_desktop.sh faild
Posted by: yours_david - 04-10-2018, 11:41 PM - Forum: Linux on Rock64 - No Replies

Hi Pine64 community, 

I have been very happy to have Rock64 running openmediavault to manager my 3 HDDs for share, 2 HDDs sitting on USB3 HDD dock for non-raid share, 1 HDD USB2 running cold backup. Now I would like to install desktop, e.g. xfce4/lxde/gnome/i3, on top of my OMV image. I run "install_desktop.sh" script from "/usr/local/sbin/" after searching through forum and internet. 

The installation progress get stuck while fetch plex, the error code is in below. The full details list at bottom for better reading.

Code:
E: Failed to fetch https://downloads.plex.tv/repo/deb/dists/./public/InRelease                     Unable to find expected entry 'main/binary-armhf/Packages' in Release file (Wron                   g sources.list entry or malformed file) E: Some index files failed to download. They have been ignored, or old ones used                    instead.


My firmware based on 0.6.31: jenkins-linux-build-rock-64-209, which was upgraded from 0.6.28: jenkins-linux-build-rock-64-197 by running "sudo apt-get update -y & sudo apt-get install linux-rock64 -y". 

As a linux noob, I tried what I can but still failed to install xfce4 then run KODI while running OMV at background. 
I checked install_desktop.sh trying to comment off fetch plex in order to continue such installation, but I can't find anything. 
I also run "apt-get install xfce4", but don't know how to run xfce4. 

Can anyone help me to run OMV+HTPC Kodi solution on my rock64 NAS build? Two questions.

Q1, how to fix install_desktop.sh?
Q2, without that .sh strip, how can I install xfce4 and kodi then run based on OMV rock64 firmware? Thank you for any advise.

Cheers, 
David

Full log which run install_desktop.sh

Code:
root@NAS-David:/usr/local/sbin# install_desktop.sh xfce4 Get:1 file:/var/cache/openmediavault/archives  InRelease Ign:1 file:/var/cache/openmediavault/archives  InRelease Get:2 file:/var/cache/openmediavault/archives  Release Ign:2 file:/var/cache/openmediavault/archives  Release Get:3 file:/var/cache/openmediavault/archives  Packages Ign:3 file:/var/cache/openmediavault/archives  Packages Get:4 file:/var/cache/openmediavault/archives  Translation-en Ign:4 file:/var/cache/openmediavault/archives  Translation-en Get:3 file:/var/cache/openmediavault/archives  Packages Ign:3 file:/var/cache/openmediavault/archives  Packages Get:4 file:/var/cache/openmediavault/archives  Translation-en Ign:4 file:/var/cache/openmediavault/archives  Translation-en Get:3 file:/var/cache/openmediavault/archives  Packages Ign:3 file:/var/cache/openmediavault/archives  Packages Get:4 file:/var/cache/openmediavault/archives  Translation-en Ign:4 file:/var/cache/openmediavault/archives  Translation-en Get:3 file:/var/cache/openmediavault/archives  Packages Ign:3 file:/var/cache/openmediavault/archives  Packages Get:4 file:/var/cache/openmediavault/archives  Translation-en Ign:4 file:/var/cache/openmediavault/archives  Translation-en Get:3 file:/var/cache/openmediavault/archives  Packages Ign:3 file:/var/cache/openmediavault/archives  Packages Get:4 file:/var/cache/openmediavault/archives  Translation-en Ign:4 file:/var/cache/openmediavault/archives  Translation-en Get:3 file:/var/cache/openmediavault/archives  Packages Get:4 file:/var/cache/openmediavault/archives  Translation-en Ign:4 file:/var/cache/openmediavault/archives  Translation-en Hit:5 http://security.debian.org stretch/updates InRelease Hit:6 http://ppa.launchpad.net/ayufan/rock64-ppa/ubuntu bionic InRelease Get:7 https://download.docker.com/linux/debian stretch InRelease [39.1 kB] Get:11 https://downloads.plex.tv/repo/deb ./public InRelease [3408 B] Hit:12 http://packages.openmediavault.org/public arrakis InRelease Ign:14 https://dl.bintray.com/openmediavault-plugin-developers/arrakis stretch I                   nRelease Ign:15 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-testing s                   tretch InRelease Ign:16 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-plex stre                   tch InRelease Get:17 http://deb.ayufan.eu/orgs/ayufan-rock64/pre-releases  InRelease [1253 B] Ign:18 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-sync stre                   tch InRelease Hit:19 https://openmediavault.github.io/packages arrakis InRelease Ign:20 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-docker st                   retch InRelease Hit:9 https://apt.syncthing.net syncthing InRelease Get:21 https://dl.bintray.com/openmediavault-plugin-developers/arrakis stretch R                   elease [4389 B] Hit:21 https://dl.bintray.com/openmediavault-plugin-developers/arrakis stretch R                   elease Hit:8 http://cdn-fastly.deb.debian.org/debian stretch-backports InRelease Ign:10 http://cdn-fastly.deb.debian.org/debian stretch InRelease Hit:13 http://cdn-fastly.deb.debian.org/debian stretch-updates InRelease Hit:22 http://cdn-fastly.deb.debian.org/debian stretch Release Get:24 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-testing s                   tretch Release [4389 B] Hit:24 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-testing s                   tretch Release Get:26 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-plex stre                   tch Release [3540 B] Hit:26 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-plex stre                   tch Release Get:29 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-sync stre                   tch Release [3540 B] Hit:29 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-sync stre                   tch Release Get:31 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-docker st                   retch Release [3540 B] Hit:31 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-docker st                   retch Release Fetched 43.8 kB in 8s (5031 B/s) Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at                    0xf6ca1468> Traceback (most recent call last):  File "/usr/lib/python3.5/weakref.py", line 117, in remove TypeError: 'NoneType' object is not callable Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at                    0xf6ca1468> Traceback (most recent call last):  File "/usr/lib/python3.5/weakref.py", line 117, in remove TypeError: 'NoneType' object is not callable Reading package lists... Done E: Failed to fetch https://downloads.plex.tv/repo/deb/dists/./public/InRelease                     Unable to find expected entry 'main/binary-armhf/Packages' in Release file (Wron                   g sources.list entry or malformed file) E: Some index files failed to download. They have been ignored, or old ones used                    instead.


  Making a DVD Server (including burning) using Rock64
Posted by: Ron Piggott - 04-10-2018, 01:25 PM - Forum: Linux on Pine A64(+) - Replies (1)

Is someone able to provide a set of steps that would result in a DVD server?  I have a USB 3.0 DVD drive I'd like to share on my home network as it's own independent server.

- I use to burn a weekly backup
- I'd like to also use it on my home network so anyone could watch videos

Ron


  Footprint for the recommended Wi-Fi+BT breakout board
Posted by: Madhuwesly - 04-09-2018, 04:28 AM - Forum: Wifi/BT Module - Replies (1)

Hello,

Can anyone ping me here the package/Footprint information for the recommended Wi-Fi+BT breakout board for SoPine A64 Baseboard?


Awaiting a reply.

Thanks in advance.


  OpenAuto
Posted by: polybius - 04-08-2018, 07:15 PM - Forum: LCD and Touch Panel - No Replies

I have the Pine64 LCD touchscreen kit and was wondering if anybody would have the time to help configure it to work with OpenAuto. It looks like this would be a good use for the kit and I might finally get some use out of it. I tried to set everything up with the Armbian image but I couldn't get aasdk compiled properly because I didn't have the correct version of protobuf or something. Any help would be appreciated!


Sad Rock64 4GB poor USB3 HDD performance
Posted by: KernelPanic - 04-08-2018, 12:18 PM - Forum: Linux on Rock64 - Replies (7)

I've received my Rock64 4GB a few weeks back but I'm having some trouble getting the external hard drive to perform as it should.

I really hope anyone here has some idea's on how to get performance up to spec because I'm about to pull my hair out with this issue. The main purpose of the Rock64 was a replacement for my RasbPI3 as a NAS. Since the Rock64 has Gigabit ethernet and USB3 it seemed like a good fit but so far it's been dissapointing.  (It's rock stable though Shy )

The drive I'm a Seagate STEA4000400 USB3 (powered by wall adapter) which performs great on my Windows rig. Transferring files from the same server as I'm using to test with the Rock64 gives me a stable 110MB/s up/down.

I'm currently running bionic-minimal-rock64-0.6.31-209-arm64, but I've also tried xenial-minimal-rock64-0.5.15-136-arm64 (the current stable release) and but had similar results.

Right now I'm only get around 20MB/s write and about 40MB/s read on the drive when using RSYNC or SAMBA, which seems way too low.

I've tried Rsync (SSH), then after reading SSH might be the culprit for poor speed changed to NFS, then when this didn't help I tried the Rsync protocol (no notable change in performance).  Then said screw it and tried transferring files via samba, same crap performance. I just tried to do a local rysnc moving files around on the drive, around 18MB/s.

At first the drive was formatted as EXT4, I've formatted it to NTFS now and still get the same performance. (I didn't expect any improvement, but this gave me the change to test the drive on my windows machine, which doesn't have the problem).

Here's some more debugging I've tried to do to narrow down the cause.. (all done with governor @ performance on 4.4.120-rockchip-ayufan-209)

Iperf with Rock64 as client: 

Code:
sudo iperf3 -c 192.168.2.10 \Connecting to host 192.168.2.10, port 5201 [  4] local 192.168.2.101 port 52794 connected to 192.168.2.10 port 5201 [ ID] Interval           Transfer     Bandwidth       Retr  Cwnd [  4]   0.00-1.00   sec  96.3 MBytes   805 Mbits/sec    0    946 KBytes [  4]   1.00-2.00   sec   100 MBytes   839 Mbits/sec    0   1.04 MBytes [  4]   2.00-3.00   sec   100 MBytes   839 Mbits/sec    0   1.25 MBytes [  4]   3.00-4.00   sec   100 MBytes   839 Mbits/sec    0   1.25 MBytes [  4]   4.00-5.00   sec   100 MBytes   840 Mbits/sec    0   1.90 MBytes [  4]   5.00-6.01   sec   101 MBytes   845 Mbits/sec    0   1.90 MBytes [  4]   6.01-7.00   sec   100 MBytes   840 Mbits/sec    0   1.90 MBytes [  4]   7.00-8.00   sec   100 MBytes   842 Mbits/sec    0   1.90 MBytes [  4]   8.00-9.01   sec   101 MBytes   845 Mbits/sec    0   1.93 MBytes [  4]   9.01-10.00  sec   100 MBytes   840 Mbits/sec    0   1.93 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval           Transfer     Bandwidth       Retr [  4]   0.00-10.00  sec   999 MBytes   838 Mbits/sec    0             sender [  4]   0.00-10.00  sec   995 MBytes   834 Mbits/sec                  receiver

Rock64 as server:
Code:
sudo iperf3 -s ----------------------------------------------------------- Server listening on 5201 ----------------------------------------------------------- Accepted connection from 192.168.2.10, port 48590 [  5] local 192.168.2.101 port 5201 connected to 192.168.2.10 port 48592 [ ID] Interval           Transfer     Bandwidth [  5]   0.00-1.00   sec   108 MBytes   907 Mbits/sec [  5]   1.00-2.00   sec   112 MBytes   941 Mbits/sec [  5]   2.00-3.00   sec   112 MBytes   940 Mbits/sec [  5]   3.00-4.00   sec   112 MBytes   940 Mbits/sec [  5]   4.00-5.00   sec   112 MBytes   941 Mbits/sec [  5]   5.00-6.00   sec   112 MBytes   941 Mbits/sec [  5]   6.00-7.00   sec   112 MBytes   941 Mbits/sec [  5]   7.00-8.00   sec   112 MBytes   941 Mbits/sec [  5]   8.00-9.00   sec   111 MBytes   933 Mbits/sec [  5]   9.00-10.00  sec   112 MBytes   941 Mbits/sec [  5]  10.00-10.03  sec  3.43 MBytes   929 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval           Transfer     Bandwidth [  5]   0.00-10.03  sec  0.00 Bytes  0.00 bits/sec                  sender [  5]   0.00-10.03  sec  1.09 GBytes   937 Mbits/sec                  receiver

As client is a bit slower, but acceptable (if anyone knows why I'd gladly hear it, firewall is disabled)

iozone test:
Code:
iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2        Iozone: Performance Test of File I/O                Version $Revision: 3.429 $                Compiled for 64 bit mode.                Build: linux        Contributors:William Norcott, Don Capps, Isom Crawford, Kirby Collins                     Al Slater, Scott Rhine, Mike Wisner, Ken Goss                     Steve Landherr, Brad Smith, Mark Kelly, Dr. Alain CYR,                     Randy Dunlap, Mark Montague, Dan Million, Gavin Brebner,                     Jean-Marc Zucconi, Jeff Blomberg, Benny Halevy, Dave Boone,                     Erik Habbinga, Kris Strecker, Walter Wong, Joshua Root,                     Fabrice Bacchella, Zhenghua Xue, Qin Li, Darren Sawyer,                     Vangel Bojaxhi, Ben England, Vikentsi Lapa.        Run began: Sun Apr  8 19:54:02 2018        Include fsync in write timing        O_DIRECT feature enabled        Auto Mode        File size set to 102400 kB        Record Size 4 kB        Record Size 16 kB        Record Size 512 kB        Record Size 1024 kB        Record Size 16384 kB        Command line used: iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2        Output is in kBytes/sec        Time Resolution = 0.000001 seconds.        Processor cache size set to 1024 kBytes.        Processor cache line size set to 32 bytes.        File stride size set to 17 * record size.                                                              random    random     bkwd    record    stride              kB  reclen    write  rewrite    read    reread    read     write     read   rewrite      read   fwrite frewrite    fread  freread          102400       4    22657    26762    91373    92627    90584    31170          102400      16    53854    65291   261840   273802   270460    65326          102400     512    88260    91791   308807   324209   361771    94020          102400    1024    85033    92685   356563   368805   368856    92340          102400   16384    91176    96230   350895   369697   370204    97167
Not sure if these are good results

Test with DD: Sad
Code:
/mnt/sg1/test$ dd if=/dev/zero of=./largefile bs=1M count=1024 1024+0 records in 1024+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 29.5178 s, 36.4 MB/s

Cleared cache with
Code:
sudo sh -c "sync && echo 3 > /proc/sys/vm/drop_caches"

Then tested read, seems fine:
Code:
/mnt/sg1/test$ dd if=./largefile of=/dev/null bs=4k 262144+0 records in 262144+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 6.97084 s, 154 MB/s

This is how the drive is mounted in fstab: (ext4 I had some bad perf)
Code:
/dev/disk/by-id/ata-ST4000DM004-2CV104_ZFN0B7VM-part1  /mnt/sg1     ntfs-3g rw, big_writes, defaults,nofail 0 0

Hope someone one of the smart people on here can help me figure this one out.
Thanks in advance!