My suggestion continues to be to delete all your partitions, and let the ISO
installer install the partitions it wants to install.
It has worked for me every time.
But if you don’t want to do that, and it fails to install for you, then I have
no further suggestions.
Best,
Ken
> On Mar 25,
Completely erase the hard drive, until you have a totally blank disk, with no
partitions whatsoever on it.
To do this, I mounted the HD using Firewire disc mode from another system, and
formatted it until it was bare.
Then let the CD installer ISO take care of doing everything. Let it use the
On 3/18/22 11:59 AM, John Paul Adrian Glaubitz wrote:
> Hello!
>
> I have created the first set of installation images in 2022, these are
> available at the usual location in [1].
>
> The ISO image for sparc64 has been verified to work correctly, I don't
> know about the other architectures,
Correction: The Pismo has 1 GiB memory.
On 3/25/22 9:06 PM, Stan Johnson wrote:
> On 3/18/22 11:59 AM, John Paul Adrian Glaubitz wrote:
>> Hello!
>>
>> I have created the first set of installation images in 2022, these are
>> available at the usual location in [1].
>>
>> The ISO image for sparc64
Hello!
> On Mar 26, 2022, at 12:07 AM, Peter wrote:
>
> Or does this mean that /boot/grub is mounted read-only and I have to
> follow the procedure you described?
If the screen remains black, it means the firmware is missing inside the initrd
that the kernel was booted with, hence the
Hi Adrian,
Thanks for the fast reply. The firmware-amd-graphics was already
installed (via linux-firmware-nonfree? I didn't install it manually).
Still a black screen.
Or does this mean that /boot/grub is mounted read-only and I have to
follow the procedure you described?
Peter
pvz@ibook:~$
Hello,
A thank you goes out to all the people who have attempted to help me.
In all the excitement of this endeavor, my G4's motherboard has died.
Based on previous discussion, I believe the culprit in its failure to
load GRUB was the system's memory. Upon closer inspection of the machine
Hello,
Bad memory modules can actually result in such weird behavior. We've seen
similar reports
before.
When I have time, I'll run a memory test. Can this be done from OF? What
commands should I use?
You can also create a fresh chroot from unstable using debootstrap and that
pivot
the
El vie, 25-03-2022 a las 08:43 +0100, John Paul Adrian Glaubitz
escribió:
> Hello!
>
> I would like to ask users running Debian on a real PowerMac machine
> (G3, G4, G5 etc)
> to help me verify a theory on the boot mechanism. In particular, the
> question is
> whether we can skip setting the
Hello!
On 3/25/22 12:48, Ben Westover wrote:
>> What is more likely is that you have bad memory modules in your machines and
>> Yaboot
>> just happens to use different memory regions which is why it's not affected
>> by the
>> problem.
>
> Hmmm… this computer came from my High School's IT
Hello Adrian,
What is more likely is that you have bad memory modules in your machines and
Yaboot
just happens to use different memory regions which is why it's not affected by
the
problem.
Hmmm… this computer came from my High School's IT department, so its RAM
was upgraded by High
Hi Peter!
On 3/25/22 11:58, Peter van Zaanen wrote:
> https://cdimage.debian.org/cdimage/ports/snapshots/2022-03-24/
>
> works without a problem, and my iBook boots and starts loading the
> kernel. I added linux-firmware-nonfree, but it boots to a completely
> black screen. I can only access the
The grub install with the latest image from
https://cdimage.debian.org/cdimage/ports/snapshots/2022-03-24/
works without a problem, and my iBook boots and starts loading the
kernel. I added linux-firmware-nonfree, but it boots to a completely
black screen. I can only access the iBook via ssh.
On 2022-03-25, John Paul Adrian Glaubitz wrote:
> I would like to ask users running Debian on a real PowerMac machine
> (G3, G4, G5 etc) to help me verify a theory on the boot mechanism. In
> particular, the question is whether we can skip setting the
> boot-device in NVRAM in the grub-installer
Hello!
On 3/25/22 09:56, John Ogness wrote:
> I suppose it would be better if someone did the test on a system where
> *only* Linux is installed, to make sure that OpenFirmware is able to
> find GRUB without boot-device being set.
I have already tested that on my iBook G4 and it still boots fine
Hi Mark!
On 3/25/22 09:51, Mark Cave-Ayland wrote:
> However I suspect the reason the NVRAM is changed is for the case of dual-boot
> machines where the existing MacOS partition is first shrunk and the Linux
> partitions
> added at the end. In this case without the OF NVRAM boot-device update
On 25/03/2022 07:37, John Paul Adrian Glaubitz wrote:
Hi Mark!
On 3/24/22 16:39, John Paul Adrian Glaubitz wrote:
On 3/24/22 15:40, John Paul Adrian Glaubitz wrote:
Are there any plans to improve the NVRAM emulation in QEMU or is there any
alternative
command that we should run on
cam@propaganda:~$ cat /proc/cpuinfo
processor : 0
cpu : PPC970, altivec supported
clock : 1600.00MHz
revision: 2.2 (pvr 0039 0202)
timebase:
platform: PowerMac
model : PowerMac7,2
machine : PowerMac7,2
motherboard
Hello Cameron!
On 3/25/22 09:40, Cameron MacPherson wrote:
> nvram --print-config='boot-device /pci@f400/ata-6@d/@0:2,\\:txbi'
> nvram --update-config boot-device=""
> nvram --print-config=boot-device
> reboot
>
> result is another login prompt
On which machine exactly?
And by "another
hi,
nvram --print-config='boot-device /pci@f400/ata-6@d/@0:2,\\:txbi'
nvram --update-config boot-device=""
nvram --print-config=boot-device
reboot
result is another login prompt
On Fri, Mar 25, 2022, 12:44 AM John Paul Adrian Glaubitz <
glaub...@physik.fu-berlin.de> wrote:
> Hello!
>
> I
Hello!
I would like to ask users running Debian on a real PowerMac machine (G3, G4, G5
etc)
to help me verify a theory on the boot mechanism. In particular, the question is
whether we can skip setting the boot-device in NVRAM in the grub-installer
script
which causes incompatibilities with the
Hi Mark!
On 3/24/22 16:39, John Paul Adrian Glaubitz wrote:
> On 3/24/22 15:40, John Paul Adrian Glaubitz wrote:
>> Are there any plans to improve the NVRAM emulation in QEMU or is there any
>> alternative
>> command that we should run on QEMU-based systems?
>
> OK, the solution is actually as
22 matches
Mail list logo
