S390x/Known Issues: Difference between revisions
m (+ category:IBM +draft) |
No edit summary |
||
Line 15: | Line 15: | ||
</pre> | </pre> | ||
This is because the clocksource on s390x was not | This is because the clocksource on s390x was not detected. There is a pull request to make this work (should be available in the 3.9.1 release): | ||
<pre> | <pre> | ||
https://github.com/alpinelinux/aports/pull/6183 | https://github.com/alpinelinux/aports/pull/6183 | ||
Line 21: | Line 21: | ||
</pre> | </pre> | ||
In the | In the meantime, to overcome this problem, you need to update the system time, either manullay using <code> date </code> command or using NTP then start the installer as shown below: | ||
<pre> | <pre> |
Revision as of 05:35, 29 September 2021
This material is work-in-progress ... Do not follow instructions here until this notice is removed. |
When running the 3.9 netboot installer, you might face this problem mostly z/VM hypervisor (common among architectures without a RTC clock like armhf, aarch64, s390x) :
Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony] busybox \* service ntpd added to runlevel default \* Starting busybox ntpd ... [ ok ] ssl_client: mirrors.alpinelinux.org: ocsp verify failed: ocsp response not current wget: error getting response: Connection reset by peer r) Add random from the above list f) Detect and add fastest mirror from above list e) Edit /etc/apk/repositories with text editor Enter mirror number (1-0) or URL to add (or r/f/e/done) [f]:
This is because the clocksource on s390x was not detected. There is a pull request to make this work (should be available in the 3.9.1 release):
https://github.com/alpinelinux/aports/pull/6183 https://github.com/alpinelinux/aports/pull/6184
In the meantime, to overcome this problem, you need to update the system time, either manullay using date
command or using NTP then start the installer as shown below:
# setup-interfaces # setup-dns # service networking start # ntpd -qn -p pool.ntp.org # setup-alpine