On 08/02/2017 06:09, Ed Greshko wrote:
On 02/06/17 05:08, Stephen Morris wrote:
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).
You may want to try adding....
Before=network.target
Wants=network.target
To the Unit portion of the dkms.service file.
Hi Ed,
I've tried adding the two statements to the unit section of
dkms.service and they do cause dkms to run prior reaching
network.target, but they make no difference to the network being
available at boot time.
It seems to me that the issue is that Fedora is not providing
proper functionality on 802.11ac USB devices as evidenced by the
following situations:
* Network Manager Ethernet Definition set to "Onboot=yes", the network
is available at boot
* Network Manager 2.4GHz SSID Definition set to "Onboot=yes" and
restricted to the pci wifi device, the network is available at boot
* Network Manager 2.4GHz SSID Definition set to "Onboot=yes" and
restricted to the usb adapter device, the network is available at boot
* Network Manager 5GHz SSID Definition set to "Onboot=yes" and
restricted to the usb adapter device, the network is not available
at boot and is not available until the desktop actually starts
(unlike in Ubuntu where the same driver source code that is used in
Fedora, is compiled and installed into the kernel with DKMS, the
network is available at Display Manager start time)
What I'm not sure of at the moment is what I need to do to rectify
the situation.
regards,
Steve
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
