Hello, Thank you for your answer. On 9/18/05, Hans-Joachim Ehlers wrote:

Hi Frederico, i have got once on a DELL Client a similar problem. in the file /etc/sysconfig/hardware-bus-pci-........ there was not an entry for the network card. E.a the value for the attribut ' MODULE='MyNetworkCardModule' was missing. After adding the value ( the correct network card module name ) and restarting/rebooting the machine everythink worked fine.

I forgot to see that file, as I said SuSE manual network configuration method is not something that I know very well yet. I can, however, happily announce that I have it sorted, more or less: incredible as it may sound it started working (both interfaces fully configured) after I changed from "Full Installation" to "Minimal". I also changed the LVM config to the new format, but the thing that appears to make a difference is the package selection. Totally bizarre, I can't imagine what can be the interference between this two configuration options. Now that I have everything working I can leave some suggestiong on things that can probably take a bit more fine tunning: o The before mentioned eth-- problem, of course. o When creating the LV's with the new syntax I now get a "lvremove" error on some lv's, complaining about "no such device or address". Everything works if I just ignore the warning. o GRUB refuses to install in some servers (the DL380, actually). The error message I get trough the ILO console is only the GRUB version banner, and no manual ammount of fiddling with the parameters will make it work; installing LILO is the only way to ger past that point. o Not SuSE or autoyast related, but I might as well take the opportunity in the chance that this can be useful to someone: don't ever assume that the PXE boot will go trough the eth0 interface; I had to deconfigure all the VLAN's to make PXE boot to work since it seams to use the interfaces in an absolutely random order. This is something awful not only during th actuall PXE boot, but also during the "pxeboot" DHCP request: not adding a "netdevice=eth2" on some servers would make them request an IP address in a 192.168.0.0 network and it would just freeze. All in all, apart from the above glitches that did take their toll in time, autoyast was very helpful; I was used to FAI and Solaris Jumpstart, and autoyast is a useful adittion to my automatic installation knowledge. Best regards, Frederico Muñoz