https://bugzilla.novell.com/show_bug.cgi?id=335486 User m.van.munnen@hccnet.nl added comment https://bugzilla.novell.com/show_bug.cgi?id=335486#c5 Marc Munnen <m.van.munnen@hccnet.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |m.van.munnen@hccnet.nl Priority|P5 - None |P3 - Medium --- Comment #5 from Marc Munnen <m.van.munnen@hccnet.nl> 2007-12-08 15:10:16 MST --- I just have the same problem. I upgraded Suse 10.2 to 10.3 on two pc's and both refused to load the network cards after booting. I tried almost every configuration option in Yast for my 3 network cards, but only allowing the networkmanager to start them gave me at least one working card. Alas, the other 2 are greyed out and so can't be started. Also advanced routing does not work with the Networkmanager. (And, strange enough, it refuses my netmask of 255.255.255.0 and uses 255.0.0.0) In contrast, when I do a fresh install on both pc's, all network cards are started upon booting as might be expected, with ifup. After logging in on my upgraded pc's I can start them with 'rcnetwork start'. But this is hardly a solution, because I can't tell my friend he has to live with that. So please, please, repair this in some way or the other. I must admit that the Workaround from Walter Haidinger does not ring much bells in me at first sight. Marc -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.