cvxx

  • Content Count

    34
  • Joined

  • Last visited

Everything posted by cvxx

  1. Hi, I have connected Orange Pi Lite over serial UART, but looks like the default settings are to not output the boot log to serial. You can only see U-Boot messages, then "Uncompressing Linux kernel" and after some time the login prompt comes. What exactly do I need to change/configure to get the classic kernel boot log to serial console? Thanks
  2. There was a critical vulnerability found in Realtek wireless drivers: The vulnerability has been assigned CVE-2019-17666 and a patch proposed: https://lkml.org/lkml/2019/10/16/1226 I would like to get some statement if Armbian users are affected and if yes when is the patch going to be released Thanks
  3. I am successfully using this cron script every 1 minute to detect wifi failure and reload the module: #!/bin/bash status=`/sbin/ifconfig wlan0 | grep "inet 192"` if [ ! -z "$status" ]; then exit 0; fi echo "Detected wifi failure" dmesg | grep __cfg80211_connect_result | mail -s "Wifi failure" root@localhost sudo rmmod 8189fs sudo modprobe 8189fs sleep 3 nmcli connection up id mynetworkname HTH
  4. https://pastebin.com/AAvCYVkd Note that the script reports it's 26 C, but kernel reports different:
  5. Hi, as it is quite hot now in Europe, one of my boards is experiencing overheat and shuts down automatically: Jun 25 16:52:27 localhost kernel: [74505.568246] thermal thermal_zone0: critical temperature reached (90 C), shutting down Who is initiating this shutdown? Is it possible to: 1. Change the temperature value that triggers the shutdown 2. Hook a script instead of direct shutdown so I can handle the overheat Thanks
  6. Thanks for the idea I found this solution to be more compatible: /etc/NetworkManager/NetworkManager.conf Source: https://wiki.debian.org/NetworkManager#Wired_Networks_are_Unmanaged
  7. Hi, I have few boards that were once connected to wifi manually, but now are headless. I would like now to upgrade Armbian and put wifi connection during sd card flash. Tried the classic way: /etc/network/interfaces When the board boots it connects to the wifi, I see few pings and then it goes offline After taking one of the boards for troubleshooting using serial console I found that NeworkManager starts right after the network is up and screws everything: Executing sudo ifdown wlan0 && sudo ifup -v wla
  8. One more update I found that reloading the kernel module helps to restore wireless interface:
  9. Hi, I have two OrangePi Lite running side by side. After working fine for about 8 months both started to experience same issue with wireless: The board works randomly for few hours or few days and then looses wireless connection. When this happens reboot does not help as then issue occurs immediately after the boot. Unplugging and replugging power source resolves that for a while and then happens again I suspect it may not be related to a hardware issue or wireless hotspot, as I have at least 3 other clients that continue to work fine. Searching for it
  10. I followed instruction of adding overlay at http://linux-sunxi.org/1-Wire This resulted in an error during boot and non functional 1-wire: Removing "#" comments from armbianEnv.txt resolved the issue Can you please confirm if comments are allowed in armbianEnv.txt? Thanks
  11. I don't have "sun8i-h3-nanopi-neo-air.dts" file, so I can't evaluate the patch. Same file from linux-sunxi repo looks far too small for the patch: https://github.com/linux-sunxi/linux-sunxi/blob/sunxi-next/arch/arm/boot/dts/sun8i-h3-nanopi-neo-air.dts Just appending same lines to my dts gives an error during compile: # dtc -I dts -O dtb test.dts > sun8i-h3-orangepi-lite-pathced.dtb Error: test.dts:1641.1-7 Label or path ehci0 not found Error: test.dts:1645.1-7 Label or path ohci0 not found Error: test.dts:1649.1-9 Label or path usb_otg not found FATAL ERROR: Syntax error parsing input
  12. Does 4.14 kernel support otg serial? If yes, how do I enable it?
  13. Oh, I forgot about the TTL onboard... Thanks, the board boots fine, I can log in through the serial connection
  14. Hi, I have flashed Armbian_5.35_Orangepilite_Ubuntu_xenial_default_3.4.113_desktop.img - and it works fine with my Orange Pi Lite v.1.1 But if I flash Armbian_5.38_Orangepilite_Debian_stretch_next_4.14.14.img which is aslo supported, the device does not boot. At least I get no output on HDMI, and no serial console over OTG. So I cannot check if it does not boot at all, or dies somewhere in the middle How can I check why it does not boot?
  15. Switched kernels. Total made 4 tests, here are my results so far: H - Hardkernel's A - Armbian's +---+--------+----------+--------+-----+ | 0 | Kernel | boot.ini | RootFS | 433 | +---+--------+----------+--------+-----+ | 1 | H | H | H | OK | | 2 | A | H | H | OK | | 3 | H | A | A | NO | | 4 | A | A | A | NO | +---+--------+----------+--------+-----+ So, the issue is caused by either boot.ini or root fs. Not easy to swap and test: both are very different boot.ini diff: ---
  16. Tested "performance" governor, tested same boot.ini params - didn't help Can I try to run Hardkernel's kernel on Armbian root file system? Is it enough just to replace uImage and modules dir to test this case?
  17. After more testing it looks like I have to put the sender close to the receiver, like few centimeters. Then it shows codes received. Previously, with Hardkernel's image it worked fine at the distance ~ 6 meters What could be the root cause? Some power limit on the pin? Cpu clock? Please, any suggestion to troubleshoot
  18. Hi, I was using Hardkernel's provided image for Odroid C1 and that was working fine. There is bunch of test sensors attached to gpio, like DHT22, BMP085, DS18B20 and 433 mhz receiver. Now I have tried to switch to Armbian and all the sensors keep working as they did, except 433 mhz receiver The RFSniffer I use is this one: https://github.com/ninjablocks/433Utils I changed WiringPI PIN to be used to "5": --- a/RPi_utils/RFSniffer.cpp +++ b/RPi_utils/RFSniffer.cpp @@ -22,7 +22,7 @@ int main(int argc, char *argv[]) { // This pin is not the first pin on th
  19. As most of boards are using wifi I wanted to confirm if KRACK vulnerability has been fixed in Armbian? https://www.krackattacks.com/
  20. Yes, I definitely connected to a wrong pin. Now all works. Thanks!
  21. Is "PH20" an equivalent of "GPIO-4"?
  22. I tried to follow your steps, but I still get these: Should it work on Armbian 5.25 and kernel 4.9.7 Feb 2 01:52:06 CET 2017?
  23. After some testing I found the same behavior with legacy kernel 3.4.113 The thing is that while "digitalRead" returns me "0", I execute "gpio readll" in a command line and I see that there pin's status is shown correctly - it is "1". Very weird and so far I have no idea how to troubleshoot such issue. All worked fine when my BananaPi was running Lubuntu 14.04 from Lemaker. Now, after upgrade to Armbian 16.04 this issue appeared. Really strange
  24. That worked after applying this patch: https://github.com/armbian/build/blob/master/extras/rtl8192cu.sh#L25-L50 Thanks