[opensuse-arm] FYI: wicked issue with custom arm64 kernels

Hi, Since I ran into this the second time within three weeks myself: The currently published aarch64 wicked packages contain a known incompatibility with upstream defconfigs [1]. The issue has been fixed in wicked 0.6.36, but no new packages have been published yet for aarch64 (0.6.35). For armv7hl and armv6hl we have 0.6.36 already. Symptoms: You boot your kernel okay and after `zypper dup` network stops working, with the wicked.service failing to start and the interfaces failing to come up (`ip a`). If you're using official openSUSE kernels (e.g., openSUSE:Factory:ARM, Kernel:stable or Kernel:HEAD) you won't be affected, as the config options have been enabled all along. Contrib kernels may be affected! Our JeOS images don't contain an alternative to wicked, so the naive idea of simply switching to NetworkManager won't work easily, given the lack of network. Workaround: Either modify your kernel to enable the intermittently required config options [1] (IP_ADVANCED_ROUTER, IP_MULTIPLE_TABLES) or download on another machine and install via USB/SD a newer wicked .rpm. Regards, Andreas [1] https://bugzilla.opensuse.org/show_bug.cgi?id=981887 -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (1)
-
Andreas Färber