no network after updrade

[jpff]

@deano_ferrari

Ah, I wasn’t aware that this user had used an unsupported upgrade method. That is likely to be relevant here somehow.

This user was not aware that an unsupported upgrade was used either. I was just following the instructions on the web.

“There are 2 supported upgrade mechanisms” and I used the second
From https://en.opensuse.org/openSUSE:Tumbleweed_upgrade

[jpff]

@deano_ferrari

It’s not clear to me why it fails to activate/associate. I was expecting you to report an error message given that this does not cause wicked to activate the device and associate with your AP. You could observe the journal logging while bringing eth1 up…so this in one terminal

sudo journalctl -f

and this executed from another

sudo ip link set eth1 up

Knurpht’s advice might be the best course of action given you have other issues with this install.

FWIW, I don’t have “USERCONTROL=‘no’” in my working configuration, and I’m using “STARTMODE=‘ifplugd’”, but ‘auto’ should be ok IMHO.

I ran the “ip link set eth1 up” command and the journal just reported that the command had been issued followed by comments on the sudo session.

And just reported from smartd that the disk has 1 currently unreadable (pending) sectors.