Architectures/s390x/16: Difference between revisions

Revision as of 17:55, 7 September 2011

using anaconda-16.15-1.fc16.dh.1 + dracut-013-6.fc16

(resolved) when number of CPUs > 1 then "unknown filesystem in squashfs.img" error appears - probably 735199
(resolved) even with 1 CPU I got boots when the CMSCONFFILE wasn't read because CMSDASD device wasn't ready ("could not set device online" error message)
VNC install requires "vnc" in the parameters file
Bug 733680 - DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1
Bug 735026 - loader crashes when trying to install in vnc mode

using anaconda-16.16-1.fc16.dh.1 + dracut-013-7.fc16 + systemd-35-1.fc16

the addrsize utility isn't built in anaconda any more and thus lorax fails after writing kernel.img and initrd.img => moved to lorax - patch
anaconda dropped the mk-s390-cdboot tool in version 16 => remove relevant code also from lorax - patch

@@ Line 2: / Line 2: @@
 == issues found in F-16 Alpha 20110830 ==
 using anaconda-16.15-1.fc16.dh.1 + dracut-013-6.fc16
-* when number of CPUs > 1 then "unknown filesystem in squashfs.img" error appears - probably [https://bugzilla.redhat.com/show_bug.cgi?id=735199 735199]
+* (resolved) when number of CPUs > 1 then "unknown filesystem in squashfs.img" error appears - probably [https://bugzilla.redhat.com/show_bug.cgi?id=735199 735199]
-* even with 1 CPU I got boots when the CMSCONFFILE wasn't read because CMSDASD device wasn't ready ("could not set device online" error message)
+* (resolved) even with 1 CPU I got boots when the CMSCONFFILE wasn't read because CMSDASD device wasn't ready ("could not set device online" error message)
 * VNC install requires "vnc" in the parameters file
 * [https://bugzilla.redhat.com/show_bug.cgi?id=733680 Bug 733680] - DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1