Re: ISA NE NIC driver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hmmm ... These two cards were manufactured during the transition 
from jumpers to isa pnp. They have pnp, but under windows, i had 
nothing but trouble with the pnp feature. So pnp is disabled on 
these cards and jumpers are used instead. I'm not trying to set 
the addresses and interrupts using 'alias' and 'options'. Rather, 
I'm telling each copy of the ISA 'ne' driver which card has which 
address and uses which interrupt.

I got this original configuration through googling many moons ago 
with someone else whom was having a similar problem in the 2.4.x 
environment. Apparently, the ISA 'ne' driver doesn't deal with 
re-entrancy well. {Guess on my part. As noted, I am not a C/C++ 
programmer}


On Thursday 04 March 2004 02:40, Henrik Nordstrom wrote:
> Have you tried using isapnp rather than specifying the I/O and
> interrupts manually?
>
> Having to load the driver more than once does not make sense
> unless you have more than 4 ne2000 cards.
>
> On Wed, 3 Mar 2004, NoTellin wrote:
> > This is not a high priority item, even to me. But it may be
> > symptomatic of something else. Then again, it may not.
> >
> > I wanted to try the 2.6.x series of kernels on my firewall.
> > But I can't because the ISA based 'ne' NIC driver will not
> > load properly in my hardware configuration.
> >
> > My 2.4.25 {and earlier dating back to 2.4.19} configuration
> > looks like this:
> >
> > =====================
> > alias eth0 ne
> > alias eth1 ne
> >
> > # 2.4
> > options eth0 -o ne-0 io=0x300 irq=3
> > options eth1 -o ne-1 io=0x200 irq=5
> >
> > # 2.6 - non functional - ne driver issues?
> > # options ne io=0x300,200 irq=3,5
> >
> > alias eth2 winbond-840
> > alias eth3 3c509
> > ======================
> >
> > The 'ne' driver requires two copies of itself in this harware
> > configuration to work. One driver with two address and
> > interrupts does not work.

-- 
Free Speech is better than Free Beer
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux