Listmates,
I ran into an annoying bug with Yast -> Network Device _not_ restarting eth0 after making changes to a network card. This was incredibly frustrating to have to run back across town to the office after the ssh connection went dead. Yast correctly created /etc/sysconfig/ifcfg-eth0, but then for some reason just did not restart the device. I get to the office and loopback is the only device shown with ifconfig. A simply ifup eth0 started the card just fine.
This is a brand new install of 11.0. The card is activated on boot using traditional ifup and the card comes up fine. The install DVD media was verified and no errors occurred during the install. I have 4 other 11.0 installs and this is the only time I have seen this behavior. However, this is the only x86_64 fixed IP install I have that is working with traditional ifup. I have my x86_64 laptop, but that is using network manager.
All 32-bit installs with fixed IP's work fine. Has anyone else experienced this "feature" with a fixed IP and x86_64?
-- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com I have a similar problem with a wireless connection. It never starts first time after a reboot, I always have to go into Yast->Network Devices and select
On Sunday 19 October 2008 07:19:02 David C. Rankin wrote: the adaptor, click edit (not change anything), click next etc. finish and then it starts up. Strange? Phil -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org