Our friend and talented developer Neil Cafferkey posted to AROS-EXEC a nice guide to most common issues people met with Icaros Desktop 2.0 in the first days after release. If you have issues, before sending a help request to our support forum, please try these hints:
The native SATA/AHCI driver doesn't always work. If you get errors related to ahci.device, try disabling it. Press E when your chosen boot entry is highlighted in the GRUB menu, scroll down to the ahci.device entry, and delete it with Ctrl-K. Then press Ctrl-X to boot. If your disk isn't accessible at all with this change, you might need to change the SATA controller to IDE legacy mode in the BIOS: however, making this change will likely cause problems booting Windows on the same machine (if it's already installed). To disable ahci.device permanently, edit the text file "SYS:Arch/pc/grub/grub/cfg", and remove the ahci.device line from all boot entries you intend to use.
The ATA driver doesn't always work. If you get errors related to ata.device, try using the alternative, older version provided: Press E when your chosen boot entry is highlighted in the GRUB menu, scroll down to the ata.device entry, and change it to read "module /Devs/Alt/ata.device". Then press Ctrl-X to boot. To make this change permanent, edit the text file "SYS:Arch/pc/grub/grub/cfg", and change the path to ata.device in all boot entries you intend to use.
The NTFS filesystem driver doesn't always work. In some cases, ntfs-handler locks up during boot if you have NTFS (i.e. "Windows") partitions on your PC. To disable ntfs-handler, move it from "L:" to "SYS:Storage".
AROS won't boot when some themes are selected. Avoid choosing the os3.1 or mason themes. If you want a similar appearance to the os3.1 theme, move "C:Decoration" to "SYS:Storage". If you've already selected a broken theme, you can recover the situation as follows:
Boot from your installation media.
Move "AROS:C/Decoration" as described above.
Reboot from your HD, and select a working theme.
Restore "Decoration" to its original location ("C:").
The "noacpi" boot option cause all PCI devices to be invisible to AROS. Although disk drives may still work, network, sound etc. drivers won't.
Changing video resolution may cause a crash, especially when using the Intel GMA driver. I'm not sure if the new resolution will still be saved for the next boot. If not, you can work around the problem by temporarily switching to Wanderer in Icaros preferences.
Some VirtualBox settings are incompatible with AROS. Do not select ICH9 or ICH6 chipsets, nor SATA drives. Only use AC97 audio.