PINE64

Welcome, Guest

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

Search Forums

Forum Statistics

» Members: 29,700
» Latest member: runongw
» Forum threads: 16,260
» Forum posts: 117,188

Full Statistics

Latest Threads

Volumio (PINE A64-LTS / S...
Forum: Linux on PINE A64-LTS / SOPINE
Last Post: kapqa
Yesterday, 02:02 AM
» Replies: 8
» Views: 15,528

Reinstallation Arch Linux...
Forum: General Discussion on PineTab
Last Post: rth
11-22-2025, 08:25 PM
» Replies: 1
» Views: 208

Old Danctnix server in Pa...
Forum: PineTab Software
Last Post: brorean
11-21-2025, 08:45 PM
» Replies: 1
» Views: 135

PinePhone, PinePhone Pro,...
Forum: PinePhone Hardware
Last Post: brb78
11-20-2025, 04:15 PM
» Replies: 0
» Views: 113

Recycling pinephone as ho...
Forum: PinePhone Hardware
Last Post: biketool
11-20-2025, 09:04 AM
» Replies: 5
» Views: 612

Light Sensor / Proximity ...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
11-18-2025, 03:07 PM
» Replies: 1
» Views: 178

How to stop it turning on
Forum: General Discussion on PinePhone
Last Post: biketool
11-18-2025, 02:30 PM
» Replies: 3
» Views: 481

8/24 status of JumpDrive
Forum: PinePhone Software
Last Post: biketool
11-18-2025, 01:27 PM
» Replies: 5
» Views: 2,176

Questions about running U...
Forum: General Discussion on PineTime
Last Post: alicesphere
11-18-2025, 12:48 AM
» Replies: 0
» Views: 107

Difficulty with openSUSE ...
Forum: PinePhone Software
Last Post: danm1988
11-17-2025, 07:49 AM
» Replies: 0
» Views: 105

Using DD to Backup and Restore EMMC

Posted by: appdev46 - 01-31-2020, 04:08 PM - Forum: Linux on Pinebook Pro - Replies (6)

I have the Intel 660p NVME (SSDPEKNW512G8X1) installed in my pinebook pro. I was attempting to backup the EMMC to the NVME drive as an .img and then restore that to the EMMC. My intent was to find a way to do a backup and a restore for testing purposes.

I used a process similar to this. Don't recall exact details...

Backup: dd if=/dev/mmcblk1 of=/NVME_Folder/emmc_Backup.img

Restore: dd if=/NVME_Folder/emmc_Backup.img of=/dev/mmcblk1

After the restore I could boot to login screen but I could not log in with my user. I CAN log in with root.

Any ideas what I missed or could be wrong with this process?

Installing Wine i386 on Pinebook Pro

Posted by: wrzomar - 01-31-2020, 03:52 PM - Forum: Pinebook Pro Tutorials - No Replies

I've mostly followed the Novaspirit's tutorial from:
https://www.novaspirit.com/2019/04/15/run-x86-arm/

First, I've built and run vmsplit checking code from wine (from https://gist.github.com/liuqi/ccf638adc675a3b00c98):

Code:
#include <sys/mman.h>

#include <stdio.h>

#include <errno.h>

static void check_vmsplit( void *stack )

{

    printf("user space is %x\n", stack);

    if (stack < (void *)0x80000000)

    {

        /* if the stack is below 0x80000000, assume we can safely try a munmap there */

        if (munmap( (void *)0x80000000, 1 ) == -1 && errno == EINVAL)

            fprintf( stderr,

                     "Warning: memory above 0x80000000 doesn't seem to be accessible.\n"

                     "Wine requires a 3G/1G user/kernel memory split to work properly.\n" );

    }

}

int main()

{

    int temp;

    check_vmsplit( &temp );

}

I assume, if above code doesn't print warning, everything is OK and I don't need to rebuild kernel.

Then we need to install prerequisites:

Quote:sudo apt update && sudo apt upgrade

sudo apt install qemu qemu-user qemu-user-static binfmt-support debootstrap binutils

After successful install, run:

Quote:sudo debootstrap --foreign --arch i386 stretch ./chroot-stretch-i386 http://ftp.us.debian.org/debian

Then prepare system to run chroot:

Quote:sudo mount -t sysfs sys ./chroot-stretch-i386/sys/
sudo mount -t proc proc ./chroot-stretch-i386/proc/
sudo mount --bind /dev ./chroot-stretch-i386/dev/
sudo mount --bind /dev/pts ./chroot-stretch-i386/dev/pts/
sudo mount --bind /dev/shm ./chroot-stretch-i386/dev/shm/

With system qemu-i386-static there may be 'illegal instruction' errors, so we'll build qemu from source. I've followed instructions from
http://logan.tw/posts/2018/02/18/build-q...urce-code/

Quote:sudo apt-get build-dep qemu
$ git clone git://git.qemu.org/qemu.git
$ cd qemu
$ git submodule update --init --recursive
$ ./configure --prefix=$(cd ..; pwd)/qemu-user-static --static --disable-system --enable-linux-user --target-list=i386-linux-user --disable-tools
make -j6
make install
cd ../qemu-user-static/bin
mv qemu-i386 qemu-i386-static
sudo mv qemu-i386-static ./chroot-stretch-i386/usr/bin

Without --disable-tools there were linker errors, --target-list=i386-linux-user will build only qemu-i386 binary.

And start second stage:

Quote:sudo chroot ./chroot-stretch-i386/ /debootstrap/debootstrap --second-stage

On my Pinebook Pro it took 28 minutes 30 seconds to finish second stage.

Next, we'll chroot as root user:

Quote:sudo chroot ~/chroot-stretch-i386/ /bin/su -l root

If your DNS isn't working inside chroot check /etc/resolv.conf and fix your name server address!

Quote:nano .bashrc

Then we need to add this:

Code:
export LANGUAGE="C"

export LC_ALL="C"

export DISPLAY=:0

to the end of .bashrc file and run:

Quote:source ~/.bashrc

so change will to effect.
Then run:

Quote:apt update

And create user account:

Quote:adduser -uid 1000 <username>

where <username> is your chosen username.
Then install leafpad or xterm to install all needed dependencies.

Quote:apt install leafpad

Then open second terminal window and enter:

Quote:sudo chroot /home/marek/chroot-stretch-i386/ /bin/su -l <username>

to chroot as your newly created user.

Quote:nano .bashrc

Add at the end:

Code:
export LANGUAGE="C"

export LC_ALL="C"

export DISPLAY=:0

and run:

Quote:source ~/.bashrc

and then run leafpad (or xterm):

Quote:leafpad

Now we are ready to install Wine.

Switch focus to your root terminal window or run:

Quote:sudo chroot ~/chroot-stretch-i386/ /bin/su -l root

To make things easier first install apt-transport-https package:

Quote:apt install apt-transport-https

It will install all dependencies for SSL certificates to work (and we might need apt-transport-https it in the future).
Download Wine from Playonlinux with:

Quote:wget -c https://www.playonlinux.com/wine/binarie...ux-x86.pol

I've chosen version 3.20, but you can choose a different version (and maybe have better luck with running Windows programs).
Then install bzip2:

Quote:apt install bzip2

and then unpack previously downloaded Wine and "install' it:

Quote:tar -jxf PlayOnLinux-wine-3.20-linux-x86.pol --strip-components=1
mv ./3.20/bin/wine-preloader ./3.20/bin/wine-preloader.renamed
mv ./3.20 /opt/wine-3.20/
cd /opt
ln -s wine-3.20 wine
cd

Symbolic link will help with switching wine versions in the future.
Then open .bashrc:

Quote:nano .bashrc

and add this:

Quote:export PATH=/opt/wine/bin:$PATH

at the end and run:

Quote:source ~/.bashrc

to refresh session then do the same line to the .bashrc file of your new i386 user account.
Run:

Quote:sudo chroot ~/chroot-stretch-i386/ /bin/su -l <username>

Then open .bashrc:

Quote:nano .bashrc

and add this:

Quote:export PATH=/opt/wine/bin:$PATH

at the end and run:

Quote:source ~/.bashrc

to refresh session.
Now you need to check, if Wine is working, run:

Quote:winecfg

The window should appear and it will download gecko and stuff, finally Wine config window should appear.

Novaspirit has prepared winetricks but I haven't tried them, yet.
https://github.com/novaspirit/winetricks

Let's finish the installation.
Outside of chroot we'll create script to mount /sys, /proc and the rest at start.

Quote:sudo mkdir -p /opt/chrootscript/
sudo nano /opt/chrootscript/chrootmount

Paste this:

Code:
#!/bin/sh

mount -t sysfs sys /opt/chroot-stretch-i386/sys/

mount -t proc proc /opt/chroot-stretch-i386/proc/

mount --bind /dev /opt/chroot-stretch-i386/dev/

mount --bind /dev/pts /opt/chroot-stretch-i386/dev/pts/

mount --bind /dev/shm /opt/chroot-stretch-i386/dev/shm/

As you can see I've moved chroot-stretch-i386 to /opt but I've forgot to umount previously mounted sys, proc and the rest, which wasn't probably a good idea Shy

Next, make above script executable:

Quote:sudo chmod a+x /opt/chrootscript/chrootmount

Then create service file:

Quote:sudo nano /etc/systemd/system/chrootmount.service

paste this:

Code:
[Unit]

Description = mounts chroot on boot

[Service]

Type=one-shot

ExecStart=/opt/chrootscript/chrootmount

[Install]

WantedBy=multi-user.target

Then enable service:

Quote:sudo systemctl enable chrootmount.service

Then we will make scripts to make chrooting easier:

Quote:sudo nano /opt/chrootscript/start_x86_user

And paste:

Code:
#!/bin/sh

/usr/sbin/chroot /opt/chroot-stretch-i386/ /bin/su -l <username>

Make it executable:

Quote:sudo chmod a+x /opt/chrootscript/start_x86_user

Repeat this process for root:

Quote:sudo nano /opt/chrootscript/start_x86_root

Code:
#!/bin/sh

/usr/sbin/chroot /opt/chroot-stretch-i386/ /bin/su -l root

Quote:sudo chmod a+x /opt/chrootscript/start_x86_root

At last create desktop shortcuts:

Quote:nano ~/Desktop/chroot_user.desktop

Code:
[Desktop Entry]

Type=Application

Comment=Start Wine x86 Environment

Name=Wine x86 User

Exec=mate-terminal -e 'sudo /opt/chrootscript/start_x86_user'

Icon=utilities-terminal

Terminal=false

Categories=Utility

StartupNotify=True

Quote:nano ~/Desktop/chroot_root.desktop

Code:
[Desktop Entry]

Type=Application

Comment=Start Wine x86 Environment

Name=Wine x86 Root

Exec=mate-terminal -e 'sudo /opt/chrootscript/start_x86_root'

Icon=gksu-root-terminal

Terminal=false

Categories=Utility

StartupNotify=True

And make them executable:

Quote:chmod a+x ~/Desktop/chroot_user.desktop
chmod a+x ~/Desktop/chroot_root.desktop

Restart Pinebook Pro. After restart check status of our mounting service:

Quote:sudo systemctl status chrootmount.service

If there are no error, you can double click on one of Wine x86 shortcuts to open terminal.

Unfortunately, I was only able to run installers but installed programs (like Notepad++ or Treesheets) crashed but I haven't used Wine for years, so maybe recent Notepad++ or Treesheets are not good starting points. Don't look at me, I didn't touch it, I swear Angel

Maybe different Wine version would do the trick.

Good luck, and good night.

EDIT: One of the problems was broken qemu-i386-static (there was qemu's 'illegal instruction' error at one of last lines of messages when putty crashed), so I've added instructions to build qemu. I've also changed icons of desktop shortcuts.
Now putty works and I was able to install Notepad++ 6.7.4, but it crashed anyway with wine client bad descriptor error.

New product announcement?

Posted by: gillham - 01-31-2020, 03:29 PM - Forum: News - Replies (3)

	Hey it is January 31st (almost February in Brussels) and I thought there was going to be a post about new products?

FOSDEM 2020 PineTime BoF

Posted by: bergzand - 01-31-2020, 09:04 AM - Forum: General Discussion on PineTime - Replies (8)

Hi all,

For those of us PineTime developers/users attending FOSDEM, maybe we could have a small meet-up during a BoF slot. With all the development ideas floating around here, it would be nice to meet up in person and sync ideas and opinions.

Please let me know if you will be at FOSDEM and if you would like to meet up and share ideas. Also let me know if you have a preference for either Sunday or Saturday.

I don't mind organizing this, but the community mods are of course welcome to take over Tongue

Pinebook pro random reboot default Debian

Posted by: tso4ev - 01-31-2020, 07:30 AM - Forum: General Discussion on Pinebook Pro - Replies (3)

	PBP random reboot default Debian So do anyone of you have the same problem it happens not so often but it happens.. I'm. wondering if its not rk3399 problem becouse I own an android tv box with the same soc and there happens too quaite often

Packaging considerations

Posted by: simp - 01-31-2020, 06:51 AM - Forum: General Discussion on PinePhone - Replies (6)

	Hi, just as a heads-up, you might want to reconsider the packaging a bit for future versions. I've received my brave-heart edition and the plastic shroud where the phone is mounted inside the box has some breakage after shipping. No qualms from me, I don't think anything else is damaged and that's what beta-runs are for, but you might want to iterate on the material for future versions.

No shipping email? March delivery now confirmed

Posted by: ozzeruk - 01-31-2020, 04:53 AM - Forum: General Discussion on PinePhone - Replies (3)

Hey guys,

Just wanted to create a new thread to confirm the information I have received about my PinePhone.

I ordered on Jan 7 2020 and received an email that day with my order number.

I have received nothing since.

In my other thread we discovered that there are other people in the same situation. Several who ordered in January, and some who ordered right back in November.

We got information that "about 80 PinePhones were left in the warehouse due to a problem with mailing labels not being printed". These were apparently all ordered after January 5 2020.

I also got an official response from a support ticket I sent to Pine:

"Please to inform you that the PinePhone ordered at January 2020, is estimate to be dispatch at around mid/end of February.

Also, we will provide the tracking number once available."

So my phone has not been shipped and won't be until mid/end of February, so arrival won't be before mid-March. No reason was given, officially they were supposed to be shipped in January and now that has slipped to the end of February with no notice.

This is disappointing to say the least as otherwise Pine have been so impressive to me.

So I can only assume that if you haven't received any update after your order confirmation email, then you won't receive your PinePhone until March now.

Don't get me wrong I'm still a huge supporter of Pine, and I really hope the PinePhone succeeds in changing hearts and minds about the possibility of a popular Linux phone in the coming years. I really do wish them all the best, though I have been burnt here somewhat.

My advice to them would be simple, be 100% transparent and clear about shipping, even when delays are present. I know in China/Hong Kong things are a little on edge right now with the virus. I also know Chinese New Year is clearly a very important time, and so work might be less of a priority. The right thing to do would have been to confirm on Jan 24th, that X amount of PinePhones still had not been shipped due to reason X or Y (they have this info clearly, or could do an easy database lookup), and would not be until late Feb. I would have been sad but I would accepted that mistakes happen. This week of no information is just frustrating, and entirely unneccessary.

I was going to order a PineBook, but now I've decided to wait until my PinePhone has arrived, trust has been lost slightly.

But anyway, I just want to confirm I'm still a big fan, and I'm not mad, just gutted that's all! I'm a software dev/tinkerer and was looking forward to being 'the first' to do something on the PinePhone. Now others will get a 2 month headstart on me.

Manjaro kde Enterprise wifi issues

Posted by: mamboman777 - 01-30-2020, 08:37 PM - Forum: General Discussion on Pinebook Pro - No Replies

I am Manjaro KDE on my Pinebook Pro and I can't for the life of me get it to connect to the Enterprise network at the school I teach at. I know it's something on the software because I am able to connect to the network when using chromium on the same machine. It looks like it hangs at "setting network address.". I have tried deleting and manually re adding the network. I have tried restarting. I have fiddled with all sorts of the network settings, but I know I have them correct because my phone and the same device connects with these settings. I have tried reinstalling wpa_supplicant. I have tried adding the network with some command line tool, but it didn't support PEAP. I've exhausted all that I know and all I can find out from Google. Any help is welcome.

Detecting throttling

Posted by: clach04 - 01-30-2020, 07:56 PM - Forum: Linux on Rock64 - Replies (1)

I want to make sure I'm not cooking my board. I'd also like to ensure its getting enough power.

With raspberry pi:

Code:
vcgencmd get_throttled

can be used to determine if throttling is happening, has happened. Along with under voltage detection (etc.)

Is there anyway to do something similar with rock64 under linux (any distribution)? Main thing I'd like to check is if throttling is happening or do I need to check temperature and use that as the indicator depending on what thresholds are set?

Is there a way at run time to determine the thresholds set in https://github.com/ayufan-rock64/linux-k...4.dts#L734 ?

Pinebook Pro not powering on / not booting (tried things listed in wiki/forum)

Posted by: kiefer - 01-30-2020, 05:46 PM - Forum: General Discussion on Pinebook Pro - Replies (16)

My new pinebook pro worked well when I first used it on Monday (except for the trackpad, but I hadn't done the firmware update yet).
I used it to connect to my desktop via remmina & enjoyed the experience.
Then I closed the lid & left it in my backpack (assuming it would go hibernate/suspend), the next morning it was off and would not turn on anymore.
I assumed the battery had drained so I connect the charger (DC wall-plug, not USB). The red LED next to the charger input lighted up.
I left it charging all afternoon and occasionally tried to turn it on. But it wouldn't even after a couple of hours.
After a couple of hours the red indicator LED stopped lighting up (someone on the irc told me later that indicates full battery - Initially I thought my battery did not charge).

So far I tried a bunch of stuff that was suggested in the forum, or the wiki, but so far nothing has made the device turn on or show any indications of life (leds, screen) when pressing power:

1. remove battery while power plug connected (in case battery had completely drained), wait 5 seconds, reconnect, wait 20 min then press power. Tried this four times total.
2. try if powers up with battery unplugged, DC-plug connected and bypass cable closed -> except high high pitch noise for a few seconds nothing happen
3. checked for loose connections of emmc, daugtherboard, flipped emmc/sd switch.
4. tried to boot from sd (mrfixit2001 image), with emmc/sd switch toggled on or off.
5. hit reset button.
6. flashed emmc via emmc-sd-adapter directly from my laptop with bionic lxde image via dd & tried to boot that.

Thankful for any suggestions.

Pages (1602): « Previous 1 … 946 947 948 949 950 … 1602 Next »

Login




Remember me Lost Password?

About Us