On 10/02/2017 09:26, Ed Greshko wrote:
On 02/10/17 04:30, Stephen Morris wrote:
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 tim
On 02/10/17 04:30, Stephen Morris wrote:
> 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
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 th
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 th
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
> tol
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)
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
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
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 M
Hi,
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 an
10 matches
Mail list logo
