| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Pine Time dead
Forum: General Discussion on PineTime
Last Post: chris.burmajster
9 hours ago
» Replies: 0
» Views: 41
|
Booting Issues
Forum: PineNote Software
Last Post: vlagged
Yesterday, 04:17 PM
» Replies: 24
» Views: 18,887
|
App launcher shows tiny i...
Forum: PineNote Software
Last Post: vlagged
Yesterday, 04:12 PM
» Replies: 1
» Views: 1,022
|
Freezes and kernel panics...
Forum: Linux on RockPro64
Last Post: prahal
04-15-2026, 06:48 PM
» Replies: 4
» Views: 1,263
|
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
04-06-2026, 08:44 AM
» Replies: 0
» Views: 214
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
04-05-2026, 03:03 AM
» Replies: 19
» Views: 8,834
|
Finally got Kali working ...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
04-04-2026, 08:00 AM
» Replies: 0
» Views: 315
|
Charging problem
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
04-04-2026, 07:30 AM
» Replies: 0
» Views: 140
|
Latest firmware for PineP...
Forum: PinePhone Software
Last Post: baptx
04-03-2026, 08:37 AM
» Replies: 106
» Views: 217,672
|
Updates have gotten me ex...
Forum: General Discussion on PineNote
Last Post: bills2002
04-02-2026, 05:16 PM
» Replies: 0
» Views: 268
|
|
|
| Longer Power Cable |
|
Posted by: Tekchip - 11-10-2019, 09:51 AM - Forum: Pinebook Pro Hardware and Accessories
- Replies (4)
|
 |
The power cable that comes with the device is incredibly short. Nearly useless. It doesn't reach my couch from an outlet so I can't sit on the couch and use the laptop when battery is low while it's charging. I've tried a few different USB-C wall warts and cables and while most can charge the laptop while I'm not using it they can't really push enough power to charge in a reasonable amount of time while in use.
Does anyone have recommendations for either a USB-C wall wart that can charge the laptop quickly?
Alternatively can a USB-A wall wart of reasonable power used in connection with this https://store.pine64.org/?product=2-mete...ower-cable be used? If yes, then what wall warts are others using with this cable? This cable is listed under the laptops section of the store page and it's noted it works for "Pinebook" but I don't want to assume this matches the PBP as there are a hand full of other exceptions I've seen mentioned. If this does match with the PBP perhaps this could be more explicit on the store page.
Thanks for any help or insight anyone can provide!
|
|
|
|
| Oops! I messed up the graphics drivers |
|
Posted by: diodelass - 11-10-2019, 08:48 AM - Forum: Linux on Pinebook Pro
- Replies (1)
|
 |
Okay, I admit I'm in over my head a little bit here. I know messing with the graphics drivers wasn't a very clever idea this early in the software ecosystem's life, but I bear a certain curse of wild curiosity and can never leave anything alone. It's my cross to bear, but if anyone else has useful insight into what's going on with my unit, I would be quite grateful indeed.
I have ayufan's Bionic image running. The other day, I was poking around the list of packages, and I encountered three that were of interest:
Code: libmali-rk-midgard-t86x-r14p0 [installed]
libmali-rk-midgard-t86x-r14p0-gbm
libmali-rk-midgard-t86x-r14p0-wayland
I'd previously tried to no success to get Wayland working, and here I thought - hey, there's what I need, I better install those other two drivers. So I did, and now Wayland appears to work (!) but... now a lot of other stuff is broken. Namely, sddm and lightdm won't work (the former exits with status 6), and KDE plasma (which worked fine before under X) will not start, popping up a nice little dialog box informing me that my OpenGL 2.0 is broken (when run from either X or Wayland). Xfce still works alright (using that now to post this) but the general status of the system's graphics is perplexing.
According to glxinfo, I have OpenGL 3.1 support:
Code: % glxinfo | grep -i version
server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
Version: 19.0.8
Max core profile version: 3.3
Max compat profile version: 3.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.0
OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.8
OpenGL core profile shading language version string: 3.30
OpenGL version string: 3.1 Mesa 19.0.8
OpenGL shading language version string: 1.40
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.8
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
However, systemsettings5 (the KDE Plasma system configurator) crashes immediately on startup, and most utilities related to OpenGL seem to emit a similar error that may indicate the problem:
Code: libGL error: MESA-LOADER: failed to open rockchip (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libGL error: failed to load driver: rockchip
I admit I don't really know what's going on here, but it looks like something is missing. I have searched through my apt logs to see if I accidentally autoremoved something important, but I can't find it.
My real question now is simply: what do? Have I hosed it to the point where I need to reimage, or is there just some little thing missing that I can install and be on my way, or what?
Thanks in advance for whatever advice any of you might have.
|
|
|
|
| Help me understand the boot up process |
|
Posted by: olivercfc - 11-10-2019, 08:30 AM - Forum: Linux on Rock64
- No Replies
|
 |
I'm obviously missing something fundamental here.
I built an image with buildroot which creates a u-boot-tpl-spl.img, a u-boot.itb file and a root partition
Code: image = "u-boot-tpl-spl.img"
offset = 32768 # 512 * 0x40 from start of sd card
image = "u-boot.itb"
offset = 262144 # 512 * 0x200 from start of sd card
bootable = "yes"
image = "rootfs.ext2"
In the rootfs partition there's a file called /boot/extlinux.conf which has the following
Code: label rock64-buildroot
kernel /boot/Image
devicetree /boot/rk3328-rock64.dtb
append console=ttyS2,1500000n8 root=/dev/mmcblk0p1 ro rootwait
This boots up and all is good. However, I'm wondering why I can't just replace /boot/Image and /boot/rk3328-rock64.dtb (and /lib/modules/*) with the one from slack (for example) and have that boot up.
When I tried, it didn't find /boot/Image and tried to boot off the network.
What am I missing here?
|
|
|
|
| Original factory Pinebook64 bsp recently not booting |
|
Posted by: Fox7799 - 11-10-2019, 08:25 AM - Forum: Ubuntu
- No Replies
|
|
My Pinebook with factory software that arrived Nov 5, 2018 has been working with no problem (except no hdmi out) but now it suddenly will not boot. The red light at the charging port is not coming on but it apparently is getting power because the green power light comes on when I plug it in. Is there an approved fix for this? Thanks
|
|
|
|
| NVME not detected |
|
Posted by: VoxUnius - 11-09-2019, 08:29 PM - Forum: Pinebook Pro Hardware and Accessories
- Replies (4)
|
 |
Guys, I've seen someone managed to get NVME working. My one doesn't work no matter what I do. I tried all possible OSes, checked the adapter in and out. No effect.
Does anyone know:
1. If it has to be a specific NVME card? My one is Samsung EVO 860, 250Gb.
2. If it's somehow related to the adapter problem? It thought the issue was only about the geometry and didn't affect functionality.
Cheers.
|
|
|
|
| Cannot power on the PBP |
|
Posted by: MC68060 - 11-09-2019, 01:20 PM - Forum: General Discussion on Pinebook Pro
- Replies (6)
|
|
Hi,
I just received my new Pinebook Pro today.
But I can not turn it on 
When I press the Power-Button most times nothings happens, sometimes the power-LED turns on for a quarter second and then it's off again.
I've tried with and without power-supply, read in the wiki about the emmc-switch and the SD-Card ribbon.
Tried both with no luck.
I tried also without battery and the power-brick cable connected, but also nothing.
Any suggestions?
|
|
|
|
Help: Keyboard and trackpad SPI update utility broke trackpad |
|
Posted by: User 11436 - 11-09-2019, 01:14 PM - Forum: Pinebook Pro Hardware and Accessories
- Replies (9)
|
|
Hi,
I ran ayufan's keyboard and trackpad SPI update utility (found here: https://github.com/ayufan-rock64/pineboo...rd-updater) I got the following error message:
Code: update pass
QObject: Cannot create children for a parent that is in a different thread.
(Parent is QApplication(0xfffbe9dc), parent's thread is QThread(0xab2ca308), current thread is QThread(0xec1201a8)
I'm still able to use the keyboard on the PBP, but the trackpad behaves as through one of the mouse buttons is being held down. Then after a couple of uses the cursor seizes in place. I've tried running it again but I get more or less the same error. I can work around it for now by plugging in a USB mouse.
Does anyone have any guidance on how to re-flash the SPI, or know when the keyboard/trackpad update utility will be fixed?
Ben
|
|
|
|
| Modkey + arrow keys not registered by xev |
|
Posted by: maldus - 11-09-2019, 11:43 AM - Forum: Linux on Pinebook Pro
- Replies (17)
|
|
Hello everyone,
Just started working with my new pbp, factory OS.
I'm trying to configure my window manager (awesomewm, but I believe the same problem applies on Mate as well) as I usually do. I like to move around windows and desktops by using combinations that involve the Mod4 key (the pine logo) and the arrow keys.
Unfortunately I've hit a brick wall; it seems that those particular key comps are not picked up at all. When running xev to test them nothing is displayed.
Clicking them separately works, of course.
A quick checkup with xmodmap shows me nothing unusual. What could be the issue? Is it possible to fix it?
|
|
|
|
|
