On 27Feb2021 09:50, Doug H. wrote:
>I am having an odd problem with my ethernet port. I assume this came
>with a dnf update but that was some weeks ago so I can't help figure
>out what update might have done it. When first discovered I think I
>found that booting from an older kernel did not fix i
On Sat, Feb 27, 2021, at 1:36 PM, Cameron Simpson wrote:
> On 27Feb2021 09:50, Doug H. wrote:
> >I am having an odd problem with my ethernet port. I assume this came
> >with a dnf update but that was some weeks ago so I can't help figure
> >out what update might have done it. When first discovered
On 2/27/21 9:50 AM, Doug H. wrote:
I am having an odd problem with my ethernet port. I assume this came
with a dnf update but that was some weeks ago so I can't help figure
out what update might have done it. When first discovered I think I
found that booting from an older kernel did not fix it.
On Sat, Feb 27, 2021, at 2:12 PM, Samuel Sieb wrote:
> On 2/27/21 9:50 AM, Doug H. wrote:
> > I am having an odd problem with my ethernet port. I assume this came
> > with a dnf update but that was some weeks ago so I can't help figure
> > out what update might have done it. When first discovered I
On Sat, 27 Feb 2021 at 17:59, Doug H. wrote:
> On Sat, Feb 27, 2021, at 1:36 PM, Cameron Simpson wrote:
> > On 27Feb2021 09:50, Doug H. wrote:
> > >I am having an odd problem with my ethernet port. I assume this came
> > >with a dnf update but that was some weeks ago so I can't help figure
> > >
On 2/27/21 3:12 PM, Samuel Sieb wrote:
Given that an older kernel doesn't fix it, that suggests it might not be
software.
Or, of course, it just might not be kernel related.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send
On 2/27/21 2:21 PM, Doug H. wrote:
On Sat, Feb 27, 2021, at 2:12 PM, Samuel Sieb wrote:
On 2/27/21 9:50 AM, Doug H. wrote:
I am having an odd problem with my ethernet port. I assume this came
with a dnf update but that was some weeks ago so I can't help figure
out what update might have done it
On Sat, Feb 27, 2021, at 2:31 PM, Samuel Sieb wrote:
> On 2/27/21 2:21 PM, Doug H. wrote:
> > On Sat, Feb 27, 2021, at 2:12 PM, Samuel Sieb wrote:
> >> On 2/27/21 9:50 AM, Doug H. wrote:
> >>> I am having an odd problem with my ethernet port. I assume this came
> >>> with a dnf update but that was
You might try ethtool commands it will have an option to "test" and
reset options. these options may or may not be the exact same code
as the older mii-tool. It is also possible that not all of the
possible options in mii-tool and/or ethtool are actually implemented
in the driver, so one may wor
On 28/02/2021 01:50, Doug H. wrote:
The simple fix is to physically unplug and replug the cable. When it is
not working (each reboot) there are not lights on. The physical
"bounce" lights up the LEDs and it comes right up.
When you boot the system and get to the kernel selection menu can you st
On 2/27/21 3:06 PM, Doug H. wrote:
On to answering the question from Samuel:
I am not seeing much help in the "while bad" journal:
# grep enp5s0 journalctl-b.while_not_working.txt
Feb 27 14:52:58 wombat.wombatz.com kernel: r8169 :05:00.0 enp5s0: renamed
from eth0
That grep isn't going to
On Sat, Feb 27, 2021, at 3:56 PM, Samuel Sieb wrote:
> On 2/27/21 3:06 PM, Doug H. wrote:
> > On to answering the question from Samuel:
> > I am not seeing much help in the "while bad" journal:
> >
> > # grep enp5s0 journalctl-b.while_not_working.txt
> > Feb 27 14:52:58 wombat.wombatz.com kernel:
On 2/27/21 4:24 PM, Doug H. wrote:
Is it directly connected to the Pi?
Yup, it is CAT5 from port to port. I set it up to get better speeds when transferring
files for the Plex player on the Pi. I then started to use it for the ability to
"wake on LAN" since the Pi runs all time and this syste
On Sat, Feb 27, 2021, at 4:36 PM, Samuel Sieb wrote:
> On 2/27/21 4:24 PM, Doug H. wrote:
> >> Is it directly connected to the Pi?
> >
> > Yup, it is CAT5 from port to port. I set it up to get better speeds when
> > transferring files for the Plex player on the Pi. I then started to use it
> > f
On 2/27/21 4:56 PM, Doug H. wrote:
On Sat, Feb 27, 2021, at 4:36 PM, Samuel Sieb wrote:
Do you have a network switch of some kind around? If so, try putting
that in between and see if it makes any difference. It it does, then
there might be something to try with ethtool.
I do. Netgear FS116
On 28/02/2021 10:36, Samuel Sieb wrote:
So this confirms what I was suspecting. The 10M you see at first is the "default" state of the ethernet card where it's watching for the wake-on-lan signal. Once the kernel boots and initializes the card, the card tries to auto-negotiate. This seems to be
Make sure to set the PI end to match. The 100Mbit/full auto-neg
failure default is 10mbit/half and works badly with the other end
running 100/full.
As someone also said you might want to try a 100Mbit crossover cable.
The gig port would need to figure out correctly that it needs to have
2 pairs
On Sun, Feb 28, 2021, at 5:09 AM, Roger Heflin wrote:
> Make sure to set the PI end to match.
Ah, good point. It should have been obvious but I have not even looked at the
Pi end yet, other than `dmesg` and seeing the renewed connection:
$ dmesg |tail -2
[1932715.302313] smsc95xx 1-1.1:1.0 eth0:
On Sat, Feb 27, 2021, at 6:36 PM, Samuel Sieb wrote:
> On 2/27/21 4:56 PM, Doug H. wrote:
> > On Sat, Feb 27, 2021, at 4:36 PM, Samuel Sieb wrote:
> >> Do you have a network switch of some kind around? If so, try putting
> >> that in between and see if it makes any difference. It it does, then
>
On Sun, Feb 28, 2021, at 9:44 AM, Doug H. wrote:
> And you did ask for ethtool output while working:
I just realized that the ethtool output from the Pi side had only the single
100Full as advertised. It still needed a reboot after some tests to lock them
both to 100Full. I ended up rolling that
For what it is worth, I had a smoothieboard I was trying to connect
directly to my computer, and no power on earth seemed to be able to
make it work reliably with DHCP. I statically configured the IP, and it
connects every time with a direct connection. Never did figure
out that issue, just leaving
On Sun, Feb 28, 2021, at 10:01 AM, Tom Horsley wrote:
> For what it is worth, I had a smoothieboard I was trying to connect
> directly to my computer, and no power on earth seemed to be able to
> make it work reliably with DHCP. I statically configured the IP, and it
> connects every time with a di
On 2/27/21 6:55 PM, Ed Greshko wrote:
On 28/02/2021 10:36, Samuel Sieb wrote:
So this confirms what I was suspecting. The 10M you see at first is
the "default" state of the ethernet card where it's watching for the
wake-on-lan signal. Once the kernel boots and initializes the card,
the card
On 2/28/21 9:44 AM, Doug H. wrote:
On Sat, Feb 27, 2021, at 6:36 PM, Samuel Sieb wrote:
One thing to try if you can is to use a cross-over network cable.
I still think this would be your best option if you can find or make one.
It would have been helpful to see what the output of ethtool is
On Sun, Feb 28, 2021, at 12:07 PM, Samuel Sieb wrote:
> On 2/28/21 9:44 AM, Doug H. wrote:
> > On Sat, Feb 27, 2021, at 6:36 PM, Samuel Sieb wrote:
> >> One thing to try if you can is to use a cross-over network cable.
>
> I still think this would be your best option if you can find or make one.
On 2/28/21 12:36 PM, Doug H. wrote:
On Sun, Feb 28, 2021, at 12:07 PM, Samuel Sieb wrote:
On 2/28/21 9:44 AM, Doug H. wrote:
On Sat, Feb 27, 2021, at 6:36 PM, Samuel Sieb wrote:
One thing to try if you can is to use a cross-over network cable.
I still think this would be your best option if
On Sun, Feb 28, 2021, at 12:50 PM, Samuel Sieb wrote:
> On 2/28/21 12:36 PM, Doug H. wrote:
> > On Sun, Feb 28, 2021, at 12:07 PM, Samuel Sieb wrote:
> >> On 2/28/21 9:44 AM, Doug H. wrote:
> >>> On Sat, Feb 27, 2021, at 6:36 PM, Samuel Sieb wrote:
> One thing to try if you can is to use a cro
On 28Feb2021 13:41, Doug H. wrote:
>P.S. I found a Belkin cable for $3.99. I like that name better, so
>ordered it.
>Belkin 3-Foot CAT5e Crossover Molded Networking Cable (Yellow)
>
>It seems worth the test and worth having such a cable.
Aye. FWIW, in a former life the place I worked at made all
On Tue, 2021-03-02 at 08:33 +1100, Cameron Simpson wrote:
> Aye. FWIW, in a former life the place I worked at made all our
> crossover cables yellow so that we knew what we were looking at.
I'd always understood that gigabit didn't need crossover cables, though
just read that it's in the spec that
On Sun, Feb 28, 2021, at 12:07 PM, Samuel Sieb wrote:
> On 2/28/21 9:44 AM, Doug H. wrote:
> > On Sat, Feb 27, 2021, at 6:36 PM, Samuel Sieb wrote:
> >> One thing to try if you can is to use a cross-over network cable.
>
> I still think this would be your best option if you can find or make one.
30 matches
Mail list logo
