< Architectures | s390x
Release Notes
for older notes see Architectures/s390x/18
- when running the Gnome desktop, having 2 GB RAM allocated for the VM is useful, I saw a lot of swapping in VM with 1 GB, XFCE run fine with 1 GB
- installation on SCSI/zFCP disk fails because a change in kernel broke the WWPN parsing (bug 975696) and it was too late for including the fixed kernel in F-19
- you can get "RuntimeError: cannot join thread before it is started" error thrown during the install (bug 970858), seems more widespread than originally thought
- installation in Hercules fails because it's not able to run reipl at the end of the installation, see bug 904245 for more information and a workaround
Developer information
Global info
Image composes are run on F-19 with
- pungi-2.13-2.fc19
- lorax-19.1-1.fc19
- lorax-19.1-2.fc19 (since 20130416)
- lorax-19.2-1.fc19 (since 20130424) + fix for rhbz#956241
- lorax-19.3-1.fc19 (since 20130515)
- lorax-19.4-1.fc19 (since 20130528)
- lorax-19.5-1.fc19 (since 20130628)
The test composes are available from http://s390.koji.fedoraproject.org/test/
issues found in F-19 Alpha 20130412
using anaconda-19.18-1.fc19, python-blivet-0.10-1.fc19
Installation status: FAIL
- graphical - traceback during post-installation step (bug #951628)
- kickstart - doesn't start (bug #951632)
issues found in F-19 Alpha 20130416
using anaconda-19.19-1.fc19, python-blivet-0.11-1.fc19
installation may require 2 GB of memory because debug kernel is used
Installation status: OK
Boot status: FAIL
issues found in F-19 post-Alpha 20130424
using anaconda-19.21-1.fc19, python-blivet-0.11-1.fc19
Installation status: OK (graphical), OK (kickstart with VNC), FAIL (kickstart with text)
Boot status: OK
- anaconda prints an error about "No IP address avaiable ..." but networking is working so one can continue in the installation with VNC (956583)
issues found in F-19 pre-Beta 20130515
using anaconda-19.25-1.fc19
Installation status: OK (graphical), OK (kickstart with VNC), N/A (kickstart with text)
Boot status: OK
- can be again installed with 1 GB of RAM
issues found in F-19 pre-Beta 20130520
using anaconda-19.28-1.fc19
Installation status: OK (graphical), OK (kickstart with VNC), OK (kickstart with text)
Boot status: OK
- minimal package set works fine, default package set fails with a dependency error
issues found in F-19 post-Beta 20130528
using anaconda-19.30-1.fc19
Installation status: OK (graphical), OK (kickstart with VNC), OK (kickstart with text)
Boot status: OK
- fixed the dependency issue in the default package set (#967422)
issues found in F-19 post-Beta 20130603
using anaconda-19.30-1.fc19
Installation status: N/A (graphical), OK (kickstart with VNC), N/A (kickstart with text)
Boot status: OK
issues found in F-19 post-Beta 20130610
using anaconda-19.30-1.fc19
Installation status: OK (graphical), OK (kickstart with VNC), OK (kickstart with text)
Boot status: OK
issues found in F-19 post-Beta 20130612
using anaconda-19.30.5-1.fc19, latest mesa and llvm
Installation status: N/A (graphical), N/A (kickstart with VNC), OK (kickstart with text)
Boot status: OK
- anaconda crashes because it calls hwclock - 973999, please use the updates.img from the bug
issues found in F-19 pre-GA 20130624
using anaconda-19.30.9-1.fc19, latest mesa and llvm
Installation status: OK (graphical), OK (kickstart with VNC), OK (kickstart with text)
Boot status: OK
general anaconda/lorax/pungi/... issues
- pungi
- lorax - /etc/os-release is missing - bug 956241