Depending on the configuration of the PC being used there could be conflicts when using the Discwizard boot CD such as the system freezing during boot, the system rebooting unexpectedly, or fails to load when running the detection process within the Linux Kernel, or the Discwizard Bootable CD.
Additional parameters can be applied during the creation of the Boot CD, which could resolve issues in regards to the above mentioned issues. These parameters are added during the screen “Boot Media Options”, selecting the Bootable media startup parameters and adding in one or more parameter entries listed below.
The following parameters can be used to load Linux kernel in a special mode:
acpi=off
Disables ACPI and may help with a particular hardware configuration.
noapic
Disables APIC (Advanced Programmable Interrupt Controller) and may help with a
particular hardware configuration.
nousb
Disables USB modules loading.
nousb2
Disables USB 2.0 support. USB 1.1 devices still work with this option. This option
allows using some USB drives in USB 1.1 mode, if they do not work in USB 2.0 mode.
quiet
This parameter is enabled by default and the startup messages are not displayed.
Deleting it will result in the startup messages being displayed as the Linux kernel is
loaded and the command shell being offered prior to running the very Acronis
program.
nodma
Disables DMA for all IDE disc drives. Prevents kernel from freezing on some
hardware.
nofw
Disables FireWire (IEEE1394) support.
nopcmcia
Disables PCMCIA hardware detection.
nomouse
Disables mouse support.
[module name]=off
Disables the module (e.g. sata_sis=off).
pci=bios
Forces to use PCI BIOS, not access the hardware device directly. For instance, this
parameter may be used if the machine has a non-standard PCI host bridge.
pci=nobios
Disallows use of PCI BIOS; only direct hardware access methods are allowed For
instance, this parameter may be used if you experience crashes upon boot-up,
probably caused by the BIOS.
pci=biosirq
Uses PCI BIOS calls to get the interrupt routing table. These calls are known to be
buggy on several machines and they hang the machine when used, but on other
computers it is the only way to get the interrupt routing table. Try this option, if the
kernel is unable to allocate IRQs or discover secondary PCI buses on your
motherboard.
