<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 10 November 2016 at 16:38, M. Fioretti <span dir="ltr"><<a href="mailto:mfioretti@nexaima.net" target="_blank">mfioretti@nexaima.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On 2016-11-10 16:17, Liam Proven wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 10 November 2016 at 13:37, M. Fioretti <<a href="mailto:mfioretti@nexaima.net" target="_blank">mfioretti@nexaima.net</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Today I did, and found out that<br>
lspci -k | grep -EA2 'Eth|Net' does list both Wifi chip (Broadcom<br>
Corporation BCM4313, and the Ethernet controller (Realtek RFL8101)<br>
<br>
but networkctl -a only lists the lo interface, and<br>
</blockquote>
<br>
<br>
Connect a USB Ethernet or Wifi adaptor and do a full system upgrade?<br>
<br>
Also, upgrade your firmware, if possible?<br>
</blockquote>
<br></span>
Hi Liam,<br>
<br>
First, a sincere, general question: upgrading firmware doesn't hurt, of course,<br>
but WHY should it make a difference in this specific case, where everything<br>
still works fine under windows, and (afair, at least) no upgrade was done that could<br>
have caused settings to be messed up?<br></blockquote><div><br></div><div>I have more than once fixed a problem by upgrading mother board firmware even when the release notes for the upgrade did not seem to bear any relation to the problem experienced. The fact that the problem appeared following a s/w upgrade does not mean it will not be fixed by upgrading the firmware. Perhaps the kernel uses an interface in a different way and that is causing he problem. If you mess around for ages and then finally upgrade the firmware and that fixes it you will feel a bit silly. That is exactly what happened to me on one occasion. My philosophy is that if there is something that you know is fixable (and there would not be an upgrade to the firmware unless it fixes *something*) and it is fairly easy to do then do it.<br></div><div><br>>...<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
About the full system upgrade: even if a USB ethernet or wifi<br>
adaptor would be detected by a system currently broken as this,<br>
I'm afraid is not a viable option. For family reasons this machine<br>
can't be moved from home right now, but at home we have only a VERY slow<br>
instable connection. Fetching the necessary packages or any other files from another computer/place,<br>
and then feeding them to this laptop via an USB drive is doable though.<br></blockquote><div><br></div><div>Again I think you really must do this. Particularly as you think an upgrade may have caused the problem. Perhaps there was a problem and it has now been fixed and a new release made. Again you will feel silly if you do not do this and eventually discover that an upgrade did fix it.<br><br></div><div>In another post you said you had re-typed an error message rather than copying/pasting. It is far better to copy/paste as sometimes the devil is in the detail. You can copy from the terminal using Ctrl+Shift+C.<br><br></div><div>Meanwhile it may be worth looking in syslog at the bootup sequence to see if there are any networking errors reported.<br></div><div><br>Colin<br></div><br></div></div></div>