I seldom mess with the s390x linux stuff unless something in Hercules has changed or seems buggy etc...
This past week Hercules has changed the Floating Point emulation for the "hardware". I pulled out the old FC11 disk image, ipled and finally got "ucbtest" floating point test suite running. One of the things needed was addition of some defines to the fpu_control.h include file as described in a web post - http://www.eglibc.org/archives/patches/msg00511.html from which I only added the following:
+#define _FPU_RC_NEAREST 0x00 /* RECOMMENDED */
+#define _FPU_RC_DOWN 0x03
+#define _FPU_RC_UP 0x02
+#define _FPU_RC_ZERO 0x01
Since I don't know anything about this stuff I don't know if the "Stub version" of fpu_control.h needs these additional items or if they are correct values defined.
Most of the floating point stuff passed the tests but variations in GCC and glibc can have an effect on results so I cranked up the FC14 disk image and found:
No GCC installed
No ssh ability ( maybe this is a daemon which needs to be started but which one ? - it works with the FC11 image )
yum really likes to print a couple of lines and then Hercules belches "illegal instruction" and returns the prompt
yum list installed or one of the simple yum commands work but can't install or update gcc or anything else it seems
So to finally get to the end of this stuff, I see FC15 is available but so far no 'turnkey' disk image. If I follow the instructions to build from the page: http://secondary.fedoraproject.org/pub/alt/spins/S390/README where it mentions
"11) Just relax and enjoy the rest of the automated install"
When it is finished do I get a FC11 style image ( ssh, gcc, yum work ) or a FC14 style image ( no gcc, yum problematic, ssh maybe works with something in init.d (?) which needs manual editing ) ?
When I install kernel-devel on either F14 or F15, the arch/s390/kernel
subdirectory doesn¹t have the kernel source code like entry.S, head64.S etc.
>From the description the RPM is only for building modules against the kernel
headers etc. Is there an RPM kernel-src or similar? Or is it just grab from
I'm trying out F15 under z/VM 5.4. I have no ECKD DASD at my site; I rely
on FCP disks. I try to use z/VM FBA Emulation as much as possible (rather
than zfcp) as it makes disk management much easier.
I tried to install F15 on a guest with FBA minidisks, and the result is a
non-bootable system. At the completion of the installation phase, I tell
the system to Shutdown and it does so cleanly. The re-ipl fails however;
the kernel is unable to find the root filesystem and panics.
Two things are notable. In the kernel output after the reboot, the kernel
command line is about four lines of gibberish (mostly blanks, but a
smattering of random punctuation marks). Also, I tried attaching the disks
to a running system but no valid filesystem was found. (I was trying to
fix what I thought might have just been a problem with zipl, by attaching
the disks to a running system.)
I tried to do a RHEL6 install a while ago, but I could not even get it to
install -- Anaconda had no support for FBA disks. The fact that F15 was
able to successfully go through Anaconda was encouraging, but perhaps it's
not there yet. Has anyone tried a similar install and has experiences to
On a related note, a Kickstart install to FBA disks fails in much the same
way as my prior RHEL6 attempts. In the anaconda.log during install I see
Anaconda successfully finds the DASDs and the partition, but it "ignores"
the partitions and then reports that there are no usable disks.
Thanks and regards,
Vic Cross -- System z Technical Specialist -- IBM Australia --
I’m attempting to do a clean install of Fedora 15, using the materials on
your site, on a number of 3390 devices. I'd like to be able to specify the
partitioning myself but I think it's picking up a default configuration that
causes one huge LVM to be created from all available disks. The only way I
get to modify things is via this screen:
┌──────────┤ Partitioning Type ├────────────┐
│ Installation requires partitioning of your hard drive. The │
│ default layout is suitable for most users. Select what space │
│ to use and which drives to use as the install target. │
│ Use entire drive │
│ Replace existing Linux system │
│ Use free space │
How do I specify the full partitioning configuration I wish to use? I seem
to recall when I installed Fedora 14 I had to create a modified kickstart
file and put it somewhere I could point the installer to but I can't recall
and assume there must be an easier way.