S390x/Known Issues - Revision history

Prabuanand: Renamed Category from IBM to S390x

2024-10-15T15:50:41Z

Renamed Category from IBM to S390x

← Older revision		Revision as of 15:50, 15 October 2024
Line 32:		Line 32:


	[[category:~~IBM~~]]		[[category:S390x]]

Bt129 at 05:35, 29 September 2021

2021-09-29T05:35:09Z

← Older revision		Revision as of 05:35, 29 September 2021
Line 15:		Line 15:
	</pre>		</pre>

	This is because the clocksource on s390x was not ~~yet~~ detected. There is a pull request to make this work (~~would~~ be available on 3.9.1 release):		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 ~~mean time~~, 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 ~~bellow~~:		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>

Innsill: + category:IBM +draft

2019-09-14T06:53:49Z

+ category:IBM +draft

← Older revision		Revision as of 06:53, 14 September 2019
Line 1:		Line 1:
			{{draft}}

	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) :		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) :
Line 29:		Line 30:
	# setup-alpine		# setup-alpine
	</pre>		</pre>


			[[category:IBM]]

Innsill: Undo revision 15935 by Tmhoang (talk)

2019-09-14T06:52:45Z

Undo revision 15935 by Tmhoang (talk)

← Older revision	Revision as of 06:52, 14 September 2019
Line 1:	Line 1:

		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) :
		<pre>
		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]:
		</pre>

		This is because the clocksource on s390x was not yet detected. There is a pull request to make this work (would be available on 3.9.1 release):
		<pre>
		https://github.com/alpinelinux/aports/pull/6183
		https://github.com/alpinelinux/aports/pull/6184
		</pre>

		In the mean time, 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 bellow:

		<pre>
		# setup-interfaces
		# setup-dns
		# service networking start
		# ntpd -qn -p pool.ntp.org
		# setup-alpine
		</pre>

Tmhoang: Blanked the page

2019-05-09T20:29:21Z

Blanked the page

← Older revision		Revision as of 20:29, 9 May 2019
Line 1:		Line 1:

	~~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) :~~
	~~<pre>~~
	~~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]:~~
	~~</pre>~~

	~~This is because the clocksource on s390x was not yet detected. There is a pull request to make this work (would be available on 3.9.1 release):~~
	~~<pre>~~
	~~https://github.com/alpinelinux/aports/pull/6183~~
	~~https://github.com/alpinelinux/aports/pull/6184~~
	~~</pre>~~

	~~In the mean time, 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 bellow:~~

	~~<pre>~~
	~~# setup-interfaces~~
	~~# setup-dns~~
	~~# service networking start~~
	~~# ntpd -qn -p pool.ntp.org~~
	~~# setup-alpine~~
	~~</pre>~~

Tmhoang at 10:25, 5 February 2019

2019-02-05T10:25:41Z

← Older revision		Revision as of 10:25, 5 February 2019
Line 1:		Line 1:

	When running the 3.9 installer, you might face this problem (common among architectures without a RTC clock like armhf, aarch64, s390x) :		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) :
	<pre>		<pre>
	Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony] busybox		Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony] busybox

Tmhoang at 15:24, 4 February 2019

2019-02-04T15:24:25Z

← Older revision		Revision as of 15:24, 4 February 2019
Line 16:		Line 16:
	This is because the clocksource on s390x was not yet detected. There is a pull request to make this work (would be available on 3.9.1 release):		This is because the clocksource on s390x was not yet detected. There is a pull request to make this work (would be available on 3.9.1 release):
	<pre>		<pre>
			https://github.com/alpinelinux/aports/pull/6183
	https://github.com/alpinelinux/aports/pull/6184		https://github.com/alpinelinux/aports/pull/6184
	~~https://github.com/alpinelinux/aports/pull/6184~~
	</pre>		</pre>

Tmhoang at 14:40, 31 January 2019

2019-01-31T14:40:51Z

← Older revision		Revision as of 14:40, 31 January 2019
Line 1:		Line 1:
	~~= 1 =~~
	<~~code~~>		When running the 3.9 installer, you might face this problem (common among architectures without a RTC clock like armhf, aarch64, s390x) :
			<pre>
	Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony] busybox		Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony] busybox
	* service ntpd added to runlevel default		\* service ntpd added to runlevel default
	* Starting busybox ntpd ... [ ok ]		\* Starting busybox ntpd ... [ ok ]
	ssl_client: mirrors.alpinelinux.org: ocsp verify failed: ocsp response not current		ssl_client: mirrors.alpinelinux.org: ocsp verify failed: ocsp response not current
	wget: error getting response: Connection reset by peer		wget: error getting response: Connection reset by peer
Line 11:		Line 12:

	Enter mirror number (1-0) or URL to add (or r/f/e/done) [f]:		Enter mirror number (1-0) or URL to add (or r/f/e/done) [f]:
	</~~code~~>		</pre>

	This is because the clocksource on s390x was not yet detected. There is a pull request to make it work		This is because the clocksource on s390x was not yet detected. There is a pull request to make this work (would be available on 3.9.1 release):
	<~~code~~>		<pre>
	https://github.com/alpinelinux/aports/pull/6184		https://github.com/alpinelinux/aports/pull/6184
	https://github.com/alpinelinux/aports/pull/6184		https://github.com/alpinelinux/aports/pull/6184
	</code>		</pre>

			In the mean time, 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 bellow:

	~~In the mean time, please run below command before running~~ <~~code~~> # setup-~~alpine </code> for the installer:~~		<pre>
	~~<code>~~		# setup-interfaces
			# setup-dns
			# service networking start
	# ntpd -qn -p pool.ntp.org		# ntpd -qn -p pool.ntp.org
	# setup-alpine		# setup-alpine
	</~~code~~>		</pre>

Tmhoang: Created page with "= 1 = `Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony] busybox * service ntpd added to runlevel default * Starting busybox ntpd ......"`


2019-01-31T14:27:40Z
Created page with "= 1 = <code> Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony] busybox  * service ntpd added to runlevel default  * Starting busybox ntpd ......"
New page
= 1 =

<code>

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]: 

</code>



This is because the clocksource on s390x was not yet detected. There is a pull request to make it work

<code>

https://github.com/alpinelinux/aports/pull/6184

https://github.com/alpinelinux/aports/pull/6184 

</code>



In the mean time, please run below command before running <code> # setup-alpine </code> for the installer:

<code>

# ntpd -qn -p pool.ntp.org

# setup-alpine

</code>