Technical data

B. Appendixes to optional packages
• wrong disk is configured for the installation
• Controller is not supported by fli4l. Some controllers may need special drivers not in-
cluded with fli4l
Problem:
• Installation routine stops
• after a remote update of the opt-archive the router refuses to boot
• Error messages occur while partitioning or formatting the harddisk
Possible Causes:
• IDE harddisks can suffer from cables too long or unmatching
• older harddisks may suffer from wrong PIO mode or transfer rate settings in Bios (or
controller) eventually being too fast for the disk.
• IDE-Chipset not suitable
Remarks:
• Problems with DMA eventually can be solved by setting LIBATA_NODMA='no'. (The
default is ’yes’). This activates DMA with ATA devices.
Problem:
• fli4l doesn’t boot from harddisk after the installation
Possible Cause:
• If booting from a CF module fails check if the CF was recognized as LBA or LARGE by
the Bios. Correct setting for modules smaller than 512MB is NORMAL or CHS.
• an Adaptec 2940 Controller with an old BIOS is used and extended mapping for harddisks
over 1GB is active. Update the Bios of the SCSI controller or switch mapping.
By switching the mapping all data on the disk will be lost!
Problem:
• Windows error message while preparing of a CF-card: „Medium in drive (X:) contains
no FAT. [Cancel]“.
Possible Cause:
• The card was removed from the reader too early / without unmounting. Windows did
not finish writing and the file system is damaged. Prepare the CompactFlash again at
the fli4l via HD-install.
353