Hi all,
tested on powerbook g4, boot from usb0.

Install options:
- installation language : English default;
- disk space : use all disk, all files on same dir;
- mirror : deb.debian.org/debian-ports
- software : default option;

Results:
detected a regression respect to previous version: grub cannot be installed;

1.
   May 12 16:33:59 grub-installer: grub-install: error: ofpathname: not
   found.
2.
   May 12 16:33:59 grub-installer: error: Running 'grub-install
     --force --macppc-directory=/boot/grub' failed.


here is full log:
https://pastebin.com/aFuQP8sN
https://pastebin.com/jYAVnWXK

Regards,
Roberto

Il 09/05/2019 18:24, John Paul Adrian Glaubitz ha scritto:
Hello!

I just uploaded updated installation images 2019-05-09 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.
    - The images now includes the pata-modules package so users previously
      missing PATA drivers should be able to install their machines now.
  * hppa
    - No known issues and changes.
  * 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".
    - The installer has been switched to boot using GRUB now,
      ELILO is no longer available.
  * 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
    - The installer has been switched to boot using GRUB now,
      Yaboot is still in the archives but will be removed
  * 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.
    - The installer has been switched to boot using GRUB now,
      SILO is no longer available.

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-05-09/
[2] https://cdimage.debian.org/cdimage/ports/debian-installer/

Reply via email to