June-15th-2021, 01:59 PM
I personally tried my netPI setup by activating the I2C-0 device which is normally not available. It is used to reach the EEPROM bus of HAT and NPIX in a container. So I added the line "dtparam=i2c_vc=on" to the config.txt file on RESC and I was immediately able to map the I2C-0 device into the container which worked. So editing this file works.
But now back to your problem. Of course the netPI OS includes the standard Linux network manager which is handling all the network interfaces and a kernel driver for Wifi/BT chip which is enabled by default. This driver has a fixed setup to initialize across the device "/dev/ttyAMA0". So I suspect this driver takes over the control of /dev/ttyAMA0 but fails cause due to your new config settings it can't reach the Wifi/BT chip ... but is still blocking this device for any other access. I could imaging that you can see some failures in the system logs after changing the ttyAMA0 setup. But for this scenario ... to be honest ... I have no solution how to disable the network manager or kernel driver in the netPI OS.
But now back to your problem. Of course the netPI OS includes the standard Linux network manager which is handling all the network interfaces and a kernel driver for Wifi/BT chip which is enabled by default. This driver has a fixed setup to initialize across the device "/dev/ttyAMA0". So I suspect this driver takes over the control of /dev/ttyAMA0 but fails cause due to your new config settings it can't reach the Wifi/BT chip ... but is still blocking this device for any other access. I could imaging that you can see some failures in the system logs after changing the ttyAMA0 setup. But for this scenario ... to be honest ... I have no solution how to disable the network manager or kernel driver in the netPI OS.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
