On 21/01/2017 10:21, Rick Stevens wrote:
On 01/20/2017 02:39 PM, Stephen Morris wrote:
On 20/01/2017 08:42, Rick Stevens wrote:
On 01/19/2017 12:40 PM, Stephen Morris wrote:
On 19/1/17 6:15 pm, Joe Zeff wrote:
On 01/18/2017 11:53 PM, Stephen Morris wrote:
I've checked the KEY_MGMT value and
On 01/20/2017 02:39 PM, Stephen Morris wrote:
> On 20/01/2017 08:42, Rick Stevens wrote:
>> On 01/19/2017 12:40 PM, Stephen Morris wrote:
>>> On 19/1/17 6:15 pm, Joe Zeff wrote:
On 01/18/2017 11:53 PM, Stephen Morris wrote:
> I've checked the KEY_MGMT value and it matches the entry in the
On 20/01/2017 08:42, Rick Stevens wrote:
On 01/19/2017 12:40 PM, Stephen Morris wrote:
On 19/1/17 6:15 pm, Joe Zeff wrote:
On 01/18/2017 11:53 PM, Stephen Morris wrote:
I've checked the KEY_MGMT value and it matches the entry in the
associated keys file.
I've also added the two WPA_ALLOW keys
On 01/19/2017 12:40 PM, Stephen Morris wrote:
> On 19/1/17 6:15 pm, Joe Zeff wrote:
>> On 01/18/2017 11:53 PM, Stephen Morris wrote:
>>> I've checked the KEY_MGMT value and it matches the entry in the
>>> associated keys file.
>>> I've also added the two WPA_ALLOW keys but they have made no differe
On 19/1/17 6:15 pm, Joe Zeff wrote:
On 01/18/2017 11:53 PM, Stephen Morris wrote:
I've checked the KEY_MGMT value and it matches the entry in the
associated keys file.
I've also added the two WPA_ALLOW keys but they have made no difference
to NM acknowledging that the device can be connected to.
On 01/18/2017 11:53 PM, Stephen Morris wrote:
I've checked the KEY_MGMT value and it matches the entry in the
associated keys file.
I've also added the two WPA_ALLOW keys but they have made no difference
to NM acknowledging that the device can be connected to.
Do you have any way of testing the
On 19/1/17 10:22 am, Rick Stevens wrote:
On 01/18/2017 01:21 PM, Stephen Morris wrote:
On 19/1/17 3:43 am, Rick Stevens wrote:
On 01/18/2017 01:54 AM, Stephen Morris wrote:
On 18/1/17 7:44 am, Terry Polzin wrote:
In my experience, you won't get any further than lsusb "seeing" the
device if yo
On 01/18/2017 01:21 PM, Stephen Morris wrote:
> On 19/1/17 3:43 am, Rick Stevens wrote:
>> On 01/18/2017 01:54 AM, Stephen Morris wrote:
>>> On 18/1/17 7:44 am, Terry Polzin wrote:
In my experience, you won't get any further than lsusb "seeing" the
device if you haven't the firmware. It
On 19/1/17 3:43 am, Rick Stevens wrote:
On 01/18/2017 01:54 AM, Stephen Morris wrote:
On 18/1/17 7:44 am, Terry Polzin wrote:
In my experience, you won't get any further than lsusb "seeing" the
device if you haven't the firmware. It may be blacklisted.
How do I determine if it or wifi has bee
On 01/18/2017 01:54 AM, Stephen Morris wrote:
> On 18/1/17 7:44 am, Terry Polzin wrote:
>> In my experience, you won't get any further than lsusb "seeing" the
>> device if you haven't the firmware. It may be blacklisted.
> How do I determine if it or wifi has been blacklisted? On reflecting on
> t
On 18/1/17 7:44 am, Terry Polzin wrote:
In my experience, you won't get any further than lsusb "seeing" the
device if you haven't the firmware. It may be blacklisted.
How do I determine if it or wifi has been blacklisted? On reflecting on
this issue there is a possibility that I may have manual
On 18/1/17 8:14 am, Rick Stevens wrote:
On 01/17/2017 01:12 PM, Stephen Morris wrote:
On 18/1/17 6:40 am, Rick Stevens wrote:
On 01/17/2017 12:12 PM, Stephen Morris wrote:
On 17/1/17 7:49 am, Rick Stevens wrote:
On 01/16/2017 12:22 PM, Joe Zeff wrote:
On 01/16/2017 12:17 PM, Stephen Morris w
On 01/17/2017 01:12 PM, Stephen Morris wrote:
> On 18/1/17 6:40 am, Rick Stevens wrote:
>> On 01/17/2017 12:12 PM, Stephen Morris wrote:
>>> On 17/1/17 7:49 am, Rick Stevens wrote:
On 01/16/2017 12:22 PM, Joe Zeff wrote:
> On 01/16/2017 12:17 PM, Stephen Morris wrote:
>> I am using kde
In my experience, you won't get any further than lsusb "seeing" the device
if you haven't the firmware. It may be blacklisted.
On Tue, Jan 17, 2017 at 4:20 PM, Stephen Morris
wrote:
> On 18/1/17 6:50 am, Terry Polzin wrote:
>
>> Is the device firmware getting loaded?
>>
> Thanks Terry. At the m
On 18/1/17 6:50 am, Terry Polzin wrote:
Is the device firmware getting loaded?
Thanks Terry. At the moment I'm not sure. This device used to work so I
am assuming the firmware is being loaded, but at the moment I'm not sure
if the firmware extensions package has been uninstalled for some reason
On 18/1/17 6:40 am, Rick Stevens wrote:
On 01/17/2017 12:12 PM, Stephen Morris wrote:
On 17/1/17 7:49 am, Rick Stevens wrote:
On 01/16/2017 12:22 PM, Joe Zeff wrote:
On 01/16/2017 12:17 PM, Stephen Morris wrote:
I am using kde at the moment and I have cut and pasted the wifi
password
back int
Is the device firmware getting loaded?
On Tue, Jan 17, 2017 at 3:38 PM, Stephen Morris
wrote:
> On 17/1/17 7:49 am, Rick Stevens wrote:
>
>> On 01/16/2017 12:22 PM, Joe Zeff wrote:
>>
>>> On 01/16/2017 12:17 PM, Stephen Morris wrote:
>>>
I am using kde at the moment and I have cut and paste
On 17/1/17 7:49 am, Rick Stevens wrote:
On 01/16/2017 12:22 PM, Joe Zeff wrote:
On 01/16/2017 12:17 PM, Stephen Morris wrote:
I am using kde at the moment and I have cut and pasted the wifi password
back into the Networkmanager definition, and had the new password stored
in Kwallet, but Network
On 01/16/2017 12:22 PM, Joe Zeff wrote:
> On 01/16/2017 12:17 PM, Stephen Morris wrote:
>> I am using kde at the moment and I have cut and pasted the wifi password
>> back into the Networkmanager definition, and had the new password stored
>> in Kwallet, but Networkmanager still refuses to recogniz
On 01/16/2017 12:17 PM, Stephen Morris wrote:
I am using kde at the moment and I have cut and pasted the wifi password
back into the Networkmanager definition, and had the new password stored
in Kwallet, but Networkmanager still refuses to recognize that the
device is a device it can connect to.
Hi,
Some time ago I was using this device on the 2.4GHz channel (Linux
has always refused to use the 5GHz channel, I say Linux, because Ubuntu
has always refused to use the 5GHz channel as Fedora has always refused
to) and when it was working it was via the ATH9K driver.
I switched t
21 matches
Mail list logo
