ams.br

  • Content Count

    5
  • Joined

  • Last visited

About ams.br

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. at a Linux OS (Armbian recommend Ubuntu), download the latest source of armbian build git clone https://github.com/armbian/build.git copy patch file arm_arch_timer.patch to folder userpatches/kernel/sunxi-next (more details in documentation). Run the compile script ./compile.sh choose "U-boot and kernel packages", apply. choose "Do not change the kernel configuration" for a standard kernel, or "Show a kernel configuration menu before compilation" for customize your kernel (recommended for advanced users), apply choose your board choose "next"
  2. After 14 days, the date remains stable. The patch apparently worked
  3. I compiled the kernel (branch next 4.19.y) applying a patch based in https://github.com/arctype-co/linux/commit/5fcb4e57eeaa4d670ef4acf5818c6fe16aa0d3d0 Strikes me as a more stable workaround, but I'm still evaluating. Patch: --- a/drivers/clocksource/arm_arch_timer.c +++ b/drivers/clocksource/arm_arch_timer.c @@ -328,16 +328,17 @@ * number of CPU cycles in 3 consecutive 24 MHz counter periods. */ #define __sun50i_a64_read_reg(reg) ({ \ - u64 _val; \ - int
  4. I switched to 5.3.0-rc3, but not work. After +/- 8 days. Welcome to Debian Stretch with Armbian Linux 5.3.0-rc3-sunxi64 System load: 0.82 0.73 0.70 Up time: 24855 days # date Sat Dec 16 19:19:42 -03 2209
  5. Hi, for me the problem persist. I'm using 5.2.5-sunxi64 dev 5.92. I've already try other, stable, next, dev. After some time it's jump to 2114. My board is a Orange Pi Win Plus (a64), others boards 32bit work normaly