Re: Vortex NIC problem

[Ciro Cavani]

Em Ter, 2003-03-04 às 12:37, grant@seinfeld.arrowstreet.com escreveu:
> You might have a irq problem which could be solved using the 3com firmware
> utilities to modify the cards IRQ,IO address, etc. Or pull any devices your 
> not going to use.

At first I think that could be irq ploblem, then I define the IRQ of NIC
PCI slot on BIOS:

           CPU0
  0:      39941          XT-PIC  timer
  1:       1300          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
**5:       7913          XT-PIC  eth0
  7:         11          XT-PIC  parport0
  9:          0          XT-PIC  acpi
 10:       3723          XT-PIC  EMU10K1
 11:      20859          XT-PIC  nvidia
 12:       7928          XT-PIC  PS/2 Mouse
 14:      11365          XT-PIC  ide0
 15:         49          XT-PIC  ide1
NMI:          0
LOC:      39903
ERR:          1
MIS:          0

this is kernel output (thanks by the tip):

On GNU Mach

GNUmach 1.2
AT386 boot: physical memory from 0x0 to 0x1ffec000
GNUmach 1.2
AT386 boot: physical memory from 0x0 to 0x1ffec000
pcibios_init : BIOS32 Service Directory structure at 0x000f1430
pcibios_init : BIOS32 Service Directory entry at 0xf0bc0
pcibios_init : PCI BIOS revision 2.10 entry at 0xf0dc0
Probing PCI hardware.
hd0: QUANTUM FIREBALLP AS40.0, 38172MB w/1902kB Cache, CHS=4866/255/63
hd2: LG DVD-ROM DRD-8160B, ATAPI CDROM drive
hd3: LG CD-RW CED-8120B, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
Failed initialization of WD-7000 SCSI card!
EATA0: address 0x1f0 in use, skipping probe.
EATA0: address 0x170 in use, skipping probe.
ppa: Version 1.42
ppa: Probing port 03bc
ppa: Probing port 0378
ppa:     SPP port present
ppa:     ECP with a 16 byte FIFO present
ppa:     PS/2 bidirectional port present
ppa:     Failed Intel bug check. (Phony EPP in ECP)
ppa: Probing port 0278
scsi : 0 hosts.
scsi : detected total.
3c59x.c:v0.99L 5/28/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
eth0: 3Com 3c905C Tornado at 0xa000,  00:01:03:ce:40:17, IRQ 5
  8K byte-wide RAM 5:3 Rx:Tx split, 10baseT interface.
  Enabling bus-master transmits and whole-frame receives.
0 3c515 cards found.
eth1: D-Link DE-600 pocket adapter: not at I/O 0x378.
D-Link DE-620 pocket adapter not identified in the printer port
...


And on OSKit-Mach:

<7>Probing hpplus
<7>Probing ac3200
<7>Probing ne
<7>Probing e2100
<7>Probing at1700
<7>Probing fmv18x
<7>Probing eth16i
<7>Probing etherlink3
<7>Probing znet
<7>Probing eexpress
<7>Probing eepro
<7>Probing ewrk3
<7>Probing de4x5
<7>Probing etherlink
<7>Probing etherlink16
<7>Probing etherlinkplus
<7>Probing sk_g16
<7>Probing ni52
<7>Probing ni65
<7>Probing lance
<7>Probing vortex
<7>Probing epic100
...

And the real output from ping:

PING 161.24.72.1 (161.24.72.1): 56 data bytes
64 bytes from 161.24.73.87: Destination Host Unreachable
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst Data
 4  5  c0 8400 0200   0 0000  ff  01 d7e5 161.24.73.87  161.24.73.87
64 bytes from 161.24.73.87: Destination Host Unreachable
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst Data
 4  5  c0 8400 0300   0 0000  ff  01 d6e5 161.24.73.87  161.24.73.87
--- 161.24.72.1 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss


I use 3COM Diagnostc for Windows to configure the NIC to half-duplex
(instead of auto-detect), normal (instead of nmin CPU usage) and 10baseT
(instead of auto)... but no effect!!!

> Thanks
> MattG
Thank you!

-- 
Ciro Cavani <cavani@h8.ita.br>
Instituto Tecnológico de Aeronáutica