Next Previous Contents

2. CPUs, Motherboards, Buses, Etc.

2.1 Not listed = not supported

Note: Hardware vendors like to re-use product names on different hardware as they have trademarks on certain words or they are trying to establish a "brand-name." This overuse of brand-names can be very confusing to the consumer in that one may have purchased something that looks to be supported but has a slightly different name (an added letter or a plus or some other little item.) Most of the time these changes indicate that the hardware is very different, and thus will not be supported. When considering the items below, we have tried to be explicit on what items are covered. If it is not listed, then it is probably not supported (though it might be compatible and supported in the future).

2.2 Definitions of Hardware

If you find the terms "Tier 1", "Tier 2", etc confusing , you will want to look at the following sections for more information on what we mean:

2.3 CPUs

Tier 1 Supported CPUs

Intel 80386, 80486, Pentium, Pentium Pro, and Pentium II, and Pentium III (regular and Xeon versions) central processing units (CPUs). For older boards without a floating point co-processor, the Linux kernel has built in FPU emulation.

AMD K6-2 (3DNow): Some early K6-2 300mhz have problems with the system chips. You will need to get replacement chips from AMD.

AMD K6-3: No known problems with the 2.2 kernels.

Tier 2 Supported CPUs

Non-Intel clone CPUs. These CPUs may not be any more "buggy" than pure Intel CPUs, but since the market size of these chips is smaller, what problems do occur seem to be harder to get around.

Tier 3 Compatible CPUs

Tier 3 Incompatible and Unsupported CPUs

2.4 Motherboards

Compatible Motherboards

Except for those listed under the section Incompatible Motherboards below, we don't know of a motherboard chip-set Red Hat Linux 6.1/Intel doesn't work with.

Incompatible Motherboards

2.5 Buses

Compatible Buses

PCI, AGP, ISA, EISA, VESA local bus (VLB).

Compatible but Unsupported Buses

Not Supported Buses

2.6 RAM (memory)

16 MB minimum (requires 32 MB swap space). 24 MB or more is recommended for better performance. If you wish to run GNOME or KDE, it is recommended that you have 48 MB or more RAM.

2.7 Plug-and-Play

The 2.2.x series of kernels have some Plug-and-Play (PNP) support. Red Hat Linux Intel/6.1 ships with kernel 2.2.12 with PNP support compiled in by default. Not all Plug and Play devices are supported but a growing number of them are.

Factors of PNP Compatability

Things to keep in mind for determining if a Plug and Play card or device is recognized properly by the kernel.

  1. The BIOS revision of the motherboard and whether it is set to utilize a Plug and Play aware operating system or not factors into whether the devices are recognized.
  2. BIOS Configures PnP (For the PCI bus you only need a PCI BIOS, otherwise you need a PnP BIOS)
  3. Systems that multi-boot can end up having changes written to the BIOS about the configuration of the devices that are correct for other operating systems but not for Linux.
  4. Plug and Play modems are still considered to be incompatible.
  5. Hardware that is not recognized and requires plug and play to be configured at startup is not supported. This includes items like plug and play SCSI cards or other disk controllers.
  6. For PNP peripherals that don't work with Red Hat Linux see if the peripherals have jumper or BIOS settings that will ``turn off'' their PNP support and simply use their configured IRQ and port settings. It is recommended to turn off PNP support in that manner for each PNP peripheral you want to use with Red Hat Linux 6.1/Intel.
  7. The isapnptools included on the CD-ROM can be used to configure plug and play hardware. The sndconfig program uses it to detect and configure the plug and play Creative Labs sound cards. Another method of configuring this hardware includes using Win95 to setup the hardware and then warm booting into Linux via LOADLIN.
  8. PCI Utilities can be used for configuring the PCI bus
  9. The Linux kernel can be patched to transform Linux into a PnP operating system (see the Plug and Play howto below for instructions. This is not covered under installation support.)
  10. Some device drivers can configure the device regardless of PNP support.

Any of the above can set the resources in the hardware. But only the last two should tell device driver what it's done. Only the last one definitely tells the driver (since it is the driver). How the driver gets informed depends on the driver and you may need to do something to inform it.


Next Previous Contents