Issue updating from CD on PM 2.3 with 1950.
  • Order of the Butterfly
    Order of the Butterfly
    matt3
    Posts: 405 from 2004/2/10
    I had an issue upgrading from 3.15 to 3.16 on my PM G5 2.3 with a X1950.

    I boot from CD (Pressing C on keyboard) like I normally do and receive the following message:

    MorphOS 3.16 install media was found yet, the system booted with MorphOS kernal 3.15.

    It suggests I use the Alt key, but I can't since I use the 1950.

    Any suggestions?
  • »09.03.22 - 22:11
    Profile
  • MorphOS Developer
    geit
    Posts: 979 from 2004/9/23
    Well, booting using the hybrid MorphOS image written to an USB stick, may overcome your boot problems. It should boot without any key press straight into the iso.

    Ok, this only works without any other bootable device.

    You can also replace the boot.img on your boot partition with the correct (!!!) boot image from the 3.16 CD.

    The issue is that MorphOS 3.15 will boot with the new boot image, but the old boot image wont boot any newer iso.

    So in your case the mac_ppc64/boot.img file. Any other boot image will render your system non bootable.



    [ Edited by geit 10.03.2022 - 00:09 ]
  • »09.03.22 - 23:02
    Profile
  • MorphOS Developer
    jacadcaps
    Posts: 2650 from 2003/3/5
    From: Canada
    You won't be able to boot from CD on a Mac without an OpenFirmware-compatible graphics card. This is a limitation of the OpenFirmware itself (neither Alt key nor C do anything without a graphics card that OF knows how to handle).

    You could try to copy the boot.img and modify the bootinfo.txt to force it to boot an update image, but I would advise against this. Any mistake will render your system unbootable.

    Your best course of action is to put an NVidia card in alongside the Radeon and use it to enter the OpenFirmware, then boot via USB.
  • »09.03.22 - 23:10
    Profile Visit Website
  • Paladin of the Pegasos
    Paladin of the Pegasos
    Papiosaur
    Posts: 1578 from 2003/4/10
    From: France
    Same problem here... (Quad+X1950Pro) i have pressed "c" key and same message. MorphOS boot from CD but read bad boot.img from boot: partition. Alt key don't work because the graphic card is not compatible with the openfirmware. I have copied good boot.img image file to boot: partition and now is ok.

    [ Edité par Papiosaur 10.03.2022 - 09:28 ]
  • »10.03.22 - 08:19
    Profile Visit Website
  • Order of the Butterfly
    Order of the Butterfly
    BatteMan
    Posts: 265 from 2003/2/24
    From: France
    Same here (dual G5 2,7 Ghz).

    Replaced the boot.img in my Boot: partition with the boot.img from 3.16 ISO and it worked.

    Not the best method for sure but, without graphic card compatible with OF, it's maybe the only one.
    Proud user of MorphOS since 2003 !
  • »10.03.22 - 09:09
    Profile Visit Website
  • Order of the Butterfly
    Order of the Butterfly
    amyren
    Posts: 219 from 2010/5/15
    From: Norway
    Could one use this method to update from 3.15 to 3.16 without having to use a CD or USB?

    like this for my macmini:
    1. Extract the iso file into a folder somewhere.
    2. Use Mounter to mount the Boot partion.
    3. Copy mac_ppc32/boot.img into Boot:
    4. Bless the boot.img file using 'HFSSetMacBoot Boot:boot.img' (*1)
    5. Reboot
    6. Run the update setup from the extracted iso folder


    *1 : This part I find a bit confusing.
    Reading the boot.txt it says you need to bless the boot.img file.
    Further down it also says its important to bless the bootinfo.txt file if it have been edited.
    But the information also say "It is only possible to bless one file per partition."
    Now, in my case I should only need to bless the boot.img file, since I have not touched the bootinfo.txt file.
  • »10.03.22 - 13:13
    Profile
  • MorphOS Developer
    jacadcaps
    Posts: 2650 from 2003/3/5
    From: Canada
    @amyren

    Several incorrect assumptions there. You should never bless the boot.img file for starters. Copying a boot.img may make your system un-bootable, too.

    @All

    If you have no other graphics card for the Mac, I can only recommend buying one or moving the HDD to a different MorphOS machine to update there - the only thing you'll need to do afterwards is copying the right boot.img to the target disk.
  • »10.03.22 - 13:35
    Profile Visit Website
  • jPV
  • Paladin of the Pegasos
    Paladin of the Pegasos
    jPV
    Posts: 1884 from 2003/2/24
    From: po-RNO
    Quote:

    amyren wrote:
    1. Extract the iso file into a folder somewhere.

    You could just mount the ISO (rmb over ISO and "Mount..."). "Extracting" files into folder sounds like overkill and there's always chance to mess something in files (dates, protection bits..) and your drive just gets fragmented ;) By using the mounted ISO you keep everything in the original state.
  • »10.03.22 - 17:14
    Profile Visit Website
  • Order of the Butterfly
    Order of the Butterfly
    amyren
    Posts: 219 from 2010/5/15
    From: Norway
    Quote:

    jacadcaps wrote:
    @amyren

    Several incorrect assumptions there. You should never bless the boot.img file for starters. Copying a boot.img may make your system un-bootable, too.



    It was not my assumption, it is clearly written in the boot.txt file found inside the 3.16 iso, in first sentence in the Manual section.

    Code:
    MorphOS booting instructions for PowerPC Apple hardware

    Automatic:

    IWizard automatically creates a HFS Boot partition when installing MorphOS
    and places the boot.img and a bootinfo.txt boot script file on it. In case
    the harddrive is partitioned manually, the installation process will fail
    if a Boot HFS partition isn't found. By default MorphOS will boot using the
    settings from the bootinfo.txt file.

    Manual:

    In order to boot MorphOS on a supported PowerPC Apple machine you need to
    place the boot.img file on a HFS formatted partition called Boot. Each
    time the file is updated, it will have to be blessed with the HFSSetMacBoot
    command. This tells the OpenFirmware which file to load when booting.

    It is only possible to bless one file per partition. OpenFirmware can only
    read HFS or HFS+ formatted partitions of the internal harddrive.

    IMPORTANT:
    OpenFirmware may sometimes be unable to read the boot.img if it's the
    only file on the partition, therefore it is best not to remove this file.

    IMPORTANT:
    You have to bless the bootinfo.txt file after editing it to make it
    bootable again!
  • »10.03.22 - 17:42
    Profile
  • Order of the Butterfly
    Order of the Butterfly
    amyren
    Posts: 219 from 2010/5/15
    From: Norway
    Quote:

    jPV wrote:
    Quote:

    amyren wrote:
    1. Extract the iso file into a folder somewhere.

    You could just mount the ISO (rmb over ISO and "Mount..."). "Extracting" files into folder sounds like overkill and there's always chance to mess something in files (dates, protection bits..) and your drive just gets fragmented ;) By using the mounted ISO you keep everything in the original state.



    Unfortunately if I try to mount it from RMB, it fails.
    The output window says it cant find the command
    MOSSYS:Ambient/scripts/mountisoimage
    This might be due to some leftovers from a Chrysalis pack I installed long time ago. But I dont know how to fix these menu entries.
    What is the correct syntax to mount the iso file from shell?
  • »10.03.22 - 18:13
    Profile
  • MorphOS Developer
    zukow
    Posts: 620 from 2005/2/9
    From: Poland
    set +s protection bit for this script
  • »10.03.22 - 21:10
    Profile Visit Website
  • jPV
  • Paladin of the Pegasos
    Paladin of the Pegasos
    jPV
    Posts: 1884 from 2003/2/24
    From: po-RNO
    Quote:

    amyren wrote:
    Quote:

    jPV wrote:
    Quote:

    amyren wrote:
    1. Extract the iso file into a folder somewhere.

    You could just mount the ISO (rmb over ISO and "Mount..."). "Extracting" files into folder sounds like overkill and there's always chance to mess something in files (dates, protection bits..) and your drive just gets fragmented ;) By using the mounted ISO you keep everything in the original state.



    Unfortunately if I try to mount it from RMB, it fails.
    The output window says it cant find the command
    MOSSYS:Ambient/scripts/mountisoimage
    This might be due to some leftovers from a Chrysalis pack I installed long time ago. But I dont know how to fix these menu entries.
    What is the correct syntax to mount the iso file from shell?

    When looking at Ambient MIME types for x-iso-9660:
    MOSSYS:S/MountISO %sp OPENVIEW

    So, replace %sp with the image name.

    This is how it is on the standard MorphOS installation... and I don't think that I've never touched it myself either. Haven't had Chrysalis installed, I wonder if it has modified MOSSYS: contents at some point or what's the case...

    EDIT: checked MorphOS 2.0 ISO, and there indeed is the MOSSYS:Ambient/scripts/mountisoimage file :D So, it has changed during the years and if you had saved the filetype with some own settings it probably haven't got updated in MorphOS upgrades. It could also be possible that I have fixed it on my setup at some point but have forgotten it...

    [ Edited by jPV 10.03.2022 - 23:41 ]
  • »10.03.22 - 21:17
    Profile Visit Website
  • Order of the Butterfly
    Order of the Butterfly
    amyren
    Posts: 219 from 2010/5/15
    From: Norway
    Quote:

    zukow wrote:
    set +s protection bit for this script


    I forgot to write, the problem is that the script file is missing.
  • »10.03.22 - 22:12
    Profile
  • jPV
  • Paladin of the Pegasos
    Paladin of the Pegasos
    jPV
    Posts: 1884 from 2003/2/24
    From: po-RNO
    I think the situation is like this now:

    1) MorphOS originally had the mounting script in MOSSYS:Ambient/scripts/mountisoimage
    2) If you (or Chrysalis pack) had saved any modifications to the x-iso-9660 mimetype, mountisoimage was left as a user setting which overrides the default settings and kept it pointing to the original script location.
    3) At some point the default mounting script in MorphOS was replaced by MOSSYS:S/MountISO and mountisoimage was removed.
    4) Your custom x-iso-9660 mimetype kept pointing to the removed file.
    5) If you want to revert the whole mimetype to the official defaults to fix the issue, remove the SYS:Prefs/Ambient/filetypes/application/x-iso-9660 file. And of course you could also edit the current mimetype to execute the MountISO line told in the previous post if you want to keep other changes in it.

    This has been a small overlook by the team at that point and should probably have been handled in some other way...


    [ Edited by jPV 11.03.2022 - 08:19 ]
  • »11.03.22 - 05:48
    Profile Visit Website
  • Order of the Butterfly
    Order of the Butterfly
    amyren
    Posts: 219 from 2010/5/15
    From: Norway
    Quote:

    jPV wrote:
    I think the situation is like this now:


    That sounds like a plausible cause. Anyway, I have temporarly resolved it by downloading MorphOS iso v2.4 and got the missing script file from there.

    I copied the boot.img from the iso, and at reboot it shows 3.16 in the boot picture.
    Then mounted the iso.
    The install did not work at first, but the shell command
    'assign sys: MorphOSBoot:' resolved this and the update went without errors.

    Thanks for the help:)
  • »11.03.22 - 16:33
    Profile