On 02/10/2015 06:31 AM, Dan Williams wrote:
On Thu, 2015-01-29 at 10:24 -0500, Jeremy Moles wrote:
On 01/28/2015 01:23 PM, Dan Williams wrote:
On Wed, 2015-01-28 at 11:43 -0500, Jeremy Moles wrote:
On 01/12/2015 12:50 PM, Dan Williams wrote:
On Mon, 2015-01-12 at 12:44 -0500, Jeremy Moles
On Thu, 2015-01-29 at 10:24 -0500, Jeremy Moles wrote:
On 01/28/2015 01:23 PM, Dan Williams wrote:
On Wed, 2015-01-28 at 11:43 -0500, Jeremy Moles wrote:
On 01/12/2015 12:50 PM, Dan Williams wrote:
On Mon, 2015-01-12 at 12:44 -0500, Jeremy Moles wrote:
On 01/12/2015 12:42 PM, Dan Williams
On 01/28/2015 01:23 PM, Dan Williams wrote:
On Wed, 2015-01-28 at 11:43 -0500, Jeremy Moles wrote:
On 01/12/2015 12:50 PM, Dan Williams wrote:
On Mon, 2015-01-12 at 12:44 -0500, Jeremy Moles wrote:
On 01/12/2015 12:42 PM, Dan Williams wrote:
On Mon, 2015-01-12 at 12:39 -0500, Jeremy Moles
On Thu, 2015-01-29 at 10:24 -0500, Jeremy Moles wrote:
On 01/28/2015 01:23 PM, Dan Williams wrote:
On Wed, 2015-01-28 at 11:43 -0500, Jeremy Moles wrote:
On 01/12/2015 12:50 PM, Dan Williams wrote:
On Mon, 2015-01-12 at 12:44 -0500, Jeremy Moles wrote:
On 01/12/2015 12:42 PM, Dan Williams
Dan Williams d...@redhat.com writes:
On Thu, 2015-01-29 at 10:24 -0500, Jeremy Moles wrote:
I'm working on testing this patch, but something else funny is
occurring. I can no longer actually query the device using qmicli
anymore under any condition... every attempt times out or returns:
On 01/12/2015 12:50 PM, Dan Williams wrote:
On Mon, 2015-01-12 at 12:44 -0500, Jeremy Moles wrote:
On 01/12/2015 12:42 PM, Dan Williams wrote:
On Mon, 2015-01-12 at 12:39 -0500, Jeremy Moles wrote:
On 01/12/2015 12:34 PM, Dan Williams wrote:
On Mon, 2015-01-12 at 11:04 -0500, Jeremy Moles
On Wed, 2015-01-28 at 11:43 -0500, Jeremy Moles wrote:
On 01/12/2015 12:50 PM, Dan Williams wrote:
On Mon, 2015-01-12 at 12:44 -0500, Jeremy Moles wrote:
On 01/12/2015 12:42 PM, Dan Williams wrote:
On Mon, 2015-01-12 at 12:39 -0500, Jeremy Moles wrote:
On 01/12/2015 12:34 PM, Dan Williams
Dan Williams d...@redhat.com writes:
State: LowPowerMode
LPM force flags - W_DISABLE:0, User:0, Temp:0, Volt:0, BIOS:1, GOBIIM:0
W_DISABLE: 0
Poweroff mode: 0
LPM Persistent: 0
This says that it's BIOS that is forcing the device to be in low power
mode. That means that the kernel rfkill
On Mon, 2015-01-12 at 10:12 -0500, Jeremy Moles wrote:
On 01/09/2015 02:24 PM, Dan Williams wrote:
On Fri, 2015-01-09 at 12:14 -0500, Jeremy Moles wrote:
On 01/09/2015 12:01 PM, Jeremy Moles wrote:
Hey everyone! I'm not entirely sure where else to ask this, and I'm
somewhat desperate at
On 01/12/2015 10:46 AM, Dan Williams wrote:
On Mon, 2015-01-12 at 10:12 -0500, Jeremy Moles wrote:
On 01/09/2015 02:24 PM, Dan Williams wrote:
On Fri, 2015-01-09 at 12:14 -0500, Jeremy Moles wrote:
On 01/09/2015 12:01 PM, Jeremy Moles wrote:
Hey everyone! I'm not entirely sure where else to
On 01/12/2015 12:42 PM, Dan Williams wrote:
On Mon, 2015-01-12 at 12:39 -0500, Jeremy Moles wrote:
On 01/12/2015 12:34 PM, Dan Williams wrote:
On Mon, 2015-01-12 at 11:04 -0500, Jeremy Moles wrote:
On 01/12/2015 10:46 AM, Dan Williams wrote:
On Mon, 2015-01-12 at 10:12 -0500, Jeremy Moles
On Mon, 2015-01-12 at 12:44 -0500, Jeremy Moles wrote:
On 01/12/2015 12:42 PM, Dan Williams wrote:
On Mon, 2015-01-12 at 12:39 -0500, Jeremy Moles wrote:
On 01/12/2015 12:34 PM, Dan Williams wrote:
On Mon, 2015-01-12 at 11:04 -0500, Jeremy Moles wrote:
On 01/12/2015 10:46 AM, Dan Williams
On Mon, 2015-01-12 at 11:04 -0500, Jeremy Moles wrote:
On 01/12/2015 10:46 AM, Dan Williams wrote:
On Mon, 2015-01-12 at 10:12 -0500, Jeremy Moles wrote:
On 01/09/2015 02:24 PM, Dan Williams wrote:
On Fri, 2015-01-09 at 12:14 -0500, Jeremy Moles wrote:
On 01/09/2015 12:01 PM, Jeremy Moles
On 01/12/2015 12:34 PM, Dan Williams wrote:
On Mon, 2015-01-12 at 11:04 -0500, Jeremy Moles wrote:
On 01/12/2015 10:46 AM, Dan Williams wrote:
On Mon, 2015-01-12 at 10:12 -0500, Jeremy Moles wrote:
On 01/09/2015 02:24 PM, Dan Williams wrote:
On Fri, 2015-01-09 at 12:14 -0500, Jeremy Moles
On Mon, 2015-01-12 at 12:39 -0500, Jeremy Moles wrote:
On 01/12/2015 12:34 PM, Dan Williams wrote:
On Mon, 2015-01-12 at 11:04 -0500, Jeremy Moles wrote:
On 01/12/2015 10:46 AM, Dan Williams wrote:
On Mon, 2015-01-12 at 10:12 -0500, Jeremy Moles wrote:
On 01/09/2015 02:24 PM, Dan Williams
On 01/09/2015 12:16 PM, Adam Tauno Williams wrote:
On Fri, 2015-01-09 at 12:01 -0500, Jeremy Moles wrote:
Hey everyone! I'm not entirely sure where else to ask this, and I'm
somewhat desperate at this point having tried everything I'm capable of.
We have a machine here with the card listed in
On Fri, 2015-01-09 at 12:14 -0500, Jeremy Moles wrote:
On 01/09/2015 12:01 PM, Jeremy Moles wrote:
Hey everyone! I'm not entirely sure where else to ask this, and I'm
somewhat desperate at this point having tried everything I'm capable of.
We have a machine here with the card listed in
Hey everyone! I'm not entirely sure where else to ask this, and I'm
somewhat desperate at this point having tried everything I'm capable of.
We have a machine here with the card listed in the subject. It shows up
in lsusb as:
1199:901f Sierra Wireless, Inc.
It will work in Linux so far
On Fri, 2015-01-09 at 12:01 -0500, Jeremy Moles wrote:
Hey everyone! I'm not entirely sure where else to ask this, and I'm
somewhat desperate at this point having tried everything I'm capable of.
We have a machine here with the card listed in the subject. It shows up
in lsusb as:
1199:901f
On 01/09/2015 12:01 PM, Jeremy Moles wrote:
Hey everyone! I'm not entirely sure where else to ask this, and I'm
somewhat desperate at this point having tried everything I'm capable of.
We have a machine here with the card listed in the subject. It shows
up in lsusb as:
1199:901f Sierra
20 matches
Mail list logo
