Re: What do Network Manager / Network Messages Mean That are Shown at Boot Time

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux