On 05/02/2017 11:39, Ed Greshko wrote:
On 02/05/17 09:30, Stephen Morris wrote:
What do the messages listed below, particularly the last two, which are listed in
boot.log, mean relative to ethernet and wifi network devices (I am assuming a wireless
mouse has no impact on this situation) that are configured in Network Manager to not be
connected to at boot time and definitions that are?
Starting Network Manager...
[ OK ] Started Network Manager.
Starting Network Manager Wait Online...
Starting Network Manager Script Dispatcher Service...
[ OK ] Started Network Manager Script Dispatcher Service.
[ OK ] Started Network Manager Wait Online.
Starting LSB: Bring up/down networking...
[ OK ] Started LSB: Bring up/down networking.
[ OK ] Reached target Network.
[ OK ] Reached target Network is Online.
I am particularly interested in whether the last two are produced because the
checking process successfully found usable devices that could be used for the network,
as opposed to devices that Network Manager has been told to connect to at boot, and if
it is the latter option how can the network be online when dkms has not finished
compiling and installing into the kernel the driver for the only device that Network
Manager has been told to connect to boot. I am assuming that the pci wireless device
that functions with an inbuilt kernel module (ATH9K) is not being network activated when
there isn't a definition for that device in Network Manager.
This may be of interest/value....
http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget
Thanks Ed, I have read this article and given the last of the above
messages indicates to me that Fedora is potentially not working
properly. Based on the write up you have indicated, the last message is
indicating that the network online service has been started because of
the network device mounts I have in /etc/fstab, and that all configured
devices are up and have an IP address. This explanation of what that
message means reinforces the question raised by this thread, how can all
configured devices be up and have an IP address when the driver for the
device I am using to provide network connectivity is still being built
and installed into the kernel by DKMS?
Having received the last message the first mount for the network device
is issued but that mount times out because the network is not actually
available, as the device seems to not be able to provide network
interfacing until the desktop is up, be that KDE or Gnome.
I have two interfaces on the USB adapter I am using, a 5Ghz interface
which is the one I am trying to use, and a 2.4Ghz interface. If I have
the 5Ghz interface configured with ONBOOT=yes and the 2.4Ghz interface
is configured with ONBOOT=no, the network interface is not available at
boot until the desktop is up whereby that desktop using the 5Ghz
interface for networking, but if I set ONBOOT=yes on the 2.4 Ghz
interface as well, then the network is available during boot and all the
network mounts all work correctly, but the desktop starts with the
2.4Ghz interface for networking and I have to manually switch to the
5Ghz interface.
I have raised another thread to deal with this network functionality
issue between the two interfaces.
regards,
Steve
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
