Hello!

I just uploaded updated installation images 2019-04-20 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
- There have been reports about missing firmware for storage devices.
The firmware required for these devices is located in the
"firmware-linux" and "firmware-linux-nonfree" packages but currently
don't have a floppy driver in debian-installer to load additional
firmware. I will figure out how to build CD images including firmware
similar to the images available for i386 and amd64.
* 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).
This issue is most likely a bug specific to hppa as the issue doesn't
show on other architectures despite the fact that the missing key
would normally affect all architectures. I suspect a hack that
was added for hppa when the first CD images were built for Debian
Ports by the PA-RISC porters. I'll look into it.
* ia64
- The kernel might be unstable during install
(try passing "hardened_usercopy=off" at the boot prompt,
e.g. "install hardened_usercopy=off").
- If the machine locks up during boot with a radeon GPU,
try passing "modprobe_blacklist=radeon nomodeset".
* 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.
- Unfortunately, upgrading the GRUB package will currently
render PowerMacs unbootable. See this thread for more:
https://lists.debian.org/debian-powerpc/2019/04/msg00165.html
- 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.

I am currently collecting bug reports but cannot push the fixes
immediately as the imminent Debian Buster release means that
debian-installer and components are effectively frozen.

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)

On 4/20/19 10:09, John Paul Adrian Glaubitz wrote:

Hello!

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

* alpha
[...]
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
- There have been reports about missing firmware for storage devices.
The firmware required for these devices is located in the
"firmware-linux" and "firmware-linux-nonfree" packages but currently
don't have a floppy driver in debian-installer to load additional
firmware. I will figure out how to build CD images including firmware
similar to the images available for i386 and amd64.

I just tried the 2019-04-20 ISO on my DS25. Unfortunately the disc drive
cannot be detected by the installer so I'm stuck at this point.

Checking the drivers available in the shipped initramfs, there seems to
be only one PATA driver available - `pata_sis` - and according to [1]
this is actually a dependency of a SATA driver.

[1]: https://salsa.debian.org/kernel-team/linux/blob/master/debian/installer/modules/pata-modules#L4-5

The missing driver for my machine is `pata_ali`, but as said the other
PATA drivers are also missing. From [2] and [3] I'd expect them to be
included, but this seems to be not the case for an unknown reason.

[2]: https://salsa.debian.org/kernel-team/linux/blob/master/debian/installer/modules/pata-modules#L1-2

[3]: https://salsa.debian.org/kernel-team/linux/blob/master/debian/installer/modules/alpha-generic/pata-modules

Loading this driver manually when using a NFS root FS makes the disc
drive accessible on my DS25:

```
root@ds25:/lib/modules/4.19.0-4-alpha-smp/kernel/drivers/ata# modprobe
-v pata_ali
insmod /lib/modules/4.19.0-4-alpha-smp/kernel/drivers/ata/libata.ko
insmod /lib/modules/4.19.0-4-alpha-smp/kernel/drivers/ata/pata_ali.ko

[ 182.457914] libata version 3.00 loaded.
[ 182.463773] scsi host0: pata_ali
[ 182.520414] scsi host1: pata_ali
[ 182.559476] ata1: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bmdma 0x10050
irq 14
[ 182.643461] ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0x10058
irq 15
[ 182.882718] ata1.00: ATAPI: SAMSUNG DVD-ROM SD-616Q, F401, max UDMA/33
[ 182.960843] ata1.00: WARNING: ATAPI DMA disabled for reliability
issues. It can be enabled
[ 183.061429] ata1.00: WARNING: via pata_ali.atapi_dma modparam or corresponding sysfs node.
[ 183.162015] scsi 0:0:0:0: CD-ROM SAMSUNG DVD-ROM SD-616Q
F401 PQ: 0 ANSI: 5
[ 183.192289] scsi 0:0:0:0: Attached scsi generic sg0 type 5
[ 183.733304] sr 0:0:0:0: [sr0] scsi3-mmc drive: 16x/48x cd/rw xa/form2
cdda tray
[ 183.734280] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 183.736234] sr 0:0:0:0: Attached scsi CD-ROM sr0
```

****

UPDATE: On second thought, [2] and [3] seem to be unrelated to what is available in the initramfs of the installer. From what I saw, the
drivers from the sata-modules UDEB are actually included in the
initramfs, but the needed drivers from the pata-modules UDEB are not.

Where is this configured? [4] includes the sata-modules UDEB as
optional, but no pata-modules UDEB. So is this maybe configured in [4]?
If yes, I can provide a patch on salsa.d.o to fix that issue, just need
a confirmation.

[4]: https://salsa.debian.org/installer-team/debian-installer/blob/master/build/pkg-lists/cdrom/alpha.cfg

Cheers,
Frank

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

--Apple-Mail-205BE5B4-6E5F-46CB-ABEC-D4A8624392A8
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: quoted-printable

On May 6, 2019, at 11:17 PM, Frank Scheiner <frank.scheiner@web.de> wrote:

I just tried the 2019-04-20 ISO on my DS25. Unfortunately the disc drive cannot be detected by the installer so I'm stuck at this point.

As far as I know, a lot of Alpha-specific hardware needs firmware but I haven’t looked into creating images with firmware yet.

UPDATE: On second thought, [2] and [3] seem to be unrelated to what is available in the initramfs of the installer. From what I saw, the
drivers from the sata-modules UDEB are actually included in the
initramfs, but the needed drivers from the pata-modules UDEB are not.

Where is this configured? [4] includes the sata-modules UDEB as
optional, but no pata-modules UDEB. So is this maybe configured in [4]?
If yes, I can provide a patch on salsa.d.o to fix that issue, just need
a confirmation.

Here: https://salsa.debian.org/kernel-team/linux/tree/master/debian/installer/modules/alpha-generic

Try to understand the include logic first before sending a PR. A lot of modules are actually included using the “common” directory.

Adrian
--Apple-Mail-205BE5B4-6E5F-46CB-ABEC-D4A8624392A8
Content-Type: text/html;
charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div dir="ltr"><br></div><div dir="ltr"><br>On May 6, 2019, at 11:17 PM, Frank Scheiner &lt;<a href="mailto:frank.scheiner@web.de">
frank.scheiner@web.de</a>&gt; wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><span>I just tried the 2019-04-20 ISO on my DS25. Unfortunately the disc drive</span><br><span>cannot be detected by the installer so I'm stuck at this point.</span><

</div></blockquote><div><br></div><div>As far as I know, a lot of Alpha-specific hardware needs firmware but I haven’t looked into creating images with firmware yet.</div><br><blockquote type="cite"><div dir="ltr"><span>UPDATE: On second thought, [2]

and [3] seem to be unrelated to what is</span><br><span>available in the initramfs of the installer. From what I saw, the</span><br><span>drivers from the sata-modules UDEB are actually included in the</span><br><span>initramfs, but the needed drivers
from the pata-modules UDEB are not.</span><br><span></span><br><span>Where is this configured? [4] includes the sata-modules UDEB as</span><br><span>optional, but no pata-modules UDEB. So is this maybe configured in [4]?</span><br><span>If yes, I can
provide a patch on salsa.d.o to fix that issue, just need</span><br><span>a confirmation.</span><br></div></blockquote><br><div>Here:&nbsp;<a href="https://salsa.debian.org/kernel-team/linux/tree/master/debian/installer/modules/alpha-generic">https://
salsa.debian.org/kernel-team/linux/tree/master/debian/installer/modules/alpha-generic</a></div><div><br></div><div>Try to understand the include logic first before sending a PR. A lot of modules are actually included using the “common” directory.</

<div><br></div><div>Adrian</div></body></html> --Apple-Mail-205BE5B4-6E5F-46CB-ABEC-D4A8624392A8--

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

On 5/6/19 23:37, John Paul Adrian Glaubitz wrote:

On May 6, 2019, at 11:17 PM, Frank Scheiner <frank.scheiner@web.de <mailto:frank.scheiner@web.de>> wrote:

I just tried the 2019-04-20 ISO on my DS25. Unfortunately the disc drive
cannot be detected by the installer so I'm stuck at this point.

As far as I know, a lot of Alpha-specific hardware needs firmware but I haven’t looked into creating images with firmware yet.

Yeah, but this problems seems purely due to the pata-modules missing in
the initramfs.

UPDATE: On second thought, [2] and [3] seem to be unrelated to what is
available in the initramfs of the installer. From what I saw, the
drivers from the sata-modules UDEB are actually included in the
initramfs, but the needed drivers from the pata-modules UDEB are not.

Where is this configured? [4] includes the sata-modules UDEB as
optional, but no pata-modules UDEB. So is this maybe configured in [4]?
If yes, I can provide a patch on salsa.d.o to fix that issue, just need
a confirmation.

Here: https://salsa.debian.org/kernel-team/linux/tree/master/debian/installer/modules/alpha-generic

Try to understand the include logic first before sending a PR. A lot of modules are actually included using the “common” directory.

Could you explain a little more? With the "common" directory you mean [5]?

[5]: https://salsa.debian.org/kernel-team/linux/tree/master/debian/installer/modules/

The way I understand it, the configuration files in [6] control what
UDEBs are built for the alpha kernel used for the installer, as they
seem to include the configuration files from the assumed "common" super directory which list the drivers to include for the respective devices/protocols/standards/etc..

And the configuration in [7] seems to control what UDEBs are installed
in the initramfs. This would make sense for [7] as it looks like the
alpha configuration file for the installer CDROM and the initramfs for
this CDROM should contain all needed drivers to be able to access the
used disc drive. Hence I think we need to update [7].

The question remains if one needs to specify dependencies explicitly or
if dependencies are resolved during build. I'll try to correlate the
modules in the initramfs with what is configured in [7] and come to a conclusion.

[6]: https://salsa.debian.org/kernel-team/linux/tree/master/debian/installer/modules/alpha-generic

[7]: https://salsa.debian.org/installer-team/debian-installer/blob/master/build/pkg-lists/cdrom/alpha.cfg

Cheers,
Frank

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

On 5/8/19 10:51 AM, Frank Scheiner wrote:

As far as I know, a lot of Alpha-specific hardware needs firmware but I
haven’t looked into creating images with firmware yet.

Yeah, but this problems seems purely due to the pata-modules missing in
the initramfs.

That's true. But we have has also many reports on people complaining about missing firmware, so that should definitely be addressed.

Here:
https://salsa.debian.org/kernel-team/linux/tree/master/debian/installer/modules/alpha-generic

Try to understand the include logic first before sending a PR. A lot of
modules are actually included using the “common” directory.

Could you explain a little more? With the "common" directory you mean [5]?

[5]: https://salsa.debian.org/kernel-team/linux/tree/master/debian/installer/modules/

Yes. Unless the driver you want is alpha-specific, you would put it into
this list:

https://salsa.debian.org/kernel-team/linux/blob/master/debian/installer/modules/pata-modules

The way I understand it, the configuration files in [6] control what
UDEBs are built for the alpha kernel used for the installer, as they
seem to include the configuration files from the assumed "common" super directory which list the drivers to include for the respective devices/protocols/standards/etc..

No. They simply control which modules are put into which modules UDEBS.

And the configuration in [7] seems to control what UDEBs are installed
in the initramfs.

Correct. debian-cd itself just includes all UDEBs.

The question remains if one needs to specify dependencies explicitly or
if dependencies are resolved during build. I'll try to correlate the
modules in the initramfs with what is configured in [7] and come to a conclusion.

You put in all the modules you need. If you need "pata1", "pata2" and "pata-helper", you add them to the list.

For example:

https://salsa.debian.org/kernel-team/linux/commit/db4ed9e563092b5847556f319fa29109bc5221a9

Adrian

--
.''`. 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)