See below.
At 10:42 AM 5/16/00 +0100, [EMAIL PROTECTED] wrote:
...
>Regarding Plug and Pray.
>I have a generic (read cheap) NE2000 compatible PnP NIC.
>If I do a default network install I get something called lo as the NIC
>device. What is lo (could it be loopback only ?)
Yes, lo is the standard name for loopback.
>I can ping localhost and, if I edit /etc/sysconfig/network-scripts/ifcfg-
>lo I can ping another ip address (e.g 148.197.200.3)
Without knowing (a) what editing you do to the file or (b) what the example
IP address is (beyond the fact that I cannot ping it), there's really
nothing useful one can say about this part.
> On startup device lo is initialised but device eth0 fails to start. In
>the bios (AMIBIOS 1998) I have an item called 'Plug and Play
>Aware O/S'. Setting this to no causes the system to start as
>above.
NO is the correct choice here.
>Setting this to yes makes no difference WRT the ethernet
>card. The card seems to be 'working' as the correct light comes on
>on the hub.
This means the card is working in a hardware sense. So the problem is
probably that the appropriate module is not detecting it.
>Can anybody give me the definitive answer as to what
>this field should read for Linux ?
See above.
>I've tried to configure the card via /etc/sysconfig/network-
>scripts/ifcfg-eth0. However I don't have a device called eth0 in /dev
That's because eth0 is not a device; it is an interface. To see if you have
an eth0 interface after booting, run the command "ifconfig -a" (on most
systems). The -a flag tells the app to report on all interfaces found, not
just configured ones (the default). This step will let you see if the
problem is with interface detection or interface configuration.
If this check does not report an eth0, then focus on card detection.
A. How are you doing PnP initialization of the card? If it
really is an NE2000 card, it is on the isa bus,
which requires you to run isapnp to set it up. If it
is a pci-bus card, the BIOS will do that part for you,
but then it isn't NE2000 (though it may be NE2000-PCI,
which uses a different module).
B. What kernel module are you running to initialize the card,
and what parameters are you giving it? If the card
is isa, then you use the ne.o module (which requires
8390.o, a dependency that modprobe will handle but
not insmod). If it is pci, then you want ne2k-pci.o
(which also depends on 8390.o, as I recall).
C. What messages do you get at the time that the module tries
to detect a card? This is part of the boot/init
messages you see on the screen (some distributions let
you scroll back to see them again with SHIFT-PgUp; not
all implement this). dmseg may also let you see these
messages.
D. How certain are you that the card is NE2000?
If the "ifconfig -a" command does report an eth0, then focus on your
attempts to configure the interface. You've done something wrong here,
probably, but without knowing anything about what you are trying, I can't
help you see what it is.
BTW, it's always helpful to remind us what Linux distribution, version, and
kernel version ("uname -a") you are using. Every time, for those of us who
don't save your mail and have poor memories.
--
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
