OK, after going through /proc/pci, I found out that
the card is actually an NE200-PCI card (so much for
advertising!), and I installed the appropriate driver,
and the network interface seems to work now.
However, now I have an entirely different problem: I
can't resolve hostnames to addresses. Debian also
apparently does NOT install nslookup in its base
package, so I'm going to have to dig that up off the
CD. /etc/resolv.conf wasn't already present, so I
created it using 'man resolv.conf' as my guide, with
both of my ISP's DNS servers' addresses entered, but I
am still unable to resolve names. Do I need to be
running BIND in order to resolve names?
--Kevin Fogleman
--- Scott Piper <piper@ij.net> wrote:
>
> FIrst, enter lsmod to see which modules you have
> loaded. It may
> be loaded already.
>
> You can look at /proc/pci to see which irq and port
> your pci
> devices are using, but you shouldn't have to mess
> with it - at
> least I dont' think so - aren't PCI devices set up
> before any ISA
> stuff?
>
> I always use modprobe instead of insmod to load
> modules. I don't
> know off hand if insmod will load all of the
> dependent modules or
> not.
>
> In Debian (the newer versions, anyway) the network
> is configured
> using the /etc/network/interfaces file. It should
> be written out
> for you during the install, but if it isn't (I don't
> know if you
> have to have the net card up and running first) it
> would be a
> format such as the following (see man interfaces for
> more info -
> you can do things like set up different ways based
> on different
> situations)
>
>
> # automatically set up loopback interface on start
> up
> auto lo
> iface lo inet loopback
>
> #you would usually use one of the two, depending on
> whether you
> have a static ip or use dhcp
>
> # automatically set up eth0 on startup, dhcp
> auto eth0
> iface eth0 inet dhcp
>
> #automatically set up eth0 on startup, static ip -
> replace the
> addresses with your requirements
> auto eth0
> iface eth0 inet static
> address 192.168.0.23
> netmask 255.255.255.0
> network 192.168.0.0
> broadcast 192.168.0.255
> gateway 192.168.0.1
>
> #if you add a second network card, then do a setion
> with eth1
> instead of eth0
>
>
>
> You bring the network up with the command
>
> /etc/init.d/networking start
>
> stop it with
>
> /etc/init.d/networking stop
>
> and restart (stop then start) with
>
> /etc/init.d/networking restart
>
>
> scott
>
>
> Electric Monk wrote:
>
> > Well, since last Friday, I decided to bring in my
> > Debian CDs to install on this
> > computer here at work, instead of Redhat. I also
> > bought a brand new PCI network
> > card for said machine. However, I am still having
> > difficulties with using insmod to
> > load the appropriate kernel module for the card.
> It
> > uses the Realtek 8139 chipset,
> > so I'm assuming that rtl8139.o is the correct
> module.
> >
> > When I try to load it, I get an error message
> telling
> > me that the device is busy, which
> > it says means that the IRQ or I/O port could be
> > configured incorrectly, although if I
> > recall correctly, this SHOULD NOT be a problem
> with
> > the PCI bus. What do I
> > need to do to get it working?
> >
> > Also, when I type "ifconfig -a" at the console,
> the
> > only interface that is shown is the
> > loopback. Will the network card automatically be
> > added once I install its module?
> >
> > --Kevin Fogleman
> >
> > =====
> > --electricmonk
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Get personalized email addresses from Yahoo! Mail
> > http://personal.mail.yahoo.com/
>
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 16:11:39 EDT