Home Page The Club Computers News Links Glossary EYAWTK
Before Amiga Background ICS OCS ECS AGA ??? PPC
U-Boot SLB Linux Amiga OS Dual Boot Motherboards Peripherals Other
Initialisation Installation OS4 Updates About OS4 File Systems Networking Printing Other

AmigaOS 4.0 - Initialisation Displays

AmigaOS 4.0 Initialisation
When AmigaOS 4.0 is started, display diagnostic information is output which can be captured via the serial port, and there is also the opportunity to interrupt the early startup process from the keyboard or mouse.

AmigaOS 4.0 Initialisation using onboard VIA686B under Update 4

Booting configuration Default

a1ide.device 51.49 (21.11.2005)
[dev_init] Running on AmigaOne
[dev_init] Found chip #0
[init_port] ---> Port 0
[init_port] Config not forced, scanning ...
[ide_list] IDE port 0 :
[ide_list] Master : 'ATA'
[ide_list] Slave : 'unknown type'
[init_port] ---> Port 1
[init_port] Config not forced, scanning ...
[ide_list] IDE port 1 :
[ide_list] Master : 'no device'
[ide_list] Slave : 'no device'
[init_unit] Trying to configure unit 0
[ata_read_drive_properties] Unit 0 is LBA48-capable but has LBA28 size
[ata_read_drive_properties] MultiCount 16
[ata_read_drive_properties] Adjusting unit 0 to xfer mode 12
[init_unit] Unit successfully configured, flags $0185
[init_unit] Trying to configure unit 1
[init_unit] Trying to configure unit 2
[init_unit] Trying to configure unit 3

sii0680ide.device 51.49 (12.11.2005)
[dev_init] Running on AmigaOne
[dev_init] Nothing started, bailing out

sii3112ide.device 51.49 (12.11.2005)
[dev_init] Running on AmigaOne
[dev_init] Nothing started, bailing out

sii3114ide.device 51.49 (12.11.2005)
[dev_init] Running on AmigaOne
[dev_init] Nothing started, bailing out

sii3512ide.device 51.49 (12.11.2005)
[dev_init] Running on AmigaOne
[dev_init] Nothing started, bailing out

The exact content that is captured will depend on your machine, the components connected to it, and the values stored in some of the environment variables. Because of this, the checks may appear quite different and produce different results. If you have any hardware issues that cause AmigaOS 4.0 to fail during initialisation, this is a useful place to look.

Please note that significant changes were made between Update 3 and Update 4. Typically output from Update 3 is available here for comparison purposes.

AmigaOS 4.0 Initialisation using add-on SiI0680 under Update 4

Booting configuration Default

a1ide.device 51.49 (21.11.2005)
[dev_init] Running on AmigaOne
[dev_init] Found chip #0
[init_port] ---> Port 0
[init_port] Config not forced, scanning ...
[init_port] 0 device(s) on port
[init_port] ---> Port 1
[init_port] Config not forced, scanning ...
[init_port] 0 device(s) on p
[dev_init] Nothing started, bailing out

sii0680ide.device 51.49 (21.11.2005)
[dev_init] sii0680ide_timeout : '20', adjusted ata timeout to 20
[dev_init] Config forced in $sii0680ide_conf : 1122
[dev_init] Xfer modes forced in $sii0680ide_xfer : F0CC
[dev_init] Running on AmigaOne
[dev_init] Found chip #0
[init_port] ---> Port 0
[init_port] Config forced, no scan
[init_port] 2 device(s) on port
[port_list] 0 Master : 'ATA'
[port_list] 1 Slave : 'ATA'
[init_port] Starting 'sii0680ide.device - chip 0 port 0' task
[int_install_handler] Installing handler for irq 25
[init_unit] Trying to configure unit 0
[ata_read_drive_properties] Unit 0 is LBA48-capable but has LBA28 size

[ata_read_drive_properties] multi_count 16
[ata_read_drive_properties] Adjusting unit 0 to xfer mode 69
[init_unit] Unit configured, flags $0185
[init_unit] Trying to configure unit 1
[init_port] ---> Port 1
[init_port] Config forced, no scan
[init_port] 2 device(s) on port
[port_list] 0 Master : 'ATAPI'
[port_list] 1 Slave : 'ATAPI'
[init_port] Starting 'sii0680ide.device - chip 0 port 1' task
[init_unit] Trying to configure unit 2
[ata_read_drive_properties] Adjusting unit 2 to xfer mode 66
[init_unit] Unit configured, flags $011D
[init_unit] Trying to configure unit 3
[ata_read_drive_properties] Adjusting unit 3 to xfer mode 66
[init_unit] Unit configured, flags $011D
[dev_init] All done

sii3112ide.device 51.49 (21.11.2005)
[dev_init] Running on AmigaOne
[dev_init] Nothing started, bailing out

sii3114ide.device 51.49 (21.11.2005)
[dev_init] Running on AmigaOne
[dev_init] Nothing started, bailing out

sii3512ide.device 51.49 (21.11.2005)
[dev_init] Running on AmigaOne
[dev_init] Nothing started, bailing out

The exact content that is captured will depend on your machine, the components connected to it, and the values stored in some of the environment variables. Because of this, the checks may appear quite different and produce different results. If you have any hardware issues that cause AmigaOS 4.0 to fail during initialisation, this is a useful place to look.

Please note that significant changes were made between Update 3 and Update 4. Typically output from Update 3 is available here for comparison purposes.

AmigaOS 4.0 Amiga Early Startup Control
These initialisation process can be interrupted by holding down the 'Scroll Lock' key during the AmigaOS 4.0 boot process. You should also be able to use the left and right-mouse button combination on a PS/2 mouse (not USB mouse), but we have not found this particularly reliable. When interrupted, the folllowing screen is displayed:

At this time only 'Display Options ...' is not available and will be shaded blue, while 'Expansion Board Diagnostic ...' was not available under Update 3 and appeared ghosted as shown here.

Boot Options Display
Clicking on the 'Boot Options ...' button will display a screen similar to the following but exact content will depend on your configuration:

The devices shown on this display will depend on what you have defined for your system, which will typically be different to what is shown here.

The Select Boot Device box, displays all bootable devices and you can select which device you want to boot from simply by clicking on the device to highlight it. The highlighted device will be used as the boot device.

The Control Active Devices box displays all of the active devices, and clicking on devices here will change the device status from 'Enabled' to 'Disabled' and vice versa. The right most column shows the IDE controller associated with the device which for SiI0680 systems will be 'sii0680ide'.

Press the 'Use' button to boot using the highlighted value. Press the 'Cancel' button to revert to the original setting. Both buttons will return you to the AmigaOS 4.0 Amiga Early Startup Control screen.

Expansion Board Diagnostic Display
Clicking on the 'Expansion Board Diagnostic ...' button will display a screen similar to the following, but exact content will depend on components installed:

The information displayed here is fairly self-explanatory apart from the actual meaning, for example:
  • the third item in the list shown is on PCI bus 0 (the motherboard), has an address of 06.00, was manufactured by 3COM (10B7) and is actually a 3C905C-TX Fast Etherlink for PC Management NIC (9200) with a generic description of Network and the good news is that it is Working.
  • the last item in the list shown is on PCI bus 1 (the AGP slot), has an address of 00.00, was manufactured by ATI (1002) and is actually a Radeon 7000 graphics card (5159) with a generic description of Display and again the good news is that it is Working.
  • if anyone knows where an accessible list of manufacturer codes can be found we would happily publish it here. Finding a list of product codes for each manufacturer would need a miracle. Until then, see if you can guess the code for Intel.

The Select Boot Device box, displays all bootable devices and you can select which device you want to boot from simply by clicking on the device to highlight it. The highlighted device will be used as the boot device.

The Control Active Devices box displays all of the active devices, and clicking on devices here will change the device status from 'Enabled' to 'Disabled' and vice versa.

Booting the System
Once you have configured which device you want to boot from, enabled or disabled specific devices, or simply checked the expansion board diagnostics, you can then boot the system using either of the two options.

Clicking on 'Boot' will boot the AmigaOS 4.0 system in the normal way using the configuration you have selected. Clicking on 'Boot With No Startup-Sequence' does just that, it boots without using the defined startup sequence to boot directly into an AmigaDOS Shell window as follows:

This will also occur if you hold down the Ctrl key during booting rather than using the Amiga Early Startup Control window. It can be very useful if you have an error in your startup sequence that prevents the system from booting. If you need assistance to debug the Startup-sequence, at the prompt above you could type
    Set Interactive ON
    Execute S:Startup-sequence
This will enable you to step through each command in the Startup-sequence to help you can trace the problem.

Disclaimer: Amiga Auckland have prepared the above information for the use of its members based on our experiences and as such is subject to revision at any time. Amiga Auckland cannot guarantee any of the information and cannot be held accountable for any issues that may result from using it.


Copyright 2006 Amiga Auckland Inc. All rights reserved.
Revised: February 9, 2006.