PCI NE2000 clone problem

PCI NE2000 clone problem

Post by wra.. » Sat, 06 Sep 1997 04:00:00




Check out the contents of /proc/pci for your addrress and your boot waffle for the irq.
Compile in PCI card support and off you (should) go...

Your bios settings may need to differ between Win95 and Linux (I have this problem with a Hayes Accura
Internal which really confuses the pci setup for some reason. Go figure. Plug and Pray dude..)

    > I have a K6 box, mostly running 95. It has a PCI NE2000
    > clone with the standard chipset (I forget which at
    > present). 95 finds it at 0x6100 (yes, rather high) and
    > all is hunkydory.
    > Slackware 3.2 can't find it on boot. I tried setting
    > the address to 0x6100 in the module call and I then
    > couldn't boot at all - had to go back to the boot/root
    > set and copy back the only rc.whatever (no editor
    > would work with the boot/root set).
    > Suggestions welcome.

--

    -----------------------
     "Weaving a Wicked Web"
    ------------------------
member: Force9 Usergroup Committee.
          ICQ-3046261
  http://www.hades.force9.co.uk/

 
 
 

PCI NE2000 clone problem

Post by John Alle » Sat, 06 Sep 1997 04:00:00


Look at this page for PCI NE2000 cards:

http://rsphy1.anu.edu.au/~gpg109/ne2000.html

This is Paul Gortmaker's page on the topic.  To make these cards
work you will more that likely apply a patch to ne.c



> Check out the contents of /proc/pci for your addrress and your boot waffle for the irq.
> Compile in PCI card support and off you (should) go...

> Your bios settings may need to differ between Win95 and Linux (I have this problem with a Hayes Accura
> Internal which really confuses the pci setup for some reason. Go figure. Plug and Pray dude..)

>     > I have a K6 box, mostly running 95. It has a PCI NE2000
>     > clone with the standard chipset (I forget which at
>     > present). 95 finds it at 0x6100 (yes, rather high) and
>     > all is hunkydory.
>     > Slackware 3.2 can't find it on boot. I tried setting
>     > the address to 0x6100 in the module call and I then
>     > couldn't boot at all - had to go back to the boot/root
>     > set and copy back the only rc.whatever (no editor
>     > would work with the boot/root set).
>     > Suggestions welcome.

> --

>     -----------------------
>      "Weaving a Wicked Web"
>     ------------------------
> member: Force9 Usergroup Committee.
>           ICQ-3046261
>   http://www.hades.force9.co.uk/

--
===================================================
Jonathan Allen
Raytheon E-Systems, Fallschurch Division


phone: 703-560-5000x2497

** Any opinions expressed above are my own, and not
   those of my employer.



 
 
 

PCI NE2000 clone problem

Post by Pagonis Joh » Tue, 09 Sep 1997 04:00:00


  What I did whith all my PCI NE2000 card is to compile the kernel with the PCI ethernet option and the
NE2000
option both enabled....it worked all the times, although i did NOT specify a PCI card......
good luck

John

 
 
 

1. ne2000 PCI clone: HW problem?

Hi all,

when adding a new box to a ethernetwork I encountered some problem
that looks to me like a hardware problem:

The network:  used to consist of two linux boxes with ISA ne2000
        cards and 10base 2 cable. It used to work fine (and still
        does for those two boxes).

The nex box: has a rtl8029 (ne2000 compatible) PCI card. It is running
        a SUSE 6.0 Linux with the included 2.0.36 kernel included.

The symptoms: the card is correctly recognized by the driver, ifconfig
        works as I expect and shows me

        eth0      Link encap:10Mbps Ethernet  HWaddr 00:E0:7D:50:29:FA
                inet addr:192.128.10.141  Bcast:192.128.10.255  Mask:255.255.255.0
                UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                RX packets:0 errors:0 dropped:0 overruns:0
                TX packets:18 errors:0 dropped:0 overruns:0
                Interrupt:11 Base address:0x6300

        what looks fine to me.

        Now what looks wrong?

        - there are two LEDs on the card, one to show I/O traffic and
          one to show  `network connected' (LED on) or `network disconnected'
          (LED off). And this second LED is allways off.

        - when I try to ping another box in the network, the number of
          transmitted packages slowly goes up, but ping gets nothing back
          Ping claims to have transmitted a lot more packages than
          the statistics from ifconfig or netstat -i

        - arp -a  prints instead the ethernet address of the pinged box
          `<incomplete>'

        - the LED on the card signalling traffic indicates no traffic

The included diagnistics software for the card finds no errors when checking
the cards components. Unfortunately I cannot test the network conection
with this software because this needs two boxes running the software; but
this software detects unplugging the cable.

I used two different cables and exchanged the T-connectors between the
ethernet cards of the three boxes without changing the symptoms.

Well this looks to me like a hardware problem but I would like to be sure
before going back to the dealer... Is there any other possibility?

Thanks a lot for any help!

Andy

2. Free network device monitoring

3. Problems with NE2000 Clone PCI card.

4. Linux Wireless: DHCPCD Question:

5. ne2000-pci clone is clown

6. driver update to kernel 2.5.50?

7. patch for ne2000 pci clones 2.1.93/94

8. Combination of Leaky-Bucket and Token Bucket

9. Caldera base 1.1- support for PCI NE2000 clone card

10. Trying to install PCI NE2000 clone

11. Configure PCI in the BIOS for a NE2000 Clone

12. Sharing IRQ on ne2000 PCI clones ?

13. PCI NE2000 Clone Woes....