ww9rivers

Members
  • Content Count

    9
  • Joined

  • Last visited

  1. No. I have not, since the stress test didn't show any problem with power supply. The workaround has kept the box up for 11 days now: $ uptime 04:42:34 up 11 days, 5:02, 9 users, load average: 0.21, 0.28, 0.28
  2. I have read two old threads in this forum: I have been running this (will post more details if needed) for a few days: VERSION=5.90 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS" NAME="Ubuntu" VERSION="18.04.3 LTS (Bionic Beaver)" Kernel is 4.19.62-sunxi The BPi would hang/freeze, seemingly randomly within a day or two. When it does that, there is no HDMI video or response to ping. After reading the first thread, I did stress test on the BPi for more than 2 days. The BPi actually hold up. So, next I ran "ping -i 30 -D 192.168.8.1" -- pinging my home gateway every 30 seconds. The BPi has also been up while that is going on. Now its uptime is more than 5 days. I have no problem keeping this going as a workaround -- just thought it may also be of interest to some one.
  3. Sorry it's been a while. Just wanted to say that Igor was right: The problem had been the SD card. I misunderstood the BPi's boot process, which actually attaches the BPi to the network and tries to boot off the network when the SD card doesn't work, which explains the activities on the network side. Once I attached to the UART serial console, it immediately became clear to me what was wrong. So thanks to Igor for the help.
  4. 1. Used different HDMI cables and different monitors; 2. Used different power supplies as well 3. Used different SD cards -- although not with the same image. The thing is, with the Armbian Bionic downloaded image, the BPi boots -- as I stated, I did see its IP address and it responded to pings. Just no HDMI video. Also, with all things equal, the old SD card still boots fine, with HDMI console. I guess I'll try serial console when I get back to it.
  5. Thank you very much for responding. What you said are what I had done, prior to coming here for help. I did not see anything specific in the documentation about HDMI or what could cause it to not function properly. I guess the option is to go to the serial console. I was hoping for a way to get HDMI video.
  6. My BPi M1 board is working fine, but the old bananalinux is no longer updating. So I downloaded Armbian Bionic mainline image as it is supported. However, after I boot it up, I get no HDMI video signal. I know that the BPi is working as I can see its IP address on my router and ping it. Any suggestions? Try a different image? Build my own? Thank you in advance for helping.
  7. Thank you again. I will try to remove the cache and try again. But it seems to have worked as I just ran "./compile.sh" without removing the cache:
  8. Thank you very much for responding. I am new to the build process. I just cloned the "build" repository from github, ran "compile.sh", and followed the menus popped up from there. My build environment is a Ubuntu 18.04.3 x86_64 VM with 12GB RAM. The log is attached. compilation.log
  9. Got an error message when trying to build an image for BPi-Pro: AR drivers/usb/built-in.a CC [M] drivers/net/wireless/rtl88x2bu/hal/phydm/phydm_rssi_monitor.o CC [M] drivers/net/wireless/rtl88x2bu/hal/phydm/phydm_auto_dbg.o CC [M] drivers/net/wireless/rtl88x2bu/hal/phydm/phydm_math_lib.o CC [M] drivers/net/wireless/rtl88x2bu/hal/phydm/phydm_api.o CC [M] drivers/net/wireless/rtl88x2bu/hal/phydm/phydm_pow_train.o CC [M] drivers/net/wireless/rtl88x2bu/hal/phydm/halrf/halrf.o CC [M] drivers/net/wireless/rtl88x2bu/hal/phydm/halrf/halphyrf_ce.o CC [M] drivers/net/wireless/rtl88x2bu/hal/phydm/halrf/halrf_powertracking_ce.o CC [M] drivers/net/wireless/rtl88x2bu/hal/phydm/halrf/halrf_powertracking.o CC [M] drivers/net/wireless/rtl88x2bu/hal/phydm/halrf/halrf_kfree.o CC [M] drivers/net/wireless/rtl88x2bu/hal/phydm/rtl8822b/halhwimg8822b_bb.o CC [M] drivers/net/wireless/rtl88x2bu/hal/phydm/rtl8822b/halhwimg8822b_mac.o CC [M] drivers/net/wireless/rtl88x2bu/hal/phydm/rtl8822b/halhwimg8822b_rf.o CC [M] drivers/net/wireless/rtl88x2bu/hal/phydm/halrf/rtl8822b/halrf_8822b.o CC [M] drivers/net/wireless/rtl88x2bu/hal/phydm/rtl8822b/phydm_hal_api8822b.o CC [M] drivers/net/wireless/rtl88x2bu/hal/phydm/halrf/rtl8822b/halrf_iqk_8822b.o CC [M] drivers/net/wireless/rtl88x2bu/hal/phydm/rtl8822b/phydm_regconfig8822b.o CC [M] drivers/net/wireless/rtl88x2bu/hal/phydm/rtl8822b/phydm_rtl8822b.o CC [M] drivers/net/wireless/rtl88x2bu/hal/phydm/txbf/haltxbf8822b.o CC [M] drivers/net/wireless/rtl88x2bu/hal/btc/halbtc8822bwifionly.o CC [M] drivers/net/wireless/rtl88x2bu/hal/btc/halbtc8822b1ant.o CC [M] drivers/net/wireless/rtl88x2bu/hal/btc/halbtc8822b2ant.o CC [M] drivers/net/wireless/rtl88x2bu/platform/platform_ops.o CC [M] drivers/net/wireless/rtl88x2bu/core/rtw_mp.o LD [M] drivers/net/wireless/rtl88x2bu/88x2bu.o AR drivers/net/wireless/built-in.a AR drivers/net/built-in.a Makefile:1083: recipe for target 'drivers' failed [ error ] ERROR in function compile_kernel [ compilation.sh:382 ] [ error ] Kernel was not built [ @host ] [ o.k. ] Process terminated I suppose that there are more logs somewhere?