Re: Kernel 6.9 fails to boot with "can't boot dump kernel from OF"

Hi Reimar, > On Jul 6, 2024, at 5:45 PM, Reimar Döffinger wrote: > >> Could you verify that this change actually fixes the problem? This would >> save me some work. > > I checked the kernel source, the error message is under a if (PHYSICAL_START > > 0), so that I am quite certain is the issue

Re: Kernel 6.9 fails to boot with "can't boot dump kernel from OF"

> On 6 Jul 2024, at 17:26, Reimar Döffinger wrote: > > >> On 6 Jul 2024, at 17:17, John Paul Adrian Glaubitz >> wrote: >> >> Hi Reimar, >> >>> On Jul 6, 2024, at 5:09 PM, Reimar Döffinger >>> wrote: >>> >>> Hi! >>> The newest 6.9 powerpc kernel build seems to be incompatible with >>>

Re: Kernel 6.9 fails to boot with "can't boot dump kernel from OF"

> On 6 Jul 2024, at 17:17, John Paul Adrian Glaubitz > wrote: > > Hi Reimar, > >> On Jul 6, 2024, at 5:09 PM, Reimar Döffinger >> wrote: >> >> Hi! >> The newest 6.9 powerpc kernel build seems to be incompatible with >> OpenFirmware boot, >> so boot fails on my PowerPC macMini. >> The err

Re: Kernel 6.9 fails to boot with "can't boot dump kernel from OF"

Hi Reimar, > On Jul 6, 2024, at 5:09 PM, Reimar Döffinger wrote: > > Hi! > The newest 6.9 powerpc kernel build seems to be incompatible with > OpenFirmware boot, > so boot fails on my PowerPC macMini. > The error message is > "Error: You can't boot a kdump kernel from OF!" > The error message

Kernel 6.9 fails to boot with "can't boot dump kernel from OF"

Hi! The newest 6.9 powerpc kernel build seems to be incompatible with OpenFirmware boot, so boot fails on my PowerPC macMini. The error message is "Error: You can't boot a kdump kernel from OF!" The error message seems not entirely accurate, it seems the issue is that CONFIG_PHYSICAL_START is no l

Bug#1075851: mayavi2: FTBFS on ppc64el and riscv64

Source: mayavi2 Version: 4.8.1-5 Severity: serious Tags: ftbfs X-Debbugs-Cc: debian-ri...@lists.debian.org, debian-powerpc@lists.debian.org Hi Maintainer mayavi2 FTBFS on ppc64el [1] and riscv64 [2], where it built previously. I've copied what I hope is the relevant part of the log below. This