My Lenovo T500 will not boot 4.6 though it will 4.5 ones. I have posted a bug report. https://bugzilla.redhat.com/show_bug.cgi?id=1320922
However it seems that since the last update of the iwl* files, or maybe the NetworkManager files, kernel 4.5 will not start the WiFi. From what I can see the fact that NetworkManager is still a running service means that the wired Ethernet port cannot be started.
Is there something wrong with my set up that stops NetworkManager using wired Ethernet?
I found that stopping the NetworkManager service allows me to use ifup to get the wired Ethernet working, but this is initd type stuff rather than systemd type stuff and so feels ugly, or is it the right thing?
What is officially the best way of getting wired Ethernet to be part of the set up?
On 03/30/2016 11:08 AM, Russel Winder wrote:
However it seems that since the last update of the iwl* files, or maybe the NetworkManager files, kernel 4.5 will not start the WiFi. From what I can see the fact that NetworkManager is still a running service means that the wired Ethernet port cannot be started.
NetworkManager should bring up the wired ethernet as soon as the port detects a connection.
Is there something wrong with my set up that stops NetworkManager using wired Ethernet?
Anything in the logs?
I found that stopping the NetworkManager service allows me to use ifup to get the wired Ethernet working, but this is initd type stuff rather than systemd type stuff and so feels ugly, or is it the right thing?
ifup should work with NetworkManager. Have you tried running ifup with NetworkManager running?
What is officially the best way of getting wired Ethernet to be part of the set up?
It should just work.
On Wed, 2016-03-30 at 11:16 -0700, Samuel Sieb wrote:
[…] NetworkManager should bring up the wired ethernet as soon as the port detects a connection.
Definitely not on this T500. Plug the RJ45 in, green lights appear, no activity of any sort trying to make a DHCP call. Cannot see any activity relating to the Ethernet in the journalctl -r listing.
[…]
Anything in the logs?
Nothing in the journalctl -r listing as far as I can see when the RJ45 is removed or inserted.
[…]
ifup should work with NetworkManager. Have you tried running ifup with NetworkManager running?
The ifup command offloads to nmcli if the NetworkManager service is running and it bombs out:
Error: Connection activation failed: No suitable device found for this connection.
Terminate the NetworkManager service and the same ifup command offloads to something else, gets the DHCP going and it works fine.
It should just work.
Sadly on this T500, it doesn't :-(
On 03/31/2016 02:44 AM, Russel Winder wrote:
On Wed, 2016-03-30 at 11:16 -0700, Samuel Sieb wrote: Definitely not on this T500. Plug the RJ45 in, green lights appear, no activity of any sort trying to make a DHCP call. Cannot see any activity relating to the Ethernet in the journalctl -r listing.
Does "ifconfig -a" show the ethernet interface? Does "journalctl -b" show the interface getting initialized? Try "ethtool <interfacename>" with the cable out and in. Particularly note the "Link detected" line at the bottom. "nmcli d" "nmcli c | grep ethernet"
[…]
Anything in the logs?
Nothing in the journalctl -r listing as far as I can see when the RJ45 is removed or inserted.
Strange.
Terminate the NetworkManager service and the same ifup command offloads to something else, gets the DHCP going and it works fine.
The journalctl output at that time would be very interesting.
The latest NetworkManager upgrade appears to have fixed the WiFi connection on the T500, which is great :-)
And, it now automatically detects the RJ45 wired Ethernet and responds properly. Double yay! :-))
I guess the proposed experimenting is now redundant, or is it worth trying anyway?
On Thu, 2016-03-31 at 08:10 -0700, Samuel Sieb wrote:
On 03/31/2016 02:44 AM, Russel Winder wrote:
On Wed, 2016-03-30 at 11:16 -0700, Samuel Sieb wrote: Definitely not on this T500. Plug the RJ45 in, green lights appear, no activity of any sort trying to make a DHCP call. Cannot see any activity relating to the Ethernet in the journalctl -r listing.
Does "ifconfig -a" show the ethernet interface? Does "journalctl -b" show the interface getting initialized? Try "ethtool <interfacename>" with the cable out and in. Particularly note the "Link detected" line at the bottom. "nmcli d" "nmcli c | grep ethernet"
[…]
Anything in the logs?
Nothing in the journalctl -r listing as far as I can see when the RJ45 is removed or inserted.
Strange.
Terminate the NetworkManager service and the same ifup command offloads to something else, gets the DHCP going and it works fine.
The journalctl output at that time would be very interesting.
test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.o rg
On 04/01/2016 07:48 AM, Russel Winder wrote:
The latest NetworkManager upgrade appears to have fixed the WiFi connection on the T500, which is great :-)
And, it now automatically detects the RJ45 wired Ethernet and responds properly. Double yay! :-))
I guess the proposed experimenting is now redundant, or is it worth trying anyway?
Only if you want to create a baseline in case something happens again.
One command that should know about is "journalctl -f". This gives you a live stream of log entries as they happen. Very useful for this case. When that is running, you can see immediately if anything happens when you plug or unplug the ethernet cable.
There was a bug in NM which was fixed[0]. I guess you have this one.
[0] https://bugzilla.gnome.org/show_bug.cgi?id=764332
On Fri, Apr 1, 2016 at 5:58 PM Samuel Sieb samuel@sieb.net wrote:
On 04/01/2016 07:48 AM, Russel Winder wrote:
The latest NetworkManager upgrade appears to have fixed the WiFi connection on the T500, which is great :-)
And, it now automatically detects the RJ45 wired Ethernet and responds properly. Double yay! :-))
I guess the proposed experimenting is now redundant, or is it worth trying anyway?
Only if you want to create a baseline in case something happens again.
One command that should know about is "journalctl -f". This gives you a live stream of log entries as they happen. Very useful for this case. When that is running, you can see immediately if anything happens when you plug or unplug the ethernet cable. -- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
-
Igor Gnatenko -
Russel Winder -
Samuel Sieb