| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Danctnix USB GPS for Pine...
Forum: PineTab Software
Last Post: biketool
33 minutes ago
» Replies: 0
» Views: 2
|
Pinetab2 camera drivers
Forum: PineTab Software
Last Post: biketool
3 hours ago
» Replies: 10
» Views: 6,766
|
what is the point?
Forum: General Discussion on PinePhone
Last Post: biketool
4 hours ago
» Replies: 4
» Views: 104
|
Old Danctnix server in Pa...
Forum: PineTab Software
Last Post: realchunkyflea
Yesterday, 05:01 PM
» Replies: 3
» Views: 255
|
PinePhone sensors - Gyros...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
Yesterday, 04:23 PM
» Replies: 2
» Views: 59
|
irradium (based on crux l...
Forum: Linux on Rock64
Last Post: mara
Yesterday, 10:30 AM
» Replies: 10
» Views: 15,923
|
irradium (based on crux l...
Forum: Linux on RockPro64
Last Post: mara
11-26-2025, 02:45 PM
» Replies: 10
» Views: 16,846
|
PinePhone, PinePhone Pro,...
Forum: PinePhone Hardware
Last Post: j_s
11-26-2025, 11:33 AM
» Replies: 4
» Views: 227
|
Quill OS for the PineNote
Forum: PineNote Software
Last Post: JhonSmith
11-26-2025, 01:42 AM
» Replies: 1
» Views: 137
|
auto-owning the SD card i...
Forum: PineTab Software
Last Post: biketool
11-25-2025, 04:16 AM
» Replies: 1
» Views: 407
|
|
|
| Downgrading packages on Manjaro ARM (on the example of boinc) |
|
Posted by: wrzomar - 10-02-2020, 12:20 PM - Forum: Pinebook Pro Tutorials
- No Replies
|
 |
There is a problem with boincmgr from the newest boinc package (7.16.9), it's impossible to add projects.
The solutions are:
- wait for update,
- use another boincmgr over network,
- downgrade boinc package.
In Arch Linux there is a way to downgrade a package installing a package (from cache or from Arch Linux Archive a.k.a ALA) and blocking its version in /etc/pacman.conf using IgnorePkg definition.
You can do it manually or using 'downgrade' script from AUR. The catch (on Manjaro ARM) is the downgrade script uses default ALA url (https://archive.archlinux.org/) and unless you have older versions of boinc in your cache, it fails to downgrade boinc package.
ARM packages are archived here: http://tardis.tiny-vps.com/aarm/
To downgrade boinc manually you have to:
1. Go to '/aarm/packages/b/boinc/' http://tardis.tiny-vps.com/aarm/packages/b/boinc/
2. Download tar.xz and tar.xz.sig files with older version of boinc (e.g. 7.16.7)
http://tardis.tiny-vps.com/aarm/packages...pkg.tar.xz
http://tardis.tiny-vps.com/aarm/packages...tar.xz.sig
3. Verify package with 'pacman-key --verify'
Code: pacman-key --verify boinc-7.16.7-1-aarch64.pkg.tar.xz.sig
Code: sudo pacman -U boinc-7.16.7-1-aarch64.pkg.tar.xz
Add
line to the /etc/pacman.conf and synchronize (you will have to close update icon before, I had to reboot for pamac-manager to block boinc updates):
The easier way is by downgrade script, you need to install it from AUR with pamac-manager or manually:
First install yay:
Then install downgrade:
Then you will need to "tell" downgrade script ALA url using its cli option:
Code: downgrade --ala-url http://tardis.tiny-vps.com/aarm/ boinc
Open ~/.bashrc with your favourite text editor and add line:
Code: alias downgrade-arm='downgrade --ala-url http://tardis.tiny-vps.com/aarm/'
Then you will be asked couple of questions, to choose version and to add IgnorePkg (the last one is only if package was not ignored already).
Downgrading packages in Manjaro is better explained here:
https://wiki.manjaro.org/index.php?title...g_packages
|
|
|
|
| Sluggish keyboard response since a few days |
|
Posted by: LinAdmin2 - 10-02-2020, 11:17 AM - Forum: Mobian on PinePhone
- No Replies
|
 |
When I started using mobian, the keyboard response (local and via sssh) was ok.
Now, after a few days of upgrades from SID, it has become very sluggish. On ssh (when system is idling) it may take a few seconds from a key-press until it gets displayed.
htop on ssh shows an avg. load of 3-7% (including htop itself) and nothing suspicious.
Do others have the same problem?
What can be done?
|
|
|
|
| XMonad on Manjaro: is anyone having success? |
|
Posted by: yashrk - 10-02-2020, 09:40 AM - Forum: Linux on Pinebook Pro
- No Replies
|
 |
Hi. I'm using Manjaro on PineBook Pro and I'm trying to install XMonad.
There is no official package for this WM, and packages from aur cannot be built (Haskell infrastructure for aarch64 in Manjaro seems broken at all).
I installed GHC and Cabal from Nix repository. I even had successfully built XMonad once, but it failed to recompile itself after an update.
I can now build XMonad binary using GHC from Nix, but it won't start because of different versions of glibc in the system and in the nix environment.
Have anyone a success in running XMonad in Arch? If so, what toolchain you used?
|
|
|
|
| Correct setup for u-boot and fstab ? Device not booting |
|
Posted by: as365n4 - 10-02-2020, 09:11 AM - Forum: Linux on Pine H64
- Replies (30)
|
|
I am trying to get Vanilla Debian up and running on the H64B.
I have build Arm-Trusted-Firmware and U-Boot from git/source and got the u-boot-sunxi-with-spl.bin file which I copied with "sudo dd if=u-boot-sunxi-with-spl.bin of=/dev/sdX bs=1024 seek=8" to my eMMC-Module.
My fstab is as below, with /boot flagged as bootable by fdisk.
/dev/mmcblk1p1 /boot ext2 defaults 0 2
/dev/mmcblk1p2 / ext4 errors=remount-ro 0 1
/dev/mmcblk1p3 swap swap defaults 0 0
Then powered up the H64B only shows that he has loaded u-boot and then stops/hangs and does not carry on to load Linux from /boot.
Am I missing something ???
Any adivce would be greatly appreciated.
I am tinkering with this for a while now and can't get past the U-Boot SPL prompt....
Here is that i am doing https://github.com/as365n4/Debian_on_Pin...neH64B.pdf
|
|
|
|
| Running Libgdx sdk on pinebookpro |
|
Posted by: Nick_dnepr - 10-02-2020, 07:49 AM - Forum: General Discussion on Pinebook Pro
- Replies (2)
|
|
Hey, guys, has anyone successfully launched libgdx sdk? I just wanted to try to do a bit of game development, but it just fails with
"wrong ELF class: ELFCLASS32"
I reckon the reason is 64 and 32 bit compatibility but i am not sure how to fix that. If anyone had encountered similar issue before please tell if is even possible to solve it.
Feel free to ask for any additional information
|
|
|
|
| Ubuntu 20.10 beta |
|
Posted by: Mangled - 10-02-2020, 06:14 AM - Forum: Linux on Pinebook Pro
- Replies (21)
|
|
Hi,
Would it be possible to upgrade from the pinebook Ubuntu 20.04 image to 20.10 beta? Does anyone run Ubuntu currently? Does the Ubuntu os work fine on pinebook?
|
|
|
|
| Shipping 1.2a - HDMi No Solder ? |
|
Posted by: bmsleight - 10-02-2020, 05:42 AM - Forum: PinePhone Hardware
- Replies (8)
|
|
Hello!
I am a middle of the road hacker and I am comfortable with early release hardware and software. However I can not solder, especially anything small - I lack the dexterity (even with a microscope)
I like to play with a PinePhone. To have Mobian running with the option, using a UBC-C cable/Hub to have HDMI output when needed.
https://wiki.pine64.org/index.php?title=...rdware_Fix
Concerned if I purchase today, my lack of soldering skills is an issue. Is pinephone purchase today 1.2a+ with this issue fixed ?
Thanks,
Brendan
|
|
|
|
| NVMe timeout when booting from eMMC but not SD |
|
Posted by: satwell - 10-01-2020, 09:49 PM - Forum: Linux on Pinebook Pro
- Replies (5)
|
|
I just got an NVMe adapter for my Pinebook Pro and have installed it with a Kingston A2000 250GB NVMe SSD. This is an SSD that others have reported success with on the wiki.
The boot process stalls for 60s and then I get a timeout error like this:
Code: [ 3.742566] nvme nvme0: pci function 0000:01:00.0
[ 3.742612] nvme 0000:01:00.0: enabling device (0000 -> 0002)
[ 64.480323] nvme nvme0: I/O 12 QID 0 timeout, disable controller
[ 64.600233] nvme nvme0: Device shutdown incomplete; abort shutdown
[ 64.640667] nvme nvme0: Identify Controller failed (881)
[ 64.641472] nvme nvme0: Removing after probe failure status: -5
And then it boots normally, but none of the /dev/nvme0* devices are available. This is on Debian Bullseye installed with Daniel Thompson's installer and kernel. Kernel 5.5 and 5.7 both have this same behavior.
Here's the weird part. I only have this problem booting from eMMC. If I boot from an SD card with basically the same Bullseye install and the same kernel, the NVMe drive works perfectly. So it doesn't seem to be bad hardware or a simple compatibility issue.
I'm a little stumped.
|
|
|
|
|
![[Image: jf5eE7s.png]](https://i.imgur.com/jf5eE7s.png)