Hello!

I just uploaded updated installation images 2019-04-12 for the
following Debian Ports architectures:

* alpha
* hppa
* ia64
* m68k
* powerpc
* ppc64
* sh4
* sparc64

I uploaded both CD images [1] as well as netboot images [2].

Please test those images and report back over the mailing list for
the corresponding architecture.

Known issues:

* alpha
- No known issues
* hppa
- There have been reports about missing GPG keys during installation.
If you are seeing this issue, please provide me with the syslog,
information on your hardware, information on the image used and
a rough recap of what was done during install (normal vs. expert
mode etc).
* ia64
- The kernel might be unstable during install
(try passing "hardened_usercopy=off" at the boot prompt,
e.g. "install hardened_usercopy=off"
* m68k
- The drivers for IDE hardware may have to be loaded manually, e.g.:
+ modprobe pata_gayle
+ modprobe pata_falcon
- There is no automatic installation of the bootloader yet,
users have to boot the kernel and initrd manually after
installation.
* powerpc/ppc64
- The bootloader installation still defaults to Yaboot and
is being switched to GRUB for IBM POWER and PowerMacs,
please report any issues you find.
- On some machines, the fans might produce a lot of noise,
this can be addressed by manually the windfarm kernel
modules:
+ modprobe windfarm_core
* sh4
- There is no CD image, installation has to be performed
using the debian-installer images.
- Currently supported targets are Renesas SH-7785LCR and
SH-7751R, the latter should be identical to qemu-sh4.
- debian-installer for sh4 is completely untested, please
test with QEMU and report back.
- The filenames for kernel and initrd still contain an
old 2.6.32.5 kernel version. This can be ignored.
* sparc64
- Installation over a serial console is currently broken
on sparc64 due to a bug in the rootskel package
(can also be considered a kernel bug), see: #926539.
Use any image before 2019-04-06 as workaround.

Important:

When reporting issues or bugs, please include the syslog
from your installation in the bug report/mail. The log
file can be access when switching to another console using
<Alt>+<Cursor> for normal installations or <Ctrl>+<a>+<n>
when installing over a serial console. I also need to know
what hardware was used, which installation steps (normal
vs. expert) and which image was used.

Thanks,
Adrian

[1] https://cdimage.debian.org/cdimage/ports/2019-04-12/
[2] https://cdimage.debian.org/cdimage/ports/debian-installer/

--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)