Joe Zeff:
> Indeed. At one point, I was doing senior tech support for an
> ISP. One day I got a call from a customer who was having connection
> issues with his ADSL, and the description made it sound like line
> noise. After asking some questions, I learned that the cable from
> the phone soc
Allegedly, on or about 7 October 2017, George N. White III sent:
> Don't ignore battery terminals, and don't use abrasives (which many
> erasers contain), as they will damage metal plating. At one time,
> carbon tetrachloride was used for cleaning contacts. These days
> there are much safer des
On 7 October 2017 at 16:59, fred roller wrote:
> You mentioned having this mouse for awhile. Used to have similar issues
> and something to try (low tech) is to clean the connections. An eraser or
> equivalent will do if you can get to the connectors on the dongle.
> Sometimes the connections g
You mentioned having this mouse for awhile. Used to have similar issues
and something to try (low tech) is to clean the connections. An eraser or
equivalent will do if you can get to the connectors on the dongle.
Sometimes the connections get a micro build up on them and a mild
non-residual abras
Joe Zeff ha scritto il 07/10/2017 alle 00:05:
On 10/06/2017 02:54 PM, Rick Stevens wrote:
Yeah. As a hardware engineer that has, over many years, transitioned to
a software engineer, I always assume my software is buggy. I can't
believe how often it turns out it's hardware like a bad cable or
so
On 10/06/2017 04:46 PM, Rick Stevens wrote:
> On 10/06/2017 04:18 PM, Tom Horsley wrote:
>> In my experience, hardware deliberately waits till
>> the worst possible time to break. For instance: You've
>> just loaded a new operating system, and suddenly
>> nothing works right. Because the hardware k
On 10/06/2017 04:18 PM, Tom Horsley wrote:
> In my experience, hardware deliberately waits till
> the worst possible time to break. For instance: You've
> just loaded a new operating system, and suddenly
> nothing works right. Because the hardware knows
> you'll be sure the new OS is the problem, i
In my experience, hardware deliberately waits till
the worst possible time to break. For instance: You've
just loaded a new operating system, and suddenly
nothing works right. Because the hardware knows
you'll be sure the new OS is the problem, it chooses
that precise moment to break.
I have seen
On 10/06/2017 03:26 PM, George N. White III wrote:
Cables and connections were always a problem area for hardware; now we
need to think about whether problems are due to RF "interference", which
could be a too strong RF signal from some other device, or poorly
designed hardware that is not reje
On 6 October 2017 at 17:23, Joe Zeff wrote:
> On 10/06/2017 12:54 PM, Samuel Sieb wrote:
>
>>
>> He sent me the log directly and I've included the relevant lines below.
>> It definitely looks like a hardware problem. It keeps disconnecting,
>> maybe some connection inside is loose.
>>
>
> I woul
On 10/06/2017 03:05 PM, Joe Zeff wrote:
> On 10/06/2017 02:54 PM, Rick Stevens wrote:
>> Yeah. As a hardware engineer that has, over many years, transitioned to
>> a software engineer, I always assume my software is buggy. I can't
>> believe how often it turns out it's hardware like a bad cable or
On 10/06/2017 02:54 PM, Rick Stevens wrote:
Yeah. As a hardware engineer that has, over many years, transitioned to
a software engineer, I always assume my software is buggy. I can't
believe how often it turns out it's hardware like a bad cable or
something. My rule of thumb is "If it always happ
On 10/06/2017 01:23 PM, Joe Zeff wrote:
> On 10/06/2017 12:54 PM, Samuel Sieb wrote:
>>
>> He sent me the log directly and I've included the relevant lines below.
>> It definitely looks like a hardware problem. It keeps disconnecting,
>> maybe some connection inside is loose.
>
> I wouldn't be su
On 10/06/2017 12:54 PM, Samuel Sieb wrote:
He sent me the log directly and I've included the relevant lines below.
It definitely looks like a hardware problem. It keeps disconnecting,
maybe some connection inside is loose.
I wouldn't be surprised. I can remember, back in the '80s, when many
On 10/05/2017 02:09 PM, Antonio M wrote:
I have the log (tnx for help anyway) from 20:00:00 and forward: but the
full log is 225 lines and I suppose that I cannot load here..
He sent me the log directly and I've included the relevant lines below.
It definitely looks like a hardware problem. It
I had similar sounding problems with a bluetooth mouse, turns out that
the power management was shutting it down. Take a look at tlp or
powertop if you are using them, and see if you can put a powerdown
exception for your dongle.
On Thu, Oct 5, 2017 at 3:12 PM, Antonio M wrote:
> sometimes I loo
On Thu, 2017-10-05 at 22:00 +0200, Antonio M wrote:
> battery is new . Anyway for a long time I had no issue with this port and
> it started short ago after upgrading recent kernels.
>
> No idea how to debug it. (this port is the high-power port, but it should
> not matter). And this issue is real
On Thu, Oct 05, 2017 at 10:00:25PM +0200, Antonio M wrote:
>battery is new . Anyway for a long time I had no issue with this port
>and it started short ago after upgrading recent kernels.
>No idea how to debug it. (this port is the high-power port, but it
>should not matter). And th
I have the log (tnx for help anyway) from 20:00:00 and forward: but the
full log is 225 lines and I suppose that I cannot load here..
Antonio Montagnani
Linux Fedora 26(Workstation)
inviato da Gmail
2017-10-05 22:58 GMT+02:00 Samuel Sieb :
> On 10/05/2017 01:45 PM, Antonio M wrote:
>
>> how can
On 10/05/2017 01:45 PM, Antonio M wrote:
how can I check it ?? especially after the mouse is working again? sorry
for the silly question
As root, run "journalctl -b". If you remember about what time it
happened, you can scroll down until you find that time. By default it
uses "less" as the
how can I check it ?? especially after the mouse is working again? sorry
for the silly question
Antonio Montagnani
Linux Fedora 26(Workstation)
inviato da Gmail
2017-10-05 21:55 GMT+02:00 Samuel Sieb :
> On 10/05/2017 12:12 PM, Antonio M wrote:
>
>> sometimes I loos the control of a wireless mo
battery is new . Anyway for a long time I had no issue with this port and
it started short ago after upgrading recent kernels.
No idea how to debug it. (this port is the high-power port, but it should
not matter). And this issue is really random, I worked one day with no
issue, but tonight I had t
On 10/05/2017 12:12 PM, Antonio M wrote:
sometimes I loos the control of a wireless mouse from Logitech: as soon
as I reinsert the receiver mouse starts again to work!!!
when mouse is dead
$ lsusb
Bus 002 Device 004: ID 8087:07da Intel Corp.
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrat
On Thu, Oct 5, 2017 at 3:12 PM, Antonio M
wrote:
> sometimes I loos the control of a wireless mouse from Logitech: as soon as
> I reinsert the receiver mouse starts again to work!!!
>
> when mouse is dead
> $ lsusb
> Bus 002 Device 004: ID 8087:07da Intel Corp.
> Bus 002 Device 002: ID 8087:0024
sometimes I loos the control of a wireless mouse from Logitech: as soon as
I reinsert the receiver mouse starts again to work!!!
when mouse is dead
$ lsusb
Bus 002 Device 004: ID 8087:07da Intel Corp.
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID
25 matches
Mail list logo
