At this time a math-coprocessor chip is required equipment for Linux m68k. Also your CPU must have a functional MMU (Memory Management Unit, or address translator), which means you need a 68020 or better.

RedHat m68k Linux will not install correctly if any of your AFFS partitions have the DirCache option enabled. Linux may not be able to see or use any partition located on any drive also containing DirCache partitions. This affects system disk drivers as well as the afdisk program. This problem is being looked into.

The supplied Linux kernel images are used only during the installation process- they are not used thereafter. This usually results in Linux not recognizing disk controllers, network cards, etc. The current work-around is to use a pre-compiled kernel image from a public m68k Linux FTP site (described later). This will allow you to bring Linux up to the point where you can build your own customized kernel.

There are several known problems with the 2.0.32 kernel, the worst being major problems with masquerade. This is a concern only if you wish your Amiga to act as an internet gateway for your local network. The solution is to upgrade to 2.0.33 kernel or newer, which is a good idea in any case.

I have reproduced a problem that seems to be related to specifying nameserver/gateway machines during initial network setup for NFS/FTP installs. I recommend leaving the nameserver and gateway fields empty (totally blank) until after the installation is complete. (try man resolver for details)

One problem I noticed on the AmigaDos side is that the CDROM drivers that came with OS3.x cannot handle Rock-Ridge extensions correctly. You can avoid this issue by using more recent CDROM drivers (amicdfs240.lha from AmiNet seems to work fine).

This is not a Linux problem, but it is possible for the Amiga boot process to lock up if it sees partitions created with other operating systems such as MsDos or intel Linux. The solution is to boot AmigaDos with a floppy and run HDToolBox on the new (alien) partition. Select the disk in question and enter the partition drive screen. After enabling the Advanced checkbox, Disable the Automount and Boot checkboxes, save the changes back to disk. AmigaDos should now boot correctly (assuming this was the cause of your problem).

While partitioning the IDE hard disk on my A4000 (running AmigaDos 3.0) I found that I had to set the MaxTransfer field to a value of 0xfffe or the filesystem would be corrupt, and the system would eventually crash. This problem does not seem to exist with AmigaDos 3.1 .

After entering the amiboot command, the video from my (North American NTSC) A4000 started rolling and was unusable. The solution was to specify the video=ntsc option on the amiboot command-line, which forced the video to NTSC mode.