On Fri, 23 Mar 2018 17:12:58 Michal Kubecek wrote:

On Friday, 23 March 2018 16:44 Ludwig Nussel wrote:

H Zeng wrote:

On Friday, 23 March 2018 12:36:23 GMT Terje J. Hanssen wrote:

So far every Leap 15 updates has worked ok, but the last one yesterday, Build 174.1 broke my system on XPS 13. "zypper dup" caused no wifi setup available after the update, and YaST2 wouldn't start any more. Other experiences with this?

You're not alone. I got a WiFi-less system after the update took yesterday night. I am just trying to understand this and find a way to solve the problem.

Looks like kernel modules that are unsupported on SLE side accidentally ended up in a separate kernel-default-extra subpackage. Try installing that one. The next snapshot should have all modules in the kernel-default package again.

It might not be sufficient to install kernel-default-extra as you will also need to enable allow_unsupported_modules in /etc/modprobe.d/ (and probably regenerate initrd as some of the affected modules might be there). Simply rebooting back to 4.12.14-lp150.5 (which seems to be still available in the repository) until fixed package is available might be easier.

Michal Kubeček

Lastly I ended up to (re)install the last working Build 168.1 (over Build 174.1), as "upgrade" (downgrade) didn't work. A tip for other instances is that this previous Build was preserved and found here (a link on the normal download site could be benefical) : http://ftp.uni-hannover.de/opensuse/distribution/leap/15.0/iso/ Terje J. H -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

H Zeng wrote:

On Friday, 23 March 2018 12:36:23 GMT Terje J. Hanssen wrote:

...

So far every Leap 15 updates has worked ok, but the last one yesterday, Build 174.1 broke my system on XPS 13. "zypper dup" caused no wifi setup available after the update, and YaST2 wouldn't start any more. Other experiences with this?

You're not alone. I got a WiFi-less system after the update took yesterday night. I am just trying to understand this and find a way to solve the problem.

Looks like kernel modules that are unsupported on SLE side accidentally ended up in a separate kernel-default-extra subpackage. Try installing that one. The next snapshot should have all modules in the kernel-default package again. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Friday, 23 March 2018 16:44 Ludwig Nussel wrote:

H Zeng wrote:

...

On Friday, 23 March 2018 12:36:23 GMT Terje J. Hanssen wrote:

...

So far every Leap 15 updates has worked ok, but the last one yesterday, Build 174.1 broke my system on XPS 13. "zypper dup" caused no wifi setup available after the update, and YaST2 wouldn't start any more. Other experiences with this?

You're not alone. I got a WiFi-less system after the update took yesterday night. I am just trying to understand this and find a way to solve the problem.

Looks like kernel modules that are unsupported on SLE side accidentally ended up in a separate kernel-default-extra subpackage. Try installing that one. The next snapshot should have all modules in the kernel-default package again.

It might not be sufficient to install kernel-default-extra as you will also need to enable allow_unsupported_modules in /etc/modprobe.d/ (and probably regenerate initrd as some of the affected modules might be there). Simply rebooting back to 4.12.14-lp150.5 (which seems to be still available in the repository) until fixed package is available might be easier. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 03/26/2018 02:15 PM, Linux Kamarada wrote:

2018-03-23 13:12 GMT-03:00 Michal Kubecek :

...

On Friday, 23 March 2018 16:44 Ludwig Nussel wrote:

...

H Zeng wrote:

...

On Friday, 23 March 2018 12:36:23 GMT Terje J. Hanssen wrote:

...

So far every Leap 15 updates has worked ok, but the last one yesterday, Build 174.1 broke my system on XPS 13. "zypper dup" caused no wifi setup available after the update, and YaST2 wouldn't start any more. Other experiences with this?

I upgraded from 42.3 to 15.0 yesterday / today. I've got a similar problem. I'm not sure, but I think I'm using Leap 15.0 Build 174.1, as that was the last update I received from Ludwig Nussel on March 23.

After upgrade, I can get to the GNOME desktop, everything seems to be in place, except for Wi-Fi.

I use NetworkManager. It shows as connected to my home Wi-Fi. But I'm unable to open any site using a browser.

It seems to be related to DNS, because ping 8.8.8.8 works, while ping google.com does not.

cat /etc/resolv.conf shows the file is empty, except for a comment "Generated by NetworkManager".

There's your problem. Try adding the following lines to the file: nameserver 8.8.8.8 nameserver 8.8.4.4 as well as 2001:4860:4860::8888 and 2001:4860:4860::8844, for IPv6 nameservers. These are provided by google. -- Ken Schneider -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Brüns, Stefan [03-26-18 15:37]:

On Montag, 26. März 2018 21:07:59 CEST Ken Schneider - Factory wrote:

...

On 03/26/2018 02:15 PM, Linux Kamarada wrote:

...

2018-03-23 13:12 GMT-03:00 Michal Kubecek : [...]

I upgraded from 42.3 to 15.0 yesterday / today. I've got a similar problem. I'm not sure, but I think I'm using Leap 15.0 Build 174.1, as that was the last update I received from Ludwig Nussel on March 23.

After upgrade, I can get to the GNOME desktop, everything seems to be in place, except for Wi-Fi.

I use NetworkManager. It shows as connected to my home Wi-Fi. But I'm unable to open any site using a browser.

It seems to be related to DNS, because ping 8.8.8.8 works, while ping google.com does not.

cat /etc/resolv.conf shows the file is empty, except for a comment "Generated by NetworkManager".

There's your problem. Try adding the following lines to the file:

nameserver 8.8.8.8 nameserver 8.8.4.4

as well as 2001:4860:4860::8888 and 2001:4860:4860::8844, for IPv6 nameservers. These are provided by google.

Thats completely wrong:

1. Not everybody wants to use Googles nameservers

yes, but there are other nameservers available, use "namebench" to find the better ones.

2. It will break lookup of internal services

still works from me.

3. It will stop Networkmanager and/or wicked from doing any updates in the future.

I have not experienced this. configured using yast: ### Please remove (at least) this line when you modify the file! search attlocal.net wahoo.no-ip.org nameserver 8.8.4.4 nameserver 8.8.8.8 nameserver 192.168.1.254

Please check the journal if there are any messages from Networkmanager regarding nameservers.

This is also unrelated to the original thread, as wireless obviously works (so no missing kernel modules), only DNS does not.

-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Montag, 26. März 2018 22:17:46 CEST Larry Finger wrote:

On 03/26/2018 03:00 PM, Patrick Shanahan wrote:

...

* Brüns, Stefan [03-26-18 15:37]:

...

...

On 03/26/2018 02:15 PM, Linux Kamarada wrote:

...

2018-03-23 13:12 GMT-03:00 Michal Kubecek :

On Montag, 26. März 2018 21:07:59 CEST Ken Schneider - Factory wrote: 3. It will stop Networkmanager and/or wicked from doing any updates in the future.

I have not experienced this.

Nor have I. What is the justification for #3 above? It seems to me that as long as you have a nameserver that works, all updates should work. In addition, doesn't PackageKit and/or zypper control updates?

/etc/resolv.conf is a file generated at runtime using netconfig (called by NetworkManager/wicked). netconfig checks if the file has been been modified and stops updating the file, if not run with the -f parameter. Regards, Stefan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

2018-03-26 18:07 GMT-03:00 Bengt Gördén :

Den 2018-03-26 kl. 22:58, skrev Brüns, Stefan:

...

/etc/resolv.conf is a file generated at runtime using netconfig (called by NetworkManager/wicked). netconfig checks if the file has been been modified and stops updating the file, if not run with the -f parameter.

Or more precisely netconfig update -f

If you use nm and see logs like this: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... You can find my version in /etc/resolv.conf.netconfig ...

It's not updated.

Check with: journalctl _COMM=NetworkManager or journalctl _COMM=NetworkManager | grep resolv.conf

Thank you! It was that! # journalctl _COMM=NetworkManager | grep resolv.conf | less ... mar 26 18:42:53 viny-notebook NetworkManager[3517]: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... mar 26 18:42:53 viny-notebook NetworkManager[3517]: You can find my version in /etc/resolv.conf.netconfig ... ... # netconfig update -f # cat /etc/resolv.conf ### /etc/resolv.conf file autogenerated by netconfig! # # Before you change this file manually, consider to define the # static DNS configuration using the following variables in the # /etc/sysconfig/network/config file: # NETCONFIG_DNS_STATIC_SEARCHLIST # NETCONFIG_DNS_STATIC_SERVERS # NETCONFIG_DNS_FORWARDER # or disable DNS configuration updates via netconfig by setting: # NETCONFIG_DNS_POLICY='' # # See also the netconfig(8) manual page and other documentation. # # Note: Manual change of this file disables netconfig too, but # may get lost when this file contains comments or empty lines # only, the netconfig settings are same with settings in this # file and in case of a "netconfig update -f" call. # ### Please remove (at least) this line when you modify the file! nameserver 201.21.192.167 nameserver 201.21.192.162 Curiously, I haven't edited that file manually... anyways... now it's working! Thank you for all of your answers! 2018-03-26 15:15 GMT-03:00 Linux Kamarada :

Also, I haven't tested wired network. I'm going to test it as well and keep you in touch.

Wired networking works as expected. 2018-03-26 16:35 GMT-03:00 Brüns, Stefan :

This is also unrelated to the original thread, as wireless obviously works (so no missing kernel modules), only DNS does not.

Sorry, I thought they were related. I was going to start a new, separate thread, but the issue has already been solved. 2018-03-26 17:00 GMT-03:00 Patrick Shanahan :

* Brüns, Stefan [03-26-18 15:37]:

...

On Montag, 26. März 2018 21:07:59 CEST Ken Schneider - Factory wrote:

...

There's your problem. Try adding the following lines to the file:

nameserver 8.8.8.8 nameserver 8.8.4.4

Thats completely wrong:

1. Not everybody wants to use Googles nameservers

yes, but there are other nameservers available, use "namebench" to find the better ones.

Hmm I didn't know that tool. I'm going to look for it. I'm used to this one: DNS Benchmark https://www.grc.com/dns/benchmark.htm Antonio The Linux Kamarada Project http://kamarada.github.io/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 27/03/18 12:41 PM, Ken Schneider - Factory wrote:

On 03/26/2018 03:35 PM, Brüns, Stefan wrote:

...

On Montag, 26. März 2018 21:07:59 CEST Ken Schneider - Factory wrote:

...

On 03/26/2018 02:15 PM, Linux Kamarada wrote:

...

2018-03-23 13:12 GMT-03:00 Michal Kubecek : [...]

I upgraded from 42.3 to 15.0 yesterday / today. I've got a similar problem. I'm not sure, but I think I'm using Leap 15.0 Build 174.1, as that was the last update I received from Ludwig Nussel on March 23.

After upgrade, I can get to the GNOME desktop, everything seems to be in place, except for Wi-Fi.

I use NetworkManager. It shows as connected to my home Wi-Fi. But I'm unable to open any site using a browser.

It seems to be related to DNS, because ping 8.8.8.8 works, while ping google.com does not.

cat /etc/resolv.conf shows the file is empty, except for a comment "Generated by NetworkManager".

There's your problem. Try adding the following lines to the file:

nameserver 8.8.8.8 nameserver 8.8.4.4

as well as 2001:4860:4860::8888 and 2001:4860:4860::8844, for IPv6 nameservers. These are provided by google.

Thats completely wrong:

1. Not everybody wants to use Googles nameservers 2. It will break lookup of internal services 3. It will stop Networkmanager and/or wicked from doing any updates in the future.

Firstly it in NOT completely wrong. At least I provided a way to get his DNS lookups working until he could figure out why his resolv.conf file was not beimg populated. You offered no such work-around.

Perhaps restarting networkmanager would force a rebuild of the file.

I agree. Usually a disable and enable systemctl enable NetworkManager.service and systemctl restart network.service could have fixed it. -- Cheers! Roman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Op dinsdag 27 maart 2018 20:07:19 CEST schreef Brüns, Stefan:

On Dienstag, 27. März 2018 19:46:01 CEST Roman Bysh wrote:

...

On 27/03/18 12:41 PM, Ken Schneider - Factory wrote:

...

On 03/26/2018 03:35 PM, Brüns, Stefan wrote:

...

On Montag, 26. März 2018 21:07:59 CEST Ken Schneider - Factory wrote:

...

On 03/26/2018 02:15 PM, Linux Kamarada wrote:

...

2018-03-23 13:12 GMT-03:00 Michal Kubecek : [...]

...

...

I upgraded from 42.3 to 15.0 yesterday / today. I've got a similar problem. I'm not sure, but I think I'm using Leap 15.0 Build 174.1, as that was the last update I received from Ludwig Nussel on March 23.

After upgrade, I can get to the GNOME desktop, everything seems to be in place, except for Wi-Fi.

I use NetworkManager. It shows as connected to my home Wi-Fi. But I'm unable to open any site using a browser.

It seems to be related to DNS, because ping 8.8.8.8 works, while ping google.com does not.

cat /etc/resolv.conf shows the file is empty, except for a comment "Generated by NetworkManager".

There's your problem. Try adding the following lines to the file:

nameserver 8.8.8.8 nameserver 8.8.4.4

as well as 2001:4860:4860::8888 and 2001:4860:4860::8844, for IPv6 nameservers. These are provided by google.

Thats completely wrong:

1. Not everybody wants to use Googles nameservers 2. It will break lookup of internal services 3. It will stop Networkmanager and/or wicked from doing any updates in the future.>

Firstly it in NOT completely wrong. At least I provided a way to get his DNS lookups working until he could figure out why his resolv.conf file was not beimg populated. You offered no such work-around.

Then mention it's a workaround. Tell what effect the the changes have, and mention the side effects.

...

...

Perhaps restarting networkmanager would force a rebuild of the file.

No. Definitely not.

...

I agree. Usually a disable and enable systemctl enable NetworkManager.service and systemctl restart network.service could have fixed it.

System-administration pumpgun style ... network.service is a symlink to NetworkManager.service, but even restarting NetworkManager twice won't update resolv.conf after it has been altered. It does recreate it, if you remove resolv.conf, and it does update it. I'm running around with my laptop using various networks, and the content of the file does change.

Regards,

Stefan

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Dienstag, 27. März 2018 22:35:56 CEST Knurpht @ openSUSE wrote:

Op dinsdag 27 maart 2018 20:07:19 CEST schreef Brüns, Stefan:

...

On Dienstag, 27. März 2018 19:46:01 CEST Roman Bysh wrote:

...

On 27/03/18 12:41 PM, Ken Schneider - Factory wrote:

...

On 03/26/2018 03:35 PM, Brüns, Stefan wrote:

...

On Montag, 26. März 2018 21:07:59 CEST Ken Schneider - Factory wrote:

...

Then mention it's a workaround. Tell what effect the the changes have, and mention the side effects.

...

...

Perhaps restarting networkmanager would force a rebuild of the file.

No. Definitely not.

...

I agree. Usually a disable and enable systemctl enable NetworkManager.service and systemctl restart network.service could have fixed it.

System-administration pumpgun style ... network.service is a symlink to NetworkManager.service, but even restarting NetworkManager twice won't update resolv.conf after it has been altered.

It does recreate it, if you remove resolv.conf, and it does update it. I'm ^ iff ...

'nough said, Stefan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org