![]() I have had this happen twice, once when I applied patches during the install routine, and once after running through the install routine and updating using Yast on a seemingly stable system. But once updates are applied, both nics in the machine are registered as hardware in YAST, but will not activate. They seem to work physically - indicator lights. After reboot, my ethernet interfaces are non-functioning. When I download and apply the recommended packages a new kernel install recommends a reboot. SLES wants to apply patches right after registration, which seems reasonable to me. I am kind of OK with that in an academic sense, but my next problem has really stumped me. I can get the OES media to register as a source for add on's, and there are no explicit errors about the OES failures, just repeated messages that say something to the effect of 'The module 'something_oes_somethingelse is not working.' The module name changes, and these problems only come up during the 'OES Install' portion of the server setup. ![]() First, I can get SLES installed with no problems, but the OES install (which I am trying to install as add on software during the SLES install) seems to fail. So, setting out I am running into 2 distinct problems. ![]() For work I am tasked with installing Suse Linux Enterprise Server 10 SP3 and Open Enterprise Server 2 SP3, both 64bit, first in a test environment, and then into production - you know the drill. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |