[opensuse] Flag this message Kernel update kills networking
Today, the kernel for my 11.0 64 bit system was updated and now I have no networking at all. In Yast, Network settings, I can't even see the NIC listed. When I try to go to the "Overview" tab, it tries for a couple of minutes to display something and then stops with no NIC listed. What would be the easiest way to recover from this, considering that computer no longer has network access? tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Aug 20, 2009 at 01:42:59PM -0400, James Knott wrote:
Today, the kernel for my 11.0 64 bit system was updated and now I have no networking at all. In Yast, Network settings, I can't even see the NIC listed. When I try to go to the "Overview" tab, it tries for a couple of minutes to display something and then stops with no NIC listed. What would be the easiest way to recover from this, considering that computer no longer has network access?
A good approach would be to have the old kernel still available. This
is possible with the help of the multiversion setting of
/etc/zypp/zypp.conf. The multiversion might be introduced with the
openSUSE 11.1 code base. Please check your current /etc/zypp/zypp.conf
for a line beginning with the word "multiversion".
You might downgrade the all your kernel packages to the previously used
version. The kernel packages are available from
http://download.openSUSE.org/pub/opensuse/update/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2009-08-20 at 22:50 +0200, Lars Müller wrote:
On Thu, Aug 20, 2009 at 01:42:59PM -0400, James Knott wrote:
Today, the kernel for my 11.0 64 bit system was updated and now I have no networking at all. In Yast, Network settings, I can't even see the NIC listed. When I try to go to the "Overview" tab, it tries for a couple of minutes to display something and then stops with no NIC listed. What would be the easiest way to recover from this, considering that computer no longer has network access?
A good approach would be to have the old kernel still available. This is possible with the help of the multiversion setting of /etc/zypp/zypp.conf. The multiversion might be introduced with the openSUSE 11.1 code base. Please check your current /etc/zypp/zypp.conf for a line beginning with the word "multiversion".
You might downgrade the all your kernel packages to the previously used version. The kernel packages are available from http://download.openSUSE.org/pub/opensuse/update/
He has no longer any network, remember. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkqN2sQACgkQtTMYHG2NR9X9NgCeOytDYB4rQw4gR86/JRAfSMwQ o5oAn1yaYtSkl+ebw4YMCwbMq7ugKbjR =1DGM -----END PGP SIGNATURE-----
Carlos E. R. wrote:
On Thursday, 2009-08-20 at 22:50 +0200, Lars Müller wrote:
On Thu, Aug 20, 2009 at 01:42:59PM -0400, James Knott wrote:
Today, the kernel for my 11.0 64 bit system was updated and now I have no networking at all. In Yast, Network settings, I can't even see the NIC listed. When I try to go to the "Overview" tab, it tries for a couple of minutes to display something and then stops with no NIC listed. What would be the easiest way to recover from this, considering that computer no longer has network access?
A good approach would be to have the old kernel still available. This is possible with the help of the multiversion setting of /etc/zypp/zypp.conf. The multiversion might be introduced with the openSUSE 11.1 code base. Please check your current /etc/zypp/zypp.conf for a line beginning with the word "multiversion".
You might downgrade the all your kernel packages to the previously used version. The kernel packages are available from http://download.openSUSE.org/pub/opensuse/update/
He has no longer any network, remember.
I do have another computer, so perhaps I can copy it to a flash drive & copy it over. BTW, I wonder where that "Flag this message" in the subject came from? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Lars Müller wrote:
On Thu, Aug 20, 2009 at 01:42:59PM -0400, James Knott wrote:
Today, the kernel for my 11.0 64 bit system was updated and now I have no networking at all. In Yast, Network settings, I can't even see the NIC listed. When I try to go to the "Overview" tab, it tries for a couple of minutes to display something and then stops with no NIC listed. What would be the easiest way to recover from this, considering that computer no longer has network access?
A good approach would be to have the old kernel still available. This is possible with the help of the multiversion setting of /etc/zypp/zypp.conf. The multiversion might be introduced with the openSUSE 11.1 code base. Please check your current /etc/zypp/zypp.conf for a line beginning with the word "multiversion".
You might downgrade the all your kernel packages to the previously used version. The kernel packages are available from http://download.openSUSE.org/pub/opensuse/update/
You're able to downgrade with the help of
rpm -ivh --oldversion <list of kernel rpm packages>
Usually you need to install kernel-default, kernel-default-base, kernel-default-extra.
Before you do this please check with
rpm -qa --last | grep ^kernel-
which particular kernel flavour you currently use.
I'm not sure if it's possible to drive such a roll back from inside YaST. Maybe this requires yet another feature request.
Lars
I don't have that multiversion line. So, I just download the kernel RPM and install? Is there anything else I need? The package I've downloaded is kernel-default-2.6.25.18-0.2.x86_64.rpm, which appears to be the one prior to the one installed today. tnx -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Lars Müller wrote:
On Thu, Aug 20, 2009 at 01:42:59PM -0400, James Knott wrote:
Today, the kernel for my 11.0 64 bit system was updated and now I have no networking at all. In Yast, Network settings, I can't even see the NIC listed. When I try to go to the "Overview" tab, it tries for a couple of minutes to display something and then stops with no NIC listed. What would be the easiest way to recover from this, considering that computer no longer has network access?
A good approach would be to have the old kernel still available. This is possible with the help of the multiversion setting of /etc/zypp/zypp.conf. The multiversion might be introduced with the openSUSE 11.1 code base. Please check your current /etc/zypp/zypp.conf for a line beginning with the word "multiversion".
You might downgrade the all your kernel packages to the previously used version. The kernel packages are available from http://download.openSUSE.org/pub/opensuse/update/
You're able to downgrade with the help of
rpm -ivh --oldversion <list of kernel rpm packages>
Usually you need to install kernel-default, kernel-default-base, kernel-default-extra.
Before you do this please check with
rpm -qa --last | grep ^kernel-
which particular kernel flavour you currently use.
I'm not sure if it's possible to drive such a roll back from inside YaST. Maybe this requires yet another feature request.
Lars
That rpm query shows the kernel that was installed today. Also, I only see the one package that I mentioned in another note. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Aug 20, 2009 at 01:42:59PM -0400, James Knott wrote:
Today, the kernel for my 11.0 64 bit system was updated and now I have no networking at all. In Yast, Network settings, I can't even see the NIC listed. When I try to go to the "Overview" tab, it tries for a couple of minutes to display something and then stops with no NIC listed. What would be the easiest way to recover from this, considering that computer no longer has network access?
rpm -qa |grep kernel please. It might be that only kernel-flavour-base was upgraded, not kernel-flavour itself with the funny modules. :( Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
James Knott wrote:
Today, the kernel for my 11.0 64 bit system was updated and now I have no networking at all. In Yast, Network settings, I can't even see the NIC listed. When I try to go to the "Overview" tab, it tries for a couple of minutes to display something and then stops with no NIC listed. What would be the easiest way to recover from this, considering that computer no longer has network access?
tnx jk
This problem is resolved, with a bit of a bizarre cause. After installing the kernel update, I decided to shut down my computer and rearrange the equipment connected to my UPSs, including an ethernet switch. After powering everything back up, I had no networking. By pulling the ethernet cable from my computer to the switch, I could see the change in the switch LEDs. I could also see the same, when I unplugged my WiFi/router, so it appeared the switch was OK. I was able to use my notebook, as it connected to the router via WiFi and did not pass through the switch. The clue was when I tried to update the software on my Blu-ray player and it complained it couldn't connect. The player is on the same ethernet switch as the failed computer. I then powered down & up the switch again and all was well. Even the network settings in Yast was back to normal. Wierd! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 22 August 2009 02:20:07 James Knott wrote:
James Knott wrote:
Today, the kernel for my 11.0 64 bit system was updated and now I have no networking at all. In Yast, Network settings, I can't even see the NIC listed. When I try to go to the "Overview" tab, it tries for a couple of minutes to display something and then stops with no NIC listed. What would be the easiest way to recover from this, considering that computer no longer has network access?
tnx jk
This problem is resolved, with a bit of a bizarre cause. After installing the kernel update, I decided to shut down my computer and rearrange the equipment connected to my UPSs, including an ethernet switch. After powering everything back up, I had no networking. By pulling the ethernet cable from my computer to the switch, I could see the change in the switch LEDs. I could also see the same, when I unplugged my WiFi/router, so it appeared the switch was OK. I was able to use my notebook, as it connected to the router via WiFi and did not pass through the switch. The clue was when I tried to update the software on my Blu-ray player and it complained it couldn't connect. The player is on the same ethernet switch as the failed computer. I then powered down & up the switch again and all was well. Even the network settings in Yast was back to normal.
Wierd!
It is possible that the switch uses an arp cache to keep track of the MAC addresses of the device plugged into each port. If you plugged devices into different ports from what they were previously plugged into without power- cycling the switch, it may have used its cached arp table instead of refreshing it, thus trying to switch packets to specific devices via the wrong ports. We have a number of HP switches in our company network that can exhibit exactly this behaviour. Power cycling the switch would flush the switch's arp cache forcing it to relearn what devices are on what ports, restoring connectivity. BTW, when I say "arp cache", the switch doesn't necessarily use arp but rather sniffs the packets on each port and thus learns the mac addresses that way. You could confirm this by deliberately switching a couple of ports around and seeing what effect it has. OTOH, it may have just been a one-off glitch... -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au =================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Rodney Baker wrote:
On Saturday 22 August 2009 02:20:07 James Knott wrote:
James Knott wrote:
Today, the kernel for my 11.0 64 bit system was updated and now I have no networking at all. In Yast, Network settings, I can't even see the NIC listed. When I try to go to the "Overview" tab, it tries for a couple of minutes to display something and then stops with no NIC listed. What would be the easiest way to recover from this, considering that computer no longer has network access?
tnx jk
This problem is resolved, with a bit of a bizarre cause. After installing the kernel update, I decided to shut down my computer and rearrange the equipment connected to my UPSs, including an ethernet switch. After powering everything back up, I had no networking. By pulling the ethernet cable from my computer to the switch, I could see the change in the switch LEDs. I could also see the same, when I unplugged my WiFi/router, so it appeared the switch was OK. I was able to use my notebook, as it connected to the router via WiFi and did not pass through the switch. The clue was when I tried to update the software on my Blu-ray player and it complained it couldn't connect. The player is on the same ethernet switch as the failed computer. I then powered down & up the switch again and all was well. Even the network settings in Yast was back to normal.
Wierd!
It is possible that the switch uses an arp cache to keep track of the MAC addresses of the device plugged into each port. If you plugged devices into different ports from what they were previously plugged into without power- cycling the switch, it may have used its cached arp table instead of refreshing it, thus trying to switch packets to specific devices via the wrong ports.
We have a number of HP switches in our company network that can exhibit exactly this behaviour.
Power cycling the switch would flush the switch's arp cache forcing it to relearn what devices are on what ports, restoring connectivity. BTW, when I say "arp cache", the switch doesn't necessarily use arp but rather sniffs the packets on each port and thus learns the mac addresses that way.
You could confirm this by deliberately switching a couple of ports around and seeing what effect it has.
OTOH, it may have just been a one-off glitch...
I didn't move any ethernet cables, just power plugs on the UPSs. Also, an arp cache would not survive a power down, which had occurred when I moved the ethernet switch from one UPS to the other. For some reason, the switch could receive data, as evidenced by the flashing LEDs, but not transmit. Whatever it was doing, was enough to cause problems for network settings in Yast. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Carlos E. R. -
James Knott -
Lars Müller -
Marcus Meissner -
Rodney Baker