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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 17,845
» Latest member: etothepii
» Forum threads: 7,693
» Forum posts: 62,879

Full Statistics

Latest Threads
Barometer/Pressure sensor...
Forum: PineTime Hardware and Accessories
Last Post: danielt
4 minutes ago
» Replies: 1
» Views: 33
Fastest SD card
Forum: PinePhone Hardware
Last Post: happybot-4678
9 minutes ago
» Replies: 4
» Views: 169
Pinetab Smart Home expans...
Forum: General Discussion on PineTab
Last Post: eaglecup
52 minutes ago
» Replies: 9
» Views: 290
RISC OS
Forum: General Discussion on Pinebook
Last Post: Twig
54 minutes ago
» Replies: 7
» Views: 1,897
Pinebook without stuck or...
Forum: General Discussion on Pinebook
Last Post: tiagoespinha
1 hour ago
» Replies: 5
» Views: 109
Ayufan's Ubuntu Focal Gno...
Forum: Linux on Pinebook Pro
Last Post: Wizzard
2 hours ago
» Replies: 12
» Views: 467
SSD Adapter MIA
Forum: Pinebook Pro Hardware and Accessories
Last Post: noeman5
4 hours ago
» Replies: 0
» Views: 19
Kali Linux for Pinebook P...
Forum: Linux on Pinebook Pro
Last Post: junefish
6 hours ago
» Replies: 33
» Views: 5,191
Suggested UX improvements...
Forum: General
Last Post: xmixahlx
6 hours ago
» Replies: 6
» Views: 159
mesa-git build script for...
Forum: Pinebook Pro Tutorials
Last Post: xmixahlx
6 hours ago
» Replies: 27
» Views: 2,683

 
  SSD Adapter MIA
Posted by: noeman5 - 4 hours ago - Forum: Pinebook Pro Hardware and Accessories - No Replies

Back on March 24th, I ordered a PineBook Pro and the SSD adapter for it so that I could use a 1TB M.2 SSD as the main drive instead of an SD card.  On the 29th I received an email stating the adapter was being prepared for shipping.  Using the 17Track tracking number I kept watch for progress of the adapter.  In one month, there was no movement, so I contacted customer support and was told they would look into it.  Now another month later, and I have not heard anything.  I hope to see my PineBook Pro sometime before Christmas.  I have no faith in 17Track whatsoever.  Anybody else having trouble with a similar lack of information?


  PBP not powering up (anymore)
Posted by: Criena - 10 hours ago - Forum: General Discussion on Pinebook Pro - Replies (1)

Hi there,

after waiting for such a loooong time, I finally got my PBP on Friday.

Over the weekend I played around a little bit with Manjaro and then wanted to try a different OS. After repartitioning the eMMC, I accidentally pressed the false delete key (i.e. the power button) and the system shut down. Since then I can't get the PBP powering up anymore. Neither a USB stick (the one I used for the interrupted installation) nor an SD card with the Manjaro KDE image does the job.

I don't really understand what's wrong since at least the SD card should do the trick. A hardware failure just in that unfortunate moment would be a big coincidence. But what else could it be and most importantly: how can I get it fixed?


Anyone got a lifesaving clue?

Thanks!
Criena


Bug WiFi enabled but refuses to connect
Posted by: cardboardmaster - Yesterday, 01:36 PM - Forum: Getting Started - No Replies

Brand-new pinebook pro. Factory KDE Manjaro.

I turned on the wifi hardware switch and I see `wlan0` in my interfaces. If I click the NetworkManager icon in the taskbar, I see all the wifi networks in my area.
If I click on one and type in the password, it'll spin for 30 seconds and then ask for the password again. I tried with `nmcli` too. Same result: just keeps asking for the password, even when I know it's correct.

What do I do?


  Not receiving SMS messages
Posted by: newton688 - Yesterday, 08:23 AM - Forum: Debian on PinePhone - Replies (2)

Hi All,

I have been having a problem for some time where SMS messages were not being received, but outgoing ones, phone calls and data are working fine. I am posting this in case other run into the same problem, which seems to be fairly rare so far.

It turns out that that the cause of my problem was related to a bunch of SMS messages that lingered in the modem's queue (10 of them). This queue appears to be persistent across reboots and also re-imaging the OS. I don't yet understand all of the technical details.

What worked for me was to use the ModemManager command-line. Note that on Mobian the ModemManager does all of the communications with the 3G modem including phone calls, cellular data, GPS and SMS. This may not be the case with other PinePhone OSes.

You can access the ModemManager using the mmcli command.

$ sudo mmcli -m 0 --messaging-list-sms
Found 10 SMS messages:

/org/freedesktop/ModemManager1/SMS/0 (received)
...

In my case there were 9 SMS messages in the received state and 1 in the receiving state. I deleted all of the messages like this:

$ sudo mmcli -m 0 --messaging-delete-sms=1  # Repeat with 1 through 10 to delete all of the messages

Note that the "-m 0" refers to modem 0 (the only one usually in a pinephone). For more help on the messaging related actions available in mmcli you can check the help with "mmcli --help-messaging." This article is also helpful in learning: https://electronproton.com/mmcli-command-examples/

I hope that this is helpful for anyone else having the same problems as I did.

Chris


  SDR-Overview (HackRF, rad1o, PlutoSDR, rtl-sdr, LimeSDR, AirSpy)
Posted by: manawyrm - Yesterday, 08:20 AM - Forum: Pinebook Pro Tutorials - No Replies

Hi,

I've gone ahead and tested a couple of SDRs on the Pinebook Pro running Manjaro. 
[Image: urgjpbyaqhk.jpg]

So far the AirSpy and HackRF are my clear favorites.
Here's my notes on what worked, what didn't and how to get it running: 

HackRF / rad1o: 
Very painless experience. 
Just install (and run) gqrx via

Code:
sudo pacman -S gqrx
It'll depend on the HackRF driver.
To get it working without root-permissions create /etc/udev/rules.d/53-hackrf.rules.
Code:
sudo nano /etc/udev/rules.d/53-hackrf.rules
Code:
ATTR{idVendor}=="1d50", ATTR{idProduct}=="604b", SYMLINK+="hackrf-jawbreaker-%k", MODE="660", GROUP="plugdev"
ATTR{idVendor}=="1d50", ATTR{idProduct}=="6089", SYMLINK+="hackrf-one-%k", MODE="660", GROUP="plugdev"
ATTR{idVendor}=="1d50", ATTR{idProduct}=="cc15", SYMLINK+="rad1o-%k", MODE="660", GROUP="plugdev"
ATTR{idVendor}=="1fc9", ATTR{idProduct}=="000c", SYMLINK+="nxp-dfu-%k", MODE="660", GROUP="plugdev"
(save with Ctrl+O, Enter, Ctrl+X), then reboot.

[Image: ntsreobximc.jpg]
[Image: fotdunihyjq.jpg]

PlutoSDR:
Doesn't work! libiio segfaults at the moment (using software from 31.05.2020).
If you want to try yourself:
Code:
pacman -S soapyplutosdr

[Image: etqjronuxac.png]

RTL-SDR:
Works very well.
Just install (and run) gqrx via
Code:
sudo pacman -S gqrx
[Image: yfvdnzahixl.jpg]

AirSpy (non-HF+):
Works very well.
Just install (and run) gqrx via
Code:
sudo pacman -S gqrx

LimeSDR:
Didn't work with GQRX, worked with SDRAngel.
Code:
sudo pacman -S sdrangel-sse4.1 limesuite
[Image: jvytfkgedap.jpg]

Have fun,
Tobias


  Rock64 v3 with Real Time Clock (RTC), how to verify?
Posted by: Enig123 - Yesterday, 02:03 AM - Forum: General Discussion on ROCK64 - Replies (1)

After over 2 months' voyage, my Rock64 v3 finally was delivered. It is known to have a RTC (Real Time Clock) module that v2 does not have.

My question is, how can I verify RTC module is there working?

BTW, anyone can shed some light on what exactly the RTC module means for an OS?

My dmesg message is as follow (running OpenBSD 6.7):

OpenBSD 6.7 (GENERIC.MP) #1: Sat May 16 15:59:24 MDT 2020
    root@syspatch-67-arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP
real mem  = 1006903296 (960MB)
avail mem = 945868800 (902MB)
mainbus0 at root: Pine64 Rock64
cpu0 at mainbus0 mpidr 0: ARM Cortex-A53 r0p4
cpu0: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu0: 256KB 64b/line 16-way L2 cache
efi0 at mainbus0: UEFI 2.8
efi0: Das U-Boot rev 0x20200400
apm0 at mainbus0
psci0 at mainbus0: PSCI 1.1, SMCCC 1.2
syscon0 at mainbus0: "syscon"
"io-domains" at syscon0 not configured
"grf-gpio" at syscon0 not configured
"power-controller" at syscon0 not configured
"reboot-mode" at syscon0 not configured
rkclock0 at mainbus0
syscon1 at mainbus0: "syscon"
"usb2-phy" at syscon1 not configured
ampintc0 at mainbus0 nirq 160, ncpu 4 ipi: 0, 1: "interrupt-controller"
rkpinctrl0 at mainbus0: "pinctrl"
rkgpio0 at rkpinctrl0
rkgpio1 at rkpinctrl0
rkgpio2 at rkpinctrl0
rkgpio3 at rkpinctrl0
"opp_table0" at mainbus0 not configured
simplebus0 at mainbus0: "amba"
"dmac" at simplebus0 not configured
"arm-pmu" at mainbus0 not configured
rkdrm0 at mainbus0
drm0 at rkdrm0
agtimer0 at mainbus0: tick rate 24000 KHz
"xin24m" at mainbus0 not configured
"i2s" at mainbus0 not configured
"spdif" at mainbus0 not configured
com0 at mainbus0: ns16550, no working fifo
com0: console
rkiic0 at mainbus0
iic0 at rkiic0
rkpmic0 at iic0 addr 0x18: RK805
"spi" at mainbus0 not configured
"watchdog" at mainbus0 not configured
rktemp0 at mainbus0
"efuse" at mainbus0 not configured
"gpu" at mainbus0 not configured
"video-codec" at mainbus0 not configured
"iommu" at mainbus0 not configured
"vop" at mainbus0 not configured
"iommu" at mainbus0 not configured
"hdmi" at mainbus0 not configured
"codec" at mainbus0 not configured
"phy" at mainbus0 not configured
dwmmc0 at mainbus0: 50 MHz base clock
sdmmc0 at dwmmc0: 4-bit, sd high-speed, mmc high-speed, dma
dwmmc1 at mainbus0: 50 MHz base clock
sdmmc1 at dwmmc1: 8-bit, mmc high-speed, dma
dwge0 at mainbus0: address xx:xx:xx:xx:xx:xx
rgephy0 at dwge0 phy 0: RTL8169S/8110S/8211 PHY, rev. 6
"usb" at mainbus0 not configured
ehci0 at mainbus0
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "Generic EHCI root hub" rev 2.00/1.00 addr 1
ohci0 at mainbus0: version 1.0
"external-gmac-clock" at mainbus0 not configured
"sdmmc-regulator" at mainbus0 not configured
"vcc-host-5v-regulator" at mainbus0 not configured
"vcc-host1-5v-regulator" at mainbus0 not configured
"vcc-sys" at mainbus0 not configured
"ir-receiver" at mainbus0 not configured
"leds" at mainbus0 not configured
"sound" at mainbus0 not configured
"spdif-dit" at mainbus0 not configured
cpu1 at mainbus0 mpidr 1: ARM Cortex-A53 r0p4
cpu1: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu1: 256KB 64b/line 16-way L2 cache
cpu2 at mainbus0 mpidr 2: ARM Cortex-A53 r0p4
cpu2: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu2: 256KB 64b/line 16-way L2 cache
cpu3 at mainbus0 mpidr 3: ARM Cortex-A53 r0p4
cpu3: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu3: 256KB 64b/line 16-way L2 cache
usb1 at ohci0: USB revision 1.0
uhub1 at usb1 configuration 1 interface 0 "Generic OHCI root hub" rev 1.00/1.00 addr 1
scsibus0 at sdmmc0: 2 targets, initiator 0
sd0 at scsibus0 targ 1 lun 0: <SD/MMC, SDU1, 0002> removable
sd0: 15100MB, 512 bytes/sector, 30924800 sectors
sdmmc1: can't enable card
vscsi0 at root
scsibus1 at vscsi0: 256 targets
softraid0 at root
scsibus2 at softraid0: 256 targets
bootfile: sd0a:/bsd
boot device: sd0
root on sd0a (f994f9ec2de5c2ae.a) swap on sd0b dump on sd0b
WARNING: bad clock chip time
WARNING: CHECK AND RESET THE DATE!
rkdrm0: no display interface ports configured
rock64$ dmesg | grep clock
rkclock0 at mainbus0
dwmmc0 at mainbus0: 50 MHz base clock
dwmmc1 at mainbus0: 50 MHz base clock
"external-gmac-clock" at mainbus0 not configured
WARNING: bad clock chip time


  KVM ARM virtualisation
Posted by: vanja - Yesterday, 01:51 AM - Forum: PinePhone Software - No Replies

Hi,
would this work on pinehphone? any distribution, like debian?
https://systems.cs.columbia.edu/projects/kvm-arm/

https://systems.cs.columbia.edu/archive/...hitecture/

what I dont really undestand is in which phase of development is this? can it be downloaded and installed or this is just design phase..


  What is the most polished OS for pinephone?
Posted by: coolguy129 - 05-30-2020, 02:49 PM - Forum: General Discussion on PineTime - No Replies

I have recently been looming at buying a pinephone and pinebook and am now looking at the pinetime. However, I was wondering if there was an OS for pinetime with a decent UI? What would be the most polished one? Thanks in advance, Coolguy129.

Moderator edit: Moving to Pinephone forum, (from PineTime forum).\

Edit: Sorry, didn't make it clear that I was looking for an OS for pinetime.


  New PBP - Wifi Disabled on First Boot
Posted by: cephalien - 05-30-2020, 12:37 PM - Forum: General Discussion on Pinebook Pro - Replies (1)

Hi All!

First post, just got my new Pinebook Pro. Initial impressions are great but I ran into one small snag.

My wifi was disabled via hardware when I first powered on the machine, and I had to go googling. If this has happened to anyone else, hit the Pine Key + F11 and look for the numlock light to flash twice. Then reboot.

Wifi was fine after that, but there's no indication in the wireless settings - the adapter is just gone because it's disabled from HW.


Bug open wifi works and secure wifi does not
Posted by: j3bel - 05-30-2020, 08:46 AM - Forum: General Discussion on Pinebook Pro - Replies (1)

Hey guys

Received my pinebook a few days ago and it's a great device. Wifi was working as expected (after super +f11 fix).

I started messing around seeing how well it could multitask aaand ended up with a frozen screen. I power cycled and all seemed fine, until I couldn't sign into the wifi I was just on.

I can see available networks and attempt to sign in but it fails. But if I go into my router and remove the password I can sign in. Weird!

Any thoughts?