From chankhun@netapp.com Mon Nov 30 21:34:19 1998 Date: Mon, 30 Nov 1998 02:25:24 -0800 (PST) From: Anawat Chankhunthod To: steveh@eecs.umich.edu Subject: PCMCIA Instruction for I7000 with 3com 575 Somebody posted it on message board at stanford. It really works. Anawat ------------------------------------------------------------------------- [Next-in-Thread] [Next Message] [Previous Message] [Next Thread] [Note:] more details Forum: PCMCIA Network Adapter Issues Re: [Question:] 3COM 3CCFE575BT-D card on Dell Inspiron 7000 (Nev Okyay) Keywords: 3CCFE575BT redhat dell inspiron 7000 Date: Sun, 29 Nov 1998 23:09:41 GMT From: Nev Okyay Installing 3CCFE575BT on Dell Inspiron 7000 with RedHat 5.1: 1. First, you need to enable the modules support in the kernel. There is a lot of info and readme files in the /usr/src/linux directory, but the gist of it is this: a. Type "make xconfig" in /usr/src/linux directory. b. Select modules support option. c. Follow the directions in the readme file, including the module-related steps. d. NOTE: redhat is shipped with the wrong link in the /boot/vmlinuz. Make this link to look like this: cd /boot; rm vmlinuz; ln -s /boot/vmlinuz-2.0.34 vmlinuz e. Now you can type "make install" to activate your new kernel. f. Don't forget to run lilo. type "lilo", and reboot. 2. Get the latest version (pcmcia-cs-3.0.6) of the pcmcia module. Note that what is shipped with redhat will not work with the network card above. Check out and get pcmcia-cs-3.0.6.tar.gz. 3. Unpack this package under /usr/src/linux. Type "tar xvzf pcmcia-cs-3.0.6.tar.gz" and read some documents, they are good! If you are impatient tho, continue on... 4. Type "cd pcmcia-cs-3.0.6". Now you go through three steps, config, make, and install. 5. Type "make config". Leave all defaults alone, except for two things: say "yes" to cardbus support, and say "yes" to experimental interrupt support like this- Include 32-bit (CardBus) card support (y/n) [y]: Experimental interrupt probe code (y/n) [y]: 6. Then type "make all" and "make install". Type "lilo" again to update the symbol table. Reboot the system by typing "shutdown -r now". 7. Now it is time to "futz with" the pcmcia configuration files. They are in two different directories: /etc/sysconfig and /etc/pcmcia. 8. In /etc/sysconfig there is a file called pcmcia. Make it look exactly like this: PCMCIA=yes PCIC=i82365 PCIC_OPTS="do_scan=0" CORE_OPTS= 9. The second file is config.opts in the /etc/pcmcia directory. The first uncommented line in this file includes some ports and memory. Only change the memory from 0xc0000-0xfffff to 0xA0000000-0xA0FFFFFF. (Note: I am not sure if this is necessary since I never checked the original settings). Leave everything else alone, but note that in this file some irq's are excluded from probing. Later you may have to exclude more irq's in this file. 10. Now update your network configuration files. This may take a little while, so my recommendation would be to do this while you try some home-brewed beer. Here is the list of files I know about: /etc/pcmcia/network.opts /etc/sysconfig/network /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/HOSTNAME /etc/hosts /etc/resolv.conf 11. You can independently start and stop the pcmcia and the networking modules. Note that networking relies on pcmcia, so start networking always after the pcmcia module, and stop networking always before the pcmcia module. Both scripts are in the /etc/rc.d/init.d directory. To start pcmcia, type "./pcmcia start". To start networking, type "./network start". 12. How do you know if it is working? You should hear two beeps when the pcmcia starts. Detailed info is dumped into the /var/log/messages file. Also type "cardctl status/config/ident". If the card seems to work for a little while and then stops with an error like "unknown interrupt" or "IRQ blocked by another device?", you have a potential interrupt conflict. To fix it, find out which interrupt was assigned to the card, and exclude that interrupt in the /etc/pcmcia/config.opts. Then stop and start the pcmcia module. NOTE: Win98 interrupt assignments have nothing to do with linux interrupt assignments. Sooo..., don't try to make them identical. ----------------------------------------------------------------------- Here are how various outputs should look when the card is set up properly. /var/log/messages ================= Nov 28 15:29:17 mobile kernel: Linux PCMCIA Card Services 3.0.6 Nov 28 15:29:17 mobile kernel: kernel build: 2.0.34 #8 Thu Nov 26 00:29:18 PS T 1998 Nov 28 15:29:17 mobile kernel: options: [pci] [cardbus] Nov 28 15:29:17 mobile kernel: Intel PCIC probe: Nov 28 15:29:17 mobile kernel: TI 1220 PCI-to-CardBus at bus 0 slot 4, mem 0x 68000000, 2 sockets Nov 28 15:29:17 mobile kernel: host opts [0]: [pwr save] [serial pci & irq] [no pci irq] [lat 168/176] [bus 32/34] Nov 28 15:29:17 mobile kernel: host opts [1]: [pwr save] [serial pci & irq] [no pci irq] [lat 168/176] [bus 35/37] Nov 28 15:29:17 mobile kernel: ISA irqs (default) = 3,4,5,7,9,10,11,12 poll ing interval = 1000 ms Nov 28 15:29:17 mobile cardmgr[222]: starting, version is 3.0.6 Nov 28 15:29:17 mobile cardmgr[222]: watching 2 sockets Nov 28 15:29:17 mobile kernel: cs: IO port probe 0x0100-0x03ff: clean. Nov 28 15:29:17 mobile cardmgr[222]: initializing socket 0 Nov 28 15:29:17 mobile cardmgr[222]: socket 0: 3Com 3CCFE575B/3CXFE575B Fast Et herLink XL Nov 28 15:29:17 mobile cardmgr[222]: executing: 'insmod /lib/modules/2.0.34/pcm cia/cb_enabler.o' Nov 28 15:29:18 mobile cardmgr[222]: executing: 'insmod /lib/modules/2.0.34/pcm cia/3c575_cb.o' Nov 28 15:29:18 mobile kernel: 3c59x.c:v0.99H 11/17/98 Donald Becker http://ces dis.gsfc.nasa.gov/linux/drivers/vortex.html Nov 28 15:29:18 mobile kernel: cs: cb_config(bus 32): vendor 0x10b7, device 0x5 157 Nov 28 15:29:18 mobile kernel: fn 0 bar 1: io 0x200-0x27f Nov 28 15:29:18 mobile kernel: fn 0 bar 2: mem 0xa0021000-0xa002107f Nov 28 15:29:18 mobile kernel: fn 0 bar 3: mem 0xa0020000-0xa002007f Nov 28 15:29:18 mobile kernel: fn 0 rom: mem 0xa0000000-0xa001ffff Nov 28 15:29:18 mobile kernel: vortex_attach(bus 32, function 0, device 5157) Nov 28 15:29:18 mobile kernel: eth0: 3Com 3CCFE575 Cyclone CardBus at 0x200, 0 0:10:4b:f1:8c:5a, IRQ 9 Nov 28 15:29:18 mobile kernel: eth0: CardBus functions mapped a0020000->0482300 0 Nov 28 15:29:18 mobile kernel: 8K byte-wide RAM 5:3 Rx:Tx split, MII interfac e. Nov 28 15:29:18 mobile kernel: MII transceiver found at address 0, status 780 9. Nov 28 15:29:18 mobile kernel: Enabling bus-master transmits and whole-frame receives. Nov 28 15:29:18 mobile cardmgr[222]: executing: './network start eth0' cardctl status output: ====================== Socket 0: 3.3V cardbus card present Function 0: ready Socket 1: no card cardctl config output: ====================== Socket 0: Vcc = 3.3, Vpp1 = 0.0, Vpp2 = 0.0 Interface type is cardbus IRQ 9 is exclusive, level mode, enabled Function 0: I/O window 1: 0x0200 to 0x027f, 32 bit Socket 1: not configured cardctl ident output: ===================== Socket 0: product info: "3Com Corporation", "3CCFE575BT", "LAN Cardbus Card", "001" manfid: 0x0101, 0x5157 function: 6 (network) Socket 1: No product info available. ----------------------------------------------------------------------- I have done the following simple tests using this card on the Dell Inspiron 7000: 1. nfs mounted another computer and copied ~800Mbytes of data (~6800 files) over the 10baseT network. 2. recursively 'diff'ed all the files/dirs. (This takes a while). 3. I repeated the above procedure at least three times. There were no errors. These tests/results do not mean there are no bugs in this driver, but I think it is pretty solid. I haven't seen any problems so far. Congratulations for a job well done! -- nev [Next-in-Thread] [Next Message] [Previous Message] [Next Thread] [Add message] to: "more details"