Hello Roman, hello List, I installed this kernel-update this night and after that I have a problem with my network-card. I'm running SuSE 8.1 on a Puretec-Root-Server with a network-card that uses the 8139too module. I can boot into a rescue-system and in the /var/log/boot.msg I see the following error:
Ok, it somehow can't find the nic driver module. See if
depmod -a rcnetwork start
solves the problem.
I have the same card in my machine at home, but I'm using the rtl8139 driver (not 8139too).
Fine thing if you have direct access to your server. Not fine if it is somewhere in a serverfarm and can only be remoted via ssh or confix-lite. I think SuSE updates should be more reliable while the update runs. Had a similar problem with intel pro/100 nic on SuSE 7.3. While yast ran my server got out of control. For good sake a friend of me rebooted the server some hours later. The logs in /var/log/allmessages did not show the problem and nothing in /var/log/y2*. Debugging is not enabled in my kernel, so I cannot find the reason for this crash. The y2* logs even did not show me updates to the kernel. Now I'm scared to update any other servers running SuSE. Remark: I run Red Hat and Debian as well. With both distributions I never had problems with any updates and followed reboots of each system. Debian wins any uptimes and is totally free so I decide to change.
vi /etc/modules.conf and search the file for all occurrences of eth0. The (only) line should be close to the top. Remove the "too" from the module name, run depmod -a;rcnetwork start and see if it works.
This should be the part of the update and not of the user itself! Philippe