Jump to content

cvxx

Members
  • Posts

    47
  • Joined

  • Last visited

Everything posted by cvxx

  1. Hi, on latest Armbian 23.11.1 Bookworm with PINE64 board I noticed those warnings in journal: Feb 12 10:00:45 pine64 systemd[1]: /lib/systemd/system/systemd-journal-upload.service:33: Unknown key name 'RestartSteps' in s> Feb 12 10:00:45 pine64 systemd[1]: /lib/systemd/system/systemd-journal-upload.service:34: Unknown key name 'RestartMaxDelaySec> I suspect the `systemd-journal-upload.service` is not in tact with systemd daemon version installed.
  2. Sorry for bumping, but I have just tried Armbian_23.02.2_Pine64_jammy_current_5.15.93.img and there is rpcbind started on boot and listening on all interfaces: root@pine64:~# netstat -atnp Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 694/rpcbind tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 695/systemd-resolve tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1426/sshd: /usr/sbi tcp6 0 0 :::111 :::* LISTEN 694/rpcbind tcp6 0 0 :::22 :::* LISTEN 1426/sshd: /usr/sbi I think this is a security risk
  3. added: console=both now I have a shell! Thanks!
  4. This is armbianEnv.txt: verbosity=1 bootlogo=false rootdev=UUID=30b36fce-65d1-44c4-bcec-3677c9fe01bd rootfstype=ext4
  5. No, I meant, on HDMI everything is ok, it boots and I can login. But the serial stays quiet
  6. Hi, when booting Armbian Sid minimal rolling 6.1.11, there is no serial console login. Console output: Found U-Boot script /boot/boot.scr 1993 bytes read in 146 ms (12.7 KiB/s) ## Executing script at 12000000 93 bytes read in 94 ms (0 Bytes/s) 38318 bytes read in 2603 ms (13.7 KiB/s) 33621022 bytes read in 3482 ms (9.2 MiB/s) 11215360 bytes read in 1257 ms (8.5 MiB/s) ## Loading init Ramdisk from Legacy Image at 14800000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 33620958 Bytes = 32.1 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 18000000 Booting using the fdt blob at 0x18000000 Using Device Tree in place at 18000000, end 1800c5ad Starting kernel ... Is there a way to enable console login to use the device headlessly? Thanks
  7. I haven't yet tried to build my own image, but I tested few other dongles. Surprisingly, `0cf3:9271 Qualcomm Atheros Communications AR9271 802.11n` also did not work because of missing firmware `htc_9271-1.4.0.fw`. So, I think that build has issues with not only missing RTL8188EUS.
  8. Flashed the latest Jammy 5.15.48 image and the device went offline After connecting to HDMI I found out that RTL8188EUS is no longer available. Previous Focal image worked fine in headless mode with a `0bda:8179` dongle. Anyone knows why the driver has been removed? Thanks
  9. I had to downgrade to last known working Armbian 20.05.1 Bionic version with this 8189fs module version: $ modinfo 8189fs filename: /lib/modules/5.4.43-sunxi/kernel/drivers/net/wireless/rtl8189fs/8189fs.ko version: v4.3.24.8_22657.20170607 author: Realtek Semiconductor Corp. description: Realtek Wireless Lan Driver license: GPL srcversion: 782ED5E387B69B8750A9E7F alias: sdio:c*v024CdF179* depends: cfg80211 intree: Y name: 8189fs vermagic: 5.4.43-sunxi SMP mod_unload ARMv7 thumb2 p2v8 Now all works fine like previously
  10. Hi, I have been running Armbian on OrangePi Lite for more than a year just fine. Then I decided to upgrade and flashed the latest version. Now with the latest version the device looses wifi every few days no matter which wifi device I use. In order to investigate I have plugged additional USB wifi. Some time both wifi work. Then built-in may disconnect and stop working, but USB keeps working. Or vice versa, USB stops working, but the built in keeps working. I have been able to send syslog to an external machine and here what it showed Connection works fine: The next day one of the connections stops working and complains that the WPA key may be wrong: Obviously, nothing has changed, the hotspot is still the same and WPA key has not been changed. Both wifi connections are using the same key, and one works fine. Rebooting resolves the issue, but after few days it is back again. Anyone have seen this behavior? Before downgrading to a version prior 2020 I'd like to check as much as possible if this is some bug Thanks
  11. UPDATE I have set up a fresh sd card to investigate and collect logs, but this time `ifupdown` worked Probably it was some typo I made in /etc/network/interfaces during setup Also, a note for future myself when I visit this thread again, there is a way to create the connection through `armbian_first_run.txt`. I tested and it worked. So, probably, better to switch to this way to have less conflicts between Network Manager and ifupdown
  12. The `ifupdown` method to connect a headless device no longer works with the latest Armbian 21.02.3. For some reason the interface remains down and requires manual `sudo ifup -v wlan0` `rc.local` does not start as there is root password change prompt blocking it Anyone knows what do I need to change to start wlan0 on boot? Or any other way to configure network on a device without HDMI? Thanks
  13. 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
  14. 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
  15. 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
  16. https://pastebin.com/AAvCYVkd Note that the script reports it's 26 C, but kernel reports different:
  17. 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
  18. 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
  19. 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 wlan0 restores the connection My question is: what is the correct way to put wifi configuration on the sd card of a headless Armbian installation? Thanks
  20. One more update I found that reloading the kernel module helps to restore wireless interface:
  21. 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 on the internet brought this issue with Raspberry Pi: https://github.com/raspberrypi/linux/issues/1988. Raspberry uses different wireless chipset either. All that makes me think this may be an issue in the kernel itself Any ideas or thoughts? Workaround also appreciated Thanks
  22. 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
  23. 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 tree My original dts "sun8i-h3-orangepi-lite.dts" looks like this: https://pastebin.com/6qUhWuTC Any ideas where to apply the patch?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines