• Content Count

  • Joined

  • Last visited

About lampra

  • Rank
    Advanced Member

Recent Profile Visitors

1446 profile views
  1. I had a similar issue with similar output in dmesg on an H6 board Try param_w1_pin_int_pullup=1 In my case including a resistor solved the issue
  2. I tried today the recommended and test(03042021) images. The kernel booted, but I could not pass the password change using UART at 115200 (cu, bootterm, minicom) nor I could connect from ssh using Ethernet cable. I will try with a new sd card next week.
  3. Off-topic: Do we need to open a new thread (in general chit-chat maybe?) if we seek experiences from other forum members and not from the person who started the current thread?
  4. I am using apt proxy on opi pc 20.11.1 buster. Te proxy was working fine but now it gives error for only, not for debian repos. Err:2 buster InRelease 500 INTERNAL SERVER ERROR [IP: 8080] Any hint? Edit: https works
  5. Probably something you installed. Welcome to Armbian 20.11.6 Buster with Linux 5.10.4-sunxi Linux cubietruck 5.10.4-sunxi #20.11.7 SMP Tue Jan 5 23:17:54 CET 2021 armv7l System load: 8% Up time: 25 days 19:51 I had more or less similar crash issues with the previous version. I had to disable ram logging for a while to find out the issue. I also doubled my dev/zram1 97M 40M 51M 45% /var/log
  6. @Rötti Are you able to boot from the onboard SATA? (not from the extension card via MiniPCIe). I couldn't boot from SATA a year ago so I gave up and used openwrt but I would prefer using Armbian (I can't test newer releases as it is installed far away from home).
  7. If you scroll down the download section you will find the archives link. Some (v5.59 (2018-08-18) and later) previous images do exist there.
  8. Linux cubietruck 5.10.4-sunxi #20.11.6 SMP Sun Jan 3 21:28:45 CET 2021 armv7l GNU/Linux ------------[ cut here ]------------ [ 1.304783] WARNING: CPU: 0 PID: 1 at arch/arm/mm/ioremap.c:287 __arm_ioremap_pfn_caller+0x13f/0x14c [ 1.304791] Modules linked in: [ 1.304812] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.4-sunxi #20.11.6 [ 1.304818] Hardware name: Allwinner sun7i (A20) Family [ 1.304852] [<c010c9ed>] (unwind_backtrace) from [<c0109501>] (show_stack+0x11/0x14) [ 1.304873] [<c0109501>] (show_stack) from [<c0966dcb>] (dump_stac
  9. so this does not seem to be the issue for you
  10. I had the same issue but went away after upgrade to 20.11 Welcome to Armbian 20.11 Buster with Linux 5.8.16-sunxi Linux cubietruck 5.8.16-sunxi #20.08.14 SMP Tue Oct 20 22:15:32 CEST 2020 armv7l System load: 7% Up time: 5 days 23:38
  11. Can you provide the output of: df -h In my case /dev/zram0 was 50M and most of it was occupied. Probably because the installation was some years ago and since then I upgrade the system leaving all the logs from all the packages that I have installed. I had a freeze and I show in the journal errors due to full /dev/zram0 So I cleaned /var/log and /var/log.hdd from ancient logs and increased /dev/zram0 to 100M. It has been 5 days now that the system is up without issues. The load reported is probably a bug, if you upgrade to 20.11 its ok
  12. To my understanding zram is swap substitute. If you re-enable zram then you will have 1giga swap. Given that you had zram enabled during the first freeze I don't expect that this is a solution. Does Fhem ram usage increase overtime?
  13. In this case you can assume (not with certainty) that the issue is originating from fhem.service (same error logged twice before freeze). Reach out to the developers and report the issue. Then you could check if there was an update of fhem before the freezes started and downgrade if possible. At the same time you could check if scheduled periodic (eg. once a day or more) reboots may be used as a workaround until the main issue is resolved. PS: you can now re-enable zram and ram logging.
  14. It seems to me that this service is "eating" your memory. If you can live without it, you could stop it for some days as a test. Though I am not an expert.
  15. As I am not an expert, I can only see an out of memory issue in the messages. Maybe some expert could help further.