Hi ya'll,

So I'm a pinetab noob trying to make lora go. I have some questions about the internal USB hub routing.


The block diagram on page 2 of the schematic says "SATA SSD" port(?) connected to the four port internal usb hub (via HOST-DP2/DM2):



But if I look on page 16 of the schematic is says that the "Docking" port is connected to port DP2/DM2 on the hub.  Also the docking portion of the schematic seems to have presence sensing to control power for that port.  So I assume it really is the "docking" connector for the keyboard add on.


So is the correct internal expansion port actually the "usb host" connected to HOST-DP1/DM1?
If so, I suspect the reason I don't see my lora device is that I need to turn on GPIO0-LDO on the PMIC?  Does anyone know how to do that yet?  (Or even how to get pmic status in /proc or somesuch so I can poke around?

Alternatively: Is there a recommended way to open the case on the Pinetab (so I can physically look to confirm that the Lora board that was supposed to be installed is actually present   )

Thanks much!

Hi ya'll,

So I just received my pinetab (with an alpha version of the Lora radio module).  I'm eager to port meshtastic to your slick board but I admit I haven't been following pinetab development closely.  

I'm reasonably experienced with linux driver development (though not this year) and I think I can handle that part, but I have some questions on distribution choice etc...  Any advice would be appreciated:

* What OS distribution should I target initially? - I assume the development branch of the "ubuntu touch" that came preinstalled on the tablet?
* I will need to build and distribute an (improved) version of the CS341 driver for the USB/SPI chip used in this radio.  Where would be best to provide that for others (a .deb?)

My general current (crummy) plan is here.

What is happening: trying to put pinebook pro to sleep results in complete death of the laptop. Power light goes off, screen goes off and it absolutely refuses to come back alive. I have to hold the power button for 7 seconds, and turn it back on to get to to work. Otherwise it absolutely refuses to show any signs of life.

What I tried: removing swap file completely

Started happening since I ran the updates through software updater. Before that it was working fine for a good week since I first got the laptop.

Given I am a beginner at linux, I am not even sure how to begin to debug something like that. Any help would be appreciated.

I am having problems getting ArchLinux installed on my Pine Book Pro. I've follows the instructions at boot of these locations
https://github.com/nadiaholmquist/archis.../README.md
https://www.bencode.net/posts/pinebook/

I can reliably boot from the sdcard and mount the root partition and arch-chroot into it, but I can only get the amber light when trying to boot from the eMMC.

Does anyone have any ideas on what I could start looking at to get this working?

Hi,


I just received my RockPro64, very cool, I want to use it with a 10GbE NIC.


I tried a few distros but rockpro64-debian-mrfixit-190531 was the only one I could get booting from eMMC.



I upgraded to Debian 10, the kernel stays at 4.4, trying to upgrade to a Debian kernel fails (thankfully) probably because the partition is RO.


OK so I see a rock64 5.9 here, as debs:


https://github.com/ayufan-rock64/linux-m...l/releases


Any idea if this 5.9 supports booting from eMMC, if so, what is the easiest way to get this kernel deployed, right now I'm just connected up with a keyboard and monitor, can I just remount RW, I read something that suggests I have to interrupt the boot and do something in u-boot but I'm unsure on that, if I have to do it this way, do I have to use a serial console or something?


Cheers
Richard

I received my PBP around a week ago and the keyboard doesn't work. I contacted support that night, while they said they would send me a new keyboard, they havn't said anything since, not even how long it might take to ship the part, nor what the status of the part is. Is this normal? Is there something going on I'm unaware of that would induce a delay in getting this sort of information? As-is, the device is unusable and is making me quite sad.

Good evening,
i'm one of the guys that has preordered the pinephone PMOS-Edition very early, because i was really eager to get a working linux phone.
And yeah, i received my pinephone, was very happy, until i noticed that the screen was not working as intended.
   

The did work, but had many problems with the image on it. I tried many things like flashing manjaro, in hope it world be the os, but no.
So then i did contact the Pine64 support. Didn't receive a message back for 9 days. Then i became worried and did, what i didn't want to do at all, opening a paypal case just to be on the safe side and get things going. After that i finally got a message back from the support telling me to please try to adjust the cables in the phone. So i did, and nothing changed.

After some conversation i was offered to get a replacement screen, which they sent out to me. While it was shipping my paypal case time was running out, but i didn't worry about that anymore. I would have a replacement screen, so no worries for me.

And indeed, i did receive my screen six days ago. I immediately started replacing it, and indeed, it worked. The problem here was, the touchscreen did not. So i tried reinserting the cables and looking for broken cables in the screen. I didn't find anything. What i tried then was connecting the old screen, and yeah, while the image was broken, the touchscreen worked. So in that case i can be sure it's a problem with the new screen, not with the phone itself.

I'm quite puzzled how it can be that i received two non-working devices in a row. After all i did not notice anyone else having problems with the quality of their phone here on the forums, maybe i just didn't look enough.

But i wonder how that could happen. Additionally i'm a bit disappointed in the support. I know, it's not like Pine64 is a multi-million dollar company with a giant support section. But i had to wait 10 days and a paypal case for an answer. While the case was running i got my answers rather quickly, now after it ran out and i have those two partially broken screens i don't get any answers anymore. Still waiting for one.

Did anyone else have a similar experience, am i just in an unlucky position to be here?

Greetings
Janik

Hi, 9 days ago I opened an ticket on Pine64's desk.zoho. No one has answered me yet.

How long does Pine usually take to respond?

Just wanted to let everyone know that after installing Fedora 32 Workstation the upgrade to Fedora 33 Workstation went off without a hitch.

Gnome is version 3.38.

Memory usage in Fedora 32 hovered around 1.2G. In Fedora 33, memory usage hovers around 980M. The desktop is snappier and animations are smoother. CPU usage seems to be lower as well. Videos and Youtube run fine. I haven't tested anything above default settings for video playback, yet. I have lots of testing and playing to find all the changes.

Fedora 33 adds better support all around for Pine64 hardware. I didn't get a chance to really test Fedora 32 that much but it was a solid experience. I have it installed on emmc.

Fedora Magazine Article

In my opinion, Pinebook Pro went from tinker toy to a serious daily driver for me with Fedora. It really is solid. Software installation is a breeze with gnome store and RPMFusion is a nice equivalent to AUR. Also, dnf package manager is great. The documentation is superb for learning and getting things done as quickly and easily as possible.

This is my first experience with this distro and I'm really enjoying it.

So I just got my Pinebook Pro ANSI in and right off the bat I found I was having trouble connecting to Wi-Fi under Manjaro. It refused to connect, and kept asking for the password again and again.

I then remembered I had 802.11r Fast Transition enabled across my APs (under OpenWRT). When I disabled it on one of them, my Pinebook was able to connect. Turning it back on kicks it off the network.

Is this a known issue? I haven't experienced an issue with any of my other wireless devices. I'd like to keep it enabled if at all possible. A lot of people in my home make use of Wi-Fi calling, and FT helps with dropouts.

Thanks!