A true mainline Linux Kernel for the Pinebook Pro
you're welcome to try and fix nvme support in the upstream-ish uboot, contributions will be accepted Big Grin until that's done (or another bootloader pops up), it'll be a choice :/
I was suspecting that it's uboot...
As to the contributions - it's well beyond my competences unfortunately Sad
(01-31-2020, 05:06 AM)tsys Wrote: Hi @xmixahlx,

(01-30-2020, 11:44 AM)xmixahlx Wrote: regarding pinebook_pro_defconfig, please disable the new ARM erratum addition. if enabled the big cores won't come up. an interesting note: without the big cores i get a *970* octane2 score versus *10200* with!!! Smile

the BIG cores are online on my device with CONFIG_ARM64_ERRATUM_1319367=y. Tasks seem to be scheduled to them as well. Also corrupted TLBs don't sound particularly fun to me. Are you sure I should disable that option?

unexpected! so I built a kernel with this enabled and the two cores didn't come up, and specifically listed this erratum in error. rebuilding with the sole change of disabling the erratum brought the cores up. I AM using maxcpus=4 uboot option.

I used linaro arm 9.2 cross compiler on an amd64 system.

if this is working for you then the issue must be on my side. thoughts?
A recent systemd upgrade wanted to write into sysrq

Code:
Feb 06 21:41:55 manjaro systemd-sysctl[267929]: Couldn't write '16' to 'kernel/sysrq', ignoring: No such file or directory



@tsys, to make systemd happy, consider adding sysrq support into the default (manjaro) kernel


Code:
manjaro:~$ zgrep -i sysrq /proc/config.gz
# CONFIG_MAGIC_SYSRQ is not set
(02-06-2020, 11:59 PM)Der Geist der Maschine Wrote: A recent systemd upgrade wanted to write into sysrq

Code:
Feb 06 21:41:55 manjaro systemd-sysctl[267929]: Couldn't write '16' to 'kernel/sysrq', ignoring: No such file or directory



@tsys, to make systemd happy, consider adding sysrq support into the default (manjaro) kernel

Hm, agreed.  The magic sysrq is actually super helpful when debugging crashes, too. My defconfig has it enabled, Manjaro does not though. Will probably be fixed with the next release now.

(02-06-2020, 11:59 PM)Der Geist der Maschine Wrote:
Code:
manjaro:~$ zgrep -i sysrq /proc/config.gz
# CONFIG_MAGIC_SYSRQ is not set
Manjaro ARM

Kernel dev
Buy me a coffee
Hi,

I've a small update on headphone and speaker audio for all of you. https://gitlab.manjaro.org/tsys/linux-pinebook-pro does now feature control over the speaker amplifier and working headphone detection. Thus in tools like pavucontrol you can now select headphone output and actually have your speakers disabled.

Note that the kernel sound subsystem does not automatically disable the speakers when headphones are plugged in. However the headphone jack is exposed as an input device, thus an input daemon like acpid can be used for automatic switchover.
Manjaro ARM

Kernel dev
Buy me a coffee
@tsys excellent. thank you. I assume that the v5.5 branch has now merged with master? will the v5.5 branch continue separately?
(02-07-2020, 12:00 PM)xmixahlx Wrote: @tsys excellent. thank you. I assume that the v5.5 branch has now merged with master? will the v5.5 branch continue separately?

Yes, I might still push more experimental changes to the v5.5 branch. Only code I deem stable enough is pushed to the master branch
Manjaro ARM

Kernel dev
Buy me a coffee
perfect. thanks for the clarity. (and thank you!)
so an update on the ARM erratum 1319367 situation.

A> kernel 5.5 with 1319367 disabled and maxcpus4 = boots "normally"/quickly
B> kernel 5.5 with 1319367 enabled and maxcpus4 = boots "normally"/quickly, and big cores disabled
C> kernel 5.5 with 1319367 enabled and without maxcpus4 = boots "slowly", and big cores enabled (boot takes ~30sec longer)

i am using luks with password prompt

B> dmesg | grep CPU
Quote:[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: detected: ARM erratum 845719
[    0.000000] CPU features: detected: GIC system register CPU interface
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=6, Nodes=1
[    0.000000] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=6.
[    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x00000000fef00000
[    0.000000] GICv3: CPU0: using allocated LPI pending table @0x00000000ee450000
[    0.129847] smp: Bringing up secondary CPUs ...
[    0.210055] Detected VIPT I-cache on CPU1
[    0.210088] GICv3: CPU1: found redistributor 1 region 0:0x00000000fef20000
[    0.210102] GICv3: CPU1: using allocated LPI pending table @0x00000000ee460000
[    0.210146] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.290112] Detected VIPT I-cache on CPU2
[    0.290135] GICv3: CPU2: found redistributor 2 region 0:0x00000000fef40000
[    0.290146] GICv3: CPU2: using allocated LPI pending table @0x00000000ee470000
[    0.290174] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[    0.370202] Detected VIPT I-cache on CPU3
[    0.370225] GICv3: CPU3: found redistributor 3 region 0:0x00000000fef60000
[    0.370236] GICv3: CPU3: using allocated LPI pending table @0x00000000ee500000
[    0.370262] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[    0.370378] smp: Brought up 1 node, 4 CPUs
[    0.370391] CPU features: detected: 32-bit EL0 Support
[    0.370397] CPU features: detected: CRC32 instructions
[    0.387040] CPU: All CPU(s) started at EL2
[    1.069331] kvm [1]: GIC system register CPU interface enabled
[    2.003712] cacheinfo: Unable to detect cache hierarchy for CPU 0
[    2.505357] ledtrig-cpu: registered to indicate activity on CPUs
[   19.765698] CPU features: CPU4: Detected conflict for capability 48 (ARM erratum 1319367), System: 0, CPU: 1
[   19.765913] CPU4: will not boot
[   24.790850] CPU4: failed to come online
[   24.790873] psci: CPU4 killed (polled 0 ms)
[   24.790882] CPU4: died during early boot
[   24.817137] CPU features: CPU5: Detected conflict for capability 48 (ARM erratum 1319367), System: 0, CPU: 1
[   24.817147] CPU5: will not boot
[   29.830875] CPU5: failed to come online
[   29.830898] psci: CPU5 killed (polled 0 ms)
[   29.830907] CPU5: died during early boot

C> dmesg | grep CPU
Quote:[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: detected: ARM erratum 845719
[    0.000000] CPU features: detected: GIC system register CPU interface
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=6, Nodes=1
[    0.000000] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=6.
[    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x00000000fef00000
[    0.000000] GICv3: CPU0: using allocated LPI pending table @0x00000000ee450000
[    0.129845] smp: Bringing up secondary CPUs ...
[    0.210053] Detected VIPT I-cache on CPU1
[    0.210086] GICv3: CPU1: found redistributor 1 region 0:0x00000000fef20000
[    0.210100] GICv3: CPU1: using allocated LPI pending table @0x00000000ee460000
[    0.210143] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.290112] Detected VIPT I-cache on CPU2
[    0.290135] GICv3: CPU2: found redistributor 2 region 0:0x00000000fef40000
[    0.290146] GICv3: CPU2: using allocated LPI pending table @0x00000000ee470000
[    0.290173] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[    0.370198] Detected VIPT I-cache on CPU3
[    0.370221] GICv3: CPU3: found redistributor 3 region 0:0x00000000fef60000
[    0.370232] GICv3: CPU3: using allocated LPI pending table @0x00000000ee500000
[    0.370258] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[    0.453580] CPU features: detected: ARM erratum 1319367
[    0.453881] Detected PIPT I-cache on CPU4
[    0.455126] GICv3: CPU4: found redistributor 100 region 0:0x00000000fef80000
[    0.455581] GICv3: CPU4: using allocated LPI pending table @0x00000000ee510000
[    0.456820] CPU4: Booted secondary processor 0x0000000100 [0x410fd082]
[    0.542739] Detected PIPT I-cache on CPU5
[    0.543943] GICv3: CPU5: found redistributor 101 region 0:0x00000000fefa0000
[    0.544370] GICv3: CPU5: using allocated LPI pending table @0x00000000ee520000
[    0.545480] CPU5: Booted secondary processor 0x0000000101 [0x410fd082]
[    0.550967] smp: Brought up 1 node, 6 CPUs
[    0.551045] CPU features: detected: 32-bit EL0 Support
[    0.551070] CPU features: detected: CRC32 instructions
[    0.765585] CPU: All CPU(s) started at EL2
[   30.374026] kvm [1]: GIC system register CPU interface enabled
[   33.805600] cacheinfo: Unable to detect cache hierarchy for CPU 0
[   35.821491] cpufreq: cpufreq_online: CPU4: Running at unlisted freq: 12000 KHz
[   35.843470] cpufreq: cpufreq_online: CPU4: Unlisted initial frequency changed to: 408000 KHz
[   36.056860] ledtrig-cpu: registered to indicate activity on CPUs


Possibly Related Threads…
Thread Author Replies Views Last Post
  Debian on Pinebook Pro u974615 7 1,423 03-31-2024, 10:11 AM
Last Post: u974615
  Pinebook Pro upgrading from the factory image yamsoup 12 1,888 02-22-2024, 04:02 PM
Last Post: tllim
  Attempting to install Void Linux, boots into a black screen 9a3eedi 0 411 02-18-2024, 08:54 AM
Last Post: 9a3eedi
  Help installing Manjaro on eMMC of Pinebook Pro pine4546464 4 2,274 12-13-2023, 07:22 PM
Last Post: trillobite
  Need Help Recovering Manjaro /boot Contents on Pinebook Pro calinb 6 2,374 12-11-2023, 03:47 AM
Last Post: calinb
  Gentoo on Pinebook Pro RELEASE jannik2099 54 90,328 12-08-2023, 11:25 PM
Last Post: tllim
  Boot Order in Pinebook Pro food 8 1,412 11-23-2023, 07:37 AM
Last Post: KC9UDX
  How to mainline kernel on daniel thompson's debian installer? hellojack 14 7,711 09-07-2023, 09:38 PM
Last Post: Der Geist der Maschine
  PineBook Pro seems to go to deep sleep, but doesn't wake up pogo 11 5,578 08-31-2023, 04:20 PM
Last Post: TRS-80
  Would a Pinebook Pro be good for a Linux newbie? cassado10 6 1,596 08-08-2023, 04:58 AM
Last Post: moobythegoldensock

Forum Jump:


Users browsing this thread: 3 Guest(s)