Integrity check doesn't work...sometimes?

Btw, ./md5sum.txt on the image has

  b60e1e09e13135b8537380ebb1882f60 /dists/edgy/restricted/binary-powerpc/Release

Sorry for my last comment, that was for restricted.

grep /dists/edgy/main/binary-powerpc/Release /cdrom/md5sum.txt
76da0c7fb89cfae9595a369f927bb1dd ./dists/edgy/main/binary-powerpc/Release

so this is right; the bug seems to be elsewhere then.

md5sum.txt on the image is correct:

$ isoinfo -R -i edgy-alternate-powerpc.iso -x /dists/edgy/restricted/binary-powerpc/Release | md5sum
b60e1e09e13135b8537380ebb1882f60 -
$ isoinfo -R -i edgy-alternate-powerpc.iso -x /md5sum.txt | grep /dists/edgy/restricted/binary-powerpc/Release
b60e1e09e13135b8537380ebb1882f60 ./dists/edgy/restricted/binary-powerpc/Release

Could you please extract anything relevant from /var/log/syslog in the installer after it complains?

Will do syslog in a minute. So far, just for the record:

$ grep /dists/edgy/main/binary-powerpc/Release md5sum.txt | md5sum -c
./dists/edgy/main/binary-powerpc/Release: Ok

I'm afraid there isn't terribly much to learn from /var/log/syslog. The screenshot shows the last couple of lines (before there are only kernel boot messages). It's the only non-empty file in /var/log, and /var/log/installer does not exist.

Works fine on amd64.

I have some serious trouble to copy a file to anywhere at this stage; trying to mount my USB stick or hard disk just fails with 'no such device' or 'invalid argument' and there are no ethernet modules available either (for netcat'ing). I'm inclined to say that DEBCONF_DEBUG=5 does not show anything helpful, but I did a screenshot of the relevant section nevertheless.

Now failed on amd64 20060915.1, too (same error, except s/powerpc/amd64/)

Adding milestone: This does not seem to be limited to one platform, and since it's prominently advertised at the boot screen and we often suggest people to check the CD when they report bugs, this should really work.

You said both that amd64 failed and that amd64 worked. Were these different ISOs, different hardware, ...?

Different ISO versions, yes. 20060912.1/amd64 worked, 20060915.1 failed.

seen with 20060927.7 i386 as well.

The check works perfectly for me in vmware

Fails with the current server CD for me too (amd64 in vmware)

Could you please give Edgy Beta a shot? Thanks.

Andrew, we did test the edgy beta (I installed it about 20 times :) ), still the same problem.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Mon, 9 Oct 2006 11:51:56 +0200
Source: cdrom-checker
Binary: cdrom-checker
Architecture: source
Version: 1.06ubuntu2
Distribution: edgy
Urgency: low
Maintainer: Debian Install System Team <email address hidden>
Changed-By: Tollef Fog Heen <email address hidden>
Description:
 cdrom-checker - Verify the cd contents
Changes:
 cdrom-checker (1.06ubuntu2) edgy; urgency=low
 .
   * Strip the \n from end of lines before passing this to md5sum. This
     makes md5sum checking actually work again. Launchpad: Bug: #60188
Files:
 3c3b40cc57270812f95c79b1e65e8ac9 800 debian-installer optional cdrom-checker_1.06ubuntu2.dsc
 c851de574c5ce1691029867f98009b0d 52931 debian-installer optional cdrom-checker_1.06ubuntu2.tar.gz
Package-Type: udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iQCVAwUBRSoclscmO3YsB1PjAQKN+AQA6RbuD74cmeojeVpvMvva0HynVQt4wCG9
it7tXA+zZELknJ9Hbysc3JG+lnlRngYtJHUodlIxX6BEQEiyEy0FsfWfUmMO477D
y5Y9fpuKZTwE/x40fDz7oEfk/J++llvS+3WSwPtFUqbQFIPpYGuQUeAyuCN3Uqhz
kE3au3y3A4U=
=+wzW
-----END PGP SIGNATURE-----