On 17/02/2017 08:04, Stephen Morris wrote:
On 16/02/2017 09:53, Rick Stevens wrote:
On 02/15/2017 01:27 PM, Stephen Morris wrote:
On 15/02/2017 04:42, Rick Stevens wrote:
On 02/13/2017 04:38 PM, Rick Stevens wrote:
On 02/13/2017 03:39 PM, Rick Stevens wrote:
On 02/13/2017 12:22 PM, Stephen M
On 16/02/2017 09:53, Rick Stevens wrote:
On 02/15/2017 01:27 PM, Stephen Morris wrote:
On 15/02/2017 04:42, Rick Stevens wrote:
On 02/13/2017 04:38 PM, Rick Stevens wrote:
On 02/13/2017 03:39 PM, Rick Stevens wrote:
On 02/13/2017 12:22 PM, Stephen Morris wrote:
On 13/02/2017 19:21, Stephen M
On 02/15/2017 01:27 PM, Stephen Morris wrote:
> On 15/02/2017 04:42, Rick Stevens wrote:
>> On 02/13/2017 04:38 PM, Rick Stevens wrote:
>>> On 02/13/2017 03:39 PM, Rick Stevens wrote:
On 02/13/2017 12:22 PM, Stephen Morris wrote:
> On 13/02/2017 19:21, Stephen Morris wrote:
> I've remo
On 15/02/2017 04:42, Rick Stevens wrote:
On 02/13/2017 04:38 PM, Rick Stevens wrote:
On 02/13/2017 03:39 PM, Rick Stevens wrote:
On 02/13/2017 12:22 PM, Stephen Morris wrote:
On 13/02/2017 19:21, Stephen Morris wrote:
I've removed the driver from DKMS in Ubuntu and re-added it, then run a
DKMS
On 02/13/2017 04:38 PM, Rick Stevens wrote:
> On 02/13/2017 03:39 PM, Rick Stevens wrote:
>> On 02/13/2017 12:22 PM, Stephen Morris wrote:
>>> On 13/02/2017 19:21, Stephen Morris wrote:
>>> I've removed the driver from DKMS in Ubuntu and re-added it, then run a
>>> DKMS AUTOINSTALL to rebuild and r
On 02/13/2017 03:39 PM, Rick Stevens wrote:
> On 02/13/2017 12:22 PM, Stephen Morris wrote:
>> On 13/02/2017 19:21, Stephen Morris wrote:
>> I've removed the driver from DKMS in Ubuntu and re-added it, then run a
>> DKMS AUTOINSTALL to rebuild and re-install the driver back into the
>> running kern
On 02/13/2017 12:22 PM, Stephen Morris wrote:
> On 13/02/2017 19:21, Stephen Morris wrote:
> I've removed the driver from DKMS in Ubuntu and re-added it, then run a
> DKMS AUTOINSTALL to rebuild and re-install the driver back into the
> running kernel and under Ubuntu the modprobe command to active
On 13/02/2017 19:21, Stephen Morris wrote:
On 13/02/2017 15:46, Ed Greshko wrote:
On 02/13/17 11:43, Ed Greshko wrote:
I have done some checking and have yet to determine why dkms feels the
need to rebuild the modules.
Does the module loading succeed on subsequent boots?
Well, my knowledge s
On 13/02/2017 15:46, Ed Greshko wrote:
On 02/13/17 11:43, Ed Greshko wrote:
I have done some checking and have yet to determine why dkms feels the
need to rebuild the modules.
Does the module loading succeed on subsequent boots?
Well, my knowledge seems "Out of Date".
Even though the additio
On 02/13/17 11:43, Ed Greshko wrote:
> I have done some checking and have yet to determine why dkms feels the
> need to rebuild the modules.
>
> Does the module loading succeed on subsequent boots?
Well, my knowledge seems "Out of Date".
Even though the additions install process mentions "dkms"
On 02/13/17 05:14, Stephen Morris wrote:
> To test out dkms compiling and installing my wifi driver I have
> uninstalled the driver from the kernel with dkms, removed the driver
> from dkms and re-added the driver to dkms.
>
> When I boot Fedora dkms compiles and installs the driver into t
Hi,
To test out dkms compiling and installing my wifi driver I have
uninstalled the driver from the kernel with dkms, removed the driver
from dkms and re-added the driver to dkms.
When I boot Fedora dkms compiles and installs the driver into the
kernel but it does not issue a modprob
12 matches
Mail list logo
