On 2013-08-13 23:05 (GMT+0200) Stefan Seyfried composed:
Felix Miata composed:
[Fresh e17 32 bit HTTP M4 snapshot installation just hours ago]
"A start job is running for LSB: Configure network interfaces and set up routing"
Not timed, but delay estimated at well over 2 minutes. Installation was begun with net.ifnames=0 on cmdline, but networking seems working as intended on eth0. /var/log/warn seems to be the only log with a clue, but I don't recognize what's happening except for some apparent time gaps: http://fm.no-ip.com/Tmp/SUSE/Factory/varlogwarn131m4-gx260.txt
Try "systemd-analyze blame" to see what's taking too long.
first place: 5min 2ms network.service second place: 7.338s systemd-fsck@dev....
And check for "job xxx timed out" messages in "journalctl -b"
http://fm.no-ip.com/Tmp/SUSE/Factory/journalctl-b-gx260-os131m4.txt tail of journalctl - b output shows the five minutes, but it's not terribly clear to me where the problem might lie. First line in the saved tail is: ifup[900]: Aug 13 16:55:27 gx260 network[403]: if-up.d/21-cifs: line 57: /bin/mountpoint: No such file or directory Avahi isn't anything I ever use knowingly. Is /bin/mountpoint something from the failed schrodinger package? /usr/bin/mountpoint does exist. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org