sunzone

  • Content Count

    35
  • Joined

  • Last visited

About sunzone

  • Rank
    Advanced Member

Recent Profile Visitors

899 profile views
  1. I have observed kernel panics using xradio driver before. Check Opizero wifi kernel hang I decided to test it with this driver. Summary: No improvements Ap mode No kernel panics were observed during 1 day when running only on AP mode. However, when Orange Pi is rebooted in AP mode, kernel panic was observed. After running 5 Orange Pi devices, after 60 average reboots, Kernel panic occurred for all devices. [ 25.238909] xradio WSM-ERR: CMD timeout!>>> 0x0006 (16), buf_use=1, bh_state=0 [ 25.247990] xradio WSM-ERR: bh error!>>
  2. This issue exists on previous version
  3. I will look into that. Thanks. Edit: building Armbian with the CRYPTROOT_ENABLE option works
  4. Also tried with an Opi Zero Plus I had since it is 64bit, following the steps and also using the script. Boot hangs after Starting kernel ...
  5. 1) Checked 2) Applied Still the same error.. 1) Used automated script 2) Used Buster image Still the same error....
  6. Thanks for the post. I test the script with Orange Pi zero with the latest Ubuntu Focal image. Armbian 20.08.1 Focal with Linux 5.8.5-sunxi After writing to the SD, at booting phase, following error occurs. Starting kernel ... Uncompressing Linux... done, booting the kernel. Error: invalid dtb and unrecognized/unsupported machine ID r1=0x00001029, r2=0x40000100 r2[]=05 00 00 00 01 00 41 54 00 00 00 00 00 00 00 00 Available machine support: ID (hex) NAME ffffffff Generic DT based system ffffffff Allwinner suniv Family ffffffff Allwinner
  7. Unfortunately I gets the same "rcu_sched detected stalls on CPUs/tasks" error even with corrected "/etc/default/cpufrequtils" file 2020-08-06T13:30:01+09:00 10.8.2.182 CRON[14672]: pam_unix(cron:session): session opened for user root by (uid=0) 2020-08-06T13:30:01+09:00 10.8.2.182 CRON[14671]: pam_unix(cron:session): session opened for user root by (uid=0) 2020-08-06T13:30:01+09:00 10.8.2.182 CRON[14673]: (root) CMD (/root/logDasIpHealthInfo.sh) 2020-08-06T13:30:01+09:00 10.8.2.182 CRON[14674]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs) 2020-08-06T13:30:01+09:00 10.8.2.182 CRO
  8. I've seen some times OPi Zero crashing at 1.01GHz clock due to high heat. I recommend running it at 816MHz for stable usage.
  9. This is a known bug at speed test. Please refer: https://bugs.launchpad.net/ubuntu/+source/speedtest-cli/+bug/1828929 For testing, install speedtest-cli via pip. Don't use apt. speedtest-cli version installed with apt : 2.0.0(problem) speedtest-cli version installed with pip : 2.1.2(no problem) apt install python-pip -y pip install speedtest-cli for testing, speedtest-cli
  10. Just a follow up After changing the driver software some places and testing, without any in-depth understanding about this chip, I was not able to stop kernel hang on X-radio wifi driver. I noticed problems with xradio in 2 modes. 1) When using xradio in AP mode: kernel hang, reboot -f does not work 2) Using xradio in concurrent mode: kernel hang In either cases AP mode had the problem. I decided to stop using the xradio for good after all the testing. I stopped xradio module loading from boot: commented out 'xradio_wlan' from /et
  11. Hi. I am trying to control an i2c device at the u-boot stage. i2c 0 bus is activated through /boot/armbianEnv.txt file After settings some i2c commands at /boot/boot.cmd i checked the i2c sdk and sda pins via an oscilloscope. But neither output a signal. i2c dev 0 i2c mw 0x3c 0x00 0xae I included above commands and tested. Can I know how to activate or use i2c at u-boot level? image: ARMBIAN 5.75 stable Ubuntu 18.04.2 LTS 4.19.38-sunxi
  12. I was not familiar with IRC. However, I just asked about this problem on the #linux-sunxi channel. Let's see what replays I get. In the meantime, I wrote a program to reboot the system if a channel change is detected. But still, sometimes the device doesn't boot after calling 'reboot -f'. Another option is just to use a wifi dongle to work as the client interface. I already tried this. But then again, sometimes, the USB wifi module is not detected at the boot by the device; It has to be replugged again, which is not that ideal.
  13. Thanks, @Tido for the links. [20149.090066] [<bfb2d42d>] (wsm_handle_rx [xradio_wlan]) from [<bfb29e05>] (xradio_bh_exchange+0x27c/0x588 [xradio_wlan]) In the error logs, it seems program stalled on wsm_handle_rx in xradio_wlan. I found the official xradio_wlan driver to be fifteenhex http://linux-sunxi.org/Wifi I checked the fifteenhex wlan_driver code for "wsm_handle_rx" and found this line in wsm.c https://github.com/fifteenhex/xradio/blob/master/wsm.c It seems like kernel hang is done on purpose.
  14. ARMBIAN 5.75 stable Ubuntu 18.04.2 LTS 4.19.38-sunxi Orange Pi Zero Board Please refer armbianmonitor.log for armbianmonitor -U command output details I have configured My Orange Pi Zero onboard wlan chip (xradio_wlan driver) to work on both Ap mode and Client modes simultaneously. When both Ap and Client interfaces are up and working, and when the connected wifi channel of the Client interface changes, kernel hang occurs. Error message [20148.872296] rcu: INFO: rcu_sched self-detected stall on CPU [20148.877893] rcu: 1-....: (4945709 ticks this GP