Re: Mount of NAS Ethernet Connect to Router Fails at Boot Time for CIFS Interface in F24
On Mon, Jan 16, 2017 at 12:36 PM, Stephen Morris wrote: > My Nas device now fails to mount at boot time via the CIFS definition in > fstab but the corresponding NFS definition mounts quite happily. Also after > the system comes up and I log into KDE I can manually mount the CIFS device. > As far as I am aware the only difference between when it was mounting at > boot time and now is several system updates, also the system update I did > yesterday morning (which updated several hundred packages, which included a > new kernel) has not rectified the issue. I've been curious about this, and I was able to replicate the problem shortly after you sent your email. I wasn't able to get any useful information beyond that, so I let it sit for a few days. Last night I thought I should try logging the state of the network interfaces and routes when systemd reached the "network-online" state, so I wrote a shell script and systemd unit to do that, and tested again. I'm no longer able to reproduce the problem. :( It's possible that some update in the last few days has fixed the issue, but I don't see anything that looks relevant. If it comes back, you should try logging the network state to try to get some idea of when NetworkManager and systemd consider the network to be online. My fstab entry was something like: //10.1.1.1/windows /mntcifs username=user1,password=**,rw 0 0 Note that "auto" is a default option and does not need to be specified, and _netdev is only needed for filesystems that refer to a block device which is backed by a network-available source (such as an iSCSI device). See the man page for systemd.mount for details. The unit and script are: $ cat /etc/systemd/system/iproute.service [Unit] Description=Log IP route after network is online Wants=network-online.target After=network-online.target [Service] Type=oneshot ExecStart=/usr/local/bin/iproute-log [Install] WantedBy=multi-user.target $ cat /usr/local/bin/iproute-log #!/bin/sh logger "addr at network-online" /usr/sbin/ip addr show | logger logger "route at network-online" /usr/sbin/ip route show | logger ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Networkmanager Will not Start the Network at Boot Time on 5Ghz Channel on USB Wifi Adapter
On 05/02/2017 00:28, poma wrote: ping Sorry, I'm a little confused by what this response means? regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: What do Network Manager / Network Messages Mean That are Shown at Boot Time
On 05/02/2017 14:30, Ed Greshko wrote: On 02/05/17 09:30, Stephen Morris wrote: 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. One other thing, which may not be relevant to your current situation but I thought I'd mention. I've not had the need to use dkms lately. However, it was my understanding that the kernel modules for newly installed kernels are built at the time the new kernel is installed. This being triggered by /etc/kernel/postinst.d/dkms script being called. However, if it is done anything like the akmods process you have to wait a while before rebooting as there may be no indication the modules are being rebuilt in the background after the install of the latest kernel. Hi Ed, From what I've read, DKMS will compile the driver after a new kernel is installed if the right parameter is supplied on the make command it has been told to use. At boot time DKMS will run and check if the source modules it has been told to build and install have been added to the running kernel and if not it will undertake those actions. The situation that prompted this mail was where to test the auto build functionality in DKMS I forced the boot time building. I've checked the /etc/kernel/postinst.d/dkms script and I'm not sure its working properly (I will need to check what the autoinstaller is doing). It seems to me that the autoinstaller is being run against the kernel identified by $kern_inst, which without knowing what Fedora is doing, I would have assumed is set to the name of the running kernel, which if I am correct it seems that DKMS is building the specified module against the newly installed kernel headers and installing into the new kernel (this is if the make parameter that identifies the kernel version to build against is specified, which in my case is specified in dkms.conf). regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: What do Network Manager / Network Messages Mean That are Shown at Boot Time
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@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Dummy audio and no Wifi after upgrading to f25
no it did not - Original Message - > The newer kernels didn't work? Current F25 kernel is 4.9.6. > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
