Recent changes to Hardware2

Hardware2 modified by Olaf Westrik

Olaf Westrik — Wed, 25 Dec 2013 11:05:31 -0000

--- v3
+++ v4
@@ -24,7 +24,7 @@
 If your hardware is not recognised:

 * first make sure the hardware is working, try swapping PCI slots for example
-* identity the driver that is used for the hardware by using a (recent) 2.6 or 3.x kernel (for example [KNOPPIX](http://www.knoppix.org/)
+* identity the driver that is used for the hardware by using a (recent) 2.6 or 3.x kernel (for example [KNOPPIX](http://www.knoppix.org/))
 * find the id of your hardware
     * for PCI, use lspci and lspci -n or cat /proc/pci/devices during install 
     * for USB, use cat /proc/bus/usb/devices

Hardware2 modified by Olaf Westrik

Olaf Westrik — Wed, 25 Dec 2013 11:04:57 -0000

--- v2
+++ v3
@@ -16,18 +16,19 @@
 ===

 There is no hardware compatibility list for motherboards, network cards, etc. available. The list of PCI and USB IDs may give an indication, but it may be hard to correlate vendor and device IDs to a device you can buy in a shop.
-To know if your PCI or USB hardware will be recognised by IPCop v2, check the ID with the [wiki:PciIDMap PCI ID map] and with the [wiki:UsbIDMap USB ID map] lists produced after compilation.
+To know if your PCI or USB hardware will be recognised by IPCop v2, check the ID with the [PCI ID map](PciIDMap) and with the [USB ID map](UsbIDMap) lists produced after compilation.
 For ISA cards there is no such facility available. 

 The fastest way to check if the hardware is supported is to test. Installing IPCop is an easy job of only a few minutes (~ 15 minutes, less if you are more experienced). 
-If your hardware is not recognised: 
+If your hardware is not recognised:
+
 * first make sure the hardware is working, try swapping PCI slots for example
-* identity the driver that is used for the hardware by using a (recent) 2.6 or 3.x kernel (for example [http://www.knoppix.org/](KNOPPIX))
+* identity the driver that is used for the hardware by using a (recent) 2.6 or 3.x kernel (for example [KNOPPIX](http://www.knoppix.org/)
 * find the id of your hardware
- * for PCI, use lspci and lspci -n or cat /proc/pci/devices during install 
- * for USB, use cat /proc/bus/usb/devices 
- * check if the vendor ID and device ID are present on the kernel compiled for IPCop (using above lists)
+    * for PCI, use lspci and lspci -n or cat /proc/pci/devices during install 
+    * for USB, use cat /proc/bus/usb/devices 
+    * check if the vendor ID and device ID are present on the kernel compiled for IPCop (using above lists)

 If the ID is known in the IPCop kernel, that means that the driver or the installation process does not work as intented, this usually means the hardware is defective.
 If the ID is not known, that means that the ID may have to be added to the driver, the driver is not enabled or the driver is not yet available in the kernel version used by IPCop.

Hardware2 modified by Olaf Westrik

Olaf Westrik — Wed, 25 Dec 2013 10:58:57 -0000

--- v1
+++ v2
@@ -2,13 +2,14 @@
 ==

 Hardware requirements for IPCop v2:
+
 * 486 CPU or better
 * 512 MiB disk space
 * 64 MiB RAM
 * 2 network cards or 1 network card, if you are using one of the following to connect to the internet
- * analog modem
- * ISDN card 
- * GSM, UMTS etc. modem
+    * analog modem
+    * ISDN card 
+    * GSM, UMTS etc. modem

 Find and report supported/unsupported hardware

Hardware2 modified by Olaf Westrik

Olaf Westrik — Wed, 25 Dec 2013 10:49:16 -0000

Hardware requirements

Hardware requirements for IPCop v2:
486 CPU or better
512 MiB disk space
64 MiB RAM
2 network cards or 1 network card, if you are using one of the following to connect to the internet
* analog modem
* ISDN card
* GSM, UMTS etc. modem

Find and report supported/unsupported hardware

There is no hardware compatibility list for motherboards, network cards, etc. available. The list of PCI and USB IDs may give an indication, but it may be hard to correlate vendor and device IDs to a device you can buy in a shop.
To know if your PCI or USB hardware will be recognised by IPCop v2, check the ID with the [wiki:PciIDMap PCI ID map] and with the [wiki:UsbIDMap USB ID map] lists produced after compilation.
For ISA cards there is no such facility available.

The fastest way to check if the hardware is supported is to test. Installing IPCop is an easy job of only a few minutes (~ 15 minutes, less if you are more experienced).
If your hardware is not recognised:
first make sure the hardware is working, try swapping PCI slots for example
identity the driver that is used for the hardware by using a (recent) 2.6 or 3.x kernel (for example http://www.knoppix.org/)
* find the id of your hardware
* for PCI, use lspci and lspci -n or cat /proc/pci/devices during install
* for USB, use cat /proc/bus/usb/devices
* check if the vendor ID and device ID are present on the kernel compiled for IPCop (using above lists)

If the ID is known in the IPCop kernel, that means that the driver or the installation process does not work as intented, this usually means the hardware is defective.
If the ID is not known, that means that the ID may have to be added to the driver, the driver is not enabled or the driver is not yet available in the kernel version used by IPCop.

In any case, please report the problem with the ID values and drivername as a New Ticket.

non-x86 platforms

Support for other platforms (Alpha, PowerPC, Sparc) is currently not complete.