Message-ID: <000501c0537d$4ca0d500$0a02a8c0@speedy>
From: "Ron Sinclair"
Date: Tue, 21 Nov 2000 14:38:37 +0900
Subject: NIC problem
I'm located in Japan and I'm running Suse 6.4. I wanted to set up a
2-computer network and I didn't want to buy NICs from the US since I always
get raped with S/H charges. I went to a local store and bought 2 japanese
manufactured cards, Elecom's Laneed LD-10/100ALs.
These cards are supposedly Linux-compatible because the packaging have
TurboLinux icons on them. I've had headaches getting them to run with Linux
though. Suse wouldn't detect this card automatically. I did a websearch on
"Elecom Laneed LD-10/100AL" and came up with a ton of hits (Altavista and
Google) but ALL the hit sites were in Japanese. I perused them anyways and
saw that people using this card use the via-rhine NIC driver. I tried using
this driver with Suse and Suse spit back a "resource or device busy" or
something to that effect.
I then decided that since the TurboLinux icons are on the packaging, I
should try to install TurboLinux 6.0 and get the NIC working with that
distro first. I installed TL and the nic was detected, but I had to use the
82596.o driver. This driver also included the comment "common driver".
Also, I still didn't know how to test the NIC, other than pinging its IP
addy, which I did. The pinging worked. Another thing: would a common
driver fully support this card or would I just get mediocre performance?
I hate TL with a passion so I decided to go back to Suse and try to get it
working again. It is detected using Suse's 82596.o drivers but still not
the via-rhine or the via-rhineII ones. I've also tried other distros (RH
6.0 and 6.1 and Slackware 7.0) with the same effect.
It seems that others have gotten this card to work with Linux using the
via-rhine drivers but I cannot figure out why I cannot. I must be doing
something wrong.....
I know my best bet is to get 2 NICs that are easier to set up, but now I'm a
bit intrigued as to why I cannot get these to work when others have.
For now, I'll include what's happening with the NICs and my linux box. The
below text is what 'dmesg | more' spouts out. I also show pinging sessions
after modprobing 82596:
[root@POS2 /root]# dmesg | more
Linux version 2.2.14-15mdk (root@kenobi.mandrakesoft.com) (gcc version
2.95.2 19
991024 (release)) #1 Tue Jan 4 22:24:20 CET 2000
Detected 200455852 Hz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 399.77 BogoMIPS
Memory: 63024k/65536k available (1092k kernel code, 416k reserved, 940k
data, 64
k init, 0k bigmem)
Dentry hash table entries: 262144 (order 9, 2048k)
Buffer cache hash table entries: 65536 (order 6, 256k)
Page cache hash table entries: 16384 (order 4, 64k)
VFS: Diskquotas version dquot_6.4.0 initialized
CPU: Intel Pentium MMX stepping 03
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
Intel Pentium with F0 0F bug - workaround enabled.
POSIX conformance testing by UNIFIX
PCI: PCI BIOS revision 2.10 entry at 0xfb2d0
PCI: Using configuration type 1
PCI: Probing PCI hardware
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
TCP: Hash tables configured (ehash 65536 bhash 65536)
Initializing RT netlink socket
Starting kswapd v 1.5
Detected PS/2 Mouse Port.
Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
pty: 256 Unix98 ptys configured
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.9)
Real Time Clock Driver v1.09
RAM disk driver initialized: 16 RAM disks of 4096K size
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
hda: WDC WD205BA, ATA DISK drive
hdb: Pioneer CD-ROM ATAPI Model DR-A24X 0107, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: WDC WD205BA, 19574MB w/2048kB Cache, CHS=2495/255/63
hdb: ATAPI 20X CD-ROM drive, 128kB Cache
Uniform CDROM driver Revision: 2.56
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12
raid5: measuring checksumming speed
raid5: MMX detected, trying high-speed MMX checksum routines
pII_mmx : 304.419 MB/sec
p5_mmx : 362.712 MB/sec
8regs : 219.075 MB/sec
32regs : 171.069 MB/sec
using fastest function: p5_mmx (362.712 MB/sec)
scsi : 0 hosts.
scsi : detected total.
md.c: sizeof(mdp_super_t) = 4096
Partition check:
hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 hda10 hda11 hda12 >
autodetecting RAID arrays
autorun ...
... autorun DONE.
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 64k freed
Adding Swap: 257000k swap-space (priority -1)
eth0: 82596 at 0x300, 20 7A 84 C4 48 50 IRQ 10.
82596.c:v1.0 15/07/98
eth0: lp at 0xc3fdbb60, lp->scb at 0xc3fdbb74
eth0: i596_open() irq 10.
eth0: init_rx_bufs 16.
eth0: starting i82596.
eth0: i82596 initialization timed out with status 0000, cmd 0000.
eth0: receive unit start timed out with status 0000, cmd 0100.
i82596 init timed out with status 0000, cmd 0010.
eth0: set multicast list, 0 entries, promisc OFF, allmulti OFF
eth0: set multicast list, 1 entries, promisc OFF, allmulti OFF
eth0: Adding address 01:00:5e:00:00:01
eth0: set multicast list, 1 entries, promisc OFF, allmulti OFF
eth0: Adding address 01:00:5e:00:00:01
eth0: set multicast list, 1 entries, promisc OFF, allmulti OFF
eth0: Adding address 01:00:5e:00:00:01
VFS: Disk change detected on device ide0(3,64)
ISO 9660 Extensions: Microsoft Joliet Level 1
ISO 9660 Extensions: RRIP_1991A
VFS: Disk change detected on device fd(2,0)
end_request: I/O error, dev 02:00 (floppy), sector 0
[root@POS2 /root]# ifconfig
eth0 Link encap:Ethernet HWaddr 20:7A:84:C4:48:50
inet addr:192.168.2.20 Bcast:192.168.2.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:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:10 Base address:0x300 Memory:c3fdbb60-0
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:18 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
HERE, I'M TRYING TO PING MY OTHER SYSTEM, WITH NO SUCCESS
[root@POS2 /root]# ping 192.168.2.10
PING 192.168.2.10 (192.168.2.10): 56 data bytes
<p>[1]+ Stopped ping 192.168.2.10
[root@POS2 /root]#
[root@POS2 /root]# ping pos2
PING POS2.zma.attmil.ne.jp (192.168.2.20): 56 data bytes
64 bytes from 192.168.2.20: icmp_seq=0 ttl=255 time=0.3 ms
64 bytes from 192.168.2.20: icmp_seq=1 ttl=255 time=0.2 ms
64 bytes from 192.168.2.20: icmp_seq=2 ttl=255 time=0.2 ms
64 bytes from 192.168.2.20: icmp_seq=3 ttl=255 time=0.2 ms
64 bytes from 192.168.2.20: icmp_seq=4 ttl=255 time=0.2 ms
[3]+ Stopped ping pos2
[root@POS2 /root]#
[root@POS2 /root]# ifconfig
eth0 Link encap:Ethernet HWaddr 20:7A:84:C4:48:50
inet addr:192.168.2.20 Bcast:192.168.2.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:18 errors:11 dropped:0 overruns:0 carrier:11
collisions:0 txqueuelen:100
Interrupt:10 Base address:0x300 Memory:c3fdbb60-0
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:46 errors:0 dropped:0 overruns:0 frame:0
TX packets:46 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
[root@POS2 /root]#
I'm losing my sanity with this, so some help would be GREATLY appreciated!
:o)
