Re: baffled .. the 2019-01-27 debian-10.0-ppc64-NETINST-1.iso not bootable
It’s *possible* that the DVD drive in the dual-socket machine is not able to boot from DVD-RW. (I have seen this before occasionally)
Try burning to a DVD-R
Just a thought…
Rick
PS: Also note that Adrian is in the process of making an updated boot CD for PowerPC64. See the recent mail in the Debian PowerPC list.
> On Apr 5, 2019, at 8:16 PM, Dennis Clarke <dclarke@blastwave.org> wrote:
>
> On 4/5/19 11:00 PM, Dennis Clarke wrote:
>>
>> So here is further odd behavior. At this point I am just going to dig in
>> and keep plugging away here.
>>
>> I fetched from :
>>
>>
>> https://cdimage.debian.org/cdimage/ports/2019-01-27/debian-10.0-ppc64-NETINST-1.iso
>>
>
>
> Carefulyl tested. It boots fine on a PowerMac G5 "quad" unit but not on
> a PowerMac G5 which is a dual socket PPC970FX unit. No idea why.
>
> I was able to get a very very basic install from the 2018 netinst but
> then I am stonewalled by the usual gpg signature issues :
>
> root@callisto:~# vi /etc/apt/sources.list
> root@callisto:~# apt-get update
> Get:1 http://ftp.debian.org/debian unstable InRelease [242 kB]
>
> Get:2 http://incoming.debian.org/debian-buildd buildd-unstable InRelease
> [54.5 kB]
> Get:3 http://ftp.ports.debian.org/debian-ports unstable InRelease [47.1
> kB]
> Get:4 http://incoming.ports.debian.org/buildd unstable InRelease [49.1
> kB]
> Get:5 http://ftp.ports.debian.org/debian-ports unreleased InRelease
> [52.4 kB]
> Get:6 http://incoming.debian.org/debian-buildd buildd-unstable/main
> Sources [37.5 kB]
> Err:3 http://ftp.ports.debian.org/debian-ports unstable InRelease
> The following signatures couldn't be verified because the public key
> is not available: NO_PUBKEY DA1B2CEA81DCBC61
> Get:7 http://ftp.debian.org/debian unstable/main Sources [8735 kB]
> Err:5 http://ftp.ports.debian.org/debian-ports unreleased InRelease
> The following signatures couldn't be verified because the public key
> is not available: NO_PUBKEY DA1B2CEA81DCBC61
> Err:4 http://incoming.ports.debian.org/buildd unstable InRelease
> The following signatures couldn't be verified because the public key
> is not available: NO_PUBKEY DA1B2CEA81DCBC61
> Reading package lists... Done
>
> W: GPG error: http://ftp.ports.debian.org/debian-ports unstable
> InRelease: The following signatures couldn't be verified because the
> public key is not available: NO_PUBKEY DA1B2CEA81DCBC61
> E: The repository 'http://ftp.ports.debian.org/debian-ports unstable
> InRelease' is not signed.
> N: Updating from such a repository can't be done securely, and is
> therefore disabled by default.
> N: See apt-secure(8) manpage for repository creation and user
> configuration details.
> W: GPG error: http://ftp.ports.debian.org/debian-ports unreleased
> InRelease: The following signatures couldn't be verified because the
> public key is not available: NO_PUBKEY DA1B2CEA81DCBC61
> E: The repository 'http://ftp.ports.debian.org/debian-ports unreleased
> InRelease' is not signed.
> N: Updating from such a repository can't be done securely, and is
> therefore disabled by default.
> N: See apt-secure(8) manpage for repository creation and user
> configuration details.
> W: GPG error: http://incoming.ports.debian.org/buildd unstable
> InRelease: The following signatures couldn't be verified because the
> public key is not available: NO_PUBKEY DA1B2CEA81DCBC61
> E: The repository 'http://incoming.ports.debian.org/buildd unstable
> InRelease' is not signed.
> N: Updating from such a repository can't be done securely, and is
> therefore disabled by default.
> N: See apt-secure(8) manpage for repository creation and user
> configuration details.
> root@callisto:~#
> root@callisto:~#
> root@callisto:~# uname -a
> Linux callisto 4.16.0-1-powerpc64 #1 SMP Debian 4.16.5-1 (2018-04-29)
> ppc64 GNU/Linux
> root@callisto:~#
> root@callisto:~# cat /etc/debian_version
> buster/sid
> root@callisto:~#
>
> So .. that's nice. Not sure how to get around the need for that key.
>
> Dennis
>
Reply to: