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.
Neither configuration works in 2.6.2, 2.6.3 or 2.6.4-rc1. I'm
obviously not a programmer. I am, however, interested in
salvaging equipment for good causes.
Some info about this machine:
==============================
Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.3,
glibc-2.3.3_pre20040207-r0, 2.4.24)
System uname: 2.4.24 i586 Pentium 75 - 200
Gentoo Base System version 1.4.3.13p1
Autoconf: sys-devel/autoconf-2.59-r3
Automake: sys-devel/automake-1.8.2
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-Os -march=pentium -pipe"
CHOST="i586-pc-linux-gnu"
COMPILER="gcc3"
===============================
BTW - this machine works fine configured the way it is under the
2.4.x series of kernels. However, everything I read about 2.6
tells me that this machine would probably benefit in total
throughput using the 2.6 kernel.
And yes, I really did bootstrap Gentoo on this machine and compile
every package on it. ;-) Speed is 120MHz, RAM is 64 megs.
--
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
