AmigaOS 3.2.2 Loadmodule problem

[Amigaz]

Hardware: CD32 with TF360 (68060) accelerator and kickrom 3.2. 32GB CF card hooked up to TF360 IDE and pfs2aio as FS
OS: AmigaOs 3.2

I have installed AmigaOS 3.2 and after that the general CPU libraries from the 3.2 install floppy, system boots fine with this setup

When I update to AmigaOS 3.2.2 I get LoadModule failed returncode 10 when booting



I have noticed that the startup-sequence gets some stuff added when updating from 3.2 -> 3.2.2 that must be the root cause but I cannot understand the logic and would appreciate if I could get some help with what I should change, add or edit to successfully get my system up and running

3.2 startup-sequence



3.2.2 startup-sequence, here the extra stuff added with the LoadModule commands must be the culprit. But what exactly?

[Boing-ball]

Hardware: CD32 with TF360 (68060) accelerator and kickrom 3.2. 32GB CF card hooked up to TF360 IDE and pfs2aio as FS
OS: AmigaOs 3.2

I have installed AmigaOS 3.2 and after that the general CPU libraries from the 3.2 install floppy, system boots fine with this setup

When I update to AmigaOS 3.2.2 I get LoadModule failed returncode 10 when booting



I have noticed that the startup-sequence gets some stuff added when updating from 3.2 -> 3.2.2 that must be the root cause but I cannot understand the logic and would appreciate if I could get some help with what I should change, add or edit to successfully get my system up and running

3.2 startup-sequence



3.2.2 startup-sequence, here the extra stuff added with the LoadModule commands must be the culprit. But what exactly?

You need to debug the output.

Where you have Version……. >NIL:

Remove the >NIL: at the end of those lines. That way when you bootup you will see what’s happening.

Once you know and have it working. Put the >NIL: back at the end of those lines.

[kolla]

Try if adding “ALLTOCHIP” after “ROMUPDATE” makes any difference.

[Amigaz]

Try if adding “ALLTOCHIP” after “ROMUPDATE” makes any difference.

I will try that and get back with the results

[Amigaz]

Tried booting with the trace option from the early startup menu, seems like files are missing (??) Shouldn't they exist after I have installed AmigaOS 3.2?

[Amigaz]

Try if adding “ALLTOCHIP” after “ROMUPDATE” makes any difference.

It made no difference

[Boing-ball]

Tried booting with the trace option from the early startup menu, seems like files are missing (??) Shouldn't they exist after I have installed AmigaOS 3.2?

This is on a CD32. I know when I’ve done upgrades on A1200 and A4000 machines, these worked without issue. Maybe a bug on Hyperions installation for the CD32?

I have a feeling the missing files will be on the Modules disk. Hopefully there is a CD32 modules adf you can mount and copy these files over.

[Amigaz]

Problem solved. I actually got a working disk image with AmigaOS 3.2.2.1 from a kind gentleman. He had ran it successfully in his CD32/TF360 machine. It had all the missing files in L and Libs. These files are on the AmigaOS 3.2 modules floppy so you can copy them over if you are missing them like I did.

[F0LLETT]

I had this exact same problems.

I just copied all the missing stuff to the drive and added modules that were missing, like updated kenel and scsi device.

[Amigaz]

I had this exact same problems.

I just copied all the missing stuff to the drive and added modules that were missing, like updated kenel and scsi device.

ah, weird

Buggy installers or stuff "you should know about and copy the files youself to relevant locations"? 

[F0LLETT]

ah, weird

Buggy installers or stuff "you should know about and copy the files youself to relevant locations"? 

I only fixed the issue you had, then noticed it wasnt seeing my 64GB Games partition. Thats when I noticed it was missing half the rom updates.
As soon as I added those to the LoadModule command it all started working as I expected it too.

[Boing-ball]

ah, weird

Buggy installers or stuff "you should know about and copy the files youself to relevant locations"? 

I think I have read somewhere that the CD32 version of AmigaOS3.2 does not have proper support due to its nature.

You will need to discuss this with Hyperion on that….

[kolla]

Right person to discuss this with is ThoR who no longer works on OS. The installer should detect what hardware it is being installed on and ask for modules disk accordingly, the detection of hardware use same code as LoadModule. Of course this only works if you actually perform the installation on a CD32 and not UAE with A1200-like settings. Only a few modules are system dependent and the way LoadModule works, you can have them all installed on same boot media… I don’t grasp why they didn’t opt for just doing that as default.

[F0LLETT]

Right person to discuss this with is ThoR who no longer works on OS. The installer should detect what hardware it is being installed on and ask for modules disk accordingly, the detection of hardware use same code as LoadModule. Of course this only works if you actually perform the installation on a CD32 and not UAE with A1200-like settings. Only a few modules are system dependent and the way LoadModule works, you can have them all installed on same boot media… I don’t grasp why they didn’t opt for just doing that as default.

CD32 is not officially supported. They call it an experiment. So not sure who actually tested it, or if it was tested at all.

[kolla]

CD32 is not officially supported. They call it an experiment. So not sure who actually tested it, or if it was tested at all.

I'm just pointing out that discussing anything with _Hyperion_ is quite pointless.

In the OS team, the right person is probably Olsen at this point.

But the person who's doing the whole System-Startup, kickstart modules, LoadModule dance... is (or was) Thomas Richter.