Hi!
On 12/3/20 6:08 PM, John Paul Adrian Glaubitz wrote:
> So, my wild guess is that's a regression in glibc, util-linux or the kernel
> as parted wasn't updated either and no other package is involved.
It *might* be related to this change [1] in glibc since the parted_server.c code
uses the %ms
Hello!
On 11/11/20 10:29 AM, John Paul Adrian Glaubitz wrote:
>> Did you provide such a command ?
>
> No, not yet when running valgrind. But I guess I should do that on the
> test system. I'll try that, thanks for the suggestion.
I have tried that now. valgrind didn't find any leaks.
On 11/19/20 9:29 AM, Jeroen Diederen wrote:
> Is there any news on this ?
Not yet. I'm currently busy with other job-related stuff, but it's
still on my TODO pile, so don't worry.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie
Hi all,
Is there any news on this ?
Have a nice day!
Jeroen
On 11/11/20 10:25 AM, Thomas Schmitt wrote:>> Valgrind didn't find any memory
leaks, so I'm currently out of ideas:
>> [..] valgrind --leak-check=yes ./parted_server
>> [...]
>> ==280387== in use at exit: 0 bytes in 0 blocks
>
> I had a look at the code and wonder how the variable
On 11/11/20 9:24 AM, John Paul Adrian Glaubitz wrote:
> Valgrind didn't find any memory leaks, so I'm currently out of ideas:
Next thing to try would be replacing the parted_server binary from a known
working version of the partman-base package.
Older versions of the package can be found here
Hi,
John Paul Adrian Glaubitz wrote:
> Valgrind didn't find any memory leaks, so I'm currently out of ideas:
> [..] valgrind --leak-check=yes ./parted_server
> [...]
> ==280387== in use at exit: 0 bytes in 0 blocks
I had a look at the code and wonder how the variable "device_name"
gets freed
On 11/10/20 11:15 PM, John Paul Adrian Glaubitz wrote:
> On 11/10/20 10:21 PM, John Paul Adrian Glaubitz wrote:
>> On 11/9/20 10:02 PM, John Paul Adrian Glaubitz wrote:
>>> Okay, that has been fixed and mounting the CD works again [1].
>>>
>>> But for some reason partman (the partitioning tool) is
Forgot the reference:
On 11/10/20 11:15 PM, John Paul Adrian Glaubitz wrote:
> Turns out that parted_server is crashing with a:
>
> free(): invalid next size (fast)
>
> in command_open() [1]. I don't know yet why that happens but that explains
> why the partitioning just hangs forever.
On 11/10/20 10:21 PM, John Paul Adrian Glaubitz wrote:
> On 11/9/20 10:02 PM, John Paul Adrian Glaubitz wrote:
>> Okay, that has been fixed and mounting the CD works again [1].
>>
>> But for some reason partman (the partitioning tool) is hanging now.
>
> So far I know that the "DUMP" command for
On 11/9/20 10:02 PM, John Paul Adrian Glaubitz wrote:
> Okay, that has been fixed and mounting the CD works again [1].
>
> But for some reason partman (the partitioning tool) is hanging now.
So far I know that the "DUMP" command for partman is hanging, i.e.
try executing "partman-dump" in
> On Nov 10, 2020, at 7:54 PM, Jeroen Diederen wrote:
>
> Do you have a fix for partman also?
Not yet. That’s a completely different problem which will require some more
debugging.
Adrian
well done Adrian!
I'm sometimes not very smart ;-).
Will fix that. Working image by tomorrow.
Adrian
Do you have a fix for partman also?
On 11/10/20 7:01 PM, John Paul Adrian Glaubitz wrote:
> Ok, your syslog is actually complete. I was confused by your previous
> messages.
>
> Just sending the syslog file is enough, no need to send anything else.
>
> Anyway, the error is here:
>
> Nov 10 17:15:58 mk-hfs-bootstrap: `hformat -l
On 11/10/20 6:59 PM, John Paul Adrian Glaubitz wrote:
> Just grepping for GRUB doesn't help. We're just seeing
>
> "Configuring 'grub-installer' failed with error code 1"
>
> which is already something that we already know, i.e. "GRB installation
> failed."
>
> I need everything from the
On 11/10/20 6:47 PM, Stan Johnson wrote:
> $ fgrep -i grub syslog
> Nov 10 09:29:25 anna[2818]: DEBUG: retrieving grub-installer 1.173+mac
> Nov 10 09:29:28 anna[2818]: DEBUG: retrieving grub-mount-udeb 2.04-10
> Nov 10 16:46:35 in-target: linux-doc-5.9 debian-kernel-handbook mkvmlinuz
>
On 11/9/20 11:45 PM, John Paul Adrian Glaubitz wrote:
On 11/10/20 4:51 AM, Stan Johnson wrote:
Thanks for creating the 9 Nov 2020 CD. I was able to use that CD to
install Debian SID on a PPC Cube (G4) from an external Firewire CD
drive. ...
The
On 11/10/20 5:11 PM, John Paul Adrian Glaubitz wrote:
> On 11/10/20 4:59 PM, Jeroen Diederen wrote:
>> If I go to a console, I can see that the disk has five partitions (with
>> parted).
>> The strange thing is that if I issue a
>> fdisk -l
>> I do not see the partitions.
>
> Regular fdisk
On 11/10/20 4:59 PM, Jeroen Diederen wrote:
> If I go to a console, I can see that the disk has five partitions (with
> parted).
> The strange thing is that if I issue a
> fdisk -l
> I do not see the partitions.
Regular fdisk doesn't support Mac partitions as far as I know.
That's by
If I go to a console, I can see that the disk has five partitions (with
parted).
The strange thing is that if I issue a
fdisk -l
I do not see the partitions.
I also see an error message in tty4 saying:
partman: no matching physical volumes found
Jeroen
On Nov 10, 2020, at 3:57 PM, John Paul
On 11/10/20 12:05 PM, John Paul Adrian Glaubitz wrote:
> On 11/10/20 11:54 AM, Jeroen Diederen wrote:
>> I see another image, produced on the 10th of November (today).
>> Do we need to test that one as well ?
>
> I already tested it. Same problem.
FWIW, I tested sparc64 and it works there. So
On 11/10/20 11:54 AM, Jeroen Diederen wrote:
> I see another image, produced on the 10th of November (today).
> Do we need to test that one as well ?
I already tested it. Same problem.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie
Adrian,
I see another image, produced on the 10th of November (today). Do we
need to test that one as well ?
Jeroen
John Paul Adrian Glaubitz schreef op 2020-11-10 11:17:
On 11/10/20 11:00 AM, Jeroen Diederen wrote:
I tried the powerpc image produced on the 9th of November. I
experience
On 11/10/20 11:00 AM, Jeroen Diederen wrote:
> I tried the powerpc image produced on the 9th of November. I experience the
> same problem as Adrian: the partitioning tool is hanging. It says that it is
> scanning disks and stays at 47%. If I look in tty4 I see that it detected 5
> partitions on
Hi!
I tried the powerpc image produced on the 9th of November. I experience the
same problem as Adrian: the partitioning tool is hanging. It says that it is
scanning disks and stays at 47%. If I look in tty4 I see that it detected 5
partitions on sda: [mac] sda1 sda2 sda3 sda4 sda5. I cannot
On 11/10/20 4:51 AM, Stan Johnson wrote:
> Thanks for creating the 9 Nov 2020 CD. I was able to use that CD to
> install Debian SID on a PPC Cube (G4) from an external Firewire CD
> drive. Previous CDs had failed while detecting hardware to find the
> installation media, and I had thought there
On 11/9/20 7:55 PM, John Paul Adrian Glaubitz wrote:
>> Found the problem. isofs-modules is no longer pulled in automatically and
>> this
>> fix [1] forgot powerpc :-).
>
> Fixed:
>
>> https://salsa.debian.org/installer-team/debian-installer/-/commit/d82eedd0577361610cb453533ae8cbf40e395e37
>>
On 11/9/20 7:37 PM, John Paul Adrian Glaubitz wrote:
> On 11/9/20 7:30 PM, John Paul Adrian Glaubitz wrote:
>> I gave it a try and indeed the installation media is not being mounted.
>>
>> The problem is that the isofs module is missing. Have to figure out why.
>>
>> Most likely a change to kernel
On 11/9/20 7:30 PM, John Paul Adrian Glaubitz wrote:
> I gave it a try and indeed the installation media is not being mounted.
>
> The problem is that the isofs module is missing. Have to figure out why.
>
> Most likely a change to kernel packaging.
Found the problem. isofs-modules is no longer
Hello!
On 11/8/20 5:04 PM, John Paul Adrian Glaubitz wrote:
> On 11/8/20 4:59 PM, Jeroen Diederen wrote:
>> To come back to my incorrect sha256sum, I downloaded the iso yesterday. It
>> was the
>> image created on 7.11.2020. I checked against the shasums of the 'current'
>> iso,
>> thinking
Hi,
if nothing else helps:
What happens if you destroy the Apple Partition Map of the ISO before you
burn it to the CD.
cp debian-10.0.0-powerpc-NETINST-1.iso test.iso
dd if=/dev/zero conv=notrunc bs=2048 count=16 of=test.iso
... burn test.iso with SAO ...
This won't boot. But maybe it
Hi,
> Can you guys try it please? I am lost here.
On amd64 Debian:
# mount debian-10.0.0-powerpc-NETINST-1.iso.1 /mnt/iso
mount: /dev/loop0 is write-protected, mounting read-only
$ tar cf - /mnt/iso | dd bs=2K of=/dev/null
tar: Removing leading `/' from member names
158930+0 records
Hi!
On 11/8/20 4:59 PM, Jeroen Diederen wrote:
> To come back to my incorrect sha256sum, I downloaded the iso yesterday. It
> was the
> image created on 7.11.2020. I checked against the shasums of the 'current'
> iso,
> thinking that the one of yesterday was the 'current' one. I did not know
Hi,
Jeroen Diederen wrote:
> If I boot and try to mount the CDROM it fails again to mount the CDROM
> but I don't see the kernel messages as before.
> [...]
> I tried several ways of burning this image now, always failing to be
> mounted. I also tried an iBook G4, with the same result.
This
To come back to my incorrect sha256sum, I downloaded the iso yesterday. It was
the image created on 7.11.2020. I checked against the shasums of the 'current'
iso, thinking that the one of yesterday was the 'current' one. I did not know
that there is a newly spinned iso, from the 8th of November
Hi!
I tried again, checksummed the iso, all correct. I burnt the iso on the usual
G5 iMac, also on a newer MacBook Pro.
I tried the CD-R's in my PowerBook G5 as well as in my iBook G4. Nothing works.
I always get the same error that it cannot mount the CDROM.
Can you guys try it please? I am
Hi,
i wrote:
> > [PATCH 0/3] Fix the old CD read-ahead bug for media with a single TAO
> > track
John Paul Adrian Glaubitz wrote:
> I would definitely support that effort. [...]
> So feel free to post your patches to the corresponding LKML and put me in
> CC,
Will do. Let's wait
Hi all,
I burn the iso again as Thomas suggested with this command:
> xorriso -as cdrecord \
> -v dev=/dev/sr0 blank=as_needed -eject padsize=300k \
> -sao debian-10.0.0-powerpc-NETINST-1.iso
If I boot and try to mount the CDROM it fails again to mount the CDROM
Hi Thomas!
On 11/8/20 3:10 PM, Thomas Schmitt wrote:
> If this all turns out to be really the old readahed bug, does anybody here
> have enough reputation in linux-scsi to get a fix committed, which i have
> ready as set of
> [PATCH 0/3] Fix the old CD read-ahead bug for media with a single TAO
Hi,
Jeroen Diederen wrote:
> kernel: [timestamp] sr 1:0:0:0: [sr0] tag#0 Sense Key : Illegal Request
> kernel: [timestamp] sr 1:0:0:0: [sr0] tag#0 Add. Sense: Illegal mode for
> this track
> ...
> kernel: [timestamp] attempt to access beyond end device
> kernel: [timestamp] sr0: rw=0, want
On 11/8/20 2:26 PM, Jeroen Diederen wrote:
> I don't agree Adrian. The same PowerBook does not have these problems with
> the 19.04.2020 image you created. The CDROM gets mounted each time and I
> can install Debian without problems, except now of course because of hfsprogs.
Are you using an
I don't agree Adrian. The same PowerBook does not have these problems with the
19.04.2020 image you created. The CDROM gets mounted each time and I can
install Debian without problems, except now of course because of hfsprogs.
On Sun, 8 Nov 2020 13:46:31 +0100
John Paul Adrian Glaubitz wrote:
On 11/8/20 1:42 PM, Jeroen Diederen wrote:
> kernel: [timestamp] sr 1:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_OK
> driverbyte=DRIVER_SENSE cmd_age=0s
> kernel: [timestamp] sr 1:0:0:0: [sr0] tag#0 Sense Key : Illegal Request
> [current]
> kernel: [timestamp] sr 1:0:0:0: [sr0] tag#0 Add.
kernel: [timestamp] sr 1:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE cmd_age=0s
kernel: [timestamp] sr 1:0:0:0: [sr0] tag#0 Sense Key : Illegal Request
[current]
kernel: [timestamp] sr 1:0:0:0: [sr0] tag#0 Add. Sense: Illegal mode for this
track
kernel: [timestamp]
With this image I cannot get my cdrom mounted, I tried manual mounting as well
with the cdrom module, which worked with older images, not with this one
unfortunately.
Any idea ?
Jeroen
On Sat, 7 Nov 2020 16:44:53 +0100
John Paul Adrian Glaubitz wrote:
> Hello!
>
> On 11/7/20 10:08 AM, John
On 11/7/20 8:17 PM, Jeroen Diederen wrote:
> With this image I cannot get my cdrom mounted, I tried manual mounting as
> well with the cdrom module, which worked with older images, not with this
> one unfortunately.
As always, I need the installer log file otherwise I have no means to know
what's
Hello!
On 11/7/20 10:08 AM, John Paul Adrian Glaubitz wrote:
> On 11/7/20 10:04 AM, Jeroen Diederen wrote:
>> I don't need to do manual testing ?
>
> No. And I already know how to fix this issue.
Please try today's image and report back whether it works [1].
Adrian
> [1]
>
On 11/7/20 10:04 AM, Jeroen Diederen wrote:
> I don't need to do manual testing ?
No. And I already know how to fix this issue.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`-
I don't need to do manual testing ?
On 11/7/20 9:56 AM, John Paul Adrian Glaubitz wrote:
On 11/7/20 9:51 AM, John Paul Adrian Glaubitz wrote:
Can you try to invoke the command manually, please and tell me what the error
message is?
Well, ok, the problem is apparently that the tool no longer
On 11/7/20 9:51 AM, John Paul Adrian Glaubitz wrote:
> Can you try to invoke the command manually, please and tell me what the error
> message is?
Well, ok, the problem is apparently that the tool no longer support HFS Legacy.
>From the manpage:
> HISTORY
>The newfs_hfs command appeared in
Hello Jeroen!
On 11/7/20 9:46 AM, Jeroen Diederen wrote:
> I just tried to install Debian on a PowerBook G4. I had the partitioning
> done automatically. At the end, the installation of grub failed. The problem
> resides in hfsprogs. The error message I get is the following:
>
> ...setting up
Hi,
I just tried to install Debian on a PowerBook G4. I had the partitioning
done automatically. At the end, the installation of grub failed. The
problem resides in hfsprogs. The error message I get is the following:
...setting up hfsprogs (540.1.linux3-1) ...
mk-hfs-bootstrap: 'mkfs.hfs -h
Hi Samuel!
I'm working on adopting hfsprogs now and I will also pick the patch from
Fedora to resolve this issue, see [1].
A new version of hfsprogs should be uploaded within the next days.
Adrian
> [1]
>
53 matches
Mail list logo
