my answers == After opening the session and invoking YAST as previously explained the network connection works and other software dependent upon this connection works. I use STATIC IP ADDRESSES not DHCP. Although during the session and after using YAST everything with that interface works okay. But when I
Anders you asked << What does this mean? That the network connection works, and you're only concerned about a message during boot? Or do you have to do something actively to start the network connection? power down and reboot then the boot message correctly identifies that the boot process finds the network card hardware (3c509c) as "not (yet?) active and also on a second line while examining the hardware address -- in the form of some kind of count down -- producing the meassage "no interface found". YAST makes this hardware work but it does not work on the following boot up. == Here are the boot messages: == Warning: interface eth-id-00:50:04:22:24:58 is not (yet?) active. Warning: No interface active (yet?) ------------------------------------done Waiting for mandatory devices: eth-id-00:50:04:22:24:58 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 eth-id-00:50:04:22:24:58 No interface found--------------failed == I must enter a session after boot up and use YAST and then just for that session the eth0 interface works. I can send you the routing information or any other information. It is obvious that the interface does not come alive and perform as it should until I use YAST as explained and then only for the current session. Thanks -- TED