From Fedora Project Wiki
< Architectures | s390x
(Created page with "<!-- = Fedora/s390x specific Release Notes = --> = Downloads = Please download pre-release composes from * http://s390.koji.fedoraproject.org/compose/ or * http://downloa...") |
|||
| Line 15: | Line 15: | ||
for older notes see [[Architectures/s390x/23]] | for older notes see [[Architectures/s390x/23]] | ||
* network interfaces were renamed by upstream udev - https://github.com/systemd/systemd/commit/0037a669ac9a2bbedccdb2f483111351e8ff4659 | * network interfaces were renamed by upstream udev - https://github.com/systemd/systemd/commit/0037a669ac9a2bbedccdb2f483111351e8ff4659 - so enccw0.0.0600 becomes enc600, updating parameter files is required | ||
= Developer information = | = Developer information = | ||
Revision as of 13:16, 16 June 2016
Downloads
Please download pre-release composes from
or
Release Notes
for older notes see Architectures/s390x/23
- network interfaces were renamed by upstream udev - https://github.com/systemd/systemd/commit/0037a669ac9a2bbedccdb2f483111351e8ff4659 - so enccw0.0.0600 becomes enc600, updating parameter files is required
Developer information
Global info
Image composes are run on F-24 with
- lorax-23.14-1.fc23
- pungi-4.0.2-1.fc23
The test composes are available from http://s390.koji.fedoraproject.org/compose/
F-24 Alpha
skipped due missing tooling
issues found in F-23 TC1
using anaconda-23.19.7-1.fc23
Known issues:
- traceback on systems with zFCP disk: https://bugzilla.redhat.com/show_bug.cgi?id=1273009 (it's only possible to use zFCP disks during manual installation in VNC mode)
- traceback during kickstart VNC installation on a system with unformatted DASD disk: https://bugzilla.redhat.com/show_bug.cgi?id=1273553
Installation status: OK (graphical), OK (kickstart with VNC), OK (kickstart with text)
Boot status: OK
issues found in F-23 RC1
using anaconda-23.19.9-1.fc23
Installation status: OK (graphical), OK (kickstart with VNC), OK (kickstart with text)
Boot status: OK