On Sat, 17 Jun 2000 at 16:10, Jackson Ching wrote:
>I have installed RedHat 6.2, But it was not able to detect the network
>card (e2000plus) which is NE2000 compatible daw. how must i configure my
>linux so that it can detect the NIC and be able to use it? Thanks!
I hope this reply is not too late. I also recently installed a no-brand
PNP ISA NIC that was supposedly NE2000 compatible. The computer (with the
NIC already) was originally running Windows 95 OSR2 and I set it up with
Linux instead to serve as an e-mail and Internet gateway for a small LAN.
It's proven to be much more efficient and reliable than a previous WinGate
setup on a Celeron 400 running Windows98. Hahaha! Go go go Linux!
Anyway, enough with the historical sales pitch. Because I had Windows
previously installed, I copied the address information of the NIC (IO and
IRQ) and then tried to plug them into the module's parameters, but to no
avail. The NIC wouldn't work just like that. Here's what worked:
1. Compiled latest kernel with NE2000 support as a module - you probably
won't have to compile the latest kernel, and AFAIK RedHat's stock has
NE2000 as a module. However, I wanted this box to have the latest security
updates, including as far as the kernel is concerned. Plus I didn't want
the bloat, it was a 486. So I compiled a streamlined kernel. I compiled
NE2000 support as a module versus built into the kernel because I needed
to be able to set the NIC up via the Linux ISA PNP tools before loading
the module with the proper parameters for the IO and IRQ.
2. Installed the Linux ISA PNP tools and read the PNP HOWTO. For RedHat
6.2 you've got an RPM called isapnptools-1.21b-1.i386.rpm in
$cdrom/RedHat/RPMS/. That's what you need installed. The HOWTO you can
find on the 'Net. :-)
3. Cold boot without touching the NIC (meaning no attempts to load it or
anything like that), and using the new kernel I built.
4. Ran pnpdump, redirecting output to /etc/isapnp.conf
5. Edited /etc/isapnp.conf. You may have to read the man pages a bit to
feel comfortable with this file. I uncommented some of the lines that
pnpdump by default leaves commented. This set the parameters for isapnp to
use to know which card to talk to, and what addresses to set. I do not
know if pnpdump recommends addresses with conflicts. In my case it did
not. A little trial and error did the trick.
6. Use settings in isapnp.conf (after testing, of course) to know what to
tell the module to load, then edit /etc/conf.modules adding the line:
alias eth0 ne irq=y,io=zxzzz
(Please correct me if I'm wrong, I'm not sure if it's a comma or a space
in between io and irq)
7. Make sure /etc/sysconfig/network and
/etc/sysconfig/network-scripts/ifcfg-eth0 are properly configured. You can
use the graphical tool to set these up for you, but just in case you can't
or don't want to use a graphical tool, here are the parameters to set (as
is in my setup), adjust to your own settings:
/etc/sysconfig/network:
NETWORKING=yes
FORWARD_IPV4="yes"
HOSTNAME=linux-server.tlc
GATEWAYDEV=""
GATEWAY=""
/etc/sysconfig/network-scripts/ifcfg-eth0:
DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
BROADCAST=192.168.0.255
NETWORK=192.168.0.0
NETMASK=255.255.255.0
IPADDR=192.168.0.100
USERCTL=no
8. Cold boot. Hope things work. I noticed that warm reboots cause isapnp
to cough up some warnings. I think I'm making it set something that can
only be set after a cold boot. I'm not so sure. Cold boots get my system
booting up very smoothly, though, and my NIC works.
Good luck! :)
-+[ Jijo Sevilla ]+-
[EMAIL PROTECTED]
-
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
