On Fri, 29 Aug 2014 00:08:43 +1000
Basil Chupin wrote:
(I skipped quoting)
Let me further confuse the issue for you:
I currently have factory installed on 5 computers (well, 4 computers, 5
partition sets).
For four of those, it was a clean install. Two of those clean
installs were in June (or maybe late may) and updated ("zypper dup")
since. The third clean install was this month (maybe 20140807). The
fourth clean install was two days ago on my laptop (using an external
drive for the install).
My 5th factory system was installed (clean install) as 13.2M0, back in
March, and updated yesterday to current factory. I did have networking
problems with that back in March and again yesterday (probably a
residue of the March problems). But all is now working.
Networking has mostly been fine on all of them. I think they currently
all use "wicked", but I have switched between that and NetworkManager,
without problem.
I always uncheck "Change Host via DHCP". And doing that has never
caused problems.
For all of those systems, I did start with a clean $HOME/.kde4 . I
always do that when beta testing. So, although I usually retain my old
home partition, I start with fresh desktop settings files. But I think
that should only be relevant for NetworkManager, and not for "wicked".
I perhaps overstated slightly, in saying that I have no networking
problems. I do have a problem on one system, and I have seen that on
another. What happens, is that when networking starts, I have no IPv6
access to the Internet. I have only a link-local IPv6 address. If I
wait -- perhaps 30 minutes -- the IPv6 addresses show up. I'm seeing
that with "wicked". However, on my first install on my laptop (and
WiFi), I saw that both with NetworkManager and "wicked". After a
re-install, I am not seeing that.
Original install on the laptop was from the KDE live iso. The reinstall
used the DVD installer. I doubt that is the difference, but I could be
wrong. The original install used straight partitioning. The reinstall
used an encrypted LVM. I'm guessing that's the difference. The IPv6
problem is likely a timing issue, and the use of an encrypted LVM
changes the timing of system startup a little because it is limited by
the kernel modules that are in the initrd until the crypto key is
provided.
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse-factory+owner@opensuse.org