| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Irradium (based on crux l...
Forum: Linux on Pinebook
Last Post: mara
3 hours ago
» Replies: 3
» Views: 11,845
|
Danctnix USB GPS for Pine...
Forum: PineTab Software
Last Post: biketool
5 hours ago
» Replies: 0
» Views: 28
|
Pinetab2 camera drivers
Forum: PineTab Software
Last Post: biketool
7 hours ago
» Replies: 10
» Views: 6,775
|
what is the point?
Forum: General Discussion on PinePhone
Last Post: biketool
9 hours ago
» Replies: 4
» Views: 117
|
Old Danctnix server in Pa...
Forum: PineTab Software
Last Post: realchunkyflea
Yesterday, 05:01 PM
» Replies: 3
» Views: 262
|
PinePhone sensors - Gyros...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
Yesterday, 04:23 PM
» Replies: 2
» Views: 65
|
irradium (based on crux l...
Forum: Linux on Rock64
Last Post: mara
Yesterday, 10:30 AM
» Replies: 10
» Views: 15,924
|
irradium (based on crux l...
Forum: Linux on RockPro64
Last Post: mara
11-26-2025, 02:45 PM
» Replies: 10
» Views: 16,849
|
PinePhone, PinePhone Pro,...
Forum: PinePhone Hardware
Last Post: j_s
11-26-2025, 11:33 AM
» Replies: 4
» Views: 236
|
Quill OS for the PineNote
Forum: PineNote Software
Last Post: JhonSmith
11-26-2025, 01:42 AM
» Replies: 1
» Views: 150
|
|
|
| Tutorial: Run Debian off NVMe |
|
Posted by: hive - 10-18-2020, 03:20 PM - Forum: Pinebook Pro Tutorials
- Replies (4)
|
 |
Here are steps that worked for me, to get Debian to boot from NVMe on the PineBook Pro.
- Install NVMe adapter and NVMe drive
- Get the NVME device name --lsblk should list it, the actual device will be something like = /dev/nvme0n1
- Install Debian to the NVMe using this: https://github.com/daniel-thompson/pineb...-installer -- Note: The install failed with a hang (flashing amber-green) the first 2 times I tried it, and succeeded the 3rd time.
- Install an updated uboot that supports NVMe onto the SPI: https://github.com/pcm720/u-boot-build-s...v2020.07-1. (Note the boot order is microSD, eMMC, then NVMe, so if you want the PBP to boot from NVMe, you need to disable booting from the eMMC)
- Boot into manjaro on eMMC
- Disable booting from the eMMC (so the PBP will boot from the NVMe): Rename the /boot/extlinux folder on the eMMC e.g. sudo mv /boot/extlinux /boot/extlinux.dontboot (so the PBP will not boot off the eMMC)
- Reboot, and it should boot from NVMe
Note: if you want to go back to booting from eMMC, mount the 1st partition off eMMC--that is eMMC partition that would normally be mounted to /boot on Manjaro) and change the name from extlinux.dontboot (or whatever you used in step 6) back to extlinux and reboot
|
|
|
|
| Occasional boot |
|
Posted by: toiny - 10-18-2020, 01:41 PM - Forum: Getting Started
- No Replies
|
|
Bonjour,
This is my first post on a forum. I am good with computers, but not with Linux.
I bought a pinebook pro this week (4 october 2020) but i have alot of problems.
I am on majaro but my biggest problem is booting, it does not boot from a usb stick, it does not boot from a sd card.
99% of the time it does not boot on a emmca if not powered on 110 volt
90% of the time it does not boot from on emmca if usbC if not plugged
never boots on a sd card.
Never boots on a usb stick
Never boots on a usb3/usb hard drive
I have tried to burn with etcher, many different micro sd cards, even on usb stick
I saw the pine/utube video../. my swicth for booting was ok ... so what else could i try ...
Antoine
|
|
|
|
| Touchpad self generates events |
|
Posted by: jpalus - 10-18-2020, 11:38 AM - Forum: General Discussion on Pinebook Pro
- No Replies
|
|
I've noticed it a couple of times already after longer use of PBP: touchpad starts misbehaving like cursor is not moving correctly, spurious button clicks are made etc. Now that it happened again I've run xev moved cursor over the window and observed without touching touchpad. Small excerpt:
Code: ButtonPress event, serial 32, synthetic NO, window 0x2c00001,
root 0x22b, subw 0x0, time 31950669, (440,132), root:(1403,155),
state 0x0, button 1, same_screen YES
MotionNotify event, serial 32, synthetic NO, window 0x2c00001,
root 0x22b, subw 0x0, time 31952637, (440,133), root:(1403,156),
state 0x100, is_hint 0, same_screen YES
MotionNotify event, serial 32, synthetic NO, window 0x2c00001,
root 0x22b, subw 0x0, time 31952685, (440,133), root:(1403,156),
state 0x100, is_hint 0, same_screen YES
MotionNotify event, serial 32, synthetic NO, window 0x2c00001,
root 0x22b, subw 0x0, time 31952725, (440,134), root:(1403,157),
state 0x100, is_hint 0, same_screen YES
MotionNotify event, serial 32, synthetic NO, window 0x2c00001,
root 0x22b, subw 0x0, time 31953101, (440,134), root:(1403,157),
state 0x100, is_hint 0, same_screen YES
MotionNotify event, serial 32, synthetic NO, window 0x2c00001,
root 0x22b, subw 0x0, time 31953285, (440,134), root:(1403,157),
state 0x100, is_hint 0, same_screen YES
MotionNotify event, serial 32, synthetic NO, window 0x2c00001,
root 0x22b, subw 0x0, time 31953813, (440,134), root:(1403,157),
state 0x100, is_hint 0, same_screen YES
MotionNotify event, serial 32, synthetic NO, window 0x2c00001,
root 0x22b, subw 0x0, time 31953861, (439,134), root:(1402,157),
state 0x100, is_hint 0, same_screen YES
MotionNotify event, serial 32, synthetic NO, window 0x2c00001,
root 0x22b, subw 0x0, time 31953917, (439,134), root:(1402,157),
state 0x100, is_hint 0, same_screen YES
MotionNotify event, serial 32, synthetic NO, window 0x2c00001,
root 0x22b, subw 0x0, time 31953957, (439,135), root:(1402,158),
state 0x100, is_hint 0, same_screen YES
MotionNotify event, serial 32, synthetic NO, window 0x2c00001,
root 0x22b, subw 0x0, time 31953973, (439,135), root:(1402,158),
state 0x100, is_hint 0, same_screen YES
On average it's about 4 events a second, including micro motions by 1px, no motion at all (same coordinates) or button clicks -- it's actually extremely hard to type this comment now when it happens.
Anyone noticed similar thing? Any clue how to fix it?
|
|
|
|
Sound defaults to Headset |
|
Posted by: User 18618 - 10-18-2020, 10:03 AM - Forum: Mobian on PinePhone
- Replies (10)
|
|
The fix is listed in this reply.
Is there any way to prevent the Sound Output and Input resetting to using the Headset?
In earlier builds, the Sound would default to the Internal speaker and microphone, and route audio through the earpiece when making a call.
After an indeterminate upgrade, Output and Input persistently reset to the Headset - despite being changed in the Sound (Settings) menu, or pavucontrol.
|
|
|
|
| fan continously runs on kernel 5.8 but I need to use 5. kernel for PCIe sata card |
|
Posted by: GreyLinux - 10-18-2020, 09:19 AM - Forum: General Discussion on ROCKPRO64
- Replies (4)
|
|
Hi all
so I have an issue and i need to know the options available to me, so I have a Rockpro64 NAS case setup ,running Openmediavault on armbian buster wit kernel 4.4 and ats to control the fan .
My issue is that I get the same fault described in several of the thread regarding the PCIe card , my card fails under intense uploading mounts as read only then eventually remounts as a different drive. not ideal for a Nas. 
so I decided to get the marvel 88SE9230 PCIe sata card and I can confirm that binding the driver to the card using a udev rule does allows the card to be recognised,
as discussed in this thread here.
Quote:Code: root@rockpro64:~# nano /etc/udev/rules.d/99-marvell.rules
RUN+="/bin/bash -c 'echo 0000:01:00.0 > /sys/bus/pci/drivers/ahci/bind'"
however the drives are not discovered , so as others have said in other threads I changed to the latest available stable kernel 5.8.13 , success! the drives are discovered and I can successfully mount them.
However the problem I discovered is that all the kernels I tried on 5.(+) caused the fan to run continuously , I couldn't get ats to control it! and fresh image with 5.8 kernel on armbian bullseye , buster (upgraded to 5.8) or bionic with 5.8 would all have the fan running continuously.
so here in lies the problem what are my options?
A) do I have to either have the pcie card that doesn't result in a fault (marvell 88SE9230) and have the fan running constantly? , or have it disconnected ?
B) use the asmedia PCIe card with existing 4.4 kernel so at least I can control the fan but I cant use the card intensively.
C) reduce the sata link speed on the asmedia PCIe as patsnew mentioned in another thread and not use the card intensively.
Quote:You can also try reducing the SATA link speed using "libata.force=1.5G" or "libata.force=3G" in the kernel arguments. That seems to have fixed some intermittent problems with my ASMedia SATA card.
or do I have other options ? any advice you guys can give would be great.
|
|
|
|
|
