wireless mouse dies

classic Classic list List threaded Threaded
25 messages Options
12
Reply | Threaded
Open this post in threaded view
|

wireless mouse dies

antonio montagnani-2
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 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 04f2:b302 Chicony Electronics Co., Ltd
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

when it works
[antonio@fujitsu ~]$ lsusb
Bus 002 Device 004: ID 8087:07da Intel Corp.
Bus 002 Device 017: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 04f2:b302 Chicony Electronics Co., Ltd
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

any idea: shall I file a bug??
Antonio Montagnani

Linux Fedora 26(Workstation)
inviato da Gmail

_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: wireless mouse dies

foxec208


On Thu, Oct 5, 2017 at 3:12 PM, Antonio M <[hidden email]> 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. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 04f2:b302 Chicony Electronics Co., Ltd
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

when it works
[antonio@fujitsu ~]$ lsusb
Bus 002 Device 004: ID 8087:07da Intel Corp.
Bus 002 Device 017: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 04f2:b302 Chicony Electronics Co., Ltd
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

any idea: shall I file a bug??
Antonio Montagnani

Linux Fedora 26(Workstation)
inviato da Gmail

_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]

How old is the battery in the mouse?  Try the receiver in a different USB port you appear to have two different USB hubs.


_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: wireless mouse dies

Samuel Sieb
In reply to this post by antonio montagnani-2
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. Integrated Rate Matching Hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 004: ID 04f2:b302 Chicony Electronics Co., Ltd
> Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Since the receiver has gone off the USB bus, that sounds like a hardware
problem.  Have you checked the journal for what happened at that point?
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: wireless mouse dies

antonio montagnani-2
In reply to this post by foxec208
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 two stops.

Antonio Montagnani

Linux Fedora 26(Workstation)
inviato da Gmail

2017-10-05 21:31 GMT+02:00 Terry Polzin <[hidden email]>:


On Thu, Oct 5, 2017 at 3:12 PM, Antonio M <[hidden email]> 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. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 04f2:b302 Chicony Electronics Co., Ltd
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

when it works
[antonio@fujitsu ~]$ lsusb
Bus 002 Device 004: ID 8087:07da Intel Corp.
Bus 002 Device 017: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 04f2:b302 Chicony Electronics Co., Ltd
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

any idea: shall I file a bug??
Antonio Montagnani

Linux Fedora 26(Workstation)
inviato da Gmail

_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]

How old is the battery in the mouse?  Try the receiver in a different USB port you appear to have two different USB hubs.


_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]



_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: wireless mouse dies

antonio montagnani-2
In reply to this post by Samuel Sieb
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 <[hidden email]>:
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. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 04f2:b302 Chicony Electronics Co., Ltd
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Since the receiver has gone off the USB bus, that sounds like a hardware problem.  Have you checked the journal for what happened at that point?

_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]


_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: wireless mouse dies

Samuel Sieb
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 pager, so hopefully you know some of the keys.  The
easiest method might be to use the "/" command to search for "Logitech".
  The first match should be from booting, but there should be another
match further down where you replugged it.  Then you can go back a bit
to see what happened when it disappeared.
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: wireless mouse dies

antonio montagnani-2
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 <[hidden email]>:
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 pager, so hopefully you know some of the keys.  The easiest method might be to use the "/" command to search for "Logitech".  The first match should be from booting, but there should be another match further down where you replugged it.  Then you can go back a bit to see what happened when it disappeared.

_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]


_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: wireless mouse dies

fred smith-5
In reply to this post by antonio montagnani-2
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 this issue is really random, I worked one day
>    with no issue, but tonight I had two stops.
>
>    Antonio Montagnani
>    Linux Fedora 26(Workstation)
>    inviato da Gmail
>    2017-10-05 21:31 GMT+02:00 Terry Polzin <[1][hidden email]>:
>
>    On Thu, Oct 5, 2017 at 3:12 PM, Antonio M
>    <[2][hidden email]> 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. Integrated Rate Matching
>    Hub
>    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>    Bus 001 Device 004: ID 04f2:b302 Chicony Electronics Co., Ltd
>    Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching
>    Hub
>    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>    when it works
>    [antonio@fujitsu ~]$ lsusb
>    Bus 002 Device 004: ID 8087:07da Intel Corp.
>    Bus 002 Device 017: ID 046d:c52f Logitech, Inc. Unifying Receiver
>    Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching
>    Hub
>    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>    Bus 001 Device 004: ID 04f2:b302 Chicony Electronics Co., Ltd
>    Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching
>    Hub
>    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>    any idea: shall I file a bug??

you may have a bad usb dongle, or an intermittent USB port. Have you
tried it in a different port?



--
---- Fred Smith -- [hidden email] -----------------------------
               Show me your ways, O LORD, teach me your paths;
                     Guide me in your truth and teach me,
                         for you are God my Savior,
                    And my hope is in you all day long.
-------------------------- Psalm 25:4-5 (NIV) --------------------------------
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: wireless mouse dies

Patrick O'Callaghan-2
In reply to this post by antonio montagnani-2
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 really random, I worked one day with no
> issue, but tonight I had two stops.

I had similar problems with a Logitech mouse until I moved the dongle
closer to the mouse pad using a USB extension cable. Previously it had
been under the desk and frequently lost connection.

poc
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: wireless mouse dies

murph
In reply to this post by antonio montagnani-2
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 <[hidden email]> 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. Integrated Rate Matching Hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 004: ID 04f2:b302 Chicony Electronics Co., Ltd
> Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> when it works
> [antonio@fujitsu ~]$ lsusb
> Bus 002 Device 004: ID 8087:07da Intel Corp.
> Bus 002 Device 017: ID 046d:c52f Logitech, Inc. Unifying Receiver
> Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 004: ID 04f2:b302 Chicony Electronics Co., Ltd
> Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> any idea: shall I file a bug??
> Antonio Montagnani
>
> Linux Fedora 26(Workstation)
> inviato da Gmail
>
> _______________________________________________
> users mailing list -- [hidden email]
> To unsubscribe send an email to [hidden email]
>
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: wireless mouse dies

Samuel Sieb
In reply to this post by antonio montagnani-2
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 keeps disconnecting,
maybe some connection inside is loose.

ott 05 21:06:45 fujitsu kernel: usb 2-1.1: USB disconnect, device number 10
ott 05 21:06:51 fujitsu kernel: usb 2-1.1: new full-speed USB device
number 11 using ehci-pci
ott 05 21:06:51 fujitsu kernel: usb 2-1.1: New USB device found,
idVendor=046d, idProduct=c52f
ott 05 21:06:51 fujitsu kernel: usb 2-1.1: New USB device strings:
Mfr=1, Product=2, SerialNumber=0
ott 05 21:06:51 fujitsu kernel: usb 2-1.1: Product: USB Receiver
ott 05 21:06:51 fujitsu kernel: usb 2-1.1: Manufacturer: Logitech
ott 05 21:06:51 fujitsu kernel: usb 2-1.1: USB disconnect, device number 11
ott 05 21:06:52 fujitsu kernel: usb 2-1.1: new full-speed USB device
number 12 using ehci-pci
ott 05 21:06:52 fujitsu kernel: usb 2-1.1: device not accepting address
12, error -32
ott 05 21:06:53 fujitsu kernel: usb 2-1.1: new full-speed USB device
number 14 using ehci-pci
ott 05 21:06:53 fujitsu kernel: usb 2-1.1: New USB device found,
idVendor=046d, idProduct=c52f
ott 05 21:06:53 fujitsu kernel: usb 2-1.1: New USB device strings:
Mfr=1, Product=2, SerialNumber=0
ott 05 21:06:53 fujitsu kernel: usb 2-1.1: Product: USB Receiver
ott 05 21:06:53 fujitsu kernel: usb 2-1.1: Manufacturer: Logitech
ott 05 21:07:38 fujitsu kernel: usb 2-1.1: USB disconnect, device number 14
ott 05 21:09:01 fujitsu kernel: usb 2-1.1: new full-speed USB device
number 15 using ehci-pci
ott 05 21:09:01 fujitsu kernel: usb 2-1.1: New USB device found,
idVendor=046d, idProduct=c52f
ott 05 21:09:01 fujitsu kernel: usb 2-1.1: New USB device strings:
Mfr=1, Product=2, SerialNumber=0
ott 05 21:09:01 fujitsu kernel: usb 2-1.1: Product: USB Receiver
ott 05 21:09:01 fujitsu kernel: usb 2-1.1: Manufacturer: Logitech
ott 05 21:09:02 fujitsu kernel: usb 2-1.1: USB disconnect, device number 15
ott 05 21:09:07 fujitsu kernel: usb 2-1.1: new full-speed USB device
number 16 using ehci-pci
ott 05 21:09:07 fujitsu kernel: usb 2-1.1: New USB device found,
idVendor=046d, idProduct=c52f
ott 05 21:09:07 fujitsu kernel: usb 2-1.1: New USB device strings:
Mfr=1, Product=2, SerialNumber=0
ott 05 21:09:07 fujitsu kernel: usb 2-1.1: Product: USB Receiver
ott 05 21:09:07 fujitsu kernel: usb 2-1.1: Manufacturer: Logitech
ott 05 21:09:07 fujitsu kernel: usb 2-1.1: USB disconnect, device number 16
ott 05 21:09:07 fujitsu kernel: usb 2-1.1: new full-speed USB device
number 17 using ehci-pci
ott 05 21:09:07 fujitsu kernel: usb 2-1.1: New USB device found,
idVendor=046d, idProduct=c52f
ott 05 21:09:07 fujitsu kernel: usb 2-1.1: New USB device strings:
Mfr=1, Product=2, SerialNumber=0
ott 05 21:09:07 fujitsu kernel: usb 2-1.1: Product: USB Receiver
ott 05 21:09:07 fujitsu kernel: usb 2-1.1: Manufacturer: Logitech
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: wireless mouse dies

Joe Zeff-2
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
people assumed that all computers were hardware, and were surprised to
find that they were caused by a software issue.  Now, the hardware is
considered to be so reliable that the situation is reversed, and people
will spend weeks trying to debug a software issue that's really caused
by a piece of wonky hardware.
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: wireless mouse dies

Rick Stevens-4
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 surprised.  I can remember, back in the '80s, when many
> people assumed that all computers were hardware, and were surprised to
> find that they were caused by a software issue.  Now, the hardware is
> considered to be so reliable that the situation is reversed, and people
> will spend weeks trying to debug a software issue that's really caused
> by a piece of wonky hardware.

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 happens, it's probably
software. If it's intermittent, then it's likely hardware. Or not."
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    [hidden email] -
- AIM/Skype: therps2        ICQ: 226437340           Yahoo: origrps2 -
-                                                                    -
-           Denial.  It ain't just a river in Egypt anymore!         -
----------------------------------------------------------------------
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: wireless mouse dies

Joe Zeff-2
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 happens, it's probably
> software. If it's intermittent, then it's likely hardware. Or not."

Pournelle's first rule of debugging is, "The first thing you check is
the cables."
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: wireless mouse dies

Rick Stevens-4
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
>> something. My rule of thumb is "If it always happens, it's probably
>> software. If it's intermittent, then it's likely hardware. Or not."
>
> Pournelle's first rule of debugging is, "The first thing you check is
> the cables."

Ah, yes. Good ol' Jerry from the appropriately named "Chaos Manor". He
was an old friend of mine, going back to the ancient and crusty VCC
days. ----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    [hidden email] -
- AIM/Skype: therps2        ICQ: 226437340           Yahoo: origrps2 -
-                                                                    -
-       Charter Member of the American Society of Curmudgeons        -
----------------------------------------------------------------------
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: wireless mouse dies

George N. White III
In reply to this post by Joe Zeff-2
On 6 October 2017 at 17:23, Joe Zeff <[hidden email]> 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 surprised.  I can remember, back in the '80s, when many people assumed that all computers were hardware, and were surprised to find that they were caused by a software issue.  Now, the hardware is considered to be so reliable that the situation is reversed, and people will spend weeks trying to debug a software issue that's really caused by a piece of wonky hardware.

Actually, today's hardware problems are often caused by buggy firmware -- software has taken control of the developed world.

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 rejecting spurious signals.   USB3 interference with 2.4 GHz devices is going to be more common as el cheapo USB3 devices and cables become more common.

If you suspect interference, turn off all but essential devices and see if the errors go away.  If so, add devices back one at a time
until the errors resume.  If you have things like external drives, it may help to run a grund wire to bond the cases together with the system case. 

 
--
George N. White III <[hidden email]>
Head of St. Margarets Bay, Nova Scotia

_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: wireless mouse dies

Joe Zeff-2
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 rejecting spurious signals.

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 socket to
the modem was too long and he'd coiled it up.  I explained that this
just made an electromagnet out of the line and it was causing
interference with itself.  I told him to get a shorter cable, and not
let it get coiled again.  AFAICT, problem solved.
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: wireless mouse dies

Tom Horsley-5
In reply to this post by Rick Stevens-4
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 this happen many times. I can only
assume computer hardware is both sentient and
malevolent :-).
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: wireless mouse dies

Rick Stevens-4
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, it chooses
> that precise moment to break.
>
> I have seen this happen many times. I can only
> assume computer hardware is both sentient and
> malevolent :-).

As I understand it, the curriculum of hardware design courses require
potential engineers to develop CUD (critical use detector) circuits.
To show how smart they are when they hit the real world, they insert
them into any hardware they design.

The original concept was invented by Xerox and the early versions were
only able to cause massive paper jams when you needed that report to
give to your boss. This also gave rise to the adult version of the old
childhood "my dog ate my homework" excuse.

It has since become more sophisticated and can cause far more subtle
faults. I suspect this was to get even with those who stole the public-
domain PARC desktop metaphor and would sue anyone else who used it (are
you listening, Apple?)

The auto industry has a similar device which explains why your car
always does something weird--but only when there's no mechanic around.

"Just because I'm paranoid doesn't mean they AREN'T out to get me!"
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    [hidden email] -
- AIM/Skype: therps2        ICQ: 226437340           Yahoo: origrps2 -
-                                                                    -
-      We are born naked, wet and hungry. Then things get worse.     -
----------------------------------------------------------------------
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: wireless mouse dies

Rick Stevens-4
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 knows
>> you'll be sure the new OS is the problem, it chooses
>> that precise moment to break.
>>
>> I have seen this happen many times. I can only
>> assume computer hardware is both sentient and
>> malevolent :-).
>
> As I understand it, the curriculum of hardware design courses require
> potential engineers to develop CUD (critical use detector) circuits.
> To show how smart they are when they hit the real world, they insert
> them into any hardware they design.
>
> The original concept was invented by Xerox and the early versions were
> only able to cause massive paper jams when you needed that report to
> give to your boss. This also gave rise to the adult version of the old
> childhood "my dog ate my homework" excuse.
>
> It has since become more sophisticated and can cause far more subtle
> faults. I suspect this was to get even with those who stole the public-
> domain PARC desktop metaphor and would sue anyone else who used it (are
> you listening, Apple?)
>
> The auto industry has a similar device which explains why your car
> always does something weird--but only when there's no mechanic around.

I should also mention that the television industry has an even more evil
device. It's called a "kardashian". :-)
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    [hidden email] -
- AIM/Skype: therps2        ICQ: 226437340           Yahoo: origrps2 -
-                                                                    -
-      Cuteness can be overcome through sufficient bastardry         -
-                                         --Mark 'Kamikaze' Hughes   -
----------------------------------------------------------------------
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
12