I filed a bug report on 10.0 OSS and 10.1, both seemed to prefer one of two imbedded nics and made it very difficult (multiple yast network device configs) to switch to the "working" nic, the one that the working 9.3 installation on the same computer uses to connect to the cable modem. Well, i got tired of that and changed the cable connection to the "preferred by 10.0" nic, Nvidia brand. Suse 9.3 took to the change immediately, i called up yast once and took care of the eth0 assignment. Well, 10.0 needs at least 5 yast resets of the network device each time i boot to it! Apparently it does not prefer one of the two nics, it just loses track of what's there! For some reason the nic becomes a nonexistent device when connection to it is attempted, that's what i read in the boot log. something wrong with hardware detection/ hardware config retention? any workarounds? I would like to explore 10 and 10.1, but it does get quite bothersome to reset the net connection on each reboot, actually it becomes irritating when the reset has to be tried 4-5-6-7 times before success! btw, the mobo is a DFI socket 939, running a 64 bit AMD 3000 (i think).