lanefu Posted July 14, 2019 Posted July 14, 2019 47 minutes ago, guidol said: The compile did work again - BUT I had for the PC2 the same NetworkManager Error..... Also the new compiled image for NanoPi K1 Plus does have - for me - the NetworkManager Error Did you clean your cache and do ROOT_FS_CREATE_ONLY=force ? i did notice that when I did the ROOT_FS_CREATE_ONLY=force it stopped after making the FS, so then i ran again without and it picked up the FS
guidol Posted July 14, 2019 Posted July 14, 2019 3 minutes ago, lanefu said: Did you clean your cache and do ROOT_FS_CREATE_ONLY=force ? I did as igor wrote: ./compile CLEAN_LEVEL="cache"
lanefu Posted July 14, 2019 Posted July 14, 2019 (edited) 2 hours ago, guidol said: I did as igor wrote: ./compile CLEAN_LEVEL="cache" gotcha.. i should have said USE_TORRENT=false instead of ROOT_FS_CREATE_ONLY anyway i'm testing again myself. something went amiss Edited July 14, 2019 by lanefu ignore anythig I say.... lol :P
guidol Posted July 14, 2019 Posted July 14, 2019 3 hours ago, lanefu said: gotcha.. i should have said USE_TORRENT=false instead of ROOT_FS_CREATE_ONLY anyway i'm testing again myself. something went amiss I recompiled Armbian_5.91_Nanopik1plus_Debian_buster_next_4.19.57 while I had deleted the content of the dirctory cache/rootfs and the compile option USE_TORRENT=false but I also get the NetworkManager error BUT as interesting information: today I switched back from buster to stretch on my TVBox Sunvell T95K Pro (S912-CPU) - for getting rid of the errors with PiHole (PiHole doenst support buster completly - only debian 8/9) and while booting stretch I also did get the NetworkManager error on the following image from @balbes150 Armbian_5.84_Aml-s905_Debian_stretch_default_5.1.0-rc1_20190507.img So maybe it isnt buster... [EDIT] a freshly compiled Armbian_5.91_Odroidc2_Debian_stretch_next_4.19.59 also got no network-connection. I didnt see the NetworkManager error, but the network also did work after deconfiguring network-manager and using ifupdown.
guidol Posted July 15, 2019 Posted July 15, 2019 On 7/14/2019 at 1:34 PM, guidol said: The compile did work again - BUT I had for the PC2 the same NetworkManager Error..... Also the new compiled image for NanoPi K1 Plus does have - for me - the NetworkManager Error Since @igor created the new rootfs: The new compiled images doesnt have the NetworkManager error anymore. So clean/empty your rootfs-directory at ./build/cache/rootfs - while compiling the script will load the new one
Igor Posted July 15, 2019 Posted July 15, 2019 2 hours ago, guidol said: The new compiled images doesnt have the NetworkManager error anymore. Great. I am recompiling Buster images. Images must be v5.91 ->
Ireng Posted July 21, 2019 Author Posted July 21, 2019 Hi, many thanks for your valuable support and input ! However, I would like to add my 50 cents to the subject: Resolving the issue, I figured out, that DEBIAN renames the ETHERNET interface with some strange characters and numbers: I figured out the name of the LAN interface ip a added the information to /etc/network/interfaces, saved, rebooted and voila..... no more NetworkManager Error. I repeated the same procedure with the Armbian_5.90_Cubietruck_Debian_buster_next_4.19.57 image. However issuing ip a resulting into the interface name of eth0, as the old fashion and well known name. Adding to /etc/network/interfaces, saving and reboot resulted in a booting process without any Network Manager error. Does anybody know, which startup service is responsible in naming the Ethernet interface ? Anything wrong, why it does not add it "automatically" to /etc/network/interfaces, when the system starts up including a LAN cable plugged into the LAN Adapter ? Sorry, for late reply, I was very busy lately! Hope my input helps somewhat ! Best regards Ireng
Recommended Posts