https://bugs.kde.org/show_bug.cgi?id=413211
Fabian Vogt <fab...@ritter-vogt.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fab...@ritter-vogt.de
--- Comment #7 from Fabian Vogt <fab...@ritter-vogt.de> ---
(In reply to Dennis Schridde from comment #6)
> I am coming here after, with Beniamino Galvani <bgalv...@redhat.com>'s help
> in https://bugzilla.redhat.com/show_bug.cgi?id=1765490#c13, it became clear
> that KDE Plasma NetworkManager interprets the data from NetworkManager
> wrongly:
>
> $ nmcli connection show $conn_uuid
> 802-3-ethernet.speed: 0
> 802-3-ethernet.duplex: --
> 802-3-ethernet.auto-negotiate: no
>
> shows up as Auto Negotiate: No, Speed: 100Mbps, Duplex: Half in the KDE
> Plasma NetworkManager connection configuration dialogue.
>
> According to him, it *should* mean: Auto Negotiate: No, Speed: Link Default,
> Duplex: Link Default.
There's another layer of weirdness above that, as nmcli edit describe says:
> When TRUE, enforce auto-negotiation of speed and duplex mode.
> If "speed" and "duplex" properties are both specified, only that single mode
> will be advertised and accepted during the link auto-negotiation process:
> this works only for BASE-T 802.3 specifications and is useful for enforcing
> gigabits modes, as in these cases link negotiation is mandatory. When FALSE,
> "speed" and "duplex" properties should be both set or link configuration will
> be skipped.
I did some tests and if either .speed or .duplex are not set, "auto-negotiate:
no" has no effect.
Currently the KCM shows that as "100MiB/s Full-Duplex" and saving that has
weird effects.
--
You are receiving this mail because:
You are watching all bug changes.
