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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 22,706
» Latest member: timturner
» Forum threads: 11,454
» Forum posts: 91,184

Full Statistics

Latest Threads
E-Note Device (E-Ink, E-P...
Forum: General
Last Post: poVoq
21 minutes ago
» Replies: 3
» Views: 861
Advice on building a simp...
Forum: General
Last Post: davidmml78
43 minutes ago
» Replies: 5
» Views: 416
LTE doesn't work (Ukraine...
Forum: Manjaro on PinePhone
Last Post: mouffa
52 minutes ago
» Replies: 18
» Views: 255
manjaro-pinephone / plasm...
Forum: Manjaro on PinePhone
Last Post: mouffa
55 minutes ago
» Replies: 12
» Views: 330
Axolotl signal client pac...
Forum: Manjaro on PinePhone
Last Post: quixote
3 hours ago
» Replies: 3
» Views: 123
PSA: WiFi driver is broke...
Forum: PinePhone Software
Last Post: Merc
3 hours ago
» Replies: 3
» Views: 110
firefox-esr stopped worki...
Forum: Debian on PinePhone
Last Post: henrythemouse
6 hours ago
» Replies: 4
» Views: 150
Anyone have bluetooth hea...
Forum: PinePhone Accessories
Last Post: awaittrot
7 hours ago
» Replies: 11
» Views: 452
Arch Linux ARM root files...
Forum: Linux on Pinebook Pro
Last Post: rimaille
7 hours ago
» Replies: 2
» Views: 97
My pbp is a sleek, black,...
Forum: General Discussion on Pinebook Pro
Last Post: wdt
9 hours ago
» Replies: 12
» Views: 283

 
  Self-compiled GTK4: artefacts and missing icons
Posted by: Zombie Feynman - 06-19-2021, 11:21 AM - Forum: Debian on PinePhone - No Replies

I compiled GTK4 in my home directory (specifically, in /home/mobian/build) because I want to use the latest version of Megapixels on Mobian. Compilation itself went fine, but for some reason, most icons are missing, and I'm getting strange coloured artefacts.

GTK4 demo application: https://i.imgur.com/MMrO6Qv.png
Megapixels: https://i.imgur.com/K4qRRmL.png

To see if I wasn't missing anything, I followed the same steps to compile GTK4 on my Gentoo desktop, and the demo application there looks normal: https://i.imgur.com/ocFLhbC.png The key difference is that I used the Wayland backend on the PinePhone, and the X11 backend on Gentoo.

The packages I manually compiled are atk-2.36.0, gdk-pixbuf-2.42.6, glib-2.68.2, gobject-introspection-1.68.0, gtk-4.3.0, libepoxy-1.5.8, pango-1.48.5, and wayland-protocols-1.21. Other dependencies are installed systemwide from Mobian's standard repos (total package list here: http://dpaste.com/A3WZZ8Q2N). Environment variables:

Code:
$ export
declare -x CPPFLAGS="-I/home/mobian/build/include"
declare -x DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus"
declare -x FEEDBACK_THEME="/usr/share/feedbackd/themes/pinephone.json"
declare -x GSETTINGS_SCHEMA_DIR="/home/mobian/build/share/glib-2.0/schemas"
declare -x HOME="/home/mobian"
declare -x LANG="en_GB.UTF-8"
declare -x LDFLAGS="-L/home/mobian/build/lib -L/home/mobian/build/lib/aarch64-linux-gnu"
declare -x LD_LIBRARY_PATH="/home/mobian/build/lib:/home/mobian/build/lib/aarch64-linux-gnu"
declare -x LOGNAME="mobian"
declare -x LS_COLORS="rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.webp=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:"
declare -x MOTD_SHOWN="pam"
declare -x MOZ_ENABLE_WAYLAND="1"
declare -x OLDPWD="/home/mobian/build/source/gtk-4.3.0"
declare -x PATH="/home/mobian/build/bin:/home/mobian/build/bin:/home/mobian/build/bin:/home/mobian/build/bin:/home/mobian/bin:/home/mobian/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games"
declare -x PKG_CONFIG_PATH="/home/mobian/build/lib/pkgconfig:/home/mobian/build/share/pkgconfig:/home/mobian/build/lib/aarch64-linux-gnu/pkgconfig"
declare -x PS1="\\[\\033]0;\\u@\\h:\\w\\007\\]\\[\\033[01;32m\\]\\u@\\h\\[\\033[01;34m\\] \\w \\\$\\[\\033[00m\\] "
declare -x PWD="/home/mobian/build/source"
declare -x QT_QPA_PLATFORM="wayland"
declare -x QT_WAYLAND_DISABLE_WINDOWDECORATION="1"
declare -x SHELL="/bin/bash"
declare -x SHLVL="2"
declare -x SSH_TTY="/dev/pts/0"
declare -x STY="11127.pts-0.mobian"
declare -x TERM="screen.xterm-256color"
declare -x TERMCAP="SC|screen.xterm-256color|VT 100/ANSI X3.64 virtual terminal:DO=\\E[%dB:LE=\\E[%dD:RI=\\E[%dC:UP=\\E[%dA:bs:bt=\\E[Z:cd=\\E[J:ce=\\E[K:cl=\\E[H\\E[J:cm=\\E[%i%d;%dH:ct=\\E[3g:do=^J:nd=\\E[C:pt:rc=\\E8:rs=\\Ec:sc=\\E7:st=\\EH:up=\\EM:le=^H:bl=^G:cr=^M:it#8:ho=\\E[H:nw=\\EE:ta=^I:is=\\E)0:li#59:co#238:am:xn:xv:LP:sr=\\EM:al=\\E[L:AL=\\E[%dL:cs=\\E[%i%d;%dr:dl=\\E[M:DL=\\E[%dM:dc=\\E[P:DC=\\E[%dP:im=\\E[4h:ei=\\E[4l:mi:IC=\\E[%d@:ks=\\E[?1h\\E=:ke=\\E[?1l\\E>:vi=\\E[?25l:ve=\\E[34h\\E[?25h:vs=\\E[34l:ti=\\E[?1049h:te=\\E[?1049l:us=\\E[4m:ue=\\E[24m:so=\\E[3m:se=\\E[23m:mb=\\E[5m:md=\\E[1m:mh=\\E[2m:mr=\\E[7m:me=\\E[m:ms:Co#8:pa#64:AF=\\E[3%dm:AB=\\E[4%dm:op=\\E[39;49m:AX:vb=\\Eg:G0:as=\\E(0:ae=\\E(B:ac=\\140\\140aaffggjjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~..--++,,hhII00:po=\\E[5i:pf=\\E[4i:Z0=\\E[?3h:Z1=\\E[?3l:Km=\\E[<:k0=\\E[10~:k1=\\EOP:k2=\\EOQ:k3=\\EOR:k4=\\EOS:k5=\\E[15~:k6=\\E[17~:k7=\\E[18~:k8=\\E[19~:k9=\\E[20~:k;=\\E[21~:F1=\\E[23~:F2=\\E[24~:kB=\\E[Z:kh=\\E[1~:@1=\\E[1~:kH=\\E[4~:@7=\\E[4~:kN=\\E[6~:kP=\\E[5~:kI=\\E[2~:kD=\\E[3~:ku=\\EOA:kd=\\EOB:kr=\\EOC:kl=\\EOD:km:"
declare -x USER="mobian"
declare -x WINDOW="1"
declare -x XDG_DATA_DIRS="/home/mobian/build/share"
declare -x XDG_RUNTIME_DIR="/run/user/1000"
declare -x XDG_SESSION_CLASS="user"
declare -x XDG_SESSION_ID="4"
declare -x XDG_SESSION_TYPE="tty"

Has anyone seen issues like these on the PinePhone before, and if so, is there a simple fix (that doesn't involve switching distros or installing GTK4 systemwide)?


  My pbp is a sleek, black, flat brick, and won't boot from any kind of media
Posted by: rotwang - 06-19-2021, 09:01 AM - Forum: General Discussion on Pinebook Pro - Replies (12)

Hiya PBP folks,

My new pinebook pro will not give any indication of booting regardless of media. Now before you tell me the PBP isn't brickable, let me say that I've searched the forums here and found lots of answers describing non-booting PBPs, but none of them match the behavior I'm seeing. Let me also run down what I've tried:

- I tried to power on with an SD card flashed with this image: https://github.com/nadiaholmquist/archiso-pbp/releases
(With a nice long hold on the power button.)

- I tried to power on with a USB drive flashed with that same arch linux image (on the opposite-side USB port from the SD card to eliminated the chance that it was something wrong with the mini-board).

- I tried removing the eMMC and disabling with the eMMC switch on the board and powering on with an SD or USB drive.

- I tried  disconnecting the battery and connecting the bypass cables and tried to power on using the eMMC, SD, and USB.

- I tried re-seating the mini-board connector cable.

- I tried pushing the reset button. A lot.

In all cases the only life of any kind the PBP will show is a red light for the battery indicator when the power supply is plugged in. (So _some_ kind of power is going through the system.)

Here's some background that may or may not be relevant:

I got this unit a month or two ago. From the very first time I booted it the keyboard didn't work correctly. It seems it was an unusual hardware problem with the keyboard, see this thread for details: https://forum.pine64.org/showthread.php?tid=11300

The PINE64 folks replaced the keyboard and shipped it back to me. Manjaro booted and the keyboard worked perfectly at that point. The first thing I did was try to boot it off the SD card with that Arch image because I wanted to install Arch. But the SD card would not boot and would not be recognized by Manjaro. _Before_ the keyboard was replaced, I had booted this same SD card with the same Arch Linux image (and when the keyboard didn't work correctly in Arch on the SD I knew it wasn't a software problem with the keyboard.) 

So I pacman -Syu updated Manjaro, including the uboot flash because I was hoping this might fix my SD card not reading. It was after that update that it would never boot again.

My guess:

I suspect there's probably two things going wrong at the same time (the really tricky problems are always compound like that!) I suspect the SD card reader (and possibly the mini board) is not working (hardware). And at the same time I toasted the eMMC with the uboot flash (software). But then why I can't I boot my USB drive? Is there a way to move USB up the boot order so the PBP wants to boot from it first?

I contacted PBP support about this, but since it (initially) sounds so much like the normal toasting of the eMMC, they sent me back to the forum to get your opinions on whether this is purely a software issue.

Let me know if you have any insights! And thanks for reading!


  2 weeks in! This is how it went!
Posted by: AwHereWeGoAgain - 06-19-2021, 05:55 AM - Forum: General Discussion on PinePhone - No Replies

So I got my new Pinephone and obviously started playing with it immediately.  While the phone itself worked, I was running into various issues with the hardware I was sticking in it.  Various non compatible sims, bad micro SD cards, etc.  (The stuff that is frustrating but in no way pinephones fault and all part of the process.)  The micro SD cards im more salty about as I purchased a 3 pack of fast 64gb micro SD's and when they arrived they were labeled as 64gb but they were actually around 8 gig and not fast.  (I had fell victim to one of the fake SD card scams that had been going around lately.)  Basically every time I tried to resize to 64 gig, the SD card would corrupt itself.  I used various tricks in Gparted to resize to just under 8 gig and it booted Mobian.  (Frustrated, I went out to Wallyworld and purchased a new set of 64 gig SD cards and they worked.)  Needless to say, if your new SD card dont work, consider using a different make/model. 

The operating systems I used: Mobian as well as Manjero Phosh,  I played around with the included Plasma and decided it had enough potential I would let it stay....it just needs to mature a bit. 

I learned that patience is a virtue.  When booting your OS for the first time, be prepared for Manjero Phosh to dump you to a terminal login prompt and look like it is hung for a good several minutes. 
(This is OK...dont shut your phone down and screw it up like I did Wink )
Mobian was nice enough to put up a splash screen informing me that it was resizing the SD and thus was going to take a bit......like about an hour and a half......
(Apparently this is also OK...dont shut your phone down and screw it up like I did Wink
Once the OS's are set up, they work pretty well although a bit laggy at times.  The last sytem update for Mobian speed up Mobian a noticeable amout for me.  (Currently Mobian is feeling like it will be my favorite all though Manjero is very similar and has a precompiled Anbox which works well enough. 

The sim experience. 
Me sticking in a verizon sim via Visible: Fail..... Nothing works...proceed to spend 4 hours looking for APN configurations and then finally realize that Visible is listed on the not compatible carrier list generously provided by the PinePhone Wiki.  Lol Should have researched that one ahead of time.

Me then grabbing an old flipphone that has a Verizon sim via Straight Talk:  Success!  I made 2 call and made 1 text before ST shut me down and send me a message informing me to put the sim back in the original phone.  (Well gee thanks ST....wont be doing business with you anytime soon Rolleyes )


I finally got a US Mobile sim and it worked great. I highly recommend them.  Service costs about 16USD after tax and the customer service is decent. 
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Things that work:

All Calls, Text, and data seem to be working well.  Very pleased.
The dock is proving very helpful
The camera is better than expected.
Screen rotation works on all OS's
Anbox works!.....enough.
Most apps work with the occasional cant fit on the screen issue.
The battery lasts longer than anticipated!
Mobian can mount a docked SD card.....eventually


Things that dont work or significant issues.

Apparently im dead.....the GPS says I am currently residing in the Lynn Wood Cemetery.  (At Least I got good reception out here Angel )
Oh....this is an Arm based CPU.....I guess a lot of my linux programs aren't going to like that much very much......
Everything is rather slow.......  The Plasma OS seemed much snappier.  I wonder if it has to do with it being on the EMMC instead of the SD card.  (Does putting the OS on the EMMC speed the OS's up any?)

--------------------------------------------------------------------------------------------------------------------------------------------------------
Things i haven't tried but am going to.

Hot Spot.
Setting up my VPN
Installing my first successful 3rd party linux app on this thing.  (Just got to find one that will work lol)

 

Overall, this phone is pretty exciting.  I have started carrying it on my person along with my android.  (My pinephone is getting its daily driver training Big Grin )  I look forward to each update and thank everyone for their hard work on this project!  Its looking good so far!


  Pinebook pro nearly unusable after using manjaro-arm-installer
Posted by: TheCounselor - 06-18-2021, 03:34 PM - Forum: Linux on Pinebook Pro - No Replies

Good afternoon everyone, about a month ago I tried using the manjaro-arm-installer script to flash the emmc. This completely bricked my device, no booting from emmc or sd card, not even the green LED power light would come on. Finally got around to opening the thing up and hitting the RESET button. This got booting from the sd card working again, but the performance is absolute garbage. I can get to the manjaro KDE desktop but it will freeze if I try to do anything useful. I'm at my wit's end with this thing, any guidance you can offer would be greatly appreciated, Thank You!


  How to install Linphone
Posted by: AndyM - 06-18-2021, 07:42 AM - Forum: Arch Linux on PinePhone - No Replies

Has anyone managed to install linphone, or for that matter any other VOIP software?

I have Jami installed, but unfortunately voice calls seem to be very distorted


  Kernel panics on Youtube
Posted by: solostian - 06-18-2021, 02:36 AM - Forum: General Discussion on Pinebook Pro - No Replies

Hi,

For a couple of weeks now, my Pinebook Pro gets into frequent kernel panics.
The most noticable activity going on at those time is Youtube playing long clips.

At first, I thought it was the NVMe drive overheating, so I set the laptop on a cooling pad.
The kernel panics still occur even though the temp is low (I keep Psensor on the screen foreground).

This page suggest rebuilding the initramfs but I am wary of these kind of operations.

My unit is running the stock Manjaro distribution.

Can anyone propose a troubleshooting course?

Cheers,
Solostian


  cannot boot SD card : "unable to select a mode"
Posted by: alchemist - 06-18-2021, 02:03 AM - Forum: General Discussion on Pinebook Pro - No Replies

Hi!

I have U-Boot installed on SPI and Gentoo Linux running on eMMC.
I would like to be able to boot from SD card for maintenance purposes.

The boot order is this by default :

Code:
altbootcmd=setenv boot_syslinux_conf extlinux/extlinux-rollback.conf;run distro_bootcmd
boot_scripts=boot.scr.uimg boot.scrboot_syslinux_conf=extlinux/extlinux.conf
boot_targets=mmc1 mmc0 nvme0 usb0 pxe dhcp sf0
bootcmd=run distro_bootcmd
distro_bootcmd=setenv nvme_need_init; for target in ${boot_targets}; do run bootcmd_${target}; done


So it should be: sd card, eMMC, nvme, usb, pxe, ...

but when I boot, U-Boot try to initilize the SD card and fails "unable to select a mode", then continues to eMMC:
Code:
The system is going down for reboot NOW!
pbp ~ #
U-Boot TPL 2020.07-pcm720-00007-g132da38490 (Jul 20 2020 - 20:40:04)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...

U-Boot SPL 2020.07-pcm720-00007-g132da38490 (Jul 20 2020 - 20:40:04 +0300)
Trying to boot from SPI
NOTICE:  BL31: v2.3(release):v2.3-353-gae72c4d5e
NOTICE:  BL31: Built : 20:39:57, Jul 20 2020


U-Boot 2020.07-pcm720-00007-g132da38490 (Jul 20 2020 - 20:40:04 +0300)

SoC: Rockchip rk3399
Reset cause: RST
Model: Pine64 Pinebook Pro
DRAM:  3.9 GiB
PMIC:  RK808
MMC:  mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
In:    serial
Out:  serial
Err:  serial
Model: Pine64 Pinebook Pro
Net:  No ethernet found.
Hit any key to stop autoboot:  0
unable to select a mode
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
651 bytes read in 18 ms (35.2 KiB/s)
## Executing script at 00500000
===========================
=== GENTOO LINUX (eMMC) ===
===========================
Boot script loaded from mmc 0
25088512 bytes read in 1104 ms (21.7 MiB/s)
61463 bytes read in 22 ms (2.7 MiB/s)
## Flattened Device Tree blob at 01f00000
  Booting using the fdt blob at 0x1f00000
  Loading Device Tree to 00000000f4e8c000, end 00000000f4f03fff ... OK

Starting kernel ...

pbp login:


I've tried many different OS : manjaro, dietpi, and same result:
Code:
=> mmc dev 1
unable to select a mode

==== unplug SD card ; replug it


=> mmc dev 1                 
switch to partitions #0, OK
mmc1 is current device
=> mmc part

Partition Map for MMC device 1  --  Partition Type: DOS

Part Start Sector Num Sectors UUID Type
** Can't read partition table on 1:0 **

but Linux can read the SD card and the contents. The partition table is MBR, boot partition 1 is in FAT or EXT2 and marked as active.

I will try an other SD card...

SOLVED: I change the SD card and now it boots first on it, then the eMMC.


  Axolotl signal client package
Posted by: lolgzs - 06-18-2021, 01:09 AM - Forum: Manjaro on PinePhone - Replies (3)

Hi,

as I never managed to run Axolotl using flathub / snap packages, I've built an Arch AUR package that works at least for me (phosh).

https://aur.archlinux.org/packages/axolotl-bin/

Installation:


Code:
pamac install axolotl-bin

It just repackages the mobian binairies for Arch (see https://github.com/nuehm-arno/axolotl-mobian-package ). Hope it helps.


  phone call using built it app will not go to bluetooth
Posted by: motox6 - 06-18-2021, 12:46 AM - Forum: Debian on PinePhone - Replies (1)

I was listening to a podcast via a bluetooth headset.

I paused the podcast app and dialed a number using the standard phone app.

It would not connect the audio to the the bluetooth headset.

It was stuck using the phone speaker.  I toggled between speakerphone mode and hold the phone up to your ear mode.  But no bluetooth.

Is there supposed to be a bluetooth button somewhere?

After I gave up on the call, I went back to the podcast app and the bluetooth worked as expected.


  display will not wake up
Posted by: motox6 - 06-18-2021, 12:43 AM - Forum: Debian on PinePhone - No Replies

I am listening to a podcast, the screen is blank and won't wake up.

The button on the side of the phone does nothing.

No amount of time waiting looks to matter.

I can ssh into the phone via the wifi.

I would prefer the button worked.

Is there a way to wake up the display from the command line?