Debian + Windows 98 + ADSL...

Hi,
I have a windows 98 box that I wish to network to my Debian box, which is in
turn hooked up to ADSL modem via ethernet.
My problem is this; I can't get a link light on eth1. It can ping itself,
but not the 98 box.

There are a couple of errors that I suspect are the relevant details;
ifconfig shows TX errors; Atlantic says "bus error detected"; and probably
most important, "eth1: Tx timed out, lost interrupt? TSR=0x41, ISR=0x2,
t=808."

I have IRQ 4 set as Legacy ISA in the BIOS. I am stuck for what to do. Any
help appreciated. Thanks.

The hardware and dumps are as follows:
____________________________________
____________________________________
ADSL Modem -> Debian Box via Ethernet (eth0), PCI tlan card, working fine.

Debian Box: (runnning 3.0)

eth0: PCI tlan card, dynamically assigned IP from modem. Working fine.
eth1: ISA nic - Magitronic I-E16-Combo-5
Using ne2000 module
Appears fine. Pings itself, can't ping 'doze box

Windows Box:

IP 192.168.0.2, netmask 255.255.255.0
NIC works fine connected to ADSL modem
Can ping itself, not the linux box
_____________________________________
_____________________________________
Various dumps below:

IFCONFIG:
eth1 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:4 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:540 (540.0 b)
Interrupt:4 Base address:0x300

ATLANTIC:
Reading the configuration from the AT/LANTIC at 0x300...
The current configuration is
Register A 0x4c: I/O base @ 0x2c0, IRQ 4, NE2000 mode, fast ISA read.
Register B 0xff: Interface 10baseT (LRT).
Boot PROM writes are enabled, CHRDY after BALE, IO16 after IORD/IOWR.
Bus error detected.

DMESG:
ThunderLAN driver v1.3c
TLAN: eth0 irq=10 io=6500, Olicom OC-2326, Rev. 1
ne.c:v1.10 9/23/94 Donald Becker ((E-Mail Removed))
NE*000 ethercard probe at 0x300: 00 40 05 25 30 bd
eth1: NE2000 found at 0x300, using IRQ 4.
eth1: Tx timed out, lost interrupt? TSR=0x41, ISR=0x2, t=808.
eth1: Tx timed out, lost interrupt? TSR=0x41, ISR=0x2, t=1000.

cat /proc/interrupts
CPU0
0: 54831 XT-PIC timer
1: 802 XT-PIC keyboard
2: 0 XT-PIC cascade
4: 0 XT-PIC NE2000
8: 3 XT-PIC rtc
10: 1116 XT-PIC TLAN
12: 13463 XT-PIC PS/2 Mouse
13: 1 XT-PIC fpu
14: 135915 XT-PIC ide0
NMI: 0

cat /proc/net/dev
Inter-| Receive | Transmit
face |bytes packets errs drop fifo frame compressed multicast|bytes
packets errs drop fifo colls carrier compressed
lo: 12892 242 0 0 0 0 0 0 12892
242 0 0 0 0 0 0
eth0: 238228 562 0 0 0 0 0 0 86403
568 0 0 0 0 0 0
eth1: 0 0 0 0 0 0 0 0 540
0 4 0 0 0 0 0
ppp0: 230817 560 0 0 0 0 0 0 91081
566 0 0 0 0 0 0

route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface

On Sun, 8 Feb 2004 18:02:52 -0500, Hmmmmm
<(E-Mail Removed)> wrote:

> My problem is this; I can't get a link light on eth1.

The driver isn't able to configure the card, or the cable is wrong or bad.


> I have IRQ 4 set as Legacy ISA in the BIOS. I am stuck for what to
> do. Any help appreciated. Thanks.

IRQ 4 is usually COM1. You can't share interrupts on ISA. Maybe you
can change the NIC to another interrupt or turn off COM1 in the BIOS.


--
-| Bob Hauck
-| To Whom You Are Speaking
-| http://www.haucks.org/

Cheers for the reply bob,

Bob Hauck <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ...
> On Sun, 8 Feb 2004 18:02:52 -0500, Hmmmmm
> <(E-Mail Removed)> wrote:
> The driver isn't able to configure the card, or the cable is wrong or bad.

Well, I can eliminate the cable problem, as the cable works fine if I switch
it with the one to the modem.
As for the driver not able to configure the card, it seems fine. There are
no errors given on the probe, eth1 is set up fine, it can ping itself, the
problem is that it seems to have issues when I try to do anything with it.
I have heard that the Magitronic cards are a heap of junk, but I have seen
several threads aroudn the place with ostensibly decent hardware showing the
same error.
Incidentally, I failed to post the netstat -nr result, which is as expected;
192.168.0.0, n\mask 255.255.255.0 device eth1. The network should be
available, but the card is knackered I suspect. Off to buy a new pci card
tomorrow

> IRQ 4 is usually COM1. You can't share interrupts on ISA. Maybe you
> can change the NIC to another interrupt or turn off COM1 in the BIOS.

COM1 is off. cat /proc/interrupts gives no conflict, but a '0' in the column
that seems like it should have numbers in...will look more into that.
Atlantic can't write the EEPROM, and the DOS module doesn't work.
i am jacking in the card if this isn't solved tonight. It's frustrating me
to the point that I'm thinking of watching the Grammys!!

Hmmmmm <(E-Mail Removed)> wrote:
> Hi,
> I have a windows 98 box that I wish to network to my Debian box, which is in
> turn hooked up to ADSL modem via ethernet.
> My problem is this; I can't get a link light on eth1. It can ping itself,
> but not the 98 box.

You need a crossover cable between the two computers.
Chris