Hello,
On Tue, 7 Jan 2025 14:15:01 +0530 Aditi Mishra wrote:
> May I know which patches you have removed?
As already mentioned, it's this patch [1] that broke the framebuffer.
> Also, does installer hangs at the time of language selection or before ?
The installer does not hang, th
Hello Niels,
this should be discussed on the mailing list, CC'ing it.
On Wed, 2025-01-15 at 23:16 +0100, Niels de Vries wrote:
> Found this issue here
> (https://www.mail-archive.com/debian-powerpc@lists.debian.org/msg71505.html)
> This issue is still current, so the main ppc64
ore only?
This particular patch [1] breaks the console output extremely early so that
debian-installer doesn't even show.
I have also observed that while removing this patch makes debian-installer
load, it also seems to hang during language selection. I have not figured
out yet what the rea
Hello,
I was finally able to track down the problem this morning which breaks
debian-installer console output on powerpc and ppc64 since kernel v6.8.
There is a patch [1] in the current Debian kernel package which was supposed
to fix the exact same problem [2] on ppc64el and it was introduced
Hello,
just as a heads-up: We still don't know what the underlying problem of
the lockup on PowerMac G5 systems is when trying to boot the latest
installer images.
All I know so far is that the problem can be reproduced on QEMU and the
last working image is image created 2023-06-18:
&g
> in either debian-installer or debian-cd to break the installation CD.
>
> I will need to perform more debugging.
I just had another idea for testing which is building a current installation
image with an old, known
to work kernel. This will help verify whether it's actually an
-new/debian-12.0.0-ppc64-NETINST-1.iso
>
> Both behaved the same way. Got to the installer menu, I choose an install
> mode,
> showed "loading..." for approximately 1 minute bit, then showed normal
> messages like
> 'Quiescing OpenFirmware...' and 'Booti
Hi Adrian,
I tried these on my Dual-processor PCI-X G5.
>
https://cdimage.debian.org/cdimage/ports/tests/ppc64-test/debian-12.0.0-ppc64-NETINST-1.iso
>
https://cdimage.debian.org/cdimage/ports/tests/ppc64-test-new/debian-12.0.0-ppc64-NETINST-1.iso
Both behaved the same way. Got to the ins
Hello,
I have done some debugging on ppc64 to find out why the the kernel no
longer boots on PowerPC G5 (PowerPC 970) systems.
It turns out that the issue is much more complicated than I expected since
the same kernel that doesn't boot debian-installer boots perfectly fine
when installed
Hi,
Frank Scheiner wrote:
> > I believe you
> > can't have both FAT as OF bootstrap partition **and** blessing.
The only way would be that Apple had defined some protocol using the
specified capabilities of FAT, by which blessing and other Apple-specific
file properties can be expressed, and that
Hi,
John Paul Adrian Glaubitz wrote:
> What's the alternative HFS+ tree of the ISO? Does it write a small HFS+
> filesystem onto the ISO image?
Alternative trees are tradition in ISO 9660: Joliet, ISO 9660:1999, UDF.
They can refer to the same data file content as the ISO 9660 tree, but
have thei
Hello!
On Wed, 2023-05-10 at 10:03 +0200, Thomas Schmitt wrote:
> John Paul Adrian Glaubitz:
> > I just don't know how to bless a bootloader located on a FAT partition.
> > I know that xorriso does it and it works on ISO9660 filesystems, but I
> > don't understand how.
>
> xorriso attributes bles
Hi,
John Paul Adrian Glaubitz:
> I just don't know how to bless a bootloader located on a FAT partition.
> I know that xorriso does it and it works on ISO9660 filesystems, but I
> don't understand how.
xorriso attributes blessing to an alternative HFS+ tree of the ISO.
This HFS+ tree is advertise
Hi Stan!
Apologies for the late reply!
On Tue, 2023-05-02 at 12:35 -0600, Stan Johnson wrote:
> On 5/2/23 7:24 AM, John Paul Adrian Glaubitz wrote:
> > ...
> >
> > The former issue could be resolved if someone could find out how to boot
> > a PowerPC Mac from a FAT32 boot partition. It's suppose
Hi Adrian,
On 5/2/23 7:24 AM, John Paul Adrian Glaubitz wrote:
> ...
>
> The former issue could be resolved if someone could find out how to boot
> a PowerPC Mac from a FAT32 boot partition. It's supposed to work but I never
> verified that.
>
> If someone could test that, I can implement that a
I have to manually inject the
hfsprogs and partman-hfs packages into debian-installer.
Also, one always needs to make sure that the kernel in the debian-installer
image matches the kernel that is currently in unstable, otherwise you get
kernel/module version mismatch.
The former issue could be re
This does not appear to have happened (new images)
Is it something you can automate, or quasi-automate?
On 4/9/2023 11:16:01 PM, John Paul Adrian Glaubitz
wrote:
> On Apr 10, 2023, at 4:54 AM, Jeffrey Walton wrote:
>
> On Sun, Apr 9, 2023 at 6:38 PM Ken Cunningham
> wrote:
>>
>> Your issue is
> On Apr 10, 2023, at 4:54 AM, Jeffrey Walton wrote:
>
> On Sun, Apr 9, 2023 at 6:38 PM Ken Cunningham
> wrote:
>>
>> Your issue is in French, but it looks like the one I recently faced as well
>> if I am reading it correctly.
>>
>> I fixed it using the information on this page:
>>
>> ht
On Sun, Apr 9, 2023 at 6:38 PM Ken Cunningham
wrote:
>
> Your issue is in French, but it looks like the one I recently faced as well
> if I am reading it correctly.
>
> I fixed it using the information on this page:
>
> https://unix.stackexchange.com/questions/75807/no-public-key-available-on-apt
Your issue is in French, but it looks like the one I recently faced as well if
I am reading it correctly.
I fixed it using the information on this page:
https://unix.stackexchange.com/questions/75807/no-public-key-available-on-apt-get-update
I hope this helps you too.
Ken
> On Apr 9, 2023
Le 09/04/2023 à 23:09, John Paul Adrian Glaubitz a écrit :
Hello David!
On Apr 9, 2023, at 10:02 PM, David VANTYGHEM
wrote:
If someone could help me please. I have no idea of the problem.
Please provide the syslog file that is stored as /var/log/syslog
during installation. It’s otherwise
Hello David!
> On Apr 9, 2023, at 10:02 PM, David VANTYGHEM
> wrote:
>
> If someone could help me please. I have no idea of the problem.
>
Please provide the syslog file that is stored as /var/log/syslog during
installation. It’s otherwise not possible to debug the problem.
Adrian
and http:, ftp.ports.debian.org, /debian-ports/ too but the
installer can't access to them.
I'm using this AQEMU configuration:
/usr/bin/qemu-system-ppc -monitor stdio -k fr -machine accel=tcg -m 512
-drive
file="/home/david/Documents/Informatique/Documentation/Macintosh/debian-11.0.0-powerpc-N
root, /home, and swap. (So /boot is a
directory in the root volume. If grub wants a kernel and initrd, it has to dig
around in the LVM to find them)
Unlike the ppc64 installation, the installer did not complain about this setup.
(The ppc64 installation complained that there was no partition fo
On Wed, Apr 21, 2021, at 4:26 AM, John Paul Adrian Glaubitz wrote:
> >> This issue might not even specific to PowerMacs, so it
> >> would make more
> >> sense first to test this on x86 systems and report a bug against
> >> src:grub2 or partman-lvm
> >> if the issue shows there as well.
> >
>
eful because it means I will have to
spend less time doing
that myself and can fix the issues more efficiently.
You can also grep the debian-installer, GRUB and related sources on Salsa and
sources.debian.org
to see where the error message comes from. That information is very helpful,
too, and it al
On Tue, Apr 20, 2021, at 2:31 AM, John Paul Adrian Glaubitz wrote:
> I don't understand the hurry to
> make everything
> perfect at once.
I'm sorry if it seems that way. That is not my intent. I'm just reporting
what I see.
It's definitely not mission critical. The machine still boots, jus
On 4/20/21 11:16 AM, Rick Thomas wrote:
> Presumably, this message, and the check that issues it, are relics of the
> past when
> grub was not able to dig into LVM partitions to find the kernel and initrd.
> Now that
> grub understands LVM, the check and associated message are no longer
> necess
ng to fix it at some point. But
> since I am doing this in my freetime and I'm not getting paid for that,
> I'm not working on it every day.
>
> Fixing installer issues is not trivial and requires lots of testing, getting
> it working last week took me four days and 10-
aid for that,
I'm not working on it every day.
Fixing installer issues is not trivial and requires lots of testing, getting
it working last week took me four days and 10-15 installation runs, so I
cannot work on it every day.
> (2) Are the messages necessary that complain about "can'
Well... I'm not very good at letting well enough alone, so I tried installing
again. This time I used the "default install" and when it came to
partitioning, I chose the LVM option. This time, it complained that there was
no partition for /boot (though when I poked around a bit, there _was_ a
I tried it this afternoon on my PowerMac G5 - PowerMac7,3. Works great! I
used the default installation and "all in one partition" partitioning. Let me
know if you would like me to try something else.
Thanks so much for all your work! This is fantastic...
Enjoy!
Rick
On Fri, Apr 16, 2021,
On 17 Apr 2021, at 10:19, Jeffrey Walton wrote:
This is likely correct. I experienced the same issue when trying to
boot from USB.
I just burned a plain old bootable CD and things worked fine.
Yep, I think that both of you are correct. I had no trouble to boot from
USB using this OF comman
On Sat, Apr 17, 2021 at 2:48 AM Rick Thomas wrote:
>
> On Fri, Apr 16, 2021, at 5:30 AM, John Paul Adrian Glaubitz wrote:
> > On 4/16/21 1:57 PM, Johannes Brakensiek wrote:
> > > ...
> > > Ok, good to know. Then I suppose the Mac’s firmware just won’t detect it
> > > if it’s copied to a USB stick
On Fri, Apr 16, 2021, at 5:30 AM, John Paul Adrian Glaubitz wrote:
> On 4/16/21 1:57 PM, Johannes Brakensiek wrote:
> >
> > On 16 Apr 2021, at 13:54, John Paul Adrian Glaubitz wrote:
> >
> >> But the image is blessed in HFS vocabulary. If you insert such a CD and
> >> press the
> >> key duri
On 4/16/21 9:01 AM, John Paul Adrian Glaubitz wrote:
> On 4/16/21 2:55 PM, Dennis Clarke wrote:
>> Then if I accept this :
>>
>> Your boot partition is not located on the first primary partition of
>> your hard disk. This is needed by your machine in order to boot.
>> Please go back and
On 4/16/21 2:55 PM, Dennis Clarke wrote:
> Then if I accept this :
>
> Your boot partition is not located on the first primary partition of
> your hard disk. This is needed by your machine in order to boot.
> Please go back and use your first primary partition as a boot
> partition
UT: 4 299045033472-300069027327 1023993856
primary linux-swap /dev/sda4swap
parted_server: OUT: -1 300069027328-300069052415 25088 primary
free/dev/sda-1
parted_server: Partitions printed
parted_server: OUT:
This is from the automated use the whole disk partitio
On 4/16/21 1:57 PM, Johannes Brakensiek wrote:
>
> On 16 Apr 2021, at 13:54, John Paul Adrian Glaubitz wrote:
>
>> But the image is blessed in HFS vocabulary. If you insert such a CD and
>> press the
>> key during boot, the CD will be selectable during boot.
>
> Ok, good to know. Then I suppos
On 4/16/21 1:56 PM, David VANTYGHEM wrote:
> I tried a new installation with 14/04 ISO file, default installation,
> whole disk and only one partition (no /home partition). I've got this
> error message at the end :
Well, this is an error with setting the contents of NVRAM. Your emulated
machine d
On 4/16/21 5:40 AM, John Paul Adrian Glaubitz wrote:
> Hello!
>
> As promised, new images:
>
>> https://cdimage.debian.org/cdimage/ports/snapshots/2021-04-16/
>
> ppc64 should install fine on PowerMac G5 now.
>
> Adrian
>
I will jump on that right now !
--
Dennis Clarke
RISC-V/SPARC/PPC/AR
Le 16/04/2021 à 14:00, Johannes Brakensiek a écrit :
Hey David,
On 16 Apr 2021, at 13:56, David VANTYGHEM wrote:
In english : The boot partition isn't the first primary partition on
the disk. This is necessary to boot the machine. Please restart and
use the first primary partition as boot pa
Hey David,
On 16 Apr 2021, at 13:56, David VANTYGHEM wrote:
In english : The boot partition isn't the first primary partition on
the disk. This is necessary to boot the machine. Please restart and
use the first primary partition as boot partition.
If you don't come back to the partition menu
On 16 Apr 2021, at 13:54, John Paul Adrian Glaubitz wrote:
But the image is blessed in HFS vocabulary. If you insert such a CD
and press the
key during boot, the CD will be selectable during boot.
Ok, good to know. Then I suppose the Mac’s firmware just won’t
detect it if it’s copied to a
I tried a new installation with 14/04 ISO file, default installation,
whole disk and only one partition (no /home partition). I've got this
error message at the end :
Then I'm trying with today ISO file and now, the installations fails here :
In english : The boot partition isn't the first pr
Hi!
On 4/16/21 1:38 PM, Johannes Brakensiek wrote:
>> ppc64 should install fine on PowerMac G5 now.
>
> hooray! It works - smoothly! Very great! 🎉
OK, good. It was an obvious oversight when building the image and had nothing
to do with the changes I made to the various d-i packages itself.
> Re
Hello Adrian,
On 16 Apr 2021, at 11:40, John Paul Adrian Glaubitz wrote:
As promised, new images:
https://cdimage.debian.org/cdimage/ports/snapshots/2021-04-16/
ppc64 should install fine on PowerMac G5 now.
hooray! It works - smoothly! Very great! 🎉
Really nice. To say it with words li
Hello!
As promised, new images:
> https://cdimage.debian.org/cdimage/ports/snapshots/2021-04-16/
ppc64 should install fine on PowerMac G5 now.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berl
World machines.
Well, that was an important missing piece of information.
Sorry :( As I mentioned before the old installer worked fine on both QEMU machines,
and since David reported that his -M mac99 installation failed then I figured the
problem was elsewhere.
ATB,
Mark.
On 4/16/21 9:29 AM, Mark Cave-Ayland wrote:
>> Because I am starting to question my sanity. If you're showing me that
>> arch-detect
>> is detecting the machine correctly and you used the latest image which I
>> tested
>> myself on real hardware, then it's not possible that the partioner will use
On 16/04/2021 08:21, John Paul Adrian Glaubitz wrote:
On 4/16/21 8:59 AM, Mark Cave-Ayland wrote:
The interesting part will be to see what arch-detect prints out in the
installer. You can just run it from a second terminal. If it doesn't
detect a newworld machine, GRUB installation won&#
On 4/16/21 8:59 AM, Mark Cave-Ayland wrote:
>> The interesting part will be to see what arch-detect prints out in the
>> installer. You can just run it from a second terminal. If it doesn't
>> detect a newworld machine, GRUB installation won't work.
>
&g
On 4/16/21 8:53 AM, David VANTYGHEM wrote:
> I don't have arch-detect but a archdetect command :
>
> # archdetect
>
> powerpc/powermac_newworld
Then I have no clue what's wrong and you will need to debug the
problem yourself.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Develope
"powerpc/powermac_newworld",
neither the automatic partioning nor the installation of GRUB for PowerMacs is
triggered correctly.
I see, thanks - my confusion was that the old installer used to always set up
the partitioning regardless
of the machine type and so it was possible to boot on both an
On 16/04/2021 07:48, John Paul Adrian Glaubitz wrote:
On 4/16/21 8:39 AM, Mark Cave-Ayland wrote:
https://salsa.debian.org/installer-team/libdebian-installer/-/blob/master/src/system/subarch-powerpc-linux.c
Here's what I get for the QEMU machines:
The interesting part will be to see
Le 16/04/2021 à 08:48, John Paul Adrian Glaubitz a écrit :
On 4/16/21 8:39 AM, Mark Cave-Ayland wrote:
https://salsa.debian.org/installer-team/libdebian-installer/-/blob/master/src/system/subarch-powerpc-linux.c
Here's what I get for the QEMU machines:
The interesting part will be t
On 4/16/21 8:39 AM, Mark Cave-Ayland wrote:
>>> https://salsa.debian.org/installer-team/libdebian-installer/-/blob/master/src/system/subarch-powerpc-linux.c
>
> Here's what I get for the QEMU machines:
The interesting part will be to see what arch-detect prints out in the
ins
ot;,
>> neither the automatic partioning nor the installation of GRUB for PowerMacs
>> is triggered correctly.
>
> I see, thanks - my confusion was that the old installer used to always set up
> the partitioning regardless
> of the machine type and so it was possible
as "arch-detect" expects them, the installer
is not able to properly detect your platform.
I mean, I tested this whole thing on an actual iBook G4 and it works as
expected, so if QEMU's emulation is accurate, the end result must be
the same for the powerpc image (I'm not
n.org/installer-team/libdebian-installer/-/blob/master/src/system/subarch-powerpc-linux.c
Here's what I get for the QEMU machines:
Old World (default or -M g3beige):
root@debian:~# cat /proc/cpuinfo
processor : 0
cpu : 740/750
temperature : 50-126 C (uncalibra
UB for PowerMacs is
triggered correctly.
I see, thanks - my confusion was that the old installer used to always set up the
partitioning regardless of the machine type and so it was possible to boot on both an
Old World and a New World machine.
Are Old World Macs no longer supported?
# umount
n.org/installer-team/libdebian-installer/-/blob/master/src/system/subarch-powerpc-linux.c
Adrian
Under QEMU, my machine is :
https://cryptpad.fr/file/#/2/file/YT77NWCuXe-1Zei6sAam49SS/
(pcmacgeneration : NewWorld)
--
Passez à Linux : https://infolib.re
.--.
|o_o |
||_/ |
//\\E
On 4/16/21 7:56 AM, David VANTYGHEM wrote:
> Inded, I don't have the HFS partition too.
Then the emulation is not behaving as a real machine.
QEMU needs display the right information below /proc/cpuinfo:
> https://salsa.debian.org/installer-team/libdebian-installer/-/blob/master
stallation and part-modified.png is after I had manually
removed the / partition, added the /boot/grub HFS partition (I guess a
32MB size?) and then assigned the remaining space to the / partition
once again.
Once this was done, I let the base install run all the way up until
the point where the
On 4/16/21 1:27 AM, Mark Cave-Ayland wrote:
>> Yeah. From what I can see from links [1] and [2] I'd expect this to be
>> working now.
>> Let me run an install of the latest ISO here, since then I can then use a
>> debugger
>> on QEMU/OpenBIOS to find out what the problem may be.
> (...)
> The mai
emoved the / partition, added the
/boot/grub HFS partition (I guess a 32MB size?) and then assigned the remaining space
to the / partition once again.
Once this was done, I let the base install run all the way up until the point where
the installer prompted me for the mirror information. At th
On 15/04/2021 20:23, John Paul Adrian Glaubitz wrote:
OK, I was already wondering about that. grub-install contains a bless utility
and function only, but not something for the UNIX filetype.
Question: If the blessing is sufficient and the setting of the filetype not
necessary,
why
ition?
There is either a bug in GRUB or I'm using it incorrectly.
If we could use GRUB's own blessing utility and waive for hfsutils altogether,
we could
simplify the current code in grub-installer for PowerMacs [1] even further. But
at the
moment, the current changes are what I kn
ertainly what OpenBIOS does.
Ah, I wasn't aware of that.
I guess the real question is does Apple's OF do the right thing here? My
feeling is that it
does, since grub.chrp.in uses the hard-coded path
\System\Library\CoreServices\grub.elf
which is a directory that only exists if grub is
pected. As can be
>> seen from the number of test images I have created so far [1], I have already
>> been through quite a number of image rebuilds to get the grub-installer work
>> correctly on PowerMac (ignore the timestamps in the folder names, the correct
>> timestamps o
been through quite a number of image rebuilds to get the grub-installer work
correctly on PowerMac (ignore the timestamps in the folder names, the correct
timestamps of the images can be seen from the creation date in the folder view).
Great work Adrian!
The latest image is in the folder "hf
#x27;t which is most likely attributed
> to a
> race condition.
>
> The problem is that setting the correct file properties with the hattrib tool
> fails at the first attempt of installing the bootloader but succeeds when just
> reattempting to install the bootloader from the installer
grub-installer work
correctly on PowerMac (ignore the timestamps in the folder names, the correct
timestamps of the images can be seen from the creation date in the folder view).
The latest image is in the folder "hfstest-20210411-8" which I created this
morning. This image is not tested y
e the disk partitioning code path in this image at all. I guess
that's a reasonable way to work around the current breakagepartition with
the old installer, then reboot with a newer one after the partitioning step is
complete.
Adrian
Hello Alex!
On 1/4/21 1:36 AM, Alex Perez wrote:
> If you've successfully gotten 32-bit PowerPC Debian installed using one of
> the recent Debian Ports
> snapshot CDs (I used
> https://ftp.acc.umu.se/cdimage/ports/snapshots/2020-11-09/debian-10.0.0-powerpc-\
> NETINST-1.iso) but have no installe
If you've successfully gotten 32-bit PowerPC Debian installed using one
of the recent Debian Ports snapshot CDs (I used
https://ftp.acc.umu.se/cdimage/ports/snapshots/2020-11-09/debian-10.0.0-powerpc-NETINST-1.iso)
but have no installed bootloader (grub install fails), here's what you
can do to
On 12/29/20 6:54 PM, Riccardo Mottola wrote:
> I tried once again and edited partition manually: I created a separate /boot
> partition formatted ext3. The system installed and yaboot works just fine.
As expected. Current versions of Yaboot don't support modern ext4, ext2/3 work
fine though. Not s
uires the /boot partition to be ext2 or ext3, it won't work with the
ext4
in Debian unstable. This is one of the many reasons why I prefer GRUB.
> Maybe I am bitten by the fact that the installer partitioned ext4 root, but
> yaboot
> doesn't know about it. I will retry with a se
located in this [1] folder all use Yaboot, both for booting the
installer as well as for the installed system.
Adrian
> [1] https://cdimage.debian.org/cdimage/ports/10.0/powerpc/iso-cd/
> [2] https://cdimage.debian.org/cdimage/ports/10.0/ppc64/iso-cd/
--
.''`. John Paul Ad
Hi Adrian,
On 12/28/20 9:51 PM, John Paul Adrian Glaubitz wrote:
You should try to install one of the Yaboot images to make sure there is no
problem
with your machine.
That could be a check to perform... where is the last working yaboot image to
be found?
See:https://cdimage.debian.org/cdima
/ports/10.0/
If I install one of those images, yaboot gets installed and gets loaded
at reboot, although boot finally fails with "unknown or corrupt
filesystem" when loading the kernel. I used standard partitioning.
Maybe I am bitten by the fact that the installer partitioned ext4
Adrian,
John Paul Adrian Glaubitz wrote on 12/28/20 11:58 AM:
>> Yet at the end, no apparent important errors, not even noticeable at any step
>> in console, the request of reboot yields a flashing OS folder.
> You should try to install one of the Yaboot images to make sure there is no
> problem
(Please keep the conversation on the list)
On 12/28/20 9:49 PM, Riccardo Mottola wrote:
> On 12/28/20 8:58 PM, John Paul Adrian Glaubitz wrote:
>>> The only small thing is that I enabled non-free and then there are warnings
>>> since the repository doesn't have it, but it was to be expected.
>> Wh
On 12/28/20 7:31 PM, Riccardo Mottola wrote:
> On 12/28/20 1:53 AM, John Paul Adrian Glaubitz wrote:
>> Well, it's broken at the moment and I will fix that within the
>> next days.
>
> what are you going to fix? the glibc issue you say shouldn't matter.
The glibc issue prevents me from using my p
Hi Adrian,
On 12/28/20 1:53 AM, John Paul Adrian Glaubitz wrote:
Well, it's broken at the moment and I will fix that within the
next days.
what are you going to fix? the glibc issue you say shouldn't matter.
I did another interesting thing. I run the "expert installation" of the
most curre
On 12/28/20 1:28 AM, Riccardo Mottola wrote:
> Frustrating, I must say.
Well, it's broken at the moment and I will fix that within the
next days.
You can either use a Yaboot-based image if it's really urgent or just
wait.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - g
hen in rescuemode on chroot in the
targetroot
hformat -l "NewWorld Bootblock" "/dev/sda2"'
but now? If I try to run "grub-installer" in a rescue shell (not in
target root) it fails because grub-proble fails to get the canonical
path of rootfs and /boot . M
n in glibc 2.31 and unless someone is willing
to help me debug the issue, the bug will remain until I have found the
time to work on this.
I am planning to do that next week. So far I have not found the glibc
change that is causing the partman problem. Debugging this is not
trivial as it requires i
Hi,
the MintPPC project uses the images from 2020-04-19
https://cdimage.debian.org/cdimage/ports/snapshots/2020-04-19/
I guess, this should work.
Karl
> Am 27.12.2020 um 14:49 schrieb John Paul Adrian Glaubitz
> :
>
> On 12/27/20 2:39 PM, Riccardo Mottola wrote:
>> Unfortunately, it does not
On 12/27/20 2:39 PM, Riccardo Mottola wrote:
> Unfortunately, it does not work for me, the installation step of the
> bootloader
> fails. hfsutils is not found (package missing on the CD?) thus I suppose newfs
> of the grub partition fails and the step aborts, I have seen that in some
> other
> o
Hi Adrian
On 12/27/20 11:19 AM, John Paul Adrian Glaubitz wrote:
I have read previous threads about hfsutils, but thought they were fixed, as
per your
mail with Frank Scheiner.
I cannot make any further tests to the grub-installer code at the moment since
we need
to fix the partman issue
any further tests to the grub-installer code at the moment since
we need
to fix the partman issue first.
> Is there a known-good working snapshot for ppc64 macs?
Yes, 2020-05-30 should work [1].
> And... Frohe Weihnachten!
Same to you.
Adrian
> [1] https://cdimage.debian.org/c
Hi Adrian,
On 12/25/20 2:20 AM, John Paul Adrian Glaubitz wrote:
This has all been debugged and discussed on the list.
I just hadn't had the time to continue working on the issues with partman yet.
I have read the threads with Dennis, but found no solution, conclusion
about it. Can you poin
Hi!
On 12/25/20 1:43 AM, Riccardo Mottola wrote:
> 2020-12-03: installs, no boot
>
> 2020-11-16: installs, no boot
>
> 2020-10-13: broken image, installer starts, but finds "no device for
> installation media was detected" (cdrom mount fails)
>
> 2020-10-
Hi,
since the 2020-12-03 image did not work (installs, but system does not
boot) I tried walking back in time... and see
2020-12-03: installs, no boot
2020-11-16: installs, no boot
2020-10-13: broken image, installer starts, but finds "no device for
installation media was det
Hi,
On 12/3/20 3:05 PM, John Paul Adrian Glaubitz wrote:
Hi!
I uploaded updated Debian installer CD images today.
These come with the latest versions of the kernel and the debian-installer
application as well as various other updates. The images can be found at
the usual location [1] as well
On 12/5/20 2:44 PM, Jeffrey Walton wrote:
>> Your blank screen may have a different cause such as such as missing
>> firmware for your graphics card which is a result of Debian Ports
>> currently not having access to contrib and non-free during
>> installation - something I can't influence but that
On Sat, Dec 5, 2020 at 6:36 PM Dennis Clarke wrote:
> ...
> get to a shell with strange
> "busybox" wherein the "ls" command does not support the letter "b" or
> the letter "p" option.
That's par for the course with Busybox. It can be anemic at times. For
example, chmod mode only takes letters li
"folder" icon in
the center. This seems to indicate that the machine can not find a boot
sector or boot loader on the default boot device. If I leave the install
dvd in the dvd drive then the blinking folder goes away after about five
seconds and I get the grub menu from the installer. Her
On Sat, Dec 5, 2020 at 4:15 AM John Paul Adrian Glaubitz
wrote:
>
> Your blank screen may have a different cause such as such as missing
> firmware for your graphics card which is a result of Debian Ports
> currently not having access to contrib and non-free during
> installation - something I can
1 - 100 of 1136 matches
Mail list logo
