[opensuse] Need help with a broken network stack of Leap 42.3
The user contacted me yesterday alarmed saying: I just did some updates (days ago), at the end of the session I did shutdown. Now after a few days when I want to use the PC I have no network. I am only able to give advice via the phone, so all is quite complicated, user has a very low preparation in IT, so is easily "emotionally exhausted" and even easier frustrated. Therefore, less is more when it comes to “trial and error”. So what I did find (and do not really understand). Hardware: system is a ASUS M5A97 EVO R2.0 and has as eth a: Realtek 8111F Gigabit LAN controller Prior to the incident the card was recognized flawlessly. Manual: https://dlcdnets.asus.com/pub/ASUS/mb/SocketAM3+/M5A97-EVO_R2.0/ E8045_M5A97_EVO_R20_V2_WEB.pdf The system has a Wlan card and a eth card. But both seem to be out of funktion. It is branched to a Fritzbox AVM 7490 INT. There have been no changes in the router setting. User checked for network cables. So I can virtually exclude a router problem (has been rebooted for the sake of doing it) and the router resolves as it is possible to use a smartphone via WLAN to surf. The PC used networkmanager to handle the network. sudo ifup says correctly: handled by networkmanager skipping. O.K. In the network manager the connections are there, the settings correct. First observation: to my astonishment neither eth nor wlan is seen by the system (which raises in me the idea of an incomplete kernel update?). I tired to force a new /etc/resolv.conf , which worked by makes no difference, so it is not a question of address resolution either. So I went to yast and made the networkmanager deactivated and went to wicked. Now wicked says: there are three! eth cards, and one wlan card. two (eth0 configured) and wlan (non configured) the new one eth is not configured. Both eth cards have the same mac and the same brand so I am sure this is a double entry somewhere. I asked wicked to eliminate the "configured" eth and did let restart the network stack. Now I have just two cards revealed as expected. eth0 and wlan. The chipset is a Realtech card (Realtek 8111F) as expected. Now question: Have there been changes to the Realtech 8111F firmware in opensuse Leap recently? Is there any known breakage and how to deal with it. How can I get a meaningful dmesg (I do not know what error to search for) as in demsg I was not able to find (better the user for me) any message of failure. When I do try to set up the card in wicked it complains about the firmware and tells me to look for further information in dmesg. So I am stuck in the moment, as I do not understand what is wrong. It would be possible to do tethering with BT via the smartphone with the machine as BT is offered as networkstack in networkmanager. So I could try a zypper up to look for changes but given that the volume of these contracts are not endless, I would like to be more precise and just repaire the network and do the rest with the flat contract for dsl. If anybody has suggestion how to debug this, I would be really greatful. What else could be compromised to deactivate wlan and eth in networkmanager. It must be the firmware no? _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov wrote:
The user contacted me yesterday alarmed saying: I just did some updates (days ago), at the end of the session I did shutdown. Now after a few days when I want to use the PC I have no network.
I am only able to give advice via the phone, so all is quite complicated, user has a very low preparation in IT, so is easily "emotionally exhausted" and even easier frustrated. Therefore, less is more when it comes to “trial and error”.
So what I did find (and do not really understand). Hardware: system is a ASUS M5A97 EVO R2.0 and has as eth a: Realtek 8111F Gigabit LAN controller Prior to the incident the card was recognized flawlessly. Manual: https://dlcdnets.asus.com/pub/ASUS/mb/SocketAM3+/M5A97-EVO_R2.0/ E8045_M5A97_EVO_R20_V2_WEB.pdf
The system has a Wlan card and a eth card. But both seem to be out of funktion.
Can you get us more information on exactly how those interface seem to be "out of funktion" ? it would be useful to see output from "ip addr" for instance.
It is branched to a Fritzbox AVM 7490 INT. There have been no changes in the router setting. User checked for network cables. So I can virtually exclude a router problem (has been rebooted for the sake of doing it) and the router resolves as it is possible to use a smartphone via WLAN to surf.
Okay, that's good. So problem has been isolated to the upgraded machine.
The PC used networkmanager to handle the network. sudo ifup says correctly: handled by networkmanager skipping. O.K. In the network manager the connections are there, the settings correct. First observation: to my astonishment neither eth nor wlan is seen by the system
"seen by the system" ? how - lspci? in dmesg output?
How can I get a meaningful dmesg (I do not know what error to search for) as in demsg I was not able to find (better the user for me) any message of failure. When I do try to set up the card in wicked it complains about the firmware and tells me to look for further information in dmesg. So I am stuck in the moment, as I do not understand what is wrong.
What exactly does wicked say? Post the dmesg output to paste.o.o, if you can. Maybe check this article: https://medium.com/@lgobinath/no-ethernet-connection-in-ubuntu-16-04-linux-m... -- Per Jessen, Zürich (4.1°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov wrote:
The user contacted me yesterday alarmed saying: I just did some updates (days ago), at the end of the session I did shutdown. Now after a few days when I want to use the PC I have no network.
Are these not the symptoms seen by a couple of people recently and discussed on this list (or its opensuse-support twin). Some bug in an update that corrupted a network file and was cured by some magic network incantation to force it to rewrite the file? Sorry, I wasn't very interested and don't remember any more but hopefully somebody else will, or searching the recent archives might find the thread. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data venerdì 15 febbraio 2019 13:28:50 CET, Dave Howorth ha scritto:
stakanov wrote:
The user contacted me yesterday alarmed saying: I just did some updates (days ago), at the end of the session I did shutdown. Now after a few days when I want to use the PC I have no network.
Are these not the symptoms seen by a couple of people recently and discussed on this list (or its opensuse-support twin). Some bug in an update that corrupted a network file and was cured by some magic network incantation to force it to rewrite the file?
Sorry, I wasn't very interested and don't remember any more but hopefully somebody else will, or searching the recent archives might find the thread. That sounds right. I am registered in theory to this list. Never received any mail however. Very annoying BTW. Thank for the heads up.
_________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Dave Howorth <dave@howorth.org.uk> [02-15-19 07:29]:
stakanov wrote:
The user contacted me yesterday alarmed saying: I just did some updates (days ago), at the end of the session I did shutdown. Now after a few days when I want to use the PC I have no network.
Are these not the symptoms seen by a couple of people recently and discussed on this list (or its opensuse-support twin). Some bug in an update that corrupted a network file and was cured by some magic network incantation to force it to rewrite the file?
Sorry, I wasn't very interested and don't remember any more but hopefully somebody else will, or searching the recent archives might find the thread.
netconfig update -f cp /etc/resolv.conf /var/run/netconfig/resolv.conf ln -s /var/run/netconfig/resolv.conf /etc/resolv.conf -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data venerdì 15 febbraio 2019 13:53:32 CET, Patrick Shanahan ha scritto:
* Dave Howorth <dave@howorth.org.uk> [02-15-19 07:29]:
stakanov wrote:
The user contacted me yesterday alarmed saying: I just did some updates (days ago), at the end of the session I did shutdown. Now after a few days when I want to use the PC I have no network.
Are these not the symptoms seen by a couple of people recently and discussed on this list (or its opensuse-support twin). Some bug in an update that corrupted a network file and was cured by some magic network incantation to force it to rewrite the file?
Sorry, I wasn't very interested and don't remember any more but hopefully somebody else will, or searching the recent archives might find the thread.
netconfig update -f cp /etc/resolv.conf /var/run/netconfig/resolv.conf ln -s /var/run/netconfig/resolv.conf /etc/resolv.conf Patrick. Thank you! I will make this try ASAP and report it here Regards
_________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* stakanov <stakanov@eclipso.eu> [02-15-19 08:06]:
In data venerdì 15 febbraio 2019 13:53:32 CET, Patrick Shanahan ha scritto:
* Dave Howorth <dave@howorth.org.uk> [02-15-19 07:29]:
stakanov wrote:
The user contacted me yesterday alarmed saying: I just did some updates (days ago), at the end of the session I did shutdown. Now after a few days when I want to use the PC I have no network.
Are these not the symptoms seen by a couple of people recently and discussed on this list (or its opensuse-support twin). Some bug in an update that corrupted a network file and was cured by some magic network incantation to force it to rewrite the file?
Sorry, I wasn't very interested and don't remember any more but hopefully somebody else will, or searching the recent archives might find the thread.
netconfig update -f cp /etc/resolv.conf /var/run/netconfig/resolv.conf ln -s /var/run/netconfig/resolv.conf /etc/resolv.conf Patrick. Thank you! I will make this try ASAP and report it here Regards
may fail if you follow exactly, probably need to: mv /etc/resolv.conf /var/run/netconfig/resolv.conf instead of cp or setting the link will fail with existing filename -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan wrote:
may fail if you follow exactly, probably need to: mv /etc/resolv.conf /var/run/netconfig/resolv.conf instead of cp or setting the link will fail with existing filename
My 42.3 machines don't have /var/run/netconfig/resolv.conf I think Per is right that that issue is/was only relevant for TW. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data venerdì 15 febbraio 2019 14:27:01 CET, Peter Suetterlin ha scritto:
Patrick Shanahan wrote:
may fail if you follow exactly, probably need to: mv /etc/resolv.conf /var/run/netconfig/resolv.conf
instead of cp or setting the link will fail with existing filename
My 42.3 machines don't have /var/run/netconfig/resolv.conf I think Per is right that that issue is/was only relevant for TW. Astonishingly that machine HAD /etc/netconfig/resolv.conf(!) I did "recycle bin" it but it can be recovered.
So for my (very special case indeed, me myself do not have it in Leap so I am surprised..), I will follow the advice of Patrick and also take note of the pitfalls / failures. At latest Sunday we shall know if it is top or flop and nobody's advice will be "vane" because "poor soul "me, will try them all in order :-p Of course you will be given no credit(!) and I will prostrate myself to the user as "God on earth" in case it works, while I will wittily discharge all responsibilities on the forum if it fails. As usual no? Seriously thank you for the input. I have now a bit of hope to get that fixed. Thank you to all of you of course. (And now I will take care of my worship image :-p ) _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* stakanov <stakanov@eclipso.eu> [02-15-19 08:50]:
In data venerdì 15 febbraio 2019 14:27:01 CET, Peter Suetterlin ha scritto:
Patrick Shanahan wrote:
may fail if you follow exactly, probably need to: mv /etc/resolv.conf /var/run/netconfig/resolv.conf
instead of cp or setting the link will fail with existing filename
My 42.3 machines don't have /var/run/netconfig/resolv.conf I think Per is right that that issue is/was only relevant for TW. Astonishingly that machine HAD /etc/netconfig/resolv.conf(!) I did "recycle bin" it but it can be recovered.
you should recover it as that is not one of the files cited.
So for my (very special case indeed, me myself do not have it in Leap so I am surprised..), I will follow the advice of Patrick and also take note of the pitfalls / failures. At latest Sunday we shall know if it is top or flop and nobody's advice will be "vane" because "poor soul "me, will try them all in order :-p Of course you will be given no credit(!) and I will prostrate myself to the user as "God on earth" in case it works, while I will wittily discharge all responsibilities on the forum if it fails. As usual no?
incantations will not help your system and probably nothing else
Seriously thank you for the input. I have now a bit of hope to get that fixed. Thank you to all of you of course. (And now I will take care of my worship image :-p )
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan wrote:
* stakanov <stakanov@eclipso.eu> [02-15-19 08:50]:
Astonishingly that machine HAD /etc/netconfig/resolv.conf(!) I did "recycle bin" it but it can be recovered.
you should recover it as that is not one of the files cited.
Hmm, I wonder where it came from - here, /etc/netconfig is a file, not a directory. Either that has changed in the latest updates, or it might be the reason for the problems, as you cannot overwrite a directory with a file? In doubt you could try to remove the /etc/netconfig directory, and then run the magic 'netconfig -f' -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data venerdì 15 febbraio 2019 15:23:03 CET, Peter Suetterlin ha scritto:
Patrick Shanahan wrote:
* stakanov <stakanov@eclipso.eu> [02-15-19 08:50]:
Astonishingly that machine HAD /etc/netconfig/resolv.conf(!) I did "recycle bin" it but it can be recovered.
you should recover it as that is not one of the files cited.
Hmm, I wonder where it came from - here, /etc/netconfig is a file, not a directory. Either that has changed in the latest updates, or it might be the reason for the problems, as you cannot overwrite a directory with a file?
In doubt you could try to remove the /etc/netconfig directory, and then run the magic 'netconfig -f' I would also be seriously interested to know why the user had (in 42.3) a setup that, with a very similar machine I had not in 42.3, 15.0 upg. Maybe a result of making use of kde connect?
_________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* stakanov <stakanov@eclipso.eu> [02-15-19 09:57]:
In data venerdì 15 febbraio 2019 15:23:03 CET, Peter Suetterlin ha scritto:
Patrick Shanahan wrote:
* stakanov <stakanov@eclipso.eu> [02-15-19 08:50]:
Astonishingly that machine HAD /etc/netconfig/resolv.conf(!) I did "recycle bin" it but it can be recovered.
you should recover it as that is not one of the files cited.
Hmm, I wonder where it came from - here, /etc/netconfig is a file, not a directory. Either that has changed in the latest updates, or it might be the reason for the problems, as you cannot overwrite a directory with a file?
In doubt you could try to remove the /etc/netconfig directory, and then run the magic 'netconfig -f'
I would also be seriously interested to know why the user had (in 42.3) a setup that, with a very similar machine I had not in 42.3, 15.0 upg. Maybe a result of making use of kde connect?
that should not be pertinent. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data venerdì 15 febbraio 2019 15:58:13 CET, Patrick Shanahan ha scritto:
* stakanov <stakanov@eclipso.eu> [02-15-19 09:57]:
In data venerdì 15 febbraio 2019 15:23:03 CET, Peter Suetterlin ha scritto:
Patrick Shanahan wrote:
* stakanov <stakanov@eclipso.eu> [02-15-19 08:50]:
Astonishingly that machine HAD /etc/netconfig/resolv.conf(!) I did "recycle bin" it but it can be recovered.
you should recover it as that is not one of the files cited.
Hmm, I wonder where it came from - here, /etc/netconfig is a file, not a directory. Either that has changed in the latest updates, or it might be the reason for the problems, as you cannot overwrite a directory with a file?
In doubt you could try to remove the /etc/netconfig directory, and then run the magic 'netconfig -f'
I would also be seriously interested to know why the user had (in 42.3) a setup that, with a very similar machine I had not in 42.3, 15.0 upg. Maybe a result of making use of kde connect?
that should not be pertinent. Which is a pity because the rational for asking myself this is, how can I understand what happened to cause this. If the issue is just bound to some update or a legacy of past installs, then I am fairly sure no action has to be taken. But it would be stupid the user did that action and, unaware it was determining the problem, does it again... It is just to avoid a repetition. (You can guess already that I like Paganini in these cases).
_________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov wrote:
Which is a pity because the rational for asking myself this is, how can I understand what happened to cause this. If the issue is just bound to some update or a legacy of past installs, then I am fairly sure no action has to be taken. But it would be stupid the user did that action and, unaware it was determining the problem, does it again... It is just to avoid a repetition. (You can guess already that I like Paganini in these cases).
I would definitely look if there are some packages from non-standard repos. Either the user had tweaked something by hand, changing config files, or maybe installed something like a package from, e.g., fedora, that has a different structure in the /etc config files? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data sabato 16 febbraio 2019 18:30:47 CET, Peter Suetterlin ha scritto:
stakanov wrote:
Which is a pity because the rational for asking myself this is, how can I understand what happened to cause this. If the issue is just bound to some update or a legacy of past installs, then I am fairly sure no action has to be taken. But it would be stupid the user did that action and, unaware it was determining the problem, does it again... It is just to avoid a repetition. (You can guess already that I like Paganini in these cases).
I would definitely look if there are some packages from non-standard repos. Either the user had tweaked something by hand, changing config files, or maybe installed something like a package from, e.g., fedora, that has a different structure in the /etc config files? I checked for the repos and did not find in-congruence (e.g. all are 42.3 opensuse, and packman. This seems however maybe an issue with an update as two other users encountered issues AFAIK. I will have the user on the phone for "open heart operation over the wire" on Sunday. This should at least give me some insight. dmesg output would be good to have it. Journalctl also. Any other suggestions?
_________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan wrote:
* Dave Howorth <dave@howorth.org.uk> [02-15-19 07:29]:
stakanov wrote:
The user contacted me yesterday alarmed saying: I just did some updates (days ago), at the end of the session I did shutdown. Now after a few days when I want to use the PC I have no network.
Are these not the symptoms seen by a couple of people recently and discussed on this list (or its opensuse-support twin). Some bug in an update that corrupted a network file and was cured by some magic network incantation to force it to rewrite the file?
Sorry, I wasn't very interested and don't remember any more but hopefully somebody else will, or searching the recent archives might find the thread.
netconfig update -f cp /etc/resolv.conf /var/run/netconfig/resolv.conf ln -s /var/run/netconfig/resolv.conf /etc/resolv.conf
I thought that was a tumbleweed issue only? -- Per Jessen, Zürich (7.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Per Jessen <per@computer.org> [02-15-19 08:20]:
Patrick Shanahan wrote:
* Dave Howorth <dave@howorth.org.uk> [02-15-19 07:29]:
stakanov wrote:
The user contacted me yesterday alarmed saying: I just did some updates (days ago), at the end of the session I did shutdown. Now after a few days when I want to use the PC I have no network.
Are these not the symptoms seen by a couple of people recently and discussed on this list (or its opensuse-support twin). Some bug in an update that corrupted a network file and was cured by some magic network incantation to force it to rewrite the file?
Sorry, I wasn't very interested and don't remember any more but hopefully somebody else will, or searching the recent archives might find the thread.
netconfig update -f cp /etc/resolv.conf /var/run/netconfig/resolv.conf ln -s /var/run/netconfig/resolv.conf /etc/resolv.conf
I thought that was a tumbleweed issue only?
I cannot remember, blame it on old-timers or ... at present I only have Tw boxes to check. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data venerdì 15 febbraio 2019 11:19:51 CET, Per Jessen ha scritto:
stakanov wrote:
The user contacted me yesterday alarmed saying: I just did some updates (days ago), at the end of the session I did shutdown. Now after a few days when I want to use the PC I have no network.
I am only able to give advice via the phone, so all is quite complicated, user has a very low preparation in IT, so is easily "emotionally exhausted" and even easier frustrated. Therefore, less is more when it comes to “trial and error”.
So what I did find (and do not really understand). Hardware: system is a ASUS M5A97 EVO R2.0 and has as eth a: Realtek 8111F Gigabit LAN controller Prior to the incident the card was recognized flawlessly. Manual: https://dlcdnets.asus.com/pub/ASUS/mb/SocketAM3+/M5A97-EVO_R2.0/ E8045_M5A97_EVO_R20_V2_WEB.pdf
The system has a Wlan card and a eth card. But both seem to be out of funktion.
Can you get us more information on exactly how those interface seem to be "out of funktion" ? it would be useful to see output from "ip addr" for instance. Thank you for the input, I will try to provide asap
It is branched to a Fritzbox AVM 7490 INT. There have been no changes in the router setting. User checked for network cables. So I can virtually exclude a router problem (has been rebooted for the sake of doing it) and the router resolves as it is possible to use a smartphone via WLAN to surf.
Okay, that's good. So problem has been isolated to the upgraded machine.
The PC used networkmanager to handle the network. sudo ifup says correctly: handled by networkmanager skipping. O.K. In the network manager the connections are there, the settings correct. First observation: to my astonishment neither eth nor wlan is seen by the system
"seen by the system" ? how - lspci? in dmesg output?
sudo dmesg output yes. Astonishingly dmesg does not complain (for what reason ever) of missing firmware. If that would be a bug to be addressed. This on board eth chipset is common! (Nearly like nvidia with Thorwalds...Broadcom? f....Broadcom!)
How can I get a meaningful dmesg (I do not know what error to search for) as in demsg I was not able to find (better the user for me) any message of failure. When I do try to set up the card in wicked it complains about the firmware and tells me to look for further information in dmesg. So I am stuck in the moment, as I do not understand what is wrong.
What exactly does wicked say? Post the dmesg output to paste.o.o, if you can.
Diffidult, I can maybe by "copy by hand written story like the old catholic monks!) - just with the gimmick "over the wire oral tradition" - no! Not that intended! obviously by phone (I am not THAT lucky with administration over all :-) ).
Maybe check this article:
https://medium.com/@lgobinath/no-ethernet-connection-in-ubuntu-16-04-linux-m int-18-with-realtek-rtl8111-8168-8411-7ae2779dc9b8
this is the biggest headache. I would rather for that user have hardware (in this case even old hardware) that works just "out of the box". Not blobs or prop driver! _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 15/02/2019 10.26, stakanov wrote:
The user contacted me yesterday alarmed saying: I just did some updates (days ago), at the end of the session I did shutdown. Now after a few days when I want to use the PC I have no network.
I am only able to give advice via the phone, so all is quite complicated, user has a very low preparation in IT, so is easily "emotionally exhausted" and even easier frustrated. Therefore, less is more when it comes to “trial and error”.
Maybe he can send photos taken with mobile phone?
So what I did find (and do not really understand). Hardware: system is a ASUS M5A97 EVO R2.0 and has as eth a: Realtek 8111F Gigabit LAN controller Prior to the incident the card was recognized flawlessly. Manual: https://dlcdnets.asus.com/pub/ASUS/mb/SocketAM3+/M5A97-EVO_R2.0/ E8045_M5A97_EVO_R20_V2_WEB.pdf
The system has a Wlan card and a eth card. But both seem to be out of funktion. It is branched to a Fritzbox AVM 7490 INT. There have been no changes in the router setting. User checked for network cables. So I can virtually exclude a router problem (has been rebooted for the sake of doing it) and the router resolves as it is possible to use a smartphone via WLAN to surf.
The PC used networkmanager to handle the network. sudo ifup says correctly: handled by networkmanager skipping. O.K. In the network manager the connections are there, the settings correct. First observation: to my astonishment neither eth nor wlan is seen by the system (which raises in me the idea of an incomplete kernel update?). I tired to force a new /etc/resolv.conf , which worked by makes no difference, so it is not a question of address resolution either.
So I went to yast and made the networkmanager deactivated and went to wicked. Now wicked says: there are three! eth cards, and one wlan card. two (eth0 configured) and wlan (non configured) the new one eth is not configured. Both eth cards have the same mac and the same brand so I am sure this is a double entry somewhere.
I have seen this after some upgrades.
I asked wicked to eliminate the "configured" eth and did let restart the network stack. Now I have just two cards revealed as expected. eth0 and wlan. The chipset is a Realtech card (Realtek 8111F) as expected. Now question: Have there been changes to the Realtech 8111F firmware in opensuse Leap recently? Is there any known breakage and how to deal with it.
How can I get a meaningful dmesg (I do not know what error to search for) as in demsg I was not able to find (better the user for me) any message of failure. When I do try to set up the card in wicked it complains about the firmware and tells me to look for further information in dmesg. So I am stuck in the moment, as I do not understand what is wrong.
It would be possible to do tethering with BT via the smartphone with the machine as BT is offered as networkstack in networkmanager. So I could try a zypper up to look for changes but given that the volume of these contracts are not endless, I would like to be more precise and just repaire the network and do the rest with the flat contract for dsl.
You could do this to try ssh to the machine and do the testing yourself - but you may be unfortunate as me, because the phone gives me a 10.*.*.* address :-/
If anybody has suggestion how to debug this, I would be really greatful. What else could be compromised to deactivate wlan and eth in networkmanager. It must be the firmware no?
Maybe it is a card that needs firmware, and this fails to load or is missing the package. There was a firmware update recently: kernel-firmware-20190118-lp150.2.12.1.noarch The package is dated "Tue Feb 05 2019", I got it yesterday. So the obvious thing to try is to check what version does he have installed. If it is missing, install it. If it is this one, then install the previous version of that rpm, downloading on another machine, copy to usb stick, etc... -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
In data venerdì 15 febbraio 2019 14:37:18 CET, Carlos E. R. ha scritto:
On 15/02/2019 10.26, stakanov wrote:
The user contacted me yesterday alarmed saying: I just did some updates (days ago), at the end of the session I did shutdown. Now after a few days when I want to use the PC I have no network.
I am only able to give advice via the phone, so all is quite complicated, user has a very low preparation in IT, so is easily "emotionally exhausted" and even easier frustrated. Therefore, less is more when it comes to “trial and error”.
Maybe he can send photos taken with mobile phone?
So what I did find (and do not really understand). Hardware: system is a ASUS M5A97 EVO R2.0 and has as eth a: Realtek 8111F Gigabit LAN controller Prior to the incident the card was recognized flawlessly. Manual: https://dlcdnets.asus.com/pub/ASUS/mb/SocketAM3+/M5A97-EVO_R2.0/ E8045_M5A97_EVO_R20_V2_WEB.pdf
The system has a Wlan card and a eth card. But both seem to be out of funktion. It is branched to a Fritzbox AVM 7490 INT. There have been no changes in the router setting. User checked for network cables. So I can virtually exclude a router problem (has been rebooted for the sake of doing it) and the router resolves as it is possible to use a smartphone via WLAN to surf.
The PC used networkmanager to handle the network. sudo ifup says correctly: handled by networkmanager skipping. O.K. In the network manager the connections are there, the settings correct. First observation: to my astonishment neither eth nor wlan is seen by the system (which raises in me the idea of an incomplete kernel update?). I tired to force a new /etc/resolv.conf , which worked by makes no difference, so it is not a question of address resolution either.
So I went to yast and made the networkmanager deactivated and went to wicked. Now wicked says: there are three! eth cards, and one wlan card. two (eth0 configured) and wlan (non configured) the new one eth is not configured. Both eth cards have the same mac and the same brand so I am sure this is a double entry somewhere.
I have seen this after some upgrades.
I asked wicked to eliminate the "configured" eth and did let restart the network stack. Now I have just two cards revealed as expected. eth0 and wlan. The chipset is a Realtech card (Realtek 8111F) as expected. Now question: Have there been changes to the Realtech 8111F firmware in opensuse Leap recently? Is there any known breakage and how to deal with it.
How can I get a meaningful dmesg (I do not know what error to search for) as in demsg I was not able to find (better the user for me) any message of failure. When I do try to set up the card in wicked it complains about the firmware and tells me to look for further information in dmesg. So I am stuck in the moment, as I do not understand what is wrong.
It would be possible to do tethering with BT via the smartphone with the machine as BT is offered as networkstack in networkmanager. So I could try a zypper up to look for changes but given that the volume of these contracts are not endless, I would like to be more precise and just repaire the network and do the rest with the flat contract for dsl.
You could do this to try ssh to the machine and do the testing yourself - but you may be unfortunate as me, because the phone gives me a 10.*.*.* address :-/
If anybody has suggestion how to debug this, I would be really greatful. What else could be compromised to deactivate wlan and eth in networkmanager. It must be the firmware no?
Maybe it is a card that needs firmware, and this fails to load or is missing the package. There was a firmware update recently:
kernel-firmware-20190118-lp150.2.12.1.noarch
The package is dated "Tue Feb 05 2019", I got it yesterday.
So the obvious thing to try is to check what version does he have installed. If it is missing, install it. If it is this one, then install the previous version of that rpm, downloading on another machine, copy to usb stick, etc...
I had to go back to the snapshot of 17.01.2019. I then converted it to default. Updated 500 mb of updates And the error was away. That to say: the error of wicked was wlan would give no error but eth0: "unable to configure the network card because the kernel device(eth0) is not present. This is mostly caused by missing firmware" So it appears that the device node was either not created correctly or the firmware was not in sync on the update mirror (by chance) and was not installed. In any case now it works. Thank you for the input, sorry for not being useful for finding the exact cause. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Carlos E. R. -
Dave Howorth -
Patrick Shanahan -
Per Jessen -
Peter Suetterlin -
stakanov