Use this page to discuss PCMCIA network adapter issues. Before posting, be sure you've checked any relevant sections of the PCMCIA-HOWTO, such as: Particularly useful bits of information to post include your laptop's make and model; the type(s) of card(s) you are using; and, of course, any relevant system log messages.

Messages Inline: 0 1

Question eth0: interrupt(s) dropped! messages

Date: 1999, Nov 01
From: Rick Lerner rlerner

PROBLEM:  My network PCCard appears to work fine, but /var/log/messages
contains hundreds of lines containing the following error message:

	 Nov  1 15:46:06 localhost kernel: eth0: interrupt(s) dropped! 

Any ideas what is wrong?

I recently updated my laptop from RedHat 5.1 to 6.1.  To complete the
upgrade I needed to add an ifcfg-eth0 file with the following contents:

/etc/sysconfig/network-scripts/ifcfg-eth0:
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=no

I also added links to /etc/rc.d/init.d/pcmcia in /etc/rc.d/rc[345].d

Otherwise, the pcmcia configuration files are the ones installed by RedHat.

Thanks for any information,
  Rick Lerner
  (rick@aai.com ) Amerinex Applied Imaging, Inc.


--------------------------------------------------
DETAILS:
--------------------------------------------------

System Type:	Ergo Bigscreen4 laptop
Processor:	Pentium II, 266MHz
RAM:		96MB
Linux:		RedHat 6.1
uname -rv:	2.2.12-20 #1 Mon Sep 27 10:40:35 EDT 1999
PCMCIA Version:	cardctl version 3.0.14
Probe output:	PCI bridge probe: O2Micro OZ6836 found, 2 sockets.

cardctl status
	Socket 0:
	  5V 16-bit card present
	  Function 0: ready
	Socket 1:
	  no card

cardctl ident 
	Socket 0:
	  product info: "3Com Corporation", "3C589", "TP/BNC LAN Card Ver. 2a", "000002"
	  manfid: 0x0101, 0x0589
	  function: 6 (network)
	Socket 1:
	  no product info available


----------------------------------------------------------------------
/var/log/messages excerpt generated by
	/etc/rc.d/init.d/pcmcia start (after a stop whose output is not shown)
----------------------------------------------------------------------

Nov  1 17:50:10 localhost kernel: Linux PCMCIA Card Services 3.0.14 
Nov  1 17:50:10 localhost kernel:   kernel build: 2.2.12-20 #1 Mon Sep 27 10:40:35 EDT 1999 
Nov  1 17:50:10 localhost kernel:   options:  [pci] [cardbus] [apm] 
Nov  1 17:50:10 localhost kernel: Intel PCIC probe:  
Nov  1 17:50:10 localhost kernel:   O2Micro OZ6836 PCI-to-CardBus at bus 0 slot 3, mem 0x28000000, 2 sockets 
Nov  1 17:50:10 localhost kernel:     host opts [0]: [a 00] [b 00] [c 00] [d 83] [mhpg 18] [fifo 08] [e 0a] [no pci irq] [lat 168/176] [bus 32/34] 
Nov  1 17:50:10 localhost kernel:     host opts [1]: [a 00] [b 00] [c 50] [d 83] [mhpg 18] [fifo 08] [e 0a] [no pci irq] [lat 168/176] [bus 35/37] 
Nov  1 17:50:10 localhost kernel:     ISA irqs (scanned) = 10 polling interval = 1000 ms 
Nov  1 17:50:10 localhost cardmgr[1507]: starting, version is 3.0.14
Nov  1 17:50:10 localhost cardmgr[1507]: watching 2 sockets
Nov  1 17:50:10 localhost kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x1000-0x104f 
Nov  1 17:50:10 localhost kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x100-0x107 0x200-0x207 0x220-0x22f 0x300-0x307 0x378-0x37f 0x388-0x38f 0x4d0-0x4d7 
Nov  1 17:50:10 localhost kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
Nov  1 17:50:11 localhost cardmgr[1507]: initializing socket 0
Nov  1 17:50:11 localhost kernel: cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa00fffff 
Nov  1 17:50:11 localhost cardmgr[1507]: socket 0: 3Com 3c589 Ethernet
Nov  1 17:50:11 localhost cardmgr[1507]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/3c589_cs.o'
Nov  1 17:50:11 localhost kernel: eth0: 3Com 3c589, io 0x310, irq 10, hw_addr 00:20:AF:DF:F6:1B 
Nov  1 17:50:11 localhost kernel:   8K FIFO split 5:3 Rx:Tx, auto xcvr 
Nov  1 17:50:11 localhost cardmgr[1507]: executing: './network start eth0'
Nov  1 17:50:12 localhost pumpd[1537]: starting at Mon Nov  1 17:50:12 1999  
Nov  1 17:50:13 localhost kernel: eth0: interrupt(s) dropped! 
Nov  1 17:50:17 localhost pumpd[1537]: configured interface eth0
Nov  1 17:50:17 localhost cardmgr[1507]: + Determining IP information for eth0... done.
Nov  1 17:50:18 localhost kernel: eth0: flipped to 10baseT 
Nov  1 17:50:24 localhost kernel: eth0: interrupt(s) dropped! 
Nov  1 17:50:56 localhost last message repeated 4 times
Nov  1 17:52:03 localhost last message repeated 9 times
Nov  1 17:53:04 localhost last message repeated 10 times

None Re: Question: eth0: interrupt(s) dropped! messages

Re: Question eth0: interrupt(s) dropped! messages (Rick Lerner)
Date: 1999, Nov 01
From: David Hinds <dhinds@pcmcia.sourceforge.org>

On Mon, Nov 01, 1999 at 03:08:48PM -0800, Rick Lerner wrote:
> 
> Nov  1 15:46:06 localhost kernel: eth0: interrupt(s) dropped! 

"interrupt(s) dropped" means that the card indicates it tried to
generate an interrupt, but the host didn't actually see it.

There are a couple possible causes for this.  One is that another
system device could be occupying this interrupt line, electrically
interfering with the PCMCIA card's attempt to trigger an interrupt.
Another possibility is a problem with interrupt setup in the PCMCIA
bridge.

In the first case, you could exclude the interrupt line used by the
PCMCIA device in your /etc/pcmcia/config.opts file, to force the card
to get a different interrupt.  The second case is more tricky because
it indicates a problem in the Linux socket driver.

In your case, I think it is a problem of the second type.  The O2Micro
CardBus bridges have some known problems with the current Linux driver
package.  Interrupt routing is handled differently from other bridges,
and the datasheets are confusing.

One thing to try: in /etc/sysconfig/pcmcia, set:

    PCIC_OPTS="do_scan=0"

which will disable the i82365 module's interrupt scanning code.  The
driver seems to think that irq 10 is the only one available for
PCMCIA, and that seems likely to be wrong.  It is possible that
another interrupt line will behave better.

If this doesn't improve things, I'd count your blessings, since you've
picked a card with a driver that (relatively) painlessly recovers from
missed interrupts.  You won't get great performance, but it is better
than a card that doesn't work at all.

-- Dave

Ok do_scan did the trick

Re: None Re: Question: eth0: interrupt(s) dropped! messages (David Hinds)
Date: 1999, Nov 02
From: Rick Lerner rlerner

Thanks David,

Adding do_scan=0 to /etc/sysconfig/pcmcia did the trick.
It now picks IRQ 3 and I do not get any "interrupt(s) dropped!" messages.

Other than 3c589_cs moving from IRQ 10 to 3, /proc/interrupts was unaffected by this change.

Rick

Question Billionton LNA-100B

Date: 1999, Nov 04
From: Markus Troebensberger troebs

Is a driver available for the Billionton LNA-100B ?

Have anyone experience with this card ?

If not:

I will try to write a driver. Have anyone contact to Billionton ?

None It is not a supported card, but...

Re: Question Billionton LNA-100B (Markus Troebensberger)
Date: 1999, Nov 04
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The obvious question would be, have you tried adding an entry to
/etc/pcmcia/config, to see if any of the existing drivers already
work?

(the chance that it is actually a new design and needs a new driver to
be written from scratch are roughly... zero)

-- Dave

Sad I have testet ...

Re: None It is not a supported card, but... (David Hinds)
Date: 1999, Nov 05
From: Markus Troebensberger troebs

I have testet all drivers that i have seen at the other entrys in /etc/pcmcia/config.

3c589_cs, fmvj18x_cs and 3c574_cs:

At boot time these drivers show a MAC (Hardwareaddress) of: 00:00:00:00:00:00 or FF:FF:FF:FF:FF:FF This is not a correct address. Is'nt it ?

(two high beeps when putting the card into the slot)

The other drivers pcnet_cs, xirc2ps_cs, smc91c92_cs and nmclan_cs:

They beep once high and once low.

What can I do ?

Markus

Question It nearly works

Re: Question Billionton LNA-100B (Markus Troebensberger)
Date: 1999, Nov 08
From: Markus Troebensberger troebs

I have probed the pcnet_cs driver.

Because i have not found the hardware adress in my card
(with memory_cs), i have hardcoded it in config.opts.

Now i get a connection, but it is not working very well.
I belief there is a interrupt problem or a timimg problem.

This is the output from boot, ping and dmesg.
Can you pinpoint the problem ?

bootmsg:

Starting PCMCIA services: modulesLinux PCMCIA Card Services 3.0.6
  kernel build: 2.0.36 #4 Mon Nov 1 22:57:02 MET 1999
  options:  [pci] [apm]
Intel PCIC probe:
  TI 1131 PCI-to-CardBus at bus 0 slot 10, mem 0x68000000, 2 sockets
    host opts [0]: [ring] [clkrun irq 12] [pci + serial irq] [no pci irq] [lat 1
68/176] [bus 32/34]
    host opts [1]: [ring] [clkrun irq 12] [pci + serial irq] [no pci irq] [lat 1
68/176] [bus 35/37]
    ISA irqs (scanned) = 3,4,7,10,11,15 status change on irq 15
 cardmgr.
cardmgr[80]: starting, version is 3.0.6
cardmgr[80]: watching 2 sockets
cs: IO port probe 0x1000-0x17ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x330-0x337 0x378-0x37f 0x388-0x38f 0
x398-0x39f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cardmgr[80]: initializing socket 1
cs: memory probe 0xa0000000-0xa0ffffff: clean.
cardmgr[80]: socket 1: Billionton LNA-100B
Starting RPC portmap daemoncardmgr[80]: executing: 'insmod /lib/modules/2.0.36/n
et/8390.o'
cardmgr[80]: executing: 'insmod /lib/modules/2.0.36/pcmcia/pcnet_cs.o hw_addr=0x
00,0x10,0x60,0x30,0x01,0x86'
eth0: NE2000 Compatible: port 0x300, irq 11, hw_addr 00:10:60:30:01:86
cardmgr[80]: executing: './network start eth0'
net_interrupt(): irq 11 for unknown device.



Ping Output:

pino:~ # ping 192.168.100.20
PING 192.168.100.20 (192.168.100.20): 56 data bytes
64 bytes from 192.168.100.20: icmp_seq=4 ttl=128 time=10000.6 ms
64 bytes from 192.168.100.20: icmp_seq=8 ttl=128 time=8001.1 ms
64 bytes from 192.168.100.20: icmp_seq=13 ttl=128 time=7000.6 ms
64 bytes from 192.168.100.20: icmp_seq=21 ttl=128 time=5001.1 ms
64 bytes from 192.168.100.20: icmp_seq=24 ttl=128 time=4001.9 ms
64 bytes from 192.168.100.20: icmp_seq=52 ttl=128 time=2000.5 ms
64 bytes from 192.168.100.20: icmp_seq=62 ttl=128 time=1000.3 ms
64 bytes from 192.168.100.20: icmp_seq=71 ttl=128 time=1000.4 ms
64 bytes from 192.168.100.20: icmp_seq=78 ttl=128 time=1000.4 ms
64 bytes from 192.168.100.20: icmp_seq=83 ttl=128 time=1000.4 ms
64 bytes from 192.168.100.20: icmp_seq=84 ttl=128 time=1000.3 ms
64 bytes from 192.168.100.20: icmp_seq=85 ttl=128 time=1002.0 ms
64 bytes from 192.168.100.20: icmp_seq=88 ttl=128 time=1000.4 ms

--- 192.168.100.20 ping statistics ---
92 packets transmitted, 13 packets received, 85% packet loss
round-trip min/avg/max = 1000.3/3308.4/10000.6 ms


dmesg:


....
eth0: Interrupted while interrupts are masked! isr=0x3 imr=0x0.
eth0: Tx timed out, lost interrupt? TSR=0x1, ISR=0x3, t=200.
eth0: Interrupted while interrupts are masked! isr=0x3 imr=0x0.
eth0: Tx timed out, lost interrupt? TSR=0x1, ISR=0x3, t=200.
eth0: Interrupted while interrupts are masked! isr=0x43 imr=0x0.
eth0: Tx timed out, lost interrupt? TSR=0x1, ISR=0x43, t=200.
eth0: Interrupted while interrupts are masked! isr=0x3 imr=0x0.
eth0: Tx timed out, lost interrupt? TSR=0x1, ISR=0x3, t=200.
lp1 out of paper
eth0: Interrupted while interrupts are masked! isr=0x3 imr=0x0.
eth0: Tx timed out, lost interrupt? TSR=0x1, ISR=0x3, t=200.
eth0: unexpected TX-done interrupt, lasttx=20.
eth0: unexpected TX-done interrupt, lasttx=20.
eth0: unexpected TX-done interrupt, lasttx=20.
eth0: unexpected TX-done interrupt, lasttx=20.
eth0: unexpected TX-done interrupt, lasttx=20.
eth0: unexpected TX-done interrupt, lasttx=20.
eth0: unexpected TX-done interrupt, lasttx=20.
eth0: unexpected TX-done interrupt, lasttx=20.
eth0: unexpected TX-done interrupt, lasttx=20.
eth0: unexpected TX-done interrupt, lasttx=20.
eth0: Too much work at interrupt, status 0x02
eth0: Interrupted while interrupts are masked! isr=0x3 imr=0x0.
eth0: Tx timed out, lost interrupt? TSR=0x1, ISR=0x3, t=200.
eth0: Interrupted while interrupts are masked! isr=0x3 imr=0x0.
eth0: Tx timed out, lost interrupt? TSR=0x1, ISR=0x3, t=200.


--
Markus

None So close yet so far?

Re: Question It nearly works (Markus Troebensberger)
Date: 1999, Nov 20
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> eth0: Interrupted while interrupts are masked! isr=0x3 imr=0x0.
> eth0: Tx timed out, lost interrupt? TSR=0x1, ISR=0x3, t=200.
> eth0: unexpected TX-done interrupt, lasttx=20.

This chip does not appear to be 100% NE2000 compatible.

-- Dave

News first LNA-100B success

Re: Question It nearly works (Markus Troebensberger)
Date: 2000, Jun 30
From: Miroslaw Kwasniak mirek

I read about AX88190 problems on many places. I have two different cards, one is Billionton LNA-100B and other Acorp (noname (???) with Zonet MAC address). Acorp still isn't working :(

I'v got working LNA-100B. Currently it has ping time 2/3/10 ms and transfer speed about 500KB/s @ 10tx and 600KB/s @ 100tx/fullduplex on my old laptop 486/66 without RAM cache :( (other end is P200 with tulip based KNE100TX). It works in autonegotiation mode. I'd hot changed standard cable connected to 10tx hub with direct cross cable to other end and mode was switched on the fly from 10tx/HDX to 100tx/FDX without trouble.

Current configuration:

- kernel 2.2.17pre9

- pcmcia-cs 3.3.16

- Billionton src from lna100b.zip: Linux/RedHat_6.0/LNA100SR.TGZ (tgz size:92828 date:16 maj 14:16). After untaring it move all files from lna100src directory to pcmcia-cs-3.1.16/clients. Run Configure and make all :)

Use config.lna100b from lna100b.zip. Rename it to lna100b.conf. Edit it and change a line from:

  class "network" module "lnax100"  

to:

  class "network" module "lna100"  

and enjoy it :)

I'v crashed my system hot ejecting card :(

Because linux on laptop is only testing instalation (looplinux on FAT partition) speed test were made on ftp protocol with simply tools:

- server: wu_ftpd with 50MB file (full cached in RAM)

- laptop: mc (ftp-filesystem) transfering to /dev/null

Mirek

Question Kingmax? PCMCIA 10/100 adapter

Date: 1999, Nov 06
From: Nathan Hartwell MageX

I just got a laptop. With this laptop, I ordered a 10/100 card. It's a generic card, but from the checking I've done, it seems to be a Kingmax Technologies product. Anyway, it's based on the ASIX AX88190 chip (I think). This assumption is based on information that was in a Linux driver archive that shipped with the card. Unfortunately, this driver was written for older versions of pcmcia-cs (3.0.x it seems) and Linux kernel (2.0.x). According to documention from ASIX, the AX88190 is register compatible with the 8390. Ok, so I managed to get the system to see the card, and actually work with it. However, I get tons of kernel msgs regarding interrupt routine reentrance. Since these msgs don't just go to /var/log/messages, but also get dumped on the console, I find the messages more than annoying. Anyone capable of helping here?

Sad These cards are not really NE2000 compatible

Re: Question Kingmax? PCMCIA 10/100 adapter (Nathan Hartwell)
Date: 1999, Nov 23
From: David Hinds <dhinds@pcmcia.sourceforge.org>

If they were really NE2000 compatible, then the vendor would not need to distribute a modified driver. I've looked at the changes they've made, and they are substantial enough that they cannot be easily folded into the regular 8390/NE2000 driver. So, you are going to have to convince them to update their driver for later kernels. It is unlikely that the PCMCIA package will include support for these cards any time soon.

-- Dave

Idea AX88190 (Kingmax, PCMIA 10/100 Ethernet Card) on kernel 2.2.x

Re: Question Kingmax? PCMCIA 10/100 adapter (Nathan Hartwell)
Date: 2000, Jan 19
From: Thomas Pasch aanno

Hi,

I'v written to William Lee about the 2.2.x problem. 8390.c delivered with the card is for 2.0.x kernels. Not using the modified 8390.c will leed to a broken net connection (i.e. you can only ping to the net).

The response is perhaps interesting to everyone.

Hi,

 Mr. Dave Chavez send me the source code that's modified for Linux 2.2.x
 He announced the source file may compile and work properly.
 Maybe you could try somehow.

 William



----- Original Message -----
From: "Thomas Pasch" <Thomas.Pasch@e-technik.uni-magdeburg.de>
To: <william@asix.com.tw>
Sent: Wednesday, January 19, 2000 17:02
Subject: Linux AX88190 driver


> Dear William,
>
> I've recently bought a "PCMCIA 10/100 Ethernet Card" that cames with a
linux driver that was apparently written by you. It seem that the card
features a AX88190 chip. The driver - especially the 8390.c part - is a
modified version of a 2.0.36 linux kernel driver source file.
>
> As I run a 2.2.14 kernel on my laptops, I had problems even to compile
your source. There has been significant modifications of the 8390.c driver
from 2.0 to 2.2.
>
> If you still working on this subject and you try to port your changes to
the 2.2 kernels, I would really like to help you by testing the driver on my
laptop.
>
> Regards,
>
> Thomas
>
>
>
>
>



/* 8390.c: A general NS8390 ethernet driver core for linux. */
/*
  Written 1992-94 by Donald Becker.
  
  Copyright 1993 United States Government as represented by the
  Director, National Security Agency.

  This software may be used and distributed according to the terms
  of the GNU Public License, incorporated herein by reference.

  The author may be reached as becker@CESDIS.gsfc.nasa.gov, or C/O
  Center of Excellence in Space Data and Information Sciences
   Code 930.5, Goddard Space Flight Center, Greenbelt MD 20771
  
  This is the chip-specific code for many 8390-based ethernet adaptors.
  This is not a complete driver, it must be combined with board-specific
  code such as ne.c, wd.c, 3c503.c, etc.

  Seeing how at least eight drivers use this code, (not counting the
  PCMCIA ones either) it is easy to break some card by what seems like
  a simple innocent change. Please contact me or Donald if you think
  you have found something that needs changing. -- PG


  Changelog:

  Paul Gortmaker : remove set_bit lock, other cleanups.
  Paul Gortmaker : add ei_get_8390_hdr() so we can pass skb's to
       ei_block_input() for eth_io_copy_and_sum().
  Paul Gortmaker : exchange static int ei_pingpong for a #define,
       also add better Tx error handling.
  Paul Gortmaker : rewrite Rx overrun handling as per NS specs.

  William Lee: support the ASIX AX88190 Based Fast Ethernet PCMCIA Card.
  (william@asix.com.tw)


  Sources:
  The National Semiconductor LAN Databook, and the 3Com 3c503 databook.

  */

static const char *version =
    "8390.c:v1.10 9/23/94 Donald Becker (becker@cesdis.gsfc.nasa.gov)\n";

#include <linux/module.h>
#include <linux/kernel.h>
#include <linux/sched.h>
#include <linux/fs.h>
#include <linux/types.h>
#include <linux/ptrace.h>
#include <linux/string.h>
#include <asm/system.h>
#include <asm/segment.h>
#include <asm/bitops.h>
#include <asm/io.h>
#include <linux/errno.h>
#include <linux/fcntl.h>
#include <linux/in.h>
#include <linux/interrupt.h>

#include <linux/netdevice.h>
#include <linux/etherdevice.h>

#include "8390.h"

// These are the operational function interfaces to board-specific
// routines.
// void reset_8390(struct device *dev)
// Resets the board associated with DEV, including a hardware reset of
// the 8390. This is only called when there is a transmit timeout, and
// it is always followed by 8390_init().
// void block_output(struct device *dev, int count, const unsigned char *buf,
// int start_page)
// Write the COUNT bytes of BUF to the packet buffer at START_PAGE. The
// "page" value uses the 8390's 256-byte pages.
// void get_8390_hdr(struct device *dev, struct e8390_hdr *hdr, int ring_page)
// Read the 4 byte, page aligned 8390 header. *If* there is a
// subsequent read, it will be of the rest of the packet.
// void block_input(struct device *dev, int count, struct sk_buff *skb, int ring_offset)
// Read COUNT bytes from the packet buffer into the skb data area. Start
// reading from RING_OFFSET, the address as the 8390 sees it. This will always
// follow the read of the 8390 header.

#define ei_reset_8390 (ei_local->reset_8390)
#define ei_block_output (ei_local->block_output)
#define ei_block_input (ei_local->block_input)
#define ei_get_8390_hdr (ei_local->get_8390_hdr)

/* use 0 for production, 1 for verification, >2 for debug */
/* DEC - Removed this ifdef (problem defining 'ei_debug' - is it elsewhere?): */
/* #ifdef EI_DEBUG
int ei_debug = EI_DEBUG;
#else
int ei_debug = 1;
#endif
*/

/* Index to functions. */
static void ei_tx_intr(struct device *dev);
static void ei_tx_err(struct device *dev);
static void ei_receive(struct device *dev);
static void ei_rx_overrun(struct device *dev);

/* Routines generic to NS8390-based boards. */
static void NS8390_trigger_send(struct device *dev, unsigned int length,
                int start_page);
static void set_multicast_list(struct device *dev);


/* Open/initialize the board. This routine goes all-out, setting everything
   up anew at each open, even though many of these registers should only
   need to be set once at boot.
   */
int ei_open(struct device *dev)
{
    /* DEC - Added 'flags' needed by spin_[un]lock_irq functions: */
    unsigned long flags;

    struct ei_device *ei_local = (struct ei_device *) dev->priv;

    /* This can't happen unless somebody forgot to call ethdev_init(). */
    if (ei_local == NULL) {
  printk(KERN_EMERG "%s: ei_open passed a non-existent device!\n", dev->name);
  return -ENXIO;
    }
    
    /* DEC - Added spin_lock_irqsave() call: */
    spin_lock_irqsave(&ei_local->page_lock, flags);
    /* DEC - Deleted irq to dev map reference: */
    /* irq2dev_map[dev->irq] = dev; */
    NS8390_init(dev, 1);
    dev->start = 1;
    /* DEC - Added spin_unlock_irqrestore() call: */
    spin_unlock_irqrestore(&ei_local->page_lock, flags);
    ei_local->irqlock = 0;
    return 0;
}

/* Opposite of above. Only used when "ifconfig <devname> down" is done. */
int ei_close(struct device *dev)
{
    NS8390_init(dev, 0);
    dev->start = 0;
    return 0;
}

static int ei_start_xmit(struct sk_buff *skb, struct device *dev)
{
  int e8390_base = dev->base_addr;
  struct ei_device *ei_local = (struct ei_device *) dev->priv;
  int length, output_page;
  unsigned long flags;

  if (dev->start == 0) {
    printk("%s: xmit on stopped card\n", dev->name);
    return 1;
  }

// *
// * We normally shouldn't be called if dev->tbusy is set, but the
// * existing code does anyway. If it has been too long since the
// * last Tx, we assume the board has died and kick it.
// *
 
  if (dev->tbusy) { // Do timeouts, just like the 8003 driver.
    int txsr = inb(e8390_base+EN0_TSR), isr;
    int tickssofar = jiffies - dev->trans_start;

    if (tickssofar < TX_TIMEOUT || (tickssofar < (TX_TIMEOUT+5) && !(txsr & ENTSR_PTX)))
    {
      return 1;
    }
    isr = inb(e8390_base+EN0_ISR);

    //*
    //* Note that if the Tx posted a TX_ERR interrupt, then the
    //* error will have been handled from the interrupt handler.
    //* and not here.
    //*

    printk(KERN_DEBUG "%s: Tx timed out, %s TSR=%#2x, ISR=%#2x, t=%d.\n",
     dev->name, (txsr & ENTSR_ABT) ? "excess collisions." :
     (isr) ? "lost interrupt?" : "cable problem?", txsr, isr, tickssofar);

    if (!isr && !ei_local->stat.tx_packets) {
     // The 8390 probably hasn't gotten on the cable yet.
     ei_local->interface_num ^= 1; // Try a different xcvr.
    }

    // Try to restart. Perhaps the user has fixed something.
    ei_reset_8390(dev);
    NS8390_init(dev, 1);
    dev->trans_start = jiffies;
  }
    
  // Sending a NULL skb means some higher layer thinks we've missed an
  // tx-done interrupt. Caution: dev_tint() handles the cli()/sti() itself.

  if (skb == NULL) {
// dev_tint(dev);
    return 0;
  }
  if (skb->len <= 14 || skb->len >= 1518)
    return 0;

  length = skb->len;
// if (length < ETH_ZLEN) // AX88190 will auto-padding
// length = ETH_ZLEN; // the short packet

#ifdef EI_PINGPONG

  // Mask interrupts from the ethercard.
// outb_p(0x00, e8390_base + EN0_IMR);
// if (dev->interrupt) {
// printk("%s: Tx request while isr active.\n",dev->name);
// outb_p(ENISR_ALL, e8390_base + EN0_IMR);
// return 1;
// }
// ei_local->irqlock = 1;

  save_flags(flags);
  cli();

// *
// * We have two Tx slots available for use. Find the first free
// * slot, and then perform some sanity checks. With two Tx bufs,
// * you get very close to transmitting back-to-back packets. With
// * only one Tx buf, the transmitter sits idle while you reload the
// * card, leaving a substantial gap between each transmitted packet.

  if (!ei_local->txing)
  {
    if (ei_local->tx1 != 0)
      return 1;
    output_page = ei_local->tx_start_page;
    ei_block_output(dev, length, skb->data, output_page);
    ei_local->tx1 = length;
  }
  else
  {
    if (ei_local->tx2 != 0)
      return 1;
    output_page = ei_local->tx_start_page + TX_1X_PAGES;
    ei_block_output(dev, length, skb->data, output_page);
    ei_local->tx2 = length;
  }

/*
    if (ei_local->tx1 == 0) {
  output_page = ei_local->tx_start_page;
  ei_local->tx1 = length;
  if (ei_debug && ei_local->tx2 > 0)
    printk("%s: idle transmitter tx2=%d, lasttx=%d, txing=%d.\n",
      dev->name, ei_local->tx2, ei_local->lasttx, ei_local->txing);
    } else if (ei_local->tx2 == 0) {
  output_page = ei_local->tx_start_page + TX_1X_PAGES;
  ei_local->tx2 = length;
  if (ei_debug && ei_local->tx1 > 0)
    printk("%s: idle transmitter, tx1=%d, lasttx=%d, txing=%d.\n",
      dev->name, ei_local->tx1, ei_local->lasttx, ei_local->txing);
    } else { // We should never get here.
  if (ei_debug)
    printk("%s: No Tx buffers free! irq=%d tx1=%d tx2=%d last=%d\n",
      dev->name, dev->interrupt, ei_local->tx1, ei_local->tx2, ei_local->lasttx);
  dev->tbusy = 1;
// ei_local->irqlock = 0;
// outb_p(ENISR_ALL, e8390_base + EN0_IMR);
  return 1;
    }
*/

  //*
  //* Okay, now upload the packet and trigger a send if the transmitter
  //* isn't already sending. If it is busy, the interrupt handler will
  //* trigger the send later, upon receiving a Tx done interrupt.
  //*

  if (ei_local->lasttx == -1)
  {
    ei_local->lasttx = ei_local->txing;
    NS8390_trigger_send(dev, length, output_page);
    dev->trans_start = jiffies;
  }
  else
    dev->tbusy = 1;

  ei_local->txing ^= 1;

/*
    if (! ei_local->txing) {
  ei_local->txing = 1;
  NS8390_trigger_send(dev, length, output_page);
  dev->trans_start = jiffies;
  if (output_page == ei_local->tx_start_page) {
    ei_local->tx1 = -1;
    ei_local->lasttx = -1;
  } else {
    ei_local->tx2 = -1;
    ei_local->lasttx = -2;
  }
    } else
  ei_local->txqueue++;

    dev->tbusy = (ei_local->tx1 && ei_local->tx2);
*/

  // Turn 8390 interrupts back on.
// ei_local->irqlock = 0;
// outb_p(ENISR_ALL, e8390_base + EN0_IMR);

  restore_flags(flags);

#else // EI_PINGPONG

  //*
  //* Only one Tx buffer in use. You need two Tx bufs to come close to
  //* back-to-back transmits. Expect a 20 -> 25% performance hit on
  //* reasonable hardware if you only use one Tx buffer.
  //*

  ei_block_output(dev, length, skb->data, ei_local->tx_start_page);
  NS8390_trigger_send(dev, length, ei_local->tx_start_page);
  dev->trans_start = jiffies;
  dev->tbusy = 1;
// ei_local->txing = 1;

#endif /* EI_PINGPONG */

        /* DEC - Fixed (only one parameter to function call): */
  /* dev_kfree_skb (skb, FREE_WRITE); */
        dev_kfree_skb(skb);
    
  return 0;
}

/* The typical workload of the driver:
   Handle the ether interface interrupts. */
void ei_interrupt(int irq, void *dev_id, struct pt_regs * regs)
{
        /* DEC - Removed (data for 'dev' is passed in through 'dev_id'): */
  /* struct device *dev = (struct device *)(irq2dev_map[irq]); */

        struct device *dev = dev_id;
  int e8390_base;
  int interrupts;
// int nr_serviced = 0;
  struct ei_device *ei_local;
    
  if (dev == NULL) {
    printk ("net_interrupt(): irq %d for unknown device.\n", irq);
    return;
  }

  e8390_base = dev->base_addr;
  ei_local = (struct ei_device *) dev->priv;
  if (dev->interrupt) { // || ei_local->irqlock
    // The "irqlock" check is only for testing.
    printk(ei_local->irqlock
       ? "%s: Interrupted while interrupts are masked! isr=%#2x imr=%#2x.\n"
       : "%s: Reentering the interrupt handler! isr=%#2x imr=%#2x.\n",
       dev->name, inb_p(e8390_base + EN0_ISR),
       inb_p(e8390_base + EN0_IMR));
    return;
  }
  dev->interrupt = 1;

  if (ei_debug > 3)
    printk("%s: interrupt(isr=%#2.2x).\n", dev->name,
      inb_p(e8390_base + EN0_ISR));
    
  // Change to page 0 and read the intr status reg.
// outb_p(E8390_NODMA+E8390_PAGE0, e8390_base + E8390_CMD);
    
  // Mask interrupts from the ethercard.
  outb_p(0x00, e8390_base + EN0_IMR);
  ei_local->irqlock = 1;

  // !!Assumption!! -- we stay in page 0. Don't break this!
  while (
    ((interrupts = inb_p(e8390_base + EN0_ISR)) != 0)
// && (++nr_serviced < MAX_SERVICE)
    )
  {
    if (dev->start == 0) {
      printk("%s: interrupt from stopped card\n", dev->name);
      interrupts = 0;
      break;
    }
    outb_p(interrupts, e8390_base + EN0_ISR);
    while(inb(e8390_base + EN0_ISR) & interrupts) { //AX88190 Bug!
      outb_p(0, e8390_base + EN0_ISR);
      outb_p(interrupts, e8390_base + EN0_ISR);
    } //AX88190 Bug!
    if (interrupts & ENISR_OVER) {
      ei_rx_overrun(dev);
    } else if (interrupts & (ENISR_RX+ENISR_RX_ERR)) {
      // Got a good (?) packet.
      ei_receive(dev);
    }

    // Push the next to-transmit packet through.
    if (interrupts & ENISR_TX) {
      ei_tx_intr(dev);
    } else if (interrupts & ENISR_TX_ERR) {
      ei_tx_err(dev);
    }

    if (interrupts & ENISR_COUNTERS) {
      ei_local->stat.rx_frame_errors += inb_p(e8390_base + EN0_COUNTER0);
      ei_local->stat.rx_crc_errors += inb_p(e8390_base + EN0_COUNTER1);
      ei_local->stat.rx_missed_errors+= inb_p(e8390_base + EN0_COUNTER2);
    }
    
    // Ignore any RDC interrupts that make it back to here.
// if (interrupts & ENISR_RDC) {
// }

// outb_p(E8390_NODMA+E8390_PAGE0+E8390_START, e8390_base + E8390_CMD);
  }
/*
    if (interrupts && ei_debug) {
    outb_p(E8390_NODMA+E8390_PAGE0+E8390_START, e8390_base + E8390_CMD);
    if (nr_serviced >= MAX_SERVICE) {
      printk("%s: Too much work at interrupt, status %#2.2x\n",
         dev->name, interrupts);
      while(inb(e8390_base + EN0_ISR) & ENISR_ALL) {
        outb_p(0, e8390_base + EN0_ISR);
        outb_p(ENISR_ALL, e8390_base + EN0_ISR); // Ack. most intrs.
      }
    } else {
      printk("%s: unknown interrupt %#2x\n", dev->name, interrupts);
      while(inb(e8390_base + EN0_ISR) & 0x7f) {
        outb_p(0, e8390_base + EN0_ISR);
        outb_p(0x7f, e8390_base + EN0_ISR); // Ack. all intrs.
      }
    }
    }
*/
  // Turn 8390 interrupts back on.
  ei_local->irqlock = 0;
  outb_p(ENISR_ALL, e8390_base + EN0_IMR);

    dev->interrupt = 0;
    return;
}

/*
 * A transmitter error has happened. Most likely excess collisions (which
 * is a fairly normal condition). If the error is one where the Tx will
 * have been aborted, we try and send another one right away, instead of
 * letting the failed packet sit and collect dust in the Tx buffer. This
 * is a much better solution as it avoids kernel based Tx timeouts, and
 * an unnecessary card reset.
 */

static void ei_tx_err(struct device *dev)
{
    int e8390_base = dev->base_addr;
    unsigned char txsr = inb_p(e8390_base+EN0_TSR);
    unsigned char tx_was_aborted = txsr & (ENTSR_ABT+ENTSR_FU);
    struct ei_device *ei_local = (struct ei_device *) dev->priv;

#ifdef VERBOSE_ERROR_DUMP
    printk(KERN_DEBUG "%s: transmitter error (%#2x): ", dev->name, txsr);
    if (txsr & ENTSR_ABT)
    printk("excess-collisions ");
    if (txsr & ENTSR_ND)
    printk("non-deferral ");
    if (txsr & ENTSR_CRS)
    printk("lost-carrier ");
    if (txsr & ENTSR_FU)
    printk("FIFO-underrun ");
    if (txsr & ENTSR_CDH)
    printk("lost-heartbeat ");
    printk("\n");
#endif

    if (tx_was_aborted)
  ei_tx_intr(dev);

  //*
  //* Note: NCR reads zero on 16 collisions so we add them
  //* in by hand. Somebody might care...
  //*
  if (txsr & ENTSR_ABT)
    ei_local->stat.collisions += 16;
  
}

/* We have finished a transmit: check for errors and then trigger the next
   packet to be sent. */
static void ei_tx_intr(struct device *dev)
{
  int e8390_base = dev->base_addr;
  int status = inb(e8390_base + EN0_TSR);
  struct ei_device *ei_local = (struct ei_device *) dev->priv;
    
#ifdef EI_PINGPONG

  //*
  //* There are two Tx buffers, see which one finished, and trigger
  //* the send of another one if it exists.
  //*

  ei_local->lasttx ^= 1;
  if (!ei_local->lasttx)
  {
    ei_local->tx2 = 0;
    if (ei_local->tx1 != 0)
    {
      NS8390_trigger_send(dev, ei_local->tx1,
          ei_local->tx_start_page);
      dev->trans_start = jiffies;
    }
    else
      ei_local->lasttx = -1;
  }
  else
  {
    ei_local->tx1 = 0;
    if (ei_local->tx2 != 0)
    {
      NS8390_trigger_send(dev, ei_local->tx2,
          ei_local->tx_start_page + TX_1X_PAGES);
      dev->trans_start = jiffies;
    }
    else
      ei_local->lasttx = -1;
  }
  dev->tbusy = 0;


/*
    ei_local->txqueue--;
    if (ei_local->tx1 < 0) {
  if (ei_local->lasttx != 1 && ei_local->lasttx != -1)
    printk("%s: bogus last_tx_buffer %d, tx1=%d.\n",
       ei_local->name, ei_local->lasttx, ei_local->tx1);
  ei_local->tx1 = 0;
  dev->tbusy = 0;
  if (ei_local->tx2 > 0) {
    ei_local->txing = 1;
    NS8390_trigger_send(dev, ei_local->tx2, ei_local->tx_start_page + 6);
    dev->trans_start = jiffies;
    ei_local->tx2 = -1,
    ei_local->lasttx = 2;
  } else
    ei_local->lasttx = 20, ei_local->txing = 0;
    } else if (ei_local->tx2 < 0) {
  if (ei_local->lasttx != 2 && ei_local->lasttx != -2)
    printk("%s: bogus last_tx_buffer %d, tx2=%d.\n",
       ei_local->name, ei_local->lasttx, ei_local->tx2);
  ei_local->tx2 = 0;
  dev->tbusy = 0;
  if (ei_local->tx1 > 0) {
    ei_local->txing = 1;
    NS8390_trigger_send(dev, ei_local->tx1, ei_local->tx_start_page);
    dev->trans_start = jiffies;
    ei_local->tx1 = -1;
    ei_local->lasttx = 1;
  } else
    ei_local->lasttx = 10, ei_local->txing = 0;
    } else
  printk("%s: unexpected TX-done interrupt, lasttx=%d.\n",
     dev->name, ei_local->lasttx);
*/
#else // EI_PINGPONG
  // Single Tx buffer: mark it free so another packet can be loaded.

  dev->tbusy = 0;
// ei_local->txing = 0;
#endif

    // Minimize Tx latency: update the statistics after we restart TXing.
    if (status & ENTSR_COL)
  ei_local->stat.collisions++;
    if (status & ENTSR_PTX)
  ei_local->stat.tx_packets++;
    else {
  ei_local->stat.tx_errors++;
  if (status & ENTSR_ABT) ei_local->stat.tx_aborted_errors++;
  if (status & ENTSR_CRS) ei_local->stat.tx_carrier_errors++;
  if (status & ENTSR_FU) ei_local->stat.tx_fifo_errors++;
  if (status & ENTSR_CDH) ei_local->stat.tx_heartbeat_errors++;
  if (status & ENTSR_OWC) ei_local->stat.tx_window_errors++;
    }

    mark_bh (NET_BH);
}

// We have a good packet(s), get it/them out of the buffers.
static void ei_receive(struct device *dev)
{
    int e8390_base = dev->base_addr;
    struct ei_device *ei_local = (struct ei_device *) dev->priv;
    unsigned char rxing_page, this_frame, next_frame;
    unsigned short current_offset;
    struct e8390_pkt_hdr rx_frame;
    int num_rx_pages = ei_local->stop_page-ei_local->rx_start_page;
// int rx_pkt_count = 0;
    
// while (++rx_pkt_count < 10) {
  while (1) {
    int pkt_len;
    
    // Get the rx page (incoming packet pointer).
// outb_p(E8390_NODMA+E8390_PAGE1, e8390_base + E8390_CMD);
    rxing_page = inb_p(e8390_base + EN1_CURPAG -1); //AX88190
// outb_p(E8390_NODMA+E8390_PAGE0, e8390_base + E8390_CMD);
    
    // Remove one frame from the ring. Boundary is always a page behind.
    this_frame = inb_p(e8390_base + EN0_BOUNDARY) + 1;
    if (this_frame >= ei_local->stop_page)
      this_frame = ei_local->rx_start_page;
    
    // Someday we'll omit the previous, iff we never get this message.
    // (There is at least one clone claimed to have a problem.)
    if (ei_debug > 0 && this_frame != ei_local->current_page)
      printk("%s: mismatched read page pointers %2x vs %2x.\n",
         dev->name, this_frame, ei_local->current_page);
    
    if (this_frame == rxing_page) // Read all the frames?
      break; // Done for now
    
    current_offset = this_frame << 8;
    ei_get_8390_hdr(dev, &rx_frame, this_frame);
    
    pkt_len = rx_frame.count - sizeof(struct e8390_pkt_hdr);
    
    next_frame = this_frame + 1 + ((pkt_len+4)>>8);
/*
    // Check for bogosity warned by 3c503 book: the status byte is never
    // written. This happened a lot during testing! This code should be
    // cleaned up someday.
    if (rx_frame.next != next_frame
      && rx_frame.next != next_frame + 1
      && rx_frame.next != next_frame - num_rx_pages
      && rx_frame.next != next_frame + 1 - num_rx_pages) {
      ei_local->current_page = rxing_page;
      outb(ei_local->current_page-1, e8390_base+EN0_BOUNDARY);
      ei_local->stat.rx_errors++;
      continue;
    }
*/
    if (pkt_len < 60 || pkt_len > 1518) {
      if (ei_debug)
        printk("%s: bogus packet size: %d, status=%#2x nxpg=%#2x.\n",
           dev->name, rx_frame.count, rx_frame.status,
           rx_frame.next);
      ei_local->stat.rx_errors++;
    } else if ((rx_frame.status & 0x0F) == ENRSR_RXOK) {
      struct sk_buff *skb;
      
      skb = dev_alloc_skb(pkt_len+2);
      if (skb == NULL) {
        if (ei_debug > 1)
          printk("%s: Couldn't allocate a sk_buff of size %d.\n",
             dev->name, pkt_len);
        ei_local->stat.rx_dropped++;
        break;
      } else {
        skb_reserve(skb,2); /* IP headers on 16 byte boundaries */
        skb->dev = dev;
        skb_put(skb, pkt_len); /* Make room */
        ei_block_input(dev, pkt_len, skb, current_offset + sizeof(rx_frame));
        skb->protocol=eth_type_trans(skb,dev);
        netif_rx(skb);
        ei_local->stat.rx_packets++;
      }
    } else {
      int errs = rx_frame.status;
      if (ei_debug)
        printk("%s: bogus packet: status=%#2x nxpg=%#2x size=%d\n",
           dev->name, rx_frame.status, rx_frame.next,
           rx_frame.count);
      if (errs & ENRSR_FO)
        ei_local->stat.rx_fifo_errors++;
    }
    next_frame = rx_frame.next;

    // This _should_ never happen: it's here for avoiding bad clones.
    if (next_frame >= ei_local->stop_page) {
      printk("%s: next frame inconsistency, %#2x\n", dev->name,
         next_frame);
      next_frame = ei_local->rx_start_page;
    }
    ei_local->current_page = next_frame;
    outb_p(next_frame-1, e8390_base+EN0_BOUNDARY);
  }

// We used to also ack ENISR_OVER here, but that would sometimes mask
// a real overrun, leaving the 8390 in a stopped state with rec'vr off.
// while(inb(e8390_base + EN0_ISR) & (ENISR_RX+ENISR_RX_ERR)) {
// outb_p(0, e8390_base + EN0_ISR);
// outb_p(ENISR_RX+ENISR_RX_ERR, e8390_base+EN0_ISR);
// }

    return;
}

/*
 * We have a receiver overrun: we have to kick the 8390 to get it started
 * again. Problem is that you have to kick it exactly as NS prescribes in
 * the updated datasheets, or "the NIC may act in an unpredictable manner."
 * This includes causing "the NIC to defer indefinitely when it is stopped
 * on a busy network." Ugh.
 */
static void ei_rx_overrun(struct device *dev)
{
  int e8390_base = dev->base_addr;
  struct ei_device *ei_local = (struct ei_device *) dev->priv;
  unsigned long wait_start_time;
// unsigned char was_txing, must_resend = 0;
    
  ei_local->stat.rx_over_errors++;
  if (ei_debug > 1)
    printk("%s: Receiver overrun.\n", dev->name);
    
  //*
  //* Record whether a Tx was in progress and then issue the
  //* stop command.
  //*
// was_txing = inb_p(e8390_base+E8390_CMD) & E8390_TRANS;
  outb_p(E8390_NODMA+E8390_PAGE0+E8390_STOP, e8390_base+E8390_CMD);

  //*
  //* Wait a full Tx time (1.2ms) + some guard time, NS says 1.6ms total.
  //* Early datasheets said to poll the reset bit, but now they say that
  //* it "is not a reliable indicator and subsequently should be ignored."
  //* We wait at least 10ms.
  //*
// wait_start_time = jiffies;
// while (jiffies - wait_start_time <= 1*HZ/100)
// barrier();

  //*
  //* Reset RBCR[01] back to zero as per magic incantation.
  //*
// outb_p(0x00, e8390_base+EN0_RCNTLO);
// outb_p(0x00, e8390_base+EN0_RCNTHI);

  //*
  //* See if any Tx was interrupted or not. According to NS, this
  //* step is vital, and skipping it will cause no end of havoc.
  //*
// if (was_txing) {
// unsigned char tx_completed =
// inb_p(e8390_base+EN0_ISR) & (ENISR_TX+ENISR_TX_ERR);
//
// if (!tx_completed)
// must_resend = 1;
// }

  //*
  //* Have to enter loopback mode and then restart the NIC before
  //* you are allowed to slurp packets up off the ring.
  //*
  outb_p(E8390_TXOFF, e8390_base + EN0_TXCR);
  outb_p(E8390_NODMA +E8390_PAGE0 +E8390_START, e8390_base + E8390_CMD);

  //*
  //* Clear the Rx ring of all the debris, and ack the interrupt.
  //*
  ei_receive(dev);

  //*
  //* Leave loopback mode, and resend any packet that got stopped.
  //*
  outb_p(E8390_TXCONFIG, e8390_base + EN0_TXCR);

// if (must_resend)
// outb_p(E8390_NODMA +E8390_PAGE0 +E8390_START +E8390_TRANS, e8390_base + E8390_CMD);
  
}

static struct enet_statistics *get_stats(struct device *dev)
{
    short ioaddr = dev->base_addr;
    struct ei_device *ei_local = (struct ei_device *) dev->priv;
    
    /* If the card is stopped, just return the present stats. */
    if (dev->start == 0) return &ei_local->stat;

    /* Read the counter registers, assuming we are in page 0. */
    ei_local->stat.rx_frame_errors += inb_p(ioaddr + EN0_COUNTER0);
    ei_local->stat.rx_crc_errors += inb_p(ioaddr + EN0_COUNTER1);
    ei_local->stat.rx_missed_errors+= inb_p(ioaddr + EN0_COUNTER2);
    
    return &ei_local->stat;
}

/*
 * Set or clear the multicast filter for this adaptor.
 */
 
static void set_multicast_list(struct device *dev)
{
  short ioaddr = dev->base_addr;
    
  if(dev->flags&IFF_PROMISC)
  {
    outb_p(E8390_RXCONFIG |0x40 |0x18, ioaddr + EN0_RXCR);
  }
  else if((dev->flags&IFF_ALLMULTI)||dev->mc_list)
  {
    /* The multicast-accept list is initialized to accept-all, and we
     rely on higher-level filtering for now. */
    outb_p(E8390_RXCONFIG |0x40 |0x08, ioaddr + EN0_RXCR);
  }
  else
    outb_p(E8390_RXCONFIG |0x40, ioaddr + EN0_RXCR);
}

/* Initialize the rest of the 8390 device structure. */
int ethdev_init(struct device *dev)
{
    if (ei_debug > 1)
    printk(version);
    
    if (dev->priv == NULL) {
    struct ei_device *ei_local;
    
    dev->priv = kmalloc(sizeof(struct ei_device), GFP_KERNEL);
    if (dev->priv == NULL)
      return -ENOMEM;
    memset(dev->priv, 0, sizeof(struct ei_device));
    ei_local = (struct ei_device *)dev->priv;
    }
    
    dev->hard_start_xmit = &ei_start_xmit;
    dev->get_stats = get_stats;
    dev->set_multicast_list = &set_multicast_list;

    ether_setup(dev);
        
    return 0;
}


// This page of functions should be 8390 generic
// Follow National Semi's recommendations for initializing the "NIC".
void NS8390_init(struct device *dev, int startp)
{
    int e8390_base = dev->base_addr;
    struct ei_device *ei_local = (struct ei_device *) dev->priv;
    int i;
    int endcfg = ei_local->word16 ? (0x48 | ENDCFG_WTS) : 0x48;
    unsigned long flags;
    
    // Follow National Semi's recommendations for initing the DP83902.
    outb_p(E8390_NODMA+E8390_PAGE0+E8390_STOP, e8390_base); // 0x21
    outb_p(endcfg, e8390_base + EN0_DCFG); // 0x48 or 0x49
    // Clear the remote byte count registers.
    outb_p(0x00, e8390_base + EN0_RCNTLO);
    outb_p(0x00, e8390_base + EN0_RCNTHI);
    // Set to monitor and loopback mode -- this is vital!.
    outb_p(E8390_RXOFF |0x40, e8390_base + EN0_RXCR); // 0x20
    outb_p(E8390_TXOFF, e8390_base + EN0_TXCR); // 0x02
    // Set the transmit page and receive ring.
    outb_p(ei_local->tx_start_page, e8390_base + EN0_TPSR);
    outb_p(ei_local->rx_start_page, e8390_base + EN0_STARTPG);
    outb_p(ei_local->stop_page-1, e8390_base + EN0_BOUNDARY); // 3c503 says 0x3f,NS0x26
    ei_local->current_page = ei_local->rx_start_page; // assert boundary+1
    outb_p(ei_local->stop_page, e8390_base + EN0_STOPPG);
    // Clear the pending interrupts and mask.
    outb_p(0xFF, e8390_base + EN0_ISR);
    outb_p(0x00, e8390_base + EN0_IMR);
    
    save_flags(flags);
    cli();
    outb_p(E8390_NODMA + E8390_PAGE1 + E8390_STOP, e8390_base); // 0x61

    // Copy the station address into the DS8390 registers,
    // and set the multicast hash bitmap to receive all multicasts.
    for(i = 0; i < 6; i++)
    outb_p(dev->dev_addr[i], e8390_base + EN1_PHYS + i);
    // Initialize the multicast list to accept-all. If we enable multicast
    // the higher levels can do the filtering.
    for(i = 0; i < 8; i++)
    outb_p(0xff, e8390_base + EN1_MULT + i);
    
    outb_p(ei_local->rx_start_page, e8390_base + EN1_CURPAG);
    outb_p(E8390_NODMA+E8390_PAGE0+E8390_STOP, e8390_base);
    restore_flags(flags);

  ei_local->txing = ei_local->tx1 = ei_local->tx2 = 0;
  ei_local->lasttx = -1;
  dev->interrupt = 0;
  dev->tbusy = 0;

    if (startp) {
    outb_p(0xff, e8390_base + EN0_ISR);
    outb_p(ENISR_ALL, e8390_base + EN0_IMR);
    outb_p(E8390_NODMA+E8390_PAGE0+E8390_START, e8390_base);
    outb_p(E8390_TXCONFIG, e8390_base + EN0_TXCR); /* xmit on. */
    /* 3c503 TechMan says rxconfig only after the NIC is started. */
    outb_p(E8390_RXCONFIG |0x40, e8390_base + EN0_RXCR); /* rx on, */
    dev->set_multicast_list(dev); /* Get the multicast status right if this
               was a reset. */
    }
    return;
}

/* Trigger a transmit start, assuming the length is valid. */
static void NS8390_trigger_send(struct device *dev, unsigned int length,
                int start_page)
{
  int e8390_base = dev->base_addr;

// outb_p(E8390_NODMA+E8390_PAGE0, e8390_base);

  if (inb_p(e8390_base) & E8390_TRANS) {
    printk("%s: trigger_send() called with the transmitter busy.\n",
      dev->name);
    return;
  }
  outb_p(length & 0xff, e8390_base + EN0_TCNTLO);
  outb_p(length >> 8, e8390_base + EN0_TCNTHI);
  outb_p(start_page, e8390_base + EN0_TPSR);
  outb_p(E8390_NODMA+E8390_TRANS+E8390_START, e8390_base);
  return;
}

#ifdef MODULE

int init_module(void)
{
     return 0;
}

void
cleanup_module(void)
{
}
#endif /* MODULE */



/*
 * Local variables:
 * compile-command: "gcc -D__KERNEL__ -I/usr/src/linux/net/inet -Wall -Wstrict-prototypes -O6 -m486 -c 8390.c"
 * version-control: t
 * kept-new-versions: 5
 * c-indent-level: 4
 * tab-width: 4
 * End:
 */

None Compex/ReadyLINK 10Mbps Ethernet card: kernel `Oops' on insert

Date: 1999, Nov 08
From: David dbutler

Hi,

When I inserted a Compex/ReadyLINK 10Mbps Ethernet card
 in to a   Sony Vaio  notebook 
(Kernel 2.2.12, PCMCIA package 3.0.14)  (same problem with a 
Winbook XL - Linux Kernel 2.2.13, PCMCIA package 3.0.14), 
the kernel gave the following error mesage 

'Unable to handle kernel NULL pointer dereference ...'

Also, the kernel reports an `Oops' caused by the card manager.

I'd be happy to hear any advice.

thanks in advance,

david

None Re: Compex/ReadyLINK 10Mbps Ethernet card: kernel `Oops' on insert

Re: None Compex/ReadyLINK 10Mbps Ethernet card: kernel `Oops' on insert (David)
Date: 1999, Nov 08
From: David Hinds <dhinds@pcmcia.sourceforge.org>

There are a couple of bogus entries in the 3.0.14 /etc/pcmcia/config:
some cards that use the tulip_cb driver also happen to have the same
product ID as your card, and as a result, this Cardbus driver is being
loaded for your 16-bit card.

Go into /etc/pcmcia/config, and find the entries for manfid 0x8a01,
0x0100 that specify the "tulip_cb" driver, and comment them out.

-- Dave

Sad upgrading PCMCIA 3.1.1 to 3.1.2 or 3.1.3 breaks certain network adapters

Date: 1999, Nov 10
From: Patrick Hildenbrand patrick

Hi, it seams that with kernel version 2.2.13 going from 3.1.1 to 3.1.2 the following adapters will no longer work correctly:
  • IBM Ethernet Adapter II (pcnet_cs)
    various error messags on high network utilization, UDP transport not reliable (ex. host will sometimes not work, doing a tcpdump, I could see that the data gets send out, the answer returned but the system will not show the response. TCP connections are slow but work (specifiying the ip-adress).
  • Level One EPC-0100TB (pcnet_cs)
    no conectivity at all, the card gets detected and configured, eth0 is available but nothing (ping, tcp, udp) works.

going from 3.1.1 to 3.1.3 the same applies as above and in addition the IBM Etherjet cardbus adapter (tulip_cb) will no longer work. Same symptoms as for the Level One adapter. I did not try other adapters so far besides a 4lan EP100 ethernet adapter (also pcnet_cs) which just works as it has been.

The configuration had not been changed between the different test. Reinstalling the old pcmcia version did in all cases cure the problem. Hardware are IBM Thinkpad 760 and 770. TokenRing is not affected.

Anybody any hints ?

I will try to dig a bit more as I have time.

Ok Fixed

Re: Sad upgrading PCMCIA 3.1.1 to 3.1.2 or 3.1.3 breaks certain network adapters (Patrick Hildenbrand)
Date: 1999, Dec 06
From: Patrick Hildenbrand patrick

The current beta for 3.1.6 works again.

Thanks to David :-)

Question Keep receiving "register_netdev( ) failed: try again

Date: 1999, Nov 13
From: Al Charpentier Charpy

I have a WinBook XP5, Pentium 75, 16mb, 720mb. Slackware Linux, kernel v2.2.6 I am attempting to use a 3COM 3C589D PCMCIA Card.

Here's the output:

Nov 13 08:55:24 sys0 kernel: Linux PCMCIA Card Services 3.0.9 
Nov 13 08:55:24 sys0 kernel:   kernel build: 2.2.6 #20 Sat Apr 17 23:17:12 CDT 1999 
Nov 13 08:55:24 sys0 kernel:   options:  [pci] [cardbus] 
Nov 13 08:55:24 sys0 kernel: Intel PCIC probe:  
Nov 13 08:55:24 sys0 kernel:   Vadem VG-469 ISA-to-PCMCIA at port 0x3e0 ofs 0x00, 2 sockets 
Nov 13 08:55:24 sys0 kernel:     host opts [0]: none 
Nov 13 08:55:24 sys0 kernel:     host opts [1]: none 
Nov 13 08:55:24 sys0 kernel:     ISA irqs (default) = 3,4,5,7,9,10,11,12,15 polling interval = 1000 ms 
Nov 13 08:55:24 sys0 kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x110-0x117 0x268-0x26f 0x400-0x40f 0x420-0x427 0x440-0x447 0x460-0x467 0x480-0x497 0x4a0-0x4a7 0x4c0-0x4d7 0x4f0-0x4f7 
Nov 13 08:55:24 sys0 kernel: cs: memory probe 0x0d0000-0x0dffff: clean. 
Nov 13 08:55:24 sys0 kernel: 3c589_cs: register_netdev() failed 
Nov 13 09:01:26 sys0 login[111]: ROOT LOGIN on `tty1'
Nov 13 09:01:35 sys0 cardmgr[53]: shutting down socket 0
Nov 13 09:01:35 sys0 cardmgr[53]: executing: 'rmmod 3c589_cs'
Nov 13 09:01:39 sys0 cardmgr[53]: initializing socket 0
Nov 13 09:01:39 sys0 cardmgr[53]: socket 0: 3Com 3c589D Ethernet
Nov 13 09:01:39 sys0 cardmgr[53]: executing: 'insmod /lib/modules/2.2.6/pcmcia/3c589_cs.o'
Nov 13 09:01:39 sys0 kernel: 3c589_cs: register_netdev() failed 
Nov 13 09:01:40 sys0 cardmgr[53]: get dev info on socket 0 failed: Try again
Nov 13 09:01:47 sys0 cardmgr[53]: shutting down socket 0
Nov 13 09:01:47 sys0 cardmgr[53]: executing: 'rmmod 3c589_cs'

As you can see, PCMCIA services work fine (I have a 56k modem card that works perfectly). The 3COM is detected, however when the following is ran: insmod /lib/modules/2.2.6/pcmcia/c3589_cs.o I get: 3c589_cs: register_netdev() failed get dev info on socket 0 failed: Try again

I have attempted to exclude different io port and memory settings. The only other thing I have received is:

cs: IO port probe 0x0300-0x03ff: clean. 
cs: memory probe 0x0d0000-0x0dffff: clean. 
3c589_cs: RequestIRQ: Resource in use

I have even placed: PCIC_OPTS="do_scan=0" to disable IRQ scanning.

The card works well in other laptops running Win95/98.

Any suggestions? Thanx!

Question Nobody has any input?

Re: Question Keep receiving "register_netdev( ) failed: try again (Al Charpentier)
Date: 1999, Nov 20
From: Al Charpentier Charpy

No suggestions at all?

None I feel your pain....

Re: Question Nobody has any input? (Al Charpentier)
Date: 1999, Nov 21
From: Nathan Hartwell MageX

I too have posted a message looking for assistance. Have you considered installing the latest PCMCIA support? I noticed you were using 3.0.x and wondered if by chance the 3.1.x series corrected your troubles.

Note This is an unusual message

Re: Question Keep receiving "register_netdev( ) failed: try again (Al Charpentier)
Date: 1999, Nov 23
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I'm not really sure how to interpret this message in this context, and I haven't seen it before. You're using a somewhat uncommon choice of kernel (2.2.6)... which makes me wonder if there is something odd about your kernel configuration, but I'm not sure how that could cause this problem.

-- Dave

None register_netdev( ) failed: try again

Re: Note This is an unusual message (David Hinds)
Date: 1999, Nov 25
From: Al Charpentier Charpy

David, this is the kernel that comes with Slackware v4.0. I have noticed that Slackware v7.0 is now available (skipping 5.0 and 6.0).

I intend to upgrade the PCMCIA support version from 3.0.9 to 3.1.x (as sugggested by Nathan). IF that doesn't work, then I will get Slackware v7.0, which uses kernel 2.2.13.

To the best of my knowledge, it appears to be a IO Port or MemoryAddress or even IRQ problem. I have tried various settings, and have basically received the same error.

Question D-Link DFE-660 Problems

Date: 1999, Nov 15
From: <mike@enoch.org>

 I made the mistake of buying a D-Link DFE-660 rather than the
 650, which I should have purchased.  The 660 is listed as
 experimental, and in my case, it doesn't work.  The card is
 identified, but it does not work.  I can ping the IP of eth0,
 but not of my default router.  Swapping to a 3Com card I have
 laying around works just fine (I'm using it now).  So, here's
 the specifics:
IBM Thinkpad 1552
D-Link DFE-660
Kernel 2.2.13 (International version)
Linux PCMCIA Card Services 3.1.4
  kernel build: 2.2.13 #1 Sun Nov 14 23:59:00 EST 1999
  options:  [pci] [cardbus] [apm]
Intel PCIC probe: 
  O2Micro OZ6832/OZ6833 PCI-to-CardBus at bus 0 slot 19, mem 0x68000000, 2 sockets
    host opts [0]: [a 44] [b a1] [c 20] [d 06] [mhpg 18] [fifo 00] [e 28] [no pci irq] [lat 32/176] [bus 32/34]
    host opts [1]: [a 44] [b ad] [c 20] [d 06] [mhpg 18] [fifo 00] [e 28] [no pci irq] [lat 32/176] [bus 35/37]
    ISA irqs (default) = 3,4,7,11,12 polling interval = 1000 ms
cs: IO port probe 0x1000-0x17ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x3b8-0x3df 0x408-0x40f 0x480-0x48f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: clean.

And when I insert the DFE-660:

Nov 15 00:46:15 mib kernel: cs: cb_alloc(bus 35): vendor 0x1011, device 0x0019 
Nov 15 00:46:15 mib cardmgr[351]: initializing socket 1
Nov 15 00:46:15 mib cardmgr[351]: socket 1: Linksys EtherFast 10/100
Nov 15 00:46:15 mib cardmgr[351]: executing: 'insmod /lib/modules/2.2.13/pcmcia/cb_enabler.o'
Nov 15 00:46:15 mib cardmgr[351]: executing: 'insmod /lib/modules/2.2.13/pcmcia/tulip_cb.o'
Nov 15 00:46:15 mib kernel: cs: cb_config(bus 35) 
Nov 15 00:46:15 mib kernel:   fn 0 bar 1: io 0xa00-0xa7f 
Nov 15 00:46:15 mib kernel:   fn 0 bar 2: mem 0xa0081000-0xa00813ff 
Nov 15 00:46:15 mib kernel:   fn 0 rom: mem 0xa0041000-0xa0080fff 
Nov 15 00:46:15 mib kernel: tulip_attach(bus 35, function 0) 
Nov 15 00:46:15 mib kernel: tulip.c:v0.91 4/14/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford) 
Nov 15 00:46:15 mib kernel: eth0: Digital DS21143 Tulip rev 65 at 0xa00, 00:80:C8:BA:DF:BD, IRQ 3. 
Nov 15 00:46:15 mib kernel: eth0:  EEPROM default media type Autosense. 
Nov 15 00:46:15 mib kernel: eth0:  Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block. 
Nov 15 00:46:15 mib kernel: eth0:  MII transceiver #0 config 3000 status 7809 advertising 01e1. 
Nov 15 00:46:15 mib cardmgr[351]: executing: './network start eth0'
Nov 15 00:46:21 mib kernel: eth0: Setting full-duplex based on MII#0 link partner capability of 4061. 
Nov 15 00:46:21 mib kernel: eth0: Tx hung, 9 vs. 0. 

It's the last line that seems to be the problem. I've seen 10 vs 0 and 7 vs 0, sometimes in sequence.

/sbin/cardctl ident
Socket 0:
  product info: "D-Link", "DFE-660", "CardBus Ethernet", "10/100"
  manfid: 0x0149, 0x0231
  function: 6 (network)

The card also didn't work with pcmcia-cs-3.0.14, which was why I tried 3.1.4.

So, um, is there anything I can do, short of buying a new card (I can't take this one back)? Any more debugging messages I can add?

Thanks, Mike

None Re: Question: D-Link DFE-660 Problems

Re: Question D-Link DFE-660 Problems
Date: 1999, Nov 15
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Try the following:

-- build the 3.1.4 drivers with "PnP BIOS support" enabled.
-- In /etc/sysconfig/pcmcia, set:

   PCIC_OPTS="pci_int=1 pci_csc=1"

-- Dave

None It works! Great!

Re: None Re: Question: D-Link DFE-660 Problems (David Hinds)
Date: 1999, Nov 16
From: <mike@enoch.org>

Thanks David! It works now!

Out of curioisity, what did those options do? In the HOWTO, I only saw mention of pci_csc. The HOWTO says that using "pci_csc=1" selects a PCI interrupt (if available) for card status change. Is this selecting interrupt 1, or setting a flag that tells the PCMCIA driver to select a PCI interrupt? And what does pci_int=1 do? I couldn't find any documentation on it.

Thanks, Mike

None They're documented in the man page

Re: None It works! Great!
Date: 1999, Nov 16
From: David Hinds <dhinds@pcmcia.sourceforge.org>

See "man i82365" for a description of each of the options.

-- Dave

None Re: They're documented in the man page

Re: None They're documented in the man page (David Hinds)
Date: 1999, Nov 16
From: Mike Johnson <mike@enoch.org>

On Mon, 15 Nov 1999, David Hinds wrote:

> If you reply to this message at HyperNews@pcmcia.sourceforge.org, include:
> In-Reply-To: <19991115180809.A17751@valinux.com>
> 
> See "man i82365" for a description of each of the options.

Gotchya.  Thanks.  Reading now.
 
> -- Dave

Mike

Question Destination Host Unreachable

Date: 1999, Nov 15
From: David Walden Walden

I have installed RedHat 6.1 on my Mitac 6020 with no problems except my Wisecom PC400 PCMCIA network card doesn't seem to be talking to the network. I am able to ping the card itself and when netstat -r is run the default gateway is shown, but I am still unable to ping anything on the network. I keep getting a response "Destination Host UnReachable". Does anyone have any suggestions?

None Network unreachable == routing problem

Re: Question Destination Host Unreachable (David Walden)
Date: 1999, Nov 15
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Your "netstat -r" may show a route to your gateway, but there must still be a problem with your routing info. "Network unreachable" always means a routing problem. Perhaps your gateway address isn't on the same subnet as your own IP address. If you can't sort it out, post the actual "netstat -rn" output.

-- Dave

None RE: Network unreachable == routing problem

Re: None Network unreachable == routing problem (David Hinds)
Date: 1999, Nov 17
From: David Walden Walden

Here is my routing table. To me everything works fine.

Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
195.175.107.118 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
195.175.107.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 195.175.107.65 0.0.0.0 UG 0 0 0 eth0

None Another view on this problem

Re: None RE: Network unreachable == routing problem (David Walden)
Date: 2000, Jan 05
From: John Jervis JohnJ

I don't agree that "network unreachable" is *always* due to routing problems, though this is the common reason. My Olicom GoCard multifunction eth/modem card gives this, but /var/log/messages shows the following when pinging an external address (i.e. not itself):

<date> <node> kernel: eth0: timeout waiting for Tx RDC.
<date> <node> kernel: eth0: pcnet_reset_8390() did not complete

and repeats this ad infinitum.

Is this why the Olicom card is no longer in the latest list of supported cards?

Question Intel EtherExpress PRO/100 Cardbus 32

Date: 1999, Nov 17
From: Mike Rudgyard MikeR

Hi,

I am trying to get the above card working on my Dell Latitude machine with the latest tulip driver and pcmcia-cs-3.1.4.

According to the supported cards, this should work. Indeed the
network comes up, and the light on the card comes on:

Nov 17 14:28:51 rock kernel: cs: cb_alloc(bus 35): vendor 0x1011, device 0x0019
Nov 17 14:28:51 rock cardmgr[360]: initializing socket 1
Nov 17 14:28:51 rock cardmgr[360]: socket 1: Intel EtherExpress PRO/100 CardBus Mobile Adapter32
Nov 17 14:28:51 rock cardmgr[360]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/cb_enabler.o'
Nov 17 14:28:51 rock cardmgr[360]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/tulip_cb.o'
Nov 17 14:28:51 rock kernel: cs: cb_config(bus 35)
Nov 17 14:28:51 rock kernel:   fn 0 bar 1: io 0x100-0x17f
Nov 17 14:28:51 rock kernel:   fn 0 bar 2: mem 0x60081000-0x6008107f
Nov 17 14:28:51 rock kernel:   fn 0 rom: mem 0x60041000-0x60080fff
Nov 17 14:28:51 rock kernel: tulip_attach(bus 35, function 0)
Nov 17 14:28:51 rock kernel: tulip.c:v0.91 4/14/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
Nov 17 14:28:51 rock kernel: eth0: Digital DS21143 Tulip rev 48 at 0x100, EEPROM not present, 00:4C:69:6E:75:79, IRQ 3.
Nov 17 14:28:51 rock cardmgr[360]: executing: './network start eth0'
Nov 17 14:28:52 rock modprobe: can't locate module block-major-22




As it points out, there is no EEPROM present in the card, which I presume is why I can't actually send or receive any
packets. If I use the tulip-diag tool, doing tulip-diag -ee
then I get:

ulip-diag.c:v1.19 10/2/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Index #1: Found a Digital DS21143 Tulip adapter at 0x60081000.
 Port selection is 100mbps-SYM/PCS 100baseTx scrambler, full-duplex.
 Transmit started, Receive started, full-duplex.
  The Rx process state is 'Transferring Rx frame into memory'.
  The Tx process state is 'Closing Tx descriptor'.
  PCI bus error!: Unknown 7.
  The transmit unit is set to store-and-forward.
 Interrupt sources are pending!  CSR5 is ffffffff.
   Tx done indication.
   Tx complete indication.
   Tx out of buffers indication.
   Transmit Jabber indication.
   Link passed indication.
   Tx FIFO Underflow indication.
   Rx Done indication.
   Receiver out of buffers indication.
   Receiver stopped indication.
   Receiver jabber indication.
   Link changed indication.
   Timer expired indication.
   Link failed indication.
   PCI bus error indication.
   Early Rx indication.
  The NWay status register is ffffffff.
EEPROM size is 8.
WARNING: The EEPROM is missing or erased!
 This interface is missing the EEPROM.
  This is likely the non-primary interface on a multiport board.
EEPROM contents:
  ffff ffff ffff ffff ffff ffff ffff ffff
  ffff ffff ffff ffff ffff ffff ffff ffff
  ffff ffff ffff ffff ffff ffff ffff ffff
  ffff ffff ffff ffff ffff ffff ffff ffff
  ffff ffff ffff ffff ffff ffff ffff ffff
  ffff ffff ffff ffff ffff ffff ffff ffff
  ffff ffff ffff ffff ffff ffff ffff ffff
  ffff ffff ffff ffff ffff ffff ffff ffff
 ID block CRC 0xfa (vs. 0xff).
  Full contents CRC 0x6a15 (read as 0xffff).
  Internal autonegotiation state is 'Invalid state'.


Unfortunately, I can't find any details of how to program the 
EEPROM (although I can see that the above program can be used to do this...).

Has anyone any ideas ??

Thanks,

Mike

None The EEPROM isn't the problem

Re: Question Intel EtherExpress PRO/100 Cardbus 32 (Mike Rudgyard)
Date: 1999, Nov 17
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The EEPROM is not the problem: the driver isn't talking to the card at
all.  Everything is reading back as ff's.  The EEPROM message is just
one of several complaints.

I think I'd first want to see the PCMCIA messages preceeding this
(they say what kind of CardBus bridge this is, what kernel version and
PCMCIA driver version you're using, etc).

-- Dave

Question More info...

Re: Question Intel EtherExpress PRO/100 Cardbus 32 (Mike Rudgyard)
Date: 1999, Nov 18
From: Mike Rudgyard MikeR

Red Hat 6.1 Kernel 2.2.12 tulip.c:v0.91g 7/16/99 pcmcia-cs-3.1.4

Here's what I get in /var/log/messages again:

Nov 18 10:52:43 rock last message repeated 19 times
Nov 18 10:52:44 rock cardmgr[360]: initializing socket 1
Nov 18 10:52:44 rock cardmgr[360]: socket 1: Intel EtherExpress PRO/100 CardBus Mobile Adapter32
Nov 18 10:52:44 rock kernel: cs: cb_alloc(bus 35): vendor 0x1011, device 0x0019
Nov 18 10:52:44 rock cardmgr[360]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/cb_enabler.o'
Nov 18 10:52:44 rock cardmgr[360]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/tulip_cb.o'
Nov 18 10:52:44 rock kernel: cs: cb_config(bus 35)
Nov 18 10:52:44 rock kernel:   fn 0 bar 1: io 0x100-0x17f
Nov 18 10:52:44 rock kernel:   fn 0 bar 2: mem 0x60081000-0x6008107f
Nov 18 10:52:44 rock kernel:   fn 0 rom: mem 0x60041000-0x60080fff
Nov 18 10:52:44 rock kernel: tulip_attach(bus 35, function 0)
Nov 18 10:52:44 rock kernel: tulip.c:v0.91 4/14/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
Nov 18 10:52:44 rock kernel: eth0: Digital DS21143 Tulip rev 48 at 0x100, EEPROM not present, 00:4C:69:6E:75:79, IRQ 3.
Nov 18 10:52:44 rock cardmgr[360]: executing: './network start eth0'
Nov 18 10:52:45 rock modprobe: can't locate module block-major-22

Here's what I get with another 3COM card (that works fine...):

Nov 18 10:52:17 rock last message repeated 53 times
Nov 18 10:52:18 rock cardmgr[360]: initializing socket 1
Nov 18 10:52:18 rock cardmgr[360]: socket 1: 3Com 3CCFE575B/3CXFE575B Fast EtherLink XL
Nov 18 10:52:18 rock kernel: cs: cb_alloc(bus 35): vendor 0x10b7, device 0x5157
Nov 18 10:52:18 rock cardmgr[360]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/cb_enabler.o'
Nov 18 10:52:18 rock cardmgr[360]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/3c575_cb.o'
Nov 18 10:52:18 rock kernel: 3c59x.c:v0.99L 5/28/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
Nov 18 10:52:18 rock kernel: cs: cb_config(bus 35)
Nov 18 10:52:18 rock kernel:   fn 0 bar 1: io 0x100-0x17f
Nov 18 10:52:18 rock kernel:   fn 0 bar 2: mem 0x60021000-0x6002107f
Nov 18 10:52:18 rock kernel:   fn 0 bar 3: mem 0x60020000-0x6002007f
Nov 18 10:52:18 rock kernel:   fn 0 rom: mem 0x60000000-0x6001ffff
Nov 18 10:52:18 rock kernel: vortex_attach(bus 35, function 0, device 5157)
Nov 18 10:52:18 rock kernel: eth0: 3Com 3CCFE575 Cyclone CardBus at 0x100,  00:50:04:5b:b0:b9, IRQ 3
Nov 18 10:52:18 rock kernel: eth0: CardBus functions mapped 60020000->c8073000
Nov 18 10:52:18 rock kernel:   8K byte-wide RAM 5:3 Rx:Tx split, MII interface.
Nov 18 10:52:18 rock kernel:   MII transceiver found at address 0, status 7809.
Nov 18 10:52:18 rock kernel:   Enabling bus-master transmits and whole-frame receives.
Nov 18 10:52:18 rock cardmgr[360]: executing: './network start eth0'
Nov 18 10:52:18 rock modprobe: can't locate module block-major-22
Nov 18 10:52:21 rock last message repeated 5 times
Nov 18 10:52:21 rock kernel: eth0: Setting full-duplex based on MII #0 link partner capability of 41e1.
Nov 18 10:52:22 rock modprobe: can't locate module block-major-22   

Here's what tulip-diag gives:

[root@rock incoming]# tulip-diag
tulip-diag.c:v1.19 10/2/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Index #1: Found a Digital DS21143 Tulip adapter at 0x60081000.
 Port selection is 100mbps-SYM/PCS 100baseTx scrambler, full-duplex.
 Transmit started, Receive started, full-duplex.
  The Rx process state is 'Transferring Rx frame into memory'.
  The Tx process state is 'Closing Tx descriptor'.
  PCI bus error!: Unknown 7.
  The transmit unit is set to store-and-forward.
 Interrupt sources are pending!  CSR5 is ffffffff.
   Tx done indication.
   Tx complete indication.
   Tx out of buffers indication.
   Transmit Jabber indication.
   Link passed indication.
   Tx FIFO Underflow indication.
   Rx Done indication.
   Receiver out of buffers indication.
   Receiver stopped indication.
   Receiver jabber indication.
   Link changed indication.
   Timer expired indication.
   Link failed indication.
   PCI bus error indication.
   Early Rx indication.
  The NWay status register is ffffffff.
WARNING: The EEPROM is missing or erased!
  Internal autonegotiation state is 'Invalid state'.
 Use '-a' or '-aa' to show device registers,
     '-e' to show EEPROM contents, -ee for parsed contents,
  or '-m' or '-mm' to show MII management registers.  

Since it tells me there is a PCI bus error, here's some info on the PCI devices on Dell Latitude CPi (with the EtherExpress card in....)

PCI devices found:
  Bus 35, device   0, function  0:
    Ethernet controller: DEC DC21142 (rev 48).
      Medium devsel.  Fast back-to-back capable.  IRQ 3.
      Non-prefetchable 32 bit memory at 0x100 [0x100].
      Non-prefetchable 32 bit memory at 0x60081000 [0x60081000].
  Bus  0, device   0, function  0:
    Host bridge: Intel 440BX - 82443BX Host (no AGP) (rev 2).
      Medium devsel.  Master Capable.  Latency=32.
      Prefetchable 32 bit memory at 0xd0000000 [0xd0000008].
  Bus  0, device   2, function  0:
    VGA compatible controller: Neomagic MagicGraph NM2160 (rev 1).
      Medium devsel.  Fast back-to-back capable.  IRQ 11.  Master Capable.  Latency=32.  Min Gnt=16.Max Lat=255.
      Prefetchable 32 bit memory at 0xe1000000 [0xe1000008].
      Non-prefetchable 32 bit memory at 0xfde00000 [0xfde00000].
      Non-prefetchable 32 bit memory at 0xfdd00000 [0xfdd00000].
  Bus  0, device   3, function  0:
    CardBus bridge: Texas Instruments PCI1131 (rev 1).
      Medium devsel.  IRQ 11.  Master Capable.  Latency=32.  Min Gnt=192.Max Lat=7.
  Bus  0, device   3, function  1:
    CardBus bridge: Texas Instruments PCI1131 (rev 1).
      Medium devsel.  IRQ 11.  Master Capable.  Latency=32.  Min Gnt=128.Max Lat=7.
  Bus  0, device   7, function  0:
    Bridge: Intel 82371AB PIIX4 ISA (rev 1).
      Medium devsel.  Fast back-to-back capable.  Master Capable.  No bursts.
  Bus  0, device   7, function  1:
    IDE interface: Intel 82371AB PIIX4 IDE (rev 1).
      Medium devsel.  Fast back-to-back capable.  Master Capable.  Latency=32.
      I/O at 0x860 [0x861].
  Bus  0, device   7, function  2:
    USB Controller: Intel 82371AB PIIX4 USB (rev 1).
      Medium devsel.  Fast back-to-back capable.  IRQ 11.  Master Capable.  Latency=32.
      I/O at 0xece0 [0xece1].
  Bus  0, device   7, function  3:
    Bridge: Intel 82371AB PIIX4 ACPI (rev 1).
      Medium devsel.  Fast back-to-back capable.

I'd be happy to send you any other info that could help.

Cheers,

Mike

None Something to try...

Re: Question More info... (Mike Rudgyard)
Date: 1999, Dec 30
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Try getting the latest version of tulip-diag from Donald Becker's web
site, then use it to write the EEPROM on the card, and see if that
helps.

-- Dave

Ok Success !!

Re: None Something to try... (David Hinds)
Date: 2000, Jan 10
From: Mike Rudgyard MikeR

Tried your suggestion (and updated to pcmcia3.18 and the latest version of tulip.c).....

... and it seems to work fine !!!

I'll let you know if I have any problems in the coming weeks.

Thanks for the help !

Mike

Question I'd like your success

Re: Ok Success !! (Mike Rudgyard)
Date: 2000, Feb 17
From: Kurt Atkinson kjwa

Dear Mike,

I seem to be having a similar problem with the same card. I'm using a generic make laptop with an O2Micro bridge. Could you possibly give some more details of how you solved your problem so I can have a go also? I've read the preceeding messages but am a little lost. Any help will be much appreciated.

kURT <<()>>

Sad Same thing happens with Intel PRO/100 LAN+Modem56 CardBus II card

Re: Question Intel EtherExpress PRO/100 Cardbus 32 (Mike Rudgyard)
Date: 1999, Dec 07
From: Wayne Scott wscott

I just got a Intel Pro/100 LAN+Modem combo card and it has the exact same symptoms. Any help would be appreciated.

My logs look just like the other guys, but I also get these messages:

  eth0: Tx hung, 13 vs. 0.
  eth0: 21140 transmit timed out, status ffffffff, SIA ffffff.... (all 'f's)

Let me know if I can send anything to help debug.

-Wayne

None It's the chipset

Re: Sad Same thing happens with Intel PRO/100 LAN+Modem56 CardBus II card (Wayne Scott)
Date: 2000, Apr 22
From: John Kilpatrick <john@hypergeek.net>

The whole problem with that card is that it is based on the Intel i82559 chipset. The only similarity it has to the Xircom is the shape. :-)

There is a patch out there (David was kind enough to send it to me) but I can't seem to get it compiled. Still working on it.

Question eth0 won't initialise on bootup.

Date: 1999, Nov 18
From: James Bramich jb

Hi,

I'm a real Linux beginner (oh god they say). I am running Red Hat 6.0 on an IBM Thinkpad 600e.

Redhat installed OK. I upgraded the kernel and card services as per the model specific doc's on the Linux on Laptops page and it seems to go OK.

However, "eth0" fails to initialise when the machine boots. I can go into the GNOME control panel and initialise it manually, but it won't do it autimatically.

Any ideas, I still haven't got the hang of the order in which everything loads up yet so I'm not sure if there are any config files or whatever I should be looking in.

Thanks for any ideas.

James.

None need more information

Re: Question eth0 won't initialise on bootup. (James Bramich)
Date: 1999, Nov 21
From: Nathan Hartwell MageX

How about a piece of your log where pcmcia services are initialized? Perhaps there's a clue in there as to what is going wrong.

None Check the HOWTO...

Re: Question eth0 won't initialise on bootup. (James Bramich)
Date: 1999, Nov 22
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The section on Red Hat describes how you need to set up /etc/pcmcia/network.opts so that the Red Hat network control scripts will work automatically.

-- Dave

Question Kingmax 10/100 Mbps cardbus ethernet card, help?

Date: 1999, Nov 26
From: Michael Kroes yodax

Hello,

I have a question about the kingmax 10/100Mbps cardbus ethernet adapter. I added the version info to the /etc/pcmcia/config and used the tulip_cs module.

Cardmanager now detects the card and it is configurable by ifconfig. But i can only ping computers they can also ping me, but i can't use client protocols like FTP, telnet, portscanners etc.

I had an old 10 mbps 16 bit card before and it worked fine, and stil does btw.

So perhaps someone can help me with this problem?

Sincerely yours

Michael Kroes

Question dynalink lc10 network can't initialise

Date: 1999, Nov 29
From: digit

Hi,

My dynalink LC10 pcmcia card works with windows. If checked the irq's and memory vallues and copied these ranges to linux

:/etc/pcmcia/config.opts

messages say everything works modules, irq mem but ./network start eth0 failes because eth0 doesn't exist.

I allso get twe high low beep on boot and after insert.

Using redhat 6.1 the card is in the supported database and is recognised as NE2000 compatible (messages sya this)

Is this card indeed supported? The irq 3 is really free in my case and the mem seems right to. When remomving the high memory range from config.options I get the right beeps but the card is then a mem0 device and nothing eth0 like.

Thsi is ll I know is there someone thaT KNOWS WHAT TO DO OR IS THIS CARD SIMPLY NOT SUPPORTED?

None The actual messages would help

Re: Question dynalink lc10 network can't initialise
Date: 1999, Nov 29
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> 
> messages say everything works modules, irq mem but ./network start eth0
> failes because eth0 doesn't exist.

It would help to show the actual messages, because I can't really tell
what's going on from your summary.

It might be something trivial, like you haven't done a "netconf" to
enter your network settings yet.

-- Dave

None messages for compaqua armada 1750

Re: None The actual messages would help (David Hinds)
Date: 1999, Nov 30
From: digit

Nov 30 10:27:41 localhost pcmcia: Starting PCMCIA services:
Nov 30 10:27:41 localhost pcmcia:  modules
Nov 30 10:27:41 localhost kernel: Linux PCMCIA Card Services 3.0.14
Nov 30 10:27:41 localhost kernel:   kernel build: 2.2.12-20 #1 Mon Sep 27 10:40:
35 EDT 1999
Nov 30 10:27:41 localhost kernel:   options:  [pci] [cardbus] [apm]
Nov 30 10:27:41 localhost kernel: Intel PCIC probe:
Nov 30 10:27:41 localhost kernel:   TI 1225 PCI-to-CardBus at bus 0 slot 17, mem
 0x7fffe000, 2 sockets
Nov 30 10:27:41 localhost kernel:     host opts [0]: [ring] [pwr save] [pci + se
rial irq] [no pci irq] [lat 66/176] [bus 2/2]
Nov 30 10:27:41 localhost kernel:     host opts [1]: [ring] [pwr save] [pci + se
rial irq] [no pci irq] [lat 66/176] [bus 3/3]
Nov 30 10:27:41 localhost kernel:     ISA irqs (scanned) = 3,4,7,9,10,15 status
change on irq 15
Nov 30 10:27:41 localhost pcmcia:  cardmgr.
Nov 30 10:27:41 localhost cardmgr[412]: starting, version is 3.0.14
Nov 30 10:27:41 localhost cardmgr[412]: watching 2 sockets
Nov 30 10:27:41 localhost kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x1
000-0x10ff
Nov 30 10:27:41 localhost kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x1
00-0x107 0x220-0x22f 0x250-0x257 0x330-0x337 0x378-0x37f 0x388-0x38f 0x4d0-0x4d7

Nov 30 10:27:41 localhost cardmgr[412]: initializing socket 0
Nov 30 10:27:41 localhost kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.

Nov 30 10:27:41 localhost cardmgr[412]: socket 0: DynaLink L10C Ethernet
Nov 30 10:27:41 localhost rc: Starting pcmcia succeeded
Nov 30 10:27:41 localhost cardmgr[412]: executing: 'insmod /lib/modules/2.2.12-2
0/net/8390.o' Nov 30 10:27:41 localhost cardmgr[412]: executing: 'insmod /lib/modules/2.2.12-2 0/pcmcia/pcnet_cs.o' Nov 30 10:27:42 localhost kernel: eth0: NE2000 Compatible: io 0x300, irq 3, hw_a ddr 00:C0:0C:03:9D:3D
Nov 30 10:27:42 localhost cardmgr[412]: executing: './network start eth0'
Nov 30 10:27:42 localhost inet: inetd startup succeeded
Nov 30 10:27:42 localhost cardmgr[412]: + usage: ifup <device name>
Nov 30 10:27:42 localhost cardmgr[412]: start cmd exited with status 1

None No real problems here

Re: None messages for compaqua armada 1750
Date: 1999, Nov 30
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> Nov 30 10:27:42 localhost cardmgr[412]: + usage: ifup <device name>

Run "netconf" and enter some settings for your network.

Everything else looks perfect.

-- Dave

None Thanks!!

Re: None No real problems here (David Hinds)
Date: 1999, Dec 01
From: digit

Wow it works now, made an eth0 device with no kernel module and no boot start. Finally. I got confused because I entered IP netmask etc. in network.opts under RH6.1 in /etc/pcmcia/

This realy makes my millenium!!

uhmmm thanks!

Question DFE-650 only 10 Mbit?

Date: 1999, Nov 29
From: tma

Hello, i have a rather strange problem with a D-LINK DFE-650 100TX card on an ACER Travelmate 332T.. the card itself works pretty good, but the maximum speed is ~ 1.18 mb/sec, which is exactly 10Mbit. the network/connection is about 6-8 mb/sec with win98 (spit!) using the same machine/card, so the problem seems to be the driver.. the faq lists this card as 10/100 & working, so i'm optimistic

dump of dmesg: (oh yes, and it's a somehow modified slackware 7.0)

Linux version 2.2.13 (root@flap) (gcc version 2.95.1 19990816 (release)) #2 Mon Nov 29 21:47:13 CET 1999
Detected 365819234 Hz processor.
Console: colour dummy device 80x25
Calibrating delay loop... 365.36 BogoMIPS
Memory: 62908k/65472k available (1060k kernel code, 412k reserved, 1024k data, 68k init)
VFS: Diskquotas version dquot_6.4.0 initialized
CPU: Intel Mobile Pentium II stepping 0a
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.35a (19990819) Richard Gooch (rgooch@atnf.csiro.au)
PCI: PCI BIOS revision 2.10 entry at 0xf0200
PCI: Using configuration type 1
PCI: Probing PCI hardware
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
Starting kswapd v 1.5 
vesafb: framebuffer at 0x80800000, mapped to 0xc4000000, size 2560k
vesafb: mode is 800x600x8, linelength=800, pages=4
vesafb: protected mode interface info at c000:687c
vesafb: scrolling: redraw
Console: switching to colour frame buffer device 100x37
fb0: VESA VGA frame buffer device
Detected PS/2 Mouse Port.
Serial driver version 4.27 with no serial options enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS02 at 0x03e8 (irq = 4) is a 16550A
pty: 256 Unix98 ptys configured
apm: BIOS version 1.2 Flags 0x0f (Driver version 1.9)
Real Time Clock Driver v1.09
Uniform Multi-Platform E-IDE driver Revision: 6.20
ALI15X3: IDE controller on PCI bus 00 dev 78
ALI15X3: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0x7090-0x7097, BIOS settings: hda:DMA, hdb:pio
ALI15X3: simplex device:  DMA disabled
ide1: ALI15X3 Bus-Master DMA disabled (BIOS)
hda: IBM-DBCA-206480, ATA DISK drive
ide2: ports already in use, skipping probe
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ALI15X3: Ultra DMA enabled
hda: IBM-DBCA-206480, 6194MB w/420kB Cache, CHS=789/255/63, UDMA(33)
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
Partition check:
 hda: hda1 hda2 < hda5 hda6 > hda3
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 68k freed
Adding Swap: 104384k swap-space (priority -1)
parport0: PC-style at 0x378 [SPP,PS2,EPP]
lp0: using parport0 (polling).
CSLIP: code copyright 1989 Regents of the University of California
PPP: version 2.3.7 (demand dialling)
PPP line discipline registered.
PPP BSD Compression module registered
Linux PCMCIA Card Services 3.1.5
  kernel build: 2.2.13 #1 Mon Nov 29 21:17:51 CET 1999
  options:  [pci] [cardbus] [apm]
Intel PCIC probe: 
  O2Micro OZ6812 PCI-to-CardBus at bus 0 slot 19, mem 0x68000000, 1 socket
    host opts [0]: [a 24] [b 0d] [c 00] [d 83] [mhpg 18] [fifo 00] [e 2a] [no pci irq] [lat 32/176] [bus 32/34]
    ISA irqs (default) = 3,4,7,11,12 polling interval = 1000 ms
cs: IO port probe 0x1000-0x17ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x408-0x40f 0x480-0x48f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: clean.
eth0: NE2000 Compatible: io 0x300, irq 3, hw_addr 00:E0:98:73:A0:75
eth0: found link beat

thanks in advance, tma

None I don't really know

Re: Question DFE-650 only 10 Mbit?
Date: 1999, Nov 30
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I have no additional information for you.  With this card, I get about
the same throughput you do.  The card definitely does negotiate a
100baseT connection; a conventional NE2000 type card could not reach
this speed on a 10baseT link.  I had assumed that the card was doing
some sort of internal throttling, since it could never keep up with a
100baseT link anyway.

However, it is (as far as I know) not possible that you could get 6-8
mb/sec under windows with this card.  The maximum transfer rate for
the 16-bit PCMCIA bus is only about 2 mb/sec, and it is not possible
to do better than that without going to a CardBus card.

-- Dave

Question right.

Re: None I don't really know (David Hinds)
Date: 1999, Nov 30
From: tma

reinstalled 98, does really just ~1,3 mb/sec.. lesson learned, never believe anything you haven't tested yourself..damn.

1.) D-Link DFE-660TX and 2.) SURECOM EP-428X

are both CardBus. do you know if they work smooth & fast, especially the 428X ?

thanks, tma

None Re: Question: right.

Re: Question right.
Date: 1999, Nov 30
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The D-Link should be good; the Surecom is not on my list of supported
cards.

-- Dave

Question LinkSys 10baseT "Network Everywhere" NP10T?

Date: 1999, Dec 01
From: John Tunison jtunison

Hi,

I was wondering if anybody's been able to get the LinkSys 10baseT "Network Everywhere" card to work. I know it's not on the supported cards list, but it said on the box "NE2000 compatible" and it only cost $35 at CompUSA, so I thought I'd try it. (Also, I knew that LinkSys had a Linux driver page on their website. Unfortunately, it has no mention fo the Network Everywhere PC card.)

Everything appears to load correctly, but the card won't actually work. I'm _pretty_ sure I've got my ethernet settings confingured correctly.

The card seems to be detected properly:

localhost kernel: eth0: NE2000 Compatible: port 0x300, irq 5, hw_addr 00:E0:98:70:4C:8C

Any suggestions?

Thanks, -John

Feedback More info...

Re: Question LinkSys 10baseT "Network Everywhere" NP10T? (John Tunison)
Date: 1999, Dec 06
From: John Tunison jtunison

When I try installing from RH 6.1 pcmcia.img (the updated version), and I select NFS install and then look at alt-f4, I see this:

<6>eth0: NE2000 Compatible: io 0x300, irq5, hw_addr ...
<30> ... cardmgr[14]: fopen(stabfile) failed:  No such file or directory
<30> ... cardmgr[14]: exiting
<7>eth0: Tx timed out, lost interrupt?  TSR=0x3, ISR=0x3, t=1000.
<7>eth0: Tx timed out, lost interrupt?  TSR=0x3, ISR=0x3, t=1500.

Please tell me there's something I can do to make this card work. (This is on a Sony Vaio n505ve.)

Thanks, John

None There isn't much you can do to fix install problems

Re: Feedback More info... (John Tunison)
Date: 1999, Dec 14
From: David Hinds <dhinds@pcmcia.sourceforge.org>

As the PCMCIA-HOWTO says, your best bet is to install some other way
(i.e., via CD, if possible), then get the latest PCMCIA drivers and
try to debug the problem, if it persists.  There isn't much you can do
from the installation disks, to either diagnose or fix whatever might
be wrong.  In this case, it seems likely that you've got an interrupt
conflict (maybe with your sound chipset).

-- Dave

Ok For others with a Vaio N505...

Re: None There isn't much you can do to fix install problems (David Hinds)
Date: 1999, Dec 14
From: John Tunison jtunison

Thanks Dave, for your response.

You're right; I had no luck at all getting the card to work during the install.

Just in case there are other frustrated Vaio PCG-N505 owners out there, it seems that mysteriously, the ethernet card won't work under Linux under IRQ 5. (Strangely, it shows up under Windows98 as using IRQ 5 and appears to work just fine.)

At any rate, if you can install via some other method, then add "exclude irq 5" to the config file and everything is happy.

A networked Vaio owner, -John

PS. I initially discovered this from http://www.ifb.co.uk/~liz/n505.html which by the way is a very useful page. It appears that it's not just my $35 10baseT pcmcia card--ethernet cards, IRQ 5, and Vaio N505s don't seem to mix well.

Question RH6.1 505TR hangs returning from hibernate

Date: 1999, Dec 03
From: Henry Hollenberg <speed@rcwm.com>

I have installed RH6.1 on a Sony 505TR and it seems to work quite well except for one thing. With an active network pcmcia card in place going into a suspend or hibernate mode (Fn-F2 or Fn-F12) is the kiss of death. As soon as I try to "wake-up" the system it comes alive for a brief instant and then hangs cold. The only course of action is a power down and wait on the fsck scolding on reboot. My other pcmcia modem card does not have any trouble with suspend and resume.

Also noticed that if the adapter cable or ethernet cable are unplugged from the ethernet card while it is live this will cause the system to hang also.

I can do a 	/sbin/cardctl suspend
		hibernate
		wake up
		/sbin/cardctl resume
without crashing.

Is anyone familiar with this behavior? Is this to be expected? Thanks hghiii

ps the card in question is a Linksys etherfast 10/100:PCMPC200

None This driver can't handle suspend/resume events

Re: Question RH6.1 505TR hangs returning from hibernate (Henry Hollenberg)
Date: 1999, Dec 30
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The tulip driver (used by the Linksys PCMPC200 card) does not handle
suspend/resume events at this time.  It is something I've tried to
fix, but I don't have it working yet.

-- Dave

Question Support for Intel PRO/100 CardbusII (MBLA3400)

Date: 1999, Dec 03
From: Edwin van Ouwerkerk Moria <edwin@hotobjects.nl>

Is support for this (relatively new) Intel adapter planned? None of the existing (xircom) drivers seem to work - I heard the Intel & Xircom adapters are supposedly compatible (if not identical). According to the specs, it uses an (Intel) i82559 chip.

Any info/help would be appreciated!

None Not yet

Re: Question Support for Intel PRO/100 CardbusII (MBLA3400) (Edwin van Ouwerkerk Moria)
Date: 1999, Dec 03
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Some Intel CardBus cards are OEM'ed from Xircom.  Others use the
i82559 chipset.  There is no CardBus driver for the i82559 at this
time.

-- Dave

Question DHCP with PCMCIA

Date: 1999, Dec 06
From: Christopher Keller ckeller

I'm having a problem getting a DHCP client to automatically come up on boot up. It comes up fine after boot-up, which is why I think it's merely a configuration problem, rather than an incompatibility.

First the specifics:

Dell Inspiron 3200
Caldera 2.3 w/ kernel 2.2.10
PCMCIA 3.0.14
3COM 3CCFEM556B (ethernet + modem)

When I hook up to a network which is running a DHCP server the following happens (some is assumption, some is fact, please correct where appropriate):

Out of /etc/rc.d/rc2.d/S01network, it tries to start the DHCPcd client using the files in /etc/sysconfig/network-scripts. Specifically ifup-dhcp. THis fails, I'm assuming because the PCMCIA drivers haven't loaded yet. I haven't been able to find any error messages in the logs, but I've confirmed that the dhcpcd daemon is trying to run. I'm guessing it doesn't log because it doesn't get far enough along due to the drivers not being loaded (although I have confirmed that eth0 is up). Anyway...along comes S07pcmcia. Once again, dhcp setup is tried (this time using cardmgr). I get the following messages in /var/log/messages:
 
cardmgr[572]: + Trying to obtain network configuration via DHCP.
kernel: eth0: found link beat
kernel: eth0: autonegotiation complete: 100baseT-HD selected
kernel: eth0: remote fault detected
dhcpcd[587]: timed out waiting for a valid DHCP server response
cardmgr[572]: + No response from DHCP server
cardmgr[572]: + eth0: initialization failed

and so on....

At any rate, once the login screen comes up, I can log in as root and do a manual "network start eth0" and dhcp comes up perfectly. No problems whatsoever. Or I can accomplish the same thing by the scripts in /etc/sysconfig/network-scripts/ifup-dhcp.

So, it makes sense that the first attempt out of S01network fails, as there are no PCMCIA drivers yet loaded. But the second attempt (above) out of S07pcmcia should work. I can't believe I'm the only one trying to run DHCP on a laptop, so if someone could point me the right way, I'd much appreciate it.

The easy solution might be to write a S99dhcp file and kludge the thing together. However, if there is a problem with my knowledge or the PCMCIA packages, I'd rather solve that.

TIA....

-Chris

None Not sure if this is Caldera specific

Re: Question DHCP with PCMCIA (Christopher Keller)
Date: 1999, Dec 06
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I don't think it is possible to narrow down the problem based on just
this information.  Are you sure that dhcpcd is being started prior to
when PCMCIA loads?  (are there system log messages from a second copy
of dhcpcd?)  I am not familiar with Caldera, but to the extent it is
based on Red Hat, I know that Red Hat checks for and delays startup of
a PCMCIA network device to avoid exactly this problem.  It would be
strange for Caldera to have un-done this.

Another simple thing to try, is to boot with the card out, then plug
it in and see what happens.  That will distinguish between various
sorts of boot-time sequencing problems, and PCMCIA startup problems.

> cardmgr[572]: + Trying to obtain network configuration via DHCP.
> kernel: eth0: found link beat
> kernel: eth0: autonegotiation complete: 100baseT-HD selected
> kernel: eth0: remote fault detected
> dhcpcd[587]: timed out waiting for a valid DHCP server response

The timing here concerns me, because it looks like dhcpcd may be
having trouble because the card has a delay before it has properly
sensed the link speed.

-- Dave

None Hate to say it, but even Red Hat is having trouble with DHCP and PCMCIA

Re: None Not sure if this is Caldera specific (David Hinds)
Date: 2000, Jan 17
From: Nathan Hartwell MageX

I just switched out my generic PCMCIA 10/100 card for a D-Link DFE-650TX card (something on the supported list). As it would turn out, I -still- can't get dhcpcd or pump to grab an IP. At least with pump, I see the messages where it gets an offer, but the offer is never accepted for one reason or another. With dhcpcd, it just seems to sit there like a bump on a log then finally times out. I had these same troubles with the previous card which is why I switched to this D-Link. I even went so far as to re-extract the pcmcia-cs v3.1.6 package and recompile (plus a fresh copy of 8390.c and 8390.h). I have not yet forced a specific IP as I am not wanting to have it set up this way to begin with. I am certain that the card will work fine once I manually set it's IP, however. Any help will be appreciated.

None Don't be so sure!

Re: None Hate to say it, but even Red Hat is having trouble with DHCP and PCMCIA (Nathan Hartwell)
Date: 2000, Jan 17
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> I have not yet forced a specific IP as
> I am not wanting to have it set up this way to begin with. I am certain
> that the card will work fine once I manually set it's IP, however.

There is no reason whatsoever for you to be certain of this fact, and
you should absolutely test it, because it is the only way to determine
for sure if you are suffering from a driver problem, versus suffering
from some issue with your DHCP configuration.  Just do it.

-- Dave

None quite right....it wasn't a PCMCIA issue, but a DHCP issue

Re: None Don't be so sure! (David Hinds)
Date: 2000, Jan 19
From: Nathan Hartwell MageX

as it turns out, the DHCP server within the Netgear RT328 does not respond properly for dhcpcd or pump to latch on to the offer, yet Win9x will. however, I run dhcpd on my home Linux server and pump grabs the ip info just fine (though I am manually running it with this setup, defined for work and manually run pump after logging in at home)

I plan to configure the Linux server at work (as I'm the primary admin anyway) to run dhcpd. I hope to have a worry free setup after that's done.

Question Possible erroneous manfid in config file?

Date: 1999, Dec 13
From: Brian Mays brian

The Corega PCC-T Ehternet PCMCIA card (NE2000 clone) identifies its manfid as 0xc00f, 0x0000.

 $ cardctl ident 0
   product info: "corega K.K.", "corega Ether PCC-T"
   manfid: 0xc00f, 0x0000
   function: 6 (network)

But in pcmcia-cs 3.1.5, the config file config has another entry which also has manfid as 0xc00f, 0x0000.

 card "Allied Telesyn AT-2800 10/100 Fast Ethernet"
   manfid 0xc00f, 0x0000
   bind "tulip_cb"

Therefore, when a PCC-T Ethernet card is used, pcmcia-cs tried to install tulip_cb modules (instead of pcnet_cs), which results in errors.

Is the manfid for the AT-2800 correct or is something else wrong?

None Well, one of them is wrong...

Re: Question Possible erroneous manfid in config file? (Brian Mays)
Date: 2000, Jan 14
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I'll comment out the Allied Telesyn entry in future PCMCIA releases,
until it is sorted out.  We'll need to get product info strings for
the Allied Telesyn card.

-- Dave

None Problems with 3c575 and CEM33 on an NEC Versa LX

Date: 1999, Dec 13
From: Brian Mays brian

This message describes problems with two pcmcia cards. One is a 3com cardbus 10/100 (3c575), the other is a Xircom pccard CEM33 (10bt ethernet+modem 33.6). These cards are being used with an NEC Versa LX laptop.

The 3com card works ok except when ftping a file (of say, 184mb) the system freezes and there are messages on the console. They are

  eth0: Host error, FIFO diagnostic register 0000.
        This message repeats 21 times
  eth0: Too much work in interrupt, status 8003.  Temporarily disabling
        functions (7ffc).

At that point, the system is completely unusable. If the card is ejected, the kernel oops's and the system is still unusable. Note that the error messages for the oops are unavailable, since it was very long and difficult to capture.

The Xircom card freezes the system. No messages are printed. When ejecting the card, the display shifts. Column 1 starts in the middle of the screen. The system is completely unusable after inserting the card.

Before upgrading to pcmcia 3.1.5, version 3.1.1 was installed. The 3com card has experienced problems with both versions. The Xircom adapter worked under the 3.1.1 version, but not 3.1.5.

None A favorable resolution on both counts

Re: None Problems with 3c575 and CEM33 on an NEC Versa LX (Brian Mays)
Date: 1999, Dec 17
From: David Hinds <dhinds@pcmcia.sourceforge.org>

All the problems are now more or less resolved...

-- the failures in the 3c575_cb driver's error handling code are
   partly fixed in 3.1.7, and fully fixed in the 16-Dec-99 beta
   drivers.  I still do not know what is causing the initial error (a
   HostError is supposed to be a PCI bus protocol problem, according
   to the 3Com documentation), but now, it is handled gracefully
   without disrupting network activity.

-- the Xircom card problem turned out to be an IO port conflict with
   another system device, that the Linux kernel had not detected.  A
   note will be added to the HOWTO, that ports 0x300-0x31f should be
   excluded on the Versa LX.

-- Dave

Warning genius MF3000 different versions?

Date: 1999, Dec 29
From: J. Schmid jds

There is an entry in the supported cards : "Genius MF3000" (fast ethernet) and a coresponding entry in pcmcia/config:

card "Genius MF3000 Fast Ethernet"
  version "CardBus", "10/100Mbps LanCard"
  bind "tulip_cb" 

I have a card labelled "Genius MF3000" which identifies itself as:

"CardBus", "10/100Mbps LANCard" ("LAN" is all capital now!!!)

And does not work properly after changing /pcmcia/config so that tulip_cb is loaded.

I can ping another machine but long packages are lossy and I don't get ftp through the line.

System: sony vaio737 kernel: 2.2.12 pcmcia: 3.1.8

More kludge for partial functionality of genius MF3000

Re: Warning genius MF3000 different versions? (J. Schmid)
Date: 2000, Jan 02
From: J. Schmid jds

The failure of the "other" "genius MF3000" FastEthernet PCMCIA card seems to be due to problems with the tulip-driver distributed with pcmcia-cs-3.1.8 (it doesn't detect the tulip-chip and MAC-address correctly on this card).

With the following setup I get partial functionality:

 Laptop sony vaio737
 Kernel 2.2.12 (+ patch-irda3) 
 pcmcia-cs-3.1.8 

CHANGES:

add entry to /etc/pcmcia/config:

card "Genius MF3000 Fast Ethernet"
   version "CardBus", "10/100Mbps LANCard"
   bind "tulip_cb" 

replace /lib/modules/2.2.12/pcmcia/tulip_cb.o with the one compiled from tulip.c found in kernel 2.2.14pre17

Limitations of this setup:
- the tulip_cb driver seems to negotiate 100baseTx-FD without 
  setting the chip up for full duplex (-> only ~300kbyte/s 
  ftp-throughput,collisions). Forcing the tulip_cb driver to 
  100baseTx I get up to 7Mbyte/s ftp-throughput.
- suspend-resume works, eject-insert works, but 
  insert-suspend-eject-resume leads to a negative
  "use count" for tulip_cb such that the modules can't be 
  unloaded. Inserting the card, the network works fine 
  in spite of the wrong "use count".

P.S. I tried tulip.c:v0.91u 10/15/99 which didn't detect the chip right.

Question NetGear FA510 ethernet card not recognized

Date: 2000, Jan 05
From: Michael Bletzinger mbletzin

A coworker and I have the same thinkpad 600E and netgear card. He is running 2.2.13 kernel and pcmcia distribution 3.1.0. I am running kernel 2.2.12 with pcmcia 3.1.8. His configuration works mine doesn't.

When he does a "cardctl ident" the following is listed:

  product info: "NETGEAR", "FA510", "Fast Ethernet CardBus Card", "1.00"
  manfid: 0x9513, 0x0081
  function: 6 (network)

On my conputer the command list "no product info found". The card was identified once while I was hot swapping cards.

        Thanks in advance
        Michael

None The usual response: check your system log

Re: Question NetGear FA510 ethernet card not recognized (Michael Bletzinger)
Date: 2000, Jan 06
From: David Hinds <dhinds@pcmcia.sourceforge.org>

System log messages might be useful.  A comparison of log messages
between the working and non-working systems would be even more useful.

Do you have other cards that do (or do not) work?

-- Dave

Feedback Here are the logs

Re: None The usual response: check your system log (David Hinds)
Date: 2000, Jan 06
From: Michael Bletzinger mbletzin

Thanks for the quick response David!

I was able to get the card recognized if I also had my lucent wavetek card inserted. As you can tell I still need to get linuxconf to work with two ethernet cards.

First the failure:
=================================
Jan 5 19:59:59 aidalap pcmcia: Starting PCMCIA services:
Jan 5 20:00:00 aidalap kernel: Linux PCMCIA Card Services 3.1.8
Jan 5 20:00:00 aidalap kernel: kernel build: 2.2.13 #1 Fri Dec 31 09:13:09 CST 1999
Jan 5 20:00:00 aidalap kernel: options: [pci] [cardbus] [apm] [pnp]
Jan 5 20:00:00 aidalap kernel: PnP: PNP BIOS installation structure at 0xc00fe700
Jan 5 20:00:00 aidalap kernel: PnP: PNP BIOS version 1.0, entry at f0000:e724, dseg at f0000
Jan 5 20:00:00 aidalap kernel: PCI routing table version 1.0 at 0xf9e40
Jan 5 20:00:00 aidalap kernel: 00:02.0 -> irq 11
Jan 5 20:00:00 aidalap kernel: 00:02.1 -> irq 11
Jan 5 20:00:00 aidalap kernel: Intel PCIC probe:
Jan 5 20:00:00 aidalap kernel: TI 1251A PCI-to-CardBus at bus 0 slot 2, mem 0x50102000, 2 sockets
Jan 5 20:00:00 aidalap kernel: host opts [0]: [ring] [pwr save] [isa irq] [pci irq 11] [lat 168/176] [bus 2/4]
Jan 5 20:00:00 aidalap kernel: host opts [1]: [ring] [pwr save] [isa irq] [pci irq 11] [lat 168/176] [bus 5/7]
Jan 5 19:59:59 aidalap pcmcia: modules
Jan 5 20:00:00 aidalap kernel: ISA irqs (scanned) = 4,9 polling interval = 1000 ms
Jan 5 20:00:00 aidalap pcmcia: cardmgr.
Jan 5 20:00:00 aidalap rc: Starting pcmcia succeeded
Jan 5 20:00:00 aidalap cardmgr[348]: starting, version is 3.1.8
Jan 5 20:00:00 aidalap cardmgr[348]: watching 2 sockets
Jan 5 20:00:00 aidalap kernel: cs: IO port probe 0x1000-0x17ff: clean.
Jan 5 20:00:00 aidalap kernel: cs: IO port probe 0x0100-0x04ff: clean.
Jan 5 20:00:00 aidalap kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Jan 5 20:00:00 aidalap kernel: cs: cb_alloc(bus 5): vendor 0x1011, device 0x0019
Jan 5 20:00:00 aidalap cardmgr[348]: initializing socket 1
Jan 5 20:00:00 aidalap cardmgr[348]: unsupported card in socket 1
Jan 5 20:00:00 aidalap inet: inetd startup succeeded
Jan 5 20:00:00 aidalap cardmgr[348]: no product info available
========================
Now the Success:

========================
Jan 5 19:47:19 aidalap kernel: Linux PCMCIA Card Services 3.1.8
Jan 5 19:47:19 aidalap kernel: kernel build: 2.2.13 #1 Fri Dec 31 09:13:09 CST 1999
Jan 5 19:47:19 aidalap kernel: options: [pci] [cardbus] [apm] [pnp]
Jan 5 19:47:19 aidalap kernel: PnP: PNP BIOS installation structure at 0xc00fe700
Jan 5 19:47:19 aidalap kernel: PnP: PNP BIOS version 1.0, entry at f0000:e724, dseg at f0000
Jan 5 19:47:19 aidalap kernel: PCI routing table version 1.0 at 0xf9e40
Jan 5 19:47:19 aidalap kernel: 00:02.0 -> irq 11
Jan 5 19:47:19 aidalap kernel: 00:02.1 -> irq 11
Jan 5 19:47:19 aidalap kernel: Intel PCIC probe:
Jan 5 19:47:19 aidalap kernel: TI 1251A PCI-to-CardBus at bus 0 slot 2, mem 0x50102000, 2 sockets
Jan 5 19:47:19 aidalap kernel: host opts [0]: [ring] [pwr save] [isa irq] [pci irq 11] [lat 168/176] [bus 2/4]
Jan 5 19:47:19 aidalap kernel: host opts [1]: [ring] [pwr save] [isa irq] [pci irq 11] [lat 168/176] [bus 5/7]
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:7
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:8
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:9
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:10
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:11
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:12
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:13
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:14
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:15
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:16
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:17
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:18
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:19
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:20
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:21
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:22
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:23
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:24
Jan 5 19:47:18 aidalap pcmcia: Starting PCMCIA services:
Jan 5 19:47:19 aidalap kernel: ISA irqs (scanned) = 4,9 polling interval = 1000 ms
Jan 5 19:47:19 aidalap kernel: cs: cb_alloc(bus 5): vendor 0x1011, device 0x0019
Jan 5 19:47:19 aidalap kernel: cs: IO port probe 0x1000-0x17ff: clean.
Jan 5 19:47:19 aidalap kernel: cs: IO port probe 0x0100-0x04ff: clean.
Jan 5 19:47:19 aidalap kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Jan 5 19:47:19 aidalap kernel: cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa0ffffff
Jan 5 19:47:19 aidalap kernel: cs: warning: no high memory space available!
Jan 5 19:47:19 aidalap kernel: cs: memory probe 0x0d0000-0x0dffff: clean.
Jan 5 19:47:19 aidalap pcmcia: modules
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:25
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:26
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:27
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:28
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:29
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:30
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:31
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:32
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:33
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:34
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:35
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:36
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:37
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:38
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:39
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:40
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:41
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:42
Jan 5 19:47:20 aidalap kernel: eth0: WaveLAN/IEEE, io_addr 0x400, irq 9, mac_address 00:60:1D:F0:6E:FB
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:43
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:44
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:45
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:46
Jan 5 19:47:15 aidalap modprobe: can't locate module lo:47
Jan 5 19:47:16 aidalap modprobe: can't locate module lo:48
Jan 5 19:47:16 aidalap modprobe: can't locate module lo:49
Jan 5 19:47:16 aidalap network: Bringing up interface lo succeeded
Jan 5 19:47:16 aidalap ifup: Delaying eth0 initialization.
Jan 5 19:47:16 aidalap network: Bringing up interface eth0 failed
Jan 5 19:47:16 aidalap portmap: portmap startup succeeded
Jan 5 19:47:16 aidalap random: Initializing random number generator succeeded
Jan 5 19:47:19 aidalap pcmcia: cardmgr.
Jan 5 19:47:19 aidalap cardmgr[346]: starting, version is 3.1.8
Jan 5 19:47:19 aidalap cardmgr[346]: watching 2 sockets
Jan 5 19:47:19 aidalap cardmgr[346]: initializing socket 0
Jan 5 19:47:19 aidalap cardmgr[346]: socket 0: Lucent Technologies WaveLAN/IEEEJan 5 19:47:20 aidalap cardmgr[346]: executing: 'insmod /lib/modules/2.2.13/pcmcia/wavelan2_cs.o network_name=NCSA'
Jan 5 19:47:20 aidalap cardmgr[346]: executing: './network start eth0'

Jan 5 19:47:19 aidalap rc: Starting pcmcia succeeded
[skipping...]
Jan 5 19:47:35 aidalap cardmgr[346]: + Determining IP information for eth0... done.
Jan 5 19:47:35 aidalap modprobe: can't locate module eth0:0
Jan 5 19:47:35 aidalap modprobe: can't locate module eth0:1
Jan 5 19:47:35 aidalap modprobe: can't locate module eth0:2
Jan 5 19:47:35 aidalap modprobe: can't locate module eth0:3
Jan 5 19:47:35 aidalap modprobe: can't locate module eth0:4
Jan 5 19:47:35 aidalap modprobe: can't locate module eth0:5
Jan 5 19:47:35 aidalap modprobe: can't locate module eth0:6
Jan 5 19:47:35 aidalap modprobe: can't locate module eth0:7
Jan 5 19:47:35 aidalap modprobe: can't locate module eth0:8
Jan 5 19:47:35 aidalap modprobe: can't locate module eth0:9
Jan 5 19:47:35 aidalap modprobe: can't locate module eth0:10
Jan 5 19:47:35 aidalap modprobe: can't locate module eth0:11
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:12
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:13
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:14
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:15
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:16
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:17
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:18
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:19
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:20
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:21
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:22
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:23
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:24
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:25
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:26
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:27
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:28
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:29
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:30
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:31
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:32
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:33
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:34
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:35
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:36
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:37
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:38
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:39
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:40
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:41
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:42
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:43
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:44
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:45
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:46
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:47
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:48
Jan 5 19:47:36 aidalap modprobe: can't locate module eth0:49

Ok Changing the address worked

Re: Feedback Here are the logs (Michael Bletzinger)
Date: 2000, Jan 10
From: Michael Bletzinger mbletzin

Thanks for your help David.

  I changed the memory address as you suggested and the card was consistantly recognized. I still have a problem with the WaveLAN card working consistently but I need to check with lucent to see if they have a an updated driver.

  Thanks
  Michael

Question O2Micro(OZ6836/6860)+EtherFast=very slow network...

Date: 2000, Jan 07
From: Max Gotlib <max@utc.telenet.ru>

I've got a problem...
Laptop: BMx MP-995
	Mobil Pentium II 400Mhz
	O2Micro (OZ6836/OZ6860) PCI-CardBus bridge
	NIC:
		product info: "FastEthernet", "Adapter", "1.0"
		manufid: 0x0149 oxc1ab
		(FreeBSD-3.3r+PAO recognizes it as Linksys 	
		EtherFast PCMPCI00 - DL10019C based NE2000 	
		clone)
		This NIC properly operates under Win98 and
		FreeBSD-3.3r+PAO
OS: Linux (RedHat's clone) 2.2.13 kernel
PCMCIA package: 3.1.9 (tried 3.0.14, 3.1.8, 3.1.9 28 Dec,
			06 Jan - the same results)

The problem:
	NIC is recognized at bootup (it could be removed and 
inserted back - recognition is successfull again), but it 
delevers very slow performance - ping delay (across 10 and 100 
MBit/s LAN is more, than 180ms). There is no 
"routing-or-other-kinda-administration" problem - i've used 
just the same configuration in the same situation under 
FreeBSD successfully). There are no "interrupt(s) dropped!" 
messages - everithing, except performance (about 9 KB/s in FTP 
session) problems.

I've tryed virtually all combinations of i82365 and pcnet_cs options - no luck...

What can I do to fix it ?

P.S.: Here the "appendixies" are:

1. dmesg:
-----------------------------------------
Linux version 2.2.13 (root@localhost.localdomain) (gcc version egcs-2.91.66 1999
0314/Linux (egcs-1.1.2 release)) #6 pTN qNW 7 04:15:45 YEKT 2000
Detected 400921266 Hz processor.
Console: colour dummy device 80x25
Calibrating delay loop... 399.77 BogoMIPS
Memory: 63984k/66496k available (1004k kernel code, 412k reserved, 1036k data, 6
0k init)
CPU: Intel Mobile Pentium II stepping 0d
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
PCI: PCI BIOS revision 2.10 entry at 0xfb200
PCI: Using configuration type 1
PCI: Probing PCI hardware
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
Initializing RT netlink socket
Starting kswapd v 1.5 
parport0: PC-style at 0x378 [SPP,PS2]
vesafb: framebuffer at 0xe0000000, mapped to 0xc4800000, size 4096k
vesafb: mode is 1024x768x16, linelength=2048, pages=1
vesafb: protected mode interface info at c87c:0000
vesafb: scrolling: redraw
vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
Detected PS/2 Mouse Port.
Serial driver version 4.27 with no serial options enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
pty: 256 Unix98 ptys configured
lp0: using parport0 (polling).
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.9)
PCI_IDE: unknown IDE controller on PCI bus 00 device 39, VID=8086, DID=7199
PCI_IDE: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio
hda: IBM-DARA-206000, ATA DISK drive
hdb: CD-224E, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: IBM-DARA-206000, 5729MB w/418kB Cache, CHS=730/255/63, (U)DMA
hdb: ATAPI 24X CD-ROM drive, 128kB Cache
Uniform CDROM driver Revision: 2.56
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
Partition check:
 hda: hda1 hda2 hda3
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 60k freed
Adding Swap: 112448k swap-space (priority -1)
MSDOS FS: Using codepage 866
MSDOS FS: IO charset koi8-r
VFS: freeing iocharset=koi8-r
Linux PCMCIA Card Services 3.1.9
  kernel build: 2.2.13 #6 pTN qNW 7 04:15:45 YEKT 2000
  options:  [pci] [apm]
Intel PCIC probe: 
  O2Micro OZ6836/OZ6860 PCI-to-CardBus at bus 0 slot 3, mem 0xe1000000, 2 sockets
    host opts [0]: [a 44] [b 8d] [c 00] [d 02] [mhpg 18] [fifo 00] [e 1a] [no pci irq] [lat 32/176] [bus 32/34]
    host opts [1]: [a 44] [b 81] [c 50] [d 02] [mhpg 18] [fifo 00] [e 1a] [no pci irq] [lat 32/176] [bus 35/37]
    ISA irqs (default) = 10 polling interval = 1000 ms
cs: IO port probe 0x0300-0x031f: clean.
cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa00fffff
eth0: NE2000 Compatible: io 0x300, irq 10, hw_addr 00:E0:98:73:64:85
eth0: found link beat

2. /etc/sysconfig/pcmcia:

PCMCIA=yes

PCIC=i82365

PCIC_OPTS="irq_list=10 pci_int=1 pci_csc=1 do_scan=0"

CORE_OPTS=

3. /etc/pcmcia/config.opts

# i'm sure, the NIC uses 0x300 io and 10 irq.

include port 0x300-0x31f

include memory 0xd0000-0xdffff

include memory 0xa0000000-0xa0ffffff

exclude irq 4

exclude irq 3

exclude irq 7

exclude irq 9

exclude irq 11

exclude irq 12

exclude irq 13

exclude irq 14

exclude irq 15

exclude irq 0

exclude irq 1

exclude irq 2

exclude irq 5

exclude irq 6

module "pcnet_cs" opts "irq_list=10"

Note Ugly workaround:-)

Re: Question O2Micro(OZ6836/6860)+EtherFast=very slow network... (Max Gotlib)
Date: 2000, Jul 10
From: Dag Kröper dagkro

Look at Message 87 in this Newsgroup!!!!

That's a dirty Hack using win98!!!

Greetings

Dag

Question Problems with Accton EN2220

Date: 2000, Jan 09
From: Volker Wendt <wendt@nid.de>

Hi,

I tried to use an Accton EN2220 CardBus Fast Ethernet Card. I am using pcmcia-cs.3.1.8 on Linux 2.2.13. Everything seems to work well: The card is detected correctly and all modules are loaded. But it does'nt work. The log says

Jan  9 15:06:27 jc kernel: cs: cb_alloc(bus 32): vendor 0x1011, device 0x0019
Jan  9 15:06:27 jc cardmgr[1231]: initializing socket 0
Jan  9 15:06:27 jc kernel: ROM image dump:
Jan  9 15:06:27 jc kernel:   image 0: 0x000000-0x0001ff, signature PCIR
Jan  9 15:06:27 jc cardmgr[1231]: socket 0: Accton EN2220 Fast Ethernet
Jan  9 15:06:27 jc cardmgr[1231]: executing: 'insmod /lib/modules/2.2.13/pcmcia/cb_enabler.o'
Jan  9 15:06:27 jc cardmgr[1231]: executing: 'insmod /lib/modules/2.2.13/pcmcia/tulip_cb.o'
Jan  9 15:06:27 jc kernel: cs: cb_config(bus 32)
Jan  9 15:06:27 jc kernel:   fn 0 bar 1: io 0x400-0x47f
Jan  9 15:06:27 jc kernel:   fn 0 bar 2: mem 0x600c0000-0x600c03ff
Jan  9 15:06:27 jc kernel:   fn 0 rom: mem 0x60080000-0x600bffff
Jan  9 15:06:27 jc kernel: cs: cb_enable(bus 32)
Jan  9 15:06:27 jc kernel:   bridge io map 0 (flags 0x21): 0x400-0x47f
Jan  9 15:06:27 jc kernel:   bridge mem map 0 (flags 0x1): 0x60080000-0x600c0fff
Jan  9 15:06:27 jc kernel: tulip_attach(bus 32, function 0)
Jan  9 15:06:27 jc kernel: tulip.c:v0.91 4/14/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
Jan  9 15:06:27 jc kernel: eth0: Digital DS21143 Tulip rev 65 at 0x400, FC:00:FC:00:00:00, IRQ 10.
Jan  9 15:06:27 jc cardmgr[1231]: executing: './network start eth0'
Jan  9 15:06:41 jc kernel: eth0: Tx hung, 12 vs. 9.
Jan  9 15:06:41 jc kernel: eth0: 21140 transmit timed out, status f0260000, SIA 000000c6 ffff0000 fffbffff 8ff10008, resetting...
Jan  9 15:06:47 jc kernel: eth0: Tx hung, 12 vs. 9.
Jan  9 15:06:47 jc kernel: eth0: 21140 transmit timed out, status f0260000, SIA 000000c6 ffff0000 fffbffff 8ff10008, resetting...
Jan  9 15:06:53 jc kernel: eth0: Tx hung, 12 vs. 9.
Jan  9 15:06:53 jc kernel: eth0: 21140 transmit timed out, status f0260000, SIA 000000c6 ffff0000 fffbffff 8ff10008, resetting...
Jan  9 15:07:02 jc kernel: eth0: Tx hung, 15 vs. 9.
Jan  9 15:07:02 jc kernel: eth0: 21140 transmit timed out, status f0260000, SIA 000000c6 ffff0000 fffbff7f 8ff10008, resetting...
Jan  9 15:07:08 jc kernel: eth0: Tx hung, 15 vs. 9.
Jan  9 15:07:08 jc kernel: eth0: 21140 transmit timed out, status f0260000, SIA 000000c6 ffff0000 fffbff7f 8ff10008, resetting...
Jan  9 15:07:14 jc kernel: eth0: Tx hung, 15 vs. 9.
Jan  9 15:07:14 jc kernel: eth0: 21140 transmit timed out, status f0260000, SIA 000000c6 ffff0000 fffbff7f 8ff10008, resetting...
Jan  9 15:07:23 jc kernel: eth0: Tx hung, 18 vs. 9.
Jan  9 15:07:23 jc kernel: eth0: 21140 transmit timed out, status f0260000, SIA 000000c6 ffff0000 fffbffff 8ff10008, resetting...

Thanks for any help,
  Volker

None Need more messages

Re: Question Problems with Accton EN2220 (Volker Wendt)
Date: 2000, Jan 09
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The interesting part of the log is the part before where yours starts.

And what kind of laptop is this?

-- Dave

None The usual mantra: more system log messages, please

Re: Question Problems with Accton EN2220 (Volker Wendt)
Date: 2000, Jan 10
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The startup messages from the PCMCIA modules (the PCIC probe results,
etc) would be most useful.

It would also be useful to say what kind of laptop this is.

-- Dave

None might be tulip problem?

Re: Question Problems with Accton EN2220 (Volker Wendt)
Date: 2000, Jan 11
From: J. Schmid jds

This line doesn't look like the tulip driver got a good address (FC:00:FC:00:00:00 seems to have too many 0s):

 Jan  9 15:06:27 jc kernel: eth0: Digital DS21143 Tulip rev 65 at 0x400, FC:00:FC:00:00:00, IRQ 10.

I had a similar problem with a genius MF3000. My card is usable with a newer tulip driver (but not the newest :-() as posted under "kludge for partial functionality of genius MF3000".

Ok New hw_info line for PCMCIA Technology OEM NE2000 Compatible

Date: 2000, Jan 10
From: sampo

I don't know where to report these for adding to autodetection list so I try here. I figured out this stuff using the instructions for configuring a new NE2000 clone.

To pcnet_cs.c following hw_info struct:

 { /* PCMCIA Technology OEM 10/100 */ 0x01c8, 0xa0, 0x0c, 0 },

To config

 card "PCMCIA Technology OEM 10/100 NE2000 Compatible Ethernet"
   manfid 0x8a01, 0xc1ab
   bind "pcnet_cs"

Basically this card is a noname OEM card. Mine does not have any indication of manufacurer (I found the string "PCMCIA Technology, Inc." by looking into cards memory space) or country of origin. I bought mine at Portugal on Sept 1999.

On the reverse side following markings were found:

 10/100 Mbps Ethernet PC Card
 P/N: KEN0100-A
 VER: XA
 S/N: 920I07430004
 16 5V

--Sampo

Question Schemes problem

Date: 2000, Jan 10
From: Ralf Eichmann ralf.eichmann

Hello,

I installed SuSE Linux 6.3 on an Asus F7400 with a D-Link 650. Since the notebook should be usable in various networks I've set up a number of configurations in /etc/pcmcia/network.opts and the corresponding lilo.conf entries.

The lilo append lines are recognized (/sbin/init.d/pcmcia prints "using scheme: ..." correctly), but eth0 is not configured properly. None of the network.opts parameters is set. However, "cardctl scheme ..." works fine. This leads to the following: I do a "cardctl scheme home", then reboot, choose the lilo config with "append="scheme=mg33"" (where mg33 is another scheme), get the message "using scheme: mg33", but "ifconfig eth0" shows the settings from the home scheme.

Is that what is meant with "The SuSE startup script is somewhat limited and does not allow PCMCIA startup variables to be overridden from the lilo boot prompt." from the SuSE section in the PCMCIA-Howto? Can I work around this (by issuing a "cardctl scheme $SCHEME" somewhere in a boot script)?

Thanks and best regards, Ralf Eichmann

Idea Problem and Workaround with dhcpcd

Date: 2000, Jan 12
From: uffti

I've just upgrade to pcmcia-cs-3.1.8 in conjuction with dhcpcd-1.3.18-pl3. I've encountered two flaws :

1. dhcpcd seems to be called wrong
   in /etc/pcmcia/network dhcpcd is called with -V
   with the assumption that it's only displays the
   version information. But it print the version info
   AND makes a dhcp request (I've checked source code
   too).
2. No possibility to set hostname
   There is no way to pass thru parameters to dhcpd

I've modified /etc/pcmcia/network the way it works for me. Maybe this should be considered in future releases :

$ diff network /etc/pcmcia/ 56,73c56,74

<           if /sbin/dhcpcd -V 2>&1 | grep -q DHCP ; then
<               /sbin/dhcpcd $DEVICE >/dev/null 2>&1 || exit 1
<           else
<               # Jump through hoops for lame 0.70-era dhcpcd
<               L=/var/run/dhcp-lock-$DEVICE
<               /bin/echo "#!/bin/sh\nrm $L" > $L ; chmod +x $L
<               /sbin/dhcpcd -c $L $DEVICE >/dev/null 2>&1
<               for t in 0 1 2 3 4 5 6 7 8 9 ; do
<                   sleep 2 ; if [ ! -e $L ] ; then break ; fi
<               done
<               rm -f $L
<               if [ -e /etc/dhcpc/resolv.conf ] ; then
<                   echo "# $DEVICE begin" > $RESOLV.N
<                   cat /etc/dhcpc/resolv.conf >> $RESOLV.N
<                   echo "# $DEVICE end" >> $RESOLV.N
<                   cat $RESOLV >> $RESOLV.N ; mv $RESOLV.N $RESOLV
<               fi
<           fi
---
>           /sbin/dhcpcd $DEVICE -h "$DHCP_HOSTNAME" || exit 1
> #         if /sbin/dhcpcd -V 2>&1 | grep -q DHCP ; then
> #             /sbin/dhcpcd $DEVICE >/dev/null 2>&1 || exit 1
> #         else
> #             # Jump through hoops for lame 0.70-era dhcpcd
> #             L=/var/run/dhcp-lock-$DEVICE
> #             /bin/echo "#!/bin/sh\nrm $L" > $L ; chmod +x $L
> #             /sbin/dhcpcd -c $L $DEVICE >/dev/null 2>&1
> #             for t in 0 1 2 3 4 5 6 7 8 9 ; do
> #                 sleep 2 ; if [ ! -e $L ] ; then break ; fi
> #             done
> #             rm -f $L
> #             if [ -e /etc/dhcpc/resolv.conf ] ; then
> #                 echo "# $DEVICE begin" > $RESOLV.N
> #                 cat /etc/dhcpc/resolv.conf >> $RESOLV.N
> #                 echo "# $DEVICE end" >> $RESOLV.N
> #                 cat $RESOLV >> $RESOLV.N ; mv $RESOLV.N $RESOLV
> #             fi
> #         fi
154,155c155,156
<               /sbin/dhcpcd -V 2>&1 | grep -q DHCP || \
<                   rm -f /var/run/dhcpcd-$DEVICE.pid
---
> #             /sbin/dhcpcd -V 2>&1 | grep -q DHCP || \
> #                 rm -f /var/run/dhcpcd-$DEVICE.pid

None Odd changes

Re: Idea Problem and Workaround with dhcpcd
Date: 2000, Jan 12
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> 1. dhcpcd seems to be called wrong

I'll trust you, but this was not the case with dhcpcd-1.3.17.  Your
change sort-of defeats the purpose of the version check... instead I
would suggest changing "dhcpcd -V" to "dhcpcd -V bogus", which will
hopefully just print the version info and error out.  Can you check
that with dhcpcd-1.3.18?

-- Dave

None yes it works

Re: None Odd changes (David Hinds)
Date: 2000, Jan 13
From: uffti

dhcpcd -V dingsda works as expected : it doesn't get a lease. but it then logs as expected : Jan 13 21:54:35 xxx dhcpcd[172]: dhcpStart: ioctl SIOCGIFHWADDR: No such device

Sad Vaio 505V + OvisLink LFS PCM32 doesn't work

Date: 2000, Jan 18
From: Klaus Kudielka klaus.kudielka

Hello,

I have a Sony Vaio 505V and recently bought an OvisLink
LFS PCM 32 cardbus card, since it is listed in
SUPPORTED.CARDS.

Needless to say, my first try was rather unsuccessfull :-(
linux-2.2.14, pcmcia-cs-3.1.8.
Neither transmitting nor receiving works. The RX counters
ifconfig reports just stay zero, likewise the TX counters.
Only TX errors is incremented now and then. The card is
attached to a 10Mbit/s hub.

Linux PCMCIA Card Services 3.1.8
  kernel build: 2.2.14 #3 Tue Jan 18 15:46:42 UTC 2000
  options:  [pci] [cardbus] [apm]
Intel PCIC probe: 
  Ricoh RL5C475 PCI-to-CardBus at bus 0 slot 10, mem 0x68000000, 1 socket
    host opts [0]: [isa irq] [io 3/6/1] [mem 3/6/1] [no pci irq] [lat 168/176] [bus 32/34]
    ISA irqs (default) = 3,4,7,10,11,12,15 polling interval = 1000 ms
cs: IO port probe 0x1000-0x17ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x170-0x177 0x370-0x37f 0x388-0x38f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: cb_alloc(bus 32): vendor 0x1011, device 0x0019
cs: cb_config(bus 32)
  fn 0 bar 1: io 0x400-0x47f
  fn 0 bar 2: mem 0x600c0000-0x600c03ff
  fn 0 rom: mem 0x60080000-0x600bffff
cs: cb_enable(bus 32)
  bridge io map 0 (flags 0x21): 0x400-0x47f
  bridge mem map 0 (flags 0x1): 0x60080000-0x600c0fff
tulip_attach(bus 32, function 0)
tulip.c:v0.91 4/14/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
eth0: Digital DS21143 Tulip rev 65 at 0x400, 00:E0:98:12:F9:9D, IRQ 10.
eth0:  EEPROM default media type Autosense.
eth0:  Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block.
eth0:  MII transceiver #0 config 3000 status 7809 advertising 01e1.
eth0: Tx hung, 11 vs. 0.
eth0: Tx hung, 14 vs. 0.

(now executing cardctl eject)

tulip_detach(eth0)
cs: cb_disable(bus 32)
cs: cb_release(bus 32)
cs: cb_free(bus 32)

Any idea?

-Klaus

None Maybe try the latest beta?

Re: Sad Vaio 505V + OvisLink LFS PCM32 doesn't work (Klaus Kudielka)
Date: 2000, Jan 21
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Try the 18-Jan-00 beta driver package on sourceforge.org in
/pcmcia/NEW.

-- Dave

Sad 18-Jan-00 doesn't help.

Re: None Maybe try the latest beta? (David Hinds)
Date: 2000, Jan 21
From: Klaus Kudielka klaus.kudielka

Here are the messages, with options tulip_cb debug=3:

Linux PCMCIA Card Services 3.1.9
  kernel build: 2.2.14 #3 Tue Jan 18 15:46:42 UTC 2000
  options:  [pci] [cardbus] [apm]
PCI routing table version 1.0 at 0xfdf80
Intel PCIC probe: 
  Ricoh RL5C475 PCI-to-CardBus at bus 0 slot 10, mem 0x68000000, 1 socket
    host opts [0]: [isa irq] [io 3/6/1] [mem 3/6/1] [no pci irq] [lat 168/176] [bus 32/34]
    ISA irqs (default) = 3,4,7,10,11,15 polling interval = 1000 ms
cs: IO port probe 0x1000-0x17ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x170-0x177 0x370-0x37f 0x388-0x38f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: cb_alloc(bus 32): vendor 0x1011, device 0x0019
cs: cb_config(bus 32)
  fn 0 bar 1: io 0x400-0x47f
  fn 0 bar 2: mem 0x600c0000-0x600c03ff
  fn 0 rom: mem 0x60080000-0x600bffff
cs: cb_enable(bus 32)
  bridge io map 0 (flags 0x21): 0x400-0x47f
  bridge mem map 0 (flags 0x1): 0x60080000-0x600c0fff
tulip_reap()
tulip_attach(bus 32, function 0)
tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
eth0: Digital DS21143 Tulip rev 65 at 0x400, 00:E0:98:12:F9:9D, IRQ 10.
eth0:  EEPROM default media type Autosense.
eth0:  MII interface PHY 0, setup/reset sequences 0/0 long, capabilities e0 78.
eth0:  Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block.
eth0:  Advertising 01e1 on PHY 0 (0).
eth0: Using media type MII, CSR12 is c6.
eth0:  MII transceiver #0 config 3000 status 7809 advertising 01e1.
eth0: tulip_open() irq 10.
eth0:  Advertising 01e1 on PHY 0 (0).
eth0: Using media type MII, CSR12 is c6.
eth0: Using MII transceiver 0, status 7809.
eth0: Done tulip_open(), CSR0 f8a08000, CSR5 f0120000 CSR6 b20e2002.
eth0: 21143 negotiation status 000000c6, MII.
eth0: MII status 7829, Link partner report 0021.
eth0: Tx hung, 11 vs. 0.
eth0: Transmit timeout using MII device.

Ok 3.1.10 works

Re: Sad 18-Jan-00 doesn't help. (Klaus Kudielka)
Date: 2000, Feb 07
From: Klaus Kudielka klaus.kudielka

Subject says it all. The funny part is that 27-Jan-00 also started working all of a sudden. I swear it didn't work one week ago. Same BIOS settings, same network connection. Strange, but, unless the problems appear again, let's say they are solved.

-Klaus

Question Problems with Kingmax KEN0100-DF Ethernet card

Date: 2000, Jan 20
From: Albio alby

My Kingmax KEN0100-DF Ethernet card is recognized by cardmngr using the module tulip_cb, but I can't access the network (with ping for example).

I controlled several times the network configuration: IP address, DNS, Gateway etc.

Giving ifconfig the eth0 is up; the ip number and netmask are correctly setted.

Can someone help me? Thanks

None Again... system log messages??

Re: Question Problems with Kingmax KEN0100-DF Ethernet card (Albio)
Date: 2000, Jan 20
From: David Hinds <dhinds@pcmcia.sourceforge.org>

As I seem to say in response to most problem reports.

System log messages would be helpful.  It would also be helpful to say
what kind of laptop you're using.

-- Dave

Note Sys Log messages

Re: None Again... system log messages?? (David Hinds)
Date: 2000, Jan 21
From: Albio alby

System: Geo Itinera CPU AMD II 366

Red Hat 6.0

PCMCIA Card Services 3.0.9

Jan 21 21:52:01 impacomp kernel:   kernel build: 2.2.5-15 #1 Mon Apr 19 22:21:09 EDT 1999 
Jan 21 21:52:01 impacomp kernel:   options:  [pci] [cardbus] [apm] 
Jan 21 21:52:01 impacomp kernel: Intel PCIC probe:  
Jan 21 21:52:01 impacomp kernel:   TI 1250A PCI-to-CardBus at bus 0 slot 3, mem 0x68000000, 2 sockets 
Jan 21 21:52:01 impacomp kernel:     host opts [0]: [pwr save] [serial pci & irq] [no pci irq] [lat 168/176] [bus 32/34] 
Jan 21 21:52:01 impacomp kernel:     host opts [1]: [pwr save] [serial pci & irq] [no pci irq] [lat 168/176] [bus 35/37] 
Jan 21 21:52:01 impacomp kernel:     ISA irqs (scanned) = 3,4,7,9,10,11 status change on irq 11 
Jan 21 21:52:01 impacomp cardmgr[2554]: starting, version is 3.0.14
Jan 21 21:52:01 impacomp cardmgr[2554]: watching 2 sockets
Jan 21 21:52:01 impacomp cardmgr[2554]: Card Services release does not match!
Jan 21 21:52:01 impacomp kernel: cs: IO port probe 0x1000-0x17ff: clean. 
Jan 21 21:52:01 impacomp kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22f 0x330-0x337 0x378-0x37f 0x4d0-0x4d7 
Jan 21 21:52:01 impacomp kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
Jan 21 21:52:01 impacomp cardmgr[2554]: initializing socket 0
Jan 21 21:52:01 impacomp cardmgr[2554]: socket 0: CardBus
Jan 21 21:52:02 impacomp cardmgr[2554]: executing: 'insmod /lib/modules/2.2.5-15/pcmcia/cb_enabler.o'
Jan 21 21:52:02 impacomp cardmgr[2554]: executing: 'insmod /lib/modules/2.2.5-15/pcmcia/tulip_cb.o'
Jan 21 21:52:02 impacomp kernel: cs: cb_config(bus 32): vendor 0x1011, device 0x0019 
Jan 21 21:52:02 impacomp kernel:   fn 0 bar 1: io 0x280-0x2ff 
Jan 21 21:52:02 impacomp kernel:   fn 0 bar 2: mem 0x600c0000-0x600c03ff 
Jan 21 21:52:02 impacomp kernel:   fn 0 rom: mem 0x60080000-0x600bffff 
Jan 21 21:52:02 impacomp kernel: tulip_attach(bus 32, function 0) 
Jan 21 21:52:02 impacomp kernel: tulip.c:v0.89H 5/23/98 becker@cesdis.gsfc.nasa.gov 
Jan 21 21:52:02 impacomp kernel: eth0: Digital DS21142/3 Tulip at 0x280, 00 a0 0c 90 4f e3, IRQ 3. 
Jan 21 21:52:02 impacomp kernel: eth0:  EEPROM default media type Autosense. 
Jan 21 21:52:02 impacomp kernel: eth0:  Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block. 
Jan 21 21:52:02 impacomp kernel: eth0:  Index #1 - Media 10baseT-FD (#4) described by a 21142 Serial PHY (2) block. 
Jan 21 21:52:02 impacomp kernel: eth0:  Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4) block. 
Jan 21 21:52:02 impacomp kernel: eth0:  Index #3 - Media 100baseTx-FD (#5) described by a 21143 SYM PHY (4) block. 
Jan 21 21:52:02 impacomp cardmgr[2554]: executing: './network start eth0'
Jan 21 21:52:08 impacomp kernel: eth0: 21142 100baseTx link beat good. 

**********

then I ping my_nearest_neighboor in the LAN

Jan 21 21:53:15 impacomp kernel: eth0: 21140 transmit timed out, status f0120000, SIA 000000c5 ffff0001 fffbff7f 8ff10008, resetting... 
Jan 21 21:53:15 impacomp kernel: eth0: transmit timed out, switching to 100baseTx media. 
Jan 21 21:53:20 impacomp kernel: eth0: 21142 100baseTx sensed media. 
Jan 21 21:53:20 impacomp kernel: eth0: 21140 transmit timed out, status f8128000, SIA 000000c6 ffff0001 fff87f3d 8ff10000, resetting... 
Jan 21 21:53:20 impacomp kernel: eth0: transmit timed out, switching to 10baseT media. 
Jan 21 21:53:25 impacomp kernel: eth0: 21140 transmit timed out, status f0120000, SIA 000000c6 ffff0000 fff8ffff 8ff10000, resetting... 
Jan 21 21:53:25 impacomp kernel: eth0: transmit timed out, switching to 100baseTx media. 

......

None Driver upgrade?

Re: Note Sys Log messages (Albio)
Date: 2000, Jan 22
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You should probably try upgrading your PCMCIA drivers.  It looks like
maybe you've already tried to do this??  (your cardmgr is version
3.0.14, but your kernel modules are version 3.0.9)

Newer driver packages (3.0.14 and later) have a newer version of the
tulip_cb module.

-- Dave

None It doesn't work

Re: None Driver upgrade? (David Hinds)
Date: 2000, Jan 22
From: Albio alby

I istalled the package pcmcia-cs3.1.6.tar.gz

The card is recognized again, but I can't ping anywhere...

There is some other solution?

Thanks

None Re: It doesn't work

Re: None It doesn't work (Albio)
Date: 2000, Jan 24
From: David Hinds <dhinds@pcmcia.sourceforge.org>

It would again be useful to post system log messages.

Why did you pick 3.1.6?

It could be an interrupt conflict.  Try excluding interrupts in
/etc/pcmcia/config.opts, starting with irq 3, and see if that helps.

-- Dave

None It's doesn't work again.

Re: None Re: It doesn't work (David Hinds)
Date: 2000, Jan 28
From: Albio alby

> why did you pick 3.1.6?

Which version have I to pick ?

> It could be an interrupts. It could be an interrupt >conflict. Try excluding interrupts in >/etc/pcmcia/config.opts, 
> starting with irq 3, and see if that helps.

I tried to exclude irq 3 and then 9 but it doesn't work ...

A.

Ok It works !!!!

Re: None It's doesn't work again. (Albio)
Date: 2000, Feb 05
From: Albio alby

My CardBus Kingmax 10/100 KEN0100-DF works with pcmcia-cs-3.1.10 !!!!

Thank you Dave

Albio

Question Socket EA System Hang

Date: 2000, Jan 21
From: Robert Sanderson azaroth

Hi all, I've been trying unsuccessfully to get my eth0 card working with my new laptop.

System:  Dell Latitude CPi R400GT
PC Card:  Socket EA Ethernet
Kernel:  2.2.14
PCMCIA:  3.1.8
Changes:  Added exit 0; in pcmcia/network to prevent hangs (see below)
Messages:

------------------------
  
initializing socket 1
eth0: NE2000 Compatible: io 0x300 irq 3 auto xcvr hw_addr 00:C0:1B:00:5E:27
socket 1: Socket EA Ethernet
executing insmod /lib/modules/2.2.14/net/8390.o
executing insmod /lib/modules/2.2.14/pcmcia/pcnet_cs.o
executing ./network start eth0

----------------------------

At which point, the system hangs until the card is ejected.
When it is, the following messages are given:

----------------------------
Hw. address read/write mismap 0
Hw. address read/write mismap 1
Hw. address read/write mismap 2
Hw. address read/write mismap 3
Hw. address read/write mismap 4
Hw. address read/write mismap 5
eth0: interupt from stopped card

----------------------------

The card worked fine in my old laptop (Compaq Aero C33,
running linux 2.0.0), and the my modem card (psion dacom gold
card) works fine in the Dell as well as the Compaq.

In the documentation, it says that it's necessary to use
ifport to manually set the interface for EA cards - doing this
or not seems to make no difference, the system still hangs
with the same errors.

Occaisonally it won't hang when the interface is brought up,
but will on receiving any traffic. In this scenario the
messages are:

--------------------------------------

eth0: mismatched read page pointers 0 vs  e.
eth0: mismatched read page pointers 0 vs  ff.
eth0: mismatched read page pointers 0 vs  ff.
eth0: mismatched read page pointers 0 vs  ff.
...
eth0: unexpected TX-done interrupt, lasttx=0.
eth0: too much work at interrupt, status 0xff
eth0: interrupt from stopped card

---------------------------------------

Other miscellaneous messages from when the card is inserted 
but nothing has been done to it:

'probe' gives:

PCI bridge probe:  TI 1255 found, 2 sockets. 

'cardctl ident' gives:

product info: Socket Communications Inc, Socket EA PCMCIA LAN Adapter
Revision E, Ethernet ID 00c01b005e27
manfid: 0x0104, 0x000
function: 6 (network)

'cardctl status' gives:

5V 16-bit PC Card
funciton 0: [ready]   

------

This looks like a driver problem, does anyone have any 
information or ideas about it?

Thanks,

Rob Sanderson

None Resource conflict?

Re: Question Socket EA System Hang (Robert Sanderson)
Date: 2000, Jan 21
From: David Hinds <dhinds@pcmcia.sourceforge.org>

My first guess would be that this is either an IO port or interrupt
conflict.

Since you've already built 3.1.8, I'd try re-building it with "PnP
BIOS support" switched on, and see if that makes a difference: this
should make PCMCIA do a better job of avoiding resource conflicts.

Or, you can try excluding port 0x300-0x31f and irq 3 in
/etc/pcmcia/config.opts.

-- Dave

More Resource Conflict, Socket EA

Re: None Resource conflict? (David Hinds)
Date: 2000, Jan 24
From: Robert Sanderson azaroth

> Or, you can try excluding port 0x300-0x31f and irq 3 in
> /etc/pcmcia/config.opts.

I had tried excluding IRQ 3 for that reason before, but not the port. Unfortunately the same results happen with the port excluded as well. :(

In the docs it says to set ifport. The card reports as 'auto' in the syslog, but trying to set it to 10baseT results in the same hang as touching the card any other way. Is this significant perhaps?

Or any other suggestions?

Many thanks,

Rob Sanderson

More Socket EA hang,

Re: More Resource Conflict, Socket EA (Robert Sanderson)
Date: 2000, Jan 25
From: Robert Sanderson azaroth

Here, as requested, are the pcmcia boot time messages.

kernel:  Linux PCMCIA Card Services 3.1.8
kernel:    kernel build: 2.2.14 #1 Thu Jan 20 14:27:00 GMT
kernel:    options [pci] [cardbus] [apm]
kernel:  Intel PCIC probe:
kernel:    TI 1225 PCI-to-CardBus at bus 0 slot 3, mem 0x68000000, 2 sockets
kernel:   host opts [0]: [ring] [serial pci & irq] [no pci irq] [lat 32/176] [bus 32/34]
kernel:   host opts [1]: [ring] [serial pci & irq] [no pci irq] [lat 32/176] [bus 35/37]
pcmcia:  starting PCMCIA services:
pcmcia:  cardmgr.
rc:  starting pcmcia succeeded
cardmgr[332]: starting, version is 3.1.8
cardmgr[332]: watching 2 sockets
kernel: cs: IO port probe 0x1000-0x17ff: clean
kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x4d0-0x4d7


Thanks,

Rob

Question Problems starting dhclient

Date: 1999, Dec 05
From: Stefan Hahne loki

I have a Toshiba Satellite 2550CDT, Kernel 2.2.13 and pcmcia-cs-3.1.5.
Compiling and installation works fine and ifconfig
shows:
	"eth0 Link encap:Ethernet	HWAddr 00:50:22:20:3F:A9
	 unspec addr:[NONE SET] Bcast:[NONE SET] MASK:[NONE SET]
	 ..."
but the dhcp-client exit with "dhclient: eth0: not found" at
boot time and whenever I insert the card!!

Any suggestions?
Thanks in advance!

None Check your system log, etc

Re: Question Problems starting dhclient (Stefan Hahne)
Date: 2000, Jan 05
From: David Hinds <dhinds@pcmcia.sourceforge.org>

My first suggestion would be to try to verify if the card works
without DHCP, then try experimenting with DHCP.  What happens if you
invoke dhclient by hand, after inserting the card?

Also, you didn't mention what kind of card this is.  It also might be
useful to check your system log for error messages.

-- Dave

Question Trust Netlink Combi don't respond to ping

Date: 2000, Jan 06
From: A. Bosio torello

I'm using an Acer Travelmate 512T, with debian slink,
Linux 2.2.13, pcmcia-cs 3.1.8.

The card is a Trust Netlink Combi, and it is recognized
as NE2000 Compatible.

This is the output of "ifconfig eth0":

eth0      Link encap:Ethernet  HWaddr 00:80:C8:8B:5C:9E  
          inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          Interrupt:11 Base address:0x300

and this is the output of "netstat -r":
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
localnet        *               255.255.255.0   U         0 0          0 eth0

If I do a ping from the Acer to another host, or from another
host to the Acer, noone respond.

This is the output of "tcpdump -i eth0" on the Acer, doing
a ping from the Acer to another host in the net (mu is
the Acer Travelmate, yang is the other computer).

11:07:35.711389 mu.change.fake > yang.change.fake: icmp: echo request
11:07:36.703568 mu.change.fake > yang.change.fake: icmp: echo request
11:07:40.703457 arp who-has yang.change.fake tell mu.change.fake
11:07:41.703456 arp who-has yang.change.fake tell mu.change.fake
11:07:42.703449 arp who-has yang.change.fake tell mu.change.fake
11:07:43.703448 arp who-has yang.change.fake tell mu.change.fake

And so on.
This is the output for a tcpdump on the Acer for a ping from an host in the net to the Acer:
11:06:54.933617 arp who-has mu.change.fake tell yang.change.fake
11:06:54.933719 arp reply mu.change.fake is-at 0:80:c8:8b:5c:9e
11:06:55.933600 arp who-has mu.change.fake tell yang.change.fake
11:06:55.933667 arp reply mu.change.fake is-at 0:80:c8:8b:5c:9e
11:06:56.933594 arp who-has mu.change.fake tell yang.change.fake
11:06:56.933640 arp reply mu.change.fake is-at 0:80:c8:8b:5c:9e

And this is the output for the same ping on the other host:
12:06:37.406405 arp who-has mu tell yang
12:06:38.400825 arp who-has mu tell yang
12:06:39.400781 arp who-has mu tell yang


Another thing: the "collisions" led of the Trust Netlink Combi blinks a lot...

So the problem is: am I an idiot on configuring this network card or does the card have some problems?

Thanks.

None The usual: system log messages??

Re: Question Trust Netlink Combi don't respond to ping (A. Bosio)
Date: 2000, Jan 06
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Does "ifconfig eth0" always show no packets sent or received, even
after trying the pings?  I'm not familiar enough with tcpdump to know
how to interpret that output, but it does appear that some packets are
being sent and received, right?

-- Dave

Question Trouble with Linksys Ethernet Card

Date: 2000, Jan 26
From: Mike jabbera

I am trying to get this card working, and every time i insert it i get the following error.

eth0: pcnet_reset_8390() did not complete. pcnet_cs: unable to read hardware net address

Anyone give me a hand with this?

None More system log messages?

Re: Question Trouble with Linksys Ethernet Card (Mike)
Date: 2000, Jan 27
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Without more context, I have no idea.  It would also be useful to say
what kind of laptop this is.

-- Dave

Question Dual PCMCIA NIC system (Linksys plus NDC ) time outs and lost interrupts

Date: 2000, Jan 29
From: Dale moberg dmoberg

Report on dual PCMCIA MIC interface lost interrupt on Hewlett-Packard Omnibook 5500 CT

Second card (Linksys) yields time outs waiting for device to not be busy? First card working fine.

Message from log indicating what seems to be the core problem is

Jan 29 11:12:33 redhatomni kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x2, t=1000.

I enclose outputs from uname, lsmod, proc/interrupts, cardctl, ifconfig, lsmod, and startup log for pcmcia modules.

[root@redhatomni net]# uname -a
Linux redhatomni 2.2.12-20 #1 Mon Sep 27 10:25:54 EDT 1999 i586 unknown
[root@redhatomni net]# cardctl -V
cardctl version 3.0.14
[root@redhatomni net]# lsmod
Module                  Size  Used by
parport_pc              5620   0  (unused)
parport                 7124   0  [parport_pc]
nls_iso8859-1           2020   1  (autoclean)
pcnet_cs                7572   2 
8390                    5920   0  [pcnet_cs]
ds                      5740   2  [pcnet_cs]
i82365                 22640   2 
pcmcia_core            39912   0  [pcnet_cs ds i82365]
[root@redhatomni net]# cat /proc/interrupts
           CPU0       
  0:    7572752          XT-PIC  timer
  1:      31645          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  3:       8964          XT-PIC  pcnet_cs
  5:          0          XT-PIC  pcnet_cs
  8:          1          XT-PIC  rtc
 12:     255634          XT-PIC  PS/2 Mouse
 13:          1          XT-PIC  fpu
 14:     561531          XT-PIC  ide0
 15:     601841          XT-PIC  ide1
NMI:          0
[root@redhatomni net]# cardctl config
Socket 0:
  Vcc = 5.0, Vpp1 = 0.0, Vpp2 = 0.0
  Interface type is memory and I/O
  IRQ 3 is exclusive, level mode, enabled
  Function 0:
    Config register base = 0x03f8
      Option = 0x60, status = 0000
    I/O window 1: 0x0300 to 0x031f, auto sized
Socket 1:
  Vcc = 5.0, Vpp1 = 0.0, Vpp2 = 0.0
  Interface type is memory and I/O
  IRQ 5 is exclusive, level mode, enabled
  Function 0:
    Config register base = 0x0fd0
      Option = 0x43, status = 0000, copy = 0000
    I/O window 1: 0x0340 to 0x035f, auto sized
[root@redhatomni net]# cardctl status
Socket 0:
  5V 16-bit card present
  Function 0: ready
Socket 1:
  5V 16-bit card present
  Function 0: ready

[root@redhatomni pcmcia]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:80:C6:F6:8E:1F  
          inet addr:192.168.88.149  Bcast:192.168.88.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8306 errors:0 dropped:0 overruns:0 frame:21
          TX packets:927 errors:0 dropped:0 overruns:0 carrier:0
          collisions:1 txqueuelen:100 
          Interrupt:3 Base address:0x300 

eth1      Link encap:Ethernet  HWaddr 00:E0:98:06:AC:30  
          inet addr:204.210.245.55  Bcast:204.210.245.255  Mask:255.255.255.0
          UP BROADCAST RUNNING  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:2 overruns:0 frame:0
          TX packets:0 errors:45 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          Interrupt:5 Base address:0x340 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:247 errors:0 dropped:0 overruns:0 frame:0
          TX packets:247 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 

[root@redhatomni pcmcia]# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 255.255.255.255 * 255.255.255.255 UH 0 0 0 eth0 204.210.245.55 * 255.255.255.255 UH 0 0 0 eth1 192.168.88.149 * 255.255.255.255 UH 0 0 0 eth0 204.210.245.0 * 255.255.255.0 U 0 0 0 eth1 localnet * 255.255.255.0 U 0 0 0 eth0 127.0.0.0 * 255.0.0.0 U 0 0 0 lo

Startup from /var/log/debug

Jan 28 20:46:59 redhatomni pcmcia: Starting PCMCIA services:
Jan 28 20:46:59 redhatomni pcmcia:  modules
Jan 28 20:46:59 redhatomni kernel: Linux PCMCIA Card Services 3.0.14 
Jan 28 20:46:59 redhatomni kernel:   kernel build: 2.2.12-20 #1 Mon Sep 27 10:25:54 EDT 1999 
Jan 28 20:46:59 redhatomni kernel:   options:  [pci] [cardbus] [apm] 
Jan 28 20:46:59 redhatomni kernel: Intel PCIC probe:  
Jan 28 20:46:59 redhatomni kernel:   Cirrus PD6729 PCI-to-PCMCIA at bus 0 slot 3, port 0x3e0, 2 sockets 
Jan 28 20:46:59 redhatomni kernel:     host opts [0]: [ring] [1/5/0] [1/20/0] 
Jan 28 20:47:00 redhatomni kernel:     host opts [1]: [ring] [1/5/0] [1/20/0] 
Jan 28 20:47:00 redhatomni kernel:     ISA irqs (default) = 3,4,5,7,9,11,12 polling interval = 1000 ms 
Jan 28 20:46:59 redhatomni pcmcia:  cardmgr.
Jan 28 20:46:59 redhatomni cardmgr[367]: starting, version is 3.0.14
Jan 28 20:47:00 redhatomni rc: Starting pcmcia succeeded
Jan 28 20:47:01 redhatomni cardmgr[367]: watching 2 sockets
Jan 28 20:47:01 redhatomni kernel: cs: IO port probe 0x1000-0x17ff: clean. 
Jan 28 20:47:01 redhatomni kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22f 0x330-0x337 0x378-0x37f 0x388-0x38f 0x3b0-0x3ff 0x480-0x48f 
Jan 28 20:47:01 redhatomni kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
Jan 28 20:47:01 redhatomni cardmgr[367]: initializing socket 0
Jan 28 20:47:01 redhatomni kernel: cs: memory probe 0x0d0000-0x0dffff: clean. 
Jan 28 20:47:01 redhatomni cardmgr[367]: socket 0: NDC Instant-Link Ethernet
Jan 28 20:47:01 redhatomni inet: inetd startup succeeded
Jan 28 20:47:02 redhatomni cardmgr[367]: executing: 'insmod /lib/modules/r[367]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/pcnet_cs.o'
Jan 28 20:47:02 redhatomni kernel: eth0: NE2000 Compatible: io 0x300, irq 3, hw_addr 00:80:C6:F6:8E:1F 
Jan 28 20:47:02 redhatomni cardmgr[367]: executing: './network start eth0'
Jan 28 20:47:03 redhatomni lpd: lpd startup succeeded
Jan 28 20:47:03 redhatomni keytable: Loading keymap: 
Jan 28 20:47:03 redhatomni keytable: Loading system font: 
Jan 28 20:47:03 redhatomni rc: Starting keytable succeeded
Jan 28 20:47:04 redhatomni cardmgr[367]: initializing socket 1
Jan 28 20:47:04 redhatomni cardmgr[367]: socket 1: NE2000 Compatible Ethernet
Jan 28 20:47:04 redhatomni kernel: eth1: NE2000 Compatible: io 0x340, irq 5, hw_addr 00:E0:98:06:AC:30 
Jan 28 20:47:04 redhatomni cardmgr[367]: executing: './network start eth1'

[omitted stuff. Now trying to ping hosts on immediate segment that eth1 sits on]

[these messages produced because device busy flag set within the 8390 module . The TSR and ISR values are in the header file, 8390.h Check 8390.c to find the format code for this printk message.

A 0x3 value seems to be a sum of ok values. So the device is flagged busy but the interrupt and transmit status registers do not appear to give anything too helpful. No other errors found. Notice that the ifconfig message has all TX errors for eth1. Is there an option I need to set?

eth0 is working fine on its segment. Can ping localhost and the address ifconfiged to the device.204.210.245.55

#

[root@redhatomni net]# Jan 29 11:02:58 redhatomni kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=953.

Jan 29 11:03:08 redhatomni kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=1000. 
Jan 29 11:03:48 redhatomni last message repeated 4 times
Jan 29 11:03:58 redhatomni kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3t=t=1000. 
Jan 29 11:12:13 redhatomni kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=49500. 
Jan 29 11:12:23 redhatomni kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x2, t=1000. 
Jan 29 11:12:33 redhatomni kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x2, t=1000. 
Jan 29 11:13:28 redhatomni kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=5500. 
Jan 29 11:13:38 redhatomni kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=1000. 
Jan 29 11:13:58 redhatomni last message repeated 2 times

None Sounds like a classic interrupt conflict

Re: Question Dual PCMCIA NIC system (Linksys plus NDC ) time outs and lost interrupts (Dale moberg)
Date: 2000, Jan 30
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You have an interrupt conflict with some other device on irq 5.  The
PCMCIA-HOWTO actually even describes this exact scenario (where you've
got two cards that each work separately, but together, only the first
one works).

-- Dave

Ok OK, I guess next time I will just ignore proc/interruptsI

Re: None Sounds like a classic interrupt conflict (David Hinds)
Date: 2000, Jan 30
From: Dale moberg dmoberg

I did see that the case matched the HOWTO info, but I did not see any interrupt conflict in /proc/interrupt. (I now see I was too gullible about this info...)

I changed the irq_list in the pcmcia start script, and got the second card to work.

Maybe you should emphasize that the proc/interrupt info may miss a system's interrupt. I reread and found at the end the HOWTO's warning that I had missed (because pcmcia seemed to be probing ok in that it assigned IRQs and loaded...)

"Depending on system design, an inactive device can still occupy an interrupt and cause trouble .." That was true here. Thanks

Question Cardbus Tulip card works unreliably (system crash)

Date: 2000, Feb 03
From: <rolf.fiedler@ferrari.de>

I hvae a cardbus tulip based 10/100 eth card, and it is detected by the pcmcia core and the proper drivers are loaded.

The system is a palmax pd1000 running 2.2.14 with pcmcia 3.1.9.

once the card is inserted, it is detected and ifconfig and route is done. I can ping the network (reliably). I can do telnet and everything that does not transfer a lot of data.

However, if I try to transfer data (like a ftp download) the whole system freezes and I have to turn it off.

I don't know how to debug the problem, since the system crashes.

An ne2000 compatible ethernet card works like a charm, however it is a friend's card :-(.

On the cardbus card it says "Gericom Cardbus 10/100 Fast Ethernet"

I have tried to play around with the resource info in the pcmcia config., however without success (same behaviour). I have tried a 2.3.3? kernel, same result.

Any hints?

None System log messages?

Re: Question Cardbus Tulip card works unreliably (system crash)
Date: 2000, Feb 03
From: David Hinds <dhinds@pcmcia.sourceforge.org>

It is often useful to include system log messages with bug reports.

The PCMCIA-HOWTO has some instructions for debugging system crashes,
which may yield some additional information.

-- Dave

Feedback sys log messages

Re: None System log messages? (David Hinds)
Date: 2000, Feb 04
From: <rolf.fiedler@ferrari.de>

you asked for it... here it comes:

... while booting .... Feb 1 22:07:59 mini kernel: EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended

Feb  1 22:07:59 mini kernel: Linux PCMCIA Card Services 3.1.9
Feb  1 22:07:59 mini kernel:   kernel build: 2.2.14 #20 Die Feb 1 19:33:28
CET 2000
Feb  1 22:07:59 mini kernel:   options:  [pci] [cardbus] [apm]
Feb  1 22:07:59 mini kernel: PCI routing table version 1.0 at 0xfdf30
Feb  1 22:07:59 mini kernel:   unknown PCI interrupt router 1078:0002
Feb  1 22:07:59 mini kernel: Intel PCIC probe:
Feb  1 22:07:59 mini kernel:   TI 1220 PCI-to-CardBus at slot 00:0b, mem 0x68000000
Feb  1 22:07:59 mini kernel:     host opts [0]: [isa irq] [no pci irq] [lat 64/176] [bus 32/34]
Feb  1 22:07:59 mini kernel:     host opts [1]: [isa irq] [no pci irq] [lat 64/176] [bus 35/37]
Feb  1 22:07:59 mini kernel:     ISA irqs (scanned) = 3,4,10 polling interval = 1000 ms
Feb  1 22:07:59 mini kernel: cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
Feb  1 22:07:59 mini kernel: cs: IO port probe 0x0800-0x08ff: clean.
Feb  1 22:07:59 mini kernel: cs: IO port probe 0x0100-0x04ff: excluding
0x220-0x22f 0x330-0x337 0x378-0x37f 0x388-0x38f 0x398-0x39f 0x480-0x48f 0x4d0-0$
Feb  1 22:07:59 mini kernel: cs: IO port probe 0x0a00-0x0aff: excluding 0xaf8-0xaff
Feb  1 22:08:00 mini crond: crond startup succeeded
Feb  1 22:08:01 mini inet: inetd startup succeeded
Feb  1 22:08:02 mini xntpd: xntpd startup succeeded
... -> card insertion
Feb  1 22:10:53 mini cardmgr[204]: initializing socket 0
Feb  1 22:10:53 mini cardmgr[204]: socket 0: Linksys EtherFast 10/100
Feb  1 22:10:53 mini kernel: cs: cb_alloc(bus 32): vendor 0x1011, device 0x0019$
Feb  1 22:10:53 mini cardmgr[204]: executing: 'insmod /lib/modules/2.2.14/pcmcia
/cb_enabler.o' Feb 1 22:10:53 mini cardmgr[204]: + /lib/modules/2.2.14/pcmcia/cb_enabler.o: a$ module named cb_enabler already exists
Feb  1 22:10:53 mini cardmgr[204]: insmod exited with status 1
Feb  1 22:10:53 mini cardmgr[204]: executing: 'modprobe cb_enabler'
Feb  1 22:10:53 mini kernel: cs: cb_config(bus 32)
Feb  1 22:10:53 mini kernel:   fn 0 bar 1: io 0x100-0x17f
Feb  1 22:10:53 mini kernel:   fn 0 bar 2: mem 0x600c0000-0x600c03ff
Feb  1 22:10:53 mini kernel:   fn 0 rom: mem 0x60080000-0x600bffff
Feb  1 22:10:53 mini kernel: tulip_attach(bus 32, function 0)
Feb  1 22:10:53 mini kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov
Feb  1 22:10:53 mini kernel: eth0: Digital DS21143 Tulip rev 65 at 0x100, 00:E0:98:71:CD:61, IRQ 3.
Feb  1 22:10:53 mini kernel: eth0:  EEPROM default media type Autosense.
Feb  1 22:10:53 mini kernel: eth0:  Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block.
Feb  1 22:10:53 mini kernel: eth0:  MII transceiver #0 config 3000 status 7809 advertising 01e1.
Feb  1 22:10:54 mini cardmgr[204]: executing: './network start eth0'
Feb  1 22:12:19 mini xntpd[345]: synchronized to LOCAL(0), stratum=10
Feb  1 22:12:19 mini xntpd[345]: kernel pll status change 89

-> crash happened here
-> next boot
Feb  2 08:33:11 mini syslogd 1.3-3: restart.
Feb  2 08:33:11 mini syslog: syslogd startup succeeded
Feb  2 08:33:11 mini syslog: klogd startup succeeded
Feb  2 08:33:11 mini kernel: klogd 1.3-3, log source = /proc/kmsg started.
Feb  2 08:33:11 mini kernel: Inspecting /boot/System.map-2.2.14
Feb  2 08:33:12 mini kernel: Loaded 5942 symbols from /boot/System.map-2.2.14.
Feb  2 08:33:12 mini kernel: Symbols match kernel version 2.2.14.
Feb  2 08:33:12 mini kernel: Loaded 61 symbols from 7 modules.
Feb  2 08:33:12 mini kernel: Linux version 2.2.14 (rfie@server.private.net)
(gcc
 version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #20 Die Feb 1 19:33:28 CET 2000
Feb  2 08:33:12 mini kernel: Console: colour VGA+ 80x25
Feb  2 08:33:12 mini kernel: Calibrating delay loop... 55.50 BogoMIPS
...

As far as I can see from that, the start of the pcmcia modules went ok, and the start of the network (card insertion) was ok. There were no syslog messages related to the system freeze, since the cpu just stopped (no time to write anything).

I am afraid that is not very helpful

More detailed bug report

Re: Question Cardbus Tulip card works unreliably (system crash)
Date: 2000, Feb 07
From: <rolf.fiedler@ferrari.de>

I did some more experiments regarding the previously-mentioned bug.

I tried (kernel/pcmcia) 2.2.14/1.3.9 and 2.2.14/1.3.10 with the same results.

I can insert the card and the network config is done.

I can ping & telnet without crashes. I can do a ftp and everything on the control connection works. If I do a download the system crashed without any messages printed anywhere (irq pending and not handled?).

I thought the packet size is triggering the bug. So I did a ping -s 1500. That works long enough to make experiment boring.

Next theory is the packet rate. What happens if new packets arrive while the previous is not transferred off the DEC-chip yet? I thought a flood ping might show this and it did. A ping -f kills the system after a while (60 seconds or so).

Please note that we are talking about a slow computer here. It is a 166MHz Cyrix MediaGX with only 55bogomips (that is 0.055 bogogips :-).

I will do any experiments that are suggested (well, the ones that seem useful - I will not stand on my head and hold my breath for 30 minutes). who is maintaining the tulip_cb module? I suspect the bug there. What can I do if I have a kernel that I know how to crash reproducable but that just enters an endless loop (irq condition not reset?) or locks the bus or whatever. How do I debug this? I would love some oopses, but I can't get any :-(

Many thanks, Rolf

Warning Problem resolved

Re: Question Cardbus Tulip card works unreliably (system crash)
Date: 2000, Feb 08
From: <rolf.fiedler@ferrari.de>

The Palmax PD1000 mini-notebook requires the setting of

PCIC_OPTS="cb_write_post=0"

in /etc/sysconfig/pcmcia to work reliably with the tulip cardbus driver. Without the option the system will hang if the ethernet packet arrival rate is high.

thank you David!

Rolf

Feedback Problems compiling w/ kernels 2.3.43 and up

Date: 2000, Feb 14
From: Mark Rasmussen sunbane

Has anyone else ran into the roadblock w/ the newer
kernels?  They seemed to have changed the net_device
structure in the kernel (kerneldir/include/linux/netdevice.h)
and it no longer includes tbusy, interrupt, etc. so 
pcmcia won't compile up.  I have ran into this both with
using the standalone pcmcia in the kernel and the pcmcia
as a separate package - tried 3.1.9, 3.1.10...

Any workarounds for this?

Thanks,
Mark

Note Supported?

Date: 2000, Feb 15
From: Alex Pearsall rebelpacket

Hello, I hate to be a bother, but ive read the supported card list, and looked for two pcmcia ethernet cards that i hope are supported. Im not sure, i think one might be supported, but i figure you guys would know better than me. the two cards are: Linksys - Ethernet Card EC2T 10bT UMAX - 250TX 10/100 bT

Any information would be GREATLY appricated. Thanks..

                   -Alex

Question Argosy 10/100 EN-235

Date: 2000, Feb 17
From: Robert Rossmann rbr

I have an Argosy En-235 fast Etherent network card which is not supported be the current pcmcia driver. The en-220 is supported. The cardmgr wirtes the following code into the message log

cardmgr[63]: unsupported card in socket 1

kernel:cs: cb_alloc vendor 0x10ex device 0x8138

cardmgr[63]: no produkt info available

So i have no produkt info and can't set the card by editing the /etc/pcmcia/config file

Any hints pls

Robert

More Argosy 10/100 more info

Re: Question Argosy 10/100 EN-235 (Robert Rossmann)
Date: 2000, Feb 17
From: Robert Rossmann rbr

I insert the memory region 0x5042000-0x50421ff which I found from the Windows driver of these card. Now the output of

cardctl ident is

Socket 1:

produkt info: " ARGOSY", "CardBus Ethernet 10/100 (R5)"

function: 6 (network)

and of

cardctl config is

Socket 1:

Vcc 3.3V Vpp1 3.3V Vpp2 3.3V

interface type is "cardbus"

function 0:

I tried to use this info in the config file but still the card won't work. Must I do anythink else to use a 32bit cardbus card?

thx

Robert

None Re: More: Argosy 10/100 more info

Re: More Argosy 10/100 more info (Robert Rossmann)
Date: 2000, Feb 17
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> 
> I tried to use this info in the config file but still the card won't
> work. Must I do anythink else to use a 32bit cardbus card?

What did you add to the config file, exactly?  (what driver did you
specify?)  You could try either tulip_cb or epic_cb; tulip_cb would be
the more likely guess.  If those don't work, then this card would
appear to use an unsupported CardBus network controller (all the other
PCMCIA network drivers are strictly for 16-bit cards).

-- Dave

More Used both tulip_cb and epic_cb

Re: None Re: More: Argosy 10/100 more info (David Hinds)
Date: 2000, Feb 18
From: Robert Rossmann rbr

Entry in the config file

card "Argosy EN235 Fast Ethernet"
  manfid 0x10ec, 0x8138
  bind "tulip_cb"

output in the message file

Feb 18 07:55:26 armin kernel: Linux PCMCIA Card Services 3.1.3
Feb 18 07:55:26 armin kernel:   kernel build: 2.2.13 #1 Mon Nov 8 18:28:35 GMT 1999
Feb 18 07:55:26 armin kernel:   options:  [pci] [cardbus] [pnp]
Feb 18 07:55:26 armin kernel: PnP: PNP BIOS installation structure at 0xc00ff000
Feb 18 07:55:26 armin kernel: PnP: PNP BIOS version 1.0, entry at e4000:a41, dseg at e4000
Feb 18 07:55:26 armin kernel: PCI routing table version 1.0 at 0xf2bb0
Feb 18 07:55:26 armin kernel:   unknown PCI interrupt router 1045:c558
Feb 18 07:55:26 armin kernel: Intel PCIC probe: 
Feb 18 07:55:26 armin kernel:   TI 1130 PCI-to-CardBus at bus 0 slot 7, mem 0x68000000, 2 sockets
Feb 18 07:55:26 armin kernel:     host opts [0]: [ring] [isa irq] [no pci irq] [lat 168/176] [bus 2/2]
Feb 18 07:55:26 armin kernel:     host opts [1]: [ring] [isa irq] [no pci irq] [lat 168/176] [bus 3/3]
Feb 18 07:55:26 armin kernel:     ISA irqs (scanned) = 7,9,10,11,12 status change on irq 11

The windows CardBus controller uses E/A 1400-14FF memory: 0x5042000-0x5423fff interrupt: 10

must or can I use this info for the Linux cardbus controller?

thx Robert

More More info

Re: More Used both tulip_cb and epic_cb (Robert Rossmann)
Date: 2000, Feb 21
From: Robert Rossmann rbr

When I eject and re-imsert the card the following lines are in the message log.

Feb 21 07:23:16 armin cardmgr[63]: initializing socket 1
Feb 21 07:23:16 armin cardmgr[63]: unsupported card in socket 1
Feb 21 07:23:16 armin kernel: cs: cb_alloc(bus 3): vendor 0x10ec, device 0x8138
Feb 21 07:23:16 armin cardmgr[63]:   no product info available

thx Robert

None You are currently out of luck

Re: More More info (Robert Rossmann)
Date: 2000, Feb 21
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Sorry, I should have looked more closely at your first message.

Linux currently does not support CardBus cards that do not provide any
product info.  There's no way to use this card at this time, even if
it uses a supported chipset.  This may change in the future, but that
is the way it is for now.

-- Dave

Question I get "Network Unreachable" trying to ping others...

Date: 2000, Feb 17
From: Captain Panic panic

I read the PCMCIA-howto and it mentions that if you get a "Network Unreachable" trying to ping others on the LAN it means something with your routing. But I can't figure out what's wrong. Also I can ping myself fine. I have my self as ip 90.0.0.1 set through linuxconf . I am running RH 6.1 on a compaq computer with a 10baseT pcmcia ethernet card (8390.o). Can't seem to figure it out. Below is a copy of route. And ifconfig looks good with itherface eth0 and lo.

Dest Gateway Genmask Flags Iface

90.0.0.1 * 255.255.255.255 UH eth0

90.0.0.0 * 255.0.0.0 U eth0

127.0.0.0 * 255.0.0.0 U lo

Thanks in advance. Bri

Question card works fine, but 'tcpdump' cant see any of the traffic

Date: 2000, Feb 17
From: Ron Flory <ron.flory@adtran.com>

hi-

 I've been using Dave's pcmcia stuff for a while now, (thanks Dave!).

 I have a PII RedHat 6.1 based laptop with a 10/100 network adapater that works just fine, however I'm a developer working with networks and I'd like to use the system for network sniffing.  For some reason, tcpdump is not able to see any of the traffic on eth0, even traffic from this machine.

 tcpdump seems to work file on all my other machines (7-8 of various types), but for some reason its deaf on this one.

 Any hints?  (something in /proc perhaps ?).

 I actually use ethereal as my packet sniffer, however since tcpdump is used by ethereal, and most everybody already has tcpdump, I'll reduce the problem to a single user program.

 Thanks-

ron

More Untitled

Re: Question card works fine, but 'tcpdump' cant see any of the traffic (Ron Flory)
Date: 2000, Feb 17
From: Ron Flory <ron.flory@adtran.com>

David Hinds wrote:
> 
> On Thu, Feb 17, 2000 at 07:10:21AM -0800, Ron Flory wrote:
> >
> >  tcpdump seems to work file on all my other machines (7-8 of various
> > types), but for some reason its deaf on this one.
> 
> What network card are you using?  (which driver is at fault?)

 Hi Dave-

The card is marked:

   Linksys EtherFast 10/100 PC Card
   model: PCMPC100

startup message from syslog:

  NE2000 Compatable: io 0x300, irq 3 ....

its loading the 8390.o module, so its probably another (klunky 'ol) ne2000 clone.

> I thought that most of the drivers implemented promisc support, but I
> can't say I've ever used it myself.

hmmm, good thought. When I startup tcpdump, I don't see the usual "eth0: Promiscuous mode enabled" message.... Apparently the promisc request isn't getting all the way through the driver-

 If it helps, here's some more info:

      kernel: 2.2.14 (unpatched, from master sources)

 Here is slightly filtered syslog:

kernel: unloading PCMCIA Card Services 
kernel: Linux PCMCIA Card Services 3.1.10 
kernel:   kernel build: 2.2.14 #1 Wed Feb 9 10:25:19 CST 2000 
kernel:   options:  [pci] [cardbus] [apm] 
kernel: PCI routing table version 1.0 at 0xf09a0 
kernel: Intel PCIC probe:  
kernel:   TI 1225 PCI-to-CardBus at slot 00:11, mem 0x7fffe000 
kernel:     host opts [0]: [ring] [pci + serial irq] [pci irq 11] [lat
66/176] [bus 2/2] kernel: host opts [1]: [ring] [pci + serial irq] [pci irq 11] [lat 66/176] [bus 3/3] kernel: ISA irqs (scanned) = 3,4,7,9,10,15 PCI status changes cardmgr[788]: starting, version is 3.1.10 cardmgr[788]: watching 2 sockets
kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x1000-0x10ff 
kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x250-0x257
0x260-0x267 0x330-0x337 0x388-0x38f 0x4d0-0x4d7 kernel: cs: IO port probe 0x0a00-0x0aff: clean. cardmgr[788]: initializing socket 0 kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean. cardmgr[788]: socket 0: Linksys EtherFast 10/100 Fast Ethernet cardmgr[788]: executing: 'insmod /lib/modules/2.2.14/net/8390.o' cardmgr[788]: executing: 'insmod /lib/modules/2.2.14/pcmcia/pcnet_cs.o' kernel: eth0: NE2000 Compatible: io 0x300, irq 3, hw_addr 00:E0:98:71:19:03 cardmgr[788]: executing: './network start eth0' kernel: eth0: found link beat

 I appreciate any ideas or info-

 Thanks-

ron

Note Problem with ADDTRON Fast Ethernet card

Date: 2000, Feb 17
From: Andreas-Johann Ulvestad aj

I am currently having problems with my new pcmcia card. It is made by ADDTRON, and I belive it uses an intel chip (pcmcia loads the i82365 module, but it doesn't seem to work - I get 'Delaying eth0 initialization.' when trying to configure the interface.

--LOG--
Linux PCMCIA Card Services 3.1.8
 kernel build: 2.2.15-2.5.0 #1 Sat Feb 5 00:13:43 EST 2000
 options: [pci] [cardbus] [apmd] [pnp]
PnP: PNP BIOS installation structure at 0xc00f7fc0
PnP: PNP BIOS version 1.0, entry at f0000:a954, dseg at 400
PCI routing table version 1.0 at 0xfdf70
  unknown PCI interrupt router 1045:c700
Intel PCIC probe:
  TI 1131 PCI-to-CardBus at bus 0 slot 10, mem 0x68000000, 2 sockets
    host opts: [0]: [ring] [pci + serial irq] [no pci irq] [lat 168/176] [bus 32/34]
     host opts [1]: [ring] [pci + serial irq] [no pci irq] [lat 168/176] [bus 35/37]
     ISA irqs (scanned) = 3,4,7,9 polling interval = 1000 ms
cardmgr[646]: starting, version is 3.1.8
cardmgr[646]: wathcing 2 sockets
kernel: cs: IO port probe 0x1000-0x17ff: clean.
kernel: cs: IO port probe 0x0100-0x04ff: exluding 0x378-0x37f
kernel: cs: IO port probe 0x0a00-0x0aff: clean.
cardmgr[646]: initializing socket 0
kernel: cs: memory probe 0xa000000-0xa0fffff: clean.
cardmgr[646]: unsupported card in socket 0
cardmgr[646]: product info: "PCMCIA", "FastEthernet", "V", "1.0"
cardmgr[646]: manfid: 0x021b, 0x0202 function: 6 (network)

--END LOG--

Any ideas?

None It isn't an Intel network device

Re: Note Problem with ADDTRON Fast Ethernet card (Andreas-Johann Ulvestad)
Date: 2000, Feb 17
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The i82365 module is your socket driver module, not the module for the
card.  No module was loaded for the card itself, because it was not
recognized.

> cardmgr[646]: unsupported card in socket 0
> cardmgr[646]: product info: "PCMCIA", "FastEthernet", "V", "1.0"
> cardmgr[646]: manfid: 0x021b, 0x0202 function: 6 (network)

The obvious thing would be to add:

  card "Addtron Fast Ethernet"
    manfid 0x021b, 0x0202
    bind "pcnet_cs"

to /etc/pcmcia/config, which is what the PCMCIA-HOWTO suggests as a
good guess for unsupported 16-bit ethernet cards.

-- Dave

More Done that, doesn't work

Re: None It isn't an Intel network device (David Hinds)
Date: 2000, Feb 17
From: Andreas-Johann Ulvestad aj

I've done as said, and now get the following:

cardmgr: socket 0: Addtron Fast Ethernet
cardmgr: executing: 'insmod /lib/modules/2.2.15-2.5.0/net/8390.o'
cardmgr: executing: 'insmod /lib/modules/2.2.15-2.5.0/pcmcia/pcnet_cs.o'
kernel: pcnet_cs: unable to read hardware net address
cardmgr: get dev info on socket 0 failed: no such device

More af-680 ?

Re: More Done that, doesn't work (Andreas-Johann Ulvestad)
Date: 2000, Feb 18
From: Poul Erik Laursen propel

Next step is to force hw_addr into pcnet_cs in config.opts, example:

module "pcnet_cs" opts "hw_addr=0x00,0x10,0x60,0x3b,0x0e,0x76" the problem is the driver cannot read the hardware address :-( you have to use win95/98 to do that.

It is maybe not that ne2000 comp.

I am using pcmcia-cs-3.1.11 but i am not sure it do any difference.

It is all mention in the PCMCIA-HOWTO.

By the way status for me width a addtron af-680 is that works one way but only intermidient the other way ! I also have the "interrupt(s) dropped" ! plus "Reentering the interupt handler"

None That card is not a true NE2000

Re: More af-680 ? (Poul Erik Laursen)
Date: 2000, Feb 18
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> I also have the "interrupt(s) dropped" ! plus "Reentering the
> interupt handler"

This particular card is sort-of like an NE2000, but is not 100%
compatible.

-- Dave

Question Someone got AF-680 (Addtron PCMCIA NIC) work?

Re: More af-680 ? (Poul Erik Laursen)
Date: 2000, Jul 10
From: Armando Montiel viajero

I need to know if someone could set up the Addtron AF-680 NIC works, some people here bind the pcnet_cs driver to that card but I have no success =(

TIA

None The regular pcnet_cs driver won't work

Re: Question Someone got AF-680 (Addtron PCMCIA NIC) work? (Armando Montiel)
Date: 2000, Jul 10
From: David Hinds <dhinds@pcmcia.sourceforge.org>

In the BUGS file, see the note about cards using the AX88190 chipset.

-- Dave

Ok It works! Addtron PCMCIA card (Ansel 2202 Fast Ethernet)

Re: None The regular pcnet_cs driver won't work (David Hinds)
Date: 2000, Jul 18
From: Armando Montiel viajero

There is a HOWTO in the next address:

Addtron AX88190 ChipSet

Question Beffalo LPC3-TX 10/100 NIC

Date: 2000, Feb 18
From: Ian Bone ianbone

Since I've had no responce from the company, thought I would try in here...can anyone help me, please.....Thanks.



Further to my comments below, I have spent more time with the Kernel and PCMCIA package drivers, and have the following message displayed when I insert the card:

cardmgr[128]: initializing socket 0
cardmgr[128]: socket 0: Buffalo LPC3-TX 10/10 PCMCIA-NIC
cardmgr[128]: executing : 'insmod /lib/modules/2.3.45/net/8390.o'
cardmgr[128]: executing : 'insmod /lib/modules/2.3.45/pcmcia/pcnet_cs.o'
pcnet_cs: ReleaseWindow: Bad handle
pcnet_cs: unable to read hardware net address
cardmgr[128]: get dev info on socket 0 failed: no such device

I also get something similar inserted in my /var/log/messages log file.

As you can see I have added the card definition tot he /etc/pcmcia/config
file as:

card "Baffalo LPC3-TX 10/100 PCMCIA-NIC"
   manfid 0x8a01, 0xc1ab
   bind "pcnet_cs"

Following instructions to try binding the card to the memory_cs module to
get the net address gave a similar "ReleaseWindow: Bad handle" error.

Using the DOS drivers on the CD that came with the card, I got an I/O Base
address of 0300H, and hardware address of 00:A0:0C:40:1E:0E, so I used this
in the pcnet_cs.c file in the hw_info definition and added
{ /* Buffalo LPC3-TX */ 0x0300, 0x00, 0xa0, 0x0c, 0 },

which compiled fine, although I doubt if I have the memory offset correct?

Can you offer assistance, please?

Many thanks in advance.


----- Original Message -----
From: Ian Bone
To: techsupport@techworks.co.uk
Sent: Wednesday, February 16, 2000 11:37 PM
Subject: LPC3-TX Under Linux


I am having a great deal of difficulty in getting my new LPC3-TX PCMCIA
network card to work under Linux RedHat 6.1. I have installed the latest
kernel 2.3.45, the latest PCMCIA package, version 3.1.11, and have
downloaded your Linux drivers from your web site, but I can not get them to
compile? Can you try compiling them yourself and see if they compile for
you. It looks like they have been ftp'ed using binary instead of ASCII at
some point? perhaps they could be placed in gziped tar file instead of a DOS
pkzip format?

Any comments would be greatly appreciated.

I am not a C programmer but it seems that my Makefile is not correct:
', needed by 'pcnet_cs.o'. Stop.'

Which looks like the Makefile has bad characters at the end of each line, or
the line:
pcnet_cs.o : pcnet_cs.c melco.h meclo_oem.h
is in the wrong format?

I have also tried to go down the route of not using your drivers and
configuring the PCMCIA drivers to handle this card, but I have not been
clever enough to get this to work either.

Thanks in advance.

Ian Bone
Database Administrator
National Australia Group
ianbone@ibone.co.uk

None Bad kernel choice

Re: Question Beffalo LPC3-TX 10/100 NIC (Ian Bone)
Date: 2000, Feb 18
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> pcnet_cs: ReleaseWindow: Bad handle

You are using a broken kernel.  With a new card, it's probably a good
idea to start with a known stable kernel/PCMCIA combination.

-- Dave

Sad ND5120-E Card seems to be alive, but cannot ping.

Date: 2000, Feb 22
From: Martin Andrews mdda

I believe that my card is 'alive', and pinging outside the machine causes the little lights to flash.  However, no other machine will respond to pings (nor will the Presario respond to their pings).

This is an install of RedHat 6.1 out-of-the-box.  Should I be recompiling the PCMCIA from your source?

Many thanks for any help you can give me.
Martin
:-)

Machine : Compaq Presario 1622, SohoWare ND5120-E 10bT card

:::: dmesg :::::
Linux version 2.2.12-20 (root@porky.devel.redhat.com) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Mon Sep 27 10:25:54 EDT 1999
...
Linux PCMCIA Card Services 3.0.14
  kernel build: 2.2.12-20 #1 Mon Sep 27 10:25:54 EDT 1999
  options:  [pci] [cardbus] [apm]
Intel PCIC probe: 
  TI 1131 PCI-to-CardBus at bus 0 slot 10, mem 0x68000000, 2 sockets
    host opts [0]: [ring] [pci + serial irq] [no pci irq] [lat 168/176] [bus 32/34]
    host opts [1]: [ring] [pci + serial irq] [no pci irq] [lat 168/176] [bus 35/37]
    ISA irqs (scanned) = 3,4,7,10 status change on irq 10
cs: IO port probe 0x1000-0x14ff: clean.
cs: memory probe 0x60000000-0x60ffffff: clean.
eth0: NE2000 Compatible: io 0x1000, irq 3, hw_addr 00:C0:F0:1C:FF:FF
eth0: bogus packet size: 8481, status=0x21 nxpg=0x40.

:::: ifconfig status ::::
Socket 0:
  no card
Socket 1:
  5V 16-bit card present
  Function 0: ready

:::: ifconfig ident ::::
Socket 0:
  no product info available
Socket 1:
  product info: "NDC", "Ethernet", "A", "004743118001"
  function: 6 (network)

:::: ifconfig eth0 ::::
eth0      Link encap:Ethernet  HWaddr 00:C0:F0:1C:FF:FF  
          inet addr:192.168.1.12  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:26 dropped:0 overruns:0 frame:1
          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          Interrupt:3 Base address:0x1000 

:::: route ::::
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.12    *               255.255.255.255 UH    0      0        0 eth0
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0
127.0.0.0       *               255.0.0.0       U     0      0        0 lo

Question Dynalink L100C32 not recognized

Date: 2000, Feb 22
From: Jasper Spit jasper

Hi,

I have a Dynalink L100C32 pcmcia network adapter which isn't recognized by cardmgr. This is the output I get :

cardctl config:

Socket 0:
  Vcc 3.3V  Vpp1 3.3V  Vpp2 3.3v
  interface type is "cardbus"
  function 0:
Socket 1:
  not configured

cardctl ident:

Socket 0:
  product info: "PCMCIA", "CardBus Ethernet 10/100 (R5)"
  function 6 (network)
Socket 1:
  no product info available

when inserting the card, dmesg gives me this :

cs: cb_alloc(bus 32): vendor 0x10ec, device 0x8138

that's all :(

I already tried to modify the pcmcia config file by adding a new entry using manfid 0x10ec, 0x8138, but with no luck. (yes, I made cardmgr re-read the configfile).

Can anybody tell me how I can get this card to work ?

Kernel = 2.2.13

Thanks !!

jasper

None Wrong ID numbers

Re: Question Dynalink L100C32 not recognized (Jasper Spit)
Date: 2000, Feb 22
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Use the product info strings in your config entry.  The numbers are
PCI device numbers, which are not the same as the manfid numbers that
go in the config file.

Then I'd try the tulip_cb driver.

-- Dave

Sad No luck

Re: None Wrong ID numbers (David Hinds)
Date: 2000, Feb 22
From: Jasper Spit jasper

Hi,

Created a new entry in /etc/pcmcia/config :

card "Dynalink L100C32 Fast Ethernet"
  version "PCMCIA", "CardBus Ethernet 10/100 (R5)"
  bind "tulip_cb"

Made cs reload config file. /var/log/messages when removing and inserting the card :

Feb 23 21:36:36 laptop kernel: cs: cb_free(bus 32)
Feb 23 21:36:36 laptop cardmgr[62]: initializing socket 0
Feb 23 21:36:36 laptop cardmgr[62]: unsupported card in socket 0
Feb 23 21:36:36 laptop kernel: cs: cb_alloc(bus 32): vendor 0x10ec, 0x8138
Feb 23 21:36:36 laptop cardmgr[62]: no product info available

cardctl ident still says this :
Socket 0:
  product info: "PCMCIA", "CardBus Ethernet 10/100 (R5)"
  function: 6 (network)

Now what ? :-)

Thanks,

Jasper

Question route add unnecessary for dhclient?

Date: 2000, Feb 24
From: Adam Goode <goodea@rpi.edu>

On line 60 of etc/network, there is the line

/sbin/route add default dev $DEVICE

which presumably adds the current device as the default gateway, when dhcp is enabled.

When I insert my 3com ethernet card, configured as a static interface in network.opts, it works properly as default route. When I plug in my wavelan card, it takes over as default route, which means it knocks out default route for the ethernet, and makes it go over the wavelan. Right now, I am not near a access point, so dhclient finds nothing on the wavelan and goes to sleep. But the card is configured as default route, which I don't want. When I comment out the route add line in etc/network, it works correctly. Is the line necessary? Doesn't dhclient automatically add the route as necessary? Seems like it, check out /etc/dhclient-script.

I am running Debian woody on x86.

Adam Goode

None I'm not sure

Re: Question route add unnecessary for dhclient? (Adam Goode)
Date: 2000, Feb 24
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I believe that the route command was necessary at one time, for at
least some versions of dhcpcd and/or kernels, but I don't know if it
is/was ever necessary for dhclient.

Where do you get dhclient, anyway?  I've never been able to find a
dhclient package that wasn't for BSD.  Maybe it doesn't matter, but
network configuration scripts tend to be platform specific.

-- Dave

Feedback dhclient for Linux

Re: None I'm not sure (David Hinds)
Date: 2000, Feb 24
From: Adam Goode <goodea@rpi.edu>

Well, on Debian potato (or woody), dhclient is right there, as a package to install in dselect. It's interesting the way dhclient works in handling cross-platform issues. The binary itself does only platform independent things. Most of the platform specific implementation stuff is in /etc/dhclient-script, which is customized for your platform.

In that file, route is definitely called (correctly, as far as I can tell).

Debian also supports pump, but I'm not sure if it sets the default route correctly like dhclient seems to.

Thanks for your quick reply,

Adam Goode

None Package name confusion, and a fix

Re: Feedback dhclient for Linux (Adam Goode)
Date: 2000, Feb 24
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Oh, Debian calls it dhcp-client, which threw me off.  It appears to me
that the right fix is just to change that route command to:

  route add default dev $DEVICE netmask 0.0.0.0

which should work for any DHCP client that needs it, and should be
harmless for any client that does it on its own.

-- Dave

More Hmmm, almost, but not quite

Re: None Package name confusion, and a fix (David Hinds)
Date: 2000, Feb 24
From: Adam Goode <goodea@rpi.edu>

Yes, but this still switches the default route from the first ethernet card inserted to the second. Basically, whichever card is added last becomes default route.

My main trouble is that the second ethernet card is a wireless card, so that if I am not near an access point, dhcp fails and shouldn't change any route. This preserves my wired ethernet card as default. In general, though, I think I want to be able to select an interface to be preferred default route (because the default should be the wired card if that's active).

Is there a better solution to this (perhaps) more general problem of picking an interface to be default route?

Let me know if I've confused anyone terribly. (Besides myself.)

Adam Goode

None Argh

Re: More Hmmm, almost, but not quite (Adam Goode)
Date: 2000, Feb 24
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Then I guess it actually didn't help at all, right?  Well, I think
I'm also quite confused.

> Is there a better solution to this (perhaps) more general problem of
> picking an interface to be default route?

My suggestion would be for you to just define two PCMCIA schemes, one
for when you're wired, and one for when you're wireless.  Use cardctl
to pick your scheme.  I guess it isn't quite as nice as automatic
fall-over from one card to the other, but I'm not sure there is a good
general solution to that problem.

-- Dave

Question Wisecom PC-400 10/100 - Doesn`t work

Date: 2000, Feb 24
From: Francesc Bassas frankb

Hi to everybody,

I have a Dell Inspiron 3700 with a Wisecom PC-400 with 10/100 Ethernet.

My Linux version is 2.2.13 pcmcia version is 3.1.11

The output of "cardctl ident" is:

Socket 1:
  product info: "PCMCIA", "10/100 Ethernet Card", "", ""
  manfid: 0x8a01, 0xc1ab
  function: 6 (network)

In the startup I get this message:

 kernel: pcnet_cs: unable to read hardware net address

Reading the documentation I saw that one can hardwire the hardware address with an option, a that's what I did.

It seemed to work; in startup it got the address and it assigned an IRQ and a I/O port to the card.

I did a "ping" to a machine and it worked; but when I tried to do a "ftp" or "telnet" it blocked. Afterwards, I noticed that no machine can do a "ping" to this one; this machine doesn`t seem to answer.

I tried a NE2000 10 Mbps card, and it worked perfect.

Could anyone help me? Thanks in advance.

None The wrong driver is being loaded

Re: Question Wisecom PC-400 10/100 - Doesn`t work (Francesc Bassas)
Date: 2000, Feb 24
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Your card uses the smc91c92_cs driver, not pcnet_cs.

>   product info: "PCMCIA", "10/100 Ethernet Card", "", ""

Nice of them to pick a completely generic set of identification
strings, which unfortunately also match cards that use the pcnet_cs
driver.

Edit /etc/pcmcia/config and find the entry that matches these strings,
and replace it with:

  card "WiseCom WC-PC400"
    manfid 0x8a01, 0xc1ab
    bind "smc91c92_cs"

-- Dave

Sad It fails anyway

Re: None The wrong driver is being loaded (David Hinds)
Date: 2000, Feb 25
From: Francesc Bassas frankb

Fist of all, thanks to David for his suggestion.

In fact, that's what I tried before getting a newer drivers version. Anyway I have tried ance again, I that's what I get:

cardmgr[57]: initializing socket 1

cs: memory probe 0xa0000000-0xa0ffffff: clean.

cardmgr[57]: socket 1: WiseCom WC-PC400 Fast Ethernet

cardmgr[57]:executing: 'insmod/lib/modules/2.2.13/pcmcia/smc91c92_cs.o' smc91c92_cs: using 8-bit IO window.

eth0: smc91c??? rev 13: io 0x100, irq 9, hw_addr FF:FF:FF:FF:FF:FF

cardmgr[57]: executing: './network start eth0'

cardmgr[57]: + cat: /var/state/pcmcia/scheme: No such file or directory

smc91c92_cs: Yikes! Bad chip signature!

Configuring eth0 as 147.83.143.192...

smc91c92_cs: Yikes! Bad chip signature!

cardmgr[57]: + SIOCSIFFLAGS: No such device

It's worse. What else ca I try?

None Sorry, ignore that suggestion

Re: Sad It fails anyway (Francesc Bassas)
Date: 2000, Apr 04
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Sorry; I re-read your message and you seemed to say that you did get
"ping" to work at least once, so the pcnet_cs driver has to be the
right one.

In that case, I think I would want to see more of your system log
messages.  Do you get any error messages from the driver when you try
to open an ftp or telnet connection?

-- Dave

News NetGear FA410TXC Setup

Date: 2000, Feb 24
From: Jochen Friedrich jochen1

Hi,

i am using a recently bought FA410TXC with pcmcia 3.1.10. The card is found, but apparently the transmitter isn't enable by default:

Feb 19 16:05:50 localhost cardmgr[380]: initializing socket 1
Feb 19 16:05:50 localhost cardmgr[380]: socket 1: NetGear FA410TXC Fast Ethernet
Feb 19 16:05:50 localhost cardmgr[380]: executing: 'insmod /lib/modules/2.2.14/net/8390.o'
Feb 19 16:05:51 localhost cardmgr[380]: executing: 'insmod /lib/modules/2.2.14/pcmcia/pcnet_cs.o'
Feb 19 16:05:51 localhost kernel: eth0: NE2000 Compatible: io 0x300, irq 7, hw_addr 00:E0:98:77:A6:21
Feb 19 16:05:51 localhost cardmgr[380]: executing: './network start eth0'
Feb 19 16:09:43 localhost automount[775]: running expiration on path /home
Feb 19 16:09:43 localhost automount[775]: expired /home/xedds10
Feb 19 16:32:39 localhost kernel: eth0: found link beat
Feb 19 16:32:54 localhost kernel: eth0: Tx timed out, cable problem? TSR=0x42, ISR=0x0, t=614.
Feb 19 16:33:04 localhost kernel: eth0: Tx timed out, cable problem? TSR=0x42, ISR=0x0, t=1000.
Feb 19 16:33:10 localhost kernel: eth0: lost link beat
Feb 19 16:33:14 localhost kernel: eth0: Tx timed out, cable problem? TSR=0x42, ISR=0x0, t=1000.
Feb 19 16:33:54 localhost last message repeated 4 times
Feb 19 16:34:14 localhost last message repeated 2 times
Feb 19 16:34:21 localhost kernel: eth0: interrupt from stopped card

I also recognize, that no interrupts are generated by the card, at all.

I had a closer look at the packet driver they ship and came up with this user space program to enable the transmitter and select speed + full duplex:

usage:

fa_select <interface> <option>

option:
0: 10 MBPS/HALF
1: 10 MBPS/FULL
2: 100MBPS/HALF
3: 100MBPS/FULL

I hope it's useful to someone...

--
Jochen


#include <sys/types.h>
#include <sys/socket.h>
#include <sys/ioctl.h>
#include <net/if.h>
#include <stdio.h>
#include <errno.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>

inline unsigned char
inb (unsigned short port)
{
  unsigned char _v;

  __asm__ __volatile__ ("inb %w1,%0":"=a" (_v):"Nd" (port));
  return _v;
}

inline void
outb (unsigned char value, unsigned short port)
{
  __asm__ __volatile__ ("outb %b0,%w1"::"a" (value), "Nd" (port));
}

static int sockets_open(void)
{
    int sock;
    if ((sock = socket(AF_INET, SOCK_DGRAM, 0)) != -1)
        return sock;
    else if ((sock = socket(AF_IPX, SOCK_DGRAM, 0)) != -1)
        return sock;
    else if ((sock = socket(AF_AX25, SOCK_DGRAM, 0)) != -1)
        return sock;
    else
        return socket(AF_APPLETALK, SOCK_DGRAM, 0);
}
void write_bit(int port, int bit)
{
    outb((bit << 6) + 0x20, port);
    usleep(1);
    outb((bit << 6) + 0xa0, port);
    usleep(1);
    outb((bit << 6) + 0x20, port);
}
int read_bit(int port)
{
    int i;
    outb(0,    port);
    usleep(1);
    outb(0x80, port);
    usleep(1);
    i = inb(port);
    outb(0,    port);
    return (i & 0x10) >> 4;
}
void reset(int port)
{
    outb(0x08, port);
    usleep(1);
    outb(0x0C, port);
    usleep(1);
    outb(0x08, port);
    usleep(1);
    outb(0x0C, port);
    outb(0x00, port);
}
int reada(int port, int adr)
{
    int i,j;

    for (i=0; i<0x20; i++)
      write_bit(port, 1);

    write_bit(port, 0);
    write_bit(port, 1);
    write_bit(port, 1);
    write_bit(port, 0);

    write_bit(port, 0);
    write_bit(port, 0);
    write_bit(port, 0);
    write_bit(port, 0);
    write_bit(port, 0);

    write_bit(port, (adr & 0x10) >> 4);
    write_bit(port, (adr & 0x08) >> 3);
    write_bit(port, (adr & 0x04) >> 2);
    write_bit(port, (adr & 0x02) >> 1);
    write_bit(port, (adr & 0x01) >> 0);

    j = read_bit(port);
    if (j == 1)
      j = read_bit(port);
    for (i=0; i<16; i++) {
      j = (j << 1) + read_bit(port);
    }
    write_bit(port, 1);
    return j;
}
int writea(int port, int adr, int val)
{
    int i,j;

    outb(0x08, port);
    usleep(1);
    outb(0x0C, port);
    usleep(1);
    outb(0x08, port);
    usleep(1);
    outb(0x0C, port);
    outb(0x00, port);

    for (i=0; i<0x20; i++)
      write_bit(port, 1);

    write_bit(port, 0);
    write_bit(port, 1);
    write_bit(port, 0);
    write_bit(port, 1);

    write_bit(port, 0);
    write_bit(port, 0);
    write_bit(port, 0);
    write_bit(port, 0);
    write_bit(port, 0);

    write_bit(port, (adr & 0x10) >> 4);
    write_bit(port, (adr & 0x08) >> 3);
    write_bit(port, (adr & 0x04) >> 2);
    write_bit(port, (adr & 0x02) >> 1);
    write_bit(port, (adr & 0x01) >> 0);

    write_bit(port, 1);
    write_bit(port, 0);

    write_bit(port, (val & 0x8000) >> 15);
    write_bit(port, (val & 0x4000) >> 14);
    write_bit(port, (val & 0x2000) >> 13);
    write_bit(port, (val & 0x1000) >> 12);
    write_bit(port, (val & 0x0800) >> 11);
    write_bit(port, (val & 0x0400) >> 10);
    write_bit(port, (val & 0x0200) >> 9);
    write_bit(port, (val & 0x0100) >> 8);
    write_bit(port, (val & 0x0080) >> 7);
    write_bit(port, (val & 0x0040) >> 6);
    write_bit(port, (val & 0x0020) >> 5);
    write_bit(port, (val & 0x0010) >> 4);
    write_bit(port, (val & 0x0008) >> 3);
    write_bit(port, (val & 0x0004) >> 2);
    write_bit(port, (val & 0x0002) >> 1);
    write_bit(port, (val & 0x0001) >> 0);

    write_bit(port, 1);
    return 0;
}
void main(int argc, char **argv)
{
    int skfd, i, sub, led;
    struct ifreq ifr;

    skfd = sockets_open();
    if (skfd == -1) {
        perror("socket");
        exit(1);
    }
    strcpy(ifr.ifr_name, argv[1]);
    if (ioctl(skfd, SIOCGIFMAP, &ifr) < 0) {
        perror("ioctl");
        exit(1);
    }
    i = atoi(argv[2]);
    switch(i) {
      case 0:
        sub = 0x0000;
        break;
      case 1:
        sub = 0x0100;
        break;
      case 2:
        sub = 0x2000;
        break;
      default:
        sub = 0x2100;
        break;
    }
    ioperm(ifr.ifr_map.base_addr+0x1c, 1, 1);
    reset(ifr.ifr_map.base_addr+0x1c);
    writea(ifr.ifr_map.base_addr+0x1c, 0, 0x8000);
    writea(ifr.ifr_map.base_addr+0x1c, 0, sub);
    close(skfd);
    exit(0);
}

Question DFE-650 not always Linux-compatible?

Date: 2000, Feb 25
From: Anthony Jameson AJameson

Subject: DFE-650 not always Linux-compatible?
Reply-to: Anthony Jameson <jameson@cs.uni-sb.de>
BCC: jameson@sol.cs.uni-sb.de
--text follows this line--
Hi,

The D-Link DFE-650TX is well known as a Linux-compatible Fast
Ethernet card. For example, two such cards have been found to
work fine on my Toshiba Satellite 4090XCDT running S.u.S.e. Linux 6.0 

But just a few days ago I bought a third such card for myself,
and it's been nothing but trouble, even as its supposedly
identical twins continue to work fine. It's recognized by the
card manager, and the pcnet_cs driver is duly loaded. But it's
impossible to connect to the network: I always get the error
message "No route to host". In /var/log/messages, there's always a message like this: 

Feb 24 22:14:40 helena kernel: eth0: Tx timed out, cable problem? TSR=0x42, ISR=0x0, t=1000.

Followng the advice in the PCMCIA how-to, I've tried juggling
the IRQs and the ports, but the result is always the same.

And this is not a unique experience: I've corresponded with a
Linux expert in northern Germany who spent days combating
exactly the same problem with his new DFE-650TX card, before giving up and returning the card to the dealer.

So it looks as if D-Link may have made some change in their
card that renders it Linux-incompatible (though they still
claim Linux-compatibility for the card on the packaging and on their web site).

            Anthony Jameson

Here's some debugging information:

Kernel version: 2.0.36
cardctl version 3.0.6

Output of "cardctl ident":
Socket 0:
  no product info available
Socket 1:
  product info: "D-Link", "DFE-650", "Fast Ethernet", "Rev. D1"
  manfid: 0x0149, 0x0230
  function: 6 (network)

Output of "cardctl status":
Socket 0:
  no card
Socket 1:
  5V 16-bit card present
  Function 0: 

Typical sequence in /var/log/messages, starting with a system reboot:
Feb 24 22:13:51 helena syslogd 1.3-3: restart.
Feb 24 22:13:52 helena kernel: klogd 1.3-3, log source = /proc/kmsg started.
Feb 24 22:13:52 helena kernel: Inspecting /boot/System.map
Feb 24 22:13:52 helena kernel: Loaded 5086 symbols from /boot/System.map.
Feb 24 22:13:52 helena kernel: Symbols match kernel version 2.0.36.
Feb 24 22:13:52 helena kernel: Loaded 18 symbols from 6 modules.
Feb 24 22:13:52 helena kernel: Linux PCMCIA Card Services 3.0.6
Feb 24 22:13:52 helena kernel:   kernel build: 2.0.36 #1 Fri Dec 11 16:26:51 /etc/localtime 1998
Feb 24 22:13:52 helena kernel:   options:  [pci] [cardbus]
Feb 24 22:13:52 helena kernel: Intel PCIC probe: 
Feb 24 22:13:52 helena kernel:   Toshiba ToPIC97 PCI-to-CardBus at bus 0 slot 2, mem 0x68000000, 2 sockets
Feb 24 22:13:52 helena kernel:     host opts [0]: [slot 0xf0] [ccr 0x10] [cdr 0x86] [rcr 0x02] [no pci irq] [lat 168/176] [bus 20/20]
Feb 24 22:13:52 helena kernel:     host opts [1]: [slot 0xf0] [ccr 0x11] [cdr 0x86] [rcr 0x02] [no pci irq] [lat 168/176] [bus 21/21]
Feb 24 22:13:52 helena kernel:     ISA irqs (default) = 3,4,5,7,9,10,11,12 polling interval = 1000 ms
Feb 24 22:13:52 helena kernel: cs: IO port probe 0x1000-0x17ff: clean.
Feb 24 22:13:52 helena kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x4d0-0x4d7
Feb 24 22:13:52 helena kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Feb 24 22:13:52 helena kernel: cs: memory probe 0x0d0000-0x0dffff: clean.
Feb 24 22:13:52 helena kernel: eth0: NE2000 Compatible: port 0x300, irq 9, hw_addr 00:E0:98:77:94:FD
Feb 24 22:13:53 helena ypbind[124]: unable to register (YPBINDPROG, YPBINDVERS, udp). : Connection refused 
# Is the above relevant here?
Feb 24 22:13:54 helena lpd[147]: restarted
Feb 24 22:14:18 helena apmd[255]: Version 3.0final (APM BIOS 1.1, Linux driver 1.2)
Feb 24 22:14:18 helena apmd[255]: Charge: * * * (94% 2:38)
Feb 24 22:14:22 helena su: (to jameson) root on /dev/ttyp2
Feb 24 22:14:32 helena apmd[255]: Now using AC Power
Feb 24 22:14:40 helena kernel: eth0: Tx timed out, cable problem? TSR=0x42, ISR=0x0, t=1000.
Feb 24 22:15:45 helena kernel: eth0: Tx timed out, cable problem? TSR=0x42, ISR=0x0, t=6500.
Feb 24 22:17:45 helena kernel: eth0: Tx timed out, cable problem? TSR=0x42, ISR=0x0, t=12000.

/etc/pcmcia/config.opts: (Don't know if there's anything nonstandard here.)
#
# Local PCMCIA Configuration File
#
# System resources available for PCMCIA devices
#
include port 0x100-0x4ff, port 0x1000-0x17ff
include memory 0xc0000-0xfffff
include memory 0xa0000000-0xa0ffffff, memory 0x60000000-0x60ffffff
#
# Extra port range for IBM Token Ring
#
include port 0xa00-0xaff
#
# Resources we should not use, even if they appear to be available
#
# First built-in serial port
exclude irq 4
# Second built-in serial port
exclude irq 3

# First built-in parallel port
exclude irq 7

Idea Try This

Re: Question DFE-650 not always Linux-compatible? (Anthony Jameson)
Date: 2000, Feb 25
From: Jochen Friedrich jochen1

Hi Anthony,

please try the program i posted in my last message (NetGear FA410TXC Setup). From looking at the vendor code in the ethernet address, it looks like both cards are from the same vendor (or the NetGear card looks like a re-labled DFE-650).

-- Jochen

Feedback Hope others can try

Re: Idea Try This (Jochen Friedrich)
Date: 2000, Feb 26
From: Anthony Jameson AJameson

Hi Jochen,

Thanks for the tip, which looks promising.

I'm no longer in a position to try it out, since I
had to exchange my D-Link DFE-650TX for a working
card (incidentally, an AnyCom ECO Ethernet 10/100,
which worked right out of the box).

But the idea should be useful for anyone who is
struggling with one of the newer DFE-650TX
cards. In particular, it suggests that these newer
D-Link cards are not identical to the older
ones. (One of our older ones had a hw_addr of
00:80:C8:42:95:E9; the addresses of your FA410TXC
card and my newer DFE-650TX both start with
00:E0:98:77.)

In addition to the hardware addresses, your error
messages certainly look similar to mine.

            Anthony Jameson

Feedback tried and it works

Re: Feedback Hope others can try (Anthony Jameson)
Date: 2000, Feb 26
From: Ingo Ciechowski inki

just wanted to repeat that Anthony's tool works with the D-Link DFE-650 card.

Ingo

Question Where to add fa_select in the startup process

Re: Feedback tried and it works (Ingo Ciechowski)
Date: 2000, Jul 31
From: Juergen Lindemeyer juergen

Hello,

I had to fiddle some time to get my DFE-650 up and running. Now, after I tried fa_select, unloaded pcnet_cs and restarted it, it workes fine.

But I wonder where I can fiddle it into to PCMCIA-startup-process. I don't know if I can run fa_select before/after pcnet_cs.

Is there any "official" way without messing up all the startup scripts?

Thanks in advance!

/juergen

None There is a better way now

Re: Question Where to add fa_select in the startup process (Juergen Lindemeyer)
Date: 2000, Jul 31
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The "official" way is to use the current PCMCIA driver package, which
fixes the problem inside the pcnet_cs driver, so the fa_select program
is unnecessary.

-- Dave

Ok Success at last ...

Re: None There is a better way now (David Hinds)
Date: 2000, Aug 02
From: Juergen Lindemeyer juergen

After a lot of fiddling around with my SuSE distribution (which is really not so bad, but has the disadvantage, that the startup process is somewhat different than for example RedHat) everything is working well.

The problem really wasn't the driver (as I thought first), but the inconsistencies in the startup process.

Thank you very much Dave!

/juergen

Question bad performance with Jochen's patch and DFE-650

Re: Idea Try This (Jochen Friedrich)
Date: 2000, Feb 26
From: Ingo Ciechowski inki

Although I'm really glad that Jochen's tool works pretty well to enable that D-Link card I had to find out that the card only performs as if it was a 10Mbit card, i.e. 10% of the performance under Windows98.

The LEDs at hub and cardadapter indicate the selected transmission protocol.

Any idea out there what I could do to get it faster?

Ingo

None Performance should be equally bad under Windows

Re: Question bad performance with Jochen's patch and DFE-650 (Ingo Ciechowski)
Date: 2000, Feb 27
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Recheck your Windows performance.  It is impossible to get anything
approaching 100Mbit throughput from this card: it is a 16-bit card,
and the 16-bit PCMCIA bus has a maximum throughput of 1.5-2 MB/sec.

So unless D-Link has found a way to push 100Mbits of data through a
15Mbit pipe, I think your Windows performance numbers were incorrect?

-- Dave

Feedback correct: Windows: 8.28MBit/s - Linux: 0.94MBit/s :-((

Re: None Performance should be equally bad under Windows (David Hinds)
Date: 2000, Feb 27
From: Ingo Ciechowski inki

>Recheck your Windows performance.  It is impossible to get anything
>approaching 100Mbit throughput from this card: it is a 16-bit card,
>and the 16-bit PCMCIA bus has a maximum throughput of 1.5-2 MB/sec.

jou're right, its just a relative difference - but the factor lead me to the idea of 10Mbit vs. 100MBit performance. Here are the numbers I get when copying a lager file with the same 16-bit card:

(a) under Windows98 : 1060kByte/s (about 8.28MBit/s)

(b) unter Linux with Jochen's enabler (independent from the choosen mode and independent of using a 10BaseT oder 100BaseT hub): 120kByte/s (about 0.94MBit/s)

So indeed I'm never in the 100MBit range with that 16bit card, but for some reason I'm at 11% of the windows performance :-((

Ingo

Note Same here

Re: Feedback correct: Windows: 8.28MBit/s - Linux: 0.94MBit/s :-(( (Ingo Ciechowski)
Date: 2000, Feb 27
From: Jochen Friedrich jochen1

Hi Ingo,

i also tried ftp now and found the same performance problems. ifconfig also shows a lot of frame errors (looks like one frame error is reported for each received packet). Interesting fact is that only download is affected (both ftp and http). NFS is also not affected (that's what i mostly use here).

However, even with a flood-ping (ping -f -s 1472), i can't trigger the frame errors i get for ftp...

Additional, i noticed that the card somehow always operates in promicious mode. tcpdump -p still shows all packets on the network. Maybe the selection of speed/mode has to be done before setting up the 8390 chip...

-- Jochen

None Well, that is indeed pretty bad

Re: Feedback correct: Windows: 8.28MBit/s - Linux: 0.94MBit/s :-(( (Ingo Ciechowski)
Date: 2000, Feb 28
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Performance of 120 kb/s is pretty bad.  With the older version of this
card, I get 1000-1100 kb/s on 100baseT.  So yes, there is something
wrong here.  I'm not really sure how to go about debugging it without
maybe information from the vendor about what is really different about
these new cards.

-- Dave

Feedback just called DLink ;-)

Re: None Well, that is indeed pretty bad (David Hinds)
Date: 2000, Aug 02
From: hvx

Hi! I just called DLink Germany a few days ago and told them about the newer cards not being as linux compatible as the older ones are. Today I got mail from them, they send me 2 DLink DFE-660 cards to try them out.

The Node IDs are: 0080C8 8DA027 and 0050BA 745550

Ones of them is new, the other one is very old. (The sticker still says 16-bit, even though it IS 32-bit).

But with both of them I only get about 200kb/s. I dont know if I just got 2 cards which dont work well with linux or if I misconfigurated something. Is there anything I can try to figure it out ?

I tried Jochen´s tool as well, but it quit with a "segmentation faul". TIA Markus

None Re: Feedback: just called DLink ;-)

Re: Feedback just called DLink ;-)
Date: 2000, Aug 02
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The discussion of Jochen's tool, etc, is about different versions of
the 16-bit D-Link DFE-650TX cards.  The issue was also fixed, and both
old and new DFE-650 cards work fine with the current Linux drivers.
Jochen's tool is no longer needed, as far as I know.

This has nothing to do with CardBus DFE-660TX cards.  If there is an
issue with these cards, then it is completely unrelated.

-- Dave

News New version

Re: Feedback correct: Windows: 8.28MBit/s - Linux: 0.94MBit/s :-(( (Ingo Ciechowski)
Date: 2000, Mar 01
From: Jochen Friedrich jochen1

Hi Ingo,

i think i found what was causing this. Apparently, the collision detection uses a different register for its setup.
This one attempts to set up the collision detection as well. However, i only tested 10 MBit/s Half duplex this time.

Cheers,
Jochen

#include <sys/types.h>
#include <sys/socket.h>
#include <sys/ioctl.h>
#include <sys/io.h>
#include <net/if.h>
#include <stdio.h>
#include <errno.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>

inline unsigned char
inb (unsigned short port)
{
  unsigned char _v;

  __asm__ __volatile__ ("inb %w1,%0":"=a" (_v):"Nd" (port));
  return _v;
}

inline void
outb (unsigned char value, unsigned short port)
{
  __asm__ __volatile__ ("outb %b0,%w1"::"a" (value), "Nd" (port));
}

static int sockets_open(void)
{
    int sock;
    if ((sock = socket(AF_INET, SOCK_DGRAM, 0)) != -1)
	return sock;
    else if ((sock = socket(AF_IPX, SOCK_DGRAM, 0)) != -1)
	return sock;
    else if ((sock = socket(AF_AX25, SOCK_DGRAM, 0)) != -1)
	return sock;
    else
	return socket(AF_APPLETALK, SOCK_DGRAM, 0);
}
void write_bit(int port, int bit)
{
    outb((bit << 6) + 0x20, port);
    usleep(1);
    outb((bit << 6) + 0xa0, port);
    usleep(1);
    outb((bit << 6) + 0x20, port);
}
int read_bit(int port)
{
    int i;
    outb(0,    port);
    usleep(1);
    outb(0x80, port);
    usleep(1);
    i = inb(port);
    outb(0,    port);
    return (i & 0x10) >> 4;
}
void reset(int port)
{
    outb(0x08, port);
    usleep(1);
    outb(0x0C, port);
    usleep(1);
    outb(0x08, port);
    usleep(1);
    outb(0x0C, port);
    outb(0x00, port);
}
int reada(int port, int adr)
{
    int i,j;

    for (i=0; i<0x20; i++)
      write_bit(port, 1);

    write_bit(port, 0);
    write_bit(port, 1);
    write_bit(port, 1);
    write_bit(port, 0);

    write_bit(port, 0);
    write_bit(port, 0);
    write_bit(port, 0);
    write_bit(port, 0);
    write_bit(port, 0);

    write_bit(port, (adr & 0x10) >> 4);
    write_bit(port, (adr & 0x08) >> 3);
    write_bit(port, (adr & 0x04) >> 2);
    write_bit(port, (adr & 0x02) >> 1);
    write_bit(port, (adr & 0x01) >> 0);

    j = read_bit(port);
    if (j == 1)
      j = read_bit(port);
    for (i=0; i<16; i++) {
      j = (j << 1) + read_bit(port);
    }
    write_bit(port, 1);
    return j;
}
int writea(int port, int adr, int val)
{
    int i,j;

    for (i=0; i<0x20; i++)
      write_bit(port, 1);

    write_bit(port, 0);
    write_bit(port, 1);
    write_bit(port, 0);
    write_bit(port, 1);

    write_bit(port, 0);
    write_bit(port, 0);
    write_bit(port, 0);
    write_bit(port, 0);
    write_bit(port, 0);

    write_bit(port, (adr & 0x10) >> 4);
    write_bit(port, (adr & 0x08) >> 3);
    write_bit(port, (adr & 0x04) >> 2);
    write_bit(port, (adr & 0x02) >> 1);
    write_bit(port, (adr & 0x01) >> 0);

    write_bit(port, 1);
    write_bit(port, 0);

    write_bit(port, (val & 0x8000) >> 15);
    write_bit(port, (val & 0x4000) >> 14);
    write_bit(port, (val & 0x2000) >> 13);
    write_bit(port, (val & 0x1000) >> 12);
    write_bit(port, (val & 0x0800) >> 11);
    write_bit(port, (val & 0x0400) >> 10);
    write_bit(port, (val & 0x0200) >> 9);
    write_bit(port, (val & 0x0100) >> 8);
    write_bit(port, (val & 0x0080) >> 7);
    write_bit(port, (val & 0x0040) >> 6);
    write_bit(port, (val & 0x0020) >> 5);
    write_bit(port, (val & 0x0010) >> 4);
    write_bit(port, (val & 0x0008) >> 3);
    write_bit(port, (val & 0x0004) >> 2);
    write_bit(port, (val & 0x0002) >> 1);
    write_bit(port, (val & 0x0001) >> 0);

    write_bit(port, 1);
    return 0;
}
void main(int argc, char **argv)
{
    int skfd, i, sub, filter;
    struct ifreq ifr;

    skfd = sockets_open();
    if (skfd == -1) {
	perror("socket");
	exit(1);
    }
    strcpy(ifr.ifr_name, argv[1]);
    if (ioctl(skfd, SIOCGIFMAP, &ifr) < 0) {
        perror("ioctl");
        exit(1);
    }
    i = atoi(argv[2]);
    switch(i) {
      case 0:
        sub = 0x0000;
	filter = 0;
	break;
      case 1:
        sub = 0x0100;
	filter = 4;
	break;
      case 2:
        sub = 0x2000;
	filter = 0;
	break;
      default:
        sub = 0x2100;
	filter = 4;
	break;
    }
    ioperm(ifr.ifr_map.base_addr+0x1c, 2, 1);
    reset(ifr.ifr_map.base_addr+0x1c);
    writea(ifr.ifr_map.base_addr+0x1c, 0, 0x8000);
    writea(ifr.ifr_map.base_addr+0x1c, 0, sub);
    outb(filter, ifr.ifr_map.base_addr+0x1d);
    close(skfd);
    exit(0);
}

Note Performance

Re: News New version (Jochen Friedrich)
Date: 2000, Mar 07
From: Bernd Mathiszik BerndM

with the new version of Jochen's tool (independent from the choosen mode and independent of using a 10BaseT oder 100BaseT hub) my performance is about 450kByte/s.

Feedback can't try it any more :-(

Re: Feedback correct: Windows: 8.28MBit/s - Linux: 0.94MBit/s :-(( (Ingo Ciechowski)
Date: 2000, Mar 01
From: Ingo Ciechowski inki

Hi Jochen,

thanks a lot for that new version. Dealing with all those pc-cards during the last days I meanwhile unfortunately already sent the DFE-650 back to the distributor - still looking for some way to get a carbus card to work with my system due to the promising increase in performance.

Therefore I can't test your new tool any more, sorry :-(( Hope, someone else will have a chance to do that.

Ingo

Agree NetGear FA410TXC Tool works for D-Link DE-650

Re: Question DFE-650 not always Linux-compatible? (Anthony Jameson)
Date: 2000, Feb 26
From: Ingo Ciechowski inki

I've just found Anthony Jamesons recommendation and his great little tool as postes under #46. in this group.

Since I ran into the same problem as Phil Brooke I gave it a try and found that Anthony's enabling code works pretty well for the newer DE-650 cards.

Thanks a lot for this input - and I hope it will make it's way into one of the new versions of the pcmcia sources.

Ingo

Angry HELP! *Still* can't get D-Link DFE-650TX going! (Day 5)

Re: Agree NetGear FA410TXC Tool works for D-Link DE-650 (Ingo Ciechowski)
Date: 2000, Aug 18
From: Harold Boyer hboyer

Hi. I'm going absolutely crazy.

I've read all of this stuff, and I still can't get this D-Link going. It's the endless "found link beat" "lost link beat" crisis in /var/log/messages.

Funny thing is, it's not just the D-link, it happened with a 3com 656 modem+adapter card too. Same exact thing.

I have a Toshiba Satellite 2250CDT. I'm running RedHat 6.2, with pcmcia-cs 2.2.16-17 beta code (so the fixes aren't in the pcmcia upgrade yet). The same exact thing happened with pcmcia-cs 2.2.16-3, and the whole 2.2.14-x series. Ugh!

The card works perfectly at 10M or 100M in Windows 98 and 2000. I've tried PCIC card mode and Cardbus/16-bit in the BIOS.

I downloaded a binary for fa_select, but it doesn't run (must not be RedHat), and I downloaded the source for Jochen Friedrich's fix, but I don't know C, and can't get it to compile. If I type "make fa_select" it errors on "inline", and if I take the inline line out, it errors on the next line. I also typed "gcc fa_select" but that obviously didn't help either.

What else... I've bounced it from irq 3 to 5 to 9 to 10, and none of those worked.

Any ideas? I'm going mad. I don't care if the fix is slow, as long as it works. I've put literally 30+ hours into this, and I've already switched cards, and don't want to order another one.

If someone can send me a RedHat binary of fa_select, that might work, and could you please tell me which init script to call it from?

Any help would be REALLY appreciated! Please cc: hboyer@minn.net.

My /var/log/messages:

Aug 17 12:07:36 localhost kernel: Linux PCMCIA Card Services 3.1.8 
Aug 17 12:07:36 localhost kernel:   kernel build: 2.2.14-5.0 #1 Tue Mar 7 21:07:39 EST 2000 
Aug 17 12:07:36 localhost kernel:   options:  [pci] [cardbus] [apm] 
Aug 17 12:07:36 localhost kernel: Intel PCIC probe:  
Aug 17 12:07:36 localhost kernel:   Intel i82365sl B step ISA-to-PCMCIA at port 0x3e0 ofs 0x00, 1 socket 
Aug 17 12:07:36 localhost kernel:     host opts [0]: none 
Aug 17 12:07:36 localhost kernel:     ISA irqs (scanned) = 3,4,5,7,10 polling interval = 1000 ms 
Aug 17 12:07:36 localhost cardmgr[859]: starting, version is 3.1.8
Aug 17 12:07:36 localhost cardmgr[859]: watching 1 sockets
Aug 17 12:07:36 localhost kernel: cs: IO port probe 0x1000-0x17ff: clean. 
Aug 17 12:07:36 localhost kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x4d0-0x4d7 
Aug 17 12:07:36 localhost kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
Aug 17 12:07:37 localhost cardmgr[859]: initializing socket 0
Aug 17 12:07:37 localhost kernel: cs: memory probe 0x0d0000-0x0dffff: clean. 
Aug 17 12:07:37 localhost cardmgr[859]: socket 0: KTI ETHER-C16 Fast ethernet
Aug 17 12:07:37 localhost cardmgr[859]: executing: 'insmod /lib/modules/2.2.14-5.0/net/8390.o'
Aug 17 12:07:37 localhost cardmgr[859]: executing: 'insmod /lib/modules/2.2.14-5.0/pcmcia/pcnet_cs.o'
Aug 17 12:07:37 localhost kernel: eth0: NE2000 Compatible: io 0x300, irq 5, hw_addr 00:50:BA:73:6D:1E 
Aug 17 12:07:37 localhost cardmgr[859]: executing: './network start eth0'
Aug 17 12:07:37 localhost pumpd[891]: starting at (uptime 0 days, 0:02:31) Thu Aug 17 12:07:37 2000  
Aug 17 12:07:38 localhost kernel: eth0: found link beat 
Aug 17 12:07:39 localhost kernel: eth0: lost link beat 
Aug 17 12:07:41 localhost kernel: eth0: trigger_send() called with the transmitter busy. 
Aug 17 12:08:07 localhost kernel: eth0: trigger_send() called with the transmitter busy. 
Aug 17 12:08:07 localhost ifdown: Operation failed.
Aug 17 12:08:08 localhost network: Shutting down interface eth0 succeeded

Jochen Friedrich's code:

#include <sys/types.h>
#include <sys/socket.h>
#include <sys/ioctl.h>
#include <net/if.h>
#include <stdio.h>
#include <errno.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>

inline unsigned char
inb (unsigned short port)
{
  unsigned char _v;

  __asm__ __volatile__ ("inb %w1,%0":"=a" (_v):"Nd" (port));
  return _v;
}

inline void
outb (unsigned char value, unsigned short port)
{
  __asm__ __volatile__ ("outb %b0,%w1"::"a" (value), "Nd" (port));
}

static int sockets_open(void)
{
    int sock;
    if ((sock = socket(AF_INET, SOCK_DGRAM, 0)) != -1)
        return sock;
    else if ((sock = socket(AF_IPX, SOCK_DGRAM, 0)) != -1)
        return sock;
    else if ((sock = socket(AF_AX25, SOCK_DGRAM, 0)) != -1)
        return sock;
    else
        return socket(AF_APPLETALK, SOCK_DGRAM, 0);
}
void write_bit(int port, int bit)
{
    outb((bit << 6) + 0x20, port);
    usleep(1);
    outb((bit << 6) + 0xa0, port);
    usleep(1);
    outb((bit << 6) + 0x20, port);
}
int read_bit(int port)
{
    int i;
    outb(0,    port);
    usleep(1);
    outb(0x80, port);
    usleep(1);
    i = inb(port);
    outb(0,    port);
    return (i & 0x10) >> 4;
}
void reset(int port)
{
    outb(0x08, port);
    usleep(1);
    outb(0x0C, port);
    usleep(1);
    outb(0x08, port);
    usleep(1);
    outb(0x0C, port);
    outb(0x00, port);
}
int reada(int port, int adr)
{
    int i,j;

    for (i=0; i<0x20; i++)
      write_bit(port, 1);

    write_bit(port, 0);
    write_bit(port, 1);
    write_bit(port, 1);
    write_bit(port, 0);

    write_bit(port, 0);
    write_bit(port, 0);
    write_bit(port, 0);
    write_bit(port, 0);
    write_bit(port, 0);

    write_bit(port, (adr & 0x10) >> 4);
    write_bit(port, (adr & 0x08) >> 3);
    write_bit(port, (adr & 0x04) >> 2);
    write_bit(port, (adr & 0x02) >> 1);
    write_bit(port, (adr & 0x01) >> 0);

    j = read_bit(port);
    if (j == 1)
      j = read_bit(port);
    for (i=0; i<16; i++) {
      j = (j << 1) + read_bit(port);
    }
    write_bit(port, 1);
    return j;
}
int writea(int port, int adr, int val)
{
    int i,j;

    outb(0x08, port);
    usleep(1);
    outb(0x0C, port);
    usleep(1);
    outb(0x08, port);
    usleep(1);
    outb(0x0C, port);
    outb(0x00, port);

    for (i=0; i<0x20; i++)
      write_bit(port, 1);

    write_bit(port, 0);
    write_bit(port, 1);
    write_bit(port, 0);
    write_bit(port, 1);

    write_bit(port, 0);
    write_bit(port, 0);
    write_bit(port, 0);
    write_bit(port, 0);
    write_bit(port, 0);

    write_bit(port, (adr & 0x10) >> 4);
    write_bit(port, (adr & 0x08) >> 3);
    write_bit(port, (adr & 0x04) >> 2);
    write_bit(port, (adr & 0x02) >> 1);
    write_bit(port, (adr & 0x01) >> 0);

    write_bit(port, 1);
    write_bit(port, 0);

    write_bit(port, (val & 0x8000) >> 15);
    write_bit(port, (val & 0x4000) >> 14);
    write_bit(port, (val & 0x2000) >> 13);
    write_bit(port, (val & 0x1000) >> 12);
    write_bit(port, (val & 0x0800) >> 11);
    write_bit(port, (val & 0x0400) >> 10);
    write_bit(port, (val & 0x0200) >> 9);
    write_bit(port, (val & 0x0100) >> 8);
    write_bit(port, (val & 0x0080) >> 7);
    write_bit(port, (val & 0x0040) >> 6);
    write_bit(port, (val & 0x0020) >> 5);
    write_bit(port, (val & 0x0010) >> 4);
    write_bit(port, (val & 0x0008) >> 3);
    write_bit(port, (val & 0x0004) >> 2);
    write_bit(port, (val & 0x0002) >> 1);
    write_bit(port, (val & 0x0001) >> 0);

    write_bit(port, 1);
    return 0;
}
void main(int argc, char **argv)
{
    int skfd, i, sub, led;
    struct ifreq ifr;

    skfd = sockets_open();
    if (skfd == -1) {
        perror("socket");
        exit(1);
    }
    strcpy(ifr.ifr_name, argv[1]);
    if (ioctl(skfd, SIOCGIFMAP, &ifr) < 0) {
        perror("ioctl");
        exit(1);
    }
    i = atoi(argv[2]);
    switch(i) {
      case 0:
        sub = 0x0000;
        break;
      case 1:
        sub = 0x0100;
        break;
      case 2:
        sub = 0x2000;
        break;
      default:
        sub = 0x2100;
        break;
    }
    ioperm(ifr.ifr_map.base_addr+0x1c, 1, 1);
    reset(ifr.ifr_map.base_addr+0x1c);
    writea(ifr.ifr_map.base_addr+0x1c, 0, 0x8000);
    writea(ifr.ifr_map.base_addr+0x1c, 0, sub);
    close(skfd);
    exit(0);
}

None Re: Angry: HELP! *Still* can't get D-Link DFE-650TX going! (Day 5)

Re: Angry HELP! *Still* can't get D-Link DFE-650TX going! (Day 5) (Harold Boyer)
Date: 2000, Aug 21
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> Funny thing is, it's not just the D-link, it happened with a 3com 656
> modem+adapter card too. Same exact thing.

I don't get this.  The driver for that card doesn't generate any sort
of link beat messages, ever, so how can it be the exact same thing?

> I downloaded a binary for fa_select, but it doesn't run

Binaries are not distribution specific.  Does it give you a specific
error message?

> I downloaded the source for Jochen Friedrich's fix, but I
> don't know C, and can't get it to compile.

gcc -O -o faselect faselect.c

-- Dave

Question D-Link DE-650 PCMCIA ethernet card

Date: 2000, Feb 25
From: Phil Brooke pjbrooke

Hi,

I have a problem with a

  D-Link DE-650 PCMCIA ethernet card (+RJ45 `tail')

when using this with a Gateway 2000 Solo 2100 laptop running Debian 2.0, kernel version 2.0.34 and PCMCIA Card Services 3.1.11.

The symptoms are:

- The card appears to configure okay. (Two high beeps, and ifconfig seems okay -- output shortly.)

- No traffic appears to get off the card.

- The light on the tail with the RJ45 socket never comes on.

ifconfig reports:

 eth0     Link encap:Ethernet  HWaddr 00:80:C8:85:81:39  
          inet addr:192.168.16.99  Bcast:192.168.16.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          Collisions:0 
          Interrupt:3 Base address:0x300 

/proc/net/dev never shows any receive packets; only transmit packets.

The only other anomaly I can find is related to when I remove the card. Sometimes, there is a series of messages (from 19:46:14) like this when the card is ejected:

 Feb 24 19:36:47 diamond syslogd 1.3-3#26: restart.
 Feb 24 19:36:47 diamond kernel: Linux PCMCIA Card Services 3.1.11 
 Feb 24 19:36:47 diamond kernel:   kernel build: 2.0.34 #2 Tue Aug 3 20:22:30 GMT 1999 
 Feb 24 19:36:47 diamond kernel:   options:  [pci] [cardbus] [apm] 
 Feb 24 19:36:47 diamond kernel: Intel PCIC probe:  
 Feb 24 19:36:47 diamond kernel:   Cirrus PD6729 PCI-to-PCMCIA at slot 00:13, port 0xfcfc 
 Feb 24 19:36:47 diamond kernel:     host opts [0]: [ring] [1/3/2] [1/9/2] 
 Feb 24 19:36:47 diamond kernel:     host opts [1]: [ring] [1/3/2] [1/9/2] 
 Feb 24 19:36:47 diamond kernel:     ISA irqs (default) = 3,4,5,9,10,11,12 polling interval = 1000 ms 
 Feb 24 19:36:48 diamond kernel: cs: IO port probe 0x0100-0x03ff: excluding 0x330-0x337 0x370-0x37f 0x398-0x39f 
 Feb 24 19:36:48 diamond kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
 Feb 24 19:36:48 diamond kernel: cs: memory probe 0x0d0000-0x0dffff: clean. 
 Feb 24 19:36:48 diamond kernel: loading device 'eth0'... 
 Feb 24 19:36:48 diamond kernel: eth0: NE2000 Compatible: io 0x300, irq 3, hw_addr 00:80:C8:85:81:39 
 Feb 24 19:46:14 diamond kernel: eth0: interrupt(s) dropped! 
 Feb 24 19:46:14 diamond kernel: eth0: mismatched read page pointers  0 vs 4c. 
 Feb 24 19:46:14 diamond kernel: eth0: mismatched read page pointers  0 vs ff. 
 Feb 24 19:46:14 diamond last message repeated 7 times
 Feb 24 19:46:14 diamond kernel: eth0: unexpected TX-done interrupt, lasttx=20. 
[lots of lines snipped]
 Feb 24 19:46:15 diamond kernel: eth0: Too much work at interrupt, status 0xff 
 Feb 24 19:46:15 diamond kernel: eth0: interrupt from stopped card 

I've checked that the network cable to the hub is okay. The card and tail were reported as working okay before I bought it (however, I have no means to check it with another OS). I *think* I've excluded IRQ conflicts (the laptop IR port was allegedly on IRQ 3; that's now disabled).

The laptop has happily used a modem card before.

I've now run out of things to check. Have I missed anything I can do? (I know the answer is almost certainly `yes', but I can't think of what they are.)

Many thanks in advance,

Phil.

-- Phillip J. Brooke pjb@mithlond48.freeserve.co.uk

None Maybe a bad card??

Re: Question D-Link DE-650 PCMCIA ethernet card (Phil Brooke)
Date: 2000, Feb 25
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The errors at eject time are par for the course.  They aren't related
to your problem.

(1) when you do try to transmit, do you get any additional kernel
    error messages?  Anything about tx timeouts?
(2) Are you sure irq 3 is free?  Does /proc/interrupts show activity
    when you try to send packets through the interface?
(3) You say "the card and tail were reported as working".  Hmmm.  What
    does that mean?  You bought the card used?  Red flag?

I'm not familiar with the dongle on the DE-650.  Can you tell if the
LED(s) are supposed to indicate traffic, or just a valid link?  Many
dongles have a link light; that should be lit whether the driver works
or not, as long as power is supplied to the card and the cable is ok,
unless the card is bad.

-- Dave

Note Possibly...

Re: None Maybe a bad card?? (David Hinds)
Date: 2000, Feb 27
From: Phil Brooke pjbrooke

> The errors at eject time are par for the course.  They aren't related
>  to your problem.

Okay.

> 
>  (1) when you do try to transmit, do you get any additional kernel
>      error messages?  Anything about tx timeouts?

Nothing else at all.

> (2) Are you sure irq 3 is free?

I am, now. The IR interface which was allegedly on that IRQ is disabled. It has the same behaviour on every other IRQ that I think is free.

> Does /proc/interrupts show activity
>      when you try to send packets through the interface?

After insertion of the card, /proc/interrupts shows
 3:          2   pcnet_cs
(I've snipped the other lines).
After an attempt to ping another machine, (16 packets transmitted, 0
packets received), /proc/interrupts shows
 3:          6   pcnet_cs
Further attempts to ping another machine sometimes increase this
count; sometimes they don't.

>  (3) You say "the card and tail were reported as working".  Hmmm.  What
>      does that mean?  You bought the card used?  

Yes.

> Red flag?

I'm becoming very suspicious, sadly.

>  I'm not familiar with the dongle on the DE-650.  Can you tell if the
>  LED(s) are supposed to indicate traffic, or just a valid link?  Many
>  dongles have a link light; that should be lit whether the driver works
>  or not, as long as power is supplied to the card and the cable is ok,
>  unless the card is bad.

I think it's traffic only -- but I'm not convinced.

Can anyone tell me if the media couplers interchangable? (I.e. the 15-pin flat connector <-> RJ-45 connector.) If they are, it would mean that I can beg/borrow another one to try and exclude a fault with that component.

In case it's any further help:

  $ /sbin/cardctl info 0
    5V 16-bit PC Card
    function 0: [ready]
  $ /sbin/cardctl status 0
    Vcc 5.0V  Vpp1 0.0V  Vpp2 0.0V
    interface type is "memory and I/O"
    irq 3 [exclusive] [level]
    function 0:
      config base 0x0400
        option 0x60 status 0x00 copy 0x00
      io 0x0300-0x031f [auto]
  $ /sbin/cardctl config 0
    product info: "D-Link", "DE-650", "Ver 01.00"
    manfid: 0x0149, 0x0265
    function: 6 (network)

Phil.

None Bad hardware seems likely

Re: Note Possibly... (Phil Brooke)
Date: 2000, Feb 28
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I think I'm leaning more towards the bad hardware hypothesis.  The
driver seems ok, and at least some of the card functions are working
ok; fielding interrupts is usually a good sign that there are no
driver goof-ups.  As for swapping dongles, these are generally not
interchangeable.  They are usually vendor or even product specific.

-- Dave

Idea can you try it under Windows?

Re: Question D-Link DE-650 PCMCIA ethernet card (Phil Brooke)
Date: 2000, Feb 27
From: Ingo Ciechowski inki

The Windows95/98/NT drivers I got with my DE-650 worked out of the box (just had to configure the machines IP since I don't have a local DHCP server)

So I'd suggest you try it under Windoze first - if you have such a beast available on another notebook or partition...

This would at least make sure whether the card is working or not.

Ingo

Idea Nit in 3.0.14 pcmcia/network script

Date: 2000, Feb 26
From: Glen Ditchfield gjditchfield

My network.opts script used to contain

    # Host's IP address, netmask, network address, broadcast address
    IPADDR="192.168.0.1"
    #NETMASK=""
    #NETWORK=""
    #BROADCAST=""

This worked, but /var/log/messages contained warning messages:

	...cardmgr[361]: executing: './network start eth0'
	...cardmgr[361]: + Usage:
	...cardmgr[361]: +   ifconfig [-a] [-i] [-v] <interface> [[<AF>] <address>]
	...cardmgr[361]: +   [add <address>[/<prefixlen>]]
	...

The problem was that NETWORK wasn't set when network executed the lines

        # Basic network setup
        BC=${BROADCAST:+broadcast $BROADCAST}
        /sbin/ifconfig $DEVICE up $IPADDR netmask $NETMASK $BC

Shouldn't the 'netmask' parameter be guarded in the same way as 'broadcast'?

***************
*** 75,86 ****
      if [ "$IPADDR" ] ; then

  	# Basic network setup
  	BC=${BROADCAST:+broadcast $BROADCAST}
! 	/sbin/ifconfig $DEVICE up $IPADDR netmask $NETMASK $BC

  	if [ "$NETWORK" ] ; then
  	    /sbin/ifuser $DEVICE $NETWORK || \
! 		/sbin/route add -net $NETWORK netmask $NETMASK dev $DEVICE
  	elif [ "$GATEWAY" ] ; then
  	    /sbin/ifuser $DEVICE $GATEWAY || \
  		/sbin/route add $GATEWAY $DEVICE
--- 75,87 ----
      if [ "$IPADDR" ] ; then

  	# Basic network setup
+ 	NM=${NETMASK:+netmask $NETMASK}
  	BC=${BROADCAST:+broadcast $BROADCAST}
! 	/sbin/ifconfig $DEVICE up $IPADDR $NM $BC

  	if [ "$NETWORK" ] ; then
  	    /sbin/ifuser $DEVICE $NETWORK || \
! 		/sbin/route add -net $NETWORK $NM dev $DEVICE
  	elif [ "$GATEWAY" ] ; then
  	    /sbin/ifuser $DEVICE $GATEWAY || \
  		/sbin/route add $GATEWAY $DEVICE

None You're right

Re: Idea Nit in 3.0.14 pcmcia/network script (Glen Ditchfield)
Date: 2000, Feb 28
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Fixed in the next beta for 3.1.12.

-- Dave

Sad eth0: Tx hung, 11 vs. 0. error with Abocom FE2000 and similar with D-Link DFE-650 cards

Date: 2000, Feb 26
From: Ingo Ciechowski inki

I guess I'm about to get crazy upon this problem. If I only was somewhat deeper in driver development I'd love to figure it out by myself, but I know similar problems have been posted earlier and you sure know how to get it going.

I've got a "Gericom Hydro-Speed" no-name notebook with AMD K6-2 CPU running SuSE Linux 2.2.13 and meanwhile the latest experimental pcmcia package version 3.1.12 (tried with 3.1.10 and 3.1.11 as well).

This system shall work with an Abocom FE2000 10/100 fast ethernet cardbus network card, but it ends finally with " eth0: Tx hung, 11 vs. 0. " messages as described below.
I finally decided to purchase the D-Link DFE-650 16bit fast ethernet card which was in the list of supported devices and ended up with " eth0: Tx timed out, cable problem? TSR=0x42, ISR=0x0, t=902. " messages which look pretty similar for me :-((

BTW: Both cards work well under Windows98 and I also have a 16bit Farallon/3Com 10BaseT card which works under linux.

I'd love to get the FE2000 32bit card to work - and if it only was the D-Link DFE-650 16bit card that'd be great as well.


In /etc/pcmcia/network.opts I inserted some local network information which works fine with the 3Com card:
 ..
    IPADDR="194.162.209.41"
    NETMASK="255.255.255.192"
    NETWORK="194.162.209.0"
    BROADCAST="194.162.209.63"
    # Gateway address for static routing
    GATEWAY="194.162.209.1"
 ..

And since I read that this helped someone else with a similar problem I commented out the line
 exclude irq 3
in /etc/pcmcia/config.opts - also excluded other interrupts as well, but with no success either.


Here's what gets logged in /var/log/messages upon startup with no card inserted:

 Feb 26 16:29:31 training2 kernel: Linux PCMCIA Card Services 3.1.12
 Feb 26 16:29:31 training2 kernel: kernel build: 2.2.13 #3 Sat Feb 26 16:13:07 CET 2000
 Feb 26 16:29:31 training2 kernel: options: [pci] [cardbus] [pnp]
 Feb 26 16:29:31 training2 kernel: PCI routing table version 1.0 at 0xfdf70
 Feb 26 16:29:31 training2 kernel: unknown PCI interrupt router 1106:0686
 Feb 26 16:29:31 training2 kernel: PnP: PNP BIOS installation structure at 0xc00f7580
 Feb 26 16:29:31 training2 kernel: PnP: PNP BIOS version 1.0, entry at f0000:a0e5, dseg at 400
 Feb 26 16:29:31 training2 kernel: Intel PCIC probe:
 Feb 26 16:29:31 training2 kernel: O2Micro OZ6832/OZ6833 PCI-to-CardBus at slot 00:0a, mem 0x68000000
 Feb 26 16:29:31 training2 kernel: host opts [0]: [a 24] [b 21] [c 20] [d 02] [mhpg 18] [fifo 00] [e 2a] [no
 Feb 26 16:29:31 training2 kernel: host opts [1]: [a 24] [b 21] [c 20] [d 02] [mhpg 18] [fifo 00] [e 2a] [no
 Feb 26 16:29:31 training2 kernel: ISA irqs (default) = 3,9,10,11 polling interval = 1000 ms
 Feb 26 16:29:31 training2 kernel: cs: IO port probe 0x0c00-0x0cff: clean.
 Feb 26 16:29:31 training2 kernel: cs: IO port probe 0x0800-0x08ff: clean.
 Feb 26 16:29:31 training2 kernel: cs: IO port probe 0x0100-0x04ff: clean.
 Feb 26 16:29:31 training2 kernel: cs: IO port probe 0x0a00-0x0aff: clean.


The following information was gathered about the Abocom FE2000 card :
                                        
 /var/log/messages:
 Feb 26 16:58:45 training2 kernel: cs: cb_alloc(bus 35): vendor 0x1011, device 0x0019
 Feb 26 16:58:45 training2 cardmgr[467]: initializing socket 1
 Feb 26 16:58:45 training2 cardmgr[467]: socket 1: Linksys EtherFast 10/100
 Feb 26 16:58:45 training2 cardmgr[467]: executing: 'insmod /lib/modules/2.2.13/pcmcia/cb_enabler.o'
 Feb 26 16:58:45 training2 cardmgr[467]: executing: 'insmod /lib/modules/2.2.13/pcmcia/tulip_cb.o'
 Feb 26 16:58:45 training2 kernel: cs: cb_config(bus 35)
 Feb 26 16:58:45 training2 kernel: fn 0 bar 1: io 0x200-0x27f
 Feb 26 16:58:45 training2 kernel: fn 0 bar 2: mem 0xa00c0000-0xa00c03ff
 Feb 26 16:58:45 training2 kernel: fn 0 rom: mem 0xa0080000-0xa00bffff
 Feb 26 16:58:45 training2 kernel: cs: cb_enable(bus 35)
 Feb 26 16:58:45 training2 kernel: bridge io map 0 (flags 0x21): 0x200-0x27f
 Feb 26 16:58:45 training2 kernel: bridge mem map 0 (flags 0x1): 0xa0080000-0xa00c0fff
 Feb 26 16:58:45 training2 kernel: tulip_reap()
 Feb 26 16:58:45 training2 kernel: tulip_attach(bus 35, function 0)
 Feb 26 16:58:45 training2 kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
 Feb 26 16:58:45 training2 kernel: eth0: Digital DS21143 Tulip rev 65 at 0x200, 00:E0:98:7A:6A:40, IRQ 9.
 Feb 26 16:58:45 training2 kernel: eth0: EEPROM default media type Autosense.
 Feb 26 16:58:45 training2 kernel: eth0: Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block.
 Feb 26 16:58:45 training2 kernel: eth0: MII transceiver #0 config 3000 status 7809 advertising 01e1.
 Feb 26 16:58:45 training2 cardmgr[467]: executing: './network start eth0'
 Feb 26 16:58:49 training2 kernel: eth0: Tx hung, 11 vs. 0.
  

 bash-2.03# ifconfig eth0
 eth0 Link encap:Ethernet HWaddr 00:E0:98:7A:6A:40
          inet addr:194.162.209.41 Bcast:194.162.209.63 Mask:255.255.255.192
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:1 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          Interrupt:9 Base address:0x200


 (while trying to ping 194.162.209.1)
 bash-2.03# tcpdump -nlieth0
 User level filter, protocol ALL, datagram packet socket
 tcpdump: listening on eth0
 17:03:47.209806 arp who-has 194.162.209.1 tell 194.162.209.41 (0:e0:98:7a:6a:40)
 17:03:48.201157 arp who-has 194.162.209.1 tell 194.162.209.41 (0:e0:98:7a:6a:40)



 bash-2.03# cardctl config
 Socket 0:
  not configured
 Socket 1:
  Vcc 3.3V Vpp1 3.3V Vpp2 3.3V
  interface type is "cardbus"
  irq 9 [exclusive] [level]
  function 0:
    io 0x0200-0x027f [32bit]

 bash-2.03# tulip-diag -a
 tulip-diag.c:v1.03 5/20/98 Donald Becker (becker@cesdis.gsfc.nasa.gov)
 Chip Index #1: Found a DC21142 Tulip card at PCI bus 35, device 0 I/O 0x200.
 Digital DS21142 Tulip chip registers at 0x200:
  f8a08000 ffffffff ffffffff 00ab6810 00ab6a10 f0000146 b20e0000 f3fe0000
  e0000000 ffffcbf8 ffffffff 00000000 000000c6 ffff0000 fff80000 8ff90000
  ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
  ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
 The Rx process state is 'Stopped'.
 The Tx process state is 'Stopped'.
 Transmit stopped, Receive stopped, half-duplex.
 The transmit threshold is 128.
 Port selection is MII, half-duplex.
 EEPROM transceiver/media description for the DC21142 chip.
 
 Leaf node at offset 128, default media type 0000 (10baseT).
 0 transceiver description blocks:

 bash-2.03# tulip-diag -e
 tulip-diag.c:v1.03 5/20/98 Donald Becker (becker@cesdis.gsfc.nasa.gov)
 Chip Index #1: Found a DC21142 Tulip card at PCI bus 35, device 0 I/O 0x200.
 EEPROM transceiver/media description for the DC21142 chip.
 
 Leaf node at offset 128, default media type 0000 (10baseT).
  0 transceiver description blocks:

 bash-2.03# tulip-diag -m
 tulip-diag.c:v1.03 5/20/98 Donald Becker (becker@cesdis.gsfc.nasa.gov)
 Chip Index #1: Found a DC21142 Tulip card at PCI bus 35, device 0 I/O 0x200.
 EEPROM transceiver/media description for the DC21142 chip.
 
 Leaf node at offset 128, default media type 0000 (10baseT).
 0 transceiver description blocks:
 MII PHY found at address 0, status 0x782d.
 MII PHY #0 transceiver registers:
   3000 782d 0040 6212 01e1 0021 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   1000 0000 0000 0000 0000 0000 0100 0000
   003c d006 0f00 ff00 002c 0000 0080 000b.
  Internal autonegotiation state is 'Autonegotiation disabled'.

-------------------------------------------------------------------------------------------

And here's what I figured out about the D-Link DFE-650 card:

 /var/log/messages:
 Feb 26 17:09:18 training2 cardmgr[467]: initializing socket 1
 Feb 26 17:09:18 training2 cardmgr[467]: socket 1: KTI ETHER-C16 Fast ethernet
 Feb 26 17:09:18 training2 cardmgr[467]: executing: 'insmod /lib/modules/2.2.13/net/8390.o
'
 Feb 26 17:09:18 training2 cardmgr[467]: executing: 'insmod /lib/modules/2.2.13/pcmcia/pcn
et_cs.o'
 Feb 26 17:09:18 training2 kernel: eth0: NE2000 Compatible: io 0x300, irq 9, hw_addr 00:E0
:98:77:92:8F
 Feb 26 17:09:18 training2 cardmgr[467]: executing: './network start eth0'
 Feb 26 17:09:20 training2 kernel: eth0: found link beat
 Feb 26 17:09:38 training2 kernel: eth0: Tx timed out, cable problem? TSR=0x42, ISR=0x0, t=895.
 Feb 26 17:09:48 training2 kernel: eth0: Tx timed out, cable problem? TSR=0x42, ISR=0x0, t=1000.


 bash-2.03# ifconfig eth0
 eth0 Link encap:Ethernet HWaddr 00:E0:98:77:92:8F
          inet addr:194.162.209.41 Bcast:194.162.209.63 Mask:255.255.255.192
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:4 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          Interrupt:9 Base address:0x300


 (while trying to ping 194.162.209.1)
 bash-2.03# tcpdump -nlieth0
 User level filter, protocol ALL, datagram packet socket
tcpdump: listening on eth0
 17:09:58.931129 arp who-has 194.162.209.1 tell 194.162.209.41 (0:e0:98:77:92:8f)
 17:09:58.981151 arp who-has 194.162.209.1 tell 194.162.209.41 (0:e0:98:77:92:8f)
 17:10:08.931127 arp who-has 194.162.209.1 tell 194.162.209.41 (0:e0:98:77:92:8f)


 bash-2.03# cardctl config
 Socket 0:
  not configured
 Socket 1:
  Vcc 5.0V Vpp1 0.0V Vpp2 0.0V
  interface type is "memory and I/O"
  irq 9 [exclusive] [level]
  function 0:
    config base 0x0400
      option 0x60 status 0x00 copy 0x00
    io 0x0300-0x031f [auto]



---


Of course I'm willing to add any additional useful information immediately if that'd help to solve my problem.


Thanks a lot for your patience,

Ingo
Ciechowski@cis-computer.com

News D-Link DFE-650 problem solved - FE2000 still not working

Re: Sad eth0: Tx hung, 11 vs. 0. error with Abocom FE2000 and similar with D-Link DFE-650 cards (Ingo Ciechowski)
Date: 2000, Feb 26
From: Ingo Ciechowski inki

I've just found Anthony Jamesons recommendation and his great little tool as postes under #46. in this group.

Since I found that I ran into the same problem as Phil Brooke with this card I gave it a try and found that Anthony's enabling code works pretty well for the newer DFE-650 cards.

Thanks a lot for this input - and I hope it will make it's way into one of the new versions of the pcmcia sources.

However, this does not solve my initial problem with the FE2000 card. Since that one is a real 32bit cardbus card which makes use of the 100BaseT speed, I'd still love to find a way to get it going...

Hope someone get's an idea ;-)

Ingo

Idea Fiberline FL-4680 working!

Date: 2000, Feb 28
From: CW Zuckschwerdt zany

I recently bought a
 FIBERLINE FL-4680
 16-Bit PCMCIA NIC

It is working great with pcnet_cs driver.

Although cpu load on my 166MHz pentium is high I reach the full 10,000 KBit/sec.

This PC-Card was amazingly cheap! I paid EUR 35,- (about the same amount in USD)

Question No success with either 10/100 Etherjet nor 3Com cards on Thinkpad

Date: 2000, Mar 01
From: lyle borg-graham lyle

I have gotten the same "SIOCADDRT: Network is unreachable" message with both the IBM 10/100 EtherJet card and the 3Com 10/100 3CXFE575CT card. The machine is a Thinkpad 600E, running Red Hat 6.1, kernel 2.2.14, and using the pcmcia-cs-3.1.11 distribution. Apparently all the network configuration files are ok. I note some bizzare things, such as the ability to ping locally even when the card is not installed.

As perhaps a side note, at some point in this process the cardmgr started sending messages directly to the screen (i.e. "Network unreachable") during bootup, and *not* to /var/log/messages as it did before.

Thanks very much for any ideas!

Lyle

Included below are some (hopefully) useful tidbits (with the 3Com card installed):

   [root@cognilap ~]# uname -rv
   2.2.14 #8 Tue Feb 29 17:13:24 CET 2000

   [root@cognilap ~]# cardctl -V
   cardctl version 3.1.11

   [root@cognilap ~]# sh -x /etc/pcmcia/network start eth0
   + [ -r ./shared ]
   + . /etc/pcmcia/shared
   ++ [ 2 -lt 2 ]
   ++ ACTION=start
   ++ DEVICE=eth0
   + get_info eth0
   + [ -d /var/state/pcmcia ]
   ++ cat /var/state/pcmcia/scheme
   + SCHEME=
   + STAB=/var/state/pcmcia/stab
   + [ ! ]
   + SCHEME=default
   + grep_stab eth0
   + local CLASS DEV
   + read SOCKET CLASS DRIVER INSTANCE DEV MAJOR MINOR
   + [ eth0 = ]
   + read SOCKET CLASS DRIVER INSTANCE DEV MAJOR MINOR
   + [ eth0 = Fast ]
   + read SOCKET CLASS DRIVER INSTANCE DEV MAJOR MINOR
   + [ eth0 = eth0 ]
   + return 0
   ++ /sbin/ifconfig eth0
   ++ sed -n -e s/.*addr \([^ ]*\) */\1/p
   + HWADDR=00:00:86:51:E6:E4
   + ADDRESS=default,1,0,00:00:86:51:E6:E4
   + . /etc/pcmcia/network.opts
   ++ [ -f /etc/sysconfig/network-scripts/ifcfg-eth0 ]
   ++ BOOTP=n
   ++ IPADDR=128.122.146.142
   ++ NETWORK=128.122.146.0
   ++ NETMASK=255.255.255.0
   ++ BROADCAST=128.122.255.255
   ++ GATEWAY=128.122.146.1
   ++ DOMAIN=cns.nyu.edu
   + RESOLV=/etc/resolv.conf
   + test
   + is_true
   + [ = y -o = Y -o = yes -o = YES ]
   + is_true n
   + [ n = y -o n = Y -o n = yes -o n = YES ]
   + is_true
   + [ = y -o = Y -o = yes -o = YES ]
   + [ 128.122.146.142 ]
   + BC=broadcast 128.122.255.255
   + /sbin/ifconfig eth0 up 128.122.146.142 netmask 255.255.255.0 broadcast 128.122.255.255
   + [ 128.122.146.0 ]
   + /sbin/ifuser eth0 128.122.146.0
   + /sbin/route add -net 128.122.146.0 netmask 255.255.255.0 dev eth0
   + test 128.122.146.1
   + /sbin/route add default gw 128.122.146.1 metric 1
   SIOCADDRT: File exists
   + [ cns.nyu.edu ]
   + echo # eth0 begin
   + test cns.nyu.edu
   + echo domain cns.nyu.edu
   + test
   + echo # eth0 end
   + sed -e /# eth0 begin/,/# eth0 end/d /etc/resolv.conf
   + mv /etc/resolv.conf.N /etc/resolv.conf
   + [ ]
   + [ ]
   + start_fn eth0
   + /sbin/ifup eth0
   SIOCADDRT: Network is unreachable
   + exit 0


Now, with the cable *unplugged* (128.122.154.50 is another machine):

   [root@cognilap ~]# ping 128.122.154.50
   PING 128.122.154.50 (128.122.154.50) from 128.122.154.50 : 56(84) bytes of data.
   64 bytes from 128.122.154.50: icmp_seq=0 ttl=255 time=0.1 ms
   64 bytes from 128.122.154.50: icmp_seq=1 ttl=255 time=0.1 ms
   64 bytes from 128.122.154.50: icmp_seq=2 ttl=255 time=0.1 ms
   64 bytes from 128.122.154.50: icmp_seq=3 ttl=255 time=0.0 ms

   --- 128.122.154.50 ping statistics ---
   4 packets transmitted, 4 packets received, 0% packet loss
   round-trip min/avg/max = 0.0/0.0/0.1 ms



In the file /etc/pcmcia/network.opts:

       if [ -f /etc/sysconfig/network-scripts/ifcfg-eth0 ] ; then
           start_fn () {
               /sbin/ifup $1
           }
           stop_fn () {
               /sbin/ifdown $1
           }
       fi



       case "$ADDRESS" in
       *,*,*,*)

           BOOTP="n"
           IPADDR="128.122.146.142"
           NETWORK="128.122.146.0"
           NETMASK="255.255.255.0"
   BROADCAST="128.122.255.255"
           GATEWAY="128.122.146.1"
           DOMAIN="cns.nyu.edu"

           ;;
       esac


In the file /etc/pcmcia/config.opts:

#
# Local PCMCIA Configuration File
#
# System resources available for PCMCIA devices
#
include port 0x100-0x4ff, port 0x1000-0x17ff
include memory 0xc0000-0xfffff
include memory 0xa0000000-0xa0ffffff, memory 0x60000000-0x60ffffff
#
# Extra port range for IBM Token Ring
#
include port 0xa00-0xaff
#
# Resources we should not use, even if they appear to be available
#
# First built-in serial port
exclude irq 4
# Second built-in serial port
#exclude irq 3
# First built-in parallel port
exclude irq 7
#
# Additional stuff from the PCMCIA-HOWTO
exclude port 0x230-0x233
exclude irq 5
exclude port 0x2f8-0x2ff

# Modifications from A. Krumeich
include port 0x600-0x6ff
include irq 11

# Examples of options for loadable modules
#
# To fix sluggish network with IBM ethernet adapter...
#module "pcnet_cs" opts "mem_speed=600"
#
# Options for Xircom Netwave driver...
#module "netwave_cs" opts "domain=0x100 scramble_key=0x0"
#
# Options for IBM Token Ring adapters
#module "ibmtr_cs" opts "mmiobase=0xd0000 srambase=0xd4000"

More Addendum

Re: Question No success with either 10/100 Etherjet nor 3Com cards on Thinkpad (lyle borg-graham)
Date: 2000, Mar 01
From: lyle borg-graham lyle

I should add that I get the "good" two high beeps when the 3Com card is inserted. Also, it works under Windows.

Lyle

None This is a configuration error

Re: Question No success with either 10/100 Etherjet nor 3Com cards on Thinkpad (lyle borg-graham)
Date: 2000, Mar 01
From: David Hinds <dhinds@pcmcia.sourceforge.org>

"Network is unreachable" indicates a network configuration error.

>    ++ IPADDR=128.122.146.142
>    ++ NETWORK=128.122.146.0
>    ++ NETMASK=255.255.255.0
>    ++ BROADCAST=128.122.255.255
>    ++ GATEWAY=128.122.146.1

These settings are inconsistent.  Assuming your NETWORK and NETMASK
are correct, you should have BROADCAST=128.122.146.255.

>    + start_fn eth0
>    + /sbin/ifup eth0
>    SIOCADDRT: Network is unreachable

Your network.opts file is odd.  You should either specify all your
network settings in network.opts (as above), or replace the entire
file with just the code from the PCMCIA-HOWTO to use ifup/ifdown to
configure the network.  You should not do both: what happens is the
PCMCIA script configures eth0, then does the "ifup eth0", which
re-configures the interface using the Red Hat netconf data.

> Now, with the cable *unplugged* (128.122.154.50 is another machine):
> 
>    [ root@cognilap ~]# ping 128.122.154.50
>    PING 128.122.154.50 (128.122.154.50) from 128.122.154.50 : 56(84)
> bytes of data.

128.122.154.50 may belong to another machine, but you have also
configured this machine to have the same IP address.  It isn't the IP
address you gave in network.opts, but I'll bet it is the address that
shows up if you run "netconf".  You are pinging yourself; the kernel
knows that the packets don't have to go over the wire, so it works
even when the cable is unplugged.

-- Dave

None Progress, but...

Re: None This is a configuration error (David Hinds)
Date: 2000, Mar 01
From: lyle borg-graham lyle

> "Network is unreachable" indicates a network configuration error.

> These settings are inconsistent.  Assuming your NETWORK and NETMASK
> are correct, you should have BROADCAST=128.122.146.255.

> Your network.opts file is odd. You should either specify all your network settings in network.opts (as above), or replace the entire file with just the code from the

> PCMCIA-HOWTO to use ifup/ifdown to configure the network.

Ok, followed these suggestions, and now no "Network unreachable" message. Thanks!

However, I still can't seem to access the network.

>> Now, with the cable *unplugged* (128.122.154.50 is another machine):
>> 
>>    [ root@cognilap ~]# ping 128.122.154.50
>>    PING 128.122.154.50 (128.122.154.50) from 128.122.154.50 : 56(84)
>> bytes of data.

> 128.122.154.50 may belong to another machine, but you have also
> configured this machine to have the same IP address.  It isn't the IP
> address you gave in network.opts, but I'll bet it is the address that
> shows up if you run "netconf".  You are pinging yourself; the kernel
> knows that the packets don't have to go over the wire, so it works
> even when the cable is unplugged.

Well, the only place that 128.122.154.50 shows up is in /etc/hosts. The above behaviour still occurs with another IP that is *not* in /etc/hosts, in fact as long as the IP has 128.122.*.*. And, if I use a hostname, I get:

 [ root@cognilap ~]# ping calaf.cns.nyu.edu
 ping: unknown host calaf.cns.nyu.edu

Lyle

Question CardBus and Product Info

Date: 2000, Mar 01
From: Sergio Talens-Oliag sto

I've seen in a message from David Hinds that the CardBus cards that do not provide product info are not supported under linux.

I have a Dynalink L100C32-2 and I know of other cards with the same problem (Argosy 10/100 EN-235, Conceptronics CON100TC).

The questions are:

  • Does anyone knows what changes are needed to make the pcmcia package work with this kind of cards?
  • Is there any documentation I can read to try to add support for them?

Thanks in advance,

    Sergio

None Re: Question: CardBus and Product Info

Re: Question CardBus and Product Info (Sergio Talens-Oliag)
Date: 2000, Mar 06
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The Dynalink card does have product info; there was a PCMCIA driver
bug that prevented it from being used properly.  This is fixed in the
current beta for 3.1.12.  The card still doesn't work, because the
current tulip driver isn't able to configure it correctly.  That's a
more serious issue and I don't know how to fix that.

As for the other cards you mention, I don't know anything about them,
so I don't know if the same 3.1.12 fix will apply to them or not.  I
also can't guess if, independent of the product info, these cards are
likely to work under Linux anyway.

-- Dave

News Dynalink L100C32 and Product Info

Re: None Re: Question: CardBus and Product Info (David Hinds)
Date: 2000, Mar 07
From: Sergio Talens-Oliag sto

Last sunday I sent an e-mail to support@dynalink.nl and on
monday (this guys are really fast), they sent me a DOS utility
to upgrade the CIS (it gives the card a manufacturer id, so
cardctl can detect it) and an experimental linux driver (the
card uses a realtek 8139 chip, so the driver is the rtl8139.c
from Donald Becker, with a patch to detect the IRQ).

I've tested it and it works, but only if you have two cards.

I did two tests:

1. In my first test I was using another card on slot 0 (a
friend's Dynalink L10C) and when i inserted the LC100C32 it
worked fine.

2. In the second test, i used only the LC100C32, but it locks
the machine. I suppose the problem is in the patch to detect
the IRQ, but i think it's easy to fix, if i succed i'll post a
message with the patches.

  Sergio

Question Best PC Card Ethernet Interface for 10/100, DHCP under RH6.1

Date: 2000, Mar 07
From: Dave Aiello dave_aiello

I am new to Linux, although I am an experienced Solaris end user. I bought a RedHat 6.1 certified laptop from Dell the other day, with the idea of totally immersing myself in Linux. I do not want to spend the time fooling with hardware configurations unless I have to.

My configuration is a Dell Inspiron 7500 with a 3com 3CCFE575 running on the RH 6.1 installation provided by Dell with minimal configuration edits.

I want a 10/100 Ethernet PC Card that is capable of running DHCP without any hiccups. I am willing to go out and buy the most trouble free PC Card of this nature (and abandon the 3CCFE575 if necessary).

The problem I am having is that I cannot determine from reading these message forums if any PC Card NICs can live up to my wishlist. Are there any obvious choices that would satisfy me?

Thanks,

Dave Aiello
CTDATA

Question Thinkpad 600E and IBM etherjet 100/10

Date: 2000, Mar 11
From: Andrew Fong jester

I have installed the latest version of the pcmcia package. /var/log/messages reports that there is a card in the slot. I get two high tone beeps reporting that the card was intialized. I am not able to ping anything besides the local machine. I did change the memory addresses in /etc/pcmcia/config.opts. Any help would be appriciated. -Andrew Fong

More I dont get lights

Re: Question Thinkpad 600E and IBM etherjet 100/10 (Andrew Fong)
Date: 2000, Mar 11
From: Andrew Fong jester

There are no lights going on on the grey box conecting the ethernet wire to the card. Andrew

None More information?

Re: Question Thinkpad 600E and IBM etherjet 100/10 (Andrew Fong)
Date: 2000, Mar 13
From: David Hinds <dhinds@pcmcia.sourceforge.org>

System log messages?

The driver is experimental and people have mixed success with it.

I assume that if you run "ifconfig", the output looks ok?

-- Dave

Question Argosy EN-235 continued.

Date: 2000, Mar 15
From: Robert Rossmann rbr

I installed the new pcmcia package 3.1.13 and now the card is found but it won't work. This are the entries in the /var/log/messages file

This is for tulip

Mar 15 14:22:07 armin cardmgr[785]: starting, version is 3.1.13
Mar 15 14:22:07 armin cardmgr[785]: watching 2 sockets
Mar 15 14:22:07 armin kernel: cs: IO port probe 0x1000-0x17ff: clean.
Mar 15 14:22:07 armin kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x207 0x220-0x22f 0x300-0x307 0x378-0x37f 0x388-0x38f 0x398-0x39f 0x400-0x40f 0x480-0x48f 0x4c0-0x4df
Mar 15 14:22:07 armin kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Mar 15 14:22:07 armin cardmgr[785]: initializing socket 0
Mar 15 14:22:07 armin cardmgr[785]: socket 0: Argosy EN-235 Fast Ethernet
Mar 15 14:22:07 armin cardmgr[785]: executing: 'insmod /lib/modules/2.2.13/pcmcia/cb_enabler.o'
Mar 15 14:22:07 armin cardmgr[785]: executing: 'insmod /lib/modules/2.2.13/pcmcia/tulip_cb.o'
Mar 15 14:22:07 armin kernel: cs: cb_config(bus 2)
Mar 15 14:22:07 armin kernel:   fn 0 bar 1: io 0xa00-0xaff
Mar 15 14:22:07 armin kernel:   fn 0 bar 2: mem 0x5042000-0x50421ff
Mar 15 14:22:07 armin kernel: cs: cb_enable(bus 2)
Mar 15 14:22:07 armin kernel:   bridge io map 0 (flags 0x21): 0xa00-0xaff
Mar 15 14:22:07 armin kernel:   bridge mem map 0 (flags 0x1): 0x5042000-0x5042fff
Mar 15 14:22:07 armin kernel: tulip_reap()
Mar 15 14:22:07 armin kernel: tulip_attach(bus 2, function 0)
Mar 15 14:22:07 armin kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
Mar 15 14:22:07 armin kernel: eth0: Digital DS21143 Tulip rev 16 at 0xa00, EEPROM not present, 00:4C:69:6E:75:79, IRQ 9.
Mar 15 14:22:07 armin kernel: eth0:  Missing EEPROM, this interface may not work correctly!
Mar 15 14:22:07 armin cardmgr[785]: executing: './network start eth0'
Mar 15 14:22:10 armin kernel: eth0: Tx hung, 11 vs. 0.
Mar 15 14:22:10 armin kernel: eth0: 21140 transmit timed out, status 0801fbfc, SIA 0000000f 00000000 00000018 58fab388, resetting...
Mar 15 14:22:16 armin kernel: eth0: Tx hung, 11 vs. 0.
Mar 15 14:22:16 armin kernel: eth0: 21140 transmit timed out, status 0801fbfc, SIA 0000000f 00000000 00000018 58fab388, resetting...
Mar 15 14:22:22 armin kernel: eth0: Tx hung, 11 vs. 0.
Mar 15 14:22:22 armin kernel: eth0: 21140 transmit timed out, status 0801fbfc, SIA 0000000f 00000000 00000018 58fab388, resetting...
Mar 15 14:22:28 armin kernel: eth0: Tx hung, 11 vs. 0.
Mar 15 14:22:28 armin kernel: eth0: 21140 transmit timed out, status 0801fbfc, SIA 0000000f 00000000 00000018 58fab388, resetting...
Mar 15 14:22:34 armin kernel: eth0: Tx hung, 11 vs. 0.
Mar 15 14:22:34 armin kernel: eth0: 21140 transmit timed out, status 0801fbfc, SIA 0000000f 00000000 00000018 58fab388, resetting...
Mar 15 14:22:35 armin cardmgr[785]: executing: './network check eth0'
Mar 15 14:22:36 armin cardmgr[785]: shutting down socket 0
Mar 15 14:22:36 armin cardmgr[785]: executing: './network stop eth0'
Mar 15 14:22:36 armin kernel: tulip_detach(eth0)
Mar 15 14:22:36 armin kernel: cs: cb_disable(bus 2)
Mar 15 14:22:36 armin kernel: cs: cb_release(bus 2)
Mar 15 14:22:36 armin cardmgr[785]: executing: 'rmmod tulip_cb'
Mar 15 14:22:36 armin kernel: tulip_reap()
Mar 15 14:22:36 armin cardmgr[785]: executing: 'rmmod cb_enabler'
Mar 15 14:22:36 armin cardmgr[785]: exiting

This is for epic

Mar 15 14:24:08 armin cardmgr[835]: starting, version is 3.1.13
Mar 15 14:24:08 armin cardmgr[835]: watching 2 sockets
Mar 15 14:24:08 armin kernel: cs: IO port probe 0x1000-0x17ff: clean.
Mar 15 14:24:08 armin kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x207 0x220-0x22f 0x300-0x307 0x378-0x37f 0x388-0x38f 0x398-0x39f 0x400-0x40f 0x480-0x48f 0x4c0-0x4df
Mar 15 14:24:08 armin kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Mar 15 14:24:08 armin cardmgr[835]: initializing socket 0
Mar 15 14:24:08 armin cardmgr[835]: socket 0: Argosy EN-235 Fast Ethernet
Mar 15 14:24:08 armin cardmgr[835]: executing: 'insmod /lib/modules/2.2.13/pcmcia/cb_enabler.o'
Mar 15 14:24:08 armin cardmgr[835]: executing: 'insmod /lib/modules/2.2.13/pcmcia/epic_cb.o'
Mar 15 14:24:08 armin kernel: epic100.c:v1.06 2/10/98 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/epic100.html
Mar 15 14:24:08 armin kernel: cs: cb_config(bus 2)
Mar 15 14:24:08 armin kernel:   fn 0 bar 1: io 0xa00-0xaff
Mar 15 14:24:08 armin kernel:   fn 0 bar 2: mem 0x5042000-0x50421ff
Mar 15 14:24:08 armin kernel: cs: cb_enable(bus 2)
Mar 15 14:24:08 armin kernel:   bridge io map 0 (flags 0x21): 0xa00-0xaff
Mar 15 14:24:08 armin kernel:   bridge mem map 0 (flags 0x1): 0x5042000-0x5042fff
Mar 15 14:24:08 armin kernel: epic_attach(bus 2, function 0)
Mar 15 14:24:08 armin kernel: eth0: SMSC EPIC/C 83c175 at 0xa00, IRQ 9, 00:00:40:00:aa:4a.
Mar 15 14:24:08 armin kernel: eth0: ***WARNING***: No MII transceiver found!
Mar 15 14:24:08 armin cardmgr[835]: executing: './network start eth0'
Mar 15 14:24:16 armin cardmgr[835]: executing: './network check eth0'
Mar 15 14:24:17 armin cardmgr[835]: shutting down socket 0
Mar 15 14:24:17 armin cardmgr[835]: executing: './network stop eth0'
Mar 15 14:24:17 armin kernel: epic_detach(eth0)
Mar 15 14:24:17 armin kernel: cs: cb_disable(bus 2)
Mar 15 14:24:17 armin kernel: cs: cb_release(bus 2)
Mar 15 14:24:17 armin cardmgr[835]: executing: 'rmmod epic_cb'
Mar 15 14:24:17 armin cardmgr[835]: executing: 'rmmod cb_enabler'
Mar 15 14:24:17 armin cardmgr[835]: exiting

Any clues?

Thx

Robert

None That doesn't look so good to me

Re: Question Argosy EN-235 continued. (Robert Rossmann)
Date: 2000, Mar 15
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Based on the output, I'd say that you are out of luck unless you can
find out from the vendor what chipset this card uses.

Is the hw address reported by the tulip driver correct?  Maybe it is
just a new / unsupported tulip variant.  I am not familiar enough with
that driver to have any specific suggestions for what modifications
might be needed to make the driver work with this card.

-- Dave

More No wrong HW address

Re: None That doesn't look so good to me (David Hinds)
Date: 2000, Mar 16
From: Robert Rossmann rbr

No the HW-address according to the Windows driver is 00-10-d7-09-11-11 Windows is loading a CB8139.

Thx for your help

Robert

None So it isn't a tulip at all

Re: More No wrong HW address (Robert Rossmann)
Date: 2000, Mar 16
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Oh.  The linux rtl8139 driver hasn't been modified to support cardbus
cards yet.

-- Dave

Question Unsupported Tulip card only works with DHCP

Date: 2000, Mar 18
From: Mike McDonald <mcdonald@aeac.org>

I've got an unsupported Intel 21142/3 based 10/100 PC card that works fine using the tulip driver as long as I configure it using DHCP.

When I configure the card manually, it won't work until I reset it by issuing a "ifconfig eth0 down up". The only problem is that when I do this, I lose the default route.

My guess is that pump is somehow resetting the card when it configures it.

I know the card isn't supported, but I'd still like to use it if possible. Is there an easy way to force the card to reset without losing routes?

Thanks,
Mike

Notebook: Gateway Solo 9300 running Redhat 6.1
Card: SHOMITI 100TX_CardBus PS1101
Manfid: 0x013f, 0x4120

Syslog Messages(when not working):
Mar 17 14:35:18 localhost kernel: eth0: 21140 transmit timed out, status f0260000, SIA 40a1d2cd ffff0001 fffbffff 8ff40008, resetting...
Mar 17 14:35:18 localhost kernel: eth0: transmit timed out, switching to 100baseTx media.
...

None I know it isn't a real solution...

Re: Question Unsupported Tulip card only works with DHCP (Mike McDonald)
Date: 2000, Apr 28
From: David Hinds <dhinds@pcmcia.sourceforge.org>

but why not just do the reset, and then set up the default route
again?  That seems to me to be only marginally harder than doing just
the reset by itself.

-- Dave

Question trouble with netgear FA410TXC

Date: 2000, Mar 23
From: Matthew Austin yogi

I am running redhat 6.1 distro on a sony vaio picturebook (PCG-C1XS) and I cannot seem to get connectivity to my network.

I have assigned myself a fixed IP address to isolate the issue (was unable to get a DHCP address anyway ;-))

The adapter comes up and is recognized but no connectivity. I can ping the machine at the ip address I have assigned it but nothing on my network, including machines on the same subnet. The dongle lights just flash on and off simultaneous about every second.

I downloaded and compiled the pcmcia-3.1.14 package in the hopes that perhaps there was some issue with the redhat package. I added the recommended changes to network.opts to allow me to continue to use linuxconf.

I have forced a change in io port and IRQ to see if that was an issue as recommended by changing config.opts . . . no change.

Since compiling the new package I have been getting 2 new messages.

/var/log/messages

eth0: found link beat
eth0: lost link beat

Any thoughts?

Feedback Hardware Version

Re: Question trouble with netgear FA410TXC (Matthew Austin)
Date: 2000, Mar 25
From: Jochen Friedrich jochen1

Hi Matthew,

Please have a look at messages #46 and #47. It might be that you have the same hardware version that makes the known trouble. You might want to try the provided enabler code and compare your MAC address against the 2 listed in the above threads.

-- Jochen

Sad tried code but no go, MAC address within problem range

Re: Feedback Hardware Version (Jochen Friedrich)
Date: 2000, Mar 27
From: Matthew Austin yogi

Hi Jochen,

thanks for the code, but I am still stuck.  I tried your code (with some help compiling provided by my UNIX SA ;-)) and I get core dumps for any of the tried options with both the old enabler code and the new enabler code.  Below is /var/log/messages and my attempt with the new code.  It does look like my MAC address is within the problem range.

Mar 27 12:06:33 yogimind cardmgr[367]: socket 0: NetGear FA410TXC Fast Ethernet
Mar 27 12:06:33 yogimind cardmgr[367]: executing: 'insmod /lib/modules/2.2.12-20/net/8390.o'
Mar 27 12:06:33 yogimind cardmgr[367]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/pcnet_cs.o'
Mar 27 12:06:33 yogimind kernel: eth0: NE2000 Compatible: io 0x800, irq 5, hw_addr 00:E0:98:77:A9:5D 
Mar 27 12:06:33 yogimind cardmgr[367]: executing: './network start eth0'
Mar 27 12:06:35 yogimind kernel: eth0: found link beat 
Mar 27 12:06:36 yogimind kernel: eth0: lost link beat 

[maustin@yogimind maustin]$ gcc -Wall -O -o fa_select eth.c
eth.c: In function `writea':
eth.c:104: warning: unused variable `j'
eth.c: At top level:
eth.c:150: warning: return type of `main' is not `int'
[maustin@yogimind maustin]$ ./fa_select eth0 0
Segmentation fault (core dumped)
[maustin@yogimind maustin]$ ./fa_select eth0 1
Segmentation fault (core dumped)
[maustin@yogimind maustin]$ ./fa_select eth0 2
Segmentation fault (core dumped)
[maustin@yogimind maustin]$ ./fa_select eth0 3
Segmentation fault (core dumped)
[maustin@yogimind maustin]$

-matthew

More What version

Re: Sad tried code but no go, MAC address within problem range (Matthew Austin)
Date: 2000, Mar 31
From: Jochen Friedrich jochen1

Hi Matthew,

what version of linux, libc and gcc are you using? Did you run the program as root (it needs root for ioperm() to enable user space I/O access)? Do you have a chance to add "-g" to your compile parameters and run gdb ./fa_select? (Then do a "run eth0 0" and record the result of "bt").

Anyways, I placed a binary (needs glibc 2.1) on http://www.gxsnmp.org/fa_select

-- Jochen

Sad still no go even with your binary . . . here's the details

Re: More What version (Jochen Friedrich)
Date: 2000, Mar 31
From: Matthew Austin yogi

#info you requested

kernel-2.2.12-20
libc-5.3.12-31
glibc-2.1.2-11

#run with your binary from http://www.gxsnmp.org/fa_select

[root@yogimind maustin]# gdb fa_select
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux"...
(gdb) run eth0 0
Starting program: /home/maustin/fa_select eth0 0

Program received signal SIGSEGV, Segmentation fault.
0x80485d2 in outb ()
(gdb) bt
#0 0x80485d2 in outb ()
#1 0x804877d in reset ()
#2 0x8048e2e in main ()
#3 0x400301eb in __libc_start_main (main=0x8048d08 <main>, argc=3,
    argv=0xbffffce4, init=0x80483bc <_init>, fini=0x8048eec <_fini>,
    rtld_fini=0x4000a610 <_dl_fini>, stack_end=0xbffffcdc)
    at ../sysdeps/generic/libc-start.c:90
(gdb) q

#run with your updated source and suggested flag

[root@yogimind maustin]# gcc -g -Wall -O -o fa_select eth.c
eth.c: In function `writea':
eth.c:104: warning: unused variable `j'
eth.c: At top level:
eth.c:150: warning: return type of `main' is not `int'
[root@yogimind maustin]# gdb ./fa_select
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux"...
(gdb) run eth0 0
Starting program: /home/maustin/./fa_select eth0 0

Program received signal SIGSEGV, Segmentation fault.
0x8048667 in reset (port=2076) at eth.c:60
60 outb(0x08, port);
(gdb) bt
#0 0x8048667 in reset (port=2076) at eth.c:60
#1 0x8048a68 in main (argc=3, argv=0xbffffce4) at eth.c:184
(gdb) q
The program is running. Exit anyway? (y or n) y

None ioperm() vs iopl() issue

Re: More What version (Jochen Friedrich)
Date: 2000, Mar 31
From: David Hinds <dhinds@pcmcia.sourceforge.org>

ioperm() only works for ports below 0x400.  For higher ports, you need
to use iopl(3) instead.

-- Dave

Agree success!!!!!!!!

Re: None ioperm() vs iopl() issue (David Hinds)
Date: 2000, Apr 01
From: Matthew Austin yogi

Excellent!

Dave I removed the exclusion on the port range previously in
place (per trouble shooting section on this site) to try and
isolate the issue from a possible hardware conflict with another device.

-------------------------------------------------------------
From my original post . . .
-------------------------------------------------------------
"I have forced a change in io port and IRQ to see if that was
an issue as recommended by changing config.opts . . . no
change."
-------------------------------------------------------------
 
After removing those changes Jochen's binary now works, but I
imagine my own compile of his source would work now as well.

Thanks to you both.

-matthew

PS I was getting ready to purchase a 3com 3c575 off ebay as
cowboyneal reported that working flawlessly for him . . . ;-)

Question 410TXC and OpenBSD

Re: Question trouble with netgear FA410TXC (Matthew Austin)
Date: 2000, Mar 26
From: Morgan Neubauer Storm

I have this card, and am having the same trouble. I figure the program in #46 will fix the problem, but I'm running OpenBSD not Linux, and have been doing so for only a couple of days, so as you might imagine, my BSD experience is somewhat limited.

Any help in getting this bit of code to work under OpenBSD would be *greatly* appreciated.

thanx -
	=M=

Question Using regular kernel tulip driver with pcmcia-cs

Date: 2000, Mar 31
From: RichardA

Hello,

I'm trying to get my SMC CardBus card, which uses a DEC "tulip" chip, to work on my laptop.

I have already tried pcmcia-cs 3.1.13 with the 2.3.99-pre2 kernel and the tulip 0.91g-ppc driver from pcmcia-cs, i.e. the standalone PCMCIA support, for which I disabled PCMCIA in the kernel. Unfortunately, this version of the tulip code does not work with my card.

However, there is also the different version of the tulip code which comes with the kernel and is supposed to support "regular" PCI NICs as well as CardBus cards. I have compiled a 2.3.99-pre2 kernel and pcmcia-cs in attempt to use it for my card.

I enabled "hot-swappable" (yes), "PCMCIA" (module) and "CardBus" (yes) support in the kernel configuration as well as choosing the regular tulip DS2x14x driver in "network devices". pcmcia-cs did not compile any of its drivers, which is fine since I only need the kernel tulip driver.

Now, when I try to use the kernel PCMCIA code, it decides to exclude more memory ranges than the standalone version. This results in my card not being identified. Instead, it is listed as an "anonymous memory" card.

Here are kernel logs for the two cases. First, the way it looks when PCMCIA support in the kernel is disabled and the standalone pcmcia-cs is used:

Mar 24 21:07:37 elessar pcmcia: Starting PCMCIA services:
Mar 24 21:07:37 elessar pcmcia:  modules
Mar 24 21:07:37 elessar kernel: Linux PCMCIA Card Services 3.1.13
Mar 24 21:07:37 elessar kernel:   kernel build: 2.3.99-pre2 #8 Fri Mar 24 18:54:56 CET 2000
Mar 24 21:07:37 elessar kernel:   options:  [pci] [cardbus]
Mar 24 21:07:37 elessar kernel: Intel PCIC probe: PCI: Assigned IRQ 10 to device 00:03.1 [PIIX-NEW]
Mar 24 21:07:37 elessar kernel:
Mar 24 21:07:37 elessar kernel:   O2Micro OZ6836/OZ6860 PCI-to-CardBus at slot 00:03, mem 0x10000000
Mar 24 21:07:37 elessar kernel:     host opts [0]: [ring] [pci+isa] [pci irq 10] [lat 168/176] [bus
1/2]
Mar 24 21:07:37 elessar kernel:     host opts [1]: [ring] [pci+isa] [pci irq 10] [lat 168/176] [bus
3/4]
Mar 24 21:07:37 elessar kernel:     ISA irqs (default) = 3,4,5,7,9,12 PCI status changes
Mar 24 21:07:37 elessar pcmcia:  cardmgr.
Mar 24 21:07:37 elessar cardmgr[280]: starting, version is 3.1.13
Mar 24 21:07:37 elessar rc: Starting pcmcia succeeded
Mar 24 21:07:37 elessar cardmgr[280]: watching 2 sockets
Mar 24 21:07:37 elessar kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x1000-0x104f
Mar 24 21:07:37 elessar kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x100-0x107 0x200-0x207 0
x220-0x22f 0x300-0x307 0x378-0x37f 0x388-0x38f 0x398-0x39f 0x4d0-0x4d7
[snip]
Mar 24 21:08:36 elessar cardmgr[280]: initializing socket 0
Mar 24 21:08:36 elessar cardmgr[280]: socket 0: SMC EZ CardBus 10/100 PC Card
Mar 24 21:08:36 elessar kernel: cs: cb_alloc(bus 1): vendor 0x1011, device 0x0019
Mar 24 21:08:36 elessar kernel: ROM image dump:
Mar 24 21:08:36 elessar kernel:   image 0: 0x000000-0x0001ff, signature PCIR
Mar 24 21:08:36 elessar cardmgr[280]: executing: 'insmod /lib/modules/2.3.99-pre2/pcmcia/cb_enabler.
o'
Mar 24 21:08:36 elessar cardmgr[280]: executing: 'insmod /lib/modules/2.3.99-pre2/pcmcia/tulip_cb.o'
Mar 24 21:08:36 elessar kernel: cs: cb_config(bus 1)
Mar 24 21:08:36 elessar kernel:   fn 0 bar 1: io 0x400-0x47f
Mar 24 21:08:36 elessar kernel:   fn 0 bar 2: mem 0xa00c0000-0xa00c03ff
Mar 24 21:08:36 elessar kernel:   fn 0 rom: mem 0xa0080000-0xa00bffff
Mar 24 21:08:36 elessar kernel: cs: cb_enable(bus 1)
Mar 24 21:08:36 elessar kernel:   bridge io map 0 (flags 0x21): 0x400-0x47f
Mar 24 21:08:36 elessar kernel:   bridge mem map 0 (flags 0x1): 0xa0080000-0xa00c0fff
Mar 24 21:08:36 elessar kernel: tulip_reap()
Mar 24 21:08:36 elessar kernel: tulip_attach(bus 1, function 0)
Mar 24 21:08:36 elessar kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov (modified by
danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
Mar 24 21:08:36 elessar kernel: eth0: Digital DS21143 Tulip rev 65 at 0x400, 00:E0:29:55:E1:12, IRQ
10.
Mar 24 21:08:36 elessar kernel: eth0:  EEPROM default media type Autosense.
Mar 24 21:08:36 elessar kernel: eth0:  Index #0 - Media MII (#11) described by a 21142 MII PHY (3) b
lock.
Mar 24 21:08:36 elessar kernel: eth0:  MII transceiver #1 config 3000 status 7809 advertising 00a1.
Mar 24 21:08:36 elessar kernel: eth0:  Advertising 01e1 on PHY 1, previously advertising 00a1.
Mar 24 21:08:36 elessar kernel: eth0:  Advertising 01e1 (to advertise is 01e1).
Mar 24 21:08:36 elessar cardmgr[280]: executing: './network start eth0'
[ping local machine]
Mar 24 21:11:36 elessar kernel: spurious 8259A interrupt: IRQ7.

(various versions of the tulip driver have failed in weird & wonderful ways. The kernel one seems to be most actively developed ATM, which is why I want to try it. BTW, /proc/interrupts shows that IRQ 7 is indeed not used.)

For the second case, with PCMCIA support in the kernel, the following is logged:

Mar 24 22:20:56 elessar pcmcia: Starting PCMCIA services:
Mar 24 22:20:56 elessar pcmcia:  modules
Mar 24 22:20:56 elessar kernel: Linux PCMCIA Card Services 3.1.11
Mar 24 22:20:56 elessar kernel:   kernel build: 2.3.99-pre2 #1 Fri Mar 24 22:02:38 CET 2000
Mar 24 22:20:56 elessar kernel:   options:  [pci] [cardbus] [pm]
Mar 24 22:20:56 elessar kernel: Intel PCIC probe:
Mar 24 22:20:56 elessar kernel:   Intel i82365sl A step ISA-to-PCMCIA at port 0x3e0 ofs 0x00, 2 sock
ets
Mar 24 22:20:56 elessar kernel:     host opts [0]: none
Mar 24 22:20:56 elessar kernel:     host opts [1]: none
Mar 24 22:20:56 elessar kernel:     ISA irqs (scanned) = 3,4,5,7 polling interval = 1000 ms
Mar 24 22:20:56 elessar pcmcia:  cardmgr.
Mar 24 22:20:56 elessar rc: Starting pcmcia succeeded
Mar 24 22:20:56 elessar cardmgr[280]: starting, version is 3.1.11
Mar 24 22:20:57 elessar cardmgr[280]: watching 2 sockets
Mar 24 22:20:57 elessar kernel: cs: IO port probe 0x1000-0x17ff: clean.
Mar 24 22:20:57 elessar kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x100-0x107 0x200-0x207 0
x220-0x22f 0x300-0x307 0x378-0x37f 0x388-0x38f 0x398-0x39f 0x4d0-0x4d7
[snip]
Mar 24 22:21:55 elessar kernel: cs: memory probe 0x0d0000-0x0dffff: excluding 0xdc000-0xdffff
Mar 24 22:21:55 elessar kernel: cs: memory probe 0x0c0000-0x0cffff: excluding 0xc0000-0xcbfff
Mar 24 22:21:55 elessar cardmgr[280]: initializing socket 0
Mar 24 22:21:55 elessar cardmgr[280]: socket 0: Anonymous Memory
Mar 24 22:21:55 elessar cardmgr[280]: module /lib/modules/2.3.99-pre2/pcmcia/memory_cs.o not availab
le
Mar 24 22:21:56 elessar cardmgr[280]: get dev info on socket 0 failed: Resource temporarily unavaila
ble

AFAICT the memory ranges reported in the "memory probe" messages are not used by anything else!

Is the differing behaviour due to a difference between the pcmcia-cs 3.1.11 in the kernel and the 3.1.13 I used for the first case above? What can I do to fix the problem?

My /etc/pcmcia/config.opts for both cases was:

include port 0x100-0x4ff, port 0x1000-0x17ff
include memory 0xc0000-0xfffff, memory 0xa0000000-0xa0ffffff
exclude irq 4
exclude irq 7
card "SMC EZ CardBus 10/100 PC Card"
  manfid 0x01bf, 0x2220
  bind "tulip_cb"

When the above things failed, I tried to make the standalone pcmcia-cs load and use the kernel tulip driver. However, I don't really know how I am supposed to do this. I tried changing my /etc/pcmcia/config.opts file to load the normal tulip driver like this:

include port 0x100-0x4ff, port 0x1000-0x17ff
include memory 0xc0000-0xfffff, memory 0xa0000000-0xa0ffffff
exclude irq 4
exclude irq 7
device "tulip2_cb"
  class "network" module "cb_enabler", "net/tulip"                                                                               opts "tulip_debug=6"
card "SMC EZ CardBus 10/100 PC Card"
  manfid 0x01bf, 0x2220
  bind "tulip2_cb"

Not very surprisingly, this doesn't work; the kernel tulip driver just complains I/O ports (0x80@0x0) unavailable, aborting and refuses to load.

At this point I'm really stuck. I have been trying to get this card to work for four months now - any help would be very much appreciated!!

Thanks for reading this far,
Even more thanks for any help you can give,

  Richard

None Configuration on 2.3.*

Re: Question Using regular kernel tulip driver with pcmcia-cs
Date: 2000, Mar 31
From: David Hinds <dhinds@pcmcia.sourceforge.org>

When you build PCMCIA in the kernel in the 2.3.99 kernel, you should 
enable CardBus support, and disable the i82365 driver.  The i82365
driver was changed to only support ISA bus controllers.

As for the issue with the tulip driver in the standalone PCMCIA
package, I'm not sure what's going on there.  The tulip driver is kind
of a mess and I don't understand it; there are too many sort-of-tulip
cards around.

-- Dave

Question KingMax 10/100 Ethernet

Date: 2000, Apr 04
From: Ryan Marquis rmarquis

Any chance of getting this into the PCMCIA package? I did read above (November '99) that it probably wouldn't be included, but I was wondering if anyone was going to reconsider...

I notice they've done an update up to kernel v. 2.2.6. However, predictably, their stuff doesn't compile with pcmcia 3.1.8.

Thanks!

None Not in the immediate future

Re: Question KingMax 10/100 Ethernet (Ryan Marquis)
Date: 2000, Apr 04
From: David Hinds <dhinds@pcmcia.sourceforge.org>

It will probably wait unless/until I can figure out a non-horrible way
to merge the changes with the regular pcnet_cs driver.  The chipset
used in these cards has several significant deviations from normal
NE2000 compatible behavior.  The vendor's driver has a lot of other
changes, and was based on an old version of pcnet_cs, so it is not a
trivial merge.

-- Dave

Question Possible need for a FORWARDING="y/n" setting

Date: 2000, Apr 05
From: Dagmar d'Surreal Dagmar_dSurreal

Okay, I've got a set of wireless ethernet cards, and while frankly I would not recommend people doing this excepting in certain situations, I found a need last night for turning on ip_forwarding for the interface created by pcmcia-cs for them. This normally defaults to off (unless you turn on forwarding globally, in which case you should go stand in the corner now) but some people might have a genuine need to do this.

I know this probably seems like a minor thing, but I want to know if anyone else has any opinions on the subject of whether or not they think an IP_FORWARDING="y/n" option would be apropos for the /etc/pcmcia/network.opts file.

(For the record, I would not normally use forwarding blatantly across the interface. I'm working with Free S/WAN to get an encrypted connection authenticated by secret key which DOES have forwarding turned on)

None Another way to do it: use start_fn()

Re: Question Possible need for a FORWARDING="y/n" setting (Dagmar d'Surreal)
Date: 2000, Apr 05
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The start_fn() and stop_fn() parameters can be used to specify
additional actions to be taken after a network card is configured; you
could provide a start_fn() to turn on forwarding.  I think this might
be a sufficiently specialized application, that adding a new general
option might not be worth it: each new parameter is something else
that might confuse the majority of users who don't need it.

What is the command you use to enable forwarding?

-- Dave

Note Untitled

Re: None Another way to do it: use start_fn() (David Hinds)
Date: 2000, Apr 06
From: Dagmar d'Surreal Dagmar_dSurreal

Actually, it's fairly straightforward now compared to what it's been in the past for Linux. Forwarding of packets across interfaces is disabled by default, and to turn it on you have to do one of two things to files under /proc...

Either enable packet forwarding globally across all interfaces by stuffing a 1 into /proc/sys/net/ipv4/ip_forward (or /proc/sys/net/ipv4/conf/all/forwarding, changes made to either seem to affect both), in which case all NEW interfaces will have forwarding on by default (which is why this approach is non-optimal from a security standpoint), or...

Enable packet forwarding on an interface by interface basis by stuffing a 1 into /proc/sys/net/ipv4/conf/$IFNAME/forwarding. (Where $IFNAME is the name of the interface you wish to alter, for those who might be reading this but aren't so quick to spot implied shell substitutions)

I'll do some digging and exploring with start_fn() and stop_fn() over the weekend and see how well it works out, although for this, I don't think stop_fn() will have to be used, since the interfaces seem to go back to default settings when they are destroyed and recreated (but I haven't seen anything in documentation claiming that this is something intentional and unlikely to change, yet).

Question IBM ethernet card don't work

Date: 2000, Apr 07
From: borg1 borg1

 have a Acer travel mate 514t and a IBM credit card adapter ethernet adapter 2 pcmcia network card.
I installed the installed the pcmcia-cs 3.1.13 and i am using linux mandrake 7.0 with kernel 2.2.14.When i insert the card it finds it and beeps and the cardmgr tells me the name of the card so it must be able to see it.But the network card will not work i have configured the network and the laptop becomes slow when i insert the card.

 The error given in dmesg is

eth0: Tx timed out, cable problem? TSR=0x3, ISR=0x0, t=2000. eth0: pcnet_reset_8390() did not complete.
Hw. address read/write mismap 2
Hw. address read/write mismap 4
[root@laptop /]#

the card has two network fittings one a RJ 45 which i use and one bnc 10 base T
I hardly use the bnc one but do on the odd occasion some times.

And the led lights up when i insert the card and the access led blinks some times.

card ident

[root@laptop /]# cardctl ident
Socket 0:
  no product info available
Socket 1:
  product info: "IBM Corp.", "Ethernet", "0934214", "PC-NIC ENCC 990010759-001A" manfid: 0x00a4, 0x0002
  function: 6 (network)
[root@laptop /]#

dmesg

eth0: pcnet_reset_8390() did not complete.
eth0: NE2000 Compatible: io 0x300, irq 3, mem 0xc805c000, auto xcvr, hw_addr 00:04:AC:24:1E:24
Hw. address read/write mismap 2
Hw. address read/write mismap 4
[root@laptop /]#


the loptop runs slowley when the card is inserted and some times the hard disk will go insane and fill the screen up with the
Hw. address read/write mismap 2
Hw. address read/write mismap 4
and then stops when you take the card out but this onley happens then you have the card in slot 1

None Maybe a resource conflict

Re: Question IBM ethernet card don't work (borg1)
Date: 2000, Apr 07
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You might be seeing an IO port conflict.  I would try excluding ports
0x300-0x31f in /etc/pcmcia/config.opts.  You might also try bumping
the card off of irq 3 in case that is the problem.

If these things don't help, I'd want to see more system log messages,
particularly the startup messages from the i82365 driver.

-- Dave

Question SMC EZ CardBus 10/100 PC Card

Date: 2000, Apr 09
From: Andreas-Johann Ulvestad aj

I am currently using a pcmcia ethernet adapter, SMC EZ CardBus 10/100 PC Card is reported by cardmgr when booting or inserting the card. This is all well, but inserting "alias eth0 pcnet_cs" in /etc/conf.modules, I get "Delaying eth0 initialization" when ifup'ing eth0.

Is this the correct module to be using?

None Wrong driver; also, don't list PCMCIA drivers in conf.modules

Re: Question SMC EZ CardBus 10/100 PC Card (Andreas-Johann Ulvestad)
Date: 2000, Apr 10
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Don't put anything in /etc/conf.modules for PCMCIA devices.  It does
not do anything useful.

The SMC EZ CardBus card is listed in the SUPPORTED.CARDS file as using
the tulip_cb driver.  The right driver should be loaded automatically.
You should probably check your system log to see what's really going on.

-- Dave

More hmm....ok?

Re: None Wrong driver; also, don't list PCMCIA drivers in conf.modules (David Hinds)
Date: 2000, Apr 10
From: Andreas-Johann Ulvestad aj

I have removed the line from conf.modules, but pcmcia cardmgr doesn't load the tulip_cb module, and when modprobing it manually, it doesn't produce any error messages, but on the other hand, ifuping eth0 doesn't work either...and not sh -x /etc/pcmcia/network start eth0 either:
Delaying eth0 initialization.

None Check your system log

Re: More hmm....ok? (Andreas-Johann Ulvestad)
Date: 2000, Apr 10
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You need to consult your system log.  Every action that the PCMCIA
system takes is recorded there.  Trying to modprobe PCMCIA modules by
hand is never productive.  If the PCMCIA subsystem could configure
your card, then the right driver is loaded for you; if the card could
not be configured, then loading the driver won't help.

I guess I should also point out that the supported cards file says
that for the SMC EZ CardBus cards, "some do not work".  There is
some sort of driver incompatibility with some version(s) of the card
(I can't be more specific because I don't have any of these cards).  I
can't tell if your card is affected or not, since so far, the card
doesn't seem to be set up to the point of loading the right driver.

-- Dave

Angry Intel EtherExpress PRO/100 Mobile, model MBLA3200

Date: 2000, Apr 09
From: Jim Perry aziwoqpd

Heya... I was trying to get Linux installed on my laptop
today, and I couldn't get the bloody PCMCIA ethernet driver
to work.  I tried shoving it onto different IRQs and different
ports, but I kept getting the same error.  Anyway, I'm using Linux-2.2.13, the latest pcmcia (pcmcia-cs-3.1.13 i think?).
Here's the logs:

Apr  9 15:57:35 slackware kernel: Linux PCMCIA Card Services 3.1.13 
Apr  9 15:57:35 slackware kernel:   kernel build: 2.2.13 #1 SMP Sun Apr 9 14:10:46 PDT 2000 
Apr  9 15:57:35 slackware kernel:   options:  [pci] [cardbus] [pnp] 
Apr  9 15:57:35 slackware kernel: PCI routing table version 1.0 at 0xf6980 
Apr  9 15:57:35 slackware kernel: PnP: PNP BIOS installation structure at 0xc00fdab0 
Apr  9 15:57:35 slackware kernel: PnP: PNP BIOS version 1.0, entry at f0000:4b88, dseg at f0000 
Apr  9 15:57:46 slackware kernel: Intel PCIC probe:  
Apr  9 15:57:46 slackware kernel:   Ricoh RL5C465 PCI-to-CardBus at slot 00:13, mem 0xfedff000 
Apr  9 15:57:46 slackware kernel:     host opts [0]: [io 4/6/2] [mem 4/6/2] [pci irq 9] [lat 64/176] [bus 1/1] 
Apr  9 15:57:46 slackware kernel:     PCI irq 9 test failed 
Apr  9 15:57:46 slackware kernel:     ISA irqs (default) = 10,11,15 polling interval = 1000 ms 
Apr  9 15:57:56 slackware cardmgr[255]: starting, version is 3.1.13
Apr  9 15:57:56 slackware kernel: cs: IO port probe 0x1000-0x17ff: clean. 
Apr  9 15:57:56 slackware cardmgr[255]: watching 1 sockets
Apr  9 15:58:05 slackware kernel: cs: cb_alloc(bus 1): vendor 0x1011, device 0x0019 
Apr  9 15:58:05 slackware kernel: ROM image dump: 
Apr  9 15:58:05 slackware kernel:   image 0: 0x000000-0x0001ff, signature PCIR 
Apr  9 15:58:05 slackware kernel: cs: cb_config(bus 1) 
Apr  9 15:58:05 slackware kernel:   fn 0 bar 1: io 0x1000-0x107f 
Apr  9 15:58:05 slackware kernel:   fn 0 bar 2: mem 0x600c0000-0x600c007f 
Apr  9 15:58:05 slackware kernel:   fn 0 rom: mem 0x60080000-0x600bffff 
Apr  9 15:58:05 slackware kernel: cs: cb_enable(bus 1) 
Apr  9 15:58:05 slackware kernel:   bridge io map 0 (flags 0x21): 0x1000-0x107f 
Apr  9 15:58:05 slackware kernel:   bridge mem map 0 (flags 0x1): 0x60080000-0x600c0fff 
Apr  9 15:58:05 slackware kernel: tulip_reap() 
Apr  9 15:58:05 slackware kernel: tulip_attach(bus 1, function 0) 
Apr  9 15:58:05 slackware kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford) 
Apr  9 15:58:05 slackware kernel: eth0: Digital DS21143 Tulip rev 48 at 0x1000, EEPROM not present, 00:4C:69:6E:75:79, IRQ 11. 
Apr  9 15:58:05 slackware cardmgr[255]: initializing socket 0
Apr  9 15:58:05 slackware cardmgr[255]: socket 0: Intel EtherExpress PRO/100 CardBus Mobile Adapter32
Apr  9 15:58:05 slackware cardmgr[255]: executing: 'insmod /lib/modules/2.2.13/pcmcia/cb_enabler.o'
Apr  9 15:58:05 slackware cardmgr[255]: executing: 'insmod /lib/modules/2.2.13/pcmcia/tulip_cb.o'
Apr  9 15:58:05 slackware cardmgr[255]: executing: './network start eth0'
Apr  9 15:58:50 slackware kernel: eth0: Tx hung, 9 vs. 0. 
Apr  9 15:58:50 slackware kernel: eth0: 21140 transmit timed out, status f0678006, SIA 000000c6 ffff0001 fffbff7f 8ff04008, resetting... 
Apr  9 15:58:56 slackware kernel: eth0: Tx hung, 9 vs. 0. 
Apr  9 15:58:56 slackware kernel: eth0: 21140 transmit timed out, status f0678106, SIA 000000c6 ffff0000 fffbff7f 8ff04008, resetting... 
Apr  9 15:59:02 slackware kernel: eth0: Tx hung, 9 vs. 0. 
Apr  9 15:59:02 slackware kernel: eth0: 21140 transmit timed out, status f0678106, SIA 000000c6 ffff0000 fffbff7f 8ff04008, resetting... 
Apr  9 15:59:08 slackware kernel: eth0: Tx hung, 9 vs. 0. 
Apr  9 15:59:08 slackware kernel: eth0: 21140 transmit timed out, status f0678106, SIA 000000c6 ffff0000 fffbff7f 8ff04008, resetting... 
Apr  9 15:59:14 slackware kernel: eth0: Tx hung, 9 vs. 0. 
Apr  9 15:59:14 slackware kernel: eth0: 21140 transmit timed out, status f0678106, SIA 000000c6 ffff0000 fffbff7f 8ff04008, resetting... 
(i get mad and take the card out)
Apr  9 15:59:15 slackware kernel: tulip_detach(eth0) 
Apr  9 15:59:15 slackware kernel: cs: cb_disable(bus 1) 
Apr  9 15:59:15 slackware kernel: cs: cb_release(bus 1) 
Apr  9 15:59:15 slackware kernel: cs: cb_free(bus 1) 
Apr  9 15:59:15 slackware kernel: tulip_reap() 
Apr  9 15:59:15 slackware cardmgr[255]: shutting down socket 0

Also, I tried running tulip-diag while it was sitting there 
printing out those "hung" statements.  This is what I got:
tulip-diag.c:v1.19 10/2/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Index #1: Found a Digital DS21143 Tulip adapter at 0x1000.
 Port selection is 10mpbs-serial, full-duplex.
 Transmit stopped, Receive stopped, full-duplex.
  The Rx process state is 'Stopped'.
  The Tx process state is 'Stopped'.
  The transmit threshold is 72.
 Interrupt sources are pending!  CSR5 is f0018106.
   Tx complete indication.
   Tx out of buffers indication.
   Receiver stopped indication.
  The NWay status register is 000000c6.
EEPROM size is 6.
 A simplifed EEPROM data table was found.
 The EEPROM does not contain transceiver control information.
EEPROM contents:
  8086 0001 0087 0000 0000 0000 0000 0000
  00c4 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 4448
 ID block CRC 0xc4 (vs. 0xc4).
  Full contents CRC 0x4448 (read as 0x4448).
You have an Intel CardBus card with an incomplete EEPROM.
The station address is 00:a0:c9:7a:d8:a5
New EEPROM contents would be:
  8086 0001 0087 0000 0000 0000 0000 0000
  00c4 0103 a000 7ac9 a5d8 1e00 0000 0800
  8604 0002 08af 00a5 0286 af04 a508 8800
  0304 08af 00a5 8061 0488 af05 a508 6100
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 4448
 ID CRC 0xc4 (vs. 0xc4), complete CRC 4448.
  Internal autonegotiation state is 'Autonegotiation disabled'.

Any ideas?  I heard something about reflashing the EEPROM,
but I didn't do that for two reasons.. Mainly, it sounds
dangerous, and the more important, I don't know how.
Oh, and incidentially, I'm on a 100baseT network, not a
10baseT network.  Tried doing an "ifport eth0 100baseT", but
I just got an ioctl not allowed error.  "ifport eth0" by itself claims
that the adapter is on "auto" mode.

Thanks,
-jim

Ok EtherExpress fixed!

Re: Angry Intel EtherExpress PRO/100 Mobile, model MBLA3200 (Jim Perry)
Date: 2000, Apr 15
From: Jim Perry aziwoqpd

I got the card working.  If anyone else is having the same
problem, here's what I did:

1) I used tulip-diag to rewrite the card's EEPROM 
(tulip-diag -w), twice.  This might not have actually been
necessary, though.

2) It still didn't work, so I tried forcing the card's 
media type (add this to config.opts:)
module "tulip_cb" opts "options=3"
(for 100baseTx half-duplex, anyway).

3) And it worked!

-jim

Agree That fixes my card too. But the EEPROM rewrite seems essential.

Re: Ok EtherExpress fixed! (Jim Perry)
Date: 2000, May 24
From: Kurt Atkinson kjwa

I've been having exactly the same problem with the same card and have found that this soloution works for me. However, I can report that a rewrite of the EEPROM was needed. For anyone worried about the doing an EEPROM rewrite I can say that I dual boot my system into WIN95 and the network card still works!

Thanks Jim.

kURT <<()>>

Question DHCP and manually set MAC address

Date: 2000, Apr 12
From: Andreas Hotz ahotz

To use my laptop on the company network, I have to use DHCP. No problem so far. But I have to use DHCP with a manually configured MAC address. Don't ask me why this is so, it just is that way. The DHCP server won't answer me with thy MAC address burned into the adapter.

I could not find a suitable variable in the PCMCIA config scripts. I think I have to tweak a little with ifconfig. Maybe in the start_fn function in network.opts? Or should I change config instead. Any tips which is the best way to do it?

None There has got to be another way

Re: Question DHCP and manually set MAC address (Andreas Hotz)
Date: 2000, Apr 12
From: David Hinds <dhinds@pcmcia.sourceforge.org>

That's totally brain dead.  You need to talk to your IT people and
give them your card's MAC address if necessary, so that they can
configure the DHCP server to recognize it.

Most cards do not permit overriding the MAC address.  And almost none
of the Linux net drivers provide an interface for doing it.

-- Dave

More I agree, however...

Re: None There has got to be another way (David Hinds)
Date: 2000, Apr 13
From: Andreas Hotz ahotz

That's what I said to them: It's braindead. But they won't listen. Talking something about we have to have addresses bound to a workstation (tied to a certain desk in a certain office, not an adapter). Up to some point (but not completely) I can understand what their problem is. Besides TCP/IP, they use SNA network functions and other services bound only to the MAC address. If an adapter is interchanged with another (could easily happen with PCMCIA cards) no address (TCP/IP or other) should change with the card. Additionally, their sniffers and network managing software has a direct link from the mac address to the office and working plance. Resumee: I tried to convince them of using the burnt-in mac address, but they did not accept. So I'm back with the problem

> Most cards do not permit overriding the MAC address.

Really? Under Windoze (NT, 95) and OS/2 all brands of our Ethernet adapters (Compaq Netelligent, Xircom, 3Com), both PCI and PCMCIA do not have problems with an overwritten mac address, and neither do the Token Ring cards.

> And almost none of the Linux net drivers provide an
> interface for doing it.

The ifconfig program in Linux does provide a parameter for this purpose, and if I use it:
./network stop eth0
ifconfig eth0 hw ether <address>
./network strat eth0
Then ifconfig --status shows the new address afterwards, and a ping to the adapter from another machine still delivers an answer. I could not manage it yet to use a sniffer to find out whether ifconfig just "lies" to me and in fact the adapter still uses the burnt-in mac address.

So if the whole thing does not really work in linux, then I'm stuck. But if it works, I'd like to know the excact point in the scripts where I should insert a hack. I could immagine thing should happen between "insmod" and "./network start eth0", before the dhcp call is made. But I'm quite new to linux and am not sure whether I am right.

Can you give me a hint? Of course I'll keep you posted with the results.

Andreas

None Ok, maybe I don't know what I'm talking about

Re: More I agree, however... (Andreas Hotz)
Date: 2000, Apr 13
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I have never tried using this ifconfig interface. You are welcome to try it. Just edit /etc/pcmcia/network and add your ifconfig command before the interface is set up.

-- Dave

Ok It works!

Re: Question DHCP and manually set MAC address (Andreas Hotz)
Date: 2000, Apr 17
From: Andreas Hotz ahotz

The change of the adapter to a preset hardware address with ifconfig prior to calling DHCP works great for me. I tested it with a Compaq Netelligent Ethernet and an IBM Auto Token Ring adapter. My version of DHCP does not seem to work for Token Ring, but that's another story and does not have anything to do with the address change.

I tweaked David's network script (many thanks to David for discussing the stuff and giving hints) a little and added a new variable NEW_HWADDR to network.config and here we are. If network.opts sets this variable, the network script will try to change the adapters address to NEW_HWADDR. The version of David's scrip is: # network 1.63 2000/02/09 03:12:42 (David Hinds)

And here are the changes I made (this is an excerpt, showing only the changes I made to the "start" part of "case $ACTION in"):

>'start')
>
>    test "$IF_PORT" && /sbin/ifport $DEVICE $IF_PORT
>
>    cp $RESOLV $RESOLV.pcmcia.save
>
># Begin adddition by Andreas Hotz
>    if  [ "$NEW_HWADDR" ] ; then
>       case "$DEVICE" in
>       eth*)
>            IFDEVICE="ether"
>            ;;
>       tr*)
>    	    IFDEVICE="tr"
>    	    ;;
>       *)
>    	    logger "Device not recognized. Adress will not be overwritten"
>    	    IFDEVICE=""
>    	    ;;
>       esac
>       if [ "$IFDEVICE" ] ; then
>          logger "New device address will be set to" $NEW_HWADDR
>          /sbin/ifconfig $DEVICE hw $IFDEVICE $NEW_HWADDR
>       fi
>    fi
># End adddition by Andreas Hotz
>

The logger entries are for showing me anything that may go wrong. I have only Token Ring and Ethernet devices available, so I could not test whether the address change would work for other device types lile Arcnet. So I don't deal with other devices and give a "device not recognized" message back.

Could anybody else test whether this stuff works for him/her? And I think one could do the scripting better. I'm new to shell scripts and not an old linux/unix hacker (coming from OS/2 and REXX). So please feel free to make things better.

Andreas

Sad Toshiba+TDK Ethernet+SuSe -> SIOCSIFADRR unknown device

Date: 2000, Apr 12
From: Alexei Gorbatov alexx

I am trying to connect TDK DFL 3410/12 Ethernet/Modem card on the Toshiba Tecra 8000 using SuSe Linux 6.3 The system recognizes ethernet card and load driver succesfully. However, at the moment of mounting ethernet it gives messages: SIOCSIFADRR unknown device.............fault eth0 unknown device....................fault etc. I exclude irqs 3,5, and 9 from ./pcmcia/config.opts Unfortunately it does not resolve the problem. Please, help!!!!

None System log messages, please?

Re: Sad Toshiba+TDK Ethernet+SuSe -> SIOCSIFADRR unknown device (Alexei Gorbatov)
Date: 2000, Apr 12
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I don't think it could have loaded the driver successfully.  System
log messages would be helpful.

-- Dave

Sad log message

Re: None System log messages, please? (David Hinds)
Date: 2000, Apr 13
From: Alexei Gorbatov alexx

socket 1: TDK Global Networker Ethernet/Modem
executing: 'insmod /lib/modules/2.2.13/pcmcia/serial_cs.o'
executing: './serial start ttyS1'
mounting eth0 unknown interface; No such device SIOCSIFADDR: No such device eth0 unknown interface; No such device

well, I filled all addresses and exclude irqs 3,4,5,7,9,10 as was pointed in the notes. The sound is high when the card is mounting but fails for internet. Any idea????

None Unsupported card

Re: Sad Toshiba+TDK Ethernet+SuSe -> SIOCSIFADRR unknown device (Alexei Gorbatov)
Date: 2000, Apr 13
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The TDK 3410 is not on the supported cards list. I don't know how to support the ethernet function, and no driver was loaded for it: only the modem driver was loaded.

-- Dave

More Xircom

Re: None Unsupported card (David Hinds)
Date: 2000, Apr 14
From: Alexei Gorbatov alexx

What about Xircom Credit Card CE2??? It does not work anyway. There is no any error message and everything is mounted well. It just does not work....

Question kernel: eth0: transmit timed out, tx_status 00 status e000.

Date: 2000, Apr 11
From: Bernard BARBIER BernardJB

hello,

Could some body tell me what's wrong ? My network interface works well 
during 3 or 4 minutes and then stops, and restart...

in order : 
- error messages : 

kernel: eth0: transmit timed out, tx_status 00 status e000.
kernel: eth0: Tx Ring full, refusing to send buffer. 
cardmgr[334]: + ioctl: Operation not supported

- pcmcia-cs-3.1.13
- kernel : linux-2.2.5  (redhat)
- laptop : Dell inspiron 7500
- files :
/etc/sysconfig/pcmcia
/proc/interrupt
/var/log/messages

Any help would be grately appreciated ! 

From France, BERNARD!

---


/etc/sysconfig/pcmcia
PCMCIA=yes
PCIC=i82365
PCIC_OPTS="do_scan=0 irq_list=3,5"
CORE_OPTS=

 /proc/interrupts 
           CPU0       
  0:     328922          XT-PIC  timer
  1:       2815          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  3:     606111          XT-PIC  eth0
  8:          2          XT-PIC  rtc
 12:     111621          XT-PIC  PS/2 Mouse
 13:          1          XT-PIC  fpu
 14:     619092          XT-PIC  ide0
 15:          5          XT-PIC  ide1
NMI:          0


here is my last boot /var/log/messages

pcmcia: Starting PCMCIA services:
pcmcia:  modules
kernel: Linux PCMCIA Card Services 3.1.13 
kernel:   kernel build: 2.2.5-15 #1 Mon Apr 19 23:00:46 EDT 1999 
kernel:   options:  [pci] [cardbus] [apm] 
kernel: PCI routing table version 1.0 at 0xfdf50 
kernel:   00:04.0 -> irq 11 
kernel:   00:04.1 -> irq 11 
kernel: Intel PCIC probe:  
TI 1225 PCI-to-CardBus at slot 00:04, mem 0x68000000 
kernel:     host opts [0]: [ring] [serial pci & irq] [pci irq 11] [lat 168/32] [bus 32/34] 
kernel:     host opts [1]: [ring] [serial pci & irq] [pci irq 11] [lat 168/32] [bus 35/37] 
kernel:     PCI irq 11 seems to be wedged! 
kernel:     PCI irq 11 test failed 
kernel:     ISA irqs (default) = 3 polling interval = 1000 ms 
pcmcia:  cardmgr.
rc: Starting pcmcia succeeded
cardmgr[334]: starting, version is 3.1.13
cardmgr[334]: watching 2 sockets
kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x1000-0x1087 0x1400-0x14ff 
kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x4d0-0x4d7 
kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
inet: inetd startup succeeded
kernel: cs: cb_alloc(bus 32): vendor 0x10b7, device 0x5257 
cardmgr[334]: initializing socket 0
cardmgr[334]: socket 0: 3Com 3CCFE575CT/3CXFE575CT Fast EtherLink XL
cardmgr[334]: executing: 'insmod /lib/modules/2.2.5-15/pcmcia/cb_enabler.o'
cardmgr[334]: executing: 'insmod /lib/modules/2.2.5-15/pcmcia/3c575_cb.o'
kernel: 3c59x.c:v0.99L 5/28/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html 
kernel: cs: cb_config(bus 32) 
kernel:   fn 0 bar 1: io 0x200-0x27f 
kernel:   fn 0 bar 2: mem 0xa0021000-0xa002107f 
kernel:   fn 0 bar 3: mem 0xa0020000-0xa002007f 
kernel:   fn 0 rom: mem 0xa0000000-0xa001ffff 
kernel: vortex_attach(bus 32, function 0, device 5257) 
kernel: eth0: 3Com 3CCFE575CT Cyclone CardBus at 0x200,  00:50:da:55:27:2d, IRQ 3 
kernel: eth0: CardBus functions mapped a0020000->c8849000 
kernel:   8K byte-wide RAM 5:3 Rx:Tx split, MII interface. 
kernel:   MII transceiver found at address 0, status 7809. 
kernel:   Enabling bus-master transmits and whole-frame receives. 
cardmgr[334]: executing: './network start eth0'
lpd: lpd startup succeeded
keytable: Loading keymap: 
cardmgr[334]: + ioctl: Operation not supported

Sad eth0:interrupt(s) dropped!

Date: 2000, Mar 31
From: Ray jxray

/etc/sysconfig/pcmcia PCMCIA=yes PCIC=i82365 PCIC_OPTS="do_scan=0" #this dose not work for me. CORE_OPTS=

#cardctl ident
Socket 0:
  product info: "PCMCIA", "100BASE"
  manfid: 0xffff, 0x1090
  function: 6 (network)
Socket 1:
  no product info available

no other devices was using the irq my card was using. i tried all irqs which can be used, but get the same massage.

i think pcmcia-cs-3.1.13 can not support my poor card...

this card works perfectly in windoz using 0x320 irq 10

can any body help? thanX.

None So give us a hint: what brand and model of card is this?

Re: Sad eth0:interrupt(s) dropped! (Ray)
Date: 2000, Mar 31
From: David Hinds <dhinds@pcmcia.sourceforge.org>

System log messages are also helpful, especially the startup messages
from the PCMCIA drivers.  And what kind of laptop is this?  And how
did you modify the /etc/pcmcia/config file, exactly?

-- Dave

Feedback laplop manufactured in China. & my config files

Re: None So give us a hint: what brand and model of card is this? (David Hinds)
Date: 2000, Apr 01
From: Ray jxray

thanx for your quick reply!!

/etc/pcmcia/config:
...
card "LN1078"
  manfid 0xffff, 0x1090
  bind "pcnet_cs"
...
/etc/pcmcia/config.opts
...
module "pcnet_cs" opts "hw_addr=0x00,0x00,0x21,0x0e,0x--,0x--"
...
#dmesg    //after a /etc/rc.d/init.d/pcmcia restart & command "route" was executed
unloading PCMCIA Card Services
Linux PCMCIA Card Services 3.1.13
  kernel build: 2.2.12-20 #1 Mon Sep 27 10:40:35 EDT 1999
  options:  [pci] [cardbus] [apm]
PCI routing table version 1.0 at 0xfdf70
Intel PCIC probe: 
  TI 1225 PCI-to-CardBus at slot 00:04, mem 0x68000000
    host opts [0]: [ring] [serial pci & irq] [pci irq 11] [lat 64/176] [bus 32/34]
    host opts [1]: [ring] [serial pci & irq] [pci irq 11] [lat 64/176] [bus 35/37]
    PCI irq 11 seems to be wedged!
    PCI irq 11 test failed
    ISA irqs (default) = 3,4,5,7,9,10 polling interval = 1000 ms
cs: IO port probe 0x1000-0x17ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: clean.
eth0: NE2000 Compatible: io 0x300, irq 3, hw_addr 00:00:21:0E:--:--  //sorry for hide this.
eth0: interrupt from stopped card
eth0: interrupt(s) dropped!
eth0: Reentering the interrupt handler! isr=0x0 imr=0x0.
eth0: Reentering the interrupt handler! isr=0x0 imr=0x0.

can these messages help?
i compiled & installed pcmcia-cs-3.1.13 using default options.

PS:
this poor card is called ln1078. 
Based on IEEE 802.30Base-T,IEEE 802.3u 100Base-TX
ioport 0x240-0x360
irq 2,3,4,5,10,11,12,15
data cache buffer 64k
it can work at 10M/100M duplex mode.
info can be get at http://www.legend.com.cn but it is build in chinese language. :(

many laptop users in china use this card like me. diff is they use windoz i use linux. :)

None I'm afraid you are out of luck for now

Re: Feedback laplop manufactured in China. & my config files (Ray)
Date: 2000, Apr 03
From: David Hinds <dhinds@pcmcia.sourceforge.org>

This card is based on an NE2000 clone chip that has some serious bugs
that prevent it from working with the regular pcnet_cs driver.  I have
a similar card and hope to fix this eventually, but I don't know when
it will be done.

-- Dave

Ok I'll be waiting for your new drivers...:)

Re: None I'm afraid you are out of luck for now (David Hinds)
Date: 2000, Apr 04
From: Ray jxray

Thanx anyway. I learned more during configuring this poor card.

Question Problem with IBM 10/100 Etherjet Cardbus Adapter

Date: 2000, Apr 18
From: Torsten Tittmann tti

I use a Thinkpad 385XD with an IBM 10/100 Etherjet Cardbus Adapter and
an IBM International Modem with GSM PC Card.

The installation is an SuSE 6.4 (Kernel 2.2.14 with APM Support)
with cardctl 3.1.11.

It looks all fine during bootup and card detecting, but any access to the LAN fail.
I connected directly to our switch and the switch receive frames.
The LEDs of the cableadapter blinks too.
But there is no response to ping, traceroute, ...

After adding "debug=255" to the tulip_cs module I get the following messages.

/var/log/messages:
Apr 18 13:43:12 laptop-tti kernel: Linux PCMCIA Card Services 3.1.11
Apr 18 13:43:12 laptop-tti kernel:   kernel build: 2.2.14 #1 Sat Mar 25 00:46:59 
GMT 2000
Apr 18 13:43:12 laptop-tti kernel:   options:  [pci] [cardbus] [apm]
Apr 18 13:43:12 laptop-tti kernel: PCI routing table version 1.0 at 0xfb150
Apr 18 13:43:12 laptop-tti kernel:   00:02.0 -> irq 11
Apr 18 13:43:12 laptop-tti kernel:   00:02.1 -> irq 11
Apr 18 13:43:12 laptop-tti kernel: Intel PCIC probe: 
Apr 18 13:43:12 laptop-tti kernel:   TI 1250A PCI-to-CardBus at slot 00:02, mem 
0x50000000
Apr 18 13:43:12 laptop-tti kernel:     host opts [0]: [ring] [isa irq] [pci irq 
11] [lat 168/176] [bus 1/3]
Apr 18 13:43:12 laptop-tti kernel:     host opts [1]: [ring] [isa irq] [pci irq 
11] [lat 168/176] [bus 4/6]
Apr 18 13:43:12 laptop-tti kernel:     ISA irqs (scanned) = 3,4,7,9,10,15 PCI 
status changes
Apr 18 13:43:12 laptop-tti kernel: cs: IO port probe 0x0c00-0x0cff: excluding 
0xcf8-0xcff
Apr 18 13:43:12 laptop-tti kernel: cs: IO port probe 0x0800-0x08ff: clean.
Apr 18 13:43:12 laptop-tti kernel: cs: IO port probe 0x0100-0x04ff: excluding 
0x200-0x207 0x220-0x22f 0x388-0x38f 0x3b8-0x3df 0x4d0-0x4d7
Apr 18 13:43:12 laptop-tti kernel: cs: cb_alloc(bus 4): vendor 0x115d, device 
0x0003
Apr 18 13:43:12 laptop-tti kernel: ROM image dump:
Apr 18 13:43:12 laptop-tti kernel:   image 0: 0x000000-0xffffffff, signature 
PCIR
Apr 18 13:43:12 laptop-tti kernel: cs: cb_config(bus 4)
Apr 18 13:43:12 laptop-tti kernel:   fn 0 bar 1: io 0x100-0x17f
Apr 18 13:43:12 laptop-tti kernel:   fn 0 bar 2: mem 0x6000d000-0x6000d7ff
Apr 18 13:43:12 laptop-tti kernel:   fn 0 bar 3: mem 0x6000c000-0x6000c7ff
Apr 18 13:43:12 laptop-tti kernel:   fn 0 rom: mem 0x60008000-0x6000bfff
Apr 18 13:43:12 laptop-tti kernel: cs: cb_enable(bus 4)
Apr 18 13:43:12 laptop-tti kernel:   bridge io map 0 (flags 0x21): 0x100-0x17f
Apr 18 13:43:12 laptop-tti kernel:   bridge mem map 0 (flags 0x1): 0x60008000-
0x6000dfff
Apr 18 13:43:12 laptop-tti kernel: tulip_reap()
Apr 18 13:43:12 laptop-tti kernel: tulip_attach(bus 4, function 0)
Apr 18 13:43:12 laptop-tti kernel: tulip.c:v0.91g-ppc 7/16/99 
becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM 
CBE, fixed by Doug Ledford)
Apr 18 13:43:12 laptop-tti kernel: eth0: Xircom Cardbus Adapter (DEC 21143 
compatible mode) rev 3 at 0x100, 00:04:AC:90:DD:73, IRQ 11.
Apr 18 13:43:12 laptop-tti kernel: eth0:  MII transceiver #0 config 3100 status 
7809 advertising 01e1.
Apr 18 13:43:12 laptop-tti kernel: eth0: tulip_open() irq 11.
Apr 18 13:43:12 laptop-tti kernel: eth0: interrupt  csr5=0x60678006 new 
csr5=0x60660000.
Apr 18 13:43:12 laptop-tti kernel: eth0: The transmitter stopped.  CSR5 is 
60678006, CSR6 324c2002, new CSR6 32400000.
Apr 18 13:43:12 laptop-tti kernel: eth0: interrupt  csr5=0x60670004 new 
csr5=0x60660000.
Apr 18 13:43:12 laptop-tti kernel: eth0: interrupt  csr5=0x60660000 new 
csr5=0x60660000.
Apr 18 13:43:12 laptop-tti kernel: eth0: exiting interrupt, csr5=0x60660000.
Apr 18 13:43:12 laptop-tti kernel: eth0: Done tulip_open(), CSR0 fea08000, CSR5 
60660000 CSR6 324c2002.
Apr 18 13:43:12 laptop-tti kernel: eth0: interrupt  csr5=0x60670004 new 
csr5=0x60660000.
...

/var/log/warn:
Apr 18 13:43:12 laptop-tti kernel: eth0: The transmitter stopped.  CSR5 is 
60678006, CSR6 324c2002, new CSR6 32400000.



can somebody help me?

Thanks a lot
                Torsten

Question Problem with IBM token ring driver and 3c389

Date: 2000, Apr 18
From: Rogan Dawes rdawes

Hi

I am trying to get a 3Com 3c389 Tokenlink Velocity Card working with Linux 2.2.14. I have downloaded the 3.1.8 PCMCIA software, but have detected a problem:

My NT installation detects memory used at 0xd4000 and 0xd0000, and shows this as allocated to the token ring driver, but Linux seems to be trying to use other fairly arbitrary addresses (e.g. 0xc....)

I tried hard coding the memory ranges into the driver, to verify where the problem was, and the driver installed and worked like a champ.

I also tried passing the parameters to the module using /etc/modules.conf, but this did not seem to get the values into the driver ( perhaps the cardmgr was passing its own parameters?)

The laptop is a Dell Latitude CPiA300.

What follows is an abridged NT diags dump, as well as the dump_cis output.

Does anyone have any suggestions for me?

Drivers Report
----------------------------------------------------------------------
IBM Token Ring Adapter (ISA/PCMCIA) Driver (NDIS) Running   (Automatic)
   C:\WINNT\System32\drivers\ibmtoks.sys
   Error Severity: Normal
   Service Flags: Kernel Driver, Shared Process
IRQ and Port Report
----------------------------------------------------------------------
Devices                       Vector Level  Affinity
----------------------------------------------------------------------
IbmTok                            10    10 0x00000000
----------------------------------------------------------------------
Devices                       Physical Address  Length
----------------------------------------------------------------------
IbmTok                          0x00000a20  0x0000000004

DMA and Memory Report Devices Physical Address Length ---------------------------------------------------------------------- IbmTok 0x000d4000 0x00002000 IbmTok 0x000d0000 0x00004000 Pcmcia 0x08000000 0x00002000

Here is the dump_cis:
Socket 0:
  no CIS present

Socket 1:
  dev_info
    ROM 250ns, 8kb
    fn_specific 250ns, 64kb
  vers_1 4.1, "3Com", "TokenLink Velocity PC Card", "85H3636",
    "B3ENIPSKJRT"
  config base 0x0800 mask 0x000b last_index 0x23
  cftable_entry 0x20 [default]
    [mwait]
    Vcc Vnom 5V Iavg 300mA
    timing wait 1us
    io 0x0000-0x0003 [lines=2] [8bit]
    irq mask 0xffff [level]
    memory 0x0000-0x1fff @ 0x0000
  cftable_entry 0x21
    memory 0x400000-0x6010ff @ 0x0000
  cftable_entry 0x22
    memory 0x800000-0xa010ff @ 0x0000
  cftable_entry 0x23
    memory 0x0000-0x2010ff @ 0x0000
  manfid 0x00a4, 0x001e
  funcid network_adapter [post] [rom]
  lan_technology token_ring
  lan_speed 16 mb/sec
  lan_speed 4 mb/sec
  lan_media unshielded_twisted_pair
  lan_media shielded_twisted_pair
  lan_node_id 95 67 fb 24 a0 00
  checksum 0x0000-0x00af = 0x75

Another thing that I find funny, is that I cannot get useful information out of tcpdump. I have got a version of tcpdump 3.3 modified to support Token Ring, but all it ever shows me is broadcast traffic. It never even shows me my own traffic! Weird! Suggestions?

Thanks a lot!

Rogan

None See /etc/pcmcia/config.opts

Re: Question Problem with IBM token ring driver and 3c389 (Rogan Dawes)
Date: 2000, Apr 18
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Don't use /etc/modules.conf.  Look at /etc/pcmcia/config.opts and
there is an example for setting the token ring addresses.

-- Dave

None Problem with Fiberline PCM-FE1500 Fast Ethernet card

Date: 2000, Apr 22
From: digithi

Hi, I've bought a Fiberline PCM-FE1500 16Bit PCMCIA Fast Ethernet Card; I have pcmcia_cs 3.1.14 and kernel 2.2.14, The module pcnet_cs loads correctly: "eth0: NE2000 Compatible: io 0x300, irq 4, hw_addr 00:E0:...."

my Problem: The performance of this card under linux is really low: I reach 300kb/s in a switched 100MBit network und only 60kb/s in a 10MBit network ! The cable is ok and ifconfig doesn't show any problems or errors. With windows, I reach in a 10Mbit and 100MBit network 700kb/s.

can anyone help me with my problem ?

None No error messages? Then I'm not sure.

Re: None Problem with Fiberline PCM-FE1500 Fast Ethernet card
Date: 2000, Apr 24
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Do you get any error messages in your system log while the card is in
use?  Anything like "interrupt(s) dropped"?

You might want to try another interrupt even if you are getting no
errors.  You can exclude interrupts in /etc/pcmcia/config.opts.

-- Dave

Ok possible Half/Fullduplex problem

Re: None No error messages? Then I'm not sure. (David Hinds)
Date: 2000, Apr 25
From: digithi

Hi,

no error messages in my logfiles... ..but i've tried Jochen's "magic tool" and it helped me with my problem... no i reach 1 MByte/s with 10 and 100MBit <now happy> ;-) it doesn't seem to me, as if it is a half/full duplex problem, because I have a switched 100MBit network and without the tool I only reach 300kb/s, but as long as it works with setting the port speed manually, I don't mind ;-)

ciao
  Thimo E

Question Anyone getting the Intel PRO/100 LAN+Modem56 Cardbus II to work?

Date: 2000, Apr 22
From: John Kilpatrick <john@hypergeek.net>

I've got the patch that can be found at http://www.tux.org/hypermail/linux-eepro100/1999-Jun/0010.html (parts of which I had to apply by hand since I couldn't get the patch to work). This patch is applied against eepro100.c from 2.3.5.

NOTE: EEPROM_SAVE is a typo, I think...it should be EEPROM_SIZE.

I've been trying all night, and from 2.3.99-pre5 to 2.3.25 I could not get it to compile (i'll try 2.3.5 tomorrow). I can't get it to compile to save my soul...I get all sorts of errors against spinlock, or it compiles NOTHING in clients. (And typing make clients says there is nothing to do.) Which means I'm configuring something wrong.

So if anyone has somehow gotten this card to work, could you let me know? I'd like to try to get it working. :-)

Thanks, John

Sad Bizarre Linksys NP100 problem

Date: 2000, Apr 23
From: Larry Carter lcarter

I get normal cardmgr startup (i.e. good double beep) and all my logs/config files look good, yet the card will not talk to the lan (dongle lights do not even light up). EXCEPT that sometimes I can get the card to work if I remove it and re-insert it. The card will work fine, network lights glow, I can ping the other boxes on my net, but eventually (I have not been able to get a consistent time frame), the card just seems to shut off (lights go off). cardctl says all is fine, ifconfig looks good, I can ping my local IP but not anything else on the network! This card works great with Win95 as the only other difference. I have tried it in both slots and at different IRQ's (even though I know 3 is free) to no avail.

Here are the only things I can think may be the problem.

1. My i82365 chipset is one that is not listed anywhere (Omega Micro) and may be the problem (or part of it).
2. The card is going into some kind of low power state that Linux can't get it out of. However, I have had the card "turn off" in the middle of pinging other boxes on the network so I don't think this could the problem.
3. The NP100 is "dumbing down" to 10Mbs. Though I doubt this would be an issue (I do have a dual speed hub).

It is driving me nuts. I really, really need to have networking on this system and I cannot seem to figure this out. Does anyone have any pointers?

Here are the details:
Laptop: CTX EzBook 750cs, P150, 32MB
OS: Caldera OpenLinux eDesktop 2.4 (SuSE 6.3 seems to have same problem)
NIC: Linksys (Network Everywhere) NP100 PCMCIA
PCMCIA: tried both 3.1.8 and 3.1.14

Here is /var/log/messages output for cardmgr:
Apr 22 18:38:14 willow kernel: Linux PCMCIA Card Services 3.1.14
Apr 22 18:38:14 willow kernel: kernel build: 2.2.14 #1 SMP Thu Feb 17 11:49:42 MST 2000
Apr 22 18:38:14 willow kernel: options: [pci]
Apr 22 18:38:14 willow kernel: Intel PCIC probe:
Apr 22 18:38:14 willow kernel: Omega Micro 82c092G rev 00 PCI-to-PCMCIA at slot 00:03, port 0x3e0
Apr 22 18:38:14 willow kernel: host opts [0]: none
Apr 22 18:38:14 willow kernel: host opts [1]: none
Apr 22 18:38:14 willow kernel: ISA irqs (scanned) = 3,7,9,11,15 status change on irq 15
Apr 22 18:38:14 willow cardmgr[2007]: starting, version is 3.1.14
Apr 22 18:38:14 willow cardmgr[2007]: watching 2 sockets
Apr 22 18:38:14 willow kernel: cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
Apr 22 18:38:14 willow kernel: cs: IO port probe 0x0800-0x08ff: clean.
Apr 22 18:38:14 willow kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x01e0-0x1e7 0x208-0x20f 0x378-0x37f 0x388-0x38f 0x4d0-0x4d7
Apr 22 18:38:14 willow kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Apr 22 18:38:14 willow cardmgr[2007]: initializing socket 1
Apr 22 18:38:14 willow cardmgr[2007]: socket 1: NE2000 Compatible Ethernet
Apr 22 18:38:14 willow kernel: cs: memory probe 0x0d0000-0x0dffff: clean.
Apr 22 18:38:14 willow cardmgr[2007]: executing: 'insmod /lib/modules/2.2.14/net/8390.o'
Apr 22 18:38:14 willow cardmgr[2007]: executing: 'insmod /lib/modules/2.2.14/pcmcia/pcnet_cs.o'
Apr 22 18:38:14 willow kernel: eth0: NE2000 Compatible: io 0x300, irq 3, hw_addr 00:E0:98:77:13:C5
Apr 22 18:38:14 willow cardmgr[2007]: executing: './network start eth0'

Here is cardctl status:
Socket 0:
  no card
Socket 1:
  5V 16-bit PC Card
  function 0: [ready]

Here is cardctl config:
Socket 0:
  not configured
Socket 1:
  Vcc 5.0V Vpp1 0.0V Vpp2 0.0V
  interface type is "memory and I/O"
  irq 3 [exclusive] [level]
  function 0:
    config base 0x0400
      option 0x50
    io 0x0300-0x031f [auto]

Here is cardctl ident:
Socket 0:
  no product info available
Socket 1:
  product info: "Network Everywhere", "Fast Ethernet 10/100 PC Card", "2.0", " "
  manfid: 0x0149, 0xc1ab
  function: 6 (network)

Here is /var/state/pcmcia/stab:
Socket 0: empty
Socket 1: NE2000 Compatible Ehternet
1 network pcnet_cs 0 eth0

/etc/pcmcia/config.opts is standard from 3.1.14 (I didn't modify it)

here is the important stuff from /etc/pcmcia/network.opts:
IF_PORT=""
BOOTP="n"
DHCP="N"
DHCP_HOSTNAME=""
IPADDR="10.1.1.50"
NETMASK="255.255.255.0"
NETWORK="10.1.1.0"
BROADCAST="10.1.1.255"
GATEWAY="10.1.1.1"
DOMAIN="tron.net"

everything else is as installed from 3.1.14.

Idea Look at #46 and #47

Re: Sad Bizarre Linksys NP100 problem (Larry Carter)
Date: 2000, Apr 23
From: Jochen Friedrich jochen1

Hi Larry,

this might be another card which needs the special treatment of the MII transceiver. Please try the enabler which is provided at thread number 47 and see if this helps...

The MAC address is similar to the problematic devices.

-- jochen

Sad Didn't seem to help.

Re: Idea Look at #46 and #47 (Jochen Friedrich)
Date: 2000, Apr 23
From: Larry Carter lcarter

Darn! At first, it looked like it helped. The first time I ran it, my card activated but then shortly "turned off" again. Further runs of fa_select didn't seem to help.

It was worth a try though and I really appreciate the help.

Got a new message in /var/log/messages that may help:

Apr 23 12:00:12 willow kernel: eth0: trigger_send() called with the transmitter busy.

I wish I knew more about net card internals. Is there a tool I could use to display the "flash" section of the card or otherwise provide more usefull data about my card? Or is there any other information that I have neglected to give that could help?

Larry

Note Possible interrupt conflict?

Re: Sad Didn't seem to help. (Larry Carter)
Date: 2000, Apr 23
From: Jochen Friedrich jochen1

Hi Larry,

this might indicate some interrupt conflict. Please try to exclude interrupt 3 in your config.opts and check if this improves anything.

-- jochen

Feedback IRQ change didn't help

Re: Note Possible interrupt conflict? (Jochen Friedrich)
Date: 2000, Apr 23
From: Larry Carter lcarter

I excluded 3 and the card went to 9.

3 is normally used by my IrDA but I disabled it in BIOS. However, it was a good thing to try excluding it. However, IRQ 9 (where the card went) didn't help. I know that 9 is free on this machine but I did get the trigger_send() error again.

I am thinking one of two things is the issue. Either my i82365 is wierd (has anyone ever heard of Omega Micro before?) and is causing the problem or the NP100 has some sort of low-power or sleep state that it throwing into and Linux can't get it out of.

Could there possibly be a kernel configuration option that I have set (or not set) that could contribute to this problem?

What about some of the other PCMCIA chipset options? I have tried wakeup=1 which doesn't seem to help at all, but I would be happy to try others if anyone thinks it might help.

I feel really bad about having to ask for so much help and I certainly don't want to be wasting bandwidth. I have done everything I could possibly think of to solve this on my own. I spent about three days of constantly trying, searching the net etc. before I posted here. You guys are WAY more knowledgable about this stuff than me and I feel like I am missing something simply because I don't know enough about net hardware (although I have certainly learned a lot in the past few days :-).

Larry

Angry Bad card!!!

Re: Sad Bizarre Linksys NP100 problem (Larry Carter)
Date: 2000, Apr 24
From: Larry Carter lcarter

Well, it turns out that this card was bad.

Thanks for your help Jochen, I do appreciate your efforts.

Sorry for the wasted bandwidth.

BLAH |-P

Larry

None Slow connections with Genius MF3000 ?

Date: 2000, Apr 27
From: Thomas Moestl whoo

I own a Genius MF3000 Ethernet Cardbus adaptor that I am using with a Sony Vaio PCG-F270 (Mobile Pentium II-333, 128 MB RAM, pcmcia-cs 3.1.14 reports a Ricoh RL5C478 PCI-to-Cardbus bridge). It is working, but the maximum outgoing data rate I get is about 3MB/s. When sending, there are no collisions/errors. It can receive at up to 8MB/s however, but then I am getting collisions.

The card is reported as follows:

Apr 26 17:29:10 flux cardmgr[84]: initializing socket 0
Apr 26 17:29:10 flux cardmgr[84]: socket 0: Tulip-based CardBus Fast Ethernet
Apr 26 17:29:10 flux kernel: cs: cb_alloc(bus 32): vendor 0x1011, device 0x0019
Apr 26 17:29:10 flux kernel: ROM image dump:
Apr 26 17:29:10 flux kernel: image 0: 0x000000-0x0001ff, signature PCIR
Apr 26 17:29:10 flux cardmgr[84]: executing: 'insmod /lib/modules/2.2.14/pcmcia/cb_enabler.o'
Apr 26 17:29:10 flux cardmgr[84]: executing: 'insmod /lib/modules/2.2.14/pcmcia/tulip_cb.o'
Apr 26 17:29:11 flux kernel: cs: cb_config(bus 32)
Apr 26 17:29:11 flux kernel: fn 0 bar 1: io 0x200-0x27f
Apr 26 17:29:11 flux kernel: fn 0 bar 2: mem 0x600c0000-0x600c03ff
Apr 26 17:29:11 flux kernel: fn 0 rom: mem 0x60080000-0x600bffff
Apr 26 17:29:11 flux kernel: cs: cb_enable(bus 32)
Apr 26 17:29:11 flux kernel: bridge io map 0 (flags 0x21): 0x200-0x27f
Apr 26 17:29:11 flux kernel: bridge mem map 0 (flags 0x1): 0x60080000-0x600c0fff
Apr 26 17:29:11 flux kernel: tulip_reap()
Apr 26 17:29:11 flux kernel: tulip_attach(bus 32, function 0)
Apr 26 17:29:11 flux kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
Apr 26 17:29:11 flux kernel: eth0: Digital DS21143 Tulip rev 65 at 0x200, 00:A0:0C:90:7C:5F, IRQ 3.
Apr 26 17:29:11 flux kernel: eth0: EEPROM default media type Autosense.
Apr 26 17:29:11 flux kernel: eth0: Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block.
Apr 26 17:29:11 flux kernel: eth0: Index #1 - Media 10baseT-FD (#4) described by a 21142 Serial PHY (2) block.
Apr 26 17:29:11 flux kernel: eth0: Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4) block.
Apr 26 17:29:11 flux kernel: eth0: Index #3 - Media 100baseTx-FD (#5) described by a 21143 SYM PHY (4) block.
Apr 26 17:29:11 flux cardmgr[84]: executing: './network start eth0'

I have tried to explicitely set the media types, but it does not change anything.
Anybody has the same problem or some idea? Could it be a limitation of the bridge/card/notebook?

None I don't know if this is unusual

Re: None Slow connections with Genius MF3000 ? (Thomas Moestl)
Date: 2000, Jun 03
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I have no specific experience with the Genius MF3000 card so I can't
really say for sure, and I don't know enough about the tulip driver to
know where to look for problems.  You can use the mii-diag program
from Donald Becker's web site (www.scyld.com) to directly set the
media type.

-- Dave

Question Seems to be an issue with my notebook

Re: None I don't know if this is unusual (David Hinds)
Date: 2000, Jun 03
From: Thomas Moestl whoo

This seems actually to be a problem with my notebook. The same card works fine (and fast) on a friend's notebook. I also tried a 3cXFE575BT. Again, this is fairly slow with my notebook (even worse than the MF3k), but works fine with other laptops. Is it possible that this is a driver problem, or is it flawed hardware? Here some boot messages:

Jun  3 13:20:31 flux kernel: Linux PCMCIA Card Services 3.1.14
Jun  3 13:20:31 flux kernel:   kernel build: 2.2.15 #1 Fri May 5 21:29:34 MEST 2000
Jun  3 13:20:31 flux kernel:   options:  [pci] [cardbus] [apm]
Jun  3 13:20:31 flux kernel: PCI routing table version 1.0 at 0xfdf60
Jun  3 13:20:31 flux kernel:   00:0a.0 -> irq 9
Jun  3 13:20:31 flux kernel: Intel PCIC probe: 
Jun  3 13:20:31 flux kernel:   Ricoh RL5C478 rev 80 PCI-to-CardBus at slot 00:0a, mem 0x68000000
Jun  3 13:20:31 flux kernel:     host opts [0]: [isa irq] [io 3/6/1] [mem 3/6/1] [pci irq 9] [lat 168/176] [bus 32
Jun  3 13:20:31 flux kernel:     host opts [1]: [isa irq] [io 3/6/1] [mem 3/6/1] [pci irq 9] [lat 168/176] [bus 35
Jun  3 13:20:31 flux kernel:     PCI irq 9 test failed
Jun  3 13:20:31 flux kernel:     ISA irqs (default) = 3,4,5,7,10,11,12 polling interval = 1000 ms
Jun  3 13:20:31 flux kernel: cs: IO port probe 0x1000-0x17ff: clean.
Jun  3 13:20:31 flux kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x140-0x147 0x378-0x37f 0x4d0-0x4d7

Question Multicast and promisc issues

Date: 2000, Apr 27
From: David Shaw <dshaw@akamai.com>

I'm using a Xircom PCMCIA ethernet card (xirc2ps_cs) on a Dell Latitude CPx. MULTICAST is enabled (so says ifconfig). However, I can't receive multicast packets unless the interface is switched to PROMISC or ALLMULTI. I do see that the multicast group was joined (via/proc/net/igmp), but no packets arrive.

I've tried different ethernet cards with different drivers (the wavelan for example) and it has the same behavior.

I can duplicate the problem on both 3.1.10 and 3.1.14 using kernel 2.2.14.

Since this doesn't happen using a non-PCMCIA ethernet card, it seems like there is a bug somewhere (either in my configuration or in pcmcia-cs)

None I'm afraid it probably isn't tested much

Re: Question Multicast and promisc issues (David Shaw)
Date: 2000, Apr 27
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Each individual network client driver is responsible for implementing
multicast filtering.  I suspect that this capability is generally not
very well tested (if tested at all).  So I am not surprised to hear
that it doesn't seem to work for the drivers you tried.

It would be nice to figure out exactly which drivers have working
multicast filtering, and try to fix the ones that don't.  I don't have
a trivial way of testing drivers for this but I'll look into it.

-- Dave

None Re: I'm afraid it probably isn't tested much

Re: None I'm afraid it probably isn't tested much (David Hinds)
Date: 2000, Apr 27
From: David Shaw <dshaw@akamai.com>

On Thu, Apr 27, 2000 at 03:54:52PM -0700, David Hinds wrote:
> Each individual network client driver is responsible for implementing
> multicast filtering.  I suspect that this capability is generally not
> very well tested (if tested at all).  So I am not surprised to hear
> that it doesn't seem to work for the drivers you tried.
> 
> It would be nice to figure out exactly which drivers have working
> multicast filtering, and try to fix the ones that don't.  I don't have
> a trivial way of testing drivers for this but I'll look into it.

Hmm.  The weird thing is that when I use the same cards on my 2.0.36
laptop (a Dell Inspiron 3500) using pcmcia-cs 3.0.14 it works just
fine.

David

None I don't think I can explain that

Re: None Re: I'm afraid it probably isn't tested much (David Shaw)
Date: 2000, Apr 27
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I checked, and the multicast code in the xirc2ps_cs driver has not
changed since 3.0.14.

You can build the current 3.1.14 drivers on your 2.0.36 setup, to
determine if the issue depends on the PCMCIA driver version, or the
kernel version.

-- Dave

Question DFE660tx-problems with non-auto-negotiation

Date: 2000, Apr 28
From: Christian Froemmel ckf

I have the following problem with the D-Link DFE-660TX-Card: When I use the auto-negotiation of this card, the link is established, the half/full-duplex-led is in the beginning off, just when I transfer data the led starts to pulse. The switch is 100mbit-FD and there the half/full-duplex-led is not pulsing. mii-diag says, the card is on auto-negotiation and the switch advertised 100baseTx-FD 100baseTx 19BaseT-FD and 10baseT. When I set manually the card to option 14 of the tulip-driver (MII-100baseTx-FD) the link is not established and nothing happens (the mii-diag says: link was firstly broken, but now reestablished). Yes, I´ve changed the PCIC_OPTS to "pci_int=1 pci_csc=1" ;)

The laptop is an ibm-thinkpad 4187 with the O2Micro OZ6812 (rev 5) Cardbus-Controller. With windows the full-duplex is automatically set, nothing pulses and everything is going fine there (but its not my preferred OS).

Or is there somewhere a tool, where I can turn off the autonegotiation by default and force it to 100BaseTx-Fd (I did not found anything to setup at dlinks webpage, just diagnostic tools) ?

If anyone needs more debug-info or has THE idea, please write.

regards christian

None It isn't clear to me if you have a problem

Re: Question DFE660tx-problems with non-auto-negotiation (Christian Froemmel)
Date: 2000, Apr 28
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Is it just that the LED is bothering you, or does the card actually
misbehave?

Based on the mii-diag output, it sounds to me like you successfully
autonegotiated a 100baseTx-FD connection.  So I would ignore the LED;
maybe the meaning of the LED is a configurable setting and the linux
driver doesn't know how to set it up.

You can use mii-diag to force the MII to a specific speed and duplex
setting, with the "-F" option.

-- Dave

Ok Success with NetGear FA510C

Date: 2000, Apr 30
From: Chris Love ChrisLove

This card wasn't expressly on the supported cards list, but is working fine on a Dell Inspiron 3800, Redhat Linux 6.2.

As cited on the "Unsupported PCMCIA Card list" (http://home.snafu.de/wehe/pcmcia_linux.html), the following entry in /etc/pcmcia/config was required:

	card "NetGear FA510C Fast Ethernet CardBus Card"
	manfid: 0x9513, 0x0081
	bind: tulip_cb

Older releases may need to compile the latest tulip driver; Netgear includes rev 0.91 of the tulip.c on the driver disk.

Kudos to all who have worked on this stuff! My early impressions are that linux on laptops is pretty slick.

	Chris

Question 2 PCMCIA cards in one laptop. Help please...

Date: 2000, Apr 30
From: J Toy gee308

Hi, I have 2 Linksys Etherfast PCMCIA cards. Im trying to use my Laptop as an IPMASQ server. My Linux distribution is redhat 6.2. My laptop is an HP Omnibook 4000 CT with a 486 50 mhz with 16 mb of RAM and a 503 MB HD. I can't get both PCMCIA cards to work at the same time. If I pull one out, the other works and I can switch them so the other works. ifconfig reports that both cards have different IRQs.When I do ifconfig while both cards are in, it shows that they are both running. My test to see if they are both working is: while both cards are in laptop, ping local IPs with one card attached to a LAN cable. Then switch LAN cable to other card. The IPs I gave the PCMCIA cards were both 192.168.0.x/24. I'm sure that it is possible to do this, but I'm not sure how. My current IPMASQ server has 2 Linksys etherfast NICs. I didn't need to do a special config, but things are probably different with PCMCIA. Also, how can I set an ethernet card's hardware address so that it boots with the same set hardware address everytime? I know how to set the harware address for the card, but after rebooting, it goes back to its default address( this is normal, but I need to know how and where to put the script to make it boot with a different hardware address).If you can, please email me your information as I don't surf the web often, only check email.

Thanks for the help in advance. Jason gee308@mediaone.net

None Sounds like a fishy test procedure

Re: Question 2 PCMCIA cards in one laptop. Help please... (J Toy)
Date: 2000, May 01
From: David Hinds <dhinds@pcmcia.sourceforge.org>

This situation is specifically covered in the HOWTO, in the section on
installation and configuration problems.  You may just have an
interrupt conflict with whatever irq the second card is getting.

However, I'm a little concerned by how you say you're testing this
setup.  You cannot test a two-network-card setup by just unplugging
the cable from one card and connecting it to the other card.  The
kernel has a static table of routing information, and if it is routing
a given address to one interface, it isn't going to decide to use the
other interface just because the cable moved.

You say you configured both cards as 192.168.0.x/24, so they are on
the same subnet.  The route for the 192.168.0.x network is going to
have to point to one interface or the other: it can't point to both.
To test as you describe, when you move the cable, you would also need
to update the network routing to re-route addresses on this subnet to
the newly connected interface.

You do say you already have an IPMASQ server set up, so you must have
gotten two cards configured properly on that system.

To override a card's hardware address, which should almost never be
necessary, you could put an appropriate "ifconfig" command in the
start_fn() definition in /etc/pcmcia/network.opts.

-- Dave

Feedback Setting another MAC address is no problem

Re: Question 2 PCMCIA cards in one laptop. Help please... (J Toy)
Date: 2000, May 05
From: Andreas Hotz ahotz

Setting the MAC address of any card to another value is no problem. I posted a way to do this from your network.opts easily by changing David's network script slightly. This way you can change any MAC address by setting a variable in any of the "case" clauses in config.opts (for example based on the slot you put your PCMCIA card in.

See item 66, subitem 2 in this discussion forum for the description.

Question setting ethernet PCMCIA address

Date: 2000, May 01
From: J Toy gee308

Hi, I need help setting my ethernet Linksys etherfast PCMCIA card's hardware address automatically when it boots. I know how to set my harwade address with ifconfig eth0 hw ether FF:FFF:FF:FFF:FF:FF, but when I reboot, it resets. How can I make this automatic? Thanks Jason gee308@mediaone.net

None Don't know why you need it, but here it is

Re: Question setting ethernet PCMCIA address (J Toy)
Date: 2000, May 01
From: David Hinds <dhinds@pcmcia.sourceforge.org>

If you have your network settings in /etc/pcmcia/network.opts, then
you can just add:

  start_fn () { ifconfig $1 hw ether ff:ff:ff:ff:ff:ff }

to your settings in that file.

If you are using Red Hat's netconf tool to configure your network,
then I don't think they provide any interface for doing this.

-- Dave

Feedback Setting the hardware address from network.opts

Re: Question setting ethernet PCMCIA address (J Toy)
Date: 2000, May 05
From: Andreas Hotz ahotz

Setting the MAC address of any card to another value is no problem. I posted a way to do this from your network.opts easily by changing David's network script slightly. This way you can change any MAC address by setting a variable in any of the "case" clauses in config.opts (for example based on the slot you put your PCMCIA card in.

See item 66, subitem 2 in this discussion forum for the description.

Question LANPRO Realtek 8139 B/C supported?

Date: 2000, May 03
From: Gabriele Paciucci <paciucci@caldera.it>

Dear PCMCIA developer,
	Is the LANPRO Realtek 8139 B/C supported? I've downloaded a rtl8139.c file from realtek (with CardBus support), I've compiled in a 2.2.14 tree, with pcmcia-cs 3.1.14 (i think!!!). The card manager find my Intel PC Card controller but when i try to make modprobe rtl8139.o the kernel give me a beautiful "Resource Busy".

Any idea?

Thanks in advance...

None Not currently supported

Re: Question LANPRO Realtek 8139 B/C supported? (Gabriele Paciucci)
Date: 2000, May 03
From: David Hinds <dhinds@pcmcia.sourceforge.org>

(if they were supported, you wouldn't need to get a driver from the
vendor in the first place)

If a vendor is providing you with a driver, I think you need to first
contact them for instructions for using that driver.  The drivers I
distribute do not include a Realtek CardBus driver, and I have not
tested any such cards.

-- Dave

None Re: Not currently supported

Re: None Not currently supported (David Hinds)
Date: 2000, May 03
From: Ing. Gabriele Paciucci <paciucci@caldera.it>

--Boundary-=_nWlrBbmQBhCDarzOwKkYHIDdqSCD
Content-Type: text/plain
Content-Transfer-Encoding: 8bit

On Wed, 03 May 2000, David Hinds wrote:
> (if they were supported, you wouldn't need to get a driver from the
> vendor in the first place)
> 
> If a vendor is providing you with a driver, I think you need to first
> contact them for instructions for using that driver.  The drivers I
> distribute do not include a Realtek CardBus driver, and I have not
> tested any such cards.

I find the "driver" here :http://www.realtek.com.tw/cn/driver/8139-driver.htm
and claim to be "Linux Driver (CardBus support) is modified by Realtek "

I give you in attachment the zip file...The vendor of my card is EDIMAX and the
model is EP4301 ... I have insert the rtl8139.c from realtek in tree I have
probed...but no success... any idea??

Thanks in advance

-- 
Ing. Gabriele Paciucci http://linux.ing.uniroma1.it Linux User Group Roma

Work: paciucci@caldera.it  http://www.caldera.it  

--Boundary-=_nWlrBbmQBhCDarzOwKkYHIDdqSCD
Content-Type: application/x-zip;
  name="linux-8139.zip"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="linux-8139.zip"

UEsDBBQAAAAIABeFWCgy9+z6SSYAALRLAAAMAAAAcmVhbHRla19jYi5vtXsLdFPHteiRJWMBIlLA
gPmkHBKcmAaMZT6x+cVgjvkUJcJGQFOokS0JydiWr3QEJq2MnYMTH58oSW/6fTddTdr0ljZZXW7T
y7dNZUOQSVgpTbmJX+ARJ3WDiQ0Y4jgm8bXe3jNzJFk2zV33rXfWkufsPXv27N/s2TOSDwqbizQa
Dac+Gk7LxSGO45fRdgn5m8VN4iZwiY9N/ofUm7N9W0lE6EU4InRj0z0UjUYbw8ZDD6VwXMgSlS0X
QpZh2dKhWC5sUSwdW4xHhW6rm+NSKKl02gTUjVqkFoasFZzxiBC1wp9hK+kPCV9YK1KSkBGhC+eS
TvMuaZUDX42HfgfCK8Ehl2L5wiVbLp9AtDl80kVEO18JjXzGtWJ5wOhShMuK5bzrPo1rhVbMkNoy
pFMZknA+I1SUEhW6gEpazgXeUSxdIZ3ZJa18g01ghQmS5JBO60O2/sZwQGe+2KNt3pFVXGFKIlGC
/dKVIeORt2RLJ2UZWvIGFd408GQ1vGjE6dEjNfCyXeWJBvmIQ4Pcslbokhi6lB/iKOmjNFDk1vg2
4OPKPy/mGo++XwK2vWWN07vrtcwhJaPYSKfnKZZe8EgXfDq3bFcs+i1xEuVJEeaInpcFvXR6dmNY
3Exl1YmFIeGmtWLSKG6m+uDNOfszAXXT6u5U560oGIM0IyLo0QJRoTcqdDcEu4fRvs9c/C/oDPZy
gbRj14CuJ8UcDjlPf+vbpWdPkVjLgFiTgnzawamKwCu6Rh5dKgz1TAodofE3RMy6ivCum69M7YKY
km19a2XyJgX7uMCU6FLsdZt1nBp++goIGxO1vSyYFCHDqtjSi5XgbE1UDg5qg7OjS/5rNwxSBFM0
x/2QOhKIpLZil2wbAAuZw9crkBEM7H4eJzttkFsbbs9v4LjAeFggKFNPGryMw6i8qARM0hm3Euzd
HipMI9N170JhW13yXTBUOpNSKH2ZUndZpQyJ90Po6RZb3SUJggONrq6b4h+Li2WK5iqq3DVE7nQ1
FNOhV348HXSU12a4f4CWOM+xgbLQC4ocx+UuR8zhoU9fUWy9oLNs3ams6kTpHjf8AltFmC2vNTUL
+qa1Gc2CoWntDMU2e0D3g5oUjOUq80XzAMorDWv3r67QlBDjziHagWoNt6NRjhPnNJ4VZylCb9ML
49phwqKS6EPu+rhqBlBtTt2fGgcCWUQfdzimXrD3zFM4BA3QMwFYnKlHkFcs6VKrtSUsv3m9RetS
bAPXCeZbLRsAIwWHuDqLIgzJQl9rVd/4Zltf/UeaJlsPqNj8xNswft5ws61Hf75J6GsWhuYZw50p
9c6+U3oAbX0wZ9OPkGigbaWYVv/sX3AhkEjMxEg0NBYAovFs3fT6DzVA20xo6z8a1r9Jh4GQA/X4
ohGXUHW4VKaOew0klQodjDK+/mfUYztY3NrdgbnM1lvfjKNSwIKRp17GuIUwijz1Krz8wYRvh9F3
M+FtfcG6uYg4BoiuWfgWhreneTD6YMh5Kb6GDLCGFIvJPKDAwg5bYfn8GSPyb1cmBg0t9Ypt6HpL
03WpVVf7oPw34y/+4p8QEfpTMHb1z8EbitAs9Bua5PevX8OXp69f23jgPcUy1NIEVr523ITB8x5d
jy1Py19cv9bbdEozIL8vfaQZ/y4QAWZj49mDf2/5HOeS+0LObiJcaB/dT0wo3y49iKgUpkvhx0BA
JWhovZIqWwYbLINch5abGBw0D0hBw5y6hdLttIOzXu8GAetXmjnR5DK+nm52aUvSXdeMR9shgZyV
269KIAvG43EeXWEbwhWLcMshEiW9LY3XezceuHnciN27hlBrWLF9Oo6u2D6qdJ+hHpTuxZcGpO84
PoUj+405DEr1agZA0XCPRtVUg0jUtLN1WGM8OoCadhFNnyN66qkflF2wFvVKbboUeUwJGFo/ni5b
hlqdQ5MbLJDMUqwTA0PjLxNdM0FX47MHYc64viLoawB9N6TLHfKbrhs95URHlxz8AuxJ9Psirt8c
9M2Xxl+8jeoNHWLqDdUT9YaIcrah+jc1TefxfeOB/zyOjpeHQcFbwEVD9bkZcvYm6EH8FdQrpTuV
9emwuBRbn9T2EJh4uMV0fTssamChc6+cDOt1fwZNM5AF0mH1m459BtDV3+G+T+IlmorRUz8pHf5m
VEx1cxlqYmqVldOABJwJKpQYDkMc9h3leeyUYRt+R5zUeDawsJglEZ26FdztxuoGhClQl92xfpx7
aQruuZunc9zxbi3y0rmUwLBLDvRjfCi2/t7DJjEVtf7UfDa03y0HBhWhT9MutynCYLNOc32NdDu1
rrfFAIYehnTTJ7WuO8a9AMK8eYNABcc4HacFKCL9GCWB9dss4ZJuEgbDVYOaeuegZt7wBGGwiWDr
T2IG4IJTlBJT60cpA0+QjGo89Awqn2p8XcJu6/bud0AFlyz0Q550rYpGxekDpzWBiZloD5c0WBBI
q1dItqH6a+qw5Oq3Dkg0BaUd94EZelKP74dmi0sK9nPizM+F/nrIOeKE49/FTiPEz/FGShZCMjDe
i6mx9JxOtKPJVmU77owwuLtHB395JdAnnSluFgYhcMxIoxBfNXwIgx8mnTlyu3yL2mgzUtzY3v29
u4kHmDEj6+ehKSLreWzOrJ+tIcQrjx0Mg/Mh1lXdVoytFqHeIb/Z29RqPNJqheCDyCzGeBwX0yIj
VFIbKawl86zF5c69hH9SccXLUj3+PYnLJCI1wV/dRI6jkYVlSVfyGgjolbqdShGsgSF01Y/QVcXb
uh/4EsQ91fwsygjuGmhNMTb+Em3xJW6DxkM/Qf40xwxENIEJmWHwAvEhYLEaNx55iozt1KwQ+sQq
yD/zNPUfDutbmwjPEuPrZDe0DjxFzTCemiFNHqCGiC5z71ZVhjwNXgP3UcexEWmv7e5JBX+/xsP+
KIWL5bamDua2XUPSqdXy+65rh1PFTJJTB1pTxVnINKwyreC2RfdldH99HCqYIdXN48QMYscHizas
mgPLat/4bd2XiPpsQaYYn/k1NMp6U2tnCiRkWkV9MVBPC4jpBLWjNzOKesFUXBooNO05gna7rmWi
5RBfkBavF4hqy+Q3r1lRXEpCcCshWOJD6uND0jE7skkI5RaIlticnXFCE42KGkgT8lMYFaH1texo
wsJAHiBxsBnjALJ5wU4opRSbXvGlqxlolXwzMRwRWo2Cya3Go7e3y31S+CG5jXXCSKgQeH1cUvlz
KbISsvonuNe4biAIKTZ4GuoK6dgLOAFE/2P6+GqF0iH6++8DPvr759DSQT2WVypH80XkCXOaIIlc
wCLvBNJKV7T5XwbGH2/Rs/ghrEK6n+IEsnAOzm9ayzkwsdy6pYSyDCcICRWbtu73IJLxdVKQWaH/
48QpDSUwlfH1fyUrA8Zv754wiIl8i1s3fgSbtLr/dE+Mo3QtJsV2+vpJTNHyX8GGmJS/0XjxYD9U
xxa91Oqm+4d8S/N+s27ideCQWncLTWylURzsjTz1NEefFgPyws5YpkaAJGqStlGucZNwUZITJuij
1KN1QPb8J9CYYlHI0if/reHUi8SyvcpTxHidWiVdUoJdcvrx9XKwKzYODFcAY+UnCJPgufX5J5BL
4A2giNQ/x8SKEFp8zBdX7OoyhnBLk87wsBe9k9pC2HQotguwTN4NraQOCXYq6xb1ycIl5H5oOpGm
pR7+fn5GS8RUYIguTRZOK7ZLSvFO2dYu/7X1aoocGfr0lwNtKWKKCxqNqHkZCW2diiGFJmjYA9/R
BjpJhu4xNXxMcbZ3tLZOue8GMtu0U7q90p96fCW1wMRncXODYe+qwwpRh6eLabku/wy1hOg4OFO+
3dCKgj6H+2tEh8mPI3HzaaKdFWKh+REpqt0/ExZUpIDuBU+8wGzUczfdn3spCtOksgo7gFiu3YDR
vzaH7BQg9yeuGyHn4cR1mkHWqUHZsRMKLzk4ZDzhnsfNCMMhd4HKxqAUbJgfaYg+q8H8BRXo9u4Z
EI3HcKqrS+Ev5EtFInp1amVhEBIZ7McQPPIfM4gnjiZ4YlNIoi6Eg0S/sjJNhqCBNGHdSfwxyhuY
5ngl2KcAQ0Me9YnW1i+33+iZTDupTxDXhwGrPJroD6QwTVTQJXSUchLllIN962XyBiVMgXISbT1/
UBrU7oczlMF4omYe1zPfeOIVYmM65EFChF4wqSTGE69RAtVOYG6a43R1c+DQCacXfbRmZ5QEIpgN
cgCvrmTcNi8l+mEJ9QOYT6nZqUzFHRiqOHabpBTAVtqNYWEbNL6ylp/xDpR36wCA3LhbZQllWKSA
R/Krv9Oi7n3FgIJDenhCfGs4Bg0GwmXXjavlSCV0S+HVkPouX70GG86A0PUvImSFweLufbQIBIzB
eGgHHsFeRwtcnQKv8oAcPC85z2uVXd3SKTDIeeLzC7LQqd11QX7/mnzq81NcmCswHroFY0JPvkhc
3gFIjtstblLrlSklVIfOeIIzRItyCFmBaIwW7VRs3VJbwTENVI43Gi8GtdGi3aSXF1dHiyp78gci
BeI9yjPoYDxML+L2Gxpa8TpNJrhokUPuaB3MkDqNmqKChr9HYSfTfDsrWsQrtg5FgHVuim6sMX5f
OF8fPM+J47eoaZZ0X4joTMT8P0Q/Y0RmGE8coT4XBlkMLERw/HrlGYyS/NvGxg+HIZG3Yzjp9t0T
JeRbtlM9+ZgnIjrcdohFXZ8LXY+HjYccGvW+JqVumiJ0WZl/E7wnBbuixkOvoDPQ8JvR0q2aR3aY
w5CKugbaeOOhH3F4udML1VQIxSzCsoIWEzqxjljTTWoX88WBN6BObviQ1Fi3CwKpJ2mF9SSrsPI7
xKL6v2uaf6ie399vIq+KpVutdpVgt0uKFA88SWuniVA7jQ/94X40yGt8Uwec+uieI3TN+wAW/IDQ
5xPBgwsgNAfOFODrOsDtxpetsBBhK8uNFm0gQi5HIQflL8lseQ1/x8Q2/wP5ddy6XMqT2EjhPqx9
XXiVFfw6uS7VGY9sm1FsPFKUQWuSaGCIGrE5bsTZUUu/senyEFsGpOpolYUuzEiT0PqHeTGdyCC6
rg2c1ot4UUWyqtBFF450W1f3NTrwr8VxR70YD2IT+vRg2Nj4KsDUp9q66Tga6wW6KrmJsTsqCCUf
z4Wc4YQ6Oi+hfhrC+qk4XbYNKi1h4AVnMpdyjJhCDt5S7kH+ePu1ETiPLJ4Gpba8mKSWQal1uVpo
3dxmPBph5VXBxJjkGZSbEhiUzkBZFXjfeDR4Sw5euvpTTBaWSw0fwqKCVHMJqrr5FshH/UqgV0mf
hhuqrbu1qtuEgnzTqgS6txXTuuhFlTu8X1TfI8I5DBNwh7KrX7ur13hEa3XfisuhL4wK56TgOaHu
HyPKH0VoP6wXzUwz2dahFpVTYEo91seGhDo4OBRdv46cqgeE9tXGQzJduVIYhsI+v2vQJZ1apyaj
aYqtvZgyKUhmsgDG3wtxut4KLxniODgcRAsgAbcPtOkACgxFizYDYUJpBadn2/vXWwzXaWX1/g3g
vK37OE2qV78GIlXoSfKdTENVPoVX3RfFuyRy2DJJEp62TI0XA/NYxarKROZeAtTUVVdNwAvOA3q5
JIOOTVEUHCu1psjkBT0U7A6JD+lgU5IioHuwo2EYV5TxmXkarO7ah6KkupsvtMuWLvlNLXjzeTq0
XePfueJ5PPPtM7r7MzhuW0ncMrB194e+m6eTg1AQt8P+DTWfEjgHToKN/DDZxw/Tbbxbtp2bD2Xz
a4dI/HZqA+dk8g5VoOY7O1e8xmbYNoPjtsdnsJwjTDuVQL8inBvJlG21xmfwCjDuu98YYiHWTkPM
gPUJBmq78Yhu2sgwK5ID7dKwse6DEVF2XEck6z92Dp6hT1/p2Yy32d3FxJL9aMmYFUxgWjl4QSHu
0uAJ4gI1HWql2m3BzBFaQSRQAK+4vyHSd+ADntXUzosWzEYiW7dLY7vlkoRbafXOW0P40offccDO
BCmIHFfY0jce7ZMDlzDeeg9rjIe2Yc6BRbiaYFgmwLWfF1/7yblACV4i1UqOuzMWZgEopofk32NE
Y7Xyx/i9qZ7dS34nXSnE9HSmcDYXKcRQ4tTFNFv+QmpbHTtsLnYXTIovKexbaQ7D4Q1eHrqOfzeD
IKj+BrKX4dGbHStLon56VWYeQKvsGmJnjSlQAU2JboK9O3woLI6PXXNFtMTpp3RF0rC2rgMXC8mZ
saXTclqFcF7YyMj8xS1a0n6rZcP16KT43ZseVU+848tR83I63jmx1D4XwktqW0eSu01vPOqzboO0
Wh9XGUokvUvZYKV0kLcuw+4rzsTibFIsXHvx0rVnDjkPKFMNHCnh863iwdSBN1JEHgju4nC1DmIu
DQUGYRlFinQIXG0jHWo/WiAkDEI1FikgVznsUoVsIzVXmwnnPgjDFUWiMfQkifVuKEmOR4kc5+Go
yzVPb7J1rT+ZxtH74tASC3KQAx3NQhdUB1DsNZ4NjodjwsSe6bC+pOAFTrwLYrPh1tF7WnWy7UIP
pMUOOXABTsrhqi7NNw78MWo5f+Cw3N7aPdP4CiiB96PdymTYNhrfMTbuhambhV7cI68rln6pFbLj
ILk6hHcDlmoFOgBHfAdWAL44I3RzZ4QraCopT2NsXIPfyQT1xiPrU0F/K7Q6OBZa3dxdzM6h4ND2
CvBHpxV2MXZ1EfwC6tntFSkjsNLpBSNguQ0z9DuBcWeEi1zPuObirCbbxTPCVS4U7IcEaL5oPCJc
lYUw9V/w3PYKkOLTbYoQjn332XCFo+HQAKsibVwgn3ynmRGncQGPT8nKDurhfbuOfp8ZMDXtutIs
XG0SunsMhP/wqfovh/f9ZFi4Wh+8ete+J0JCn7VipfFI4Mo245Fd3SUqN1sfBFsfcoH1stzV8EWU
Exc3C31NwsUKrmI1y0MVqRUPxzIa7w6bd3NuLGfjWS4UvL4dcmCiPZSxTMaHgr3bKxYkmfeT7RXZ
I1B4BcKf2I2p5az6pbVY5lKC13FzgjT3BRjhXdhgADwDh+lPQrqNrXi4bFege8UxHBC4B+jfda34
rmlcYDK8nsFXfSDNtUI0TRCnDp8yHnkLhpFZXNJ323Rc4HgFh1/rXrTCXi1dGUrU6Fcf0T14Nuy4
OnO4Z1XF1Ios6nchrCyWI0Ov/uZQOPAFuMoVKbgXWJLDFjuOj7iuB5KQ8w+xnBEr5CL16pk9Uv90
7G2MW48B88VQE56SQ8+9yNH1F8GvHzjlGCYvzQdyfsMpvLuVWnVSG810l0PO/vh5kl3CWmDhmJRt
O0PfNK26CcWPOP+gYVUfvhiv1gOnVbfwfXHP/uean8DNct7DckS68rBLPmByKYUpUuccmr+NR7XW
bd3uf+BNe+E4sM43TnCd0ejcj5Qn8GSYyYH292HWwK+rMYn0fL1+U6rGeLRQZ01itMYEnMZ9jCfg
ntRjL2F4MMHRVtRUcADekN5cMBsS+11S62a8ZTul+TbuDKGi2SHn4Le+Hf+OTEe+O9JvcWepC/xk
J/nKWS+R72k50UHWo1bZsFO2DMlvSm0GJQeW19Crvw3owaODIIhuRtiggVyml/8mHTBwgb8qWoAe
ZIeIxTTcLUPKGoOsxckoPnGbCDn7YnmJVqTiWN+uuxFDV0BY1WFbSRxLroWp2BtfIl8v79ip+A1s
wRWaQrqC6JI38Hts0hutSaebJBVoKeJozC6lRkhvHAgcZRbjvupBRXAP58foi/4/PgJsy72m+Q34
iUZTuXrgWQkiPkDw+Q34ScRPIPi8Bvwk4lGtKXffPRk/ifgX74DfnUL5FKVoudH4/FF4PkavGwOP
9Kkj8J0aSv/xlKUpo/H5o/AvMvq30rkx8Pmj8LsZfW66ds1ofP4oPM/ov54+TjManw/4tBH4To7S
V6bnO0bj80fhX2T0fzJl6UbIw+iT8Xd6MM7G3eEz1lN4Of+twrfz39Jezvuy8HLeWyossc8Y8EmA
T0rso/Ipg53D5a7gHoZsUXNPnL84l/yegDwoW445O8ecML9PrMwzL87PLl++D3ry+GWLcpcuys/n
13mr7ZUOfq2zfK/Tx7tFsWb5okXlTr/D48/e43eVZ1fb/fbsPd59iyo91YHaRQ6fZ5/T51+k8nOL
VZX4S7ISW7FQ+KiFF6wLl+Tm7eAX5y4s84i8OSdnkTnHwheu8TnWBvy8tZAvtPsc3Kjnq8bbv2J8
caDswFZnuXvROnt1jbOWLxIWLluyOH/rjthQM3LK4YvsfpEXRLfTV+0U+TUOe43o9IF/RlBZymr8
caKxZxz5CA5Plb02cfjIiVT+sQmTnrWeykqPt1r0VquCrrX7nQsT5FdZjTE5PMxeScqqY7KKl84f
e5z6rHE4RB9MvqZoYe6ynK/WI9kROC7vfzAuNr68HHW3WHcszVmcw2cVO+2VW517+eKtmzHOvkJ6
iB9LoTnXbAZ7CY/hBKoFRjNKQqwFkTYuYuIld45UYmRvbnLvP31WLlvN81vdTpyNX7vx0RLebffz
1V6Rd1bbyyqdDh7Y8A7nPk+5k7eLfKZjUaZjLs/bahx20VO9h4wr91ZV2asdfOaS7CW1C1eTJpv+
jnPlUuCPNJV20VldfoAXPVWwoLMKizZvnc97/Hyg2ue0+7042QG+0rufTpLN8yVOkUwgevllS/jy
Sm/5Xj8wBYEz/fTvcj7TT8jvq6xdwG8s3gIDF/BcZm52bu1y2mSP/DXpmPojI8vGjbzos1f7y52Y
R3iXNwD6AG+7w+Fz+v0o0pis2PhHvMks/JQHmGqN3x+oQk1KvmlJpCAM1fmdDo+dFw/UOGGYrxzN
7uWLApWV/LpATaXzznqsXEzGF3oDlY7qB0DeSjAUmJq3g8h82QF48znJfLwPZAA+LuDKue2VLg7i
sApXBLzQdiz+VD7VGZn+TP9CBxGJL4NE4OBhcdgDondhtXOPV/TAzA6+xu4Tq8GI9jJPpUc8wCfG
wyj+DxH+JG3n5pd6a5zVWRAXXrQ7cSzzK7/eyls91eAIdCsfk+KrHDxK/lHSo9/ugwlgH9k7SnSv
659KH7O/ui43VkMS9QVqRGTn5Mswap0QlH7RLkKWyRzFiOlP/e93VjrLRUi3sErK9y5AnWtiOt8h
/v7Z+M2JKo2tBxvPP4rZAkJlj8cvYvDafU5UxmL376UjESphWhC4uDYRvJOBVP6Fbk8N5Ilql2eP
6sL/3vpcQsZvxWVTBRsJpg9vQIxblPIiElURI6h8F/Ak0r/iIcxr+X8JOANO5OnDxCf6DmDI8Q6P
D2JAhTMx/fBZlNTttDsw+av6AQ+H01/u89SIXh8OhtSWmZedV5ud6Z8Q8xILtRFmXs5R8bkxbcFG
bsFJHThLjR0iSiRpr4b3ex534mSQLPyVXnGMLMXis8RiBeKqQKVorwb7+ZlSEN72at4TC1o3ZPFK
lplGzB8nYYZflXkfsXm1cz92IpKhRkoA+X+E/4CL17cAFVEdSIx0xzBg8j8aEBd6XQv9B6rLmVdq
vESmBaj+Pn82Sf3o8FUjbcDmX1NW7fVV2SvjiixIFoDNRPZBNBAK+hWLn4vHp9fLVwXK3fx+r28v
OidhHlg4PrpUVuXUJjNk9nXWekh+ShgGr77SEcYeSw42fmN1LIX6arPmL+DLAz4f+JitjLUB1xqS
UBECO/mcTowZBhZWOe64GtX4TuQesxwdToOQvsO0MZuxoUU+e5UTlz7s/yJsMnSqGH/qn0dxxwQ+
jnhl5sJxC0bMNfeO8o0cBXHsoA70j2QwWkHmP4uzygvrwQ+L2/k4zOpwumA8eoSut7g6TJ/9PnsN
X5D5lfU3GwXHGef/Fw8x/iXuAN3gHN791bwTrVEOpWNM+/1Q1I0IPrxMThgPy9opgmClVV6HM4vQ
zQdeIPTChZDpY5l71GJl/rP6vFUef3kAUwuyUKvH/079xY5spXZRtJe7s8rQWWQxV9O9LNMxf0Ii
ncNJ6DL9gIbasVJ07i0tL7sD/70YFpWlJLy81avAhtnm3IW5OWo/1C5ur2/VyOPmyjLSFox13lw9
kr+a9JF5Uhm+aHSlztNjKgd7chXUOjjKv8q8MM9DMZi/Sml9koDFrO0pBzalLg8o6yut9EAmXaX2
2mtLY1mjFNOP2uNwlgX2AMCtLyxczmetf8Q2n3fuKfcvzM3ON2cvW8ab8/PzcxablyzajEdoPot0
mrPN2bmwQ1VCVe6EHS7bf6BKtJdBK/po61bfRGetyGUDKXuDE4GdwvStzO/nsuEo4QSkl6IgNjzV
Li+XjUcGiP5kd93xmcXF7zbwKYDPL+6N95tYOxc+4xPGzV7LcVl6Dn8UQMZj0ON9xIMM1qqE90Ff
DIjf1eFdRSK/dZs4rkZD+SG5ym8Fa1UWuvu5EY+OtQXwSUvE30/vB9VHw9oi9q5e9fBAt+muOB3P
2kcSxuBTvwRkSECodNuT6KSlHLcqAVb77uYSbAJPeCm9g0qmS5QNn6w8jrOmcvgrAe4BjuqLPkHb
JfKrhUl/rovDiTIlPol4HXczmtinTRqlHTEDwqnEP/EnmT6Nm8nedaRXy93L3lUYr5j1CTD615AA
F3PUtjyDH+Oob1U48dECJ/wHwd3wwR8VYD/+mxve463Toh01XBBg/DHRbDYef1GBd7LqfP8L2q4E
+DfQtoC98WeaOB5/nGqFxXGFwWFo8yDQIgx+CwUBhbRsvg6O/nvPkxoK9wCM/+TzJaO/DS3+t89C
Bk/U0P/5eZrRT9fQ//w5yvrnAoz/MqJn8uUAjP+QYdTR/rUAZwC9j9Fv1dAfu49LoXAZwIZJHPfv
TL4AwJuncdwLbHw9wLWTVP3TuO9r6D3jr9j4X2joXeP3Gf/ER5t0+6mFqPw9I5nBYczruTc19K67
gMBa7ryG+nIx6+/UUP8tY/BnAP8Q3iczeCKMPQzv0xicCfDr8P41Bm8CGH+fPpPBewEegPdJDD7I
FhPGxGSQP5SwuHAd/TQJbkmCzybB7yXBN5Pg4SQ4NSFkEZ6TBOclwcVJ8O4k2JsE70+CpST4e0nw
j5LgnyXBv06C/yMJ/nMSfDYJ7kiCrybBg0mwJiFnITwxCU5PghcB3JdCczvG04qk/nVJ8DaA9ffS
9Yb+L0vq9wGcB/17WX9DUv/zSXD8Yp3bU16eWwr7bY0HCzKOlULc6MKBIxUDN3a9wbFyhUsoUria
ck+pWFbJqZVtjc9b5jQjWFpur6FdXi8Ulqzf4dzHOTwOtRzLXrokB0s4R6nTCUOruCqHx1uKCPq2
3+eB4iHxbigGkKN6aS0KpqLKK73+OPUeqGex+PVzCZUtV+XxlHq85WIlecstJQVllb0mNixmkQSM
B8ZDbR3DkCvMOFRbyi4lYihfLedkFV9pjbfyQDUUx/ZK1SWs0I2BtJ7lSlHCQKWzdGTJirWcvSre
SwvWOJxQgMaRifVlEjbRfSN77uD3JKLRUTOSgMaQqhsJCAyTMo/XD5DTj0WfCrs81Q5wmx3qRBVF
ooGeNpC7g4QYocMLjjHJHISu3A01eynerKDNwF/i3hg1iaNkrqP44GXp2ENID4kD4laMYp8Tjopg
Kjbh3ipy8RpDe3z/AnYR3R4/Mw63F490XIXH5fI4/Zzd4WBhVFpKekr9e8u4MnepHc48+5wc4UZw
8Cn1QiyAdas95RhXIFXNgVI7miRQRRB4b1xKbpY5CDmPCwPQASFEZyDsUaAxdaPWU89R3ho/hyu3
DBYNh1fz9KKqFNii1sQGTKFYHzvTlMOJoTpQo3YnDGYE7EyhmozDf73kUqDALsQ2l+PKsYUNt5a1
WANptPS7UWx/xdrfsvYT1uJ2nwJ1733YQuEmaCj+EdZirZECG7eooXy/w/AvYwulwa8R/xDH4Q+1
U6CO/YD132TteKwx8qE2S6H0c1Mo/RJsl3NcQwql+wlrf87aV1l7jLV/YuPb2Pjz2EJheY31f876
h1g//qcAwt/RUvgZBj/P4F9qmT0QXslx57CF+voaw3/G2rt1tN2io+Nxr8HxVQz2MXhiKqVbmUrx
a1Ip3o8wyBRk7VOsfYa1P2btz1krj6N8DqTR9kE9xS+GNgXOz8UIP8xxO1jr1FO5D7D237AtAP/o
6fjX9FSeY3oqT/l4in+ZtSfG0/5W1r7H2g9Z283aPtZ+Np7yqZ9Ax39vAsX/mLVHWHtyAqW7gPAa
jrsxgerxGeLXAv1ESvcSa3/N2t9OpOOGGaw1UHi2gfJZaqDzFrPWY6B0Dax9ktH/gcHHGfx/GPwR
gz9h/IYNVJ77J1F+355E6conUbpnGfxD1raw9j9YfweDP2St9i7a6u+i/fcxOIvBmxj8KIN3MbiM
wc+aqFzvsnb4btpOmEzle2AypV8wmdJbGf5xhj/I8C8w+CUG50yhdKunUHzhFIo/i20hnF0Qvw7s
kE77H0yn/RvT6bjHGL6U4X/G8P86lSN542dTaf/LU2l/ZCrt105j9phG8fdMo/hchn+I4YMM/yeG
b2P4txh+1nSK56dT/AMMXsBggcGbGLyTwXYGf2c65SMz/DMM/yeGf5vh/8bwqyDBpgjglwyK35NB
8fsyKP3H2EI8X0N8EcdtmEHhR2dQODCD0jXPoOOfnUHHv8rg3zG4jcERBn+K7Xo4+8yk/DJnUn65
2G4A/2G7EfL8TMr/7Ew6/u2ZdPyEWRQ/dxbF3z+L4m3YboL4xvYbHPfELOr3n2ML+aKFtW/jOMgr
F1g7yPilz6b8Zsym/PIZvJrBxbMp3Uv3UPy/30Pxx++h8fEXbGH/+ABb2G/mfI3iC79G8d9j7Qls
YV94g7X/G9vNkD9Yf8oc2maw9kHWLp1D51/NWi9r/4217yEd5EcNT/VKY60Ozr2aR8Aec6ncT82l
cj89l477AWvfQ/yjHHd5LrXTDdZ+Npfy+ZK1k+6l9NNYO+teype/l/LNQtgCZxWEt4C8DC5EuATO
7WzcVtbuvpfOW8VgH2sfR/xWyMP3UjmeZHiFwd9jMD44/27W4q0hxlUtg59m8HMMfpnBhxn8RwaH
GXyBwR0M7mVwH4N1GgrrWX0wm8E8g5cwOI/BmxlsZbCDwW4Gf5fB9Qz+PoN/zOBXGdzC4NMMbmfw
JQZ3MrifwYMMNqRQmNwtATyPwVkMXsngAgZvZXAfg/sZjNdW2P5fUEsDBBQAAAAIAGuGWCj/DvDB
HUAAAIfUAAAJAAAAcnRsODEzOS5jzFttc+LGsv5s6v6IyeZDsAOYN3vxekkdjPEutcb4Ak58k5tS
CWkEOhYS0Ug2Ppv89/N0z0gGjLPJ2T2VuHZt5q2n36e7Zzg8EHEStGqNk4rzRnTESNrBRN6J0eSy
VaufHNKIuLBVInrJXMahTIQb+/cyFl4Ui0s/TFcVcXBYODwo7P0Q+0kiQ1E7OXldxq8TMX0U51Fo
B644k86djCuFwt5k7iuhIi95sGMpFvajmEqRKukKO3SF66sk9qdpQm3HiWLXD2ciiQR2F4mMF6qw
F3ncend1I67TaeA7wMORoZIl4YdYsoxim9YDX+mHhEQsPXwOHVkpCPx0gkBERI6I/dk8URhXMr6X
bo6foRGfiMxpZMeuElObsIxC3t0wiJHmz+DTdbcvpGFTYc+Z+0ulIUphp8kckAy5sbSdOVEIoMyY
f3R74/P+uDJTnlMJbWVXZtF9SWBF93BY2OvKELQLEN5bOTIIiBTQKsZLGx/O7cRmPPohsF3YiQ8c
x45Ps8AuENyNXClOGtXKUUm8i1wX5Ji1FwFxQOgNMBhLGU5lkIjBuahXX7+uAf9xugRLE94iXbrg
rRL2ve0H9jQAZSB1niTLN4eH2A7y2yTiMCAdOdQMVYeZss2TRUCseYC8ZVxO0pDlzBCXcXTvu2AP
JPfBD1UCct6quR3O5v8A54JE3lWcaFFJHr6rFKB7UD7BUqMdiPY5+NoFjWcpNC1D3gVEVlWVgEOO
cCJAFs7cjsVBtrBdePVkDfe1SrUljg/rR4dQ5Q09Fv8Zwf8fvjplbDvCkw+k9HEZaHj+LI2Z8ns7
SKUyBiUG9spfpAsh7yEdJYqjlYDM7mSiSlAzp7JPdgG2uCwFQToFpQA743SZrJOKTmjeysoHrYco
vhNtSPi08LUrPT+U2g3UTyxXTtOZ4N/r6zeH26KmKclwDNPFVGvoIg2whjwGWA7DUtAW4On5Aalw
8R7kjVZlOwjK+cx9NsuJtirBdkPMEbY4bgoZyAXoJ6HOjYJsGGLul7qjbkVsU51tYen9rcBf+AnQ
b9Q1/jcECegtbaUYnJcCMzddBnIlvMCeaVYT2IxRg86tdXPVn4xFa2+PWBDBj5EvM6om3ZLQ20Rh
8EhoRksySbWFm+n9KYf3M/D6WK6VxMv/fztdh0C4WhrXPwuFaB/7/5LCOFM/LC/kIorJVzoSqgvX
GM426B7dWmc3F9Zl78rqn9/uNfaY+mq73fpQErV2u3aMv/V2u1HH30a7fdz8sHu5KLZqJ3Xx9u0W
yP1tpCYruN6UfN009eDBlSiXIVKo1pQ1PpCkZkVX3pe/WyTpt7Xmt839DZwneoNx/8feXu2occx0
k5ueaIdzbcf2QkIxlNZA6Os8gpnDmUwfyc8lsR0qbB1rNSHdxOYeiZyHFr5izwGpxIna3vuifzG0
Ju9HvfF7UT86Jn71Qw25JGKQRl7OjR5Cgt2o84gAZgaSdmzQySgIogfCV8kkwV/F+hZEM6teZGj7
5eYbIaqiDcM8NqhXKuIYUqnWm9tiXENrr8lShGvRLAZP72WQkej5MRhM/FphTFvXGpzzQQfsHY0n
BkrmDGjBNMXSkvim+Q0xE8QbrDYZtA2hawdOGuCEoaOxdvz2LTxizorhUsZ8uNkB7DUTHDQFqpCq
FC7lkfkSRuzXw5lx+MRFf8EH5j99z/OlyuiD83WCVIcY81yiSaKP/nm6ZQFAeNIf9IY3EyGKzYP3
P+4XCl/7nvhKj7tFyxpeYwa0zbL2hfj1V7E+9qE3uupdYqTwNWIf1j/xf1GqNRoH2tKHb0voIPPo
04OfzBkthDQwytxhfLW2fCwlTwnIEHDwgDRjOypKY0cypErhaygwYondm5lYh7d7VR6+oumh63tE
G7NHirf6TNNnVWX+3bMRc4DqIQ8ki8Hw/Oayt9b6vjca94dX42drF5FrliterzffMSsFKTwhUPLJ
Gw/Prf5V17oZ96zu8OZqsjFy3tsYeYGuOzpAgl10KQrTdg4k7B93jCRQtXjXAGQQRrsG/IiOjV0j
C+h05Oxck5/zOwaXjr+rG4ckXCVC5Z3Y0TH68rC6I/+wOWKrxSFiNQRBKiKK2YKvsw6RPC4lh88O
BbvCRqQZ0kmuTWoDytRPoqV6Dt1nfpEBf2ARseLCBUz9wE8ehRY0XKmKFmQmi0XEnvTcRvwo3vuh
+42CMxp0+x2OnOyZNJEG1B7/+Hz2dRhhDm8OTLQ+qMyGHETP2gnlvu/myupMiqt9Ucw8yrcCTeMP
LvtXN7eWUXjo3nlPvBXVVb1aqzdyGHCGiYXgzYJPt8CAIlxdiWOmffG868ksdoNva/iNkwz+HqRt
aXlaFDIoIamHoweFAEJt2dFVbzKedCZjglv/1G56s6Mj7eIyD9ftjM7PbsZ8jL+L8VNiztJpQCzM
fHIJZwOySEiIHTXMHsF+nAXslcqWfmj9m/qRatRZQwzCAGuNb66vh6MJYVfbomdr+I+SlPMPVN1b
HtIhC6pfxP997rlb7yqJi1GvZ/0w6k96+6dbCPyB9bwmx+qrNUZeW5CH1Tkf9K/2c4iOvaTwl4dv
b2+hfIpSiOJ+rh1ZwNA/HAq5SnJjy9RW56zWZDjpXHJQBKpb1QJn7/jBUooAcYLkR22h0K+IM8p/
kUSu2V6hoPNkVrC1dNmVCmaOqIYMn/PkzYJCaaOTCguFPICHKiQxQh061Gk5RFgxxspxl690nQBG
bnMC5QQRqNLZORLtQj/DtayW0vE9hMlZwFQo6KAkQ1lHUFnypXNNdgOPyEcXFFxOI2gnOXNyL1BV
8c90saRAMZQ6FkQMCuhZGsJYVHQWY4Cc9YdjHKtBgGCGuELzGI3+1aQjqAeBDADZorjkCgWk+6gL
E0iLKRAkcvczcP3R//IRXylcRYl8k7nE7OxE/hcHviSu26GoVRqV1w3ElmxkWRKMJJpoBQ6F/ADR
YUOFuAf2nWtJRmvy7/dtStnEiCIOE4iT+GWeKlDESqIBU0FWOENkQUDtmJOILLIEwHmGHnEM2YYs
GKddpNoCdQgJd0qli4TsRTmxv0yiuKwzPjuGHiQIhSAxsLofYjVt4FEsqAqcg8lfUiz2ORhUWIpl
IFXXj0BELGegqsS1DOqaRxwOLcmFo73gyQV92hFToPR0Zr0RP8wpYAKdPk8EYEosaZdlBOlSWkpp
pD79kG2HjwYtOmCWge3IUoE6XRnYfOhQNq9nEwkPUYq0w7Ep7U05YXbjaGlAgFZOMv0FSdEOk+Cx
VCDsuf5GYJLIiQJKQpw7QpBknlsiYGlxSn3W+YxeyNU4CHdaoTxrTeCTteqWEarnrwCItd2DaaYx
LXkSD9NInKVajlBUWKoU+mSlKklDilTBpqntGpxgzRFMsERADI+ypI5yIPCYYwWK3jWFBW7r/Lx/
LebSpgMDavMQwS9RiujasU+BAIm11tR5VFaJy+YvJKL7AmcLdrAguUN8GQJspmuWzSrBDWhrHroY
VSbGfQ++jbKyIuzBVIQeHh4qmzWqQyfEP13w+nTZCPmkc3j1g/1oKmT9752K6MWQjV2gWtf/PFW7
dC2EXa/KD1roAtUXozRhq4aRJIiBiFoSQQQdjpeBUQWQT9GQSRhMwUrzkNkR+Hcy4HrlekWOYy0v
JRsUJnAmKOSTtFnbCawUKs1nPhJ26tSJpMYYfMQhw9MUi+Do+OAAqs8l1jQhYErCM7s6PqPliJua
PIPrfTJEjokY16L6jKJASXws7NGBj1B/bPWH7VpJ5M1Bb9Cur7c740lv1G6W9JLO+fmo2q6uatW3
b6t6GnXVTFftqatuuupPXQ3T1SgVuDITp0jTCDPftfzQiwiv9TpjCF07LeylteO9e5zYUYyJJXMi
8UeVTtcG0Fobyz9aC1vdlbg6pQCNKkF+ZCn/XwTbIGEO5oPiAWtEbb9I0wg1nIElkTUwzYM33FqE
vyUOCPAjcMbOAJ+iUL3Oj3/RH+hQBjor3fIQyjpw26fEiqxKtQU4ryJqpH4Pp2x/YLALvQ201udu
YbgTQTIhfYbqkNTobXwHDWdx2QQkFJadwKPOi/vC1zZiCv1nmQ5HML3KU1VvhwLQ52Qa/PSzaBc+
fhSvtsKhzauVVyVSflIp6ZQoNOOA6Xnbw8+aRveHv25pN0+GNm+y+zeA30Zh+3bnOQqNLRQaXx6F
MwJ0aBKAHRi0Sjvan4fBeNCt1Wu1ya3o/Ugbi1r1sFatiuIWavs5OrVag9HAqtKO9ueh03EcuuUY
XN8eVRt/HRYX5XqralgxmC7V1s1fdqdy3eWPL0mqWm8e899qtfF3QOrkv4CU6yJVCQUhd/xFOdb8
OyG3zbmjz0euUS/TgZ3tbcwuw6k4Otp/0QE0pMaj3vir8Dj58nicIdJC2E3Wb3A4Q65ThmPKUPsd
16z50nSmGp9q9S/G5+TL49Nz/YW9+rQSd1x7iezjZSY16vS3WfsS5v/5SJ18eaQ2VZmx2kDoZdbU
bZZXrXr8l2BxsoXF68/HYpROHyfSmR+e2+FSrsRFr3zcbJysabFR7k25fVKJjrlNoP6GOJ58eRzH
N6NedzgQvetys966FcZrAitgNvijx1utOnVZtoDx38ep84dOtS+JU7X0W4nTD7oP51dKfsgvkAJf
6QqsuXGn0gpXcfX9hc6HORM2KTzXOXW3PUV2wYs53/34vgNM+n3rtvv9qE12UhLU1X3fv8776rrv
8uoD+q/eUVdz88kAsLeAQZaTUIK6DrikmznQX9fBbW24OfYXLCSmZlyNpUpMJUNl72iEmnNVLZRU
0tSp3kY9/OpmYNEldG/cpftnEt9V/o5lo8KVV7eeLubHj4tpRI/PIs9TMuGa3eYslltWc8+HiOWD
TrfarmqdoV1z455DY/ldnHk7w3AwfVRtt56mD/InNvpVi541WY0h51TpakbJzJ2YO20qDmJQFC+o
fNeok8nkOO1nEBA6xrS+/rR+s9BXtAMV6RIgwzArR6uz1MO6BgxktOrZcfDYDRPqaOYdGjvqO4bQ
u9D07sKl5muagvXXSUzNlmkSLtTuYHYf+fbAVnfU7pYENZ/A9UqEepdr+Wg3GYenJlV66P6fgDVb
uaF2xEyGMraD8jKNl5Giml8a5twcrQa+UpIQbHYzZtSbVJ5UpF9UkXmI/QTLAmkbie91vdlJo3mM
RUfAQuNA/DyqZS0qLB3VgdJFYKv5SBKKR2DSu+trP6SXfNRuZW2fkD6CwyIDHQ/61OrAKoKkGxAz
js4AidWBWEIdXSqrjtPFwo4f0T6u0gQsPht0yUUc1zWss8GYm9iZqo0duoIneR0f647L6w6Pt7Cc
2r3VEnqEwJA6SSL0dip0IyeluihcXa5L+novlr+kfmzugeAql+uXCppX9AplMhgD4GtoG+BRh5iQ
IQ+odDiWAb16YLaOGfnXTZ5HqiO0+LlY2c2e0PHDx5FBRG8CMjqvW7QWPOWGQw2npN+rzGC//OqD
LzLip2clOT25+2ZrNlp7RkoAO8bHEfwNMa5G8kZz1QunaFZb3JxkzaZR6t5imZBcyH2bQ6Gf38Tk
JXRSspJI+WZg8SjogRBVr9H00kCE+k4g8zBPxpChhZOrF5M2tKpVrmmOSf+jNGHrqJJKjFbE7eG9
tgq2GIiT8CAJ17mDRr0getDUkY1pqETbZDX8kNNluuu86IOmjnjG6GVuKUNusnofqWT4ECreiBCc
rO/dNF20ioG1NMbYMU2G3g8+tO7BLK2auZ0pv7szq7NeHP+xL+NLbGfA8EiO2WgLM5h85lhz3o1W
1/NHRTc9OWqQYxzZrplWz/h5Zrv6SCD6q5qDo5SdYLVa4+Ykii6jcMY9VXZz3VHXMI8yfwOmQ9cN
uo9ZqrHUjK0a1vK5px/PCvN4du1JlBdHi+ySlavzdHcbYCx4FOma1W7ZKl2TpXSjalPoEt6tKRlZ
YK71+GxdYnz4AV2sBcSXvLvLJ60ZajF78rEnjtOgV91YeA5FH3qePhaq1YazsZRGzZDHQ2BDGppL
Li4HMwd+av6Mf23g+REznWnjxJXNRsl8dsxnb9poubKa9bdoDmK5312jP7c2Pn/Omunamunamuna
muzzb6aqzgXmpxDUv6e7HLploPsFV96Tb/ip9fOpPq9u9HU5pE5uWN/W6Ke9s+x158b9BBy1iw0s
c0+xVXcP5Sqx9Dssc+1gbgDWWzEm0zlB1xyZcBh4XufPa/xPOzx7q8K/n8b5TZVF0bT+eMreW7q+
LRSfEuT49cMrpinfmdFKYytene7p15cuMq31C2FzOY2Aj8jjW9m75AUoyaokXD9OHvlTsuILqHVC
WQupPw2C0yyAmvND1l9SmUr+QgHGNHwzqOx7utvWAR8hQkSFSdkPy3xvbB59H2pMSyxKxe9Iiib6
MlxSdxbNOSAM9A32T2sR7s/PJHKAeZi1OcnEfFvvbjfYoRfHK4tu91+CqnL6t4CZK3ijfKwZ8LAw
2dOn+Lbfz5Quf0O+Nj8hv+fLkv5AdzpG3dccomQVkjsEufZo+k3NLLxYe/SdRynsFxGNmFekm1D0
ZCuInDtA2R6Uno2TxKLb+jdNrXmXFK7zS2Xf4wGdpOwAvSC9rvM6Xjnmy1Cb75tCXz9p4DmCnw2+
AMBgpkGcR+E3CWkVoly9lB7nvbSU5+VrMzMLORqhxwxxNMtzE/JKz1587npg9Z3gB1a1o4KeZ3Vu
Ju+Ho+KrzS9WvDXfh9l1Rf7dq/3TbDUp66h/PQH84val2stfWloDgFhwUDQvakviVa38SliWGRtP
Rv2rd8X8Sf2+eOVvL11To/9k+e4vJpR2zXz2xY1ds9ipZwPZozLzKGzHtzig5GHx+bXq/matQNqu
JSXkvSg+uwWGfrGV6Bb1W4EMNwEsXD+yCMqOrcx97/yR77bXIT7BuI98VwPhTOtPQdEt2NgWuIwD
fFoUNz23i/TrpekrXoEY+nfZtrHGh7Wyj/w0p80K/haBtYImFDd9ujjg54Z/FE68+jNYGt3i23i+
OudxWmL5fBlOb3Wyu+2EKhk4EOj37s2dAMn0J0le+L7lR04S7JSq6fNxyv2CvbLr/IX7BMRM2XrV
iskGjZnpV59AhV6qibRR1++FLCd2mBFQ5lkyRxK2ebjtUBF6rIvDEIHRC1Sbr3xx+ELHexAI5msQ
SDd/CKCXKH28x3IR3WffSjCPK80DePHsuUG2WRxFQMRQj07RFlc3l5cmyXQlP1Z7kOapmSvpIR0j
Aw7y98H0Exx4+H+X9+1dbVxLvn+LdT5Em7MgapBAAkyIMc7FICesYx4DOFmZXI9GSMIoFpKilgxM
YD77rV9V7Vc/BH7cc8+sy1qJ1d37Wbt2vXftpD+kkY47fOTjHAFTXAeKxAWxcWjoHURetqI2AiFa
fdhNNfSIqPYIBs1KdHPVa19JTXAfdIEWbrrU5c1VdxB17kjO1CA6IiCYrwYhUbdnQwYSEQ+MWUf7
B8LECCZo5xQzXfohf9Sw0VmcXFdjbd7qzP2lsitaaV4ilIzgVlOJliM5WGSUd7MlWoivkGqp7mVU
jp7hPeKWqfcuJDoE6pZK4+5kOh5E1cYRscVfUBorXt72OnvJ9mjvzfJyDCEfgUORxAeZcCDpHFGU
rQFRwEH3xjzQcH0ZHUEw4z/x0iPl6J0Ha0Z62UOQTB+H4cqwf++93T07Qyzyr8en/2g2zn/GEZZz
HN3aqrjhuQCcRQuTxQAomHjp2Q7wBFGxzbN3e3uNs7M3797ylwtiEh8xNjMOZj0SnQuW1ynnw9p1
zJb7XxpH+8enzYN96l7AFH99o7RIB3sNaVTKxAw2XjUDXMYPG+xj3r5fscFc23YdaC3RAaAuX3Fo
a0ZNHs3iIh9zA9ou5hTuBKFhMbXItWYU5DE4uCsOFI0BQ6zFkRzRkrNDpFdOJ89YgixBh5z0BtMu
A+YvFgFNLDtA6Mfhc8deoBQI1dJIyBWeGQOxlQtWh1e0JOiLKh2I1AgPbqqq8HvtPcHov9el3PhP
W4jRX2L06QsoPiOwbgS82pI34z+bYAr8Lg93EF36KO4I8hwcnTdOT9+dnDdJJG7orjAdxIU9dJ6E
nqWI+3i9e9bgaETaUM2a6YOnlQaW/ZCBUDBvFRxLpQdDH3KQg8MPqR3PZRZHi4uMDlckxDdFzysb
oTHbggYtMlUMUQj8kpR6Nm6wW4yo8wtEIctx/HGLdONO67r1gdDw197ghy2OtTdK4ldu+L3jw8Pd
o30FpFJThqRHXRVm5uk+b/sYCH0f+1vMVCFq6LUn9L00InFx8rGMk4KEO2+Oo3k5UQD+yscJcLQd
0d3dAZyEHMM+Pye4QGWVRBDDXuisLnSeRdE7nNfnk658Cke6XthY2bitvuJ/Vv73YL5iWiiATyGP
CTGYhfTPgrdisIV4umnGP0cbQvBqDGnRmFmOzAkQFRHXcUWP88eWH6LPCER3Nt7rwNVDHOsiKh1B
mPWgffctyMjb3fPG0d5vfPr0VBFTm9ctrsilL0mCWF/T0QQ4dXR8TswMWAV8MKVZF4rKe2/enscw
UQlGMUpNBzTkZDjgoyn94Y3gFuQzOVgDm/HmBk7itD8mDpcMMgWDzEeUp4FBMSUFiM0NaflhTv4T
VIGkVvKWdXmZXgCVVPTyZb0fo1r0wgljD0WRy6HX/4mBy58Rt2x1r5TIBoMVBsqRyxBWPRWqQ/ze
Zq6gWZeEcPaBZHcRLztRCFMC4ciBuTBtRV6ajFTs7VX0rDE1a3snnHKZD3602Qvs9/cEx5oRfp0a
gmwRrwjI2E3+iJeXRaiYyyN6C8l8xQycN6UsLCvU5qBqmcFZ4895LbyIFhLG1r/3CZA4PLVAxIvx
M4rEEgczdx5jkvfW2jH+kzsh2L4eG6WMAzVIAoJCR9uiOhreiI6mVjX6dFGGE8O0Ey0bBzA3hq3p
G05odr65xfRN1bdiBhQHfxPctwjMm0Bwlj97Inj2sOHpH5Uty2UoCkuxZEag/7FsFMe/994X9NNb
/r7iG3F4u6R7eG57UHjPL6ytrN2+mK9EQUfUDZoICjFpyCvGcP21i5NqLWNxNaJD7MdURHzWWA9L
Jx46pyo9Km9U3OIb3PIkSKCZEQmN2Ih3EB55rGc4/wIzgG7v6dg7v/TntMWymzvBhBFORtTCRznM
XcYQhpdl2m1xJfrpzYmmBSARAg/7h7uA3XX3OulOypMRo4BXJTbDwq6lVrFn0QHNx3lnsMgpYwBV
y7EP8AeprmCilwZg2/JByZyyYPrlvWeKp1864tJhGL3p6fE6ovEDUtyJDMGmf9v+RLo9ZyTaH8pO
6rHqzubIWC0TANONavwohIOsYxyV5OrMtMbsuOSGJq2PnGBmSGvQvmJWJkBXMmSjnSweEO/2Q56E
TaoZsaK2xFu7w+gZO8B+UE3vSngsqJr58NKsE0Pn6i4R3oTvRn8vGctXItELO56JlMkZD6HueLpX
9tmORqkxKU1/gGfbMHzT/+86suVlbHt62M7IA45YYn38SAhhjy2bxQdcP2DvPgW9ugv5MIsjBl6s
OhZIt+j5aJjuPJHeSXzdTZIpH/E8++0wcoKuVzaQX/2N7QOiBgBU6yJSlh4iVQLD75wSCNh7Mp04
Gt+Dr3AGhd8LKLyE/6B3wwDWcxmAfP7u5++8rxLUE4u76LvT73Q79LutT6oFQciKxnKiUmxcxofY
58FxWBYHKCGEDFXSzh4sjLL2V2ZZAAXPm0GQMEUW2WdDxX6M6sLdpbTv36LitnT9+bYufrpUbJbD
+qYiTiHFfAYV8sUMFhr8LEeetPFKhIfs6PPLG8kkVV5AULAlLPCgdrYlQAKuwmif63o8zeKc563g
De2hWCXakABd2d8MIudF9OCha3oqpNqdZYettScHitkuLGKl5UKywjwc0FNqcNF39xjGgRBDz9Hg
F3NvTeFkMhz5Jdi2bz5aC7tfwr60TdAL5+1iIzgV94zmpmBnKA4BfLbegW0ntjOzepj7GwdfdseE
RlGjcXJ6fIjjojasDF/1fXNvMu7zfuAvJuqz0Wie/Xzw5ry59/YfJQSvAOCmpave5UQ2WrrO3hmh
MAJavOJMISQCIV18f/d8VzJDoNJauhILEL1BuhZXaNa4o1r2Q50/rGX6OW3s7uNLPbcbojXpfhpH
ryEnIsqJBA+eXcyg2+fj6RfdyU2XUMg0xQjKRLfHUv+KnPgFax63Ij3SnvD56W5HMgmtrx9e/Rd0
Nokx2tzEI9If2iOXPTSz5GVVEZm0yc2VY+KV/XJXhLLYxvmaEYmRAHtB0oRgQ7T6N627Kk6pE81k
dwKtfT6E9w73S+Xnsf8BMOT3pfJm8KFxCgMb1/g+Dr2pX+AgNQ6H3rbnTiAM/9TqR6K6ckvdlDTq
mMu21BdLwjUENtMTrFDeRGCl90R65Tmy+LD/8apXTE+WKUkB/72IvbwzJhxq3epYUxJzG4NgTmPY
oPGavqE8vBIlolp10hZQUyZdtnNZjMp1DLsXg+cEu8jwH38S96aRYBalEI8KKwniW1LwSBsPheDJ
lPXgUN/k2QeTDwfzGUMoWTQp6y8CVT3Gspd7gwu7WQiMPmGw7DsNikdnLKzIHGfgxdf912q3bXQ6
t5iDTUq2ZahsWtHQnkSIN+FP60NXsmvYBAUfppL7ZTC84dapyinwjZMScLg1RoFWXHUXe6whsya7
bFUivEn9kKQC3O3h/sGxTZmxIumgcAhDUtcxwVRBi9MkJNHayvOIiJfmdiFYcEFSNDgeJjGp59DS
NdGeC6S6aH+sToZV/MuGNuTjad+1+12Njr5B/gUaD9EFpZ5INAFvMlqZH5Jcy2OgHuapi8QkBbWp
zWgOzf2DU7CDrVrqNdb9+N05s7acTwdHIQ/hL2CFzEDC17zzalHZ9BfnfK67z4SJwRBiR9tZLnKU
/aLML5S2K0llpyo4/1qTnbbXrdHvW3xIxQSwu9h11otrfvC6Z8U3Aezy2YauUwUTc312N2iPhwPk
mszBJxjOxpcIvUO+CxA+LDVpe5xuyKd4mUCVhBoWXuBN0JF8jzSQupEljLyXPNhWvGaseJkmbP5a
3Nv1fKTqg9mg2JlfH7ODOYbTFvOCb1lZNqcYlIVhqYWDkSByucnUrMbkTLrAi+d4Nr1Y1udxSwtY
p3MSvV0nsvhXSYgHhxdEnIQ3QkSsLC8MCuFxHeuat/z0ZbRldG0PJc3n99GPc6zS35QzEy2qEisb
I+g7dAnW6bNZbf354wzWQDrkr8FeNdZbD6VkR1sW+1RMDKp9DkLOlQy1x9wnN0NP5KwgrynaNPlp
iLr3kPjYivceRH4oYLq1xybxCIN1lQmSPkXNYbGfuw1Nl69e1WNWvGHq8R0S3yQYbtr9+p36vFbj
5L31zdReXVvnF6bTly/rW3jB3X7jnYomgm3KloLCXYd9SqtyU+axVLLTLay5bcnCrF2b2raP7Nj1
+lftWKX0L3wWbdHuc3brF2xRDgDBeTf2fYj6l7MD1750A37R1uFd8jePic09FuYqjrQiLxjgX/Q1
tsb37Tk/kiqzh3yEZ6/BJRgXlFNjWvSkZ3OOzLcVykmz2HrU1MvRG/9ZNn6JijO79EwUZyU624VG
cfpvnmmKf6p72saf7f60e3CkhDeTRde4BTSYP3L+Cy+ldrTkH6H1vRlYH1TXQwJedS8N+DKRkHQl
Y6Kz/UoQI+cZDRqU97p3wkq83eWAhP92W0tmfJNc3jcBNk5PxQK4Z4IXeeycljpa6Eh6uSBPeq4R
uuLlN/cICXubDxuHisKZYOGOBI3yVkMgTcQp66xBGhEgJFL3kisJ/xCsSrPAWq0W7EGdO7OxDI4R
lTEYGFuvrAkOy/oBN60fUMhIyqnnITHOOdM/PTOfQ7jJJHQlOr9dxfEbScSdmGgCTbdOE9NU7Mmz
cJvgQCVRLHO2MnfHoHS/XA4znTPLEg4Vpp3nD3XzwWYkf/lyK2Znse3AHCp2PZynyt/D4G8OINp6
5149RUgEkYDMhDniiWMq86/V1nE2rma2YWjhTpmOvW1jvBlgLpKcN/CBeY6+jBvMRZiC9xDDfR5l
3FOBNfu53VGugvFRMQLJgZ5VzrUGTKV1ZuYN70vE2Ggr8pzrcDVwE/gp24mmkCpV27Olahs161gI
IVQv2uz1zGaHvZ83u4loWUgWEnMYyNw04cVYtaak2Q+6H4aTHud4GLXGkwFhrEnq4KKqPEpgqgeQ
IoY+Px+9MN/S0Nhix8s8geIaWVSoJB7kt20wPXWqgEcufNXqX9IoTLNGyB4+wXGVbRZHySHh8tng
Qo9WOuLBNqs75lNvPGlOhnAjlz1yHlf8XfZ6emllKngkLO37LsFpMr5xxyZPtVy0X64FrcjxfYzM
D9A3xPWz6Ik6KCY06jtVO4UF25Pb3kt2oggK8hQaQu4QaP9xgJPctlbC5gVD+a667kuEMF47s5uy
HOimYbqj3PTgjmzzgzmuzQ/mdDcI2H3EJ7f53+N/8Gd5xGltb8IHmmTByRx5m8ffO/uN1+9+4s0T
SFyxaROxNxp6wzuIN9BPJ9FJb5BEHBcS2b1meWjIQo1J3ck8AQuzaRNiU/fRHWFxS2UxiX6bDKPk
pjdBCAGu+QDfBd/DMWhiUi25/WjUHV+1aP9JSYk/0AyxrKhMcjyu4Oty2GiRiT9+Wk7AR1a7t6Me
gkh2TF758hpfLrFar8Ua1LW2sgEvlwknMTXZWklsJDjGFLOjzCt1OR20NZrLyotyjHauRGDMG53V
SmsZFTRoIe8AlSdcezK3J1SbtzGKb/+zJHGOj6FZwNO6WSP4bjvd9oncTnbFszT/dcont2MDNTzF
znrWTalFw++yDK4eMDjDyNJoTb34HuwcHig/tvP4XZRieGl2xwbRvy9IFgCP96V53fByNrt7AncK
gOyzqtJjjKr0xayq9AizkigRTwKXS+A+TJOB5ThYE5j+Aup5xhE5EOHKltQe/yN2iGDjfoqqmuXW
gtmGMKj94RQsRagUi1T56ovJ8HoQ5HqPLoC0SP6gnSzcFukviRuUp6iY84KOJHdMKKaBnMZQG57J
G8TclFGVHljUl5ADiKtrS+52HbAZS2bcwUvl3ThdUvM0RTkNruKrf5gZmSPEnBJAG681yoaNjUzi
Zaaedclrmm9VMgFc9Mm0uxiFmTBM/BWz7JykFj6u8Ri4dNBRtCYvfWL1878TI+DXErhU2EthFywd
abqdpoblVGxB/eCXlaw5pmjkysqHTNF2UdF27iR1NnN2RjkAN+HrbMakCbaJNIGA5gBftg5yisTR
K5JSBIaoOB7ebJtVs41AN7r9nuPl6DvscVzGDiQsuO4VXJtVsO4VrLuC8kJmnJoiPi1r77yaNYXe
crAkDGZJbUI13jOh1HI+jG3jHEWlY/AxxmvHG0h1/f3vQdX81jHf5eWwj5fRhkH5mfiaWt3qOia/
bqqyIvjIqj5zSyaVAty7vb3NHXPesOQMG3Qqs9lLBfsjyluL3P1RiYLet7JF2wVF7UBTmLFu8WIm
ZgRrul6IGQW4ITvQxGw+2HQBuaL/mrO0PdWggMbzlYVs5pb2R2Q8i0ZWLyjiSAXCP0/UHO37nE6B
aVasyR6ICnr2eIjxMEvH+R1Gx5MrL5GYBGUSK4aKJV3h6Ux5MJ6djmSSPqWGNGNEVnnLea+yhWkC
gVWeouwl55s5HejDemOO0d2ClZqxUJoIL859XedeH+ZmqkR2J6NsgdJSpKjMTN3wz3MFqHBbcU6w
XEu0D/1fd0+PDo5+EmnOZnLU2Tj5TRaDMcqikOihT18hNXY8BXuKdiALzPu9hO0doZWDcyQ+auaQ
MPZ8iwSbUjB7vlaBL5TFxU3sh7rhFAWI3LgZD01eK3v8BKAz+ZdE3JTbG0i9kWxO9nnBnmALIcVU
TvM/se7nckCNxJyLoGBSbiqRVW9gZshYzj1vSfosTXq3helHF/hK0oWtla3blYWkYD0r4c62+UDp
d29pwy0gOIw/jWjBHxjmEZUFXLg5J3bTKSCsqisGhO5FoA/6Wp6Fi+4HgY55eBlt2YcAPvNKIisz
tXStGXujnceaGuz8Cjfcv4o/5lu5Yx5RgQ3Oj03ui/8P3DfeaHyfTdZ+XPqrJH9AKXM8g3RPkKBz
e0u3CpiZTD7I94YEbUHitQqn+AH7Ba/4Az94of+QhXYkiPTnYPPicOV29MfyckibBCNKrrM/EEmn
9EqzwxUTASSLKwWfd/wh7GisUBoV/xBUFCGdOsn0yAcQ3Zh63I/sBDZd0kvqE1bNRdYQShbt+D7w
9D1cRoK/7l63R3eet5fx3jamP/VoY6mU74uwNUM82KUfhoRybXt8KKcd2+UjbayaC4gsGekMuwk8
zVdAJ/YxjVodk1+D+zG8Bq5DQnYzJWifjfOfm/8Ol/qPdqZEtM3bWMXZQs6AIT3ogtsV7uHtDd96
V07xLut08xZWDpkF5sp8fA1biv5CiPHdCGmAaN9MrnTGnvEo0J6V1+o7X70NP9uzXtZ545mbdowt
Sukcn1dZocp8TXLC58X/p3pu/JgYyS7cw22IJtL1VPxnRKQgjiUVmh0kVz6y8YlEtCHJk98RwL5z
YT2eTD3njIAzUpt9I5G6Z8JnsgufYU6PkqpHJTF7FC5FrOyhN0se6OWie5H83lvyQmJA0B48TaTn
RSMln5/d7Z+nnbAMrFLSa/ZqtMQzpndvmrvRJbcwItT7rdGIDyLqFa18WvGiy7enX3TZOcZZwhi3
WpPhda/dTG5ao3JdRUPe3rFExJsbj2POE5bg+nckCnO29sx1ySS3lIGTS/Gi1xqbipytYrbNObQ4
F5ucbeSOd0LP3VSPbcW5Y0ORnQEq4xf9IkDLgNt6SK6oxzWYV7JMMItBPoVDZvmjdFDMI2dxSKmb
z+H4m7AUyyc/l0t6bXwWn/wGXDKfR7oBmcOZYz4Z0orGOCSA9KwcpBzxh2oV5zuuex+u5JSWnzK4
9ZEGPZgTPdqwDNYn5BYBnqfRViXU2VyCOeD7V5UOyiH6syHnxkMuYzlHj5jpESkkXc9JJVbbp/Di
Ui4r5oHN2HG0SpYJe3vTkEiMNv58qQD78Qk9pwplOn2KBJBnidko1sz/DUvTcWI+5xgZ8dl/qOmI
I0AiQu+4fMqn5nYc0sjEBhUrgmZxxvkuGOfhyxWhRZ+ILLYCSyd6gyvxduhdyJiIdI5AHkBnkETT
Ec4VtS45ObJgmJTMHGLJevmYDX9WVtDPCADwGtv+ZkIDe2rF0J1NnqtlxHRWYddSUy+mV24/m1kG
ye2azd761mazGTNd2I3knCyuge5+AhFOejj53Bp0IVYJFwB+EaUgia3bj84OT2iIRNcG/o59lNXZ
GalnOeX8Fec+NZ3TPfKPDrK4lIurvIPCDhlEPFfGhqtWn0VgnUNwjGZbfArMAqw72I08b+Dqte5W
cTlBjrnQH2xqmH6MfmbI9W3n3OgMhVI9xRGPebYh+ve7nQ9df6sRERvbk2LcSzKcjnGt/O7Z7olm
JwEwCdhy9/EHUIoB5zkFq2j1jfX2wshU8Hx5DmgXAuC0hVg86W7My+zl9d1m9vIFFmlS6F1X1n5T
NvifP/W5UjFVLCCLDhI6sZ2Fv7NFetC9wUe81Fezow2KLdBuYF54hChY9069unfguneq1X2gWEnX
96xc3UO1umfF6l6DLLIh0KmYjFOpMrufOEaEwa0HGVFtDVTHtzYaMT/kg4dnk8oFCeZDVcc8clNG
Zw94rW8tso5XI/WDyuVagbZtucmtt2EKbMy+lFSSKUXPaBy3/sRQXCfnqcD2BpdYkkEayIt0ewBy
jQvJSbKB6HeB1ATnuJF+aVX6smJicOkLi2jICQB1Aqdtu5zQRgNqrfGISW4wyGN30Uw4OON9tkLg
TQtXEBH9+wMSP6wHyPBG7GPivMt5O6mu08xJzhf6erRNYtg6QPEBuEw8GV+FzkQtXYX2jfTMF900
zSzDui35mm6jwJTqIuHrBVZV/D3kjsNbwjgKxtCWL4/Mw1u+VP0bfulV16sLOLFx8+x89/zMtegj
RU3uqqm5CHXzmAFVe9jv8w0oSX2TuzDJVFPxO2m8O/eovFkAMKBOBwkW9cISwgO+Jcva1x2aWQHb
aD8vIzlIEIwzOICwLEGGtTU5apCeCYr1LodpaD+kEcvNGC26Ob16Fa1tgDkhL9Aj10L8kIOtOGbD
TQYL8T2ORXpADeuo6d0M9sHShzfjrqjqw3HvQ4/578cLCz0IojgwBP3bADFQxRVjC7R0BZ4V3vLU
kRTxYPsbJ00Zcuws0jdRsYooghFrOG5xZ2s56QJFulKphEvumxdX5aPGefP1z7EBEoPAOg747QNL
ugPsjkuAy+RtnCs5TMtjL1k1Llc8pT1aHV5WcZJSnbCjITPKCpSoT0Sdka0RM9yZkXgsdMQaFy2r
VVkY2UEu72SY3IOHUYFe6lgjyjE6WT/gdICDniTMs7CfiKELFi/ggCfJzRBWoidLKyqsnPoyQR5n
kQTbRXxl92IwHF8T8luhpFLEWAoiQU2/Rh4wwc721I9LKg5Icf5h2XhMRuSSRYPYbuvCv8YHNpTa
YJFScSruQIcynYLzHmaEMwToQCzWpNWlxwKbzMWjdiev2kPLaK+qiY0IHyDyorInYyCKcdQapxUO
G0fkRC0XK44KJk78/p4fcyPEI0d8RrODxB8JE39CyPXXBF0/HnZtaJFZuZ3ov93a6UYtZYXxYmdK
Q70lTiafM1CweOfYW7Ztt1NjX5SgWnI/SMgbi8YVKAVhM1kGGzTipmNWMKgNM3yKPRtCyK6RANfs
paoxSfnOhy7VWCn06lb5bG5Y92SiCeWziyCEzYzR5NZvX3c0SaV0kpcFW1Ldo2ebT9k8dFL5lEup
bOGLYR9G8cg1KnACdVhBmAilAv1StC7TbCnMbFmtWgvTy9zclhq2JZK8yUwqNrmJT3ndyQqn5e7U
bmeGIfqDWjWH8eVKmZQpwhAfDa2SC66LTB2OanOCTNUhJVdxHptZx0bKtwR0b3tsFPImSj/HCs60
DSAdk9YvVP0LDG/Fko8dQGzvfcixZlnO7zlOVUSTLL9XXdwfpm4HcfBcWGcqS3EtPiBOazOMDr67
jj5Mu0mi7ydyWc1lr9vvOO+M3FubdK9bA1xa5FthwQI8C8H/M59g/m1/anDw7v6rb0aW3Dj6UYQ2
M+zqBwN/3nHF2tgksFFplzxVXKTsJcv1Q32PwKKZQY8yvEoRZXRBjunPIH4FMZO8SXTHFAZ01WMv
Ey4vMgGwKXeHE+gUhmnCDEpKwDbCVrRUpjdLcdksx7LfDG9kbvqWE11TeVcXByM2Z1j23GmL3naa
nnlhif4SWclRQC8eELc8sj40sdlx1XaIFTNus0rxjIG8wV238LxNeDtl7MEZh//3NZcf3YspBKrM
c88A5O/+oixHvffBEEwkoeMEDrxg1Xq97wzhvDZTOD9mFeu/aM/Zawsvxx7RFzg+K2JbdjAy6Eel
FRgXVvZWXjCp01DGwYeEnZjKO7wDHN5UzSKWvUuP7+Wy43sLhXtzufG9u9N4lt5Sz4LGrXYIDxpn
Rxh5UvGuqgiglD6ROBM6GfnLX9fULN1cuOdQmMPoHm0thNNT5coQ1QS0qartcTuzwqc21lXzlSB1
ujnlear3ZtInUmSJDbYkjW759fTDj7GnowWxNiUbzTkjhNMVelrIp7Ejfm7Qp+BiNvIzP+zTQ3oH
GJucmG/oM1JTTtBnYL9D1AVnhYmmI1b4LvR6XgLliOCIyDE2CBDaVtfMhkK1Y47hv+pKuu5he0Lj
oPUUJxDeCwrYgWRDhUTQlfhKWK54HGy6MpR/OVqLLepwQT9fTrG0eti9Ho7vouTPabcrNyXQnJjT
iGGtQGZW5W2Vb3JIrjgSqO1ipRNcmUD4k4wQLoE7kIlprxgycnCJG40qwsn5WkGSjWCoklugWdro
jIejUbezvGw16gDz7WcZh7NAPCigOCI60gsP5FUTcdrjT90yx14RuDB8kmY4uQ9LarwYBycivFlx
mjejYxPLCvLlDSJiXr4fz8lCch6uT5qyR9rLf1QNZIBqtCGj12AdDHGEMyscGmabiJH0KZdbbbx3
K+OVL25UR14NGte2XVM5paTJWXKEL0kUyhLCw2/GrVH0vxY61qGR0nfS3WY4e33T4+wzeLvh5jn8
XABEYDSCFRK1t9tIOujbJez+hypSjyLYt84azYMT0klPfjt7d2iQs0sUvD0c3YkXf3ot8H5s3TB3
KwLVtOO8FXP6TGnmyj4NV/xGjQ3U7RuTKZfgjVkhsUWTI2mkJ0MaS0TmepessXy8iJ9m7g+2sDX2
63C2UxZZWzCw8LNB1nKnsv5athLwMmeiXocALvfdsTL8uI3j4bPVl31Qrv+5CkzI5o0Sl5sFpOeF
tBbe9WuzTBZrmN8yRJhfJhraZVPxmPjxepE6OiOhzdnVVMK7O4j85kuncG+YlcXh+U2batK2jBlh
DKv/907KaeKk4cgGTQZ5k0hOMrmTjI0o1yzrZT8qtONr/S8048824ne6/fzMNOynC9MgdjSO4mlR
3sZS7kd6M/foFHsBlXmkXyq2Eblw+QaV4qJ8XhJCBudP9H7wLH3TzL/wPTNIELnfSCWILKAOX3y3
9zeybPHlZzY1Et+Etjj+k1DlctyUlEPUDWdwKqNX4ASncSA2tbff+OXk9OCX3fPGC4bPT6okAHa4
BUnjv05+/g3rNU2MYI925Rohtl5rGj54a9YvgTjwQMNKe341Hk4/SGhtTqfL9RcuMQk60stf9AIt
c8TS73QdnabOROpo9EddBlK/ZBR2i5Y7gDUZwK82137+CJx381m7NQIdK+/tnuCm6Obu/uHBkajH
NuHlSeMU+S4z1+MUDFSf196nR6xpFF7MeW0fnxwdn+OK4e3w6IXiSuaCeMu8Zt4Q/0+xsgpXcszL
nUL5AnI6k56WvPsvF20HxtiNVGig6RJ6EOjElz2kNuMMSBxl3uq0cLxhRS5OoBeEzxNkFerJxbRo
FwdCOW/3J1HmcC8Mf7zoclyq5B8SyqKL5czNwwEOmarBpzka9u8Gw+ue5Hu/rW206/XOxffvth29
4ZxGMJRyJVhBOGZZtOhKlDJkmxRlEQtJRHfG7UjuBuNXasatVqU6p3aRVQnbUdmuKer7jrQrMila
veArlIQfXfREKOFITz7fTD9wXDNs49WrHTWCyZDK+Efyj/8H3pbK8gbj+Q8Wdb3KbF/+MRdskpUc
c3vg/5tLUMdts/rIsQJqZiwlvDDdwfQ6UgNIkxNZExB22+3uaNIYj3fEzyvPMGjtIAGOefF6TBgI
7KG3ta2KqXdokAqvN0zhw7sTopZ4tWZe7fb75l29MocrG3SxOejYt8x8meQJZLluNwW1icoQK4Qu
Z8eHQMMrg/kgdCxnVgw4vsAnFgWjZqkxltNR1SqEMpNWI4jBCMVJ/smXD1fSNEANXEa4kFDIzpC3
3Lg7HHdgl/ppbw97lPb4J87ghugTjV/hPct+KReE7roj5Dp486aJe18OTFAPJMKBPfciMRDDD7B1
RZOWjXsosHOfjAkzk/YUUemAh7nMOjeuW0BGq5hCrfsUTt372HQf4BEzHrvcdeaX9pF5tgth2Z7z
jd4CBSos1ptXji5q9Wa/d62h1pHm280Abvft28N3b88PYgs69gm3BneSxoKxbNQdX3bbuAOHEKLF
o2evru3Q3lFRBJDoPkqBxL25+3IwYMhulzWpBl/htnTdxr8zl+hbjMhSUZbqK5F0aza1jmbbvF5c
ZLE/WLVtXpweCK6tLD+qfGcqL545aeFYCI6F7b5tHFVs4c51Ty9/QGDjZsWNVS0GYv5st2hDtS67
tJRTUZpgBsZuw2V6I6PapVJPKBAL7NbM2X3QeOUOd08RfV3LKVfPKcfH6jxXt0bA7u2e7r9+d4Zn
vVHt5ah93e61VjtjeA2aQ9rVV68sJQYuDMAaJno39voPzdZk0iKZGp84W/pwjK/0s+BE0LaI6ijf
6yhZ7g3xYyviQJAOB4Do3burqzv2L9rr9y4vcc8uqaktguhupyOXPPEf1UcDzd6g072tSAfyU0O6
6NfF+AOiTXZq8rOjN9nWtl0rMAbTJ9Yw8YOT93zqDvh6jWR64f00c7B1aSqo0u63EkJzf+xf8zc3
N2e7AH0i2BJnm/IdsG+P95onewexYfAw97sByQ2+Un5l1O6t4CLfyMzae9+Ra3xNPZ+ES+bQ1Gqj
YQnV1CSzC52Y6bhbwdhrrjACyF9wRPm8xqV7u/v7p42zsyaCXnvDR9rJbYY0G2I7zQOEC8kiPdIK
X0efbuXg6Lxxevru5Lz59uCogcHIneB2XSVchHcKS7sJnwMc9j/5NhzcHd/vXkvSlKjH5xP6tD0J
cz8HQTLI/6Z7sbpWW0UUt9hAyhb5dyB2moeXtds33iNM5gYSqGS3CSrZh5drz597j2xnp91cvJJR
Wbmh+XM7cS56/M/brE8pLgLm4+WiRbsd4+05r0Lvsly2n1j9fMN/LtJ/s/a9RNC7Sn95Dc/lx7UZ
bMwhQiQqb1VkQMhVtJ0Zvn7Z0X/Bb7aypTB0U3In3NlxDkTsmC2527Fjymnc/RlKaSezrQusbrZs
jYfMO+/Fg76hFkru9YNbk2JoykA8gg1Yru8pLGVPmlb0zY7+qyu77UbiEdKyFnoGjQNChPf85o0D
5l/+PLzGfRiY0bORIyQq+cNv4P+1+KvaeMNtPH+8kc4MQP5Q41YI39cRYCw2g2/FufDnayee1ZMw
yviMr1ucgJ2+gcW85khMRGO/97IphCOKzjihIw5hyVk29qK7elFUNBr8KdI9mZv80jjaPz4VbiLc
34D8GzCkJzdx9u712W9n543DYDxWIPmK9kxDdmDBRva5RVQ2opTYNgzEzdv3KzSYDkmAJBVZqcvn
OCy/RGUZMijtjBbiOeEntDOFSxVUENkyVcHCJb+OfDb9+NM1tWf1KJ+101IMb6RSxW+5cfA3J14u
grYzOA4vuvVgNSHzQeRnd2dFju07kZf3tOr2oot2PCl+IDqcuacJ7tPhZdmViNNXNUGih+cZnyXj
nGeosAq8fJUDkjuRPvUG/FRzBTiByo4KraW8+6isxXcgd4bb67+0Ul72z3UYZ6xS4s80TyWBTjKq
0L8YzHaY7jCUfbXRhURE3RACmDbvEDQX4c6F4XDSdMaiT9us/YxYqkIB1kJ5PRQKi+Vi43KZ68Zi
YI4FcFAdp30ARaPyx+3rUdmWlGVJDVKjUU2ojDq8pYraO42tvznoTui9fkQv4tdyz0s6EwM5LcCA
NsuZ8h4ZU72sgNExcVsvHySkYZEK+xFqJ7VL45k3b9oXsI6FWkglWrVaaDJNRrShl1Zr/ttxN5le
d/lluIhsXpRQAw7o2GuNO9BpkuloNBzzme2/GSWZpvHubWOOrYFIgCVg55hzueSV99bF9EPMsRWr
mrFUT87xMTGQvcEwgis5ofWfEO/qdnLMZeaWhvmKqR5vp3X1kl0ggV950YOaU/Mlxp3DRfSFgQBT
kDLIgsZa0Ipwmi9OGzIdZSaY2jCMe0DojBnBx578wdmEDCwSiIvA3rwi2x/oUkEmqOQuoW76BC0z
olgKqlFMjfbpfRb7xqtcJw4E2eKtlm7POnVKZuKRuPtSezC7czIjE3JGUE66kN9peTNlPJO1i9Ux
HIijNfR42gpupJQAHnftnfeQ33nqpZIhWU3Zm96mEMRnf83q0ly0FL0dIkkQEsbBcpu8wDuOfKSF
qOr1ly+i+Q/tdlTd19rV/aZyj2Yzqv4K62b1VwJ+rz2pcpQRYouSqHq8GVXbBkdX2tF//h5VL6PV
aTJeVdvUar83mN6uEsR1byQrV9F78Otu+2ooPWrY0dl/zvPYzg5PqkXjazbpK8b0LzHSthCgwtHq
Fvv60VaHkaOpKzSYAx55Mm7rqMUAWG0n1fWV2soPdk46zipE98GkCodC/0W0oW8Ja3vtqkSambeT
1kX1pteZXOmLBs1njtFJ//4PUEsBAhQAFAAAAAgAF4VYKDL37PpJJgAAtEsAAAwAAAAAAAAAAAAg
ALaBAAAAAHJlYWx0ZWtfY2Iub1BLAQIUABQAAAAIAGuGWCj/DvDBHUAAAIfUAAAJAAAAAAAAAAEA
IAC2gXMmAABydGw4MTM5LmNQSwUGAAAAAAIAAgBxAAAAt2YAAAAA

--Boundary-=_nWlrBbmQBhCDarzOwKkYHIDdqSCD--

Question Unidentified PCMCIA Card (mayby Realtek)

Re: Question LANPRO Realtek 8139 B/C supported? (Gabriele Paciucci)
Date: 2000, Jun 28
From: Gregor Suhr gregorsuhr

Hi,
i bought a new noname (Synergy-21 S21811 10/100) PCMCIA Network adapter, so i'm not sure if has a RealTek (the importer said so. ?). I looked up the MAC manufacturer ID (00 48 54 ...) and found an entry for a 21143 Tupip card, but the tulip drivers dont work.
The PCMCIA driver also returns a "0xffff, 0c1090" as manf_id, is that normal (0xffff) ??

My last in info is now that it should be an card produced RealTek.

May someone help me ??


Gregor Suhr

None I'd go ahead and try it out

Re: Question Unidentified PCMCIA Card (mayby Realtek) (Gregor Suhr)
Date: 2000, Jul 06
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Just edit /etc/pcmcia/config, and create a new entry for the card,
like one of the other tulip_cb entries, but using those manf id
values, and see what happens.

The 0xffff is bogus so you might want to use the product info strings
instead, to be a little safer.

-- Dave

Question Hw. address read/write mishap 2 with i1500 and IBM Ethernet II

Date: 2000, May 09
From: Tim Gerla timg

I've been having problems for a long time with my IBM Thinkpad i1500 machine and this IBM Ethernet II network card. It works fine with a very specific configuration of kernel 2.2.12 and tools 3.1.8.

I'm currently trying to run kernel 2.3.99 with the tools 3.1.8, with teh built in pcmcia modules.

As soon as I insert the card, it is detected properly, I get an irq, io address, etc. The hardware address shows up properly, but I get the following messages in my syslog:

coruscant kernel: eth0: pcnet_reset_8390() did not complete.
(NE2000 Compatible stuff detected here)

Then I get:

Hw. address read/write mishap 2
Hw. address read/write mishap 4

An ifconfig shows everything in order, but I can't ping any outside hosts. I can ping myself, though. From the outside, it looks like a cable problem, but it is not.

For reference, the same exact problem occurs with a similar NE2000 compatible Kingston adapter. (KNE-PCM/M)

It's also happened with 2.2.13 and a recompiled tools set. I had to revert to 3.1.8 and 2.2.12 for things to work properly though.

An IBM modem card works fine. Another odd symptom: If I insert the modem card in slot 0, then insert the network card into slot 1, the entire kernel freezes. If I try popping out the network card, it goes into an infinite loop of "eth0: interrupt from stopped card." Nothing stops this, not even the magic sysrq key.

Any ideas? I'm getting sort of frustrated stuck with 2.2.12.

Thanks!

-Tim
timg@rrv.net

None Need to narrow down where the problem appears

Re: Question Hw. address read/write mishap 2 with i1500 and IBM Ethernet II (Tim Gerla)
Date: 2000, May 09
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I can't tell if this is a kernel version problem, or a PCMCIA version
problem.

The best thing would be for you to first, with the 2.2.12 kernel,
determine what PCMCIA driver update causes the problem to appear.  You
can try each release from 3.1.8 to 3.1.14.

-- Dave

Question OZ6832: "eth0: interrupt(s) dropped!"

Date: 2000, May 09
From: Axel Thimm Axel

Hello,

I have an as it seems common problem for O2Micro (at least on
Acer notebooks).

If my network card already receives packets during the
initialization of pcmcia-cs (either at boot time or
when plugging in the card with the connector attached),
I get dropped interrupts and some exit status 0x80.

If I start pcmcia with the cards connector detached and
attach it after the two beeps everything is perfect.

I already tried every possible solution to no extend,
including
- excluding all possible interrupts that might conflict
  (and it should not be an interrupt conflict, as I get
   almost 1MB/s on this cheap 10Mbit card)
- module "pcnet_cs" opts "mem_speed=1000 delay_output=1 delay_time=20"
- any combination in
  PCIC_OPTS="pci_int=9 irq_list=11,9 pci_csc=0 do_scan=0"

If it were not for trying to patch up the kernel with the
swsusp patch, I'd call this bug cosmetic, but it messes up
the suspend/resume cycle (I can overcome this by remembering
to remove the card before suspend, but I forget and the
machine messes up.)

System info:
Hardware: Acer TravelMate 513T, O2Micro 6832
          Longshine NE2000 compatible TypeII card.
Software: i686-pc-linux-gnu with 2.2.14 kernel (RedHat 6.2 but
          non RH modified kernel)
          pcmcia-cs-3.1.14

Symptoms:
May  9 20:06:08 pua cardmgr[3108]: executing: './network start eth0'
May  9 20:06:10 pua kernel: eth0: interrupt(s) dropped! 
May  9 20:06:10 pua kernel: eth0: Too much work at interrupt, status 0x80 
May  9 20:06:21 pua last message repeated 562 times

Thanks, Axel Thimm.

None Re: Question: OZ6832: "eth0: interrupt(s) dropped!"

Re: Question OZ6832: "eth0: interrupt(s) dropped!" (Axel Thimm)
Date: 2000, May 11
From: David Hinds <dhinds@pcmcia.sourceforge.org>

It is sounding like this is a peculiarity of whatever chipset is in
this card; I can't reproduce it with any of my NE2000 compatible
cards.  In that case, it is unlikely that I could come up with a fix
without seeing a datasheet for this specific chipset.  And I don't
know how to determine what that is.

-- Dave

Question Has anyone successfully compiled Kingmax-10/100 modified sources under 2.2.x?

Date: 2000, May 10
From: Carlos Betancourt cbetan

If there exists drivers for this cards, although non standard, why is it so hard to compile them? I mean, at least someone should have successfully compiled then, otherwise those drivers wouldn't exist. I'm using kernel 2.2.14 and pcmcia-cs-3.1.14. There is a 8390.c source for 2.2.x kernels within a message addressed to this list on november '99; however, it doesn't compile. I know that this cards are not 100% NE2000 compatible, and it is not officially supported by the kernel nor pcmcia-cs, but there must be a way to make them work with the modified sources. Please, help me, I'm desperate. I have to keep using windows in order to use my cable modem, and I've not money to buy another net card. It's a nightmare being forced to use windows. I would gladly write up a mini-howto for this cards, but I must get it to work first. The kingmax chipset is included in lots of generic network cards, so a lot of linux users have or will have troubles with these bitches. TIA

Carlos Betancourt carlos.betancourt@chello.be

Sad Untitled

Re: Question Has anyone successfully compiled Kingmax-10/100 modified sources under 2.2.x? (Carlos Betancourt)
Date: 2000, Jun 09
From: Chris Lo mychrislo

I have a hard time using this card under Linux, I've download the latest v1.3 drivers from KingMax, compiled it with some tweaks. Now it runs, only problem is that when system is halt (runlevel 0) or using cardctl eject, it will just panic the kernel.

Anyone has better luck or know if it *will* be supported? I'm using Mandrake 7.0 with pcmcia-cs 3.0.9...................

If it doesn't work out. I'm going to buy a new one or have it swapped.

Chris

None I wouldn't hold your breath

Re: Sad Untitled (Chris Lo)
Date: 2000, Jun 09
From: David Hinds <dhinds@pcmcia.sourceforge.org>

It will probably be supported eventually, but I can't really say when
the details will be worked out.  If you need something that works,
then I'd probably just go with another card.

-- Dave

Question Genius MF3000 stalls 3.1.14

Date: 2000, May 16
From: Philip Martin philip

 kernel 2.2.15
 pcmcia 3.1.14

I have a Genius MF3000 network adapter that gets identified as

 May 16 21:26:29 debian1 cardmgr[155]: initializing socket 0
 May 16 21:26:29 debian1 cardmgr[155]: socket 0: Tulip-based CardBus Fast Ethernet
 May 16 21:26:29 debian1 kernel: cs: cb_alloc(bus 32): vendor 0x1011, device 0x0019
 May 16 21:26:29 debian1 kernel: ROM image dump:
 May 16 21:26:29 debian1 kernel:   image 0: 0x000000-0x0001ff, signature PCIR
 May 16 21:26:29 debian1 cardmgr[155]: executing: 'insmod /lib/modules/2.2.15/pcmcia/cb_enabler.o'
 May 16 21:26:29 debian1 cardmgr[155]: executing: 'insmod /lib/modules/2.2.15/pcmcia/tulip_cb.o'
 May 16 21:26:29 debian1 kernel: cs: cb_config(bus 32)
 May 16 21:26:29 debian1 kernel:   fn 0 bar 1: io 0x200-0x27f
 May 16 21:26:29 debian1 kernel:   fn 0 bar 2: mem 0x600c0000-0x600c03ff
 May 16 21:26:29 debian1 kernel:   fn 0 rom: mem 0x60080000-0x600bffff  
 May 16 21:26:29 debian1 kernel: cs: cb_enable(bus 32)
 May 16 21:26:29 debian1 kernel:   bridge io map 0 (flags 0x21): 0x200-0x27f
 May 16 21:26:29 debian1 kernel:   bridge mem map 0 (flags 0x1): 0x60080000-0x600c0fff
 May 16 21:26:29 debian1 kernel: tulip_reap()
 May 16 21:26:29 debian1 kernel: tulip_attach(bus 32, function 0)
 May 16 21:26:29 debian1 kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
 May 16 21:26:29 debian1 kernel: eth0: Digital DS21143 Tulip rev 65 at 0x200, 00: A0:0C:90:6D:9A, IRQ 10.
 May 16 21:26:29 debian1 kernel: eth0:  EEPROM default media type Autosense.
 May 16 21:26:29 debian1 kernel: eth0:  Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block.
 May 16 21:26:29 debian1 kernel: eth0:  Index #1 - Media 10baseT-FD (#4) described by a 21142 Serial PHY (2) block.
 May 16 21:26:29 debian1 kernel: eth0:  Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4) block.
 May 16 21:26:29 debian1 kernel: eth0:  Index #3 - Media 100baseTx-FD (#5) described by a 21143 SYM PHY (4) block.
 May 16 21:26:29 debian1 cardmgr[155]: executing: './network start eth0'

Once the network interface is up and running I can use NFS and ssh successfully. However transferring large files with scp or network printing does not work--the transfer stalls. Setting the tulip_cb debug option I see Transmit errors:

 May 16 20:42:04 debian1 kernel:  In tulip_rx(), entry 13 005a0320.
 May 16 20:42:04 debian1 kernel: eth0: In tulip_rx(), entry 13 005a0320.
 May 16 20:42:04 debian1 kernel: eth0: interrupt  csr5=0xf0660000 new csr5=0xf0660000.
 May 16 20:42:04 debian1 kernel: eth0: exiting interrupt, csr5=0xf0660000.
 May 16 20:42:04 debian1 kernel: eth0: interrupt  csr5=0xf0670004 new csr5=0xf0660000.
 May 16 20:42:04 debian1 kernel: eth0: interrupt  csr5=0xf0660000 new csr5=0xf0660000.
 May 16 20:42:04 debian1 kernel: eth0: exiting interrupt, csr5=0xf0660000.
 May 16 20:42:04 debian1 kernel: eth0: interrupt  csr5=0xf0670040 new csr5=0xf0660000.
 May 16 20:42:04 debian1 kernel:  In tulip_rx(), entry 14 005a0320.
 May 16 20:42:04 debian1 kernel: eth0: In tulip_rx(), entry 14 005a0320.
 May 16 20:42:04 debian1 kernel: eth0: interrupt  csr5=0xf0660000 new csr5=0xf0660000.
 May 16 20:42:04 debian1 kernel: eth0: exiting interrupt, csr5=0xf0660000.
 May 16 20:42:04 debian1 kernel: eth0: interrupt  csr5=0xf0670004 new csr5=0xf0660000.
 May 16 20:42:04 debian1 kernel: eth0: Transmit error, Tx status 7fffb200.
 May 16 20:42:04 debian1 kernel: eth0: interrupt  csr5=0xf0660000 new csr5=0xf0660000.
 May 16 20:42:04 debian1 kernel: eth0: exiting interrupt, csr5=0xf0660000.
 May 16 20:42:04 debian1 kernel: eth0: interrupt  csr5=0xf0670004 new csr5=0xf0660000.
 May 16 20:42:04 debian1 kernel: eth0: Transmit error, Tx status 7fffb200.
 May 16 20:42:04 debian1 kernel: eth0: interrupt  csr5=0xf0660000 new csr5=0xf0660000.

When this happens the tulip_diag program reports:

 tulip-diag.c:v1.19 10/2/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
 Index #1: Found a Digital DS21143 Tulip adapter at 0x200.
  Port selection is 100mbps-SYM/PCS 100baseTx scrambler, full-duplex.
  Transmit started, Receive started, full-duplex.
   The Rx process state is 'Waiting for packets'.
   The Tx process state is 'Idle'.
   The transmit threshold is 128.
   The NWay status register is 45e1d2cd.
   Internal autonegotiation state is 'Negotiation complete'.

An strace of the scp process shows it stalled in a write():

 write(6, "\376\f\0\211\300PW\350\370&\375\377\203\304\20\350\20,"..., 4096) = 4096
 read(3, "\350\37\34\375\377\350\312\37\375\377\215\266\0\0\0\0\213"..., 4096) = 4096
 write(6, "\350\37\34\375\377\350\312\37\375\377\215\266\0\0\0\0\213"..., 4096) = 4096
 read(3, "\350\17\r\375\377\203\304\20\203\304\370\203\304\364\213"..., 4096) = 4096
 write(6, "\350\17\r\375\377\203\304\20\203\304\370\203\304\364\213"..., 4096) = 4096
 read(3, "\203\304\364\213E\10\203\300\4P\350Q\2\24\0\203\304\20"..., 4096) = 4096
 write(6, "\203\304\364\213E\10\203\300\4P\350Q\2\24\0\203\304\20"..., 4096) = 4096
 read(3, "\354\24S\213]\10\307\3|\236 \10\203\304\370j\2\215C\20"..., 4096) = 4096
 write(6, "\354\24S\213]\10\307\3|\236 \10\203\304\370j\2\215C\20"..., 4096 
                                                                           ^it hangs here

If I cancel the scp file transfer I can then do an NFS copy at several Mb/second.

I also have a 3Com 3CCFEM556B which works fine, so the problem would appear to lie with the tulip driver.

Any ideas?

Philip

None I think I need a bit more information

Re: Question Genius MF3000 stalls 3.1.14 (Philip Martin)
Date: 2000, Jun 06
From: David Hinds <dhinds@pcmcia.sourceforge.org>

>  May 16 21:26:29 debian1 cardmgr[155]: initializing socket 0

What messages do you get before this?  (the Intel PCIC probe
messages?)  And what sort of laptop is this?

> I also have a 3Com 3CCFEM556B which works fine, so the problem would
> appear to lie with the tulip driver.

Not necessarily; it could be in the code that configures the CardBus
bridge.

-- Dave

None Re: I think I need a bit more information

Re: None I think I need a bit more information (David Hinds)
Date: 2000, Jun 06
From: Philip Martin philip

David Hinds <dhinds@valinux.com> writes:

> >  May 16 21:26:29 debian1 cardmgr[155]: initializing socket 0
> 
> What messages do you get before this?  (the Intel PCIC probe
> messages?)

 Jun  6 21:00:39 debian1 kernel: Linux PCMCIA Card Services 3.1.14
 Jun  6 21:00:39 debian1 kernel:   kernel build: 2.2.15 unknown
 Jun  6 21:00:39 debian1 kernel:   options:  [pci] [cardbus] [apm]
 Jun  6 21:00:39 debian1 kernel: PCI routing table version 1.0 at 0xfe840
 Jun  6 21:00:39 debian1 kernel:   00:08.0 -> irq 10
 Jun  6 21:00:39 debian1 kernel:   00:08.1 -> irq 10
 Jun  6 21:00:39 debian1 kernel:   01:00.0 -> irq 10
 Jun  6 21:00:39 debian1 kernel: Intel PCIC probe: 
 Jun  6 21:00:39 debian1 kernel:   TI 1225 rev 01 PCI-to-CardBus at slot 00:08, mem 0x68000000
 Jun  6 21:00:39 debian1 kernel:     host opts [0]: [pci + serial irq] [pci irq 10] [lat 168/176] [bus 32/0]
 Jun  6 21:00:39 debian1 kernel:     host opts [1]: [pci + serial irq] [pci irq 10] [lat 168/176] [bus 35/0]
 Jun  6 21:00:39 debian1 kernel:     ISA irqs (scanned) = 3,4,7,9,11 PCI status changes
 Jun  6 21:00:39 debian1 cardmgr[134]: starting, version is 3.1.14
 Jun  6 21:00:39 debian1 cardmgr[134]: watching 2 sockets
 Jun  6 21:00:39 debian1 kernel: cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
 Jun  6 21:00:39 debian1 kernel: cs: IO port probe 0x0800-0x08ff: clean.
 Jun  6 21:00:39 debian1 kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x398-0x39f 0x4d0-0x4d7
 Jun  6 21:00:39 debian1 kernel: cs: IO port probe 0x0a00-0x0aff: clean.
 Jun  6 21:00:40 debian1 kernel: cs: cb_alloc(bus 32): vendor 0x1011, device 0x0019
 Jun  6 21:00:40 debian1 cardmgr[134]: initializing socket 0
 Jun  6 21:00:40 debian1 kernel: ROM image dump:
 Jun  6 21:00:40 debian1 kernel:   image 0: 0x000000-0x0001ff, signature PCIR
 Jun  6 21:00:40 debian1 cardmgr[134]: socket 0: Tulip-based CardBus Fast Ethernet
 Jun  6 21:00:40 debian1 cardmgr[134]: executing: 'insmod /lib/modules/2.2.15/pcmcia/cb_enabler.o'
 Jun  6 21:00:40 debian1 cardmgr[134]: executing: 'insmod /lib/modules/2.2.15/pcmcia/tulip_cb.o debug=6'
 Jun  6 21:00:40 debian1 kernel: cs: cb_config(bus 32)
 Jun  6 21:00:40 debian1 kernel:   fn 0 bar 1: io 0x200-0x27f
 Jun  6 21:00:40 debian1 kernel:   fn 0 bar 2: mem 0x600c0000-0x600c03ff
 Jun  6 21:00:40 debian1 kernel:   fn 0 rom: mem 0x60080000-0x600bffff
 Jun  6 21:00:40 debian1 kernel: cs: cb_enable(bus 32)
 Jun  6 21:00:40 debian1 kernel:   bridge io map 0 (flags 0x21): 0x200-0x27f
 Jun  6 21:00:40 debian1 kernel:   bridge mem map 0 (flags 0x1): 0x60080000-0x600c0fff
 Jun  6 21:00:40 debian1 kernel: tulip_reap()
 Jun  6 21:00:40 debian1 kernel: tulip_attach(bus 32, function 0)
 Jun  6 21:00:40 debian1 kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
 Jun  6 21:00:40 debian1 kernel: eth0: Digital DS21143 Tulip rev 65 at 0x200, 00:A0:0C:90:6D:9A, IRQ 10.
 Jun  6 21:00:40 debian1 kernel: eth0:  EEPROM default media type Autosense.
 Jun  6 21:00:40 debian1 kernel: eth0:  Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block.
 Jun  6 21:00:40 debian1 kernel: eth0:  Index #1 - Media 10baseT-FD (#4) described by a 21142 Serial PHY (2) block.
 Jun  6 21:00:40 debian1 kernel: eth0:  Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4) block.
 Jun  6 21:00:40 debian1 kernel: eth0:  Index #3 - Media 100baseTx-FD (#5) described by a 21143 SYM PHY (4) block.
 Jun  6 21:00:40 debian1 kernel: eth0: Restarting 21143 autonegotiation, 0003ffff.
 Jun  6 21:00:40 debian1 cardmgr[134]: executing: './network start eth0'
 Jun  6 21:00:40 debian1 kernel: eth0: tulip_open() irq 10.
 Jun  6 21:00:40 debian1 kernel: eth0: Restarting 21143 autonegotiation, 0003ffff.
 Jun  6 21:00:40 debian1 kernel: eth0: Done tulip_open(), CSR0 f8a08000, CSR5 f0320000 CSR6 b2422202.
 Jun  6 21:00:40 debian1 kernel: eth0: interrupt  csr5=0xf0670004 new csr5=0xf0660000.
 Jun  6 21:00:40 debian1 kernel: eth0: interrupt  csr5=0xf0660000 new csr5=0xf0660000.
 Jun  6 21:00:40 debian1 kernel: eth0: exiting interrupt, csr5=0xf0660000.

> And what sort of laptop is this?

I don't know who really manufactures it. I bought it from Rock
Computers in the UK, its their Sigma model. Its about 9 months old, it
has a 433MHz Celeron processor, a BX chipset, and a SystemSoft Mobile
Pro BIOS.

For what it's worth the User Manual (which I've just read for the
first time) claims: "PC Card Slots: Compliant with PCMCIA 2.1/JEIDA
4.1 specifications along with ExCA extension and PC CARD standard, two
PC card slots for two type II application, supporting CardBus and
Zoomed Video port".

> 
> > I also have a 3Com 3CCFEM556B which works fine, so the problem would
> > appear to lie with the tulip driver.
> 
> Not necessarily; it could be in the code that configures the CardBus
> bridge.

Sad When will pcnet_cs work with Asix AX88190 Chipset?

Date: 2000, May 24
From: Ray jxray

i installed 3.1.15. pcnet_cs told me this poor card was in the blacklist. :( so, when will this card be supported? or, will it be supported?

None We're working on it

Re: Sad When will pcnet_cs work with Asix AX88190 Chipset? (Ray)
Date: 2000, May 25
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Until it is sorted out, you can get a driver from Asix at:

http://www.asix.com.tw/driver2.htm

-- Dave

Ok Thank u.

Re: None We're working on it (David Hinds)
Date: 2000, May 26
From: Ray jxray

i will try this. but still waiting for your new driver! :)

Note It works with 3.1.15

Re: Sad When will pcnet_cs work with Asix AX88190 Chipset? (Ray)
Date: 2000, Jun 09
From: Carlos Betancourt cbetan

David, I installed 3.1.15 just to see the pcnet_cs driver detect and complain about my AX88190 based card. But, for my
 surprise, it didn't complain! And indeed, dhcp worked out and I got asigned my ip address. Unfortunately, it still is not
 reliable and packets get lost, although it works better than with previous driver versions. And sometimes, the computer
 hangs. I'm happy to see that the d-day (driver-day) is close :-) 

 BTW, David, congratulations for your e-mail promotion: @valinux.com And I suspect it's not just e-mail you were promoted
 with ;-) 

Question O2Micro OZ6836: Extremly slow Ethernet-Card

Date: 2000, May 31
From: Dag Kröper dagkro

Hi!

Can everyone help me ????

I've a problem with my Ethernet-Card. The card will be recognized correctly, but it has a very slow Data-Transfer
(about 10 KBytes/sec)

Infos (about my laptop) (I hope they are sufficient):

CPU: Mobile-Pentium II 333 MHz
Chip-Set: Intel MX
RAM: 64 MB
HDD: 4,5 GB Fujitsu
Card-Bus-Controller: O2Micro OZ6836
Ethernet-Card: Longshine LS 8534 TB-A1 10base2 or 10baseT

cardctl config:
================
Socket 0:
  not configured
Socket 1:
  Vcc 5.0V Vpp1 0.0V Vpp2 0.0V
  interface type is "memory and I/O"
  irq 10 [exclusive] [level]
  function 0:
    config base 0x0fd0
      option 0x41 status 0x00 copy 0x00
    io 0x0300-0x031f [auto]

cardctl ident
=============
Socket 0:
  no product info available
Socket 1:
  product info: "Ethernet", "Adapter", "2.0"
  manfid: 0x0149, 0xc1ab
  function: 6 (network)

dmesg:
======
Linux PCMCIA Card Services 3.1.15
  kernel build: 2.2.15 #4 Tue May 30 15:37:59 MEST 2000
  options: [pci] [cardbus] [apm]
PCI routing table version 1.0 at 0xfdf00
  00:03.0 -> irq 11
  00:03.1 -> irq 11
Intel PCIC probe:
  O2Micro OZ6836/60 rev 62 PCI-to-CardBus at slot 00:03, mem 0xe1000000
    host opts [0]: [ring] [pci/way] [pci irq 11] [lat 32/176] [bus 32/34]
    host opts [1]: [ring] [pci/way] [pci irq 11] [lat 32/176] [bus 35/37]
    ISA irqs (default) = 3,4,7,9,10,12 PCI status changes
cs: IO port probe 0x1000-0x17ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x408-0x40f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa00fffff
eth0: NE2000 Compatible: io 0x300, irq 10, hw_addr 00:E0:98:7B:D2:A3

None The messages look good

Re: Question O2Micro OZ6836: Extremly slow Ethernet-Card (Dag Kröper)
Date: 2000, May 31
From: David Hinds <dhinds@pcmcia.sourceforge.org>

A few general questions:

- Are you using a network cable that you know is good?  (are you sure
  you don't have a wiring problem?)

- When these slow transfers are going on, do you get any error
  messages from the driver in your system log?  And what do the error
  statistics reported by "ifconfig" look like?

- Does the interrupt counter for the card in /proc/interrupts run up
  while you are transfering data?  Is the transfer rate similar for
  transmit and receive?

-- Dave

None Re: The messages look good

Re: None The messages look good (David Hinds)
Date: 2000, Jun 02
From: Dag Kroeper dagkro

This is a cryptographically signed message in MIME format.

--------------msB57A418E0E6FCC1FEE3B457B
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

David Hinds wrote:

> A few general questions:
>
> - Are you using a network cable that you know is good?  (are you sure
>   you don't have a wiring problem?)

Yes, with Windows (urggh) I've rates about 600Kbyte/sec

>
>
> - When these slow transfers are going on, do you get any error
>   messages from the driver in your system log?  And what do the error
>   statistics reported by "ifconfig" look like?

No, I got no error messages by ifconfig:

eth0      Link encap:Ethernet  HWaddr 00:E0:98:7B:D2:A3
          inet addr:134.96.239.197  Bcast:134.96.239.255
Mask:255.255.255.128
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:24 errors:0 dropped:0 overruns:0 frame:0
          TX packets:23: errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          Interrupt:10 Base address:0x300

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0



>
>
> - Does the interrupt counter for the card in /proc/interrupts run up
>   while you are transfering data?  Is the transfer rate similar for
>   transmit and receive?

Yes, the counter is running up, and the rates are similar.

>
>
> -- Dave

--
--------------------------------------------------------------------------------
Dag Kröper

Universität des Saarlandes
Fachbereich 14 Informatik
Fachbereichsbibliothek
Im Stadtwald Bau 45 Raum 200
Postfach 151150
66041 Saarbrücken

Tel:   (+49)681 302 5531
Fax:   (+49)681 302 5533
Priv:  (+49)6868 1525
Mobil: (+49)170 2337546

mailto:ib14-2@broccoli.cs.uni-sb.de
--------------------------------------------------------------------------------



--------------msB57A418E0E6FCC1FEE3B457B
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIGkwYJKoZIhvcNAQcCoIIGhDCCBoACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
BDAwggQsMIIDlaADAgECAg8Al8wAAAADT9z51LcHYmswDQYJKoZIhvcNAQEEBQAwgbwxCzAJ
BgNVBAYTAkRFMRAwDgYDVQQIEwdIYW1idXJnMRAwDgYDVQQHEwdIYW1idXJnMTowOAYDVQQK
EzFUQyBUcnVzdENlbnRlciBmb3IgU2VjdXJpdHkgaW4gRGF0YSBOZXR3b3JrcyBHbWJIMSIw
IAYDVQQLExlUQyBUcnVzdENlbnRlciBDbGFzcyAxIENBMSkwJwYJKoZIhvcNAQkBFhpjZXJ0
aWZpY2F0ZUB0cnVzdGNlbnRlci5kZTAeFw05OTExMzAxNTA4MjRaFw0wMDExMjkxNTA4MjRa
MHIxCzAJBgNVBAYTAkRFMREwDwYDVQQIEwhTYWFybGFuZDEVMBMGA1UEBxMMU2Nod2VtbGlu
Z2VuMRQwEgYDVQQDEwtEYWcgS3JvZXBlcjEjMCEGCSqGSIb3DQEJARYUa3JvZXBlckBjcy51
bmktc2IuZGUwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMFUxq8bC80Sf5lU15Pog++k
0iBS3OZXl3nkmamjUz/Aqp4r3hgXznk9/mnFafpzp5VttHAORUYXkJ0FwLqb9mF0q9vl4dqw
QH7YpyZqF6XfFKgnNZnyvoslwTqMahz37KMzBDZw5nzoSPwDeFRDWoklOSBLHxkfVxtEE1V0
a2qVAgMBAAGjggF3MIIBczCByQYDVR0jBIHBMIG+oYG2MIGzpIGUMIGRMQswCQYDVQQGEwJE
RTEQMA4GA1UECBMHSGFtYnVyZzEQMA4GA1UEBxMHSGFtYnVyZzE6MDgGA1UEChMxVEMgVHJ1
c3RDZW50ZXIgZm9yIFNlY3VyaXR5IGluIERhdGEgTmV0d29ya3MgR21iSDEiMCAGA1UECxMZ
VEMgVHJ1c3RDZW50ZXIgQ2xhc3MgMSBDQYEaY2VydGlmaWNhdGVAdHJ1c3RjZW50ZXIuZGWi
AwIBAjAzBglghkgBhvhCAQgEJhYkaHR0cDovL3d3dy50cnVzdGNlbnRlci5kZS9ndWlkZWxp
bmVzMBEGCWCGSAGG+EIBAQQEAwIFoDBdBglghkgBhvhCAQMEUBZOaHR0cHM6Ly93d3cudHJ1
c3RjZW50ZXIuZGUvY2dpLWJpbi9jaGVjay1yZXYuY2dpLzk3Q0MwMDAwMDAwMzRGRENGOUQ0
QjcwNzYyNkI/MA0GCSqGSIb3DQEBBAUAA4GBAFGeVAj2w+M7D44riLWbhdeQhgKozMiGiHec
LPScffdsUIUWYX+1XcooG1CHLp2zvbenMf+UFWAYvwYcdypM74oFl7KV089G1/zkshVzmZWD
SxFflP2Ks4FLivCaiDK9u/TrZYFmZGxxdUWJaXMVs8AWdcTUyKO7dF39mSwHaRh6MYICKzCC
AicCAQEwgdAwgbwxCzAJBgNVBAYTAkRFMRAwDgYDVQQIEwdIYW1idXJnMRAwDgYDVQQHEwdI
YW1idXJnMTowOAYDVQQKEzFUQyBUcnVzdENlbnRlciBmb3IgU2VjdXJpdHkgaW4gRGF0YSBO
ZXR3b3JrcyBHbWJIMSIwIAYDVQQLExlUQyBUcnVzdENlbnRlciBDbGFzcyAxIENBMSkwJwYJ
KoZIhvcNAQkBFhpjZXJ0aWZpY2F0ZUB0cnVzdGNlbnRlci5kZQIPAJfMAAAAA0/c+dS3B2Jr
MAkGBSsOAwIaBQCggbEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUx
DxcNMDAwNjAyMDk0NjI2WjAjBgkqhkiG9w0BCQQxFgQUPG2955+mvrIww8gyR7Kcm6TNQ+Yw
UgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwBwYFKw4DAgcw
DQYIKoZIhvcNAwICAUAwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEgYCsp8kDKx9p
gfDQPnOTs43cFj7BRLyS4s8b5IlGAk17bPRKxt7TRdwpRxV8DrKhl/liaAdVrNZyR+XDM6AW
W67ZNh8U5frZWgzCuLOuJdumiZcKgNqrXD4hlo7+Z5MOA01egUKvwNGLhErQBUY6IVU8bQfI
wyZb5T4pIBShmupTww==
--------------msB57A418E0E6FCC1FEE3B457B--

Idea Solve Problem :-)

Re: None The messages look good (David Hinds)
Date: 2000, Jul 10
From: Dag Kröper dagkro

I've found a dirty hack to solve my problem with the very slow ethernet!

set in COREOPTIONS: cb_mem_base=<membase found in W98>
reboot system
start win98 (it dosn't works by starting only DOS :-()
boot linux using loadlin
if the pcmcia_cs is loaded there will be an error-message:
   ignore it :-)
log in as root
typein: /etc/rc.d/pcmcia stop
        /etc/rc.d/pcmcia start

and now my network is as fast as an 10base2-Network :-)

I've only found two differences in the pci-register sets:

the PCI-Latency-Timer is now 168 instead 32 and the Region 0 shows memory at <ignored> instead mamory at 0x0e....

I've not yet compared the EXCA-Registers!

Greetings from Germany

Dag Kröper

Question Question about epic_cb driver

Date: 2000, Jun 02
From: Brian Mays brian

Looking at the Configure script, it appears that the epic_cb client is built if CARDBUS support is enabled:

   725	if [ "$CONFIG_CARDBUS" = "y" ] ; then
   726	    if grep CARDBUS ${LINUX}/drivers/net/epic100.c >/dev/null ; then
   727		echo DO_EPIC_CB=y >> $CONFIG_MK
   728	    fi
   729	fi

I have found that if epic support (CONFIG_EPIC100) has not been compiled into the kernel, the following unresolved symbol results:

    # depmod -ae
    depmod: *** Unresolved symbols in /lib/modules/2.2.15/pcmcia/epic_cb.o
    depmod:         epic100_probe

Shouldn't the epic_cb be built only if epic support has been built into the kernel? Have I missed something here?

Thanks,

Brian

None The epic_cb driver got broken in 2.2.15

Re: Question Question about epic_cb driver (Brian Mays)
Date: 2000, Jun 02
From: David Hinds <dhinds@pcmcia.sourceforge.org>

epic_cb links the epic100 driver into itself, so no, it is not
supposed to rely on epic support in the kernel.

The problem is that someone deleted all the CardBus code from the
epic100 driver at some point in the pre-2.2.15 patches.  It still has
an "#ifdef CARDBUS" so it passes the simple test in the Configure
script.  But the driver can't work.

-- Dave

None Re: The epic_cb driver got broken in 2.2.15

Re: None The epic_cb driver got broken in 2.2.15 (David Hinds)
Date: 2000, Jun 02
From: Brian Mays brian

> epic_cb links the epic100 driver into itself, so no, it is not
> supposed to rely on epic support in the kernel.

Okay.  I thought that I had missed something there.

> The problem is that someone deleted all the CardBus code from the
> epic100 driver at some point in the pre-2.2.15 patches.  It still has
> an "#ifdef CARDBUS" so it passes the simple test in the Configure
> script.  But the driver can't work.

I see.

Thanks,
Brian

Feedback Corega 10M EtherII PCC-T failed detection

Date: 2000, Jun 03
From: Michael Fitzpatrick leahcim

I bought a Corega 10M PCMCIA PCC-T card @ Linux Expo 2000.

Plugged it in and got an Oops from CardMgr loading tulip_cb drivers.

Turns out this card isn't in the config file (only a slight difference in version info from another Corega card though)

Biggest problem is the manuf ID it reports clashes with another card in the database.

It was trivial for me to add an entry for this card (it uses pcnet_cs like the other Corega cards already defined) and comment out the clashing card, and once that's done the card works without problems.

Info returned from cardctl ident for Corega :-

Socket 1:
  product info: "corega K.K.", "corega EtherII PCC-T"
  manfid: 0xc00f, 0x0000
  function: 6 (network)

config entry for manfid clash :-

#card "Allied Telesyn AT-2800 10/100 Fast Ethernet"
# manfid 0xc00f, 0x0000
# bind "tulip_cb"

Entry I added to config :-

card "Corega PCC-T EtherII"
  version "corega K.K.", "corega EtherII PCC-T"
  bind "pcnet_cs"

None Apologies

Re: Feedback Corega 10M EtherII PCC-T failed detection (Michael Fitzpatrick)
Date: 2000, Jun 03
From: Michael Fitzpatrick leahcim

Sorry, I've just seen the manfid conflict has been reported in here before :o/

Question Abocom FE1500 supported ???

Date: 2000, Jun 06
From: Julien pwaro

Hi,

I plan to buy an Abocom FE1500 Ethernet card. On the abocom's web site, it is claimed that this card is fully supported on Linux. But on the list of supported cards by pcmcia-cs, I have only found the FE1000... So what's the truth ? Is it really supported or not ?

Thank you if you can help me ;-)

Mr Pwaro

None Probably the wrong place to ask

Re: Question Abocom FE1500 supported ??? (Julien)
Date: 2000, Jun 06
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I think you would need to ask Abocom about that.  I only list cards
that people have verified as working, and no one has told me anything
good or bad about this FE1500 card.  I doubt that they would say it
worked if it did not; but maybe they supply their own linux driver.

-- Dave

Ok FE-1500 works !!!

Re: None Probably the wrong place to ask (David Hinds)
Date: 2000, Jun 26
From: Julien pwaro

Hi David,

I have finally bought this Abocom FE-1500 (http://www.abocom.com/fe1500.htm). It works !!!

It is recognized as a NE2000 compatible ethernet card, and it works both at 10 and 100 mbits.

Here is an extract from my /var/log/messages :

Jun 26 09:49:55 pcpouet cardmgr[428]: initializing socket 0
Jun 26 09:49:55 pcpouet cardmgr[428]: socket 0: NE2000 Compatible Ethernet
Jun 26 09:49:55 pcpouet cardmgr[428]: executing: 'insmod /lib/modules/2.2.16-3/net/8390.o'
Jun 26 09:49:55 pcpouet cardmgr[428]: executing: 'insmod /lib/modules/2.2.16-3/pcmcia/pcnet_cs.o'
Jun 26 09:49:56 pcpouet kernel: eth0: NE2000 Compatible: io 0x300, irq 9, hw_addr :-)
Jun 26 09:49:56 pcpouet cardmgr[428]: executing: './network start eth0'

I am running a 2.2.16 kernel with pcmcia-cs 3.1.8 (redhat 6.2).

I think you can add it to the list of supported fast-ethernet cards. And thank you very much for your great work !

Best regards,

Julien

Question OvisLink LFS-PCM-32 not working unless in promiscous mode

Date: 2000, Jun 13
From: Miguel mtavares

I've notice this strange behaviour when using the refered in the subject.

After inserting the device and cardmgr beeps twice, so I guess that it is being recognize, I canot ping to the outside of my computer. But, if I start a tcpdump (getting eth0 in promiscuous mode) then I'm able to ping, althoug the network connectiong doesn't seem very reliable.

This board is being identified as a tulip_cb, so my guess is that I'm probably missing some configuration parameters.

More information (that I hope can help): - The computer is a Toshiba 4070CDS - I'm using Suse 6.4 with the upgraded pcmcia package ('thou I wouldn't mind having to compile and install it myself).

		Best regards to all

				Miguel

None You may have to live with that for now

Re: Question OvisLink LFS-PCM-32 not working unless in promiscous mode (Miguel)
Date: 2000, Jun 14
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The transceiver manipulation code in the tulip driver is quite arcane
and I'm afraid to mess with it.  I'm not surprised that there are
cards that are not handled correctly.

-- Dave

None Minor mistake in /etc/pcmcia/network script

Date: 2000, Jun 15
From: Brian Mays brian

There is a typo in the etc/network script. The line

    if test -x /usr/sbin/ipmasq && istrue "$IPMASQ" ; then

should read

    if test -x /usr/sbin/ipmasq && is_true "$IPMASQ" ; then

None Hmmm...

Re: None Minor mistake in /etc/pcmcia/network script (Brian Mays)
Date: 2000, Jun 15
From: David Hinds <dhinds@pcmcia.sourceforge.org>

My version of the script doesn't have an $IPMASQ paramter ;)

-- Dave

Sad invalid operand: 0000

Date: 2000, Jun 24
From: Nuitari

I get this error whenever cardmgr detects my 
3Com TokenLink III (3c689)

It happends with both the 2.3.99-pre9 and 2.4.0-test1-ac22-classproc kernels.

The token ring driver is built in the kernel.
Before I updated to 3.1.17, I think I was using version 3.1.9 (not sure).

The box is an Ascentia 910N from AST (part number 501589-301).

Note that the serial part (an 14.4 kbps data/fax modem from AST, part number 234091-001) does not cause any problem at all.


[nuitari@gandalf nuitari]$ cat bug.cardmgr 
Jun 24 02:50:33 zifnab cardmgr[684]: starting, version is 3.1.11
Jun 24 02:50:33 zifnab cardmgr[684]: watching 2 sockets
Jun 24 02:50:33 zifnab kernel: cs: IO port probe 0x0c00-0x0cff: clean.
Jun 24 02:50:33 zifnab kernel: cs: IO port probe 0x0800-0x08ff: clean.
Jun 24 02:50:33 zifnab kernel: cs: IO port probe 0x0100-0x04ff: excluding
0x100-0x107
Jun 24 02:50:33 zifnab kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Jun 24 02:50:33 zifnab cardmgr[684]: initializing socket 1
Jun 24 02:50:33 zifnab cardmgr[684]: socket 1: IBM Token Ring Adapter
Jun 24 02:50:33 zifnab kernel: invalid operand: 0000
Jun 24 02:50:33 zifnab kernel: CPU:    0
Jun 24 02:50:33 zifnab kernel: EIP:    0010:[ibmtr_probe+32/128]
Jun 24 02:50:33 zifnab kernel: EFLAGS: 00010a07
Jun 24 02:50:33 zifnab kernel: eax: c02b2fe0   ebx: c14c2600
ecx: c1a5d30c   edx: c14c2600
Jun 24 02:50:33 zifnab kernel: esi: 0000002b   edi: c03a7a24
ebp: c10d2400   esp: c03a79a4
Jun 24 02:50:33 zifnab kernel: ds: 0018   es: 0018   ss: 0018
Jun 24 02:50:33 zifnab kernel: Process cardmgr (pid: 684,
stackpage=c03a7000)
Jun 24 02:50:33 zifnab kernel: Stack: c01c94cf c14c2600 c03a79dc c01df6a8
c14c2600 c14c2600 c10d2400 c14c2600
Jun 24 02:50:33 zifnab kernel:        c1a5d358 c1a5d300 c10d249c c10d24c8
c14c2600 c10d2400 000cc000 c03a0000
Jun 24 02:50:33 zifnab kernel:        08002101 c01dff0b c10f6ba0 c03a7b00
c03a7b44 c03a7b44 c10f6ba0 42490104
Jun 24 02:50:33 zifnab kernel: Call Trace: [register_trdev+15/48]
[ibmtr_config+760/976] [tok_interrupt+443/3584]
[pcmcia_get_next_tuple+125/560] [pcmcia_get_next_tuple+163/560]
[<ffffc0c6>] [pcmcia_validate_cis+278/336]
Jun 24 02:50:33 zifnab kernel:        [msstab+28574/29086]
[kfree_skbmem+38/128] [__kfree_skb+265/272] [ibmtr_event+202/416]
[pcmcia_register_client+503/528] [register_netdevice+397/416]
[tr_configure+0/96] [init_netdev+182/208]
Jun 24 02:50:33 zifnab kernel:        [CardServices+414/848]
[list.927+6827/11800] [ibmtr_attach+364/416] [ibmtr_event+0/416]
[bind_request+352/432] [bind_request+392/432] [ds_ioctl+1213/1488]
[do_anonymous_page+92/272]
Jun 24 02:50:34 zifnab kernel:        [do_no_page+48/176]
[handle_mm_fault+240/352] [do_page_fault+391/1360] [msstab+28574/29086]
[proc_get_inode+65/288] [proc_lookup+154/176] [vsprintf+822/880]
[free_page_and_swap_cache+470/480]
Jun 24 02:50:34 zifnab kernel:        [zap_page_range+358/480]
[unmap_fixup+283/304] [do_munmap+612/640] [sys_ioctl+359/400]
[system_call+52/64] [stext+43/309]

Jun 24 02:50:34 zifnab kernel: Code: ff eb 57 50 57 e8 56 00 00 00 83 c4
08 85 c0 75 44 31 c0 eb


uname -rv
2.4.0-test1-ac22-class #1 Sat Jun 24 00:47:33 EDT 2000

cardctl -V
cardctl version 3.1.11

[nuitari@gandalf nuitari]$ 

Sad Again: eth0: interrupt(s) dropped!

Date: 2000, Jun 26
From: Michael Brandt michab

hi,

i just installed linux (suse64) on my laptop using pcmcia 3.1.17. eth0 is set up correcty via dhcp but i'm getting these messages:

kernel: eth0: Reentering the interrupt handler! isr=0x0 imr=0x0.
last message repeated 3 times
kernel: eth0: interrupt(s) dropped!

additionaly i'm not able to build up an connection....

under win irq_11 is assigned to my graphiccard, irq_10 seem to be free..

how can i fix this ?? any ideas ??

thx,
micha

some settings & messages:
---------------------------------

PCIC=i82365
PCIC_OPTS="pci_int=1 pci_irq_list=11 irq_list=10"


config:
---------
Socket 0:
  Vcc 5.0V  Vpp1 0.0V  Vpp2 0.0V
  interface type is "memory and I/O"
  irq 10 [exclusive] [level]
  function 0:
    config base 0x03c0
      option 0x47 status 0x00
    io 0x0300-0x031f [auto]
Socket 1:
  not configured

ident:
---------
Socket 0:
  product info: "PCMCIA", "FAST ETHERNET CARD"
  manfid: 0xffff, 0x1090
  function: 6 (network)
Socket 1:
  no product info available

status:
----------
Socket 0:
  5V 16-bit PC Card
  function 0: [ready]
Socket 1:
  no card

messages:
-----------
kernel: Linux PCMCIA Card Services 3.1.17
kernel:   kernel build: 2.2.14 #1 Mon Mar 13 10:54:26 GMT 2000
kernel:   options:  [pci] [cardbus] [apm]
kernel: PCI routing table version 1.0 at 0xfdf80
kernel: Intel PCIC probe: 
kernel:   O2Micro OZ6832/33 rev 34 PCI-to-CardBus at slot 00:0a, mem 0x68000000
kernel:     host opts [0]: [ring] [pci/way] [pci irq 11] [lat 168/176] [bus 32/34]
kernel:     host opts [1]: [ring] [pci/way] [no pci irq] [lat 168/176] [bus 35/37]
kernel:     PCI irq 11 test failed
kernel:     ISA irqs (default) = 10 polling interval = 1000 ms
cardmgr[253]: starting, version is 3.1.17
cardmgr[253]: watching 2 sockets
kernel: cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
kernel: cs: IO port probe 0x0800-0x08ff: clean.
kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x398-0x39f 0x4d0-0x4d7
kernel: cs: IO port probe 0x0a00-0x0aff: clean.
cardmgr[253]: initializing socket 0
kernel: cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa00fffff
cardmgr[253]: socket 0: NE2000 Compatible Fast Ethernet
cardmgr[253]: executing: 'modprobe 8390'
cardmgr[253]: executing: 'modprobe pcnet_cs mem_speed=600 hw_addr=0x00,0x50,0x22,0xF2,0x1D,0x58'
kernel: pcnet_cs: sorry, the AX88190 chipset is not supported.
kernel: eth0: NE2000 Compatible: io 0x300, irq 10, hw_addr 00:50:22:F2:1D:58
cardmgr[253]: executing: './network start eth0'
kernel: eth0: interrupt from stopped card
kernel: eth0: interrupt(s) dropped!
kernel: eth0: Reentering the interrupt handler! isr=0x0 imr=0x0.
last message repeated 3 times
kernel: eth0: interrupt(s) dropped!

None This network chipset isn't supported for the moment

Re: Sad Again: eth0: interrupt(s) dropped! (Michael Brandt)
Date: 2000, Jul 05
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> kernel: pcnet_cs: sorry, the AX88190 chipset is not supported.

That's a hint for you.  These cards have lots of problems with current
drivers.

-- Dave

Question No such file or directory?

Date: 2000, Jun 28
From: John Cusick <zen@sprynet.com>

Am attempting to configure PCMCIA network card and receive following respons to ./network start eth0 command:

  cat: /var/lib/pcmcia/scheme: No such file or directory

Previous cardmgr commands in start up script appear to be successful.

System details: IBM TPAD 770ED, Suse 6.4 upgraded to 2.2.16 kernel, PCMCIA 3.1.17, Intel CardBus 32 Pro100

None Update the PCMCIA init script...

Re: Question No such file or directory? (John Cusick)
Date: 2000, Jul 05
From: David Hinds <dhinds@pcmcia.sourceforge.org>

  mv /etc/rc.d/init.d/pcmcia.N /etc/rc.d/init.d/pcmcia

should do the trick.

-- Dave

Feedback Readonly Variable?

Re: None Update the PCMCIA init script... (David Hinds)
Date: 2000, Jul 06
From: John Cusick <zen@sprynet.com>

I moved /etc/rc.d/init.d/pcmcia.N to /etc/rc.d/init.d/pcmcia. Now the pcmcia module doesn't load. I receive the following message when it fails to load:

  /sbin/init.d/rc2.d/S03pcmcia: SCHEME: readonly variable

I checked S03pcmcia and it links to the new pcmcia script. Do I need to edit the script?

None That message is not an error

Re: Feedback Readonly Variable? (John Cusick)
Date: 2000, Jul 06
From: David Hinds <dhinds@pcmcia.sourceforge.org>

>   /sbin/init.d/rc2.d/S03pcmcia: SCHEME: readonly variable

This is not a failure message.  It is perhaps misleading, but it is
just telling you that you've overridden SCHEME from the boot prompt.

Is this the only PCMCIA message you got?

-- Dave

Feedback Other message is "failed services"

Re: None That message is not an error (David Hinds)
Date: 2000, Jul 06
From: John Cusick <zen@sprynet.com>

Dave,

Yes, that's the only message other than the failed services message:

  Failed services in runlevel 2: pcmcia

Strange, the pcmcia services started fine with the older script, the card was recognized and the "driver" was loaded, just the scheme wasn't recognized. Now, for some reason, the services don't even start.

Note Intel CardBus 32 Works!

Re: Feedback Other message is "failed services" (John Cusick)
Date: 2000, Jul 07
From: John Cusick <zen@sprynet.com>

After some tweaking, I found the following were necessary to get the Intel CardBus card working at 100bT half-duplex:

1) Moved /etc/rc.d/init.d/pcmcia.N to /etc/rc.d/init.d/pcmcia

2) Remarked out "SCHEME=" from etc/rc.d/init.d/pcmcia

3) Forced the card's media type to 100bT half-duplex by adding the following to /etc/pcmcia/config.opts:

	module "tulip_cb" opts "options=3"

Note Addition to config file for IBM EtherJet/Modem combo

Date: 2000, Jul 03
From: Peter A. Friend pafriend

I have an IBM ThinkPad 600X with the 10/100 EtherJet CardBus Ready Port Adapter with 56k Modem. I haven't attempted anything with the modem yet, but I got the NIC to work by adding this line to /etc/pcmcia/config

card "IBM 10/100 EtherJet CardBus Adapter with 56k Modem"
  manfid 0x00a4, 0x0103
  bind "tulip_cb"

I got this info by running:

cardctl ident

This has worked for me on RedHat 6.1 and Mandrake 7.0.

Question Question about Compex Linkport card.

Date: 2000, Jul 06
From: Alexandr Berezniatsky Alexandr

I have pcmcia card -Compex Linkport/ENET-A I would like to install Linux on my PC. So I would like to know if my card works in Linux. Thanks!

None You can check for yourself

Re: Question Question about Compex Linkport card. (Alexandr Berezniatsky)
Date: 2000, Jul 06
From: David Hinds <dhinds@pcmcia.sourceforge.org>

It's on the list of supported cards.

-- Dave

Sad Problems with Compex Linkport

Date: 2000, Jul 09
From: Alexandr Berezniatsky Alexandr

I have pcmcia card -Compex Linkport /ENET-A. (I/O Base Address default 320H,Interrupt default 11) (Linux kernel 2.0.34, PCMCIA package 3.0.0) When I insert my card ,Linux detects it but it detects incorrect card (while booting kernel it is written LinkSys Ethercard 10/100Tbase,I/O=300H,IRQ=3) then system gives information that my card wasn't correctly set. What can be done to solve this problem? Thanks!

None Need more info

Re: Sad Problems with Compex Linkport (Alexandr Berezniatsky)
Date: 2000, Jul 10
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The Compex and Linksys cards are the same card, so it wasn't detected
incorrectly.  I don't know what you mean when you say the "card wasn't
correctly set".  Specific system log messages might be helpful.

-- Dave

Note additional info

Re: None Need more info (David Hinds)
Date: 2000, Jul 10
From: Alexandr Berezniatsky Alexandr

Well,while booting the kernel at the moment of loading pcmcia card I hear one high beep and then one low. Then it is written (Loading device 'eth0'... eth0:NE2000 compatible:port 0x300,IRQ 3 SIOCSIFNETMASK: invalid argument Your ehternet card was not initialized properly)

None Re: Note: additional info

Re: Note additional info (Alexandr Berezniatsky)
Date: 2000, Jul 10
From: David Hinds <dhinds@pcmcia.sourceforge.org>

On Mon, Jul 10, 2000 at 03:31:58PM -0700, Alexandr Berezniatsky wrote:

> SIOCSIFNETMASK: invalid argument

If I had to guess, I'd say you have a mistake in your network
settings.  This error seems to be saying your netmask is bad.

-- Dave

Ok Thanks!!!!:)

Re: None Re: Note: additional info (David Hinds)
Date: 2000, Jul 11
From: Alexandr Berezniatsky Alexandr

My netmask was incorrect ! Now it is ok! And network works! Thanks for your help!:)

Question Psion Gold Card 10-100Mb onto Toshiba(!) 310CDS with Redhad 6.1

Date: 2000, Jul 14
From: Mike Jones nimpo

Looked at SUPPORTED.CARDS for Fast Ethernet Psion Gold Card and found it under driver: smc91c92_cs. Updated to pcmcia-cs-3.1.18 to cope with this card.

But I get "Yikes! bad chip signature" error:
dmesg > dmesg.txt

um... other info:
/sbin/cardctl ident > ident.txt
/sbin/cardctl config > config.txt
/sbin/ifup eth0 > ifup.txt

Oh by the way, have Psion Gold card 56K modem in other slot which still works!

Any suggestions?
Mike.

None Your card is not the same

Re: Question Psion Gold Card 10-100Mb onto Toshiba(!) 310CDS with Redhad 6.1 (Mike Jones)
Date: 2000, Jul 14
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Your card is not compatible with the smc91c92_cs driver (the card you
saw on the SUPPORTED.CARDS list is the Psion Gold Card *NetGlobal*
10/100, and that is not your card).  As a guess, I think you might
have better luck with the pcnet_cs driver.

-- Dave

More It pretends to be a netglobal card.

Re: None Your card is not the same (David Hinds)
Date: 2000, Jul 14
From: Mike Jones nimpo

In-Reply-To: <20000714120009.I10530@valinux.com>

Dave

All the documents that came with the card say netglobal on them and the card has the netglobal logo. I suppose I could have a weird version? (0x016c 0x0023).

Am now attempting to use pcnet_cs but I've hit a hurdle (3 hours ago): I can't find any clues as to the card's hardware ethernet address... any tips?
(All the driver info I can find neatly hides any info which might look like such an address. There are numbers on the card but they're not helpful!)

Mike.

None Re: More: It pretends to be a netglobal card.

Re: More It pretends to be a netglobal card. (Mike Jones)
Date: 2000, Jul 14
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Hmmm, ok, I guess I was wrong.  If it is a NetGlobal card, then it at
least seems to be a new version (you had to modify /etc/pcmcia/config,
right?)

The smc91c92_cs driver did report the card's hw_addr.  The fact that
pcnet_cs didn't find it is one strike against that being the right
driver, but it is still worth a shot.

You might also want to try, with the smc91c92_cs driver, editing
/etc/pcmcia/config.opts to "exclude port 0x100-0x1ff", in case this is
merely an IO port conflict.

-- Dave

Note smb91c92_cs failed with "exclude port 0x100-0x1ff"

Re: None Re: More: It pretends to be a netglobal card. (David Hinds)
Date: 2000, Jul 14
From: Mike Jones nimpo

yes I changed /etc/pcmcia/config :
card "Psion 10-100Mb Ethernet"
  manfid 0x016c, 0x0023
  bind "smc91c92_cs"

Thanks for the pointer to the hardware address! If I get the thing going with pcnet_cs I'll post the fix.

Mike

More No joy yet, small progress

Re: Note smb91c92_cs failed with "exclude port 0x100-0x1ff" (Mike Jones)
Date: 2000, Jul 16
From: Mike Jones nimpo

In-Reply-To: <20000714123609.K10530@valinux.com>

Inching through the windows binaries which came with the card this seems to be oem version of one of the Ositech cards maybe Seven of diamonds, not entirely sure. --Probably why smc91c92_cs driver makes some headway before bailing out.

currently hacking the driver round a bit at the moment to see if i can force it into recognising the card. More anon...

oh... and do you have the hw addresses of any of the Ositech cards currently out, maybe one matches the ositech address on this card 00 c0 e3 0f 70 6e?

Cheers,
Mike

None Oh, of course...

Re: More No joy yet, small progress (Mike Jones)
Date: 2000, Jul 17
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Yes, this is a re-badged Ositech card.  And now that I know that, this
is actually a problem listed in the PCMCIA BUGS file:

o Some Ositech Jack of Diamonds 33.6K modem/ethernet cards don't work
  because of a firmware issue.  With these cards, the smc91c92_cs
  driver reports "Bad chip signature".

  A DOS program to update the card firmware to v8.1B is available from
  Ositech's web site at ftp://www.ositech.com/pub/jod/JDCEL422.EXE

-- Dave

Sad Not Jack of Diamonds ... I thought: 7 of Diamonds (but looks like I'm Wrong)

Re: None Oh, of course... (David Hinds)
Date: 2000, Jul 24
From: Mike Jones nimpo

I wasn't sure about running jack of diamonds firmware update on the netglobal psion 10/100Mb card so I emailed Ositech and Psion for advice. I had these unhelpful replies:

Ositech say:

An Ethernet card does not have 'firmware', so you cannot run a 'firmware update' on it.

Running the Jack of Diamonds firmware update (JDCELLxxx) on any PCCard other than an Ositech Jack of Diamonds could risk damaging that card.

The Psion Netglobal card is not an Ositech Seven of Diamonds. Ositech does manufacture some products under OEM, this is one - you should contact Psion regarding any problems with this card.


Psion say:

Ositech are our technology partners for the gold card netglobal range, however the driver & hardware name of the card are different to an Ositech card.

I am afraid that I cannot recommend that you use a program which may try to overwrite the information on the card changing the card to Ositech card. This may cause the card to stop functioning altogether.


NB

I think there's a wrong tree here and were barking up it: This is not a ethernet/modem card it's just an ethernet card.

.....The Battle continues

Mike

More Summary of what I've done so far (that's not worked)

Re: Sad Not Jack of Diamonds ... I thought: 7 of Diamonds (but looks like I'm Wrong) (Mike Jones)
Date: 2000, Jul 25
From: Mike Jones nimpo

In-Reply-To: <"/pcmcia/network/99/1/1/1/1/1/1/1"@pcmcia.sourceforge.org>

Follow this link to see info posted to comp.os.linux.portable

Mike.

Ok Got it to work Fix enclosed...

Re: More Summary of what I've done so far (that's not worked) (Mike Jones)
Date: 2000, Jul 27
From: Mike Jones nimpo

Finally got it to work.

Please find Info Here

Thanks for all the Pointers
Mike

Question Failure to recognise D-Link DE650

Date: 2000, Jul 17
From: Mike Dwerryhouse MikeDw

I have a Dell XPi100 Laptop, on which I have been running Slackware 3.6 (Kernel 2.0.35, pcmcia-cs 3.0.5) and successfully using a D-Link DE650 Combo card. I have been trying to upgrade to Slack 7.1 (kernel 2.2.16, pcmcia-cs 3.1.16). The card apparently gives no ident string - cardctl ident says "no product info available" on both installations. However, the older system successfully identifies and configures it using pcnet_cs. The new system fails to recognise it.

Can I persuade the new setup to recognise the card ? Perhaps by editing a config file ?. Or can I manually load the drivers. If I do a modprobe pcnet_cs, nothing happens. No eth0 device.

I currently have the system dual booting, so I can try both installations. I also have a modem card which is successfully identified and configured on both setups.

Question Hamlet FE1500 poor performance problem.

Date: 2000, Jul 18
From: Alessandro De Salvo desalvo

I have a brand new Hamlet FE1500 FastEthernet card. It is correctly configured and recognized as a NE2000 compatible ethernet card, using the version 3.1.18 of the pcmcia card services. The problem is that the performance is really bad!!! This means that I cannot achieve more than ~40-50 Kb/sec on a 10Mbits network under Linux. The problem disappear using Windows (~640 Kb/s, which is reasonable), so this is not a problem of my notebook/card. I tried to use the same interrupts and memory addresses as in Windows but it did not work, and the strangest thing is that in Linux the card does not receive any incoming traffic other than its own traffic (that should be not the case since I am connected to a shared network)! Does anyone has a suggestion/solution? Thanks in advance

None Need more detailed information

Re: Question Hamlet FE1500 poor performance problem. (Alessandro De Salvo)
Date: 2000, Jul 18
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Check your system log.  Are you getting "interrupt(s) dropped"
messages, or any other error messages?  And what sort of laptop is
this?

-- Dave

None More informations...

Re: None Need more detailed information (David Hinds)
Date: 2000, Jul 18
From: Alessandro De Salvo desalvo

I see no interrupt drop in my syslog, and no other kind of error coming from the ethernet card. The laptop is an IdeaProgress SX5, Pentium III 700 MHz (Coppermine), with a Texas Instruments PCMCIA.

None Syslog dump

Re: None More informations... (Alessandro De Salvo)
Date: 2000, Jul 20
From: Alessandro De Salvo desalvo

Here it is my syslog dump, but apparently everything is fine!!!

Jul 20 21:06:33 ads pcmcia: Starting PCMCIA services: 
Jul 20 21:06:33 ads pcmcia:  modules 
Jul 20 21:06:33 ads pcmcia:  cardmgr. 
Jul 20 21:06:33 ads rc: Starting pcmcia succeeded 
Jul 20 21:06:33 ads cardmgr[179]: starting, version is 3.1.8 
Jul 20 21:06:33 ads portmap: portmap startup succeeded 
Jul 20 21:06:33 ads sysctl: net.ipv4.ip_forward = 0 
Jul 20 21:06:33 ads sysctl: net.ipv4.conf.all.rp_filter = 1 
Jul 20 21:06:33 ads sysctl: net.ipv4.ip_always_defrag = 0 
Jul 20 21:06:33 ads sysctl: kernel.sysrq = 0 
Jul 20 21:06:33 ads network: Setting network parameters succeeded 
Jul 20 21:06:33 ads cardmgr[179]: initializing socket 0 <30>Jul 20 21:06:33 card
mgr[179]: socket 0: NE2000 Compatible Ethernet Jul 20 21:06:34 ads cardmgr[179]: executing: 'insmod/lib/modules/2.2.16-3/pcmcia/pcnet_cs.o'

Jul 20 21:06:34 ads network: Bringing up interface lo succeeded 
Jul 20 21:06:34 ads ifup: SIOCADDRT: File exists 
Jul 20 21:06:34 ads last message repeated 2 times
Jul 20 21:06:34 ads network: Bringing up interface eth0 succeeded 
Jul 20 21:06:34 ads nfslock: rpc.lockd startup succeeded 
Jul 20 21:06:34 ads nfslock: rpc.statd startup succeeded 

I tried also "test_network", and this is the output:

PCMCIA network settings are coming from linuxconf.

Checking network interface eth0 (pcnet_cs driver):

  Kernel messages for eth0:
  eth0: NE2000 Compatible: io 0x300, irq 9, hw_addr 00:E0:98:34:F0:0A
  eth0: found link beat
  eth0: lost link beat

  Current ifconfig settings:
  eth0      Link encap:Ethernet  HWaddr 00:E0:98:34:F0:0A  
            inet addr:137.138.102.76  Bcast:137.138.255.255  Mask:255.255.0.0
            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
            RX packets:2317 errors:0 dropped:0 overruns:0 frame:0
            TX packets:541 errors:0 dropped:0 overruns:0 carrier:0
            collisions:3 txqueuelen:100 
            Interrupt:9 Base address:0x300 

  The interface is configured and running.
  RX and TX traffic both look ok.

  Enter a numeric IP address to ping: 137.138.1.1

  Pinging 137.138.1.1 ... response received!
  The device interrupt seems to be incrementing normally.

So, what I should conclude from here is that everything is fine, but... still only ~50 Kb/s of transfer rate. Any idea? Thanks

None Maybe a driver upgrade will help

Re: None Syslog dump (Alessandro De Salvo)
Date: 2000, Jul 20
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Can you try upgrading to the latest (3.1.18) PCMCIA driver release?  I
have a suspicion that this might be a problem that is already fixed.

-- Dave

None Upgrade done, but nothing different...

Re: None Maybe a driver upgrade will help (David Hinds)
Date: 2000, Jul 21
From: Alessandro De Salvo desalvo

I tried to upgrade to the lastest pcmcia card services (version 3.1.19, although the cardmgr says 3.1.11!) released yesterday, but the result is always the same, i.e. low transfer rate. I tried also to upgrade my kernel, so now I use the 2.3.99-pre9, but nothing happened. Here I post the syslog dump:

Jul 21 16:04:16 ads kernel: Linux PCMCIA Card Services 3.1.11 
Jul 21 16:04:16 ads kernel:   options:  [pci] [cardbus] [pm] 
Jul 21 16:04:16 ads kernel: Intel PCIC probe:  
Jul 21 16:04:16 ads kernel:   Intel i82365sl DF ISA-to-PCMCIA at port 0x3e0 ofs 0x00, 2 sockets 
Jul 21 16:04:16 ads kernel:     host opts [0]: none 
Jul 21 16:04:16 ads kernel:     host opts [1]: none 
Jul 21 16:04:16 ads kernel:     ISA irqs (scanned) = 3,4,11 polling interval = 1000 ms 
Jul 21 16:04:16 ads cardmgr[751]: starting, version is 3.1.11
Jul 21 16:04:16 ads cardmgr[751]: watching 2 sockets
Jul 21 16:04:16 ads kernel: cs: IO port probe 0x1000-0x17ff: clean. 
Jul 21 16:04:16 ads kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x4d0-0x4d7 
Jul 21 16:04:17 ads cardmgr[751]: initializing socket 0
Jul 21 16:04:17 ads kernel: cs: memory probe 0x0d0000-0x0dffff: clean. 
Jul 21 16:04:17 ads cardmgr[751]: socket 0: Level One 10/100 Fast Ethernet
Jul 21 16:04:17 ads cardmgr[751]: executing: 'modprobe 8390'
Jul 21 16:04:17 ads cardmgr[751]: executing: 'modprobe pcnet_cs'
Jul 21 16:04:17 ads kernel: eth0: NE2000 (DL10019 rev 05): io 0x300, irq 11, hw_addr 00:E0:98:34:F0:0A

Jul 21 16:04:17 ads cardmgr[751]: executing: './network start eth0'
Jul 21 16:05:26 ads sysctl: net.ipv4.ip_forward = 0
Jul 21 16:05:26 ads sysctl: net.ipv4.conf.all.rp_filter = 1
Jul 21 16:05:26 ads sysctl: kernel.sysrq = 0
Jul 21 16:05:26 ads sysctl: error: 'net.ipv4.ip_always_defrag' is an unknown key
Jul 21 16:05:26 ads network: Setting network parameters succeeded
Jul 21 16:05:27 ads network: Bringing up interface lo succeeded
Jul 21 16:05:27 ads network: Bringing up interface eth0 succeeded

...and as usual the test_network script give normal results. ????? Any given help is welcome!!!

Alex

None Back to kernel 2.2.16-3.

Re: None Upgrade done, but nothing different... (Alessandro De Salvo)
Date: 2000, Jul 21
From: Alessandro De Salvo desalvo

Now I'm back to the kernel version 2.2.16-3 (RH 6.2) and the PCMCIA cardmgr now shows the correct version! Anyway the syslog dump is:

Jul 21 19:57:53 ads pcmcia: Starting PCMCIA services: 
Jul 21 19:57:53 ads pcmcia:  modules 
Jul 21 19:57:53 ads pcmcia:  cardmgr. 
Jul 21 19:57:53 ads rc: Starting pcmcia succeeded 
Jul 21 19:57:53 ads cardmgr[179]: starting, version is 3.1.19 
Jul 21 19:57:53 ads portmap: portmap startup succeeded 
Jul 21 19:57:53 ads sysctl: net.ipv4.ip_forward = 0 
Jul 21 19:57:53 ads sysctl: net.ipv4.conf.all.rp_filter = 1 
Jul 21 19:57:53 ads sysctl: net.ipv4.ip_always_defrag = 0 
Jul 21 19:57:53 ads sysctl: kernel.sysrq = 0 
Jul 21 19:57:53 ads network: Setting network parameters succeeded 
Jul 21 19:57:54 ads cardmgr[179]: initializing socket 0 
Jul 21 19:57:54 ads cardmgr[179]: executing: 'modprobe 8390' 
Jul 21 19:57:54 ads cardmgr[179]: executing: './network start eth0' 
Jul 21 19:57:54 ads network: Bringing up interface lo succeeded 
Jul 21 19:57:54 ads network: Bringing up interface eth0 succeeded

i.e., again, no errors, no warnings... and transfer rate always the same!

	Alex

None More syslog + other infos

Re: None Back to kernel 2.2.16-3. (Alessandro De Salvo)
Date: 2000, Jul 21
From: Alessandro De Salvo desalvo

Here it is the *FULL* dump of my syslog, starting from the boot 'till the login:

Jul 21 20:20:42 ads syslog: syslogd startup succeeded
Jul 21 20:20:42 ads kernel: klogd 1.3-3, log source = /proc/kmsg started.
Jul 21 20:20:42 ads syslog: klogd startup succeeded
Jul 21 20:20:42 ads kernel: Inspecting /boot/System.map-2.2.16-3
Jul 21 20:20:43 ads kernel: Loaded 7423 symbols from /boot/System.map-2.2.16-3.
Jul 21 20:20:43 ads kernel: Symbols match kernel version 2.2.16.
Jul 21 20:20:43 ads kernel: Loaded 214 symbols from 12 modules.
Jul 21 20:20:43 ads kernel: Linux version 2.2.16-3 (root@porky.devel.redhat.com)
 (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Mon Jun 19 18
:10:14 EDT 2000 
Jul 21 20:20:43 ads kernel: Detected 701597 kHz processor. 
Jul 21 20:20:43 ads kernel: Console: colour VGA+ 80x25 
Jul 21 20:20:43 ads kernel: Calibrating delay loop... 1399.19 BogoMIPS 
Jul 21 20:20:43 ads kernel: Memory: 127792k/131072k available (1100k kernel code, 416k reserved, 1700k data, 64k init, 0k bigmem) 
Jul 21 20:20:43 ads kernel: Dentry hash table entries: 262144 (order 9, 2048k) 
Jul 21 20:20:43 ads kernel: Buffer cache hash table entries: 131072 (order 7, 512k) 
Jul 21 20:20:43 ads kernel: Page cache hash table entries: 32768 (order 5, 128k) 
Jul 21 20:20:43 ads kernel: VFS: Diskquotas version dquot_6.4.0 initialized 
Jul 21 20:20:43 ads kernel: CPU: Intel Pentium III (Coppermine) stepping 03 
Jul 21 20:20:43 ads kernel: Checking 386/387 coupling... OK, FPU using exception 16 error reporting. 
Jul 21 20:20:43 ads kernel: Checking 'hlt' instruction... OK. 
Jul 21 20:20:43 ads kernel: Checking for popad bug... OK. 
Jul 21 20:20:43 ads kernel: POSIX conformance testing by UNIFIX 
Jul 21 20:20:43 ads kernel: mtrr: v1.35a (19990819) Richard Gooch (rgooch@atnf.csiro.au) 
Jul 21 20:20:43 ads kernel: PCI: PCI BIOS revision 2.10 entry at 0xeb220 
Jul 21 20:20:43 ads kernel: PCI: Using configuration type 1 
Jul 21 20:20:43 ads kernel: PCI: Probing PCI hardware 
Jul 21 20:20:43 ads kernel: Linux NET4.0 for Linux 2.2 
Jul 21 20:20:43 ads kernel: Based upon Swansea University Computer Society NET3.039 
Jul 21 20:20:43 ads kernel: NET4: Unix domain sockets 1.0 for Linux NET4.0. 
Jul 21 20:20:43 ads kernel: NET4: Linux TCP/IP 1.0 for NET4.0 
Jul 21 20:20:43 ads kernel: IP Protocols: ICMP, UDP, TCP, IGMP 
Jul 21 20:20:43 ads kernel: TCP: Hash tables configured (ehash 131072 bhash 65536) 
Jul 21 20:20:43 ads kernel: Initializing RT netlink socket 
Jul 21 20:20:43 ads kernel: Starting kswapd v 1.5  
Jul 21 20:20:43 ads kernel: Detected PS/2 Mouse Port. 
Jul 21 20:20:43 ads kernel: Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ enabled 
Jul 21 20:20:43 ads kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A 
Jul 21 20:20:43 ads kernel: ttyS01 at 0x02f8 (irq = 3) is a 16550A 
Jul 21 20:20:43 ads kernel: pty: 256 Unix98 ptys configured 
Jul 21 20:20:43 ads kernel: apm: BIOS version 1.2 Flags 0x03 (Driver version 1.13) 
Jul 21 20:20:43 ads kernel: Real Time Clock Driver v1.09 
Jul 21 20:20:43 ads kernel: RAM disk driver initialized:  16 RAM disks of 4096K size 
Jul 21 20:20:43 ads kernel: PIIX4: IDE controller on PCI bus 00 dev 39 
Jul 21 20:20:43 ads kernel: PIIX4: not 100% native mode: will probe irqs later 
Jul 21 20:20:43 ads kernel:     ide0: BM-DMA at 0x1100-0x1107, BIOS settings: hda:DMA, hdb:pio 
Jul 21 20:20:43 ads kernel:     ide1: BM-DMA at 0x1108-0x110f, BIOS settings: hdc:DMA, hdd:pio 
Jul 21 20:20:43 ads kernel: hda: FUJITSU MHK2120AT, ATA DISK drive 
Jul 21 20:20:43 ads kernel: hdc: TOSHIBA DVD-ROM SD-C2302, ATAPI CDROM drive 
Jul 21 20:20:43 ads kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 
Jul 21 20:20:43 ads kernel: ide1 at 0x170-0x177,0x376 on irq 15 
Jul 21 20:20:43 ads kernel: hda: FUJITSU MHK2120AT, 11513MB w/512kB Cache, CHS=1467/255/63 
Jul 21 20:20:43 ads kernel: hdc: ATAPI 24X DVD-ROM drive, 128kB Cache 
Jul 21 20:20:43 ads kernel: Uniform CD-ROM driver Revision: 3.10 
Jul 21 20:20:43 ads kernel: Floppy drive(s): fd0 is 1.44M 
Jul 21 20:20:43 ads kernel: FDC 0 is a post-1991 82077 
Jul 21 20:20:43 ads kernel: md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12 
Jul 21 20:20:43 ads kernel: raid5: measuring checksumming speed 
Jul 21 20:20:43 ads kernel: raid5: MMX detected, trying high-speed MMX checksum 
routines 
Jul 21 20:20:43 ads kernel:    pII_mmx   :  1560.957 MB/sec 
Jul 21 20:20:43 ads kernel:    p5_mmx    :  1639.443 MB/sec 
Jul 21 20:20:43 ads kernel:    8regs     :  1205.103 MB/sec 
Jul 21 20:20:43 ads kernel:    32regs    :   685.038 MB/sec 
Jul 21 20:20:43 ads kernel: using fastest function: p5_mmx (1639.443 MB/sec) 
Jul 21 20:20:43 ads kernel: scsi : 0 hosts. 
Jul 21 20:20:43 ads kernel: scsi : detected total. 
Jul 21 20:20:43 ads kernel: md.c: sizeof(mdp_super_t) = 4096 
Jul 21 20:20:43 ads kernel: Partition check: 
Jul 21 20:20:43 ads kernel:  hda: hda1 hda2 hda3 < hda5 hda6 hda7 > 
Jul 21 20:20:43 ads kernel: autodetecting RAID arrays 
Jul 21 20:20:43 ads kernel: autorun ... 
Jul 21 20:20:43 ads kernel: ... autorun DONE. 
Jul 21 20:20:43 ads kernel: VFS: Mounted root (ext2 filesystem) readonly. 
Jul 21 20:20:43 ads kernel: Freeing unused kernel memory: 64k freed 
Jul 21 20:20:43 ads kernel: Adding Swap: 265032k swap-space (priority -1) 
Jul 21 20:20:43 ads kernel: maestro: version 0.14 time 18:13:15 Jun 19 2000 
Jul 21 20:20:43 ads kernel: maestro: Configuring ESS Maestro 2E found at IO 0x3100 IRQ 5
Jul 21 20:20:43 ads kernel: maestro:  subvendor id: 0x31021558 
Jul 21 20:20:43 ads kernel: maestro: not attempting power management. 
Jul 21 20:20:43 ads kernel: maestro: AC97 Codec detected: v: 0x83847600 caps: 0x6940 pwr: 0xf 
Jul 21 20:20:43 ads kernel: maestro: 1 channels configured. 
Jul 21 20:20:43 ads kernel: Linux PCMCIA Card Services 3.1.19 
Jul 21 20:20:43 ads kernel:   kernel build: 2.2.16-3 #1 Mon Jun 19 18:10:14 EDT 2000 
Jul 21 20:20:43 ads kernel:   options:  [pci] [cardbus] [apm] [pnp] 
Jul 21 20:20:43 ads kernel: PCI routing table version 1.0 at 0xfe840 
Jul 21 20:20:43 ads kernel:   00:0a.1 -> irq 10 
Jul 21 20:20:43 ads kernel: PnP: PNP BIOS installation structure at 0xc00ff020 
Jul 21 20:20:43 ads kernel: PnP: PNP BIOS version 1.0, entry at ec000:322d, dseg at ec000 
Jul 21 20:20:43 ads kernel: Intel PCIC probe:  
Jul 21 20:20:43 ads kernel:   TI 1225 rev 01 PCI-to-CardBus at slot 00:0a, mem 0x68000000 
Jul 21 20:20:43 ads kernel:     host opts [0]: [ring] [serial pci & irq] [pci irq 10] [lat 168/176] [bus 32/34] 
Jul 21 20:20:43 ads kernel:     host opts [1]: [ring] [serial pci & irq] [pci irq 10] [lat 168/176] [bus 35/37] 
Jul 21 20:20:43 ads kernel:     ISA irqs (default) = 9,11 PCI status changes
 Jul 21 20:20:43 ads kernel: cs: IO port probe 0x1000-0x17ff: clean. 
Jul 21 20:20:43 ads kernel: cs: IO port probe 0x0100-0x04ff: clean. 
Jul 21 20:20:43 ads kernel: cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa0ffffff 
Jul 21 20:20:43 ads kernel: cs: memory probe 0x60000000-0x60ffffff: clean. 
Jul 21 20:20:43 ads kernel: eth0: NE2000 (DL10022 rev 05): io 0x300, irq 9, hw_addr 00:E0:98:34:F0:0A 
Jul 21 20:20:43 ads kernel: eth0: found link beat 
Jul 21 20:20:43 ads atd: atd startup succeeded
Jul 21 20:19:18 ads rc.sysinit: Mounting proc filesystem succeeded 
Jul 21 20:19:18 ads sysctl: net.ipv4.ip_forward = 0 
Jul 21 20:19:18 ads sysctl: net.ipv4.conf.all.rp_filter = 1 
Jul 21 20:19:18 ads sysctl: net.ipv4.ip_always_defrag = 0 
Jul 21 20:19:18 ads sysctl: kernel.sysrq = 0 
Jul 21 20:19:18 ads rc.sysinit: Configuring kernel parameters succeeded 
Jul 21 20:19:18 ads date: Fri Jul 21 20:19:18 CEST 2000 
Jul 21 20:19:18 ads rc.sysinit: Setting clock : Fri Jul 21 20:19:18 CEST 2000 succeeded 
Jul 21 20:19:18 ads rc.sysinit: Activating swap partitions succeeded 
Jul 21 20:19:18 ads rc.sysinit: Setting hostname ads succeeded 
Jul 21 20:19:18 ads fsck: /dev/hda2: clean, 10423/64128 files, 66393/102414 blocks 
Jul 21 20:19:18 ads rc.sysinit: Checking root filesystem succeeded 
Jul 21 20:19:18 ads rc.sysinit: Remounting root filesystem in read-write mode succeeded 
Jul 21 20:19:22 ads rc.sysinit: Finding module dependencies succeeded 
Jul 21 20:19:23 ads rc.sysinit: Loading sound module (maestro) succeeded 
Jul 21 20:19:23 ads aumix-minimal: vol set to 37, 37 
Jul 21 20:19:23 ads aumix-minimal: pcm set to 87, 87 
Jul 21 20:19:23 ads aumix-minimal: speaker set to 50, 50 
Jul 21 20:19:23 ads aumix-minimal: line set to 50, 50, P 
Jul 21 20:19:23 ads aumix-minimal: mic set to 0, 0, R 
Jul 21 20:19:23 ads aumix-minimal: cd set to 50, 50, P 
Jul 21 20:19:23 ads aumix-minimal: igain set to 50, 50 
Jul 21 20:19:23 ads aumix-minimal: line1 set to 50, 50, P 
Jul 21 20:19:23 ads aumix-minimal: video set to 50, 50, P 
Jul 21 20:19:23 ads rc.sysinit: Loading mixer settings succeeded 
Jul 21 20:19:23 ads fsck: /dev/hda5 has reached maximal mount count, check forced. 
Jul 21 20:20:29 ads fsck: /dev/hda5: 76658/193152 files (0.1% non-contiguous), 346579/393216 blocks 
Jul 21 20:20:29 ads fsck: /dev/hda6: clean, 11599/256000 files, 232806/512064 blocks 
Jul 21 20:20:29 ads rc.sysinit: Checking filesystems succeeded 
Jul 21 20:20:30 ads rc.sysinit: Mounting local filesystems succeeded 
Jul 21 20:20:30 ads rc.sysinit: Turning on user and group quotas for local filesystems succeeded
Jul 21 20:20:31 ads rc.sysinit: Enabling swap space succeeded 
Jul 21 20:20:31 ads init: Entering runlevel: 5 
Jul 21 20:20:40 ads kudzu:  succeeded 
Jul 21 20:20:40 ads pcmcia: Starting PCMCIA services: 
Jul 21 20:20:40 ads pcmcia:  modules 
Jul 21 20:20:41 ads pcmcia:  cardmgr. 
Jul 21 20:20:41 ads rc: Starting pcmcia succeeded 
Jul 21 20:20:41 ads cardmgr[179]: starting, version is 3.1.19 
Jul 21 20:20:41 ads portmap: portmap startup succeeded 
Jul 21 20:20:41 ads sysctl: net.ipv4.ip_forward = 0 
Jul 21 20:20:41 ads sysctl: net.ipv4.conf.all.rp_filter = 1 
Jul 21 20:20:41 ads sysctl: net.ipv4.ip_always_defrag = 0 
Jul 21 20:20:41 ads sysctl: kernel.sysrq = 0 
Jul 21 20:20:41 ads network: Setting network parameters succeeded 
Jul 21 20:20:41 ads cardmgr[179]: initializing socket 0 <30>Jul 21 20:20:41 card
mgr[179]: socket 0: Level One 10/100 Fast Ethernet
Jul 21 20:20:41 ads cardmgr[179]: executing: 'modprobe pcnet_cs' 
Jul 21 20:20:41 ads network: Bringing up interface lo succeeded 
Jul 21 20:20:42 ads network: Bringing up interface eth0 succeeded 
Jul 21 20:20:42 ads nfslock: rpc.lockd startup succeeded 
Jul 21 20:20:42 ads nfslock: rpc.statd startup succeeded 
Jul 21 20:20:42 ads apmd: apmd startup succeeded 
Jul 21 20:20:42 ads apmd[391]: Version 3.0final (APM BIOS 1.2, Linux driver 1.13
) 
Jul 21 20:20:42 ads random: Initializing random number generator succeeded 
Jul 21 20:20:42 ads netfs: Mounting other filesystems succeeded 
Jul 21 20:20:44 ads crond: crond startup succeeded
Jul 21 20:20:45 ads inet: inetd startup succeeded
Jul 21 20:20:45 ads lpd: lpd startup succeeded
Jul 21 20:20:45 ads lpd[507]: restarted
Jul 21 20:20:45 ads keytable: Loading keymap: 
Jul 21 20:20:46 ads keytable: Loading /usr/lib/kbd/keymaps/i386/qwerty/us.kmap.gz
Jul 21 20:20:46 ads keytable: Loading system font: 
Jul 21 20:20:46 ads rc: Starting keytable succeeded
Jul 21 20:20:47 ads sendmail: sendmail startup succeeded
Jul 21 20:20:47 ads gpm: gpm startup succeeded
Jul 21 20:20:48 ads xfs: xfs startup succeeded
Jul 21 20:20:48 ads xfs: Warning: The directory "/usr/share/fonts/default/TrueType" does not exist. 
Jul 21 20:20:48 ads xfs:          Entry deleted from fontpath. 
Jul 21 20:20:49 ads linuxconf: Linuxconf final setup
Jul 21 20:20:51 ads rc: Starting linuxconf succeeded

...a little bit long, but complete. I am connected to a 10baseT network from CERN, in Geneva. It is a full duplex network directly connected to the central switch, used for all the laboratories. I have a static IP for this machine.

		Alex

None The problem appears to be only in RX

Re: None More syslog + other infos (Alessandro De Salvo)
Date: 2000, Jul 24
From: Alessandro De Salvo desalvo

I just discovered that the problem seems to be only in RX, because if I try to ftp from another machine to my machine and try to retrieve a file, the speed is ~630 Kb/s, while the viceversa is only 50 kb/s! Could it be important? Thanks for the help...

		Alex

Sad Strange 10/100 card Allied Telesyn 2800TX

Date: 2000, Jul 21
From: Mircea Ciocan cmircea

	Please help with this card. Is an Allied Telesyn 
AT-2800TX V2 or at leastthat is what the label and windoze reports it.
	But when used with the latest pcmcia code .18, is not recognized and and in syslog there is a record that say:
"Unsuported adapter:
Allied Telesin K. K. CentreCom LA-100-CardBus-T V.2
manfid: 0xc00f, 0x0000 function: 6 (network)"
	And that's it, no intitialization whatsoever, no i/o, irq or memory range, nothing, the dumping tools say, so I can't use tulip-diag program of Donald Becker to see if is tulip compatible card (AT2800 is listed  as supported via tulip_cs driver).
	Now the Telesyn/Telesis K.K. sound dubious to me, maybe is a clone, even was bought from an authorised distributor of AT :( but anyhow, for what is worth, that is the values that windoze allocates for it:

	IRQ=11
	I/O=0x1000-0x107f
	MEM=0x02100000-0x021003ff
	MEM=0x020C000-0x020Cfff
	Is some way of force init the card to try some tulip tests on it or I just bought myself a piece of windoze shit ( misleaded by the fact that is mentioned in compat. list)
	I mention that in the same notebook a 3Com modem 56K works great ( acttualy I was afraid that the modem will be incompatible :)

None Just edit /etc/pcmcia/config

Re: Sad Strange 10/100 card Allied Telesyn 2800TX (Mircea Ciocan)
Date: 2000, Jul 21
From: David Hinds <dhinds@pcmcia.sourceforge.org>

All you need to do is to add an entry to /etc/pcmcia/config using the
strings reported by "cardctl ident", telling cardmgr to load the
tulip_cb driver.  Then see if that works.

-- Dave

Sad MELCO LPC3-TX "eth0: interrupt(s) dropped!"

Date: 2000, Jul 23
From: Gary Chan gchan1

The problem of "eth0: interrupt(s) dropped!" cannot be solved.
I have already tried all the possible solution.
I tried all "irq" and used "do_scan=0" parameters.

I love LINUX and don't want to use MS-Window any more.
PLease help me.
Many thanks.

Hardware:
LAN Card: Buffalo MELCO LPC3-TX PCMCIA NIC 10/100.
Laptop  : NEC VERSA NOTE

The following is syslog dump.
----------------------------------------------
Jul 23 10:00:46 localhost kernel:   kernel build: 2.2.14-1mdklinus #1 Tue Jan 4 21:39:25 CET 2000 
Jul 23 10:00:46 localhost kernel:   options:  [pci] [cardbus] [apm] 
Jul 23 10:00:46 localhost kernel: PCI routing table version 1.0 at 0xfdf70 
Jul 23 10:00:46 localhost kernel: Intel PCIC probe:  
Jul 23 10:00:46 localhost kernel:   TI 1221 rev 00 PCI-to-CardBus at slot 00:0a, mem 0x68000000 
Jul 23 10:00:46 localhost kernel:     host opts [0]: [serial pci & irq] [pci irq 10] [lat 168/176] [bus 32/34] 
Jul 23 10:00:46 localhost kernel:     host opts [1]: [serial pci & irq] [pci irq 10] [lat 168/176] [bus 35/37] 
Jul 23 10:00:46 localhost kernel:     ISA irqs (default) = 3,4,7,9,11 PCI status changes 
Jul 23 10:00:46 localhost cardmgr[3198]: starting, version is 3.1.19
Jul 23 10:00:46 localhost cardmgr[3198]: watching 2 sockets
Jul 23 10:00:46 localhost kernel: cs: IO port probe 0x0100-0x03ff: excluding 0x378-0x37f 
Jul 23 10:00:47 localhost cardmgr[3198]: initializing socket 0
Jul 23 10:00:47 localhost kernel: cs: memory probe 0xa000000-0xa0fffff: clean. 
Jul 23 10:00:47 localhost cardmgr[3198]: socket 0: Melco LPC3-TX Fast Ethernet
Jul 23 10:00:47 localhost cardmgr[3198]: executing: 'modprobe 8390'
Jul 23 10:00:47 localhost cardmgr[3198]: executing: 'modprobe pcnet_cs'
Jul 23 10:00:47 localhost kernel: eth0: NE2000 Compatible: io 0x300, irq 3, hw_addr 00:A0:0C:43:70:AA 
Jul 23 10:00:47 localhost cardmgr[3198]: executing: './network start eth0'
Jul 23 10:00:49 localhost kernel: eth0: interrupt(s) dropped! 
Jul 23 10:00:49 localhost kernel: eth0: Reentering the interrupt handler! isr=0x0 imr=0x0. 
Jul 23 10:00:50 localhost last message repeated 3 times
Jul 23 10:00:54 localhost kernel: eth0: interrupt(s) dropped! 
Jul 23 10:00:54 localhost kernel: eth0: Reentering the interrupt handler! isr=0x0 imr=0x0. 
Jul 23 10:01:00 localhost PAM_pwdb[3224]: (su) session opened for user news by (uid=0)
Jul 23 10:01:00 localhost PAM_pwdb[3224]: (su) session closed for user news
Jul 23 10:01:00 localhost kernel: eth0: interrupt(s) dropped! 
Jul 23 10:01:00 localhost kernel: eth0: Reentering the interrupt handler! isr=0x0 imr=0x0. 
Jul 23 10:01:13 localhost kernel: eth0: interrupt(s) dropped! 
Jul 23 10:01:13 localhost kernel: eth0: Reentering the interrupt handler! isr=0x0 imr=0x0. 
Jul 23 10:01:39 localhost kernel: eth0: interrupt(s) dropped! 
Jul 23 10:01:39 localhost kernel: eth0: Reentering the interrupt handler! isr=0x0 imr=0x0. 
Jul 23 10:01:47 localhost dhcpcd[3217]: timed out waiting for a valid DHCP server response 
Jul 23 10:01:47 localhost cardmgr[3198]: start cmd exited with status 1
------------------------------------------



Best regards.

None It is more than an interrupt issue

Re: Sad MELCO LPC3-TX "eth0: interrupt(s) dropped!" (Gary Chan)
Date: 2000, Jul 24
From: David Hinds <dhinds@pcmcia.sourceforge.org>

On Sun, Jul 23, 2000 at 02:10:37AM -0700, Gary Chan wrote:

> Jul 23 10:00:49 localhost kernel: eth0: interrupt(s) dropped! 
> Jul 23 10:00:49 localhost kernel: eth0: Reentering the interrupt handler! isr=0x0 imr=0x0. 

This card is not supported.  It uses a chipset that is not fully
NE2000 compatible.

-- Dave

Ok Will it be supported in the near future?

Re: None It is more than an interrupt issue (David Hinds)
Date: 2000, Jul 25
From: Gary Chan gchan1

Thank you.

Will the coming release of pcmcia driver support my card?
Look forward your good new.

Best regards,
Gary

None Nope

Re: Ok Will it be supported in the near future? (Gary Chan)
Date: 2000, Jul 25
From: David Hinds <dhinds@pcmcia.sourceforge.org>

That's the short answer.  It is not a simple problem.

-- Dave

Sad Network card doesn't work after warm boot Win98->Linux

Date: 2000, Jul 24
From: Bernd Eggink beggink

My EZ PC Card 10 doesn't come up after a reboot from Win to Linux (SuSE 6.4). It reports an error like

  .../pcmcia/i82365.o: init_module: Device or resource busy

I have to power the notebook off and on again to get it working. No problems with warm boots from Linux to Linux, however. Both Linux and Win98 use IRQ 10. Is there a way to force a "hard reset" of the card during startup?

Thanks, Bernd

None I think this is fixed in the 3.1.19 drivers

Re: Sad Network card doesn't work after warm boot Win98->Linux (Bernd Eggink)
Date: 2000, Jul 24
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Give that a try.

-- Dave

Question NE2000 Compatible Fast Ethernet says: get dev info on socket 1 failed: No such device

Date: 2000, Jul 30
From: Baltasar Parreira Balta

I can't identify the card, the only thing it says on the face of card is: Fast Ethernet PC Card and some picture with E=mc2, no brand, no model, etc, can anyone help me, or have the same card?

None "eth0: Tx hung, 9 vs 0." from NETGEAR FA510c

Date: 2000, Aug 02
From: David Brooks dbrooks

I recently purchased a NETGEAR 510c network adapter. The box it was in actually advertises it as "Linux Compatible", which was a delightfull sight to behold in a mainstream retail establishment!

However, I have had been unable to get it to work. The card is detected fine, although there is no entry for it in the pcmcia configuration file, this is not a problem for it shares the same manfid as both the "UMAX250 Fast Ethernet" and the "Ambicom AMB8100 Fast Ethernet", which both also use the tulip_cb driver.

The card is detected [syslog output provided below], and then delivers the inevitable error of

"eth0: Tx hung, 9 vs. 0. "

After this, an attempt to ping a machine on the network [and this is quite strange] -DOES- suceed in at least lighting the activity lights on the hub... tcpdump run on another system demonstrates that the card is sucessfully sending out ARP requests for the desired system, but it fails to be capable of doing anything else, and after about 6 arp requests, the card then fails altogether and must be ejected+inserted to even do that much again.

And advice would be greatly appreciated. Is it possible that I just have a bad card and should exchange this one? Or should I abbandon hope of cardbus 10/100 on my laptop? [I'm certainly not about to stop running linux ;) ]

For whomever may have any assistance or advice to profer, thank you in advance for your time.

--David Brooks

Aug  2 00:13:45 note kernel: Linux PCMCIA Card Services 3.1.18 
Aug  2 00:13:45 note kernel:   kernel build: 2.2.16 #2 Tue Aug 1 23:28:29 EDT 2000 
Aug  2 00:13:45 note kernel:   options:  [pci] [cardbus] [apm] 
Aug  2 00:13:45 note kernel: PCI routing table version 1.0 at 0xfd3d0 
Aug  2 00:13:45 note kernel: Intel PCIC probe:  
Aug  2 00:13:45 note kernel:   Ricoh RL5C466 rev 02 PCI-to-CardBus at slot 00:13, mem 0xf0000000 
Aug  2 00:13:45 note kernel:     host opts [0]: [io 7/15/2] [mem 3/6/2] [no pci irq] [lat 32/176] [bus 32/34] 
Aug  2 00:13:45 note kernel:     host opts [1]: [io 7/15/2] [mem 3/6/2] [no pci irq] [lat 32/176] [bus 35/37] 
Aug  2 00:13:45 note kernel:     ISA irqs (default) = 3,4,5,7,9,10,11,15 polling interval = 1000 ms 
Aug  2 00:13:46 note cardmgr[601]: starting, version is 3.1.18
Aug  2 00:13:46 note cardmgr[601]: watching 2 sockets
Aug  2 00:13:46 note kernel: cs: IO port probe 0x1000-0x17ff: clean. 
Aug  2 00:13:46 note kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22f 0x2a0-0x2af 0x330-0x337 0x370-0x37f 0x388-0x38
f 0x398-0x39f 0x3e0-0x3e7 0x4d0-0x4d7
Aug  2 00:13:46 note kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
Aug  2 00:14:01 note kernel: cs: cb_alloc(bus 32): vendor 0x1011, device 0x0019 
Aug  2 00:14:01 note cardmgr[601]: initializing socket 0
Aug  2 00:14:01 note cardmgr[601]: socket 0: UMAX Technologies UMAX250 Fast Ethernet
Aug  2 00:14:02 note cardmgr[601]: executing: 'modprobe cb_enabler'
Aug  2 00:14:02 note cardmgr[601]: executing: 'modprobe tulip_cb'
Aug  2 00:14:02 note kernel: cs: cb_config(bus 32) 
Aug  2 00:14:02 note kernel:   fn 0 bar 1: io 0x100-0x17f 
Aug  2 00:14:02 note kernel:   fn 0 bar 2: mem 0x600c0000-0x600c03ff 
Aug  2 00:14:02 note kernel:   fn 0 rom: mem 0x60080000-0x600bffff 
Aug  2 00:14:02 note kernel:   irq 3 
Aug  2 00:14:02 note kernel: tulip_attach(device 20:00.0) 
Aug  2 00:14:02 note kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XI
RCOM CBE, fixed by Doug Ledford)
Aug  2 00:14:02 note kernel: eth0: Digital DS21143 Tulip rev 65 at 0x100, 00:10:7A:15:CB:26, IRQ 3. 
Aug  2 00:14:02 note kernel: eth0:  EEPROM default media type Autosense. 
Aug  2 00:14:02 note kernel: eth0:  Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block. 
Aug  2 00:14:02 note kernel: eth0:  MII transceiver #1 config 1000 status 7849 advertising 01e1. 
Aug  2 00:14:02 note cardmgr[601]: executing: './network start eth0'
Aug  2 00:14:24 note kernel: eth0: Setting full-duplex based on MII#1 link partner capability of 45e1. 
Aug  2 00:14:24 note kernel: eth0: Tx hung, 9 vs. 0. 

None Interrupt setup problem

Re: None "eth0: Tx hung, 9 vs 0." from NETGEAR FA510c (David Brooks)
Date: 2000, Aug 02
From: David Hinds <dhinds@pcmcia.sourceforge.org>

No interrupts are getting through from the card.  It is a problem with
the CardBus bridge configuration, not a problem with the card.

Could you post the output of the "dump_pirq" script from the
debug-tools subdirectory of the PCMCIA package?

I suspect it won't help, but you could also try bumping the card onto
a different interrupt by excluding irq 3 in /etc/pcmcia/config.opts.

-- Dave

Ok Problem solved; card working!

Re: None Interrupt setup problem (David Hinds)
Date: 2000, Aug 03
From: David Brooks dbrooks

 Thank you so very much for the accurate [and very rapid, as well] advice.

And, while I'm at it, I would be amiss to not especially thank you for the excellent and extensive work you have devoted to making linux on laptops a real world phenomena. I hold you within the same pantheon as Linus!

Sure enough, as soon as I looked in /proc/interrupts (at the same time that the card was reported in the syslog by the pcmcia tools at irq5), I noticed that it was not showing up there. Aha! You pointed me in exactly the right direction, and I proceeded to experiment with all of the interrupt options of the i82365 and pcmcia_core modules. [Although I already tried several permutations of "do_scan", "do_pci_probe" "pci_int", I had not been focusing explicitly on an interrupt problem... finally found that PCIC_OPTS="pci_irq_list=5 " and CORE_OPTS="cb_pci_irq=5 " did the trick quite marvelously. Perhaps you might want to provide a more extensive list of errors and their possible implications in the howto.

Oh, also. Minor bug report, unrelated; perhaps you would find it usefull to know that on my system, pcmcia-cs-3.3.8 had never crashed the system, but when I upgraded to pcmcia-cs-3.3.19, it would oops whenever it was called by rc at system boot up. I disabled it and tried a few things before I realized that it would sometimes start fine if I activated the init.d script by hand after the system was up... Weird! So I put a "sleep 1s" command after each insmod of the core modules, and it has worked perfectly and with no oops since then. [Laptop is a pokey old 80586 'pentium', 133Mhz]. It also did this when I was trying v3.3.18.

--David Brooks

...oh, and I do have the output from dump_pirq if you should want it for anything...

---------------------

This is from before the explicit irq=5 configuration, just a fresh install of pcmcia

Interrupt routing table found at address 0xfd3d0:
  Version 1.0, size 0x0060
  Interrupt router is device 00:01.0
  PCI exclusive interrupt mask: 0x0000
  Compatible router: vendor 0x8086 device 0x122e

Device 00:00.0 (slot 0):

Device 00:02.0 (slot 0):
  INTA: link 0x62, irq mask 0x8eb8

Device 00:01.0 (slot 0):

Device 00:13.0 (slot 0):
  INTA: link 0x60, irq mask 0x8eb8
  INTB: link 0x61, irq mask 0x8eb8

Interrupt router at 00:01.0: Intel 82371AB PIIX4/PIIX4E PCI-to-ISA bridge
  PIRQ1 (link 0x60): unrouted
  PIRQ2 (link 0x61): unrouted
  PIRQ3 (link 0x62): unrouted
  PIRQ4 (link 0x63): unrouted
  Serial IRQ: [disabled] [quiet] [frame=21] [pulse=4]

---------

this is from the working card, with the explicit force to irq 5

---------

Interrupt routing table found at address 0xfd3d0:
  Version 1.0, size 0x0060
  Interrupt router is device 00:01.0
  PCI exclusive interrupt mask: 0x0000
  Compatible router: vendor 0x8086 device 0x122e

Device 00:00.0 (slot 0):

Device 00:02.0 (slot 0):
  INTA: link 0x62, irq mask 0x8eb8

Device 00:01.0 (slot 0):

Device 00:13.0 (slot 0):
  INTA: link 0x60, irq mask 0x8eb8
  INTB: link 0x61, irq mask 0x8eb8

Interrupt router at 00:01.0: Intel 82371AB PIIX4/PIIX4E PCI-to-ISA bridge
  PIRQ1 (link 0x60): irq 5
  PIRQ2 (link 0x61): irq 5
  PIRQ3 (link 0x62): unrouted
  PIRQ4 (link 0x63): unrouted
  Serial IRQ: [disabled] [quiet] [frame=21] [pulse=4]

Question Another Netgear FA510c problem

Re: None Interrupt setup problem (David Hinds)
Date: 2000, Aug 08
From: Ed Hill ed9871

I have the same problem as above with a Netgear FA510c, after setup I get "eth0 Tx hung, 9 vs. 0". If I exclude interrupt 3, I get the same message, except its "15 vs. 0" I read the explanation of David's above about how he fixed this but since I am very new to Linux, I am not clear on what exactly I need to do. Any help you could give me would be greatly appreciated.

Ed Hill
ed9871@yahoo.com

Question DLink DFE 660 - Bad performance

Date: 2000, Aug 02
From: hvx

Hi!

Im using a DLink DFE-660 card with is an 100MBit card, but I get only about 200k/s. I tried 2 cards, a new and an old one, neither one of them was faster than that. Apart from that, the card seems to work just fine.

Here is some output from differnt commands, maybe somebody can give me a little advise how to get more speed out of this card. Thank you, M.Melms

Im using linux 2.2.16 with cardmgr 3.1.19.

bobby:~ # ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:50:BA:74:55:50  
          inet addr:192.168.100.80  Bcast:192.168.100.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1362 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2281 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          Interrupt:10 Base address:0x200 

When I put in the card, /var/log/messages sais:

Aug  2 21:53:35 bobby kernel: cs: cb_alloc(bus 35): vendor 0x1011, device 0x0019
Aug  2 21:53:35 bobby cardmgr[78]: initializing socket 1
Aug  2 21:53:35 bobby cardmgr[78]: socket 1: Linksys EtherFast 10/100
Aug  2 21:53:36 bobby cardmgr[78]: executing: 'modprobe cb_enabler'
Aug  2 21:53:36 bobby cardmgr[78]: executing: 'modprobe tulip_cb'
Aug  2 21:53:36 bobby kernel: cs: cb_config(bus 35)
Aug  2 21:53:36 bobby kernel:   fn 0 bar 1: io 0x200-0x27f
Aug  2 21:53:36 bobby kernel:   fn 0 bar 2: mem 0x600c0000-0x600c03ff
Aug  2 21:53:36 bobby kernel:   fn 0 rom: mem 0x60080000-0x600bffff
Aug  2 21:53:36 bobby kernel:   irq 10
Aug  2 21:53:36 bobby kernel: cs: cb_enable(bus 35)
Aug  2 21:53:36 bobby kernel:   bridge io map 0 (flags 0x21): 0x200-0x27f
Aug  2 21:53:36 bobby kernel:   bridge mem map 0 (flags 0x1): 0x60080000-0x600c0
fff
Aug  2 21:53:36 bobby kernel: tulip_attach(device 23:00.0)
Aug  2 21:53:36 bobby kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa
.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledfo rd) Aug 2 21:53:36 bobby kernel: eth0: Digital DS21143 Tulip rev 65 at 0x200, 00:50 :BA:74:55:50, IRQ 10.
Aug  2 21:53:36 bobby kernel: eth0:  EEPROM default media type Autosense.
Aug  2 21:53:36 bobby kernel: eth0:  Index #0 - Media MII (#11) described by a 2
1142 MII PHY (3) block. Aug 2 21:53:36 bobby kernel: eth0: MII transceiver #0 config 3000 status 7809 advertising 01e1. Aug 2 21:53:36 bobby cardmgr[78]: executing: './network start eth0'

None First guess: problem negotiating correct media type

Re: Question DLink DFE 660 - Bad performance
Date: 2000, Aug 02
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Maybe the card is confused about whether this is a full or half duplex
link.  What sort of device are you connecting to?  Hub or switch?  Do
you know if it supports autonegotiation?

Try adding to /etc/pcmcia/config.opts a line like

   module "tulip_cb" opts "options=N"

where N is a number matching your media type, taken from
http://www.scyld.com/network/tulip.html.

-- Dave

Feedback thanks, but it didnt work

Re: None First guess: problem negotiating correct media type (David Hinds)
Date: 2000, Aug 02
From: hvx

> Maybe the card is confused about whether this is a full or half duplex
> link.  

Thats what I though, too, since the LED saying Half/Full Duplex always goes on and off when there is traffic.

> What sort of device are you connecting to? Hub or switch?

Its a micronet switch.

> Do
> you know if it supports autonegotiation?

I have no documentation, so I dont - any way to figure it out ?

> Try adding to /etc/pcmcia/config.opts a line like
> 
>      module "tulip_cb" opts "options=N"

If I do so, the card wont work at all. Even if I put "11" in there, which is the mode the card is usually in, it wont work. The logs dont say much besides

eth0: Using user-specified media MII

and I got a

kernel: eth0: Tx hung, 29 vs. 11.

a few times. Anything else I can try ? thanks, M.Melms

None Re: Feedback: thanks, but it didnt work

Re: Feedback thanks, but it didnt work
Date: 2000, Aug 02
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> kernel: eth0: Tx hung, 29 vs. 11.

Do you ever get this message in normal operation (with no module
options)?  Can you show more of your PCMCIA startup messages (the PCIC
probe, etc)?

Is the 200 kb/sec in both directions?  Does "ifconfig" show lots of
errors of any sort?

Are you using a good (i.e., Category 5) 100baseT cable?

-- Dave

Feedback Re: Feedback: thanks, but it didnt work

Re: None Re: Feedback: thanks, but it didnt work (David Hinds)
Date: 2000, Aug 02
From: hvx

> Do you ever get this message in normal operation (with no 
> module
> options)? 

no, never.

>  Can you show more of your PCMCIA startup messages (the PCIC
> probe, etc)?

like when I start cardmgr ? This would be:

Aug  2 23:19:51 bobby cardmgr[1741]: starting, version is 3.1.19
Aug  2 23:19:51 bobby cardmgr[1741]: watching 2 sockets
Aug  2 23:19:51 bobby kernel: cs: IO port probe 0x1000-0x17ff: clean.
Aug  2 23:19:51 bobby kernel: cs: IO port probe 0x0100-0x04ff: clean.
Aug  2 23:19:51 bobby kernel: cs: IO port probe 0x0a00-0x0aff: clean.

> Is the 200 kb/sec in both directions?

no, its worse ;-) I logged into our server via FTP. When I put a file I get 200K/s When I get a file I get 5 k/s

I noticed that the longer the download takes, the slower the LEDs blink - speed goes down.

>  Does "ifconfig" show lots of
> errors of any sort?
>

 TX packets:888 errors:14 dropped:0 overruns:0 carrier:14
                  collisions:0 txqueuelen:100 

Thats all, after a few MBs traffic.

> Are you using a good (i.e., Category 5) 100baseT cable?

Very good ones. Thanks, M.Melms

Angry pcnet_cs, card works. SLOW!

Date: 2000, Aug 04
From: <jguerin@home.com>

I managed to get my Hawking 10/100 'Fast' ethernet card to work today. The only problem is it's FAR from being fast. Transfer rates on a local LAN usually go about 20-30K/s. SLOW! I saw some people had the same problem before and there was some ugly Windows kludge to get it to work. Unfortunately, I don't have Windows so that's going to be a little harder to fix. I'm hoping maybe somewhere there's a variable or option I can set to fix this problem (sync v. async?). Does anyone know of any such thing? I think I'm using the pcnet_cs module. Everything is stock out of the 3.1.19 (or was it 18) PCMCIA source. HELP please ^_^ muchas gracias. I'd prefer email CCs too, if possible.

Jon

Ok Toshiba Satellite Pro 4200 series, Micronet SP162A ethernet card, Redhat 6.2 - Some thoughts

Date: 2000, Aug 04
From: David Martin dcmartin

This is just a note about my experiences getting things up and going on some brand new (delivered on Monday) hardware. I thought I would post it to "get it on the record"- someone else might mind it useful (or not).

Firstly about the Satellite-Pro 4220 XCDT. Mine has the ToPIC95 (rev 07) bridge chipset, and despite reports of others having problems with Toshiba chipsets, I have had not problems with it (thankfully). Just to add to the confusion I have heard rumours that there are actually several versions of this model - mine is "Made in Europe" with a ToPIC95 and Trident Cyber video adaptor, there is also a "Made in Japan" variant with a ToPIC97 and Savage S3 video adaptor, so go figure. The only thing I had to do was exclude IRQ 9, as I had problems with SanDisk compactflash cards on that IRQ (Microsoft's SanDisk driver also hiccupped on IRQ 9 under windows 98) - something is obviously lurking on the IRQ line. Other than that, plain sailing.

Onto Redhat 6.2. This was my first installation of Redhat, my first installation with pcmcia hardware and my first x86 installation (only ever worked with PPC and Alpha ports in the past). It ships with pcmcia version 3.1.8, but the package is incomplete - it does not contain ide_info, as I discovered when using SanDisk compactflash cards. Also the pcmcia source is included as part of the kernel source rpm, so if you upgarde or replace it (as I did, read on) it technically breaks the rpm. Also, I have to say that I am not too impressed by Redhat's modified pcmcia network startup arrangement, either. I scrapped it in favour of the supplied pcmcia one.

Lastly the card. The Micronet SP162A PCMCIA Fast Ethernet Adaptor (to give it its complete name) was not an adaptor we had seen before and no information was available about what chipset it used. The accompanying driver disk included a README for linux that implied that if you installed the pcmcia system it would work...and it did, kind of. With pcmcia version 3.1.8 cardmgr autodetected it as a "NE2000 compatible" (from the manufacturer ID string, I think) and picked up the pcnet_cs diver. Output from cardctl showed

Socket 1:
  product info: "Dual Speed", "10/100 PC Card", "1.0", " "
  manfid: 0x0149, 0xc1ab
  function: 6 (network)

Configuration worked ok, but the driver did not appear to work correctly - it produced a 'eth0: lost link beat' (from the driver watchdog reset ?) message immediately after carrier was detected on the Lan at 10Mbps. The interface still worked, you could shift packets using known IP addresses, but TX behaviour seemed a bit odd and arp and dns were hung-up somehow. On the assumption that the card/driver marriage was not a happy one, I upgraded to 3.1.15 - it appeared tp contain the most recent version of the pcnet_cs driver. Compilation and installation was a doddle, and the card worked straight away, so I am guessing that it is based on one of the newer D-Link chipsets that have been recently added to the pcnet_cs driver.

So, overall, it was relatively painless exercise. I have to dip my hat to David Hinds and the other developers, the pcmcia system is a neat piece of work that works way better than I expected it would. Cheers, gents (and ladies)!!!



David Martin.

Warning FYI Linksys PCMPC200 V2 card; different from older versions

Date: 2000, Aug 06
From: Nik Conwell nikc

FYI - Be aware that the Linksys EtherFast 10/100 CardBus PCMPC200 has changed and is now V2 which apparently isn't supported yet. The box has blue edges and says something like new V2 in the upper left corner.

Details:

I'm runing RH 6.2, kernel-pcmcia-cs-2.2.16-3.

kernel: Linux PCMCIA Card Services 3.1.8
kernel:   kernel build: 2.2.16-3 #1 Mon Jun 19 18:10:14 EDT 2000
kernel: Intel PCIC probe:
kernel:   Toshiba ToPIC97 PCI-to-CardBus at bus 0 slot 19, mem 0x68000000, 2 sockets
kernel:     host opts [0]: [slot 0xf0] [ccr 0x10] [cdr 0x86] [rcr 0x02] [no pci irq] [l at 168/176] [bus 20/20]
kernel:     host opts [1]: [slot 0xf0] [ccr 0x20] [cdr 0x86] [rcr 0x02] [no pci irq] [l at 168/176] [bus 21/21]
kernel:     ISA irqs (default) = 3,4,5,7,9,10,12 polling interval = 1000 ms
pcmcia: cardmgr. cardmgr[488]: starting, version is 3.1.8 rc: Starting pcmcia succeeded cardmgr[488]: watching 2 sockets
kernel: cs: IO port probe 0x1000-0x17ff: clean.
kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22f 0x330-0x337 0x378-0x37f 0x388-0x38f 0x480-0x48f 0x4d0-0x4d7
kernel: cs: IO port probe 0x0a00-0x0aff: clean.
inet: inetd startup succeeded kernel: cs: cb_alloc(bus 20): vendor 0x13d1, device 0xab02 cardmgr[488]: initializing socket 0 cardmgr[488]: unsupported card in socket 0 cardmgr[488]: product info: "CardBus", "Fast Ethernet", "V1.0", "" cardmgr[488]: manfid: 0x13d1, 0xab02 function: 6 (network)

The manfid is different from the pcmcia config for the EtherFast 10/100. Being a tricky guy, I tried adding an entry for the new manfid, using the tulip_cb driver, and was rewarded with:

kernel: cs: cb_config(bus 20)
kernel:   fn 0 bar 1: io 0xa00-0xaff
kernel:   fn 0 bar 2: mem 0x60060000-0x600603ff
kernel:   fn 0 rom: mem 0x60040000-0x6005ffff
kernel: tulip_attach(bus 20, function 0)
kernel: tulip.c:v0.91 4/14/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
kernel: eth0: Digital DS21143 Tulip rev 17 at 0xa00, 10:80:00:80:00:80, IRQ 3.
kernel: eth0:  EEPROM default media type 10baseT.
kernel: eth0:  MII transceiver #1 config 3000 status 7849 advertising 01e1.
cardmgr[1210]: executing: './network start eth0' pumpd[1242]: starting at (uptime 0 days, 0:18:06) Sat Aug 5 17:59:54 2000
kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000
kernel: current->tss.cr3 = 02721000, %cr3 = 02721000
kernel: *pde = 00000000
kernel: Oops: 0000
kernel: CPU:    0
kernel: EIP:    0010:[lockd:__insmod_lockd_S.bss_L444+161553/21737519]
kernel: EFLAGS: 00010246
kernel: eax: fffffff8   ebx: ffffffff   ecx: 00000000   edx: c3ffab58
kernel: esi: 00000000   edi: c593ada0   ebp: c2723e4c   esp: c2723e00
kernel: ds: 0018   es: 0018   ss: 0018
kernel: Process pump (pid: 1242, process nr: 48, stackpage=c2723000)
kernel: Stack: c593ada0 00000008 00000286 c26e1000 00000246 00000003 00000008 00000000
kernel:        00000000 00000282 c593ada0 c3ffab58 00000a00 c3ffab50 c0383800 00000a00
kernel:        c593ada0 c01ded87 00000214 c2723ea0 c6857c04 c593ada0 00000001 c593ada0
kernel: Call Trace: [__delay+19/40] [lockd:__insmod_lockd_S.bss_L444+160452/21738620] [lockd:__insmod_lockd_S.bss_L444+161399/21737673] [dev_open+32/128] [dev_change_flags+84/264] [devinet_ioctl+635/1536] [sock_ioctl+0/32]
kernel:        [sk_alloc+17/60] [inet_ioctl+402/524] [sock_ioctl+26/32] [sys_ioctl+414/452] [system_call+52/56]
kernel: Code: 8a 06 8b 55 08 88 42 3c 83 7d 0c 00 74 15 8b 45 e8 0f b6 48
cardmgr[1210]: + Determining IP information for eth0... done.

The card wasn't accessible after that...

I took the card back to CompUSA and exchanged it for a not V2 PCMPC200 (which they had tried to unload on me first, but I was too smart for them...). The older PCMPC200 works just fine in my system.

I've sent a copy to the Linksys tech support as well(support@linksys.com)

Keep up the good work. I'm eternally grateful. -nik

nik@bu.edu

None 3COM 3CXFE575BT sending with no flow control?

Date: 2000, Aug 07
From: Roberto Jung Drebes <drebes@aton.inf.ufrgs.br>

Hi there,

My 3CXFE575BT is still crazy when it has to send data in a burst, giving me the "Tx Ring full, refusing to send buffer" error. It works ok when I'm receiving HTTP, FTP traffic, and it's even ok when I'm sending or receiving ssh traffic, but I just need to start a bursty data transfer leaving the machine to get the error. I'm now using pcmcia-cs-3.1.19, kernel 2.2.16, have tried using all combinations of pci_int and pci_csc in PCIC_OPTs, with no success. The brige is: 00:11.0 CardBus bridge: Texas Instruments PCI1220 (rev 02)

Well, first, is there any information I can get from the error message? Like, why the buffer is getting full? I know nothing about TCP, but why isn't the flow control working (I belive there is something like a sliding window in TCP)? Or a debug mode (The i82365 man page says something of pc_debug parameter, but only when the module is compiled with debug info, how do I do it?)

<update>I tried increasing the size of the Tx ring to 32, and the problem still exists, only it takes more time to print the message. I believe that perhaps the card is not receiving some packets, which would contain the acks, and so it cannot advance the ring and queue them again. I will test if I can see all the incoming packets with tcpdump, but it seems difficult. I'm also using debug level 7 now.</update>

If there is no easy fix, and I think it really doesn't have since I'm having this problem for a long time, I would like to have some information on using PCMCIA with 2.3/4 kernels. I remember seeing that some PCMCIA support was included in the kernel in such versions, so does this make the pcmcia-cs useless? Or do they work together? If so, should I do the same, ie, unpack it, ./Configure && make all?

Thanks in advance,

None It is not a flow control issue

Re: None 3COM 3CXFE575BT sending with no flow control? (Roberto Jung Drebes)
Date: 2000, Aug 08
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I can tell you that it is not a TCP flow control issue.  That is a
much higher level activity; the driver doesn't know anything about TCP
windowing.  The issue is that the transmitter is getting stuck... and
the ring is filling up... and when it has refused to accept more
packets for a long enough time interval, the kernel tries to force the
issue, and the driver complains.

Can you post your kernel messages again?  I don't have any older stuff
from you so when you say things are "still" this way, that doesn't
help me.

-- Dave

None Re: It is not a flow control issue

Re: None It is not a flow control issue (David Hinds)
Date: 2000, Aug 08
From: Roberto Jung Drebes <drebes@aton.inf.ufrgs.br>

On Mon, 7 Aug 2000, David Hinds wrote:

> I can tell you that it is not a TCP flow control issue.  That is a
> much higher level activity; the driver doesn't know anything about TCP
> windowing.  The issue is that the transmitter is getting stuck... and
> the ring is filling up... and when it has refused to accept more
> packets for a long enough time interval, the kernel tries to force the
> issue, and the driver complains.
> 
> Can you post your kernel messages again?  I don't have any older stuff
> from you so when you say things are "still" this way, that doesn't
> help me.

Hi,

Here is a copy of what is being logged to kern.*. I added the debug=7
option to the 3c575_cb module. When the transfer begins, a lot of data is
transfered, then soon, the connection starts to "jump": sends a burst of
data, stops for some seconds, another burst, another wait.. I have
included the log up to the point where the ring is full, but it actually
continues in this behavior until the whole file is transfered. I believe
it can be seen in the log when the card is sending and receiving data.

The card is a 3CXFE575BT, the bridge is a TI PCI1220 (PCIC: i82365), the
network has only this two machines (server and client of ftp data), but
the same happens in the university network.

Sorry to include all these logs, but I'm not sure when the data available
is enough.

Also, is this a pcmcia issue or should I seek for help at the vortex list
at scyld.com?

TIA

Aug  7 23:11:32 woodstock kernel: cs: cb_alloc(bus 1): vendor 0x10b7, device 0x5157 
Aug  7 23:11:32 woodstock kernel: 3c59x.c:v0.99Q 5/16/2000 Donald Becker, becker@scyld.com 
Aug  7 23:11:32 woodstock kernel:   http://www.scyld.com/network/vortex.html 
Aug  7 23:11:32 woodstock kernel: cs: cb_config(bus 1) 
Aug  7 23:11:32 woodstock kernel:   fn 0 bar 1: io 0x280-0x2ff 
Aug  7 23:11:32 woodstock kernel:   fn 0 bar 2: mem 0x60021000-0x6002107f 
Aug  7 23:11:32 woodstock kernel:   fn 0 bar 3: mem 0x60020000-0x6002007f 
Aug  7 23:11:32 woodstock kernel:   fn 0 rom: mem 0x60000000-0x6001ffff 
Aug  7 23:11:32 woodstock kernel:   irq 11 
Aug  7 23:11:32 woodstock kernel: cs: cb_enable(bus 1) 
Aug  7 23:11:32 woodstock kernel:   bridge io map 0 (flags 0x21): 0x280-0x2ff 
Aug  7 23:11:32 woodstock kernel:   bridge mem map 0 (flags 0x1): 0x60000000-0x60021fff 
Aug  7 23:11:32 woodstock kernel: vortex_attach(device 01:00.0) 
Aug  7 23:11:32 woodstock kernel: eth0: 3Com 3CCFE575BT Cyclone CardBus at 0x280,  00:00:86:52:a2:c9, IRQ 11 
Aug  7 23:11:32 woodstock kernel:   product code 'NV' rev 07 date 03-10-98 
Aug  7 23:11:32 woodstock kernel: eth0: CardBus functions mapped 60020000->c2282000. 
Aug  7 23:11:32 woodstock kernel:   Internal config register is 600000, transceivers 0x40. 
Aug  7 23:11:32 woodstock kernel:   8K byte-wide RAM 5:3 Rx:Tx split, MII interface. 
Aug  7 23:11:32 woodstock kernel:   MII transceiver found at address 0, status 2809. 
Aug  7 23:11:32 woodstock kernel:   Enabling bus-master transmits and whole-frame receives. 
Aug  7 23:11:32 woodstock kernel: eth0:  Filling in the Rx ring. 
Aug  7 23:11:32 woodstock kernel: eth0: Initial media type MII half-duplex. 
Aug  7 23:11:32 woodstock kernel: eth0: MII #0 status 2809, link partner capability 0000, setting half-duplex. 
Aug  7 23:11:32 woodstock kernel: eth0: vortex_open() irq 11 media status 8000. 
Aug  7 23:11:35 woodstock kernel: eth0: Media selection timer tick happened, MII. 
Aug  7 23:11:35 woodstock kernel: eth0: MII transceiver has status 282d. 
Aug  7 23:11:35 woodstock kernel: eth0: Media selection timer finished, MII. 
Aug  7 23:12:25 woodstock kernel: eth0: Queuing Tx packet, index 0. 
Aug  7 23:12:25 woodstock kernel: eth0: interrupt, status e201, latency 5 ticks. 
Aug  7 23:12:25 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:12:25 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:26 woodstock kernel: eth0: Queuing Tx packet, index 1. 
Aug  7 23:12:26 woodstock kernel: eth0: interrupt, status e201, latency 6 ticks. 
Aug  7 23:12:26 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:12:26 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:26 woodstock kernel: eth0: interrupt, status e401, latency 4 ticks. 
Aug  7 23:12:26 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:12:26 woodstock kernel:   In boomerang_rx(), status e001, rx_status 000a. 
Aug  7 23:12:26 woodstock kernel: Receiving packet size 60 status 803c. 
Aug  7 23:12:26 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:26 woodstock kernel: eth0: Queuing Tx packet, index 2. 
Aug  7 23:12:26 woodstock kernel: eth0: interrupt, status e201, latency 3 ticks. 
Aug  7 23:12:26 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:12:26 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:26 woodstock kernel: eth0: interrupt, status e401, latency 6 ticks. 
Aug  7 23:12:26 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:12:26 woodstock kernel:   In boomerang_rx(), status e001, rx_status 007a. 
Aug  7 23:12:26 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:12:26 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:26 woodstock kernel: eth0: Queuing Tx packet, index 3. 
Aug  7 23:12:26 woodstock kernel: eth0: Queuing Tx packet, index 4. 
Aug  7 23:12:26 woodstock kernel: eth0: interrupt, status e201, latency 5 ticks. 
Aug  7 23:12:26 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:12:26 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:26 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:12:26 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:12:26 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:26 woodstock kernel: eth0: interrupt, status e401, latency 255 ticks. 
Aug  7 23:12:26 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:12:26 woodstock kernel:   In boomerang_rx(), status e001, rx_status 007a. 
Aug  7 23:12:26 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:12:26 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:26 woodstock kernel: eth0: Queuing Tx packet, index 5. 
Aug  7 23:12:26 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:12:26 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:12:26 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:26 woodstock kernel: eth0: interrupt, status e401, latency 4 ticks. 
Aug  7 23:12:27 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:12:27 woodstock kernel:   In boomerang_rx(), status e001, rx_status 007a. 
Aug  7 23:12:27 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:12:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:27 woodstock kernel: eth0: Queuing Tx packet, index 6. 
Aug  7 23:12:27 woodstock kernel: eth0: Queuing Tx packet, index 7. 
Aug  7 23:12:27 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:12:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:12:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:27 woodstock kernel: eth0: Queuing Tx packet, index 8. 
Aug  7 23:12:27 woodstock kernel: eth0: Queuing Tx packet, index 9. 
Aug  7 23:12:27 woodstock kernel: eth0: interrupt, status e201, latency 3 ticks. 
Aug  7 23:12:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:12:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:27 woodstock kernel: eth0: interrupt, status e201, latency 3 ticks. 
Aug  7 23:12:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:12:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:27 woodstock kernel: eth0: interrupt, status e201, latency 3 ticks. 
Aug  7 23:12:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:12:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:27 woodstock kernel: eth0: interrupt, status e401, latency 3 ticks. 
Aug  7 23:12:27 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:12:27 woodstock kernel:   In boomerang_rx(), status e001, rx_status 007a. 
Aug  7 23:12:27 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:12:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:27 woodstock kernel: eth0: Queuing Tx packet, index 10. 
Aug  7 23:12:27 woodstock kernel: eth0: Queuing Tx packet, index 11. 
Aug  7 23:12:27 woodstock kernel: eth0: Queuing Tx packet, index 12. 
Aug  7 23:12:27 woodstock kernel: eth0: interrupt, status e201, latency 3 ticks. 
Aug  7 23:12:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:12:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:27 woodstock kernel: eth0: interrupt, status e201, latency 3 ticks. 
Aug  7 23:12:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:12:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:27 woodstock kernel: eth0: interrupt, status e201, latency 3 ticks. 
Aug  7 23:12:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:12:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:27 woodstock kernel: eth0: interrupt, status e401, latency 3 ticks. 
Aug  7 23:12:27 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:12:27 woodstock kernel:   In boomerang_rx(), status e001, rx_status 007a. 
Aug  7 23:12:27 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:12:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:27 woodstock kernel: eth0: interrupt, status e401, latency 3 ticks. 
Aug  7 23:12:27 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:12:27 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0010. 
Aug  7 23:12:27 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:12:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:27 woodstock kernel: eth0: interrupt, status e401, latency 3 ticks. 
Aug  7 23:12:27 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:12:27 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0010. 
Aug  7 23:12:27 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:12:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:27 woodstock kernel: eth0: interrupt, status e401, latency 3 ticks. 
Aug  7 23:12:27 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:12:27 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0010. 
Aug  7 23:12:27 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:12:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:27 woodstock kernel: eth0: Queuing Tx packet, index 13. 
Aug  7 23:12:27 woodstock kernel: eth0: interrupt, status e201, latency 3 ticks. 
Aug  7 23:12:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:12:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:35 woodstock kernel: eth0: Media selection timer tick happened, MII. 
Aug  7 23:12:35 woodstock kernel: eth0: MII transceiver has status 282d. 
Aug  7 23:12:35 woodstock kernel: eth0: Media selection timer finished, MII. 
Aug  7 23:12:56 woodstock kernel: eth0: interrupt, status e401, latency 6 ticks. 
Aug  7 23:12:56 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:12:56 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0010. 
Aug  7 23:12:56 woodstock kernel: Receiving packet size 74 status 6000804a. 
Aug  7 23:12:56 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:56 woodstock kernel: eth0: Queuing Tx packet, index 14. 
Aug  7 23:12:56 woodstock kernel: eth0: interrupt, status e201, latency 3 ticks. 
Aug  7 23:12:56 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:12:56 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:56 woodstock kernel: eth0: interrupt, status e401, latency 3 ticks. 
Aug  7 23:12:56 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:12:56 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0012. 
Aug  7 23:12:56 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:12:56 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:57 woodstock kernel: eth0: Queuing Tx packet, index 15. 
Aug  7 23:12:57 woodstock kernel: eth0: interrupt, status e201, latency 6 ticks. 
Aug  7 23:12:57 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:12:57 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:57 woodstock kernel: eth0: interrupt, status e401, latency 104 ticks. 
Aug  7 23:12:57 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:12:57 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0015. 
Aug  7 23:12:57 woodstock kernel: Receiving packet size 165 status a00080a5. 
Aug  7 23:12:57 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:57 woodstock kernel: eth0: Queuing Tx packet, index 16. 
Aug  7 23:12:57 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:12:57 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:12:57 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:57 woodstock kernel: eth0: interrupt, status e401, latency 4 ticks. 
Aug  7 23:12:57 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:12:57 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0012. 
Aug  7 23:12:57 woodstock kernel: Receiving packet size 129 status a0008081. 
Aug  7 23:12:57 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:57 woodstock kernel: eth0: Queuing Tx packet, index 17. 
Aug  7 23:12:57 woodstock kernel: eth0: interrupt, status e201, latency 5 ticks. 
Aug  7 23:12:57 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:12:57 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:12:57 woodstock kernel: eth0: interrupt, status e401, latency 4 ticks. 
Aug  7 23:12:57 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:12:57 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0027. 
Aug  7 23:12:57 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:12:57 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:02 woodstock kernel: eth0: interrupt, status e401, latency 5 ticks. 
Aug  7 23:13:02 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:02 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0027. 
Aug  7 23:13:02 woodstock kernel: Receiving packet size 79 status 6000804f. 
Aug  7 23:13:02 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:02 woodstock kernel: eth0: Queuing Tx packet, index 18. 
Aug  7 23:13:02 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:13:02 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:02 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:02 woodstock kernel: eth0: Queuing Tx packet, index 19. 
Aug  7 23:13:02 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:13:02 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:02 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:02 woodstock kernel: eth0: interrupt, status e401, latency 96 ticks. 
Aug  7 23:13:02 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:02 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0019. 
Aug  7 23:13:02 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:13:02 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:07 woodstock kernel: eth0: interrupt, status e401, latency 5 ticks. 
Aug  7 23:13:07 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:07 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0019. 
Aug  7 23:13:07 woodstock kernel: Receiving packet size 79 status 6000804f. 
Aug  7 23:13:07 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:07 woodstock kernel: eth0: Queuing Tx packet, index 20. 
Aug  7 23:13:07 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:13:07 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:07 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:08 woodstock kernel: eth0: Queuing Tx packet, index 21. 
Aug  7 23:13:08 woodstock kernel: eth0: interrupt, status e201, latency 5 ticks. 
Aug  7 23:13:08 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:08 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:08 woodstock kernel: eth0: interrupt, status e401, latency 174 ticks. 
Aug  7 23:13:08 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:08 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0017. 
Aug  7 23:13:08 woodstock kernel: Receiving packet size 72 status 60008048. 
Aug  7 23:13:08 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:08 woodstock kernel: eth0: Queuing Tx packet, index 22. 
Aug  7 23:13:08 woodstock kernel: eth0: interrupt, status e201, latency 3 ticks. 
Aug  7 23:13:08 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:08 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:08 woodstock kernel: eth0: interrupt, status e401, latency 3 ticks. 
Aug  7 23:13:08 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:08 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0015. 
Aug  7 23:13:08 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:13:08 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:12 woodstock kernel: eth0: interrupt, status e401, latency 5 ticks. 
Aug  7 23:13:12 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:12 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0015. 
Aug  7 23:13:12 woodstock kernel: Receiving packet size 74 status 6000804a. 
Aug  7 23:13:12 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:12 woodstock kernel: eth0: Queuing Tx packet, index 23. 
Aug  7 23:13:12 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:13:12 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:12 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:12 woodstock kernel: eth0: interrupt, status e401, latency 4 ticks. 
Aug  7 23:13:12 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:12 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0015. 
Aug  7 23:13:12 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:13:12 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:19 woodstock kernel: eth0: interrupt, status e401, latency 4 ticks. 
Aug  7 23:13:19 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:19 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0015. 
Aug  7 23:13:19 woodstock kernel: Receiving packet size 74 status 6000804a. 
Aug  7 23:13:19 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:19 woodstock kernel: eth0: Queuing Tx packet, index 24. 
Aug  7 23:13:19 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:13:19 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:19 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:19 woodstock kernel: eth0: interrupt, status e401, latency 4 ticks. 
Aug  7 23:13:19 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:19 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0015. 
Aug  7 23:13:19 woodstock kernel: Receiving packet size 90 status 6000805a. 
Aug  7 23:13:19 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:19 woodstock kernel: eth0: Queuing Tx packet, index 25. 
Aug  7 23:13:19 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:13:19 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:19 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:19 woodstock kernel: eth0: interrupt, status e401, latency 18 ticks. 
Aug  7 23:13:19 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:19 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0018. 
Aug  7 23:13:19 woodstock kernel: Receiving packet size 76 status 6000804c. 
Aug  7 23:13:19 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:19 woodstock kernel: eth0: Queuing Tx packet, index 26. 
Aug  7 23:13:19 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:13:19 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:19 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:19 woodstock kernel: eth0: Queuing Tx packet, index 27. 
Aug  7 23:13:19 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:13:19 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:19 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:19 woodstock kernel: eth0: interrupt, status e401, latency 3 ticks. 
Aug  7 23:13:19 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:19 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0012. 
Aug  7 23:13:19 woodstock kernel: Receiving packet size 74 status 6000804a. 
Aug  7 23:13:19 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:19 woodstock kernel: eth0: Queuing Tx packet, index 28. 
Aug  7 23:13:19 woodstock kernel: eth0: interrupt, status e201, latency 3 ticks. 
Aug  7 23:13:19 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:19 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:19 woodstock kernel: eth0: Queuing Tx packet, index 29. 
Aug  7 23:13:19 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:13:19 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:19 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:19 woodstock kernel: eth0: interrupt, status e401, latency 4 ticks. 
Aug  7 23:13:19 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:19 woodstock kernel:   In boomerang_rx(), status e001, rx_status 001d. 
Aug  7 23:13:19 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:13:19 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:19 woodstock kernel: eth0: Queuing Tx packet, index 30. 
Aug  7 23:13:19 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:13:19 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:19 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:19 woodstock kernel: eth0: interrupt, status e401, latency 158 ticks. 
Aug  7 23:13:19 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:19 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0025. 
Aug  7 23:13:19 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:13:19 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:19 woodstock kernel: eth0: Queuing Tx packet, index 31. 
Aug  7 23:13:19 woodstock kernel: eth0: interrupt, status e201, latency 3 ticks. 
Aug  7 23:13:19 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:19 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:19 woodstock kernel: eth0: interrupt, status e401, latency 4 ticks. 
Aug  7 23:13:19 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:19 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0010. 
Aug  7 23:13:19 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:13:19 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:19 woodstock kernel: eth0: interrupt, status e401, latency 4 ticks. 
Aug  7 23:13:19 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:19 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0010. 
Aug  7 23:13:19 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:13:19 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:19 woodstock kernel: eth0: Queuing Tx packet, index 32. 
Aug  7 23:13:19 woodstock kernel: eth0: interrupt, status e201, latency 3 ticks. 
Aug  7 23:13:19 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:19 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:19 woodstock kernel: eth0: Queuing Tx packet, index 33. 
Aug  7 23:13:19 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:13:19 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:19 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:19 woodstock kernel: eth0: interrupt, status e401, latency 103 ticks. 
Aug  7 23:13:19 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:19 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0016. 
Aug  7 23:13:19 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:13:19 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e401, latency 6 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:27 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0016. 
Aug  7 23:13:27 woodstock kernel: Receiving packet size 74 status 6000804a. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 34. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e401, latency 4 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:27 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0015. 
Aug  7 23:13:27 woodstock kernel: Receiving packet size 90 status 6000805a. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 35. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e401, latency 3 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:27 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0018. 
Aug  7 23:13:27 woodstock kernel: Receiving packet size 99 status 60008063. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 36. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e401, latency 3 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:27 woodstock kernel:   In boomerang_rx(), status e001, rx_status 0012. 
Aug  7 23:13:27 woodstock kernel: Receiving packet size 74 status 6000804a. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 37. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 38. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 39. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 40. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e201, latency 5 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e401, latency 4 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:27 woodstock kernel:   In boomerang_rx(), status e001, rx_status 007a. 
Aug  7 23:13:27 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 41. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 42. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e401, latency 3 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:27 woodstock kernel:   In boomerang_rx(), status e001, rx_status 007a. 
Aug  7 23:13:27 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 43. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 44. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 45. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e201, latency 3 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e201, latency 3 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e401, latency 2 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:27 woodstock kernel:   In boomerang_rx(), status e001, rx_status 007a. 
Aug  7 23:13:27 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 46. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 47. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 48. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e201, latency 3 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e201, latency 3 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e201, latency 3 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e401, latency 3 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:27 woodstock kernel:   In boomerang_rx(), status e001, rx_status 007a. 
Aug  7 23:13:27 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 49. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 50. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 51. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:27 woodstock kernel:   In boomerang_rx(), status e001, rx_status 007a. 
Aug  7 23:13:27 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 52. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 53. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 54. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e201, latency 3 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e201, latency 3 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e201, latency 3 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e401, latency 3 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:27 woodstock kernel:   In boomerang_rx(), status e001, rx_status 007a. 
Aug  7 23:13:27 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e401, latency 3 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:27 woodstock kernel:   In boomerang_rx(), status e001, rx_status 007a. 
Aug  7 23:13:27 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e401, latency 3 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:27 woodstock kernel:   In boomerang_rx(), status e001, rx_status 007a. 
Aug  7 23:13:27 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 55. 
Aug  7 23:13:27 woodstock kernel: eth0: interrupt, status e401, latency 5 ticks. 
Aug  7 23:13:27 woodstock kernel: eth0: In interrupt loop, status e401. 
Aug  7 23:13:27 woodstock kernel:   In boomerang_rx(), status e001, rx_status 007a. 
Aug  7 23:13:27 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:13:27 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 56. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 57. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 58. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 59. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 60. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 61. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 62. 
Aug  7 23:13:27 woodstock kernel: eth0: Queuing Tx packet, index 63. 
Aug  7 23:13:34 woodstock kernel: eth0: transmit timed out, tx_status 00 status e000. 
Aug  7 23:13:34 woodstock kernel:   diagnostics: fifo 0000 net 0cc2 dma 000000a0. 
Aug  7 23:13:34 woodstock kernel:   Flags; bus-master 1, full 1; dirty 54 current 64. 
Aug  7 23:13:34 woodstock kernel:   Transmit list 01173270 vs. c1173260. 
Aug  7 23:13:34 woodstock kernel:   0: @c1173200  length 800005ea status 800105ea 
Aug  7 23:13:34 woodstock kernel:   1: @c1173210  length 800005ea status 800105ea 
Aug  7 23:13:34 woodstock kernel:   2: @c1173220  length 800005ea status 800105ea 
Aug  7 23:13:34 woodstock kernel:   3: @c1173230  length 800005ea status 800105ea 
Aug  7 23:13:34 woodstock kernel:   4: @c1173240  length 800005ea status 800105ea 
Aug  7 23:13:34 woodstock kernel:   5: @c1173250  length 800005ea status 800105ea 
Aug  7 23:13:34 woodstock kernel:   6: @c1173260  length 800005ea status 800105ea 
Aug  7 23:13:34 woodstock kernel:   7: @c1173270  length 800005ea status 800005ea 
Aug  7 23:13:35 woodstock kernel:   8: @c1173280  length 800005ea status 800005ea 
Aug  7 23:13:35 woodstock kernel:   9: @c1173290  length 800005ea status 800005ea 
Aug  7 23:13:35 woodstock kernel:   10: @c11732a0  length 800005ea status 800005ea 
Aug  7 23:13:35 woodstock kernel:   11: @c11732b0  length 800005ea status 800005ea 
Aug  7 23:13:35 woodstock kernel:   12: @c11732c0  length 800005ea status 800005ea 
Aug  7 23:13:35 woodstock kernel:   13: @c11732d0  length 800005ea status 800005ea 
Aug  7 23:13:35 woodstock kernel:   14: @c11732e0  length 800005ea status 800005ea 
Aug  7 23:13:35 woodstock kernel:   15: @c11732f0  length 800005ea status 800005ea 
Aug  7 23:13:35 woodstock kernel: eth0: interrupt, status 8401, latency 4 ticks. 
Aug  7 23:13:35 woodstock kernel: eth0: In interrupt loop, status 8401. 
Aug  7 23:13:35 woodstock kernel:   In boomerang_rx(), status 8001, rx_status 0000. 
Aug  7 23:13:35 woodstock kernel: Receiving packet size 66 status 60008042. 
Aug  7 23:13:35 woodstock kernel: eth0: exiting interrupt, status 8000. 
Aug  7 23:13:35 woodstock kernel: eth0: Resetting the Tx ring pointer. 
Aug  7 23:13:35 woodstock kernel: eth0: Queuing Tx packet, index 64. 
Aug  7 23:13:35 woodstock kernel: eth0: Tx Ring full, refusing to send buffer. 
Aug  7 23:13:35 woodstock kernel: eth0: interrupt, status e201, latency 3 ticks. 
Aug  7 23:13:35 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:35 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:35 woodstock kernel: eth0: Queuing Tx packet, index 64. 
Aug  7 23:13:35 woodstock kernel: eth0: interrupt, status e201, latency 4 ticks. 
Aug  7 23:13:35 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:35 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:35 woodstock kernel: eth0: Queuing Tx packet, index 65. 
Aug  7 23:13:35 woodstock kernel: eth0: interrupt, status e201, latency 62 ticks. 
Aug  7 23:13:35 woodstock kernel: eth0: In interrupt loop, status e201. 
Aug  7 23:13:35 woodstock kernel: eth0: exiting interrupt, status e000. 
Aug  7 23:13:35 woodstock kernel: eth0: Queuing Tx packet, index 66. 

In /var/log/messages, many of the following:

Aug  7 23:24:44 woodstock kernel: eth0: transmit timed out, tx_status 00 status e000.
Aug  7 23:24:44 woodstock kernel:   diagnostics: fifo 0000 net 0cc2 dma 000000a0.
Aug  7 23:24:45 woodstock kernel: eth0: Tx Ring full, refusing to send buffer.
Aug  7 23:24:45 woodstock kernel: cket size 66 status 60008042.
Aug  7 23:25:35 woodstock kernel: eth0: transmit timed out, tx_status 00 status e000.
Aug  7 23:25:35 woodstock kernel:   diagnostics: fifo 0000 net 0cc2 dma 000000a0.

The "cket size 66" is weird. There are some other "incomplete" lines in the log.

--
Roberto Jung Drebes <drebes@aton.inf.ufrgs.br>
Porto Alegre, RS - Brasil
http://www.inf.ufrgs.br/~drebes/

Question 3c574 prob, no h/w address

Date: 2000, Aug 08
From: Joerg Schmitz-Linneweber jsl123

I'm trying to use a (no name/oem brand) "Allnet ALL0142+" Fast Ethernet adapter. I tried several modules and decided that the 3c574_cs worked best :-) Indeed it seems to find some config info in the card but no hardware address! I even treied to set it via ifconfig (like someone on the list did) but with no result. To give somemore info: I tried different io ranges and irq's (io > 0x300, io > 0x400, irq=5,9,10). Appended is a log with some kernel info (and debug info from 3c574_cs, this is the reason why cardmgr claims its not the right version). Beside of the pcmcia tools, i used the latest (low-level) drivers. Perhaps I'm only missing a very small thing? BTW: I had to arrange /etc/pcmcia/config and config.opts of course to let cardmgr reco. the card. Did any one know which manufac. uses these id's: 0xffff, 0x021b? BTW2: The last error messages in the log are the results from trying to ping someone on the net. I know it's hard to use a network adapter with a MAC of all zeros but why not give it a try? ;-)

Thanks in advance,
  Joerg

--- schnipp --------------------------------------------

Aug  8 12:28:26 passport kernel: Linux PCMCIA Card Services 3.1.19
Aug  8 12:28:26 passport kernel:   kernel build: 2.2.14 #1 Tue May 9 00:33:32 GMT 2000
Aug  8 12:28:26 passport kernel:   options:  [pci] [cardbus]
Aug  8 12:28:27 passport rcpcmcia: /sbin/insmod /lib/modules/2.2.14/pcmcia/i82365.o
Aug  8 12:28:27 passport kernel: Intel PCIC probe: 
Aug  8 12:28:27 passport kernel:   TI 1131 rev 01 PCI-to-CardBus at slot 00:04, mem 0x68000000
Aug  8 12:28:27 passport kernel:     host opts [0]: [isa irq] [no pci irq] [lat 32/176] [bus 1/1]
Aug  8 12:28:27 passport kernel:     host opts [1]: [isa irq] [no pci irq] [lat 32/176] [bus 2/2]
Aug  8 12:28:27 passport kernel:     ISA irqs (scanned) = 5,9,10,11 status change on irq 11
Aug  8 12:28:27 passport rcpcmcia: /sbin/insmod /lib/modules/2.2.14/pcmcia/ds.o
Aug  8 12:28:27 passport cardmgr[1547]: starting, version is 3.1.16
Aug  8 12:28:27 passport cardmgr[1547]: watching 2 sockets
Aug  8 12:28:27 passport cardmgr[1547]: Card Services release does not match
Aug  8 12:28:27 passport kernel: cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
Aug  8 12:28:27 passport kernel: cs: IO port probe 0x0800-0x08ff: clean.
Aug  8 12:28:27 passport kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x178-0x17f 0x378-0x37f 0x408-0x40f 0x480-0x48f 0x4d0-0x4d7
Aug  8 12:28:27 passport kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Aug  8 12:28:27 passport cardmgr[1547]: initializing socket 0
Aug  8 12:28:27 passport kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
Aug  8 12:28:27 passport cardmgr[1547]: socket 0: Allnet ALL0142+
Aug  8 12:28:27 passport cardmgr[1547]: executing: 'modprobe 3c574_cs pc_debug=255'
Aug  8 12:28:28 passport kernel: 3c574_cs.c v1.08 9/24/98 Donald Becker/David Hinds, becker@cesdis.gsfc.nasa.gov.
Aug  8 12:28:28 passport kernel: 3c574_cs.c 1.000 1998/1/8 Donald Becker, becker@cesdis.gsfc.nasa.gov.
Aug  8 12:28:28 passport kernel: 
Aug  8 12:28:28 passport kernel: 3c574_attach()
Aug  8 12:28:28 passport kernel: 3c574_event(0x000004)
Aug  8 12:28:28 passport kernel: 3c574_config(0xc23d1000)
Aug  8 12:28:28 passport kernel: eth0: Fast-Ethernet at io 0x300, irq 5, hw_addr 00:00:00:00:00:00.
Aug  8 12:28:28 passport kernel:   ASIC rev 0, 16K FIFO split 5:3 Rx:Tx, MII interface.
Aug  8 12:28:28 passport kernel:   MII transceiver at index 1, status 0.
Aug  8 12:28:28 passport kernel:   MII transceiver at index 2, status 0.
Aug  8 12:28:28 passport cardmgr[1547]: executing: './network start eth0'
Aug  8 12:28:28 passport kernel: eth0: opened, status 0000.
Aug  8 12:28:28 passport kernel: eth0: updating the statistics.
Aug  8 12:28:41 passport kernel: eth0: el3_start_xmit(length = 42) called, status 0000.
Aug  8 12:28:41 passport kernel: eth0: transmit error: status 0xff
Aug  8 12:28:41 passport last message repeated 31 times
Aug  8 12:28:48 passport kernel: eth0: Transmit timed out!
Aug  8 12:28:48 passport kernel:   irq status 0000, rx status ffff, tx status ff, tx free 0000
Aug  8 12:28:48 passport kernel:   diagnostics: fifo 0f00 net 4005 ethernet 0000 media ffff
Aug  8 12:28:48 passport kernel: eth0: el3_start_xmit(length = 42) called, status 0000.
Aug  8 12:28:48 passport kernel: eth0: transmit error: status 0xff
--- schnapp ------------------------------------------------

None This is the wrong driver

Re: Question 3c574 prob, no h/w address (Joerg Schmitz-Linneweber)
Date: 2000, Aug 08
From: David Hinds <dhinds@pcmcia.sourceforge.org>

This is 100% certainly not the right driver; but it doesn't do much
checking so it doesn't immediately notice that your card is wrong.
"Generic" cards like this usually use either the pcnet_cs or
smc91c92_cs drivers.  If you've already tried those, then maybe you
are out of luck.

-- Dave

Question Psion GoldCard Cardbus Network adapter problem with Mandrake 7.1

Date: 2000, Aug 10
From: Jan Calmered <jan.calmered@sbs.siemens.se>

I have a new installation of Mandrake 7.1 (RedHat mostly) 
on my mobil, Siemens 510AGP and trying to get a PCMCIA 
Network adapter going (Psion GoldCard 56k + Ethernet, Cardbus)

I am using the 2.2.15 kernel and the 3.1.19 PCMCIA package.

Two problems:

1. After cold boot the system loads the core PCMCIA OK but
not the card driver. checking the card with cardctl status
 show the card to be "busy", ejecting and inserting makes cardctl ident show:
Socket 0:
  product info: "Psion", "10-100Mb MF CardBus", "400062-01C", "123456789abc"
  manfid: 0x016c, 0x0021
  function: 6 (network)
Socket 1:
  no product info available

2. But still no driver loaded as fas as I can see

I have added the card as a "10-100Mb MF Cardbus" in the
config file to bind it to pcnet_cs but no change

There seems to be a failure of IRQ 9 in the log file which 
I have tried to exclude in the config.opts but no change

Enclose is the dmesg, lsmod  output

any clues?

Regards

Jan

dmesg =
Linux version 2.2.15-4mdk (chmou@kenobi.mandrakesoft.com) (gcc version 2.95.3 19991030 (prerelease)) #1 Wed May 10 15:31:30 CEST 2000
Detected 267277459 Hz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 532.48 BogoMIPS
Memory: 192660k/196608k available (1208k kernel code, 416k reserved, 2252k data, 72k init, 0k bigmem)
Dentry hash table entries: 32768 (order 6, 256k)
Buffer cache hash table entries: 262144 (order 8, 1024k)
Page cache hash table entries: 65536 (order 6, 256k)
VFS: Diskquotas version dquot_6.4.0 initialized
CPU: Intel Pentium II (Deschutes) stepping 02
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.35a (19990819) Richard Gooch (rgooch@atnf.csiro.au)
PCI: PCI BIOS revision 2.10 entry at 0xf5200
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Enabling I/O for device 00:3a
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
TCP: Hash tables configured (ehash 262144 bhash 65536)
Initializing RT netlink socket
Starting kswapd v 1.5 
Detected PS/2 Mouse Port.
Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
pty: 256 Unix98 ptys configured
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.12)
Real Time Clock Driver v1.09
RAM disk driver initialized:  16 RAM disks of 4096K size
Uniform Multi-Platform E-IDE driver Revision: 6.30
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xfcd0-0xfcd7, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xfcd8-0xfcdf, BIOS settings: hdc:pio, hdd:pio
hda: TOSHIBA MK1214GAP, ATA DISK drive
hdc: TOSHIBA CD-ROM XM-1602B, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: TOSHIBA MK1214GAP, 11513MB w/0kB Cache, CHS=1467/255/63
hdc: ATAPI 20X CD-ROM drive, 128kB Cache
Uniform CDROM driver Revision: 2.56
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12
raid5: measuring checksumming speed
raid5: MMX detected, trying high-speed MMX checksum routines
   pII_mmx   :   589.407 MB/sec
   p5_mmx    :   615.696 MB/sec
   8regs     :   477.774 MB/sec
   32regs    :   251.841 MB/sec
using fastest function: p5_mmx (615.696 MB/sec)
scsi : 0 hosts.
scsi : detected total.
md.c: sizeof(mdp_super_t) = 4096
Partition check:
 hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 hda10 >
autodetecting RAID arrays
autorun ...
... autorun DONE.
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 72k freed
Adding Swap: 136512k swap-space (priority -1)
usb.c: registered new driver hub
usb.c: registered new driver usb-storage
USB Mass Storage support registered.
usb.c: registered new driver keyboard
cs89x0.c: Module autoprobing not allowed.
cs89x0.c: Append io=0xNNN
Linux PCMCIA Card Services 3.1.19
  kernel build: 2.2.15-4mdk #1 Wed May 10 15:31:30 CEST 2000
  options:  [pci] [cardbus] [apm]
PCI routing table version 1.0 at 0xf57d0
  00:0a.0 -> irq 9
  00:0a.1 -> irq 9
Intel PCIC probe: 
  O2Micro OZ6832/33 rev 02 PCI-to-CardBus at slot 00:0a, mem 0x68000000
    host opts [0]: [pci irq 9] [lat 168/176] [bus 32/34]
    host opts [1]: [pci irq 9] [lat 168/176] [bus 35/37]
    PCI irq 9 test failed
    ISA irqs (default) = 3,4,5,7,11,12 polling interval = 1000 ms
cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
cs: IO port probe 0x0800-0x08ff: excluding 0x800-0x807
cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x207 0x220-0x22f 0x330-0x337 0x378-0x37f 0x388-0x38f 0x398-0x39f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
IrDA (tm) Protocols for Linux-2.2 (Dag Brattli)
cs: socket 0 timed out during reset
usb-uhci.c: $Revision: 1.228 $ time 15:46:55 May 10 2000
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: Intel USB controller: setting latency timer to 0
usb-uhci.c: USB UHCI at I/O 0xfce0, IRQ 10
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
usb.c: USB new device connect, assigned device number 1
hub.c: USB hub found
hub.c: 2 ports detected
cs: socket 0 timed out during reset
unloading PCMCIA Card Services
Linux PCMCIA Card Services 3.1.19
  kernel build: 2.2.15-4mdk #1 Wed May 10 15:31:30 CEST 2000
  options:  [pci] [cardbus] [apm]
PCI routing table version 1.0 at 0xf57d0
Intel PCIC probe: 
  O2Micro OZ6832/33 rev 02 PCI-to-CardBus at slot 00:0a, mem 0x68000000
    host opts [0]: [pci irq 9] [lat 168/176] [bus 32/34]
    host opts [1]: [pci irq 9] [lat 168/176] [bus 35/37]
    PCI irq 9 test failed
    ISA irqs (default) = 3,4,5,7,11 polling interval = 1000 ms
cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
cs: IO port probe 0x0800-0x08ff: excluding 0x800-0x807
cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x207 0x220-0x22f 0x330-0x337 0x378-0x37f 0x388-0x38f 0x398-0x39f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: cb_alloc(bus 32): vendor 0x10b8, device 0x0006
ROM image dump:
  image 0: 0x000000-0x000bff, signature PCIR
epic100.c:v1.07h 8/18/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/epic100.html
cs: cb_config(bus 32)
cs: could not allocate 512 IO ports for CardBus socket 0
cs: cb_release(bus 32)
epic_cb: RequestIO: Out of resource
cs89x0.c: Module autoprobing not allowed.
cs89x0.c: Append io=0xNNN

lsmod =

Module                  Size  Used by
serial_cb               1148   0  (unused)
epic_cb                10440   0  (unused)
cb_enabler              2536   2  [serial_cb epic_cb]
ds                      6440   2  [cb_enabler]
i82365                 22948   2 
pcmcia_core            45856   0  [cb_enabler ds i82365]
soundcore               3748   0  (autoclean) (unused)
usb-uhci               26660   0  (unused)
autofs                  9604   1  (autoclean)
irda                   84289   1 
nls_iso8859-1           2276   4  (autoclean)
nls_cp437               3784   4  (autoclean)
vfat                   11164   4  (autoclean)
fat                    32864   4  (autoclean) [vfat]
keybdev                 1832   0  (unused)
usbkbd                  2292   0  (unused)
input                   2880   0  [keybdev usbkbd]
usb-storage            10120   0  (unused)
usbcore                27236   0  [usb-uhci usbkbd usb-storage]
supermount             15112   2  (autoclean)

None IO port allocation problem

Re: Question Psion GoldCard Cardbus Network adapter problem with Mandrake 7.1 (Jan Calmered)
Date: 2000, Aug 10
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> 
> 2. But still no driver loaded as fas as I can see

Are you sure?  It looks to me like epic_cb and serial_cb were loaded.

> I have added the card as a "10-100Mb MF Cardbus" in the
> config file to bind it to pcnet_cs but no change

That would be wrong; pcnet_cs is a 16-bit driver and won't work with a
CardBus card.  But I think your addition was ignored.

> cs: could not allocate 512 IO ports for CardBus socket 0
> epic_cb: RequestIO: Out of resource

This is your problem.  This card requires a big block of IO ports.
The error message is described in the PCMCIA-HOWTO; the solution is to
add a bigger IO port window to /etc/pcmcia/config.opts, such as:

  include port 0x1000-0x17ff

See if that helps.

-- Dave

Feedback Thanks, allocating more IO helped

Re: None IO port allocation problem (David Hinds)
Date: 2000, Aug 14
From: Jan Calmered <jan.calmered@sbs.siemens.se>

Thank you for your prompt response, like you said allocating a large IO port window helped.

The card seems to be OK now, no errors in logs. I still have problems after cold boot, the card hangs with "busy" from cardctl status, but ejecting/inserting and stop/start pcmcia helps.

Any clue on this?

I have another problem regarding DHCP client, I can't get that to work but will try some documentation on that first

Regards

Jan

Question To quick to be happy, seems to have some IRQ problem still

Re: Feedback Thanks, allocating more IO helped (Jan Calmered)
Date: 2000, Aug 14
From: Jan Calmered <jan.calmered@sbs.siemens.se>

I still seem to have some IRQ problem. I understand that it might be an issue of the CardBus bridge of PCI and ISA.

The driver loads OK, everything seem fine except that I get a timeout trying to use the network, complaints about irq 9 failing. I have tried to set the PCIC_OPTS to irq_mode=0, and to set irq_list to different settings without luck

Below the log and the dump_pirq

Any ideas

Jan

Interrupt routing table found at address 0xf57d0:
  Version 1.0, size 0x00d0
  Interrupt router is device 00:07.0
  PCI exclusive interrupt mask: 0x0000

Device 00:01.0 (slot 0):
  INTA: link 0x60, irq mask 0xdef8
  INTB: link 0x61, irq mask 0xdef8
  INTC: link 0x62, irq mask 0xdef8
  INTD: link 0x63, irq mask 0xdef8

Device 00:07.0 (slot 0):
  INTA: link 0x60, irq mask 0xdef8
  INTB: link 0x61, irq mask 0xdef8
  INTC: link 0x62, irq mask 0xdef8
  INTD: link 0x63, irq mask 0xdef8

Device 00:06.0 (slot 0):

Device 00:0a.0 (slot 0):
  INTA: link 0x60, irq mask 0xdef8
  INTB: link 0x61, irq mask 0xdef8

Device 00:13.0 (slot 0):
  INTA: link 0x60, irq mask 0xdef8
  INTB: link 0x61, irq mask 0xdef8

Device 00:11.0 (slot 0):

Device ff:04.0 (slot 0):

Device ff:06.0 (slot 0):
  INTA: link 0x60, irq mask 0xdef8
  INTB: link 0x61, irq mask 0xdef8

Device ff:05.0 (slot 0):

Device ff:0e.0 (slot 2):
  INTA: link 0x61, irq mask 0xdef8
  INTB: link 0x60, irq mask 0xdef8

Device ff:0f.0 (slot 3):
  INTA: link 0x60, irq mask 0xdef8
  INTB: link 0x61, irq mask 0xdef8

Interrupt router at 00:07.0: Intel 82371AB PIIX4/PIIX4E PCI-to-ISA bridge
  PIRQ1 (link 0x60): irq 9
  PIRQ2 (link 0x61): irq 9
  PIRQ3 (link 0x62): unrouted
  PIRQ4 (link 0x63): irq 10
  Serial IRQ: [disabled] [quiet] [frame=21] [pulse=4]

dmesg

nobi.mandrakesoft.com) (gcc version 2.95.3 19991030 (prerelease)) #1 Wed May 10 15:31:30 CEST 2000
Detected 267277858 Hz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 532.48 BogoMIPS
Memory: 192660k/196608k available (1208k kernel code, 416k reserved, 2252k data, 72k init, 0k bigmem)
Dentry hash table entries: 32768 (order 6, 256k)
Buffer cache hash table entries: 262144 (order 8, 1024k)
Page cache hash table entries: 65536 (order 6, 256k)
VFS: Diskquotas version dquot_6.4.0 initialized
CPU: Intel Pentium II (Deschutes) stepping 02
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.35a (19990819) Richard Gooch (rgooch@atnf.csiro.au)
PCI: PCI BIOS revision 2.10 entry at 0xf5200
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Enabling I/O for device 00:3a
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
TCP: Hash tables configured (ehash 262144 bhash 65536)
Initializing RT netlink socket
Starting kswapd v 1.5 
Detected PS/2 Mouse Port.
Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
pty: 256 Unix98 ptys configured
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.12)
Real Time Clock Driver v1.09
RAM disk driver initialized:  16 RAM disks of 4096K size
Uniform Multi-Platform E-IDE driver Revision: 6.30
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xfcd0-0xfcd7, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xfcd8-0xfcdf, BIOS settings: hdc:pio, hdd:pio
hda: TOSHIBA MK1214GAP, ATA DISK drive
hdc: TOSHIBA CD-ROM XM-1602B, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: TOSHIBA MK1214GAP, 11513MB w/0kB Cache, CHS=1467/255/63
hdc: ATAPI 20X CD-ROM drive, 128kB Cache
Uniform CDROM driver Revision: 2.56
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12
raid5: measuring checksumming speed
raid5: MMX detected, trying high-speed MMX checksum routines
   pII_mmx   :   589.407 MB/sec
   p5_mmx    :   615.696 MB/sec
   8regs     :   477.774 MB/sec
   32regs    :   251.841 MB/sec
using fastest function: p5_mmx (615.696 MB/sec)
scsi : 0 hosts.
scsi : detected total.
md.c: sizeof(mdp_super_t) = 4096
Partition check:
 hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 hda10 >
autodetecting RAID arrays
autorun ...
... autorun DONE.
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 72k freed
Adding Swap: 136512k swap-space (priority -1)
usb.c: registered new driver hub
usb.c: registered new driver usb-storage
USB Mass Storage support registered.
usb.c: registered new driver keyboard
cs89x0.c: Module autoprobing not allowed.
cs89x0.c: Append io=0xNNN
Linux PCMCIA Card Services 3.1.19
  kernel build: 2.2.15-4mdk #1 Wed May 10 15:31:30 CEST 2000
  options:  [pci] [cardbus] [apm]
PCI routing table version 1.0 at 0xf57d0
  00:0a.0 -> irq 9
  00:0a.1 -> irq 9
Intel PCIC probe: 
  O2Micro OZ6832/33 rev 02 PCI-to-CardBus at slot 00:0a, mem 0x68000000
    host opts [0]: [pci irq 9] [lat 168/176] [bus 32/34]
    host opts [1]: [pci irq 9] [lat 168/176] [bus 35/37]
    PCI irq 9 test failed
    ISA irqs (default) = 3,4,5,7,11,12 polling interval = 1000 ms
cs89x0.c: Module autoprobing not allowed.
cs89x0.c: Append io=0xNNN
cs89x0.c: Module autoprobing not allowed.
cs89x0.c: Append io=0xNNN
hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdc: packet command error: error=0x50
ATAPI device hdc:
  Error: Illegal request -- (Sense key=0x05)
  Invalid field in command packet -- (asc=0x24, ascq=0x00)
  The failed "Start Stop Unit" packet command was: 
  "1b 00 00 00 03 00 00 00 00 00 00 00 "
  Error in command packet byte 50047 bit 0
cdrom: open failed.
cs: socket 0 timed out during reset
end_request: I/O error, dev 02:00 (floppy), sector 0
end_request: I/O error, dev 02:00 (floppy), sector 0
end_request: I/O error, dev 02:00 (floppy), sector 0
end_request: I/O error, dev 02:00 (floppy), sector 0
FAT bread failed
cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
cs: IO port probe 0x0800-0x08ff: excluding 0x800-0x807
cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x207 0x220-0x22f 0x330-0x337 0x378-0x37f 0x388-0x38f 0x398-0x39f 0x4d0-0x4d7
cs: IO port probe 0x1000-0x17ff: clean.
cs: IO port probe 0x0a00-0x0aff: clean.
IrDA (tm) Protocols for Linux-2.2 (Dag Brattli)
usb-uhci.c: $Revision: 1.228 $ time 15:46:55 May 10 2000
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: Intel USB controller: setting latency timer to 0
usb-uhci.c: USB UHCI at I/O 0xfce0, IRQ 10
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
usb.c: USB new device connect, assigned device number 1
hub.c: USB hub found
hub.c: 2 ports detected
unloading PCMCIA Card Services
Linux PCMCIA Card Services 3.1.19
  kernel build: 2.2.15-4mdk #1 Wed May 10 15:31:30 CEST 2000
  options:  [pci] [cardbus] [apm]
PCI routing table version 1.0 at 0xf57d0
Intel PCIC probe: 
  O2Micro OZ6832/33 rev 02 PCI-to-CardBus at slot 00:0a, mem 0x68000000
    host opts [0]: [pc/pci] [pci irq 9] [lat 168/176] [bus 32/34]
    host opts [1]: [pc/pci] [pci irq 9] [lat 168/176] [bus 35/37]
    PCI irq 9 test failed
    ISA irqs (default) = 3,4,5,7,11 polling interval = 1000 ms
cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
cs: IO port probe 0x0800-0x08ff: excluding 0x800-0x807
cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x207 0x220-0x22f 0x330-0x337 0x378-0x37f 0x388-0x38f 0x398-0x39f 0x4d0-0x4d7
cs: IO port probe 0x1000-0x17ff: clean.
cs: IO port probe 0x0a00-0x0aff: clean.
cs: socket 0 timed out during reset
unloading PCMCIA Card Services
Linux PCMCIA Card Services 3.1.19
  kernel build: 2.2.15-4mdk #1 Wed May 10 15:31:30 CEST 2000
  options:  [pci] [cardbus] [apm]
PCI routing table version 1.0 at 0xf57d0
Intel PCIC probe: 
  O2Micro OZ6832/33 rev 02 PCI-to-CardBus at slot 00:0a, mem 0x68000000
    host opts [0]: [pc/pci] [pci irq 9] [lat 168/176] [bus 32/34]
    host opts [1]: [pc/pci] [pci irq 9] [lat 168/176] [bus 35/37]
    PCI irq 9 test failed
    ISA irqs (default) = 3,4,5,7,11 polling interval = 1000 ms
cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
cs: IO port probe 0x0800-0x08ff: excluding 0x800-0x807
cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x207 0x220-0x22f 0x330-0x337 0x378-0x37f 0x388-0x38f 0x398-0x39f 0x4d0-0x4d7
cs: IO port probe 0x1000-0x17ff: clean.
cs: IO port probe 0x0a00-0x0aff: clean.
cs: cb_alloc(bus 32): vendor 0x10b8, device 0x0006
ROM image dump:
  image 0: 0x000000-0x000bff, signature PCIR
epic100.c:v1.07h 8/18/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/epic100.html
cs: cb_config(bus 32)
  fn 0 bar 1: io 0x1100-0x11ff
  fn 0 bar 2: mem 0x60041000-0x60041fff
  fn 1 bar 1: io 0x1000-0x10ff
  fn 1 bar 2: mem 0x60040000-0x60040fff
  fn 0 rom: mem 0x60030000-0x6003ffff
  fn 1 rom: mem 0x60020000-0x6002ffff
  irq 3
cs: cb_enable(bus 32)
  bridge io map 0 (flags 0x21): 0x1000-0x11ff
  bridge mem map 0 (flags 0x1): 0x60020000-0x60041fff
epic_attach(bus 32, function 0)
eth0: <NULL> at 0x1100, IRQ 3, 00:60:63:06:40:72.
eth0: MII transceiver #1 control 3100 status 7809.
eth0:  Autonegotiation advertising 01e1 link partner 0000.
serial_attach(device 20:00.1)
tty01 at 0x1000 (irq = 3) is a 16550A

None Try some other irq_mode values

Re: Question To quick to be happy, seems to have some IRQ problem still (Jan Calmered)
Date: 2000, Aug 14
From: David Hinds <dhinds@pcmcia.sourceforge.org>

For the O2Micro bridges, valid values for irq_mode (not documented
yet, unfortunately) are 0, 1, 2, 3, 0x80, 0x81, 0x82, and 0x83.  Try
these, and see if you can get it to stop reporting that the PCI irq
test failed.

-- Dave

None Tried irq_mode=3 and got it to stop complaining about IRQ9 but still not OK

Re: None Try some other irq_mode values (David Hinds)
Date: 2000, Aug 16
From: Jan Calmered <jan.calmered@sbs.siemens.se>

Used irg_mode=3 (for the O2 Micro) now it does not complain about IRQ 9

It still get the card to be busy after reboot, ejecting/inserting a couple of times get it to work OK

But I get cs: socket time out which I think is form the Card ifconfig show it configured OK ( I have tried both fixed and using the dhcpcd)

Am I now on a network config problem? I am using the laptop on the same network with windows and the Psion GoldCard successfully.

If I try to restart the network I get time-out from the dhcpcd if used, otherwise timeout later from a ping I have tested a friends laptop which has a Texas Instrument PCMCIA controller and a 16 bit Xircom on the same network which works fine with the same kernel. He was not too happy to let me install the Psion in his system but maybe I will try that later. I borrowed his Xircom Ethernet 10/100 + Modem 56 and installed in my laptop and I get the same type of time-out. This is not what I want to run but to me it looks like I still have problems with the O2 Micro?

Regards 
Jan
Enclose the dmesg
Linux version 2.2.15-4mdk (chmou@kenobi.mandrakesoft.com) (gcc version 2.95.3 19991030 (prerelease)) #1 Wed May 10 15:31:30 CEST 2000
Detected 267280503 Hz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 532.48 BogoMIPS
Memory: 192660k/196608k available (1208k kernel code, 416k reserved, 2252k data, 72k init, 0k bigmem)
Dentry hash table entries: 32768 (order 6, 256k)
Buffer cache hash table entries: 262144 (order 8, 1024k)
Page cache hash table entries: 65536 (order 6, 256k)
VFS: Diskquotas version dquot_6.4.0 initialized
CPU: Intel Pentium II (Deschutes) stepping 02
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.35a (19990819) Richard Gooch (rgooch@atnf.csiro.au)
PCI: PCI BIOS revision 2.10 entry at 0xf5200
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Enabling I/O for device 00:3a
PCI: Enabling memory for device 00:50
PCI: Enabling memory for device 00:51
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
TCP: Hash tables configured (ehash 262144 bhash 65536)
Initializing RT netlink socket
Starting kswapd v 1.5 
Detected PS/2 Mouse Port.
Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
pty: 256 Unix98 ptys configured
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.12)
Real Time Clock Driver v1.09
RAM disk driver initialized:  16 RAM disks of 4096K size
Uniform Multi-Platform E-IDE driver Revision: 6.30
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xfcd0-0xfcd7, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xfcd8-0xfcdf, BIOS settings: hdc:pio, hdd:pio
hda: TOSHIBA MK1214GAP, ATA DISK drive
hdc: TOSHIBA CD-ROM XM-1602B, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: TOSHIBA MK1214GAP, 11513MB w/0kB Cache, CHS=1467/255/63
hdc: ATAPI 20X CD-ROM drive, 128kB Cache
Uniform CDROM driver Revision: 2.56
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12
raid5: measuring checksumming speed
raid5: MMX detected, trying high-speed MMX checksum routines
   pII_mmx   :   588.645 MB/sec
   p5_mmx    :   616.077 MB/sec
   8regs     :   477.774 MB/sec
   32regs    :   251.841 MB/sec
using fastest function: p5_mmx (616.077 MB/sec)
scsi : 0 hosts.
scsi : detected total.
md.c: sizeof(mdp_super_t) = 4096
Partition check:
 hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 hda10 >
autodetecting RAID arrays
autorun ...
... autorun DONE.
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 72k freed
Adding Swap: 136512k swap-space (priority -1)
usb.c: registered new driver hub
usb.c: registered new driver usb-storage
USB Mass Storage support registered.
usb.c: registered new driver keyboard
cs89x0.c: Module autoprobing not allowed.
cs89x0.c: Append io=0xNNN
Linux PCMCIA Card Services 3.1.19
  kernel build: 2.2.15-4mdk #1 Wed May 10 15:31:30 CEST 2000
  options:  [pci] [cardbus] [apm]
PCI routing table version 1.0 at 0xf57d0
  00:0a.0 -> irq 9
  00:0a.1 -> irq 9
Intel PCIC probe: 
  O2Micro OZ6832/33 rev 02 PCI-to-CardBus at slot 00:0a, mem 0xfecff000
    host opts [0]: [pci only] [pci irq 9] [lat 168/176] [bus 32/34]
    host opts [1]: [pci only] [pci irq 9] [lat 168/176] [bus 35/37]
    ISA irqs (default) = 3,4,5,7,11,12 PCI status changes
cs89x0.c: Module autoprobing not allowed.
cs89x0.c: Append io=0xNNN
cs89x0.c: Module autoprobing not allowed.
cs89x0.c: Append io=0xNNN
hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdc: packet command error: error=0x50
ATAPI device hdc:
  Error: Illegal request -- (Sense key=0x05)
  Invalid field in command packet -- (asc=0x24, ascq=0x00)
  The failed "Start Stop Unit" packet command was: 
  "1b 00 00 00 03 00 00 00 00 00 00 00 "
  Error in command packet byte 50047 bit 0
cdrom: open failed.
end_request: I/O error, dev 02:00 (floppy), sector 0
cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
cs: IO port probe 0x0800-0x08ff: excluding 0x800-0x807
cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x207 0x220-0x22f 0x330-0x337 0x378-0x37f 0x388-0x38f 0x398-0x39f 0x4d0-0x4d7
cs: IO port probe 0x1000-0x17ff: clean.
cs: IO port probe 0x0a00-0x0aff: clean.
IrDA (tm) Protocols for Linux-2.2 (Dag Brattli)
usb-uhci.c: $Revision: 1.228 $ time 15:46:55 May 10 2000
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: Intel USB controller: setting latency timer to 0
usb-uhci.c: USB UHCI at I/O 0xfce0, IRQ 10
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
usb.c: USB new device connect, assigned device number 1
hub.c: USB hub found
hub.c: 2 ports detected
cs: socket 0 timed out during reset
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
end_request: I/O error, dev 02:00 (floppy), sector 0
cs89x0.c: Module autoprobing not allowed.
cs89x0.c: Append io=0xNNN
cs89x0.c: Module autoprobing not allowed.
cs89x0.c: Append io=0xNNN
cs89x0.c: Module autoprobing not allowed.
cs89x0.c: Append io=0xNNN
cs89x0.c: Module autoprobing not allowed.
cs89x0.c: Append io=0xNNN
unloading PCMCIA Card Services
Linux PCMCIA Card Services 3.1.19
  kernel build: 2.2.15-4mdk #1 Wed May 10 15:31:30 CEST 2000
  options:  [pci] [cardbus] [apm]
PCI routing table version 1.0 at 0xf57d0
Intel PCIC probe: 
  O2Micro OZ6832/33 rev 02 PCI-to-CardBus at slot 00:0a, mem 0xfecff000
    host opts [0]: [pci only] [pci irq 9] [lat 168/176] [bus 32/34]
    host opts [1]: [pci only] [pci irq 9] [lat 168/176] [bus 35/37]
    ISA irqs (default) = 3,4,5,7,11 PCI status changes
cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
cs: IO port probe 0x0800-0x08ff: excluding 0x800-0x807
cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x207 0x220-0x22f 0x330-0x337 0x378-0x37f 0x388-0x38f 0x398-0x39f 0x4d0-0x4d7
cs: IO port probe 0x1000-0x17ff: clean.
cs: IO port probe 0x0a00-0x0aff: clean.
cs: socket 0 timed out during reset
cs: cb_alloc(bus 32): vendor 0x10b8, device 0x0006
ROM image dump:
  image 0: 0x000000-0x000bff, signature PCIR
epic100.c:v1.07h 8/18/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/epic100.html
cs: cb_config(bus 32)
  fn 0 bar 1: io 0x1100-0x11ff
  fn 0 bar 2: mem 0x60041000-0x60041fff
  fn 1 bar 1: io 0x1000-0x10ff
  fn 1 bar 2: mem 0x60040000-0x60040fff
  fn 0 rom: mem 0x60030000-0x6003ffff
  fn 1 rom: mem 0x60020000-0x6002ffff
  irq 9
cs: cb_enable(bus 32)
  bridge io map 0 (flags 0x21): 0x1000-0x11ff
  bridge mem map 0 (flags 0x1): 0x60020000-0x60041fff
epic_attach(bus 32, function 0)
eth0: <NULL> at 0x1100, IRQ 9, 00:60:63:06:40:72.
eth0: MII transceiver #1 control 3100 status 7809.
eth0:  Autonegotiation advertising 01e1 link partner 0000.
serial_attach(device 20:00.1)
tty02 at 0x1000 (irq = 9) is a 16550A

None Several issues

Re: None Tried irq_mode=3 and got it to stop complaining about IRQ9 but still not OK (Jan Calmered)
Date: 2000, Aug 16
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Ok, there are several problems here.  I didn't make the epic_cb
connection at first.  The epic_cb driver is broken in the 3.1.19
driver package; get the latest beta from projects.sourceforge.net in
/pub/pcmcia-cs/NEW and that should work better.

Was 0x03 the only irq_mode that did not give a failed PCI irq test?

> cs89x0.c: Module autoprobing not allowed.
> cs89x0.c: Append io=0xNNN

If you have a line in /etc/modules.conf that mentions this cs89x0
driver, remove it.

-- Dave

Ok Ethernet working using 3.1.20 release, still some minor problems

Re: None Several issues (David Hinds)
Date: 2000, Aug 17
From: Jan Calmered <jan.calmered@sbs.siemens.se>

Thanks for your help Yes, the irq_mode=3 was the only one working, tried all you suggested. Also removed the mention of cs89x0 in conf.modules, no complaints about autoprobing now

Downloaded the pcmcia release 3.1.20 from 11th of August and installed, got the ehternet to work OK, the problem remaining is that I still get the card to be busy after a reboot, removing the card, stopping pcmcia services, restarting pcmcia services, inserting card usually gets it to work OK but once the card is working I seem to have good performance and no other issues.

Regards Jan

Question Can use card only once

Date: 2000, Aug 13
From: Maik Hassel Maik

Any of my pcmcia network-cards are correctly detected when iserted at startup. as soon as I eject them and re-insert any card, they are identified as "unknown-memory" cards. Could anybody help me?

None Not enough information to tell anything

Re: Question Can use card only once (Maik Hassel)
Date: 2000, Aug 16
From: David Hinds <dhinds@pcmcia.sourceforge.org>

It might be useful to say what kind of laptop this is, what version of
the PCMCIA tools you've got, and what network cards you're using.
Your system log messages might also help.

-- Dave

None Here it is....

Re: None Not enough information to tell anything (David Hinds)
Date: 2000, Aug 16
From: Maik Hassel Maik

Well, the Laptop is a Panasonic CF-25 and this phenomenon occurs with every network card (I tried several 3Com, one WaveLan silver and bronze and one NE2000 comp. noname card). The phenomenon is allways the same: First time (or after I do a init.d/pcmcia restart) everything is fine, after I eject one card and try to re-insert one (doesn't matter if its the same or another one), I get a low beep/high beep and in the logfiles the card is recognized as a "unknown memory card". Apart from that there`s nothing spezial in the logfiles. The same cards work fine in any combination on another laptop (Dell xyz)

None Still not enough information

Re: None Here it is.... (Maik Hassel)
Date: 2000, Aug 16
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I still don't know what version of the PCMCIA drivers you are using,
and I'd still want to see system log messages.  Whether you think
there is anything special or not.

-- Dave

None Here is all I have...

Re: None Still not enough information (David Hinds)
Date: 2000, Aug 22
From: Maik Hassel Maik

Well, here is the /var/log/messages content, with one card iserted, correctly working, removed and then not working any more...

Aug 11 15:14:34 rthor syslogd 1.3-0: restart.
Aug 11 15:14:36 rthor kernel: klogd 1.3-0, log source = /proc/kmsg started.
Aug 11 15:14:36 rthor kernel: Loaded 3728 symbols from /System.map.
Aug 11 15:14:36 rthor kernel: Symbols match kernel version.
Aug 11 15:14:36 rthor kernel: Linux PCMCIA Card Services 3.0.8
Aug 11 15:14:36 rthor kernel:   kernel build: 2.0.35 #8 Tue Jun 8 15:35:21 MEST 1999
Aug 11 15:14:36 rthor kernel:   options:  [pci] [apm]
Aug 11 15:14:36 rthor kernel: Intel PCIC probe: 
Aug 11 15:14:36 rthor kernel:   Ricoh RL5C466 PCI-to-CardBus at bus 0 slot 16, mem 0xf0002000, 2 sockets
Aug 11 15:14:36 rthor kernel:     host opts [0]: [io 7/15/2] [mem 7/15/2] [no pci irq] [lat 168/176] [bus 32/34]
Aug 11 15:14:36 rthor kernel:     host opts [1]: [io 7/15/2] [mem 7/15/2] [no pci irq] [lat 168/176] [bus 35/37]
Aug 11 15:14:36 rthor kernel:     ISA irqs (scanned) = 9,11 polling interval = 1000 ms
Aug 11 15:14:36 rthor kernel:   Ricoh RL5C466 PCI-to-CardBus at bus 0 slot 19, mem 0xf0000000, 2 sockets
Aug 11 15:14:36 rthor kernel:     host opts [2]: [io 7/15/2] [mem 7/15/2] [no pci irq] [lat 168/176] [bus 38/40]
Aug 11 15:14:36 rthor kernel:     host opts [3]: [io 7/15/2] [mem 7/15/2] [no pci irq] [lat 168/176] [bus 41/43]
Aug 11 15:14:36 rthor kernel:     ISA irqs (default) = 9,11 polling interval = 1000 ms
Aug 11 15:14:36 rthor kernel: cs: IO port probe 0x0100-0x01ff: excluding 0x190-0x19f
Aug 11 15:14:36 rthor kernel: cs: IO port probe 0x0300-0x03ff: excluding 0x300-0x307 0x388-0x38f 0x398-0x39f 0x3b8-0x3e7
Aug 11 15:14:36 rthor kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Aug 11 15:14:36 rthor kernel: cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa0afffff
Aug 11 15:14:36 rthor kernel: eth0: WaveLAN/IEEE, io_addr 0x100, irq 11, mac_address 00:60:1D:1B:DF:90
Aug 11 15:14:38 rthor /usr/sbin/cron[131]: (CRON) STARTUP (fork ok) 
Aug 11 15:14:42 rthor sshd[155]: log: Server listening on port 22.
Aug 11 15:14:42 rthor sshd[155]: log: Generating 768 bit RSA key.
Aug 11 15:14:44 rthor sshd[155]: log: RSA key generation complete.
Aug 11 15:14:45 rthor cardmgr[65]: shutting down socket 0
Aug 11 15:14:45 rthor cardmgr[65]: executing: './network stop eth0'
Aug 11 15:14:46 rthor cardmgr[65]: executing: 'rmmod wavelan2_cs'
Aug 11 15:14:50 rthor cardmgr[65]: initializing socket 0
Aug 11 15:14:50 rthor cardmgr[65]: socket 0: Anonymous Memory
Aug 11 15:14:51 rthor cardmgr[65]: executing: 'insmod /lib/modules/2.0.35/pcmcia/memory_cs.o'
Aug 11 15:14:51 rthor kernel: memory_cs: mem0: anonymous: unknown size
Aug 11 15:14:51 rthor cardmgr[65]: executing: './memory start meAug 11 15:14:34 rthor syslogd 1.3-0: restart.
Aug 11 15:14:36 rthor kernel: klogd 1.3-0, log source = /proc/kmsg started.
Aug 11 15:14:36 rthor kernel: Loaded 3728 symbols from /System.map.
Aug 11 15:14:36 rthor kernel: Symbols match kernel version.
Aug 11 15:14:36 rthor kernel: Linux PCMCIA Card Services 3.0.8
Aug 11 15:14:36 rthor kernel:   kernel build: 2.0.35 #8 Tue Jun 8 15:35:21 MEST 1999
Aug 11 15:14:36 rthor kernel:   options:  [pci] [apm]
Aug 11 15:14:36 rthor kernel: Intel PCIC probe: 
Aug 11 15:14:36 rthor kernel:   Ricoh RL5C466 PCI-to-CardBus at bus 0 slot 16, mem 0xf0002000, 2 sockets
Aug 11 15:14:36 rthor kernel:     host opts [0]: [io 7/15/2] [mem 7/15/2] [no pci irq] [lat 168/176] [bus 32/34]
Aug 11 15:14:36 rthor kernel:     host opts [1]: [io 7/15/2] [mem 7/15/2] [no pci irq] [lat 168/176] [bus 35/37]
Aug 11 15:14:36 rthor kernel:     ISA irqs (scanned) = 9,11 polling interval = 1000 ms
Aug 11 15:14:36 rthor kernel:   Ricoh RL5C466 PCI-to-CardBus at bus 0 slot 19, mem 0xf0000000, 2 sockets
Aug 11 15:14:36 rthor kernel:     host opts [2]: [io 7/15/2] [mem 7/15/2] [no pci irq] [lat 168/176] [bus 38/40]
Aug 11 15:14:36 rthor kernel:     host opts [3]: [io 7/15/2] [mem 7/15/2] [no pci irq] [lat 168/176] [bus 41/43]
Aug 11 15:14:36 rthor kernel:     ISA irqs (default) = 9,11 polling interval = 1000 ms
Aug 11 15:14:36 rthor kernel: cs: IO port probe 0x0100-0x01ff: excluding 0x190-0x19f
Aug 11 15:14:36 rthor kernel: cs: IO port probe 0x0300-0x03ff: excluding 0x300-0x307 0x388-0x38f 0x398-0x39f 0x3b8-0x3e7
Aug 11 15:14:36 rthor kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Aug 11 15:14:36 rthor kernel: cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa0afffff
Aug 11 15:14:36 rthor kernel: eth0: WaveLAN/IEEE, io_addr 0x100, irq 11, mac_address 00:60:1D:1B:DF:90
Aug 11 15:14:38 rthor /usr/sbin/cron[131]: (CRON) STARTUP (fork ok) 
Aug 11 15:14:42 rthor sshd[155]: log: Server listening on port 22.
Aug 11 15:14:42 rthor sshd[155]: log: Generating 768 bit RSA key.
Aug 11 15:14:44 rthor sshd[155]: log: RSA key generation complete.
Aug 11 15:14:45 rthor cardmgr[65]: shutting down socket 0
Aug 11 15:14:45 rthor cardmgr[65]: executing: './network stop eth0'
Aug 11 15:14:46 rthor cardmgr[65]: executing: 'rmmod wavelan2_cs'
Aug 11 15:14:50 rthor cardmgr[65]: initializing socket 0
Aug 11 15:14:50 rthor cardmgr[65]: socket 0: Anonymous Memory
Aug 11 15:14:51 rthor cardmgr[65]: executing: 'insmod /lib/modules/2.0.35/pcmcia/memory_cs.o'
Aug 11 15:14:51 rthor kernel: memory_cs: mem0: anonymous: unknown size
Aug 11 15:14:51 rthor cardmgr[65]: executing: './memory start mem0'
Aug 11 15:14:58 rthor cardmgr[65]: shutting down socket 0
Aug 11 15:14:58 rthor cardmgr[65]: executing: './memory stop mem0'
Aug 11 15:14:58 rthor cardmgr[65]: executing: 'rmmod memory_cs'
Aug 11 15:15:01 rthor cardmgr[65]: initializing socket 0
Aug 11 15:15:01 rthor cardmgr[65]: socket 0: Anonymous Memory
Aug 11 15:15:02 rthor cardmgr[65]: executing: 'insmod /lib/modules/2.0.35/pcmcia/memory_cs.o'
Aug 11 15:15:02 rthor kernel: memory_cs: mem0: anonymous: unknown size
Aug 11 15:15:02 rthor cardmgr[65]: executing: './memory start mem0'
Aug 11 15:15:08 rthor login[160]: ROOT LOGIN on `tty1' 
Aug 11 15:15:19 rthor sshd[155]: log: Received signal 15; terminating.
Aug 11 15:15:21 rthor kernel: Kernel logging (proc) stopped.
Aug 11 15:15:21 rthor syslogd: exiting on signal 15
Aug 13 11:08:18 rthor syslogd 1.3-0: restart. m0'
Aug 11 15:14:58 rthor cardmgr[65]: shutting down socket 0
Aug 11 15:14:58 rthor cardmgr[65]: executing: './memory stop mem0'
Aug 11 15:14:58 rthor cardmgr[65]: executing: 'rmmod memory_cs'
Aug 11 15:15:01 rthor cardmgr[65]: initializing socket 0
Aug 11 15:15:01 rthor cardmgr[65]: socket 0: Anonymous Memory
Aug 11 15:15:02 rthor cardmgr[65]: executing: 'insmod /lib/modules/2.0.35/pcmcia/memory_cs.o'
Aug 11 15:15:02 rthor kernel: memory_cs: mem0: anonymous: unknown size
Aug 11 15:15:02 rthor cardmgr[65]: executing: './memory start mem0'
Aug 11 15:15:08 rthor login[160]: ROOT LOGIN on `tty1' 
Aug 11 15:15:19 rthor sshd[155]: log: Received signal 15; terminating.
Aug 11 15:15:21 rthor kernel: Kernel logging (proc) stopped.
Aug 11 15:15:21 rthor syslogd: exiting on signal 15
Aug 13 11:08:18 rthor syslogd 1.3-0: restart.

None These drivers are too old for submitting a bug report

Re: None Here is all I have... (Maik Hassel)
Date: 2000, Aug 22
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> Aug 11 15:14:36 rthor kernel: Linux PCMCIA Card Services 3.0.8

These PCMCIA drivers are 18 months old.  The current driver release is
3.1.19.  My first suggestion would be that you upgrade and see if the
problem persists.

-- Dave

None Done - no difference

Re: Question Can use card only once (Maik Hassel)
Date: 2000, Sep 05
From: Maik Hassel Maik

Hi!

I downloded the latest package, but theres no effect. Appart from the version numer the log-files look the same.
 Maik

Question IBM EtherJet combo only works after bouncing eth0

Date: 2000, Aug 16
From: Peter A. Friend pafriend

A while back I posted a message saying I had gotten the IBM EtherJet Modem/Ethernet card working by adding the ident string to the /etc/pcmcia/config file. This has been working fine, but since I move around a lot, I have been using scripts after boot-up to up the interface and add the default route.

I recently started using the scheme support, which works great, except that I have to bounce eth0 to get things working. After booting, the ifconfig output looks normal, as does the route table. I can't ping anything. There are 0 errors in /var/log/messages, and the test_network in debug-tools reports nothing abnormal, except that the default gateway cannot be pinged. Again, after a 'ifconfig eth0 down up' everything works flawlessly.

I'm stumped, any ideas on what I should be looking at?

IBM ThinkPad 600X Linux Mandrake 7.0, kernel 2.2.16, pcmcia 3.1.17.

TIA,

Peter Friend

Question DFE-650 Cannot read hardware net address

Date: 2000, Aug 22
From: Ben Marsh blm

I have read all the material I can and fiddled as much as I can and yet I still can't get my DFE-650 pc card working on my laptop. It was identified as Anonymous then I fiddled with the config.opts and get the identity recognised and the correct module loading but I get

pcnet_cs: unable to read net address

I have PC Card Services v3.1.8 Kernel 2.2.14-12 Redhat 6.2 Intel PCIC i82365sl B step ISA-to-PCMCIA at port 0x3e0 ofs 0x00, 2 sockets

Anything else helpful?

None Your workaround didn't work

Re: Question DFE-650 Cannot read hardware net address (Ben Marsh)
Date: 2000, Aug 22
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The anonymous-memory problem was real and modifying the config file
didn't fix it.  The PCMCIA drivers are not able to read any data from
the card... you worked around the card identification issue but the
driver can't read from the card either.

Can you say a bit more about this laptop?  Is it an extremely old
system?  (the Intel i82365sl chip went out of use about 10 years ago).

-- Dave

Question intel pro 10/100/56k combo card

Date: 2000, Aug 22
From: Tim Newsham <newsham@lava.net>

Hi,

   I got a laptop recently with an intel pro 10/100 ethernet
plus 56k modem combo card in it.  This card was not detected
when I installed the redhat-6.2 distribution.  After 
installation I checked and got the following information
about the card:

    product info: "INTEL(R)", "PRO/100 LAN+MODEM56 CARDBUS
                   II", "MBLA3356", "1.00"
    manfid: 0x0089, 0x1103
    function: 6 (network)

This card was not listed in /etc/pcmcia/config, so I added
an entry mimicking the entry for the other manfid for
intel pro/100 lan + modem card.  It tried to load the
xirc* driver, which reported that my card was "an old CE"
card.  I don't know what the old CE card was, or what kind
of driver it woudl take, so I stopped there.

Can anyone suggest something to try at this point?  Is there
a driver that will work with this card?  If so, what kind
of entry do I want to add to the config file?  Has this
already been done in the distribution?  If not, how do I
submit a change once this is working?

Thanks in advance.

                                         Tim N.

None You can't fix this by editing the config file

Re: Question intel pro 10/100/56k combo card (Tim Newsham)
Date: 2000, Aug 22
From: David Hinds <dhinds@pcmcia.sourceforge.org>

These cards use a different chipset, and you don't have the
appropriate driver.  Support for these cards was added in the 3.1.17
PCMCIA driver release; 3.1.19 is current.

-- Dave

None Re: You can't fix this by editing the config file

Re: None You can't fix this by editing the config file (David Hinds)
Date: 2000, Aug 23
From: Tim Newsham <newsham@lava.net>

> These cards use a different chipset, and you don't have the
> appropriate driver.  Support for these cards was added in the 3.1.17
> PCMCIA driver release; 3.1.19 is current.

I just installed 3.1.19.  Unfortunately, it also does not ID my
card correctly.  It has an entry for 0089/0113 intel pro combo,
but not for 0089/1103, which is the ID my card uses.  I hand edited
the config file and duplicated the 0089/0113 entry and adjusted
it for my card, and got partial success:

    tulip_attach(device 20:00.0)
    tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov 
        (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, 
        fixed by Doug Ledford)
    eth0: Digital DS21143 Tulip rev 9 at 0x60061000, EEPROM not present, 
        00:4C:69:6E:75:79, IRQ 11.
    eth0:  Missing EEPROM, this interface may not work correctly!
    eth0: Tx hung, 9 vs. 0.
    eth0: 21140 transmit timed out, status ffffffff, SIA ffffffff 
        ffffffff ffffffff ffffffff, resetting...
    eth0: Tx hung, 10 vs. 0.
    eth0: 21140 transmit timed out, status ffffffff, SIA ffffffff 
        ffffffff ffffffff ffffffff, resetting...
    eth0: Tx hung, 11 vs. 0.
    eth0: 21140 transmit timed out, status ffffffff, SIA ffffffff
         ffffffff ffffffff ffffffff, resetting...
    eth0: Tx hung, 10 vs. 0.

(the errors were reported as the card tried to obtain an IP through
DHCP).  I was not able to perform more testing with a statically
assigned IP since my home network is down at the moment.

Any ideas or suggestions?  Is this yet another rev of the card
that I was so lucky to receive?

> -- Dave

                                             Tim N.

Question Misidentifying 'D-Link DFE-650' as 'KTI Ether-C16'

Date: 2000, Aug 22
From: William Crandall WilliamCrandall

Greetings,

System:	Acer Extensa 710TE 
PCcard:	D-Link DFE-650
[Setup:	Works without a hitch under Win98]

Kernel:	2.2.14 #1 Mon Mar 13 10:54:26 GMT 2000 (Suse 6.4)
Driver:	cardctl version 3.1.19

No changes to /etc/pcmcia or other startup scripts.


Startup (/var/log/messages):

Aug 22 11:10:32 wcra kernel: Linux PCMCIA Card Services 3.1.19
Aug 22 11:10:32 wcra kernel:   kernel build: 2.2.14 #1 Mon Mar 13 10:54:26 GMT 2000
Aug 22 11:10:32 wcra kernel:   options:  [pci] [cardbus] [apm] [pnp]
Aug 22 11:10:32 wcra kernel: PCI routing table version 1.0 at 0xfdf60
Aug 22 11:10:32 wcra kernel:   00:06.0 -> irq 11
Aug 22 11:10:32 wcra kernel:   00:06.1 -> irq 11
Aug 22 11:10:32 wcra kernel: PnP: PNP BIOS installation structure at 0xc00f77b0
Aug 22 11:10:32 wcra kernel: PnP: PNP BIOS version 1.0, entry at f0000:a515, dseg at 400
Aug 22 11:10:32 wcra kernel: Intel PCIC probe: 
Aug 22 11:10:32 wcra kernel:   TI 1250A rev 02 PCI-to-CardBus at slot 00:06, mem 0x68000000
Aug 22 11:10:32 wcra kernel:     host opts [0]: [pci + serial irq] [pci irq 11] [lat 168/176] [bus 32/34]
Aug 22 11:10:32 wcra kernel:     host opts [1]: [pci + serial irq] [pci irq 11] [lat 168/176] [bus 35/37]
Aug 22 11:10:32 wcra kernel:     ISA irqs (scanned) = 9,10 PCI status changes
Aug 22 11:10:32 wcra kernel: cs: IO port probe 0x0c00-0x0cff: clean.
Aug 22 11:10:32 wcra kernel: cs: IO port probe 0x0800-0x08ff: clean.
Aug 22 11:10:32 wcra kernel: cs: IO port probe 0x0100-0x04ff: clean.
Aug 22 11:10:32 wcra kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Aug 22 11:10:32 wcra kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
Aug 22 11:10:32 wcra kernel: eth0: NE2000 (DL10022 rev 30): io 0x300, irq 9, hw_addr 00:E0:98:77:54:FD


Operating info:

bash-2.03# lsmod
Module                  Size  Used by
usb-uhci               17000   0  (unused)
pcnet_cs               10636   0  (unused)
8390                    6228   0  [pcnet_cs]
ds                      6632   2  [pcnet_cs]
i82365                 23392   2 
pcmcia_core            52672   0  [pcnet_cs ds i82365]
serial                 42612   1  (autoclean)
memstat                 1476   0  (unused)
usbcore                42344   1  [usb-uhci]

bash-2.03# cardctl config
Socket 0:
  not configured
Socket 1:
  Vcc 5.0V  Vpp1 0.0V  Vpp2 0.0V
  interface type is "memory and I/O"
  irq 9 [exclusive] [level]
  function 0:
    config base 0x0400
      option 0x60 status 0x00 copy 0x00
    io 0x0300-0x031f [auto]

bash-2.03# cardctl ident
Socket 0:
  no product info available
Socket 1:
  product info: "D-Link", "DFE-650", "Fast Ethernet", "Rev. D1"
  manfid: 0x0149, 0x0230
  function: 6 (network)


This is the *correct* identity.
But no access to the network (ping <server>).

Cardinfo gives a warning; then all fields are blank:

bash-2.03# cardinfo
Card Services release does not match!       

Resetting the card controller:

bash-2.03# cardctl suspend
bash-2.03# cardctl reset

	... generates these /var/log/messages:

Aug 22 11:37:16 wcra cardmgr[80]: executing: './network suspend eth0'
Aug 22 11:37:32 wcra cardmgr[80]: shutting down socket 1
Aug 22 11:37:32 wcra cardmgr[80]: executing: './network stop eth0'
Aug 22 11:37:32 wcra cardmgr[80]: executing: 'modprobe -r pcnet_cs'
Aug 22 11:37:32 wcra cardmgr[80]: executing: 'modprobe -r 8390'
Aug 22 11:37:32 wcra cardmgr[80]: initializing socket 1
Aug 22 11:37:32 wcra cardmgr[80]: socket 1: KTI ETHER-C16 Fast ethernet
Aug 22 11:37:33 wcra cardmgr[80]: executing: 'modprobe 8390'
Aug 22 11:37:33 wcra cardmgr[80]: executing: 'modprobe pcnet_cs'
Aug 22 11:37:33 wcra kernel: eth0: NE2000 (DL10022 rev 30): io 0x300, irq 9, hw_addr 00:E0:98:77:54:FD
Aug 22 11:37:33 wcra cardmgr[80]: executing: './network start eth0'

So it seems the 'KTI ETHER-C-16' driver is installed, 
but cardctl still thinks its the 'D-Link':

bash-2.03# date
Tue Aug 22 11:44:38 CEST 2000
bash-2.03# cardctl ident
Socket 0:
  no product info available
Socket 1:
  product info: "D-Link", "DFE-650", "Fast Ethernet", "Rev. D1"
  manfid: 0x0149, 0x0230
  function: 6 (network)


Thanks in advance for any suggestions.

Regards,

William BC Crandall
Wiesbaden . Germany
wcra@beest.midat.de  and/or
crandall@wiesbaden.vistec.net

None The correct driver *is* loaded

Re: Question Misidentifying 'D-Link DFE-650' as 'KTI Ether-C16' (William Crandall)
Date: 2000, Aug 22
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You can ignore the "KTI" thing: there are several cards with the same
manufacturer ID's, and someone submitted the KTI name first, so that
is what is in /etc/pcmcia/config.  It is the same card with a
different sticker on top.  The DFE-650 cards do work with this driver
release.

Your messages all look good to me.  When you try to use the network,
what happens, exactly?  Do you get any additional system log messages?

> But no access to the network (ping <server>).

What does that mean, exactly?  Can you run the "test_network" script
in the debug-tools subdirectory of the PCMCIA source package?

-- Dave

Question Compex Linkport/TX32 and EEPROM

Date: 2000, Aug 26
From: Marco Dubbeld marco

When I insert my Linkport TX32 card cardmgr reports in messages:

cardmgr[9623]: initializing socket 0
cardmgr[9623]: socket 0: Compex LinkPort/TX32A
kernel: cs: cb_alloc(bus 32): vendor 0x10ec, device 0x8138
cardmgr[9623]: executing: 'modprobe cb_enabler'
cardmgr[9623]: executing: 'modprobe tulip_cb 10baseT debu
kernel: fn 0 bar 1: io 0xa00-0xaff
kernel: fn 0 bar 2: mem 0x60001000-0x600011ff
kernel: irq 11
kernel: tulip_attach(device 20:00.0)
kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasord)
kernel: eth0: Digital DS21143 Tulip rev 16 at 0xa00, EEPROM not present, 00:4C:69:6E:75:79, IRQ 11.
kernel: eth0: Missing EEPROM, this interface may not work correctly!
cardmgr[9623]: executing: './network start eth0'
kernel: eth0: Tx hung, 11 vs. 0.
kernel: eth0: 21140 transmit timed out, status 0801fbfc,
SIA 0000000f 00000000 00000018 58fab388, resetting...

And then the interface doesn't work.
What can I do?

Thanks.

None "Tx Hung" often means an interrupt delivery problem

Re: Question Compex Linkport/TX32 and EEPROM (Marco Dubbeld)
Date: 2000, Aug 28
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Can you post more of your messages, including the startup messages
from the i82365 socket driver?  (PCIC probe, etc)

-- Dave

None more info Compex TX32, "Tx hung" problem

Re: None "Tx Hung" often means an interrupt delivery problem (David Hinds)
Date: 2000, Aug 29
From: Marco Dubbeld marco

I've tried to collect most info. Since I do not really know what is most relevant.

>< >< Output of DMesg after probe: >< ><

Linux version 2.2.14-15mdk (root@kenobi.mandrakesoft.com) (gcc version 2.95.2 19991024 (release)) #1 Tue Jan 4 22:24:20 CET 2000

Linux PCMCIA Card Services 3.1.19
  kernel build: 2.2.14-15mdk #1 Tue Jan 4 22:24:20 CET 2000
  options:  [pci] [cardbus] [apm] [pnp]
PCI routing table version 1.0 at 0xfdf80
  00:04.0 -> irq 11
  00:04.1 -> irq 11
PnP: PNP BIOS installation structure at 0xc00f6780
PnP: PNP BIOS version 1.0, entry at f0000:b31a, dseg at 400
Intel PCIC probe: 
  TI 1220 rev 02 PCI-to-CardBus at slot 00:04, mem 0x68000000
    host opts [0]: [ring] [serial pci & irq] [pci irq 11] [lat 168/176] [bus 32/34]
    host opts [1]: [ring] [serial pci & irq] [pci irq 11] [lat 168/176] [bus 35/37]
    ISA irqs (scanned) = 3,4,5 PCI status changes
cs: IO port probe 0x1000-0x17ff: clean.
cs: IO port probe 0x0100-0x04ff: clean.
cs: IO port probe 0x0a00-0x0aff: clean.

>< >< Putput of dmesg after card insert >< ><

cs: cb_alloc(bus 32): vendor 0x10ec, device 0x8138
cs: cb_config(bus 32)
  fn 0 bar 1: io 0xa00-0xaff
  fn 0 bar 2: mem 0x60001000-0x600011ff
  irq 11
cs: cb_enable(bus 32)
  bridge io map 0 (flags 0x21): 0xa00-0xaff
  bridge mem map 0 (flags 0x1): 0x60001000-0x60001fff
tulip_attach(device 20:00.0)
tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
eth0: Digital DS21143 Tulip rev 16 at 0xa00, EEPROM not present, 00:4C:69:6E:75:79, IRQ 11.
eth0:  Missing EEPROM, this interface may not work correctly!
bridge-eth0: found peer eth0
bridge-eth0: up
eth0: Tx hung, 11 vs. 0.
eth0: 21140 transmit timed out, status 0801fbfc, SIA 0000000f 00000000 00000018 58fab388, resetting...
eth0: Tx hung, 11 vs. 0.
eth0: 21140 transmit timed out, status 0801fbfc, SIA 0000000f 00000000 00000018 58fab388, resetting...
eth0: Tx hung, 11 vs. 0.
eth0: 21140 transmit timed out, status 0801fbfc, SIA 0000000f 00000000 00000018 58fab388, resetting...

>< >< Output of debug-tools/dump_cis >< ><

Socket 0:
  manfid 0x018a, 0x0106
  funcid network_adapter
  lan_technology ethernet
  lan_speed 10 mb/sec
  lan_speed 100 mb/sec
  BAR 1 size 384b [io]
  BAR 2 size 384b [mem] [<1mb]
  config_cb base 0x0010 last_index 0x02
  cftable_entry_cb 0x01
    [master] [invalidate] [parity] [wait] [serr] [fast back]
    io_base 2
    irq mask 0x8ebc [level] [shared]
    mem_base 1 3
  vers_1 5.0, "CardBus", "10/100Mbps Ethernet Card", "", ""
}, {
  manfid 0x018a, 0x0106
  funcid network_adapter
  lan_technology ethernet
  lan_speed 10 mb/sec
  lan_speed 100 mb/sec
  BAR 1 size 384b [io]
  BAR 2 size 384b [mem] [<1mb]
  config_cb base 0x0010 last_index 0x02
  cftable_entry_cb 0x01
    [master] [invalidate] [parity] [wait] [serr] [fast back]
    io_base 2
    irq mask 0x8ebc [level] [shared]
    mem_base 1 3
  vers_1 5.0, "CardBus", "10/100Mbps Ethernet Card", "", ""

Socket 1:
  no CIS present

>< >< Output of debug-tools/dump_exca >< ><

Socket 0:
  Identification and revision = 0x84
  Interface status = 0x6e
    [bvd2/spkr] [detect] [ready] [poweron]
  Power control = 0x19
    [resetdrv] [Vcc=3.3v] [Vpp=5v]
  Interrupt and general control = 0x10
    [reset] [intr ena] [irq=0]
  Card status change interrupt control = 0x08
    [detect] [irq=0]
  Card detect and general control = 0xc0

  memory 0: 0x0000-0x0fff @ 0x00000000 [off] [8bit]
  memory 1: 0x0000-0x0fff @ 0x00000000 [off] [8bit]
  memory 2: 0x0000-0x0fff @ 0x00000000 [off] [8bit]
  memory 3: 0x0000-0x0fff @ 0x00000000 [off] [8bit]
  memory 4: 0x0000-0x0fff @ 0x00000000 [off] [8bit]
  io 0: 0x0000-0x0001 [off] [8bit]
  io 1: 0x0000-0x0001 [off] [8bit]

Socket 1:
  Identification and revision = 0x84
  Interface status = 0x00

  Power control = 0x00
    [resetdrv] [Vcc off] [Vpp off]
  Interrupt and general control = 0x50
    [intr ena] [irq=0]
  Card status change interrupt control = 0x08
    [detect] [irq=0]
  Card detect and general control = 0xc0

  memory 0: 0x0000-0x0fff @ 0x00000000 [off] [8bit]
  memory 1: 0x0000-0x0fff @ 0x00000000 [off] [8bit]
  memory 2: 0x0000-0x0fff @ 0x00000000 [off] [8bit]
  memory 3: 0x0000-0x0fff @ 0x00000000 [off] [8bit]
  memory 4: 0x0000-0x0fff @ 0x00000000 [off] [8bit]
  io 0: 0x0000-0x0001 [off] [8bit]
  io 1: 0x0000-0x0001 [off] [8bit]

>< >< Output of dump_pirq >< ><

Interrupt routing table found at address 0xfdf80:
  Version 1.0, size 0x0060
  Interrupt router is device 00:07.0
  PCI exclusive interrupt mask: 0x0000
  Compatible router: vendor 0x8086 device 0x122e

Device 00:07.0 (slot 0):
  INTD: link 0x63, irq mask 0x0400

Device 00:01.0 (slot 0):
  INTB: link 0x61, irq mask 0x0800

Device 00:04.0 (slot 0):
  INTA: link 0x60, irq mask 0x0800
  INTB: link 0x61, irq mask 0x0800

Device ff:00.0 (slot 0):
  INTB: link 0x61, irq mask 0x0800

Interrupt router at 00:07.0: Intel 82371AB PIIX4/PIIX4E PCI-to-ISA bridge
  PIRQ1 (link 0x60): irq 11
  PIRQ2 (link 0x61): irq 11
  PIRQ3 (link 0x62): unrouted
  PIRQ4 (link 0x63): irq 10
  Serial IRQ: [enabled] [continuous] [frame=21] [pulse=4]

>< >< Ouptut of test_network >< ><

PCMCIA network settings are coming from /etc/pcmcia/network.opts.
  /etc/sysconfig/network-scripts/ifcfg-eth0 also exists??

Checking network interface eth0 (tulip_cb driver):

  Kernel messages for eth0:
  eth0: 21140 transmit timed out, status 0801fbfc, SIA 0000000f 00000000 00000098 58fab388, resetting...
  eth0: Tx hung, 19 vs. 0.
  eth0: 21140 transmit timed out, status 0801fbfc, SIA 0000000f 00000000 00000018 58fab388, resetting...
  eth0: Tx hung, 19 vs. 0.
  eth0: 21140 transmit timed out, status 0801fbfc, SIA 0000000f 00000000 00000018 58fab388, resetting...
  eth0: Tx hung, 19 vs. 0.
  eth0: 21140 transmit timed out, status 0801fbfc, SIA 0000000f 00000000 00000018 58fab388, resetting...
  eth0: Tx hung, 19 vs. 0.
  eth0: 21140 transmit timed out, status 0801fbfc, SIA 0000000f 00000000 00000018 58fab388, resetting...
  eth0: 21140 transmit timed out, status 0801fbfc, SIA 0000000f 00000000 00000098 58fab388, resetting...

  Current ifconfig settings:
  eth0      Link encap:Ethernet  HWaddr 00:4C:69:6E:75:79  
            inet addr:192.168.161.130  Bcast:192.168.161.255  Mask:255.255.255.0
            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
            TX packets:0 errors:39 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:100 
            Interrupt:11 Base address:0xa00 

  The interface is configured and running.
  There hasn't been any traffic on this interface!

  There is a route to a gateway at 192.168.161.2.

  Pinging 192.168.161.2 ... timed out!
  The device interrupt does not seem to be incrementing normally.

>< >< Output of /proc/interrupts >< ><

           CPU0       
  0:      87925          XT-PIC  timer
  1:       2740          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  8:          1          XT-PIC  rtc
 11:          9          XT-PIC  i82365, eth0
 12:       2070          XT-PIC  PS/2 Mouse
 13:          1          XT-PIC  fpu
 14:      67663          XT-PIC  ide0
 15:          4          XT-PIC  ide1
NMI:          0

>< >< Output of /proc/ioports >< ><

0000-001f : dma1 0020-003f : pic1 0040-005f : timer 0060-006f : keyboard 0070-007f : rtc 0080-008f : dma page reg 00a0-00bf : pic2 00c0-00df : dma2 00f0-00ff : fpu 0170-0177 : ide1 01f0-01f7 : ide0 0376-0376 : ide1 03c0-03df : vga+ 03f6-03f6 : ide0 03f8-03ff : serial(auto) 0a00-0aff : cb_enabler fcd0-fcd7 : ide0 fcd8-fcdf : ide1

>< >< Output of /poc/modules >< ><

tulip_cb 32292 2 cb_enabler 2280 2 [tulip_cb] vmnet 14560 3 vmppuser 4868 0 (unused) parport_pc 7604 0 [vmppuser] parport 8084 0 [vmppuser parport_pc] vmmon 16156 0 (unused) ds 6284 2 [cb_enabler] i82365 22780 2 pcmcia_core 51392 0 [cb_enabler ds i82365] vfat 11004 0 (unused) fat 32640 0 [vfat]

>< >< Output of /proc/pci >< ><

PCI devices found:
  Bus 32, device   0, function  0:
    Ethernet controller: Realtek Unknown device (rev 16).
      Vendor id=10ec. Device id=8138.
      Medium devsel.  Fast back-to-back capable.  IRQ 11.  
      I/O at 0xa00 [0xa01].
      Non-prefetchable 32 bit memory at 0x60001000 [0x60001000].
  Bus  0, device   4, function  0:
    CardBus bridge: Texas Instruments Unknown device (rev 2).
      Vendor id=104c. Device id=ac17.
      Medium devsel.  IRQ 11.  Master Capable.  Latency=168.  Max Lat=7.
      Non-prefetchable 32 bit memory at 0x68000000 [0x68000000].
  Bus  0, device   4, function  1:
    CardBus bridge: Texas Instruments Unknown device (rev 2).
      Vendor id=104c. Device id=ac17.
      Medium devsel.  IRQ 11.  Master Capable.  Latency=168.  Min Gnt=192.Max Lat=7.
      Non-prefetchable 32 bit memory at 0x68001000 [0x68001000].

>< >< Output of tulip_diag -p 0xa00 -ee, however for all next I had to specify -p 0xa00
>since no recognition out of /proc/pci >< ><

tulip-diag.c:v2.03 7/31/2000 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Assuming a Digital Tulip series adapter at 0xa00.
 Port selection is 10mpbs-serial, full-duplex.
 Transmit stopped, Receive stopped, full-duplex.
  The Rx process state is 'Stopped'.
  The Tx process state is 'Stopped'.
  PCI bus error!: Parity Error.
  The transmit threshold is 72.
 Interrupt sources are pending!  CSR5 is 0801fbfc.
   Tx out of buffers indication.
   Transmit Jabber indication.
   Link passed indication.
   Tx FIFO Underflow indication.
   Rx Done indication.
   Receiver out of buffers indication.
   Receiver stopped indication.
   Receiver jabber indication.
   Timer expired indication.
   Link failed indication.
   PCI bus error indication.
   Early Rx indication.
EEPROM size is 6.
  * An old-style EEPROM layout was found.
  * The old-style layout does not contain transceiver control information.
  * This board may not work, or may work only with a subset of transceiver
  * options or data rates.
EEPROM contents:
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
 ID block CRC 0xe3 (vs. 00).
  Full contents CRC 0x6523 (read as 0x0000).

>< >< Output of tulip-diag -p 0xa00 -aa >< ><

tulip-diag.c:v2.03 7/31/2000 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Assuming a Digital Tulip series adapter at 0xa00.
 * A potential Tulip chip has been found, but it appears to be active.
 * Either shutdown the network, or use the '-f' flag to see all values.
 Port selection is 100mbps-SYM/PCS 100baseTx scrambler, half-duplex.
 Transmit started, Receive stopped, half-duplex.
  The Rx process state is 'Stopped'.
  The Tx process state is 'Stopped'.
  PCI bus error!: Parity Error.
  The transmit threshold is 128.
 Interrupt sources are pending!  CSR5 is 0801fbfc.
   Tx out of buffers indication.
   Transmit Jabber indication.
   Link passed indication.
   Tx FIFO Underflow indication.
   Rx Done indication.
   Receiver out of buffers indication.
   Receiver stopped indication.
   Receiver jabber indication.
   Timer expired indication.
   Link failed indication.
   PCI bus error indication.
   Early Rx indication.

>< >< Ouput of tulip-diag -p 0xa00 -mm >< ><

tulip-diag.c:v2.03 7/31/2000 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Assuming a Digital Tulip series adapter at 0xa00.
 Port selection is 10mpbs-serial, full-duplex.
 Transmit stopped, Receive stopped, full-duplex.
  The Rx process state is 'Stopped'.
  The Tx process state is 'Stopped'.
  PCI bus error!: Parity Error.
  The transmit threshold is 72.
 Interrupt sources are pending!  CSR5 is 0801fbfc.
   Tx out of buffers indication.
   Transmit Jabber indication.
   Link passed indication.
   Tx FIFO Underflow indication.
   Rx Done indication.
   Receiver out of buffers indication.
   Receiver stopped indication.
   Receiver jabber indication.
   Timer expired indication.
   Link failed indication.
   PCI bus error indication.
   Early Rx indication.
   No MII transceivers found!

>< >< Output of /sbin/ifconfig >< ><

eth0      Link encap:Ethernet  HWaddr 00:4C:69:6E:75:79  
          inet addr:192.168.161.130  Bcast:192.168.161.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:168 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          Interrupt:11 Base address:0xa00 

>< >< Output of eepro100-diag -ee -p 0xa00 >< ><

eepro100-diag.c:v2.02 7/19/2000 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Assuming a Intel i82557 (or i82558) EtherExpressPro100B adapter at 0xa00.
EEPROM contents, size 64x16:
      ...
 *****  The EEPROM checksum is INCORRECT!  *****
  The checksum is 0x00, it should be 0xBABA!
Intel EtherExpress Pro 10/100 EEPROM contents:
  Station address 00:00:00:00:00:00.
  Receiver lock-up bug exists. (The driver work-around *is* implemented.)
  Board assembly 000000-000, Physical connectors present:
  Primary interface chip None PHY #0.

>< >< Output of eepro100-diag -p 0xa00 -aa >< ><

eepro100-diag.c:v2.02 7/19/2000 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Assuming a Intel i82557 (or i82558) EtherExpressPro100B adapter at 0xa00.
i82557 chip registers at 0xa00:
  900ca000 00000fab 00000000 48000000 00002000 00002000
  Interrupt sources are pending.
   The transmit unit state is 'Idle'.
   The receive unit state is 'Idle'.
  This status is unusual for an activated interface.
 The Command register has an unprocessed command 900c(?!).

hope this will show the problem??

thanks, Marco

None Wait a second: this is not the right driver!

Re: None more info Compex TX32, "Tx hung" problem (Marco Dubbeld)
Date: 2000, Sep 01
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You didn't mention the part about how this was reported as an
"unsupported card" until you added it to /etc/pcmcia/config ;)

This card is not compatible with the tulip_cb driver.

>   Bus 32, device   0, function  0:
>     Ethernet controller: Realtek Unknown device (rev 16).
>       Vendor id=10ec. Device id=8138.

You can get a Realtek CardBus driver from http://www.scyld.com but I
have not tested it.

-- Dave

Feedback Addition to pcmcia/config file required.

Date: 2000, Aug 27
From: Rudi Heitbaum rudi

Addition to the config file to enable the EtherExpress PrO/100 Lan+Modem56 CardBus II.

card "Intel EtherExpress PRO/100 Lan+Modem56 CardBus II"
  manfid 0x0089, 0x1103
  bind "eepro100_cb" to 0, "serial_cb" to 1

The other thing I found is if minicom is set to use hardware flow control the laptop hangs.

/sbin/cardctl ident 
  product info: "INTEL(R)", "PRO/100 LAN+MODEM56 CARDBUS II", "MBLA3456", "1.00"  manfid: 0x0089, 0x1103

Regards

Rudi

Sad 2.4.0 test 7 broke pcnet_cs

Date: 2000, Aug 28
From: Heather Stern starshine

I decided to give the latest test kernel a shot since PCMCIA is supposed to be a bit handier now that it's in the real tree. Looks like they missed something in the Great ReOrg though. And the amazing thing is, they only missed the most commonly used module for me :( pcnet_cs doesn't work because it's missing these symbols:

 Aug 27 18:18:06 venus cardmgr[108]: insmod exited with status 1
 Aug 27 18:18:06 venus cardmgr[108]: executing: 'modprobe pcnet_cs'
 Aug 27 18:18:06 venus cardmgr[108]: + /lib/modules/2.4.0-test7/pcmcia/pcnet_cs.o: unresolved symbol ei_interrupt_Rb93d8fa5
 Aug 27 18:18:06 venus cardmgr[108]: + /lib/modules/2.4.0-test7/pcmcia/pcnet_cs.o: unresolved symbol ei_open_R7308bf72
 Aug 27 18:18:06 venus cardmgr[108]: + /lib/modules/2.4.0-test7/pcmcia/pcnet_cs.o: unresolved symbol NS8390_init_R73472e03
 Aug 27 18:18:06 venus cardmgr[108]: + /lib/modules/2.4.0-test7/pcmcia/pcnet_cs.o: unresolved symbol ethdev_init_R98ed9a17
 Aug 27 18:18:06 venus cardmgr[108]: + /lib/modules/2.4.0-test7/pcmcia/pcnet_cs.o: insmod /lib/modules/2.4.0-test7/pcmcia/pcnet_cs.o failed
 Aug 27 18:18:06 venus cardmgr[108]: + /lib/modules/2.4.0-test7/pcmcia/pcnet_cs.o: insmod pcnet_cs failed
 Aug 27 18:18:06 venus cardmgr[108]: modprobe exited with status 255

This was on a pentium 233 MMX. Haven't had a chance to try it compiled for other CPUs. Card services are version 3.1.19.

Thanks ... looking forward to using a new kernel one of these days.

Heather *

None Makefile bug

Re: Sad 2.4.0 test 7 broke pcnet_cs (Heather Stern)
Date: 2000, Sep 01
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The 8390 module was not compiled.  As a workaround, re-configure your
kernel with CONFIG_NE2000 turned on (as a module would be best).

-- Dave

Question Dynalink LC100-32-2

Date: 2000, Aug 30
From: Mitsuo <mfuchida@hotmail.com>

Hi friends

Does anybody know how to make this pcmcia works (Dynalink
LC100-32-2), or if this card is actually supported by linux?
I did search www.dynalink.com site for support (2-tech) and
i didn´t make it by myself (i´m just a linux newbie), so 
would anyone mind helping me?

Thank´s advanced and regards

Question Silicom pcmcia drivers: make error ?

Date: 2000, Nov 24
From: Graham FennerBarbour grahamfennerbarbour

I am trying to install the Silicom pcmcia drivers on my Laptech (?) laptop that is running Redhat 6.2.

Cardmgr is already installed (from setup) and seems to be working fine, issuing the apopriate beeps when the card is inserted etc.

I always get an error when running the make files.

Unfortunately, I am a Linux newbie (but to nothing else), so I assume the problem is not really for this forum, but know nowhere else to begin.

Has anyone encountered this problem?

PCMCIA Network Adapter Issues


Members Subscribe No Admin Mode Show Frames Help for HyperNews at pcmcia-cs.sourceforge.net 1.10
[ Edit This Forum ]