d961fb7e0e
The old setup worked fine with an ext2 initrd but fails with an initramfs, either because autodetection is different for initramfs or because of kernel changes (I suspect the first). This means that booting s390 from CD has not worked since sometime during the Etch release cycle, even though support for booting from CD was only added early in that cycle - ouch. For booting with an initramfs initrd we apparently need to specify its offset and size at specific memory locations. Change is based on SuSE's CD boot. Many thanks to Adam Thornton, Mark Post (of Novell) and Bastian Blank for providing the pointers to the missing bits. This fixes booting from CD using the d390.ins file; tested in Hercules for both Lenny (31-bit kernel) and Squeeze (64-bit kernel). Booting from CD using the d390.tdf file may still be broken (if possible at all) as I have no idea how to test that. |
||
---|---|---|
.. | ||
README.boot | ||
d390.ins | ||
d390.tdf | ||
d390oco.ins | ||
d390oco.tdf |
README.boot
About the S/390 installation CD =============================== It is possible to "boot" the installation system off this CD using the files provided in the /boot directory. Note that the /boot/d390oco.* files are only provided as an example as Debian cannot ship the object-code-only-modules-ramdisk (oco.bin). Although you can boot the installer from this CD, the installation itself is *not* actually done from the CD. Once the initrd is loaded, the installer will ask you to configure your network connection and uses the network-console component to allow you to continue the installation over SSH. The rest of the installation is done over the network: all installer components and Debian packages are retrieved from a mirror. Tip for users of the Hercules emulator -------------------------------------- If you want to ipl the installer off this CD, mount it on the host system (e.g. on /media/cdrom) and enter the following in the Hercules management console: ipl /media/cdrom/boot/d390.ins