rossyduck

I have upgraded multiple RockPiS that were happily working - new version is Armbian 22.08.8 stable - but the latest version of Armbian-config no longer includes WiFi Access point creation/ management, and seems to disable the Access Point functionality. I am hoping this is an error that will be fixed - but if not, is there any way to downgrade the version of Armbian-Config - or turn the Access Point back on ?

I am trying to run AWS Greengrass IOT software on an Armbian based Rockpi (latest versions). At its simplest it runs ok using AWs corretto or Java 8. I am running into issue when i try load up a lamda to set up tunnels. I get the following errors from the log file. The issue seems to start because Resource controller is not enabled. Reading further and taking a stab in the dark - this could be referring to the following cgroup_enable=memory cgroup_memory=1 - apparently usually found in a cmdline.txt in the boot folder. Can anyone in the community help ? [INFO] (pool-2-thread-7) com.aws.greengrass.util.platforms.unix.linux.LinuxSystemResourceController: Resource controller is not enabled. {resource-controller=Memory, componentName=aws.greengrass.SecureTunneling} 2021-10-17T08:15:16.350Z [INFO] (pool-2-thread-7) com.aws.greengrass.util.platforms.unix.linux.LinuxSystemResourceController: Resource controller is not enabled. {resource-controller=CPU, componentName=aws.greengrass.SecureTunneling} 2021-10-17T08:15:23.400Z [INFO] (Copier) com.aws.greengrass.lifecyclemanager.GenericExternalService: Run script exited. {exitCode=1, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING} 2021-10-17T08:15:23.404Z [INFO] (Copier) com.aws.greengrass.lifecyclemanager.GenericExternalService: service-report-state. {serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING, newState=ERRORED} 2021-10-17T08:15:23.410Z [INFO] (aws.greengrass.SecureTunneling-lifecycle) com.aws.greengrass.lifecyclemanager.GenericExternalService: service-set-state. {serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING, newState=BROKEN} 2021-10-17T08:15:23.433Z [INFO] (aws.greengrass.SecureTunneling-lifecycle) com.aws.greengrass.status.FleetStatusService: fss-status-update-published. Status update published to FSS. {serviceName=FleetStatusService, currentState=RUNNING} 2021-10-17T08:15:23.449Z [INFO] (aws.greengrass.SecureTunneling-lifecycle) com.aws.greengrass.status.FleetStatusService: fss-status-update-published. Status update published to FSS. {serviceName=FleetStatusService, currentState=RUNNING} 2021-10-17T08:15:23.456Z [INFO] (pool-2-thread-7) com.aws.greengrass.lifecyclemanager.GenericExternalService: Shutdown initiated. {serviceName=aws.greengrass.SecureTunneling, currentState=BROKEN} 2021-10-17T08:15:23.459Z [INFO] (pool-2-thread-7) com.aws.greengrass.lifecyclemanager.GenericExternalService: generic-service-shutdown. {serviceName=aws.greengrass.SecureTunneling, currentState=BROKEN}

Still no fix for this. Holding back our project.

Using the 5.xx kernal I have been changing the eth0 MAC address at /etc/NetworkManager/system-connections/ 'Wired connection 1.nmconnection'. This has changed a bit as the versions progress - but version Armbian 21.08.2 Focal / Linux 5.14.5-rockchip64 has now moved the "wired ..." file to the /run/NetworkManager/system-connections/ and suspect the file is recreated at every boot (edits do not stick). I have tried to set MAC at /boot/armbianEnv.txt and in the eth config file. None work. Any ideas as to how to set the MAC address - and is it now even possible?.