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 in 158930+0 records out 325488640 bytes (325 MB) copied, 0.172302 s, 1.9 GB/s $ No error messages to see in the system log which would stem from mount or the read functions of isofs. > PowerBook G5 as well as in my iBook G4 At boot time i would expect peculiarities. But when Linux is up, it should be a only matter of the ISO's content and the drives' compliance to SCSI specs. (We are lucky since 20 years that no specs violations prevail.) Does the system log tell any new info about the refusal to mount. > I did not know that there is a newly spinned iso, from the 8th of > November in the meantime. So my example with dd bs=2048 count=160103 if=/dev/sr0 | sha512sum might need a count number other than 160103. Compute it freshly from the new ISO's file size. Have a nice day :) Thomas