Re: network card problems
If I managed to follow you I think that your next step is the route command.
It is mentioned in the NETWORK-HOWTO. You might also want to take a look at
the Ethernet-HOWTO just to know what is there.
> Thanks Phil and Hubert for responding! I've loaded the module (ne.o) and
> ran the ifconfig command with success (with your help)! Can either one of
> you guys or anybody else in debian land tell me what HOWTO document I can
> use to help me with my next step(s)... i.e. should I ping my address? I've
> tried it already and it fails.
>
> -Wxb1
> ----- Original Message -----
> From: Phil Brutsche <pbrutsch@creighton.edu>
> To: Wendell Buckner <wxb1@erols.com>
> Cc: Debian Users Group <debian-user@lists.debian.org>
> Sent: Wednesday, October 06, 1999 6:47 PM
> Subject: Re: network card problems
>
>
> > A long time ago, in a galaxy far, far way, someone said...
> >
> > > I have a DE-220PCT ISA network card which is in a 486 PC. And my goal
> > > is to eventually have this P.C. as a client on my NT network. I am
> > > completly new to this and don't really know what I'm doing. I have the
> > > network HOWTO (generic network configuration information) but i'ts not
> > > helping! I ran diagnostics on the network card and it appears to be
> > > o.k. I ran the following command and got the following error:
> > >
> > > ifconfig eth0 192.168.0.0.1 netmask 255.255.255.0 up
> > > eth0:Unknown interface.
> > > SIOCSIFADDR:Operation not supported by device
> > > eth0:Unknown interface.
> > > SIOCSIFNETMASK:Operation not supported by device
> > >
> > > Please don't tell me that the network module isn't compiled into
> > > kernel! (I haven't messed around with compiling the kernel, it scares
> > > me!)
> >
> > FYI: According to the kernel source, the DE-220PCT is an ISA
> > NE2000-compatible card.
> >
> > First: The network module isn't compiled into the kernel (sorry). Are you
> > using the stock Debian kernel? If so, you should have the driver ready
> > for use.
> >
> > The first thing you need to do is see what modules you currently have
> > loaded. Running 'lsmod' will tell you that. For example, this is what I
> > get when I run 'lsmod':
> >
> > Module Size Used by
> > tulip 27132 1
> > af_packet 5836 1 (autoclean)
> > es1371 23904 0
> > soundcore 2372 4 [es1371]
> > sd_mod 15964 2 (autoclean)
> > sym53c8xx 46880 2 (autoclean)
> > scsi_mod 50800 2 (autoclean) [sd_mod sym53c8xx]
> >
> > It shows the modules for my ethernet card, needed logic for my DHCP
> > client, lowlevel and support drivers for my sound card, and drivers for my
> > SCSI card.
> >
> > If the module 'ne' (the driver for ISA NE2000 and compatible cards) isn't
> > shown, load it, like this:
> > modprobe ne
> >
> > Now, if you run 'lsmod', the module should show up. The 'ifconfig'
> > command should then work.
> >
> > Second: You didn't quite get the 'ifconfig' command right. It should be:
> > ifconfig eth0 192.168.0.1 netmask 255.255.255.0 up
> > (one too many zeroes)
> >
> > --
> > ----------------------------------------------------------------------
> > Phil Brutsche pbrutsch@creighton.edu
> >
> > "There are two things that are infinite; Human stupidity and the
> > universe. And I'm not sure about the universe." - Albert Einstein
> >
> >
> >
> > --
> > Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org <
> /dev/null
> >
> >
>
>
> --
> Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
>
Reply to: