Diagnosing Early Boot Problems

Boot progresses to the ArcaOS logo and stops.

1. Select a verbose boot option and disable the ArcaOS logo.
   • When booting the ArcaOS installer, select “Boot with menu for own values”, and then select “Verbose boot” from the last page of the pre-boot menus. This both disables the logo and enables driver reporting.
   • For installed systems using the Traditional boot environment (including UEFI with CSM), you can type Alt-F2 at the boot blob. For these types of systems you may also need to rename or delete the OS2LOGO file from the root of the boot volume.
   • For installed systems using the UEFI without CSM boot environment, type Alt-F1 at the boot blob and then choose “Display device drivers”.
2. Make a note of the last driver or message displayed on the screen. The boot problem is occurring at or before this message or the loading of this driver. This does *not* indicate a problem with the last driver that is displayed. This only tells you *when* the boot stopped, not why it stops or what is causing the problem. Analyze all the steps prior to the last message for any anomalies.
3. If no anomalies are found, an experienced developer will need to analyze the system.

Boot progresses to the IBM OS/2 banner and stops.

1. Make sure the system date is set correctly. Use the system’s BIOS settings to verify and set the correct date.
2. If using a test build of ACPI.PSD, make sure it is not expired. Test builds work for 30 days from the build date as specified by the bldlevel command.
3. Try to capture the PSD diagnostic log file.
   • The best way to capture the PSD diagnostic log file that works for any boot environment is to use a serial port. See Collecting Logs -> Collecting a Serial Port Log in the ACPI wiki.
   • Alternatively, for systems booting in a Traditional environment (including UEFI with CSM), you can try to capture a PSD video log. See Collecting Logs -> Collecting a Video Log in the ACPI wiki.
   • For systems using the UEFi without CSM environment, a Video Log will not work. In this environment, press Alt-F1 at the boot blob, or if booting the installer, immediately when you see the first menu. Then choose “Diagnostics…” and “Write log file”. You will need a FAT or FAT32 formatted volume for writing the log to. This can be almost any volume on the system including a USB stick.  An ArcaOS install USB stick will work for this.
4. An experienced developer is required to analyze the log or to debug this further. Provide any logs or other information you may have captured.

The system gets an Internal Processing Error 60004, 6009

This normally indicates a hardware error, although there can be other causes. See the ACPI wiki for more information.