linux-pinephone issueshttps://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephone/-/issues2023-03-20T03:30:43Zhttps://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephone/-/issues/20[PinePhone (OG) & (Pro) Thermals] Set lower default thermal trip / throttling...2023-03-20T03:30:43ZJan Jasper de Kroon[PinePhone (OG) & (Pro) Thermals] Set lower default thermal trip / throttling points.Currently we do not have a thermal management engine (yet) for the PinePhone/PinePhone Pro.<br>
There's something in the works, but that's still far from ready.<br>
To prevent devices from running quite hot during (even under normal load...Currently we do not have a thermal management engine (yet) for the PinePhone/PinePhone Pro.<br>
There's something in the works, but that's still far from ready.<br>
To prevent devices from running quite hot during (even under normal load conditions) it's better to lower the current default thermal trip points for the cpu.<br>
This makes thermal throttling of the cpu kick in much earlier, and prevents the phone from becoming a pocket heater.<br>
Current thermal trip points which are used quite often are (45/55/70), which seem quite good.<br>
With these settings phone doesn't feel as hot anymore as before, maybe even comparable to a modern android device.<br>
The thermal trip points can be altered (patched) in the kernel ".dtsi" files, but it's also possible to use a script to lower the defaults at boot time.<br>
Easiest way to do this, is by using SystemD's own tmpfiles.d daemon.<br>
It's a temporary solution after all until a proper thermal management engine has been finished.<p>
If you create a file **/etc/tmpfiles.d/throttling.conf**, with the following contents:<br>
`w /sys/class/thermal/thermal_zone0/trip_point_0_temp - - - - 45000`<br>
`w /sys/class/thermal/thermal_zone0/trip_point_1_temp - - - - 55000`<br>
`w /sys/class/thermal/thermal_zone0/trip_point_2_temp - - - - 70000`<br>
Please let me know what you think of it.<br>
This request also applies to the PinePhone Pro Edition, which also benefits from having these set-points lowered.<br>
Due to earlier thermal throttling also battery life will be improved somewhat, ofcourse due to the fact it down-clocks earlier.<br>
In normal day-to-day use this isn't noticeable, only maybe on very cpu intensive tasks.<br>https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephone/-/issues/19Problem to add interface to firewalld zone2023-06-01T20:23:13ZhobbitusProblem to add interface to firewalld zoneIt is not possible to add an interface to firewalld zone.
For example:
`sudo firewall-cmd --zone=internal --add-interface=eth0`
`Error: COMMAND_FAILED: 'python-nftables' failed:`
`JSON blob:`
`{"nftables": [{"metainfo": {"json_sche...It is not possible to add an interface to firewalld zone.
For example:
`sudo firewall-cmd --zone=internal --add-interface=eth0`
`Error: COMMAND_FAILED: 'python-nftables' failed:`
`JSON blob:`
`{"nftables": [{"metainfo": {"json_schema_version": 1}}, {"add": {"rule": {"family": "inet", "table": "firewalld", "chain": "filter_IN_internal", "index": 6, "expr": [{"match": {"left": {"meta": {"key": "l4proto"}}, "op": "==", "right": {"set": ["icmp", "icmpv6"]}}}, {"accept": null}]}}}, {"insert": {"rule": {"family": "inet", "table": "firewalld", "chain": "filter_INPUT_ZONES", "expr": [{"match": {"left": {"meta": {"key": "iifname"}}, "op": "==", "right": "eth0"}}, {"goto": {"target": "filter_IN_internal"}}]}}}, {"insert": {"rule": {"family": "inet", "table": "firewalld", "chain": "nat_POSTROUTING_ZONES", "expr": [{"match": {"left": {"meta": {"key": "oifname"}}, "op": "==", "right": "eth0"}}, {"goto": {"target": "nat_POST_internal"}}]}}}, {"insert": {"rule": {"family": "inet", "table": "firewalld", "chain": "filter_FORWARD_ZONES", "expr": [{"match": {"left": {"meta": {"key": "iifname"}}, "op": "==", "right": "eth0"}}, {"goto": {"target": "filter_FWD_internal"}}]}}}, {"insert": {"rule": {"family": "inet", "table": "firewalld", "chain": "nat_PREROUTING_ZONES", "expr": [{"match": {"left": {"meta": {"key": "iifname"}}, "op": "==", "right": "eth0"}}, {"goto": {"target": "nat_PRE_internal"}}]}}}, {"insert": {"rule": {"family": "inet", "table": "firewalld", "chain": "mangle_PREROUTING_ZONES", "expr": [{"match": {"left": {"meta": {"key": "iifname"}}, "op": "==", "right": "eth0"}}, {"goto": {"target": "mangle_PRE_internal"}}]}}}, {"add": {"rule": {"family": "inet", "table": "firewalld", "chain": "filter_FWD_internal_allow", "expr": [{"match": {"left": {"meta": {"key": "oifname"}}, "op": "==", "right": "eth0"}}, {"accept": null}]}}}]}`
It is not possible to add inteface with nmcli either (`sudo nmcli connection modify Wired01 connection.zone internal`)
confirmation:
`sudo firewall-cmd --info-zone=internal`
`internal`
`target: default`
`icmp-block-inversion: no`
`interfaces:`
`sources:`
`services: dhcpv6-client mdns samba-client ssh`
`ports:`
`protocols:`
`forward: yes`
`masquerade: no`
`forward-ports:`
`source-ports:`
`icmp-blocks:`
`rich rules:`
on PinePhone (`Linux hostname 5.18.0-1-MANJARO-ARM #1 SMP PREEMPT Sat May 28 21:06:18 UTC 2022 aarch64 GNU/Linux`) with:
`nftables 1:1.0.2-1`
`networkmanager 1.34.0-1`
`firewalld 1.1.1-1`
`python 3.10.4-1`https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephone/-/issues/18[Feature Request] Suggest CONFIG_NR_CPUS to be set to 4 (actual nr CPUs in Pi...2022-05-10T07:49:55ZJan Jasper de Kroon[Feature Request] Suggest CONFIG_NR_CPUS to be set to 4 (actual nr CPUs in PinePhone OG)@philm or @Strit
This is not really a bug, but rather a small optimization related setting<br>
Currently it's set at 64, but the PinePhone OG only has 4 cpus available<br>
Setting this parameter doesn't really improve kernel performance...@philm or @Strit
This is not really a bug, but rather a small optimization related setting<br>
Currently it's set at 64, but the PinePhone OG only has 4 cpus available<br>
Setting this parameter doesn't really improve kernel performance very much, but improves kernel image size some more<br>
This setting reserves 8KB per CPU set, which in our case is 64, so it reserves 512KB of space in total<br>
As we only have 4 CPUs available 480KB is wasted each kernel build and needs to be loaded in memory at boottime<br>
Let me know what you think about it.
Greetings Jasperhttps://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephone/-/issues/16DT: Indicator LED max_brightness not correct2022-04-06T13:33:32ZAndreas HartmannDT: Indicator LED max_brightness not correctHi everyone,
today I decided to find out why the indicator LED on the pinephone acts so weird in that it is solid on most of the time and then briefly turns off. The activity pattern should be a blinking with a 50% duty cycle.
It turns...Hi everyone,
today I decided to find out why the indicator LED on the pinephone acts so weird in that it is solid on most of the time and then briefly turns off. The activity pattern should be a blinking with a 50% duty cycle.
It turns out that the `max_brightness` property of the LEDs is set to 255, where really it should be 1 because since the LEDs are controlled by GPIO they can only differ between two states (on/off). Patch `0105-leds-gpio-make-max_brightness-configurable.patch` already correctly introduced the driver changes needed to read the max-brightness from the DT, but the DT itself hasn't been adapted.
Here's a proposal to make the LEDs work as they should:
```
--- a/sun50i-a64-pinephone.dtsi
+++ b/sun50i-a64-pinephone.dtsi
@@ -327,6 +327,7 @@
color = <LED_COLOR_ID_BLUE>;
gpios = <&pio 3 20 GPIO_ACTIVE_HIGH>; /* PD20 */
retain-state-suspended;
+ max-brightness = <1>;
};
led-1 {
@@ -334,6 +335,7 @@
color = <LED_COLOR_ID_GREEN>;
gpios = <&pio 3 18 GPIO_ACTIVE_HIGH>; /* PD18 */
retain-state-suspended;
+ max-brightness = <1>;
};
led-2 {
@@ -341,6 +343,7 @@
color = <LED_COLOR_ID_RED>;
gpios = <&pio 3 19 GPIO_ACTIVE_HIGH>; /* PD19 */
retain-state-suspended;
+ max-brightness = <1>;
};
};
```
I'd send a proper PR but this Gitlab instance won't let me fork the project... :/https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephone/-/issues/15FR: Add support for encryption2022-01-28T16:37:13ZHarmFR: Add support for encryptionWhen I add the `encrypt` hook to `/etc/mkinitcpio.conf` and run `sudo mkinitcpio -P` it prints this:
```
-> Running build hook: [encrypt]
==> ERROR: module not found: `dm_integrity'
```
Does that mean the `dm_integrity` module is not...When I add the `encrypt` hook to `/etc/mkinitcpio.conf` and run `sudo mkinitcpio -P` it prints this:
```
-> Running build hook: [encrypt]
==> ERROR: module not found: `dm_integrity'
```
Does that mean the `dm_integrity` module is not present in the kernel?
`uname -a` prints `Linux manjaro-arm 5.16.2-1-MANJARO-ARM #1 SMP PREEMPT Thu Jan 20 14:59:31 UTC 2022 aarch64 GNU/Linux`https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephone/-/issues/14The RTC jumps to year 21162021-11-28T09:56:39ZpizdjukThe RTC jumps to year 2116Happens 1 time on 1-2 days, and pretty annoying. The logs from journalctl attached.
[timeshift-journal.log](/uploads/10b0ec79accc3ab87462d65c09bb7c93/timeshift-journal.log)Happens 1 time on 1-2 days, and pretty annoying. The logs from journalctl attached.
[timeshift-journal.log](/uploads/10b0ec79accc3ab87462d65c09bb7c93/timeshift-journal.log)https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephone/-/issues/13Broken iptables and bridges in 5.14.14-22021-11-28T09:55:40ZpizdjukBroken iptables and bridges in 5.14.14-2Since the last update waydroid dont get the network anymore. The reason is that in a newer kernel the module ip_tables is absent. Moreover, bridges dont wokr too.Since the last update waydroid dont get the network anymore. The reason is that in a newer kernel the module ip_tables is absent. Moreover, bridges dont wokr too.https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephone/-/issues/11Enable snd_seq2021-12-09T02:10:14ZGeorge OliverEnable snd_seqMusic tools such as fluidsynth require snd_seq, which currently is not included. For example,
```
> FluidSynth runtime version 2.1.8
> Copyright (C) 2000-2021 Peter Hanappe and others.
> Distributed under the LGPL license.
> SoundFont(R...Music tools such as fluidsynth require snd_seq, which currently is not included. For example,
```
> FluidSynth runtime version 2.1.8
> Copyright (C) 2000-2021 Peter Hanappe and others.
> Distributed under the LGPL license.
> SoundFont(R) is a registered trademark of E-mu Systems, Inc.
>
> Parameter 'chpn_op10_e01.mid' not a SoundFont or MIDI file or error occurred identifying it.
> ALSA lib seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory
> fluidsynth: error: Error opening ALSA sequencer
> Failed to create the MIDI thread; no MIDI input
```
Also see https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/37
and https://github.com/dreemurrs-embedded/Pine64-Arch/commit/a1d107605b80669bd63477eeaa86b70499471ad7https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephone/-/issues/9Enable joydev module2021-08-25T22:38:57ZDidroleEnable joydev moduleI play games on my device, unfortunately `CONFIG_INPUT_JOYDEV` is not set, which prevents me from using a gamepad.
May I suggest to enable `CONFIG_INPUT_JOYDEV` ?
(`CONFIG_HID_SONY`, `CONFIG_SONY_FF` would also be awesome but I can l...I play games on my device, unfortunately `CONFIG_INPUT_JOYDEV` is not set, which prevents me from using a gamepad.
May I suggest to enable `CONFIG_INPUT_JOYDEV` ?
(`CONFIG_HID_SONY`, `CONFIG_SONY_FF` would also be awesome but I can live without it)https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephone/-/issues/8enable USB tethering2022-01-05T11:41:16ZLadislav Nesneraenable USB tetheringHave a look at [Plasma's issue](https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/plasma-mobile/-/issues/128), please.Have a look at [Plasma's issue](https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/plasma-mobile/-/issues/128), please.https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephone/-/issues/5PKGBUILD issues2021-05-22T08:52:36ZaaazPKGBUILD issuesThe way the PKGBUILD is written, it interactively asks for config, which is unidiomatic and confusing for users/developers. I've been building with `yes '' | makepkg`, but it's not clear whether this is how the package as distributed is ...The way the PKGBUILD is written, it interactively asks for config, which is unidiomatic and confusing for users/developers. I've been building with `yes '' | makepkg`, but it's not clear whether this is how the package as distributed is built.
In addition, running `makepkg` multiple times fails, because patching is not idempotent--`patch` will fail when trying to create already-existing files:
```
-> Applying patch: 0002-dts-add-pinetab-dev-old-display-panel.patch...
patching file arch/arm64/boot/dts/allwinner/Makefile
Hunk #1 succeeded at 13 with fuzz 1 (offset -2 lines).
The next patch would create the file arch/arm64/boot/dts/allwinner/sun50i-a64-pinetab-dev.dts,
which already exists! Skipping patch.
1 out of 1 hunk ignored
```
This can be circumvented by using `makepkg -e --noprepare` for subsequent invocations, but really it would be better to fix the `PKGBUILD`.https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephone/-/issues/3Suggestion: Enable NFSD2021-12-11T16:48:23ZN00byKingSuggestion: Enable NFSDHello,
I'd love if NFSD was built as part of the Kernel. (CONFIG_NFSD=y/m).
At the Moment, starting a NFS Server fails due to the config not being set. (At least that's what I got from some googlin')
Thanks!Hello,
I'd love if NFSD was built as part of the Kernel. (CONFIG_NFSD=y/m).
At the Moment, starting a NFS Server fails due to the config not being set. (At least that's what I got from some googlin')
Thanks!https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephone/-/issues/2Contribution workflow2020-11-10T12:54:06ZaaazContribution workflowFirst, sorry for creating an issue about a meta topic, but I really can't figure out the intended workflow for contribution here.
I wanted to submit a patch that changes the package url from the upstream kernel url to this repository's ...First, sorry for creating an issue about a meta topic, but I really can't figure out the intended workflow for contribution here.
I wanted to submit a patch that changes the package url from the upstream kernel url to this repository's location so that it's easier to contribute to and see history of the additional patches and kernel config used.
I couldn't edit the PKGBUILD with the web UI (it suggested to fork and submit a subsequent MR), so I clicked the presented fork button, only to receive the following error:
```
Fork Error!
You tried to fork manjaro-arm / packages / core / linux-pinephone but it failed for the following reason:
– Namespace is not valid
```
So I tried to clone the project to gitlab.com and work there, then submit a MR back to Manjaro's gitlab.
The first half of this plan went fine (https://gitlab.com/aaaz/linux-pinephone), but I can't find a way to submit a merge request on this repository.
Sorry for the trouble, and thanks for your help.