TinaB
-
Posts
7 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by TinaB
-
-
It works with Bionic build. Is there a EOL date for the bionic builds (don't want to migrate soon)...
-
Hi, seems to have some issues with the installed java version:
Feb 28 20:11:19 homecontrol systemd[1]: openhab2.service: Service RestartSec=5s expired, scheduling restart. Feb 28 20:11:19 homecontrol systemd[1]: openhab2.service: Scheduled restart job, restart counter is at 2. Feb 28 20:11:19 homecontrol systemd[1]: Stopped openHAB 2 - empowering the smart home. Feb 28 20:11:19 homecontrol systemd[1]: Started openHAB 2 - empowering the smart home. Feb 28 20:11:20 homecontrol karaf[4965]: null Feb 28 20:11:20 homecontrol karaf[4965]: Error occurred shutting down framework: java.lang.NumberFormatException: null Feb 28 20:11:20 homecontrol karaf[4965]: java.lang.NumberFormatException: null Feb 28 20:11:20 homecontrol karaf[4965]: at java.lang.Integer.parseInt(Integer.java:542) Feb 28 20:11:20 homecontrol karaf[4965]: at java.lang.Integer.parseInt(Integer.java:615) Feb 28 20:11:20 homecontrol karaf[4965]: at org.apache.karaf.main.ConfigProperties.<init>(ConfigProperties.java:235) Feb 28 20:11:20 homecontrol karaf[4965]: at org.apache.karaf.main.Main.updateInstancePidAfterShutdown(Main.java:227) Feb 28 20:11:20 homecontrol karaf[4965]: at org.apache.karaf.main.Main.main(Main.java:192) Feb 28 20:11:20 homecontrol systemd[1]: openhab2.service: Main process exited, code=exited, status=254/n/a Feb 28 20:11:20 homecontrol systemd[1]: openhab2.service: Failed with result 'exit-code'.
I'm using a NanoPC-T4, Armbian buster with Linux 5.4.20-rockchip64
-
On 1/7/2020 at 8:09 AM, Igor said:
I tried yesterday - by the way - on kernel 5.4.y and a known to work wireless dongle (RT8811AU). AP starts with our tool at once ... which means there is some bug in the upstream driver code for the onboard wireless chip which we have no option to maintain.
Sorry for the late reply, didn't see the notification. Thank you for testing this. So now, how to report this issue (and to whom)?
-
Of course, here it is:
http://ix.io/26Bv -
Hi,
after solving the WIFI issue on my T4, i've tried to setup an AP. With the armbian-config it was pretty easy and i only changed the channel to 1 on for the g mode and the country_code on for n mode:
cat /etc/hostapd.conf # # armbian hostapd configuration example # # nl80211 mode # ssid=ARMBIAN interface=wlan0 hw_mode=g channel=1 #bridge=br0 driver=nl80211 logger_syslog=0 logger_syslog_level=0 wmm_enabled=1 wpa=2 preamble=1 wpa_psk=844418fea2e83eea256a88c751f2823c2d5e6d52193b27cfa34234e0d6de0ab9 wpa_passphrase=12345678 wpa_key_mgmt=WPA-PSK wpa_pairwise=TKIP rsn_pairwise=CCMP auth_algs=1 macaddr_acl=0 noscan=1 ## IEEE 802.11n ieee80211n=1 ht_capab=[DSSS_CK-40][HT20+] country_code=DE ieee80211d=1 ## IEEE 802.11n ## IEEE 802.11a hw_mode=a ## IEEE 802.11a ### IEEE 802.11ac #ieee80211ac=1 #vht_capab= #vht_oper_chwidth=1 #vht_oper_centr_freq_seg0_idx=42 ### IEEE 802.11ac # controlling enabled ctrl_interface=/var/run/hostapd ctrl_interface_group=0
The hostapd service is running and i don't see issues on the logs:
journalctl -u hostapd -b0 -- Logs begin at Mon 2020-01-06 16:17:56 CET, end at Mon 2020-01-06 16:21:57 CET. -- Jan 06 16:18:03 monitoring systemd[1]: Starting LSB: Advanced IEEE 802.11 management daemon... Jan 06 16:18:03 monitoring hostapd[2083]: Starting advanced IEEE 802.11 management: hostapd. Jan 06 16:18:03 monitoring systemd[1]: Started LSB: Advanced IEEE 802.11 management daemon.
journalctl -u NetworkManager -b0 -- Logs begin at Mon 2020-01-06 16:17:56 CET, end at Mon 2020-01-06 16:21:13 CET. -- Jan 06 16:17:59 monitoring systemd[1]: Starting Network Manager... Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.4818] NetworkManager (version 1.14.6) is starting... (for the first time) Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.4819] Read config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf, zz-override-wifi-powersave-off.conf) (etc: 10-ignore-in Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.4838] wifi-nl80211: (wlan0): using nl80211 for WiFi device control Jan 06 16:17:59 monitoring systemd[1]: Started Network Manager. Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.5048] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager" Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.5090] manager[0xaaaad8373030]: monitoring kernel firmware directory '/lib/firmware'. Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.5099] monitoring ifupdown state file '/run/network/ifstate'. Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8126] hostname: hostname: using hostnamed Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8127] hostname: hostname changed from (none) to "monitoring" Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8132] dns-mgr[0xaaaad837f130]: init: dns=default, rc-manager=file Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8145] rfkill0: found WiFi radio killswitch (at /sys/devices/platform/fe310000.dwmmc/mmc_host/mmc0/mmc0:0001/mmc0:0001:1/ieee80211/phy0/rfkill0) ( Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8149] manager[0xaaaad8373030]: rfkill: WiFi hardware radio set enabled Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8149] manager[0xaaaad8373030]: rfkill: WWAN hardware radio set enabled Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8926] ifupdown: interface-parser: parsing file /etc/network/interfaces Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8927] ifupdown: interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d/* Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8929] ifupdown: interface-parser: parsing file /etc/network/interfaces.d/armbian.ap.nat Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8930] ifupdown: interface-parser: finished parsing file /etc/network/interfaces.d/armbian.ap.nat Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8930] ifupdown: interface-parser: finished parsing file /etc/network/interfaces Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8972] ifupdown: guessed connection type (wlan0) = 802-3-ethernet Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8984] ifupdown: update_connection_setting_from_if_block: name:wlan0, type:802-3-ethernet, id:Ifupdown (wlan0), uuid: 5391eba4-6426-faca-338e-5828 Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9006] ifupdown: addresses count: 1 Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9007] ifupdown: No dns-nameserver configured in /etc/network/interfaces Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9012] ifupdown: management mode: managed Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9013] settings: Loaded settings plugin: SettingsPluginIfupdown ("/usr/lib/aarch64-linux-gnu/NetworkManager/1.14.6/libnm-settings-plugin-ifupdown. Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9014] settings: Loaded settings plugin: NMSKeyfilePlugin (internal) Jan 06 16:17:59 monitoring NetworkManager[844]: ((src/settings/nm-settings.c:899)): assertion '<dropped>' failed Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9113] keyfile: new connection /etc/NetworkManager/system-connections/Wired connection 1.nmconnection (4b7772f2-c308-3687-a691-24fb00771bdf,"Wired Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9165] manager: rfkill: WiFi enabled by radio killswitch; enabled by state file Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9169] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9172] manager: Networking is enabled by state file Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9178] dhcp-init: Using DHCP client 'dhclient' Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9311] Loaded device plugin: NMTeamFactory (/usr/lib/aarch64-linux-gnu/NetworkManager/1.14.6/libnm-device-plugin-team.so) Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9500] Loaded device plugin: NMBluezManager (/usr/lib/aarch64-linux-gnu/NetworkManager/1.14.6/libnm-device-plugin-bluetooth.so) Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9545] Loaded device plugin: NMWifiFactory (/usr/lib/aarch64-linux-gnu/NetworkManager/1.14.6/libnm-device-plugin-wifi.so) Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9573] Loaded device plugin: NMWwanFactory (/usr/lib/aarch64-linux-gnu/NetworkManager/1.14.6/libnm-device-plugin-wwan.so) Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9595] Loaded device plugin: NMAtmManager (/usr/lib/aarch64-linux-gnu/NetworkManager/1.14.6/libnm-device-plugin-adsl.so) Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9633] device (lo): carrier: link connected Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9647] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1) Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9738] manager: (dummy0): new Dummy device (/org/freedesktop/NetworkManager/Devices/2) Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9761] device (eth0): driver '(null)' does not support carrier detection. Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9778] device (eth0): driver 'rk_gmac-dwmac' does not support carrier detection. Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9805] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/3) Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9897] device (eth0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Jan 06 16:18:00 monitoring NetworkManager[844]: <info> [1578323880.0146] device (wlan0): driver supports Access Point (AP) mode Jan 06 16:18:00 monitoring NetworkManager[844]: <info> [1578323880.0158] manager: (wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/4) Jan 06 16:18:00 monitoring NetworkManager[844]: <info> [1578323880.0230] manager: NetworkManager state is now CONNECTED_GLOBAL Jan 06 16:18:00 monitoring NetworkManager[844]: <info> [1578323880.0610] supplicant: wpa_supplicant running Jan 06 16:18:00 monitoring NetworkManager[844]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed Jan 06 16:18:00 monitoring NetworkManager[844]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed Jan 06 16:18:00 monitoring NetworkManager[844]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed Jan 06 16:18:00 monitoring NetworkManager[844]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed Jan 06 16:18:00 monitoring NetworkManager[844]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed Jan 06 16:18:00 monitoring NetworkManager[844]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed Jan 06 16:18:00 monitoring NetworkManager[844]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed Jan 06 16:18:00 monitoring NetworkManager[844]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed Jan 06 16:18:00 monitoring NetworkManager[844]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed Jan 06 16:18:02 monitoring NetworkManager[844]: <info> [1578323882.8956] agent-manager: req[0xaaaad83dcb60, :1.51/org.freedesktop.nm-applet/1000]: agent registered Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.0734] device (eth0): carrier: link connected Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.0739] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed') Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.0753] policy: auto-activating connection 'Wired connection 1' (4b7772f2-c308-3687-a691-24fb00771bdf) Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.0774] device (eth0): Activation: starting connection 'Wired connection 1' (4b7772f2-c308-3687-a691-24fb00771bdf) Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.0776] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.0785] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.0794] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.0809] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.0862] dhcp4 (eth0): dhclient started with pid 2065 Jan 06 16:18:03 monitoring dhclient[2065]: DHCPREQUEST for 192.168.178.59 on eth0 to 255.255.255.255 port 67 Jan 06 16:18:03 monitoring dhclient[2065]: DHCPACK of 192.168.178.59 from 192.168.178.1 Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1639] dhcp4 (eth0): address 192.168.178.59 Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1644] dhcp4 (eth0): plen 24 (255.255.255.0) Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1647] dhcp4 (eth0): gateway 192.168.178.1 Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1651] dhcp4 (eth0): lease time 864000 Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1655] dhcp4 (eth0): nameserver '192.168.178.1' Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1658] dhcp4 (eth0): domain name 'fritz.box' Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1662] dhcp4 (eth0): state changed unknown -> bound Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1702] device (eth0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1739] device (eth0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1748] device (eth0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Jan 06 16:18:03 monitoring dhclient[2065]: bound to 192.168.178.59 -- renewal in 371156 seconds. Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1825] policy: set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1883] device (eth0): Activation: successful, device activated. Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1918] manager: startup complete Jan 06 16:18:05 monitoring NetworkManager[844]: <info> [1578323885.3641] dhcp6 (eth0): activation: beginning transaction (timeout in 45 seconds) Jan 06 16:18:05 monitoring NetworkManager[844]: <info> [1578323885.3766] dhcp6 (eth0): dhclient started with pid 2212 Jan 06 16:18:05 monitoring NetworkManager[844]: <info> [1578323885.3884] policy: set 'Wired connection 1' (eth0) as default for IPv6 routing and DNS Jan 06 16:18:06 monitoring dhclient[2212]: XMT: Confirm on eth0, interval 1090ms. Jan 06 16:18:06 monitoring dhclient[2212]: RCV: Reply message on eth0 from fe80::218:e7ff:fe8c:47ed. Jan 06 16:18:06 monitoring dhclient[2212]: message status code NotOnLink. Jan 06 16:18:06 monitoring dhclient[2212]: RCV: Reply message on eth0 from fe80::5e49:79ff:fecc:7966. Jan 06 16:18:06 monitoring dhclient[2212]: Packet received, but nothing done with it. Jan 06 16:18:06 monitoring dhclient[2212]: XMT: Solicit on eth0, interval 1070ms. Jan 06 16:18:06 monitoring dhclient[2212]: RCV: Advertise message on eth0 from fe80::5e49:79ff:fecc:7966. Jan 06 16:18:06 monitoring dhclient[2212]: RCV: Advertise message on eth0 from fe80::218:e7ff:fe8c:47ed. Jan 06 16:18:07 monitoring dhclient[2212]: XMT: Request on eth0, interval 1010ms. Jan 06 16:18:07 monitoring dhclient[2212]: RCV: Reply message on eth0 from fe80::218:e7ff:fe8c:47ed. Jan 06 16:18:07 monitoring NetworkManager[844]: <info> [1578323887.5159] dhcp6 (eth0): valid_lft 4294967295 Jan 06 16:18:07 monitoring NetworkManager[844]: <info> [1578323887.5160] dhcp6 (eth0): preferred_lft 4294967295 Jan 06 16:18:07 monitoring NetworkManager[844]: <info> [1578323887.5161] dhcp6 (eth0): address fd66:cf76:8fa7::89d Jan 06 16:18:07 monitoring NetworkManager[844]: <info> [1578323887.5161] dhcp6 (eth0): nameserver 'fd66:cf76:8fa7::1' Jan 06 16:18:07 monitoring NetworkManager[844]: <info> [1578323887.5162] dhcp6 (eth0): state changed unknown -> bound, event ID="a8:14:15:3c|1578323887" Jan 06 16:18:39 monitoring NetworkManager[844]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed Jan 06 16:18:39 monitoring NetworkManager[844]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed Jan 06 16:18:39 monitoring NetworkManager[844]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failedAlso the interface configuration looks goog to me:
ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether f6:36:7d:30:a5:ca brd ff:ff:ff:ff:ff:ff 3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 02:1d:a8:14:15:3c brd ff:ff:ff:ff:ff:ff inet 192.168.178.59/24 brd 192.168.178.255 scope global dynamic noprefixroute eth0 valid_lft 863861sec preferred_lft 863861sec inet6 fd66:cf76:8fa7::89d/128 scope global noprefixroute valid_lft forever preferred_lft forever inet6 2001:16b8:5066:1700:e81e:ea43:845c:cdcb/64 scope global dynamic noprefixroute valid_lft 7064sec preferred_lft 3464sec inet6 fd66:cf76:8fa7:0:26ab:de71:b182:c11b/64 scope global deprecated dynamic noprefixroute valid_lft 7064sec preferred_lft 0sec inet6 fe80::8a25:20f8:3eb5:f90/64 scope link noprefixroute valid_lft forever preferred_lft forever 4: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether cc:4b:73:5a:4c:cc brd ff:ff:ff:ff:ff:ff inet 172.24.1.1/24 brd 172.24.1.255 scope global wlan0 valid_lft forever preferred_lft foreverI've compared this configuration with some other tutorials and i don't see the issue why it's not working. If i scan the wifi no ARMBIAN is shown. Also configuring the WIFI manually don't lead to success (i just want to ensure that it isn't hidden). Any idea?
-
On 12/1/2019 at 1:54 PM, Hover said:
It seems on mainline kernel 5.3 & 5.4 the serdev bcm4356 driver is broken, while it worked on kernel 5.2. Anyone on nanopc t4 or m4 found the same problem?
I can confirm this, im using the latest version of buster desktop (2019-12-27) with 5.4 kernel and no wifi/bluetooth.
NanoPC-T4 and OV13850
in Rockchip
Posted
Hello,
i'm using the NanoPC-T4 with Armbian Bookworm (23.8.1 with Linux 6.1.63-current-media) Kernel and Mainsail/Klipper is running on in smooth and gently. Since i want to record timelapse videos, i've decided to buy the orginial "FriendlyELEC Cam1320 PI Camera Module" based on the OV13850. I've connected it in the expectation that it should work together. But the System is not detecting the camera module.
I found a project which contains patches for the camera module, is there any way to see if these patches are integrated in the armbian kernel? And if not, is it possible to add these patches or is there a way to build a custom kernel with these patches easily? Or am I looking at the wrong place?