Welcome, Guest |
You have to register before you can post on our site.
|
Forum Statistics |
» Members: 29,451
» Latest member: librem.d.s
» Forum threads: 16,190
» Forum posts: 116,847
Full Statistics
|
Latest Threads |
Upgrading Armbian from v2...
Forum: Linux on Pinebook Pro
Last Post: Sb2024
Today, 06:53 AM
» Replies: 1
» Views: 686
|
PulseAudio dropouts after...
Forum: Linux on Pinebook Pro
Last Post: P. Siera
Today, 03:03 AM
» Replies: 3
» Views: 158
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: P. Siera
Today, 03:02 AM
» Replies: 6
» Views: 301
|
Hello from Ukraine
Forum: P64-LTS / SOPINE Projects, Ideas and Tutorials
Last Post: Dendrocalamus64
Yesterday, 07:13 PM
» Replies: 1
» Views: 41
|
Simple Outdoor Weather St...
Forum: General Discussion on PineTab
Last Post: aria22
Yesterday, 12:47 PM
» Replies: 0
» Views: 44
|
Armbian fix, current vers...
Forum: Linux on Pinebook Pro
Last Post: Sb2024
Yesterday, 08:49 AM
» Replies: 0
» Views: 45
|
Experimental Mobian kerne...
Forum: PinePhone Pro Software
Last Post: teekay
Yesterday, 05:39 AM
» Replies: 2
» Views: 140
|
Pinephone Pro not in stor...
Forum: General Discussion on PinePhone
Last Post: P. Siera
Yesterday, 02:12 AM
» Replies: 1
» Views: 200
|
Libre Office on Pinetab2?
Forum: General Discussion on PineTab
Last Post: Kevin Kofler
08-07-2025, 09:50 PM
» Replies: 1
» Views: 75
|
Won't boot with a MicroSD...
Forum: General Discussion on PineTab
Last Post: acruhl
08-07-2025, 06:59 PM
» Replies: 0
» Views: 35
|
|
|
PP keyboard not working at all |
Posted by: jojuma - 07-23-2022, 07:53 AM - Forum: Mobian on PinePhone
- Replies (3)
|
 |
Today my PP keyboard arrived, but doesn't work.
Since it's charging my PP, i suppose, the connection of the pins is fine.
Now I read in the instructions post, I need the KB151 driver. But before I reinstall the whole system, this results in the following questions:
1. How can I check, if this driver is present?
2. If it isn't, can I install it or do I have to reinstall the whole OS?
3. If I do have to reinstall the whole OS, how do I know if the kernel does include this driver (I read, that in stable, the driver is not present)?
Thanks for helping me
|
|
|
Call recording? |
Posted by: Greendrake - 07-23-2022, 07:51 AM - Forum: PinePhone Pro Software
- Replies (3)
|
 |
First of all, let us please not be sidetracked by the question of legality of call recording. There are places in the world where recording calls is perfectly legal without telling anyone (as long as you are a party to the call), so let's just assume the feature is to be used by people from/in those places only. I am one of them.
So, is there any software that can be run on PPP to record phone calls at all?
|
|
|
How to (try to) suspend and how to tell if it was suspended? |
Posted by: Greendrake - 07-22-2022, 10:05 PM - Forum: General Discussion of PinePhone Pro
- Replies (7)
|
 |
There are quite a few threads around about the ability to use the battery-saving "suspend" feature — whether it works, what distros, what bootloaders, whether eMMC or SD etc.
I am currently playing with different distros/configurations and would like to know/undestand how to actually try to suspend before I can even see if it works. A number of questions here:
- Where is the "Suspend" button in various GUIs (Phosh, Plasma etc.)?
- Is it the same as screen lock?
- When the phone has its screen dark/seemingly off, how to tell if it is actually suspended?
- Is "suspend" the same feature as "sleep" and "standby", or are there nuances/differences?
- How to try to suspend from command line? `systemctl suspend`?
- Given that suspend is fully supported/enabled, when is the phone supposed to suspend automatically?
- What about hibernation?
Thanks in advance .
|
|
|
Install Void Linux with near-full-disk encryption |
Posted by: dumetrulo - 07-22-2022, 04:53 AM - Forum: Linux on Pinebook Pro
- Replies (3)
|
 |
EDIT: in /etc/default/extlinux.conf, changed CMDLINE to have quiet before loglevel
Hi folks! I managed to install Void Linux on my Pinebook Pro with working near-full-disk encryption. This means that everything is encrypted except /boot because extlinux doesn't know how to open a crypt volume to load the kernel from there.
It is possible to install GRUB, and have complete encryption of everything except the GRUB loader—I once had this setup with Manjaro—but I found it a bit flakey in that approximately one out of ten boots, it would not find the crypt volume, and I had to reboot. Also, decrypting the key takes GRUB about 4 minutes because the CPU frequency is set to minimum before boot. Therefore I chose to use an unencrypted /boot, and have the password prompted by the initramfs, which will open the crypt volume in reasonable time, and (so far) works every time.
I want to thank Rudis Muiznieks for figuring most of this out already; his guide can be found at https://rdsm.ca/3lwh2, and was my main source of inspiration.
Let's begin…
What do you need?
- A Pinebook Pro
- A free eMMC, SD card, or USB drive to perform the installation on
- A second SD card or USB drive with at least 4GB
- A second system (could be the same Pinebook Pro running another system, or a different PC/laptop) to prepare the second SD card
- An hour or so to follow this guide; further configuration will take more time
Prepare the Pinebook Pro
If you haven't installed it already, download and install Tow-Boot (https://github.com/Tow-Boot/Tow-Boot/releases) as it will make booting much easier (no more need to have U-Boot on every medium). You can do without but then you'll have to remember to flash U-Boot back to eMMC after deleting everything on it but before rebooting the first time. The steps are in the guide below, just in case.
Prepare the second SD card or USB drive
Download Cameron Nemo's unofficial Void Linux image (https://repo.nohom.org/void/images/void-...530.img.xz), and flash it to the SD card or USB drive. Assuming you are using an SD card, and download on the Pinebook Pro using a system that runs a Manjaro kernel, this can be done like this:
Code: wget https://repo.nohom.org/void/images/void-pinebookpro-20220530.img.xz
blkdiscard -f /dev/mmcblk1
xzcat void-pinebookpro-20220530.img.xz|sudo dd of=/dev/mmcblk1 obs=4M status=progress;sync
Please double-check you have the correct device name; also, if you use a USB drive instead of an SD card, blkdiscard will probably not work; don't worry about it.
As the image comes tightly packed, you will have to extend the root partition, and its file system. To resize the partition, you have to delete and recreate it:
- Run sudo fdisk /dev/mmcblk1
- Press p and Enter to display the partitions; take note of the starting sector of partition 2, just in case
- Press d and Enter to delete partition 2
- Press n and three times Enter to create a new partition 2 which starts at the same sector as before, and uses the whole available space (please double-check the suggested values before pressing Enter; if it does not give you the same starting sector, enter it manually instead of just pressing Enter)
- Press n and Enter when fdisk asks whether to erase the file system signature
- Press p and Enter to display the partitions again; double-check that everything looks good
- Press w and Enter to write the partition table, and exit fdisk
Now the file system can be resized wth the following command:
Code: sudo resize2fs /dev/mmcblk1p2
Mount the file system, and copy the image onto it:
Code: sudo mount -o rw,noatime /dev/mmcblk1p2 /mnt
sudo cp void-pinebookpro-20220530.img.xz /mnt/root
sudo umount /mnt
Now you are ready to boot from this SD card or USB drive.
Boot the Pinebook Pro from the just prepared SD card or USB drive
For the purpose of preparing ths guide, I used a small (8GB) SD card for this step, a USB card reader to plug it in for booting, and a bigger (64GB) SD card to install the final system on. If you are installing to eMMC, the steps will be the same but instead of performing them on /dev/mmcblk1 (the SD card in the PBP's internal reader), you wiill perform them on /dev/mmcblk2 (the PBP's eMMC). As always, please verify you are using the correct device name, and make sure you substitute as necessary in the below steps.
Boot from the newly prepared medium (in my case, from USB via a USB card reader), and log in as root with password voidlinux. If you have the ISO keyboard, and using a US layout by default bothers you, perform the following line of code, and reboot:
Code: echo 'KEYMAP="uk"' >>/etc/rc.conf
Set up WiFi using the commands below, substituting YourSSID and YourPwd wth your WFi credentials:
Code: cp -a /etc/wpa_supplicant/wpa_supplicant.conf /etc/wpa_supplicant/wpa_supplicant-wlan0.conf
wpa-passphrase YourSSID YourPwd >>/etc/wpa_supplicant/wpa_supplicant-wlan0.conf
for i in dhcpcd wpa_supplicant;do ln -s /etc/sv/$i /var/service/;done
Now your WiFi should work (if not, double-check that you are using the correct credentials). Update xbps and install some necessary tools:
Code: xbps-install -Syu xbps
xbps-install -y cryptsetup lvm2 nano xz
Prepare your installation target, i.e. the eMMC or SD card
If your installation will be to the eMMC, use /dev/mmcblk2. In my case, I wll use an SD card, and therefore the steps wll use /dev/mmcblk1. Please adjust as necessary:
Code: blkdscard -f /dev/mmcblk1
sfdisk /dev/mmcblk1 <<EOF
label: gpt
unit: sectors
first-lba: 64
7 : start= 64, size= 16320, type=8da63339-0007-60c0-c436-083ac8230908, name="mmc_idbloader", attrs="RequiredPartition"
8 : start= 16384, size= 8192, type=8da63339-0007-60c0-c436-083ac8230908, name="mmc_uboot", attrs="RequiredPartition"
9 : start= 24576, size= 8192, type=8da63339-0007-60c0-c436-083ac8230908, name="mmc_tfa", attrs="RequiredPartition"
1 : start= 32768, size= 753664, type=0fc63daf-8483-4772-8e79-3d69d8477de4, name="mmc_boot"
2 : start= 786432, size= 121348096, type=e6d6d379-f507-44c2-a23c-238f2a3df928, name="mmc_root"
EOF
The size of partition 2 is calculated to fit on the 64GB eMMC (it also fits on the SD card I was using). If your target medium has a different size, recalculate the size (I am using a number that divides by 8192 so that the end of the partition is on a 4MB boundary, but that's just me). Partitions 7, 8, and 9 are not strictly necessary but they provide some protection against accidentally deleting the boot loader.
Copy U-Boot from the boot medium to the target (please make sure you use the correct device names). This is not needed if you use Tow-Boot but absolutely don't forget this step if you are not using any U-Boot in SPI!
Code: dd if=/dev/sda of=/dev/mmcblk1 bs=512 count=32704 skip=64 seek=64;sync
Create LUKS container, LVM partitions therein, and file systems as appropriate
Code: dd if=/dev/random of=/dev/disk/by-partlabel/mmc_root bs=4M status=progress;sync
cryptsetup luksFormat -q --align-payload 8192 /dev/disk/by-partlabel/mmc_root
cryptsetup open /dev/disk/by-partlabel/mmc_root pbp0
pvcreate --dataalignment=4096k /dev/mapper/pbp0
vgcreate vgvoid /dev/mapper/pbp0
lvcreate -n swap -L 4G vgvoid
lvcreate -n root -l '100%FREE' vgvoid
mkswap -L void_swap /dev/vgvoid/swap
mkfs.btrfs -K -L void_root /dev/vgvoid/root
mkfs.ext4 -E stride=1024,stripe_width=1024 -L void_boot /dev/disk/by-partlabel/mmc_boot
mount -o rw,noatime,commit=120,compress-force=zstd,space_cache=v2 /dev/vgvoid/root /mnt
for i in '' .toplevel boot home opt snap tmp var var.tmp;do btrfs subv create /mnt/@$i;done
for i in .snapshots home opt tmp var;do mkdir /mnt/@/$i;done
mkdir /mnt/@var/tmp
chmod 1777 /mnt/@/tmp /mnt/@var/tmp /mnt/@tmp /mnt/@var.tmp
umount /mnt
Mount the install target properly
Code: mount -o rw,noatime,commit=120,compress-force=zstd,space_cache=v2,subvol=@ /dev/vgvoid/root /mnt
mount -o rw,noatime,commit=120,compress-force=zstd,space_cache=v2,subvol=/ /dev/vgvoid/root /mnt/.toplevel
mount -o rw,noatime,commit=120,compress-force=zstd,space_cache=v2,subvol=@snap /dev/vgvoid/root /mnt/.snapshots
mount -o rw,noatime,commit=120,compress-force=zstd,space_cache=v2,subvol=@home /dev/vgvoid/root /mnt/home
mount -o rw,noatime,commit=120,compress-force=zstd,space_cache=v2,subvol=@opt /dev/vgvoid/root /mnt/opt
mount -o rw,noatime,commit=120,compress-force=zstd,space_cache=v2,subvol=@tmp /dev/vgvoid/root /mnt/tmp
mount -o rw,noatime,commit=120,compress-force=zstd,space_cache=v2,subvol=@var /dev/vgvoid/root /mnt/var
mount -o rw,noatime,commit=120,compress-force=zstd,space_cache=v2,subvol=@var.tmp /dev/vgvoid/root /mnt/var/tmp
mount -o rw,noatime,commit=120 /dev/disk/by-partlabel/mmc_boot /mnt/boot
Mount the source image
Code: unxz void-pinebookpro-20220530.img.xz
losetup -v -P /dev/loop9 /root/void-pinebookpro-20220530.img
mkdir /tmp/img
mount -r /dev/loop9p2 /tmp/img
mount -r /dev/loop9p1 /tmp/img/boot
Copy source to target
Code: tar --posix --numeric-owner --xattrs --acls -cpSC /tmp/img .|\
tar --posix --numeric-owner --xattrs --acls -xpSC /mnt;sync
Clean up, and chroot into the new installation
Code: cp -a /etc/wpa_supplicant/wpa_supplicant-wlan0.conf /mnt/etc/wpa_supplicant/
cp /etc/resolv.conf /mnt/etc/
for i in dev proc run sys tmp;do
mount --rbind /$i /mnt/$i
mount --make-rslave /mnt/$i
done
PS1='[chroot]# ' chroot /mnt
Update xbps, and install a few things
Code: xbps-install -Syu xbps
xbps-install -y cryptsetup lvm2 nano socklog-void unzip zip xz zsh wget pv neofetch inxi
# Set keymap and RTC if needed:
nano /etc/rc.conf
echo YourHostName >/etc/hostname
# Link the correct timezone
ln -s /usr/share/zoneinfo/Europe/Amsterdam /etc/localtime
# Uncomment the locales you want
nano /etc/default/libc-locales
xbps-reconfigure -f glibc-locales
# Set root password
passwd
# Edit fstab
nano /etc/fstab
Your /etc/fstab should look as follows:
Code: #
# See fstab(5).
#
# <file system> <dir> <type> <options> <dump> <pass>
LABEL=void_swap none swap sw,noatime 0 0
LABEL=void_root / btrfs rw,noatime,commit=120,compress-force=zstd,space_cache=v2,subvol=@ 0 1
LABEL=void_root /.toplevel btrfs rw,noatime,commit=120,compress-force=zstd,space_cache=v2,subvol=/ 0 1
LABEL=void_root /.snapshots btrfs rw,noatime,commit=120,compress-force=zstd,space_cache=v2,subvol=@snap 0 1
LABEL=void_root /home btrfs rw,noatime,commit=120,compress-force=zstd,space_cache=v2,subvol=@home 0 1
LABEL=void_root /opt btrfs rw,noatime,commit=120,compress-force=zstd,space_cache=v2,subvol=@opt 0 1
LABEL=void_root /tmp btrfs rw,noatime,commit=120,compress-force=zstd,space_cache=v2,subvol=@tmp 0 1
LABEL=void_root /var btrfs rw,noatime,commit=120,compress-force=zstd,space_cache=v2,subvol=@var 0 1
LABEL=void_root /var/tmp btrfs rw,noatime,commit=120,compress-force=zstd,space_cache=v2,subvol=@var.tmp 0 1
LABEL=void_boot /boot ext4 rw,noatime,nodev,nosuid,errors=remount-ro 0 2
tmpfs /tmp tmpfs rw,noatime,nodev,nosuid,size=75% 0 0
Configure extlinux and rebuild initramfs so the system can boot
Code: # Edit /etc/default/extlinux, and make sure the CMDLINE looks as follows:
# CMDLINE="panic=10 coherent_pool=1M console=ttyS2,1500000 console=tty0 quiet loglevel=3 ro rootwait root=LABEL=void_root rd.auto=1 cryptdevice=PARTLABEL=mmc_root:pbp0"
nano /etc/default/extlinux
echo 'hostonly="yes"' >/etc/dracut.conf.d/hostonly.conf
cat >/etc/kernel.d/post-install/99-zzzz-backup-boot <<EOF
PKGNAME="$1"
VERSION="$2"
usr/bin/tar --posix --numeric-owner --xattrs --acls -cpSC /boot .|usr/bin/bzip2 -9 >/boot-${VERSION}.tbz
exit 0
EOF
xbps-reconfigure -f pinebookpro-kernel
Finish up with the following commands
Code: exit
umount -R /mnt
halt
Remove all unnecessary media, and boot from the just installed system
If you are prompted for the encryption password, you have successfully installed Void Linux! Let's log in as root using the password you set earlier, and run a few commands to finsh up the minimal configuration:
Code: for i in socklog-unix nanoklogd wpa-supplicant dhcpcd;do ln -s /etc/sv/$i /var/service/;done
xbps-install -Syu
Because the above created script for backing up /boot is a crude hack, best to reboot now, and run the following commands:
Code: vkpurge rm all
xbps-reconfigure -f pinebookpro-kernel
Now you can create snapshots of ths new, clean, and working setup:
Code: for i in '' home opt tmp var var.tmp;do btrfs subv snap -r /.toplevel/@$i /.snapshots/YYYYMMDD-justinstalled-@$i;done
Replace YYYYMMDD with the current date as appropriate. If you ever bork up your system, and need to restore from a snapshot, keep that small SD card or USB drive with the initial Void Linux image handy, as you can use it to restore the snapshots like so (check the device names):
Code: cryptsetup open /dev/disk/by-partlabel/mmc_root pbp0
vgchange -a y
mount -o rw,noatime,commit=120,compress-force=zstd,space_cache=v2,subvol=/ /dev/vgvoid/root /mnt
for i in '' home opt tmp var var.tmp;do
btrfs subv del /mnt/@$i
btrfs subv snap /mnt/@snap/YYYYMMDD-your-description-@$i /mnt/@$i
done
umount /mnt
halt
Congratulations!
This concludes your installation of Void Linux with encrypted root. It is, of course, very bare-bones, has no user account, and no GUI. But from here on, you can employ any generic guide for Void Linux regarding the further configuration.
|
|
|
Blacklisted by Pine64 after 2 years and $3,941.81 |
Posted by: User 25457 - 07-21-2022, 06:49 PM - Forum: General
- Replies (13)
|
 |
Blacklisted by Pine64 after 2 years and $3,941.81
I will do whatever I can to warn others to STAY AWAY from this company!
And they still have $417.80 of my MONEY!
This is a list of my transactions with Pine64 since November of 2020. I have spent ALMOST $4,000 ($3,941.81) with Pine64!
[Order #156163] (November 7, 2020)
PINEPHONE - "Community Edition: Manjaro with Convergence Package" Limited Edition Linux SmartPhone 1 $199.99
Total: $224.99
[Order #157330] (November 17, 2020)
PINETAB - 10.1" Linux tablet with detached backlit keyboard 1 $119.98
Total: $149.98
[Order #158006] (November 22, 2020)
PINEBOOK/PINEPHONE/PINETAB SERIAL CONSOLE 1 $6.99
PINEPHONE TEMPERED GLASS SCREEN PROTECTOR 1 $4.99
PINEPHONE SOFT TPU PROTECTIVE CASE - "REDUCE DIGITAL GAP" DONATION PROGRAM 1 $9.99
PINEPHONE HARD PROTECTIVE CASE 1 $9.99
PINEPHONE BACK COVER 1 $4.99
LITHIUM BATTERY CASING 1 $9.00
16GB eMMC Module 3 $47.85
SERIAL CONSOLE "Woodpecker" Edition 1 $1.99
ROCK64 USB 3.0 Dual Band 1200Mbps WIFI 802.11A/B/G/N/AC (RTL8812AU) Adapter 1 $21.99
Subtotal: $117.78
Total: $139.78
[Order #162191] (December 19, 2020)
PINEPHONE BATTERY CHARGER 1 $4.99
USB Adapter for eMMC Module 1 $4.99
1 METER LENGTH USB TO TYPE H BARREL POWER CABLE 1 $3.99
2 METERS LENGTH USB TO TYPE H BARREL POWER CABLE 1 $5.49
ROCKPro64 2GB Single Board Computer 1 $59.99
ROCKPro64 1x1 Dual Band WIFI 802.11AC/BLUETOOTH 5.0 MODULE 1 $14.99
ROCKPro64 PREMIUM ALUMINUM CASING 1 $14.99
ROCK64-1GB Single Board Computer 1 $24.95
PINE64 ABS ENCLOSURE 1 $7.99
PineCube Single Cube Computer Dev Kit 1 $29.99
Subtotal: $172.36
Total: $194.36
[Order #166120] (January 9, 2021)
Free Pinenut - 01S Module Promotion, limit one per order 1 $0.00
Pinenut - Model:01S Wifi/BLE5 Module 1 $1.99
CLUSTERBOARD with 7 SOPine compute module slots 1 $99.99
SOPINE A64 COMPUTE MODULE 2 $58.00
PINECIL – Smart Mini Portable Soldering Iron 1 $24.99
PINECIL Portable Mini Stand 1 $1.99
PINECIL Soldering Tip Set (Fine) 1 $24.99
PINECIL Replacement Shell - Red Color 1 $5.99
PINECIL Replacement Shell - Black Color 1 $5.99
PINECIL Break Out Board 1 $3.99
Pinenut - Model:12S Wifi/BLE5 Stamp 1 $1.99
Subtotal: $229.91
Total: $251.91
[Order #168666] (January 22, 2021)
PinePower - 120W Desktop Power Supply - EU version 1 $34.99
PineTime SmartWatch Dev Kit 1 $24.99
PineTime Pogopin Jig 1 $5.99
64GB eMMC Module 1 $34.95
USB TYPE-C TO USB TYPE-C POWER CHARGING CABLE - 1.5 meter length 1 $3.49
USB TYPE-C TO USB TYPE-C POWER CHARGING CABLE - 1 meter length 1 $2.99
CLUSTERBOARD US POWER SUPPLY 1 $15.99
PinePower - 65W GaN 2C1A Charger with international plugs 1 $24.99
ROCKPro64 2GB Single Board Computer 1 $59.99
ROCKPro64 PCI-e X4 to M.2/NGFF NVMe SSD Interface Card 1 $5.99
ROCKPro64 30mm Tall Profile Heatsink 1 $3.79
Subtotal: $218.15
Total: $240.15
[Order #173086] (March 9, 2021)
PinePower - 120W Desktop Power Supply - US version 1 $34.99
PINECIL – Smart Mini Portable Soldering Iron 1 $24.99
SOPINE "MODEL A" BASEBOARD 1 $14.99
Subtotal: $74.97
Total: $96.97
[Order #177817] (March 30, 2021)
14″ PINEBOOK Pro LINUX LAPTOP (ANSI, US Keyboard) 1 $219.99
Total: $252.99
[Order #189524] (June 8, 2021)
SOEDGE AI NEURAL MODULE 10 $349.90
ROCKPro64 2GB Single Board Computer 1 $59.99
PINE A64 STEREO AUDIO DAC POT BOARD 1 $14.99
ROCKPro64 1x1 Dual Band WIFI 802.11AC/BLUETOOTH 5.0 MODULE 2 $29.98
PINE A64 WIFI 802.11BGN/BLUETOOTH 4.0 MODULE 2 $19.98
ROCK64 PREMIUM ALUMINUM CASING 1 $12.99
ROCK64-2GB Single Board Computer 1 $34.95
SOEDGE "MODEL A" BASEBOARD 1 $19.99
32GB eMMC Module 2 $49.90
Subtotal: $592.67
Total: $614.67
[Order #189525] (June 8, 2021)
PINEPHONE – Beta Edition Linux SmartPhone 1 $149.99
Total: $174.99
[Order #190544] (June 16, 2021)
SOEDGE AI NEURAL MODULE 6 $209.94
SOPINE A64 COMPUTE MODULE 2 $65.98
PINE A64-LTS Single Board Computer 1 $32.00
ROCKPro64 20mm Mid Profile Heatsink 1 $3.29
PINE A64 USB SERIAL CONSOLE/PROGRAMMER 2 $19.98
1 METER LENGTH USB TO TYPE H BARREL POWER CABLE 4 $15.96
5V 2.4A POE SPLITTER with 3.5mm OD/1.35mm ID Barrel DC jack 3 $29.97
QUARTZ64 Model-A 4GB Single Board Computer 1 $59.99
RTC BACKUP BATTERY HOLDER - CR-2032 4 $15.96
PINEBOOK Pro M.2/NGFF NVMe SSD Interface Adapter 1 $6.99
PINE A64+ 1GB Single Board Computer 1 $21.00
PINE A64 5 MEGAPIXEL CAMERA MODULE 1 $12.99
ROCK64 / PINE A64 / PINE H64 Heatsink 16 $8.00
5V 2.4A POE SPLITTER with microUSB connector 2 $19.98
Subtotal: $522.03
Total: $544.03
[Order #190916] (June 20, 2021)
PinePower - 65W GaN 2C1A Charger with international plugs 1 $24.99
PinePower - 120W Desktop Power Supply - US version 1 $35.99
PINECIL Preheater Hammerhead Tip 1 $24.99
PINEPHONE FLEX BREAK-OUT BOARD 2 $2.00
PINEPHONE 3GB/32GB MAINBOARD 1 $104.95
PINEBOOK Pro USB-C Docking Deck 1 $49.99
1 METER LENGTH USB TO TYPE H BARREL POWER CABLE 3 $11.97
QUARTZ64 Model-A 8GB Single Board Computer 1 $79.99
PINE A64 USB SERIAL CONSOLE/PROGRAMMER 1 $9.99
PUSH BUTTON - ON / OFF SWITCH 10 $5.00
ROCK64 PREMIUM AV and RCA (COMPOSITE VIDEO AUDIO) CABLE 1 $2.99
LITHIUM BATTERY CASING 1 $9.00
ROCKPro64 13 MEGAPIXEL CAMERA MODULE - m12 Mount Lens model 1 $21.99
PINE A64 5 MEGAPIXEL CAMERA MODULE 2 $25.98
PineCube Single Cube Computer Dev Kit 1 $29.99
Subtotal: $439.81
Total: $451.80
[Order #193485] (July 14, 2021)
PINECIL – Smart Mini Portable Soldering Iron 1 $24.99
PinePower - 65W GaN 2C1A Charger with international plugs 1 $24.99
Pinenut - Model:01S Wifi/BLE5 Module 10 $19.90
USB JTAG Adapter 1 $9.99
PINECIL Replacement Tip Contacts 4 $4.00
USB TYPE-C TO USB TYPE-C SILICONE POWER CHARGING CABLE - 1.5 meter length 1 $3.99
Pinenut - 01S USB Programmer 1 $1.99
PineTime SmartWatch (sealed) 1 $26.99
ROCKPro64 10mm Low Profile Heatsink with Fan 1 $5.29
ROCK64 / PINE A64 / PINE H64 Heatsink 10 $5.00
RTC BACKUP BATTERY HOLDER - CR-2032 4 $15.96
SERIAL CONSOLE "Woodpecker" Edition 1 $1.99
5V 2.4A POE SPLITTER with microUSB connector 2 $19.98
Subtotal: $165.06
Total: $187.06
[Order #243758] (June 27, 2022)
SERIAL CONSOLE "Woodpecker" Edition 10 $19.90
PineDio USB LoRa Adapter 3 $44.97
PINEBOOK(Pro) / PINEPHONE / PINETAB SERIAL CONSOLE 1 $6.99
USB TYPE A MALE TO TYPE A MALE CABLE (1 METER) 2 $5.98
PINEPHONE & PINEPHONE PRO PINEDIO LORA ADD-ON CASE 1 $19.99
PINEPHONE & PINEPHONE PRO KEYBOARD 1 $49.99
Subtotal: $147.82
Total: $159.81
[Order #245081] (July 8, 2022)
14″ PINEBOOK Pro LINUX LAPTOP (ANSI, US Keyboard) [Schedule to ship in late July/early August] 1 $219.99
Total: $257.99
Total of all orders: $3,941.81
|
|
|
Curious About Arch |
Posted by: Ferriah - 07-21-2022, 03:33 PM - Forum: Arch Linux on PinePhone
- Replies (2)
|
 |
Hey all,
Lately I've been curious abour Arch on the pinephone, and have some questions about it!
1) how stable is it? Is it could for daily drivin?
2) What are some of the current issues that users are facin with it?
3) What apps can you install on it? Can you use Chatty?
4) Can you use Lomiri with it? I've always liked that de, but don't really like ubuntu touch itself
5) Is Arch easy to install?
Thanks!
Edit: Typo
|
|
|
Improper Storage After Flashing Mobian |
Posted by: Ferriah - 07-21-2022, 03:19 PM - Forum: Mobian on PinePhone
- Replies (1)
|
 |
Hey all,
Recently I decided to do a fresh install of Mobian, and have discovered that we are now usin tow boot. I was able to install that just fine, but whenever I try to flash an image to internal storage with balena etcher I end up with only 5 gigs of space dedicated to it...? Not sure what I'm doin wrong.
After holding the power and volume button and mounting it, it comes up as Linux UMS_disk_0 (boot, rootfs) in balena etcher. I've never seen any other listin. Am I missin somethin?
Any help would greatly be appreciated!
Edit: After flashin I opened up gnome disks on my pc and just increased storage myself. Seems to be workin fine so far!
|
|
|
Pinebook Pro shows only bright white screen when powered on |
Posted by: Sean Whitton - 07-21-2022, 02:17 PM - Forum: General Discussion on Pinebook Pro
- Replies (3)
|
 |
Hello,
I received my Pinebook Pro in Spring 2021. I last used it about one month ago, and left it disconnected. So, the battery has completely drained.
I've been charging it using the barrel charger for more than twelve hours. When I turn it on, the green power light comes on, and the screen comes up bright white. After ten seconds or so, the backlight dims a bit so it's a softer white. At that point, I can do things like toggle num lock on my external keyboard.
I don't think it is an OS issue, because it booted completely fine a month ago and I haven't touched it. But just in case, I am using hand-debootstrapped Debian "bullseye" with a custom kernel build using Manjaro's patches as of a year ago, and stock Debian u-boot.
Any ideas about what these symptoms could indicate? Really hope it is not bricked! I don't have UART, but I could get one if it's not just that the screen is completely dead.
Thanks.
|
|
|
Phone carriers and the Speakout carrier |
Posted by: bedtime - 07-21-2022, 01:28 PM - Forum: General Discussion on PinePhone
- Replies (3)
|
 |
Currently, I'm on the Speakout phone plan. I'm using my 10-12 year old Samsung phone, and it works fine, but I've wanted a tinker phone with pure Linux for several years.
I'm interested in going down the rabbit hole to try my SIM card on a Pine Phone Beta Edition. I'd like to know if anyone has used the Speakout carrier on the Pine Phone and what experience they've had with it.
Are all carriers generally the same in terms of call reliability?
|
|
|
|