On 24/11/2021 23.39, Patrick Shanahan wrote:
* Carlos E. R.
[11-24-21 17:35]: On 24/11/2021 23.29, Patrick Shanahan wrote:
* Carlos E. R. <> [11-24-21 17:27]:
On 24/11/2021 14.45, Carlos E. R. wrote:
On 24/11/2021 14.28, Patrick Shanahan wrote:
* Carlos E. R. <> [11-24-21 07:05]:
What is going on?
This laptop worked previously, days ago. With the same cables. Another laptop works fine with one of those cables.
uneducated guess would be failing hardware. does your bios have a
hardward
check?
No, but I will try another OS.
It appears to be the cable. I swapped to a commercially made cable, and it works. Maybe those two old cables only works at 100, not 1000, because one of them is in use with another laptop just fine, at 100. But it worked in the past with this laptop just fine.
Weird.
but the cable *is* hardware.
But not the machine. A cable is replaceable, a laptop port is not. Not easily, anyway, not by myself. It is an expensive ordeal.
well, earlier you said, "one of those", implying more than one cable was tried ???? but still failure, which would indicate both bad cables or the port and all are hardware and hardware is not exclusively "computer".
I had tried two old cables, one on laptop 1 (wich only does 100 mbits) and another on laptop 2, the current incumbent, which should do 1gbit. Laptop 1 (with cable 1) was working the other day. Laptop 2 (with cable 2) failed to connect, but it had worked maybe two weeks before, IIRC. Cable is cat 5E. Laptop 2 also failed to connect on cable 1 (cat 5). Then you say it could be hardware. I try to boot laptop 2 on another partition that has Leap 15.0, fails to boot. Then boot Windows, which says there is no connection. I pick an almost brand new cable from suitcase, cat 6, and use it on laptop 2, on a free port of the switch. Works instantly. Suspicion is that cable 1 and 2 fail to do gigabit, now, but worked previously. Maybe some parameter changed? Chance? However, cable 3 had given my trouble with laptop 2 on another location, but that was definitely a DNS problem. When I had problems yesterday, I immediately thought I had DNS trouble again (which indeed I had, but was not the main trouble). -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)