Networkmanager question
by pchristy from LinuxQuestions.org on (#6EWE4)
System: Pi 400 running slackwareaarch64-current
This is more of a general question rather than an issue. In addition to my Pi, I also have a few x86_64 machines, and there is a distinct difference in the way networkmanager behaves between the two.
On x86_64, the network connects during boot up, before the login screen appears. On the Pi, the network doesn't connect until a user logs in.
As far as I can tell, there is no difference between the configuration of the two systems - at least at an obvious, user accessible level.
Why is this a problem? Well, the Pi doesn't have a RTC, so until a network connection is established, the system time will be wrong. I have a local NAS which I use for updates, keeping a local copy of the systems I use (Slackware64-current, Slackwareaarch64-current and slarm64-current). In order for slackpkg(+) to update, it needs the time and date to be correct. Also, it needs the network to be connected.
On x86_64, I can boot straight into a command line environment and run the usual slackpkg commands to update my system as required. On the Pi, I have to log in as a user first in order to 1) establish a network connection and 2) get the correct system time. Then I have to kill the Xserver (ctl-alt-backspace), get back to a command line (ctl-alt-F1), login as root in order to update.
As I say, not a big problem, and I accept I am nit-picking here, but why does the Pi behave differently from x86_64 with the same network manager? Have I missed something in the configuration somewhere?
I appreciate that I could probably bypass this issue by bringing up the network the old fashioned way, without networkmanager. But one of the beauties of the Pi400 is its small size and portability, which makes moving it around easy. Networkmanager is so much more convenient.
Cheers,
--
Pete
This is more of a general question rather than an issue. In addition to my Pi, I also have a few x86_64 machines, and there is a distinct difference in the way networkmanager behaves between the two.
On x86_64, the network connects during boot up, before the login screen appears. On the Pi, the network doesn't connect until a user logs in.
As far as I can tell, there is no difference between the configuration of the two systems - at least at an obvious, user accessible level.
Why is this a problem? Well, the Pi doesn't have a RTC, so until a network connection is established, the system time will be wrong. I have a local NAS which I use for updates, keeping a local copy of the systems I use (Slackware64-current, Slackwareaarch64-current and slarm64-current). In order for slackpkg(+) to update, it needs the time and date to be correct. Also, it needs the network to be connected.
On x86_64, I can boot straight into a command line environment and run the usual slackpkg commands to update my system as required. On the Pi, I have to log in as a user first in order to 1) establish a network connection and 2) get the correct system time. Then I have to kill the Xserver (ctl-alt-backspace), get back to a command line (ctl-alt-F1), login as root in order to update.
As I say, not a big problem, and I accept I am nit-picking here, but why does the Pi behave differently from x86_64 with the same network manager? Have I missed something in the configuration somewhere?
I appreciate that I could probably bypass this issue by bringing up the network the old fashioned way, without networkmanager. But one of the beauties of the Pi400 is its small size and portability, which makes moving it around easy. Networkmanager is so much more convenient.
Cheers,
--
Pete