2:43 a.m.
I have just noticed that quite a few of my systems now have their
Ethernet interfaces running at 100 MBits/s half duplex rather than the
expected 1GBits/s.
I think some update has caused this to happen, probably about 10 days
ago (noticed something was slow). These are KDE/Plasma GUI systems but
I'm not sure if this is due to a change in KDE/Plasma, NetworkManager or
something else.
On these systems the KDE/Plasma NeworkManager settings GUI interface now
has an "Allow auto-negotiation" checkbox which I don't think was there
before and it looks like this is set to non-auto, 100MBit/s, half duplex
by default if there is no ETHTOOL_OPTS="autoneg on" in the
/etc/sysconfig/network-scripts/ifcfg-* file and on initial setting of a
network interface.
I guess this is a change/bug in the KDE-Plasma network manager applet.
Where should I file this bug ?
3:52 a.m.
On 02/15/18 16:43, Terry Barnaby wrote:
I have just noticed that quite a few of my systems now have their
Ethernet
interfaces running at 100 MBits/s half duplex rather than the expected 1GBits/s.
I think some update has caused this to happen, probably about 10 days ago (noticed
something was slow). These are KDE/Plasma GUI systems but I'm not sure if this is
due to a change in KDE/Plasma, NetworkManager or something else.
On these systems the KDE/Plasma NeworkManager settings GUI interface now has an
"Allow auto-negotiation" checkbox which I don't think was there before and
it looks
like this is set to non-auto, 100MBit/s, half duplex by default if there is no
ETHTOOL_OPTS="autoneg on" in the /etc/sysconfig/network-scripts/ifcfg-* file
and on
initial setting of a network interface.
Here is a screen shot of an F24 Live system showing "autonegotiate" has been
there
for quite some time.
http://tinyurl.com/y8nzxdk5
I guess this is a change/bug in the KDE-Plasma network manager applet. Where should
I file this bug ?
I'm not seen any problems on any of my systems.
What is the output of "ethertool <devname>" ?
--
A motto of mine is: When in doubt, try it out
3:54 a.m.
I think this "allow auto-negotiation" checkbox is there for some time.
If I remember correctly, there was/is some problem with not being able
to apply settings for a (new?) interface if you do not select any proper
speed by hand or activate that checkbox.
I have checked your problem on one of my systems and I also had it set
to 100/half without auto-negotiation.
On 15/02/18 09:43, Terry Barnaby wrote:
I have just noticed that quite a few of my systems now have their
Ethernet interfaces running at 100 MBits/s half duplex rather than the
expected 1GBits/s.
I think some update has caused this to happen, probably about 10 days
ago (noticed something was slow). These are KDE/Plasma GUI systems but
I'm not sure if this is due to a change in KDE/Plasma, NetworkManager or
something else.
On these systems the KDE/Plasma NeworkManager settings GUI interface now
has an "Allow auto-negotiation" checkbox which I don't think was there
before and it looks like this is set to non-auto, 100MBit/s, half duplex
by default if there is no ETHTOOL_OPTS="autoneg on" in the
/etc/sysconfig/network-scripts/ifcfg-* file and on initial setting of a
network interface.
I guess this is a change/bug in the KDE-Plasma network manager applet.
Where should I file this bug ?
4:21 a.m.
On 02/15/18 17:54, Lukas Middendorf wrote:
I have checked your problem on one of my systems and I also had it
set
to 100/half without auto-negotiation.
I just checked with an F27 Live image as I don't have an unmodified system.
The Live image comes up with an interface defined without the "Allow
auto-negotiation" box checked. While Speed: is set to Automatic and Duplex: to
Half. I believe this may also be how the installed system will be initially configured.
However, looking at the interface via ethertool I see
Speed: 1000Mb/s
Duplex: Full
So, the question would be did your system once have "Allow auto-negotiation"
checked
but it became unchecked without action on your part? And what does ethertool show to
be the current speed? Are you unable to set it to the desired speed?
--
A motto of mine is: When in doubt, try it out
7:56 a.m.
On 15.02.2018 11:21, Ed Greshko wrote:
On 02/15/18 17:54, Lukas Middendorf wrote:
> I have checked your problem on one of my systems and I also had it set
> to 100/half without auto-negotiation.
So, the question would be did your system once have "Allow auto-negotiation"
checked
but it became unchecked without action on your part? And what does ethertool show to
be the current speed? Are you unable to set it to the desired speed?
I can select the desired settings and also enabling auto-negotiation
works, but for some reason it was set to 100/half without me doing anything.
I'm not sure I ever touched those settings on that system before (and I
definitely did not set it to something this slow on purpose). I think it
was a new install of F26 with home directory carried over from earlier
Fedora releases and then updated to F27.
During normal operation my internet connection would likely not even be
slowed down by 100/half. So I would not notice it immediately. But once
in a while I connect my notebook to the network and do file transfer
with sftp. I think the last time I did that a few weeks ago it was
faster than 100Mbit, but I can not say that for sure. The slowness I
have attributed to the slow cpu and magnetic drive on the notebook could
have been wrong network settings after all.
8:27 a.m.
On Thursday 15 February 2018 07:26 PM, Lukas Middendorf wrote:
On 15.02.2018 11:21, Ed Greshko wrote:
> On 02/15/18 17:54, Lukas Middendorf wrote:
>> I have checked your problem on one of my systems and I also had it set
>> to 100/half without auto-negotiation.
> So, the question would be did your system once have "Allow
auto-negotiation" checked
> but it became unchecked without action on your part? And what does ethertool show
to
> be the current speed? Are you unable to set it to the desired speed?
I can select the desired settings and also enabling auto-negotiation
works, but for some reason it was set to 100/half without me doing anything.
I'm not sure I ever touched those settings on that system before (and I
definitely did not set it to something this slow on purpose). I think it
was a new install of F26 with home directory carried over from earlier
Fedora releases and then updated to F27.
My understanding is that if one end (your PC) has auto negotiation
disabled while the other end (switch or router) has it enabled, the link
speed is set correctly, but the duplex setting falls back to
half-duplex. So that half-duplex setting is due to autoneg being off for
whatever reason.
Syam
9:20 a.m.
On 15/02/18 14:27, Syam Krishnan wrote:
On Thursday 15 February 2018 07:26 PM, Lukas Middendorf wrote:
> On 15.02.2018 11:21, Ed Greshko wrote:
>> On 02/15/18 17:54, Lukas Middendorf wrote:
>>> I have checked your problem on one of my systems and I also had it set
>>> to 100/half without auto-negotiation.
>> So, the question would be did your system once have "Allow
>> auto-negotiation" checked
>> but it became unchecked without action on your part? And what does
>> ethertool show to
>> be the current speed? Are you unable to set it to the desired speed?
> I can select the desired settings and also enabling auto-negotiation
> works, but for some reason it was set to 100/half without me doing
> anything.
> I'm not sure I ever touched those settings on that system before (and I
> definitely did not set it to something this slow on purpose). I think it
> was a new install of F26 with home directory carried over from earlier
> Fedora releases and then updated to F27.
My understanding is that if one end (your PC) has auto negotiation
disabled while the other end (switch or router) has it enabled, the
link speed is set correctly, but the duplex setting falls back to
half-duplex. So that half-duplex setting is due to autoneg being off
for whatever reason.
Syam
_______________________________________________
kde mailing list -- kde(a)lists.fedoraproject.org
To unsubscribe send an email to kde-leave(a)lists.fedoraproject.org
The problem I had here was that the ifcfg-* file came from an existing
configuration (F25) and did not have the ETHTOOL_OPTS="autoneg on".
Normally I don't touch the Ethernet configuration, but if you do then
when you open the KDE-Plasma NM settings it will show this as auto neg
off, 100 MBits/ half duplex. If you don't notice this (maybe you are
just setting a static IP address), it will store the settings like this
and you get a forced 100Mbits/s mode. I think it should default to auto
neg if the settings are not given in the original file or if there are
no previous settings.
If think if you remove the default ifcfg-Wired_connection_1 file, reboot
and edit your network settings you will see this behaviour.
On top of this I "believe" 3 of my systems changed to 100 MBits/s within
the last few weeks without me setting any network settings, probably on
an RPM update of something.
10:53 a.m.
New subject: Fedora27: KDE-Plasma/networkManager: Ethernet interfaces set to 100MBits/sec half duplex
On Friday, 16 February 2018 12:56:37 AM AEDT Lukas Middendorf wrote:
On 15.02.2018 11:21, Ed Greshko wrote:
> On 02/15/18 17:54, Lukas Middendorf wrote:
>
>> I have checked your problem on one of my systems and I also had it set
>> to 100/half without auto-negotiation.
>
>
> So, the question would be did your system once have "Allow
> auto-negotiation" checked
but it became unchecked without action on
your
> part? And what does ethertool show to be the current speed?
Are you
> unable to set it to the desired speed?
I can select the desired settings and also enabling auto-negotiation
works, but for some reason it was set to 100/half without me doing
anything.
I'm not sure I ever touched those settings on that system before
(and I definitely did not set it to something this slow on purpose).
I
think it was a new install of F26 with home directory carried over from
earlier Fedora releases and then updated to F27.
During normal operation my internet connection would likely not even be
slowed down by 100/half. So I would not notice it immediately. But once
in a while I connect my notebook to the network and do file transfer
with sftp. I think the last time I did that a few weeks ago it was
faster than 100Mbit, but I can not say that for sure. The slowness I
have attributed to the slow cpu and magnetic drive on the notebook could
have been wrong network settings after all.
I think you missed the question. What the GUI shows and what reality is are
two different things. I've had the GUI show 100/half - yet the switch port
indicates 1000/full.
--
Steven Haigh
📧 netwiz(a)crc.id.au 💻 http://www.crc.id.au
📞 +61 (3) 9001 6090 📱 0412 935 897
11:01 a.m.
New subject: Fedora27: KDE-Plasma/networkManager: Ethernet interfaces set to 100MBits/sec half duplex
Terry Barnaby wrote:
I have just noticed that quite a few of my systems now have their
Ethernet interfaces running at 100 MBits/s half duplex rather than the
expected 1GBits/s.
...
On these systems the KDE/Plasma NeworkManager settings GUI interface
now
has an "Allow auto-negotiation" checkbox which I don't think was there
before and it looks like this is set to non-auto, 100MBit/s, half duplex
by default if there is no ETHTOOL_OPTS="autoneg on" in the
/etc/sysconfig/network-scripts/ifcfg-* file and on initial setting of a
network interface.
I guess this is a change/bug in the KDE-Plasma network manager applet.
Where should I file this bug ?
Please do file a bug, preferably @ bugs.kde.org
-- Rex
12:39 p.m.
On 15/02/18 17:01, Rex Dieter wrote:
Terry Barnaby wrote:
> I have just noticed that quite a few of my systems now have their
> Ethernet interfaces running at 100 MBits/s half duplex rather than the
> expected 1GBits/s.
...
> On these systems the KDE/Plasma NeworkManager settings GUI interface now
> has an "Allow auto-negotiation" checkbox which I don't think was there
> before and it looks like this is set to non-auto, 100MBit/s, half duplex
> by default if there is no ETHTOOL_OPTS="autoneg on" in the
> /etc/sysconfig/network-scripts/ifcfg-* file and on initial setting of a
> network interface.
>
> I guess this is a change/bug in the KDE-Plasma network manager applet.
> Where should I file this bug ?
Please do file a bug, preferably @ bugs.kde.org
-- Rex
_______________________________________________
kde mailing list -- kde(a)lists.fedoraproject.org
To unsubscribe send an email to kde-leave(a)lists.fedoraproject.org
Ok, have added bug: 390518 <https://bugs.kde.org/show_bug.cgi?id=390518>
Terry
3:45 p.m.
On 02/16/18 00:53, Steven Haigh wrote:
I think you missed the question. What the GUI shows and what reality
is are
two different things. I've had the GUI show 100/half - yet the switch port
indicates 1000/full.
Exactly. And that is why I had requested the output of ethtool.
I just installed a fresh copy of F27/KDE from the Live-ISO. Bringing up the
Network-Manager GUI one sees
Allow Auto-negotiation: Unchecked
Speed: Automatic
Duplex: Half
The hardware is
00:03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller
The driver in use is (from lsmod) e1000.
The ifcfg-enp0s3 file contains...
[egreshko@f27k-v network-scripts]$ cat ifcfg-enp0s3
TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=enp0s3
UUID=7f87f7d8-1d0f-316e-9a2c-419042156b19
ONBOOT=yes
AUTOCONNECT_PRIORITY=-999
DEVICE=enp0s3
(No, ETHTOOL_OPTS= line)
And ethtool reports....
Settings for enp0s3:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: off (auto)
Cannot get wake-on-lan settings: Operation not permitted
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
So, what the GUI has and what reality is are different. Possibly a function of the
driver?
Oh, well.... I suppose I'll follow the BZ.
--
A motto of mine is: When in doubt, try it out
7:48 p.m.
On Friday 16 February 2018 03:15 AM, Ed Greshko wrote:
On 02/16/18 00:53, Steven Haigh wrote:
> I think you missed the question. What the GUI shows and what reality is are
> two different things. I've had the GUI show 100/half - yet the switch port
> indicates 1000/full.
Exactly. And that is why I had requested the output of ethtool.
I have your same situation. ethtool says auto-neg on and
100Mbps/full-duplex while the GUI has auto-neg disabled and shows
100Mbps/half-duplex.
The ifcfg file is also similar to yours.
Syam
I just installed a fresh copy of F27/KDE from the Live-ISO. Bringing up the
Network-Manager GUI one sees
Allow Auto-negotiation: Unchecked
Speed: Automatic
Duplex: Half
The hardware is
00:03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller
The driver in use is (from lsmod) e1000.
The ifcfg-enp0s3 file contains...
[egreshko@f27k-v network-scripts]$ cat ifcfg-enp0s3
TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=enp0s3
UUID=7f87f7d8-1d0f-316e-9a2c-419042156b19
ONBOOT=yes
AUTOCONNECT_PRIORITY=-999
DEVICE=enp0s3
(No, ETHTOOL_OPTS= line)
And ethtool reports....
Settings for enp0s3:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: off (auto)
Cannot get wake-on-lan settings: Operation not permitted
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
So, what the GUI has and what reality is are different. Possibly a function of the
driver?
Oh, well.... I suppose I'll follow the BZ.
_______________________________________________
kde mailing list -- kde(a)lists.fedoraproject.org
To unsubscribe send an email to kde-leave(a)lists.fedoraproject.org
2254
days inactive
2255
days old
11 comments
6 participants
participants (6)
-
Ed Greshko -
Lukas Middendorf -
Rex Dieter -
Steven Haigh -
Syam Krishnan -
Terry Barnaby