| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
04-06-2026, 08:44 AM
» Replies: 0
» Views: 159
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
04-05-2026, 03:03 AM
» Replies: 19
» Views: 8,698
|
Finally got Kali working ...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
04-04-2026, 08:00 AM
» Replies: 0
» Views: 249
|
Charging problem
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
04-04-2026, 07:30 AM
» Replies: 0
» Views: 116
|
Latest firmware for PineP...
Forum: PinePhone Software
Last Post: baptx
04-03-2026, 08:37 AM
» Replies: 106
» Views: 216,951
|
Updates have gotten me ex...
Forum: General Discussion on PineNote
Last Post: bills2002
04-02-2026, 05:16 PM
» Replies: 0
» Views: 207
|
Voidlinux working on eMMC
Forum: General Discussion on PineTab
Last Post: tllim
04-01-2026, 04:14 PM
» Replies: 1
» Views: 291
|
Pinecil V2 doesn’t power ...
Forum: General Discussion on Pinecil
Last Post: Juptin
03-28-2026, 02:37 AM
» Replies: 1
» Views: 2,083
|
dead Pinebook - help plea...
Forum: General Discussion on Pinebook Pro
Last Post: williamcorlin
03-26-2026, 04:22 PM
» Replies: 3
» Views: 939
|
BT PAN - we need iptables...
Forum: Mobian on PinePhone
Last Post: biketool
03-25-2026, 12:57 PM
» Replies: 1
» Views: 603
|
|
|
| openarena build script |
|
Posted by: xmixahlx - 01-28-2020, 03:11 PM - Forum: Pinebook Pro Tutorials
- Replies (4)
|
 |
greetings,
here is a simple build script for openarena that can be used on debian based systems. tested on debian sid arm64. i recommend using mesa-git for the latest panfrost graphics. see that other thread for details.
you can also append openarena commands to the run script, or use to make your own launch script. i've included my own below.
happy fragging.
Code: #! /bin/sh
## BUILD OPENAREA
PREFIX=/usr/local
DEVDIR=~/Development/UPSTREAM
ARCHDIR=release-linux-aarch64
ARENADIR=$DEVDIR/OPENARENA
DESTDIR=$PREFIX/games/openarena
BINDIR=$PREFIX/bin
## GET REQS
sudo apt-get -y install wget git make libsdl-dev libvorbis-dev libxmp-dev build-essential;
## CHANGE TO ARENADIR
mkdir -p $ARENADIR;
cd $ARENADIR;
## MAKE A SIMPLE SCRIPT
echo "#!/bin/sh" > $ARENADIR/openarena.bin
echo "cd $DESTDIR && ./openarena.aarch64" >> $ARENADIR/openarena.bin
## MAKE A SIMPLE PATCHFILE
echo "*** make simple patchfile \n\n";
echo "217a218,219" > $ARENADIR/enable_arm64.patch;
echo "> #elif defined __aarch64__" >> $ARENADIR/enable_arm64.patch;
echo "> #define ARCH_STRING \"arm64\"" >> $ARENADIR/enable_arm64.patch;
## DOWNLOAD
if [ -f $ARENADIR/openarena-0.8.8.zip ]; then
echo "Found Arena Download"
else
wget http://download.tuxfamily.org/openarena/rel/088/openarena-0.8.8.zip
fi;
## GIT
git clone --depth=1 https://github.com/OpenArena/engine;
git clone --depth=1 https://github.com/OpenArena/gamecode;
## UNPACK OPENARENA ZIP
unzip openarena-0.8.8.zip
## BUILD GAMECODE
cd $ARENADIR/gamecode;
make -j;
## PATCH ENGINE TO ENABLE ARM64 AND BUILD
cd $ARENADIR/engine;
patch code/qcommon/q_platform.h ../enable_arm64.patch;
make -j;
## INSTALL
sudo mkdir -p $DESTDIR;
sudo cp -vr $ARENADIR/openarena-0.8.8/baseoa $DESTDIR/;
sudo cp -vr $ARENADIR/gamecode/build/$ARCHDIR/* $DESTDIR/;
sudo cp -vr $ARENADIR/engine/build/$ARCHDIR/* $DESTDIR/;
sudo install -m 0755 -o root $ARENADIR/openarena.bin $BINDIR/openarena;
## FIX PERMS
sudo chown -R root.root $DESTDIR;
sudo chmod a+rx $DESTDIR/baseoa;
## EXIT
exit
my run script. (light used to save and change brightness and kill waybar, which is in the way on sway, then set lightness back to previous and relaunch waybar.)
Code: #!/bin/sh
# RUN OPENARENA
light -O;
light -S 100%;
killall waybar;
cd /usr/local/games/openarena && ./openarena.aarch64 \
+password PINE64 +connect arena.brixit.nl:22222 \
+cg_drawFPS 1 +r_vertexlight 1 +cg_autovertex 1 +r_greyscale 0 \
+r_texturebits 32;
light -I;
waybar;
exit
|
|
|
|
| mesa-git build script for latest panfrost |
|
Posted by: xmixahlx - 01-28-2020, 02:21 PM - Forum: Pinebook Pro Tutorials
- Replies (28)
|
 |
greetings,
if you are on a "recent" kernel (5.2+) you will benefit from installing mesa from git to take advantage of the VERY latest panfrost graphics driver.
below is a simple script to build and install mesa-git for debian-based setups. confirmed working on debian buster, bullseye, and sid. you may rerun the script at will to update mesa-git at any time.
folks on non-debian based systems can simply address requirements manually.
ccache is used to speed up rebuilds. feel free to remove if you don't want that.
hint: regarding rebuilding, you can review the git file changes for panfrost to determine if rebuilding is advantageous.
installing to /usr/local does not impact your distro mesa in ANY WAY. to uninstall for any reason,
enjoy your fps!
EDIT: now part of pbp-tools. see other forum thread for details.
https://github.com/xmixahlx/pbp-tools
https://forum.pine64.org/showthread.php?tid=10190
|
|
|
|
| Arguments for android support |
|
Posted by: metcalsr - 01-28-2020, 02:03 PM - Forum: Android on Pinebook Pro
- Replies (20)
|
 |
Hi guys,
I've talked personally with a few people who seem to think android support isn't really necessary for a strong Pinebook community. Even if Android support seems like the most obvious thing in the world to you, there are people who are firmly against using Android on their device. For this reason, I thought I'd try to enumerate some reasons why I think we really need to get it going.
1. Android provides easy access to Microsoft Office.
Linux users might groan at this, but the Android version of Microsoft Office is surprisingly full-featured. It provides much more than Office Online and many people, even Linux users, still have to use Office to some extent.
2. Access to games
The Pinebook will never be a gaming powerhouse, but if we can get Google Play working reliably, the Pinebook is powerful enough to play a wide variety of Android games.
3. Fills a niche
Considering the low-end specs of the Pinebook, one of the best ways to maintain healthy development for the device is to increase it's lateral utility. Being able to boot into a baremetal armv8 android install would be a strong incentive for hobbyists, developers, and mobile gamers who can't really get that experience from another laptop.
4. Access to Google proprietary video codecs
The Pinebook struggles with 1080p video streaming. There are many android devices with far inferior specs to the Pinebook that can manage it just fine on android.
I'm sure there are more, but these are some of the biggest reasons I don't want to see this area of the forum languish with only three posts.
|
|
|
|
| Sound driver 32bit sample format not working, some freezes and crashes through ALSA |
|
Posted by: aeGh7fae - 01-28-2020, 10:16 AM - Forum: General Discussion on Pinebook Pro
- No Replies
|
 |
Hello,
I got a new PinebookPro last week and did not change much except installing jackd 2.
I noticed that the sound was totally wrong, not in a distorted sense but technically wrong. After some investigation, actually some hours with ALSA devs in freenodes #alsa channel, they came to the conclusion, that there is some need for clarification and/or work to do.
Bottom line question is: Does the PinebookPro hardware support the 32bit float sample format?
If yes there is something wrong with the driver.
What follows is a curated alsa report summary with annotations from the alsa devs.
I hope this information will be useful in creating a better software revision for units shipped in the future:
Code: [color=#000000]`aplay --file-type=wav --channels=2 --format=S16_LE --rate=48000 --duration=5 --verbose --dump-hw-params --device=hw:aplay --file-type=wav --channels=2 --format=S16_LE --rate=48000 --duration=5 --verbose --dump-hw-params --device=front:es8316spksound /dev/urandom`
*sympbolic card name does not work
`aplay --file-type=wav --channels=2 --format=S16_LE --rate=48000 --duration=5 --verbose --dump-hw-params --device=front:aplay --file-type=wav --channels=2 --format=S16_LE --rate=48000 --duration=5 --verbose --dump-hw-params --device=front:0 /dev/urandom`
*no front pcm
`aplay --file-type=wav --channels=2 --format=S16_LE --rate=48000 --duration=5 --verbose --dump-hw-params --device=front:aplay --file-type=wav --channels=2 --format=S16_LE --rate=48000 --duration=5 --verbose --dump-hw-params --device=hw:0 /dev/urandom`
*system crash and reboot when accessing alsa directly with pulseaudio running
`pasuspender -- aplay --file-type=wav --channels=2 --format=S16_LE --rate=48000 --duration=5 --verbose --dump-hw-params --device=front:aplay --file-type=wav --channels=2 --format=S16_LE --rate=48000 --duration=5 --verbose --dump-hw-params --device=hw:0 /dev/urandom`
*conflict between sample bits and sample format
ACCESS: MMAP_INTERLEAVED RW_INTERLEAVED
FORMAT: S16_LE S24_LE
SUBFORMAT: STD
SAMPLE_BITS: [16 32]
FRAME_BITS: [32 64]
`pasuspender -- aplay --file-type=wav --channels=2 --format=S16_LE --rate=48000 --duration=5 --verbose --dump-hw-params --device=front:aplay --file-type=wav --channels=2 --format=S32_LE --rate=48000 --duration=5 --verbose --dump-hw-params --device=hw:0,0 /dev/urandom`
Playing raw data '/dev/urandom' : Signed 32 bit Little Endian, Rate 48000 Hz, Stereo
HW Params of device "hw:0,0":
--------------------
ACCESS: MMAP_INTERLEAVED RW_INTERLEAVED
FORMAT: S16_LE S24_LE
SUBFORMAT: STD
SAMPLE_BITS: [16 32]
FRAME_BITS: [32 64]
CHANNELS: 2
RATE: [8000 96000]
PERIOD_TIME: (333 8192000]
PERIOD_SIZE: [32 65536]
PERIOD_BYTES: [256 524288]
PERIODS: [2 4096]
BUFFER_TIME: (666 16384000]
BUFFER_SIZE: [64 131072]
BUFFER_BYTES: [256 524288]
TICK_TIME: ALL
--------------------
aplay: set_params:1299: Sample format non available
Available formats:
- S16_LE
- S24_LE
`pasuspender -- aplay --file-type=wav --channels=2 --format=S16_LE --rate=48000 --duration=5 --verbose --dump-hw-params --device=front:aplay --file-type=wav --channels=2 --format=S16_LE --rate=48000 --duration=5 --verbose --dump-hw-params --mmap --device=hw:0 /dev/urandom`
(09:59:40 AM) nilshi: that crashed
*mmap makes the machine reboot sometimes and other times hang up temporarily
*summary the driver has numerous issues[/color]
|
|
|
|
| CPU clockspeed governor |
|
Posted by: Eight Bit - 01-28-2020, 03:02 AM - Forum: General Discussion on Pinebook Pro
- Replies (2)
|
 |
Hi,
I have a quick question.
When I got my PBP, I had the option to set the CPU speed to 1.99 MHz but after moving the icons around and messing with the layout of my desktop I can set it to 1.55 MHz max. The 1.99 MHz option has disappeared. Also the on-demand option doesn't go higher than 1.55 MHz anymore.
How can I restore this setting so that it goes to 1.99 again?
Thanks for any answers!
|
|
|
|
| Boot delayed 30s; how to troubleshoot this? |
|
Posted by: alxndr.psclt - 01-27-2020, 03:46 PM - Forum: Linux on Pinebook Pro
- Replies (6)
|
 |
Hello! I've been using Manjaro Arm (burned on the emmc) on my PBP for a few weeks now and it's awesome; thanks a lot for all the work that goes into this. Really love this pinebook.
But I do have a problem happening on boot:
When I hold the Power button a few seconds, the LED light up; but the screen stays dark for 32s before anything starts showing (the M Manjaro logo comes first; then my login screen).
It's a shame because once the screen lights up the boot is pretty fast. Is this delay normal? I don't remember having these kind of delays on the default debian install.
The 30s value make me think it could be a timer on a misconfigured u-boot that maybe tries some invalid boot option, wait for 30s then tries Manjaro? I have no expierience with u-boot and am not very clear on how to debug this issue? Any clues would be welcome.
|
|
|
|
| Quick Guide to installing Ubuntu Unity on your Pinebook Pro |
|
Posted by: andybleaden@gmail.com - 01-27-2020, 02:46 PM - Forum: Pinebook Pro Tutorials
- Replies (19)
|
 |
Had my PBP now for a couple of months and while the default build it shipped with was fine I have been messing around with the excellent Mate build kindly done by Wizzard here
https://forum.pine64.org/showthread.php?tid=8119
............................but stopped short of installing KDE as I had used Kubuntu for a few years before and the Mate build was good. I had even installed Mutiny Theme
However I have been using Unity Ubuntu and now Ubuntu Desktop for long enough on a main pc that I wanted to install Ubuntu (classic as I call it)
After a few failures I realised that just installing ubuntu-desktop on top of the Mate build was not going to work for me
It installed but would not boot even with LightDM and GDM seemed to just break the installation. So another method was needed.
I reinstalled the Mate build and then followed the updates kindly provided by Ayufan here after of course installing the trackpad updates and uboot fixes
https://github.com/ayufan-rock64/linux-b...tag/0.9.14
Then installed ubuntu-unity-desktop with the following command:
sudo apt install ubuntu-unity-desktop --install-recommends
This installed fine and booted as well after selecting Unity (default) at login
However this gave me some small problems as none of the apps I use showed up in the Dash when pressing the Pine super button.
Secondly I could not open a terminal and lastly my right click on the trackpad no longer worked
So I had to reach out for help
Firstly after a few hours of thinking I remembered the old skills.
I hit Alt and F2....of course....then search for terminal (see attached photo)
Bingo
Same for finding all the other apps I needed and had installed on Mate build
This kindly provided by Tophneal fixed the right click issue:
https://itsfoss.com/fix-right-click-touchpad-ubuntu/
So Pinebook now up and running with Unity Ubuntu ...a few system errors but for now ....its just how I want it for now...no doubt it will come with a few issues but it looks good enough
See other attachment
Good luck and let me know if you get stuck
Also keen to see if others have had better luck with another method
|
|
|
|
|