This file is a compilation of the few various AppLabs text files found in the tarball. These are made as one text file for quick and easy online viewing. The text files which come with the testing programs themselves are in separate folders in the tarball. The various text files are separated with lines like: >>> BEGIN PCMCIA WORKSHEET <<< >>> END PCMCIA WORKSHEET <<< >>> BEGIN TTCP TEST TOOL TEXT FILE <<< >>> END TTCP TEST TOOL TEXT FILE <<< The text files included in this file are: pcm_cert.txt >>> BEGIN PCMCIA WORKSHEET (pcm_cert.txt) <<< Linux PCMCIA Certification Worksheet AppLabs' Linux PCMCIA Certification Test, Revision 1.1 - JCW Section 1: Product Information Tester's Name: ___________________________________________ Date: _________________ Manufacturer: _____________________________________________________________________ Product Name and Model Number: ____________________________________________________ Product Description: ______________________________________________________________ Conforms to PCMCIA Standards: 1.0 2.0 2.01 2.1 Card Form Factor: Type I Type II Type III Manufacturer supplied driver: Yes No Driver Name: _______________________________ Driver found on the Internet: Yes No URL: _______________________________________ Driver included in Distribution: Yes No Kernel/Version: ____________________ Loadable Module: Yes No Overall Result: Pass Fail Section 2: Product Set Up and Installation Distributions Tested: Version [ ] Caldera: _________________ PASS FAIL [ ] Pacific HiTech: _________________ PASS FAIL [ ] S.u.S.E.: _________________ PASS FAIL [ ] Redhat: _________________ PASS FAIL Describe Test System Hardware : ___________________________________________________ Product requires modification out of the box? YES NO Notes: ____________________________________________________________________________ Can the unit be modified as suggested by manufacturer? YES NO Does the unit install as suggested by the manufacturer? YES NO Does the unit require a specific PCMCIA slot? YES NO Are any additional steps required for set up? YES NO Section 3: Functionality Testing Driver Availability Check: YES NO Unsupported Card Check YES NO System Detection Test: PASS FAIL Cardctl/Cardinfo Detection Test: PASS FAIL Functionality Tests NIC Card Testing PASS FAIL Serial Port/Modem Testing PASS FAIL SCSI Adapter Testing PASS FAIL IDE Adapter Testing PASS FAIL Memory Card Testing PASS FAIL Multi-function Card Testing PASS FAIL Section 4: Testing Procedures Explained Driver Availability Check Procedure: Tester checks the manufacturer and the PCMCIA-HOWTO file which comes with the PCMCIA-cs package to verify the existence of a driver. If the card is not listed, the tester should check Donald Becker's website to see if a driver is available there or if one is under construction. Determination: If a driver is available for the card the tester marks the worksheet as "YES" and proceeds to the Detection Test. Otherwise, the tester marks the worksheet as "NO" and proceeds to the Unsupported Card Check. Unsupported Card Check Procedure: Tester checks both the PCMCIA-HOWTO and the various net resources to determine if an existing driver might be used for the otherwise unsupported card. Determination: If there is an existing driver that might work, the tester sets up the card and continues on to the Detection Test. The tester should note the name of the driver and attach to the worksheet. The tester should also keep extensive notes on the setup process, attached these to both the worksheet and the final report. System Detection Test Procedure: Tester verifies via dmesg, /proc/pci or /var/log/messages that the system is detecting the PCMCIA card. Note that the PCMACIA-cs package should be compiled and installed and that certain switches in the kernel may need to be turned on or off before accurate detection may occur. Determination: If the card is reported as detected in dmesg, /proc/pci or in /var/log/messages then the test is a pass; otherwise, fail. Cardctl/Cardinfo Detection Test Procedure: Tester verifies that either one of these tools correctly sees the card, correctly identifies it by name, identifies the correct socket in which the card is attached, the correct port the card is using. the device the card is using and the correct current state of the card. Determination: If any of the items listed for checking in the procedures section is incorrect the tester should make every effort to configure the card and attain full functionality. For unsupported cards, if the card cannot be configured to be fully functional, the test is a fail; otherwise, pass. Functionality Tests NIC Card Testing Procedure: Tester must complete all the above relevant tests before doing any functionality tests. Tester uses the AppLabs LAN cert test and completes all related tests, attaching the completed worksheet to this PCMCIA worksheet. Determination: If all tests complete as "PASS" as described in the AppLabs LAN cert test then the test is a pass; otherwise, fail. Serial Port/Modem Testing Procedure: Tester must complete all the above relevant tests before doing any functionality test. Tester sets up the modem using either SLIP or PPP and connects via the modem with a known destination. Determination: Connections must be clean and usable. Any abnormalities (echoing, line noise) must not impair the connection to the point of being un-usable. Tester must correct any and all configuration problems which may be the cause of such impairment. If the modem makes a usable connection to the destination, the tester then transfers a file (either upload or download) and verifies the transfer rate is within ten percent (10%) of the manufacturer's reported maximum transfer rate. Determination: If the connection is clean and usable and the file transfer rate is within ten percent (10%) of the manufacturer's reported maximum transfer rate, the test is a pass; otherwise, fail. SCSI Adapter Testing Procedure: Tester must complete all the above relevant tests before doing any functionality tests. Tester uses the AppLabs SCSI cert test and completes all related tests, attaching the completed worksheet to this PCMCIA worksheet. Determination: If all tests complete as "PASS" as described in the AppLabs SCSI cert test then the test is a pass; otherwise, fail. IDE Adapter Testing Procedure: Tester must complete all the above relevant tests before doing any functionality tests. Tester uses fdisk to partition a hard drive attached to the card. Tester then used mkfs to build ext2 file systems on the hard drive. Tester then uses the bonnie test on the hard drive to measure throughput, check for excessive bottlenecking and to verify functionality of the controller card/hard drive combination. Determination: If all hard drive functionality is achieved and throughput to the drive is within the card/s manufacturer's prompted maximum rates and the eight hour bonnie test completes, then the test is a pass; otherwise, fail. If the tester suspects a test failed due to hard drive problems, then the tests must be run again with a different hard drive. Memory Card Testing Procedure: Tester must complete all the above relevant tests before doing any functionality tests. Tester then uses mkfs to build an ext2 file system on the card. Tester then uses the bonnie test on the card to measure throughput, check for excessive bottlenecking and to verify functionality of the card/file system. Tester next copies a tarball onto the file system, un-packs the tarball, compiles the program in the tarball and runs the compiled program from the card. Tester then unmounts the file system, removes the card, re-inserts the card and remounts the file system. All files on the card should remain and be fully usable. Determination: If an ext2 file system can be successfully built; if the eight-hour bonnie test completes; if the compiled program runs; and, if the file system can be successfully unmounted, the card removed, the card inserted and the file system remounted, the test is a pass; otherwise fail. Multi-function Card Testing Procedure: Tester must complete all the above relevant tests before doing any functionality tests. Multi-function cards are tested according to each separate functionality. For example, if the card has both NIC and modem functionality, then the card must be tested for each functionality. Tester must make detailed notes concerning setup of such cards since the possibility of conflicting ioports/IRQs, etc. is much greater than with single functions cards. Determination: If the card passes all relevant tests for each function, the test is a pass; otherwise fail. Resources: PCMCIA-HOWTO This HOWTO is included in the PCMCIA-cs tarball. Laptop-HOWTO This HOWTO can be found at: http://www.snafu.de/~wehe/Laptop-HOWTO.html LILAC: http://www.snafu.de/~wehe/index_li.html Donald Becker's website: http://cesdis.gsfc.nasa.gov/linux/pcmcia/pcmcia.html David Hind's PCMCIA ftp site will direct you to: ftp://sourceforge.org/pcmcia/ where you'll find the PCMCIA-CS tarball and other related goodies. >>> END PCMCIA WORKSHEET (pcm_cert.txt) <<<