WD 8013 NIC: Strange I/O address problem

WD 8013 NIC: Strange I/O address problem

Post by Rohan Ober » Tue, 01 Jun 1999 04:00:00



I have a WD8013W card in my Compaq Prolinea 486DX2/50 (RedHat
5.2/2.0.36) that is behaving very strangely -- surprisingly, because I
have had two Intel EtherExpress NICs working more or less well in that
system for months, and the WD is supposed to be an older and better
tested Linux driver.  Perhaps this is a bug in the driver with this
hardware?

At boot time, the card is recognised properly, as seen in dmesg:

eth0: WD80x3 at 0x280,  00 00 C0 E5 38 27 WD8013, IRQ 5, shared memory
at 0xd0000-0xd3fff.

However, at ifconfig the card comes up with the last line reporting:

Interrupt:5 Base address:0x290 Memory:d0000-d4000

It looks like the base I/O address and the upper memory range are both
being bumped up.  When I put another WD in the system (which is
reported by the SMC EZSETUP program as I/O 300 IRQ 10) it shows up at
"Base address:0x310".

I searched on Deja(News) and found one report of a similar problem,
from 1997, which was fixed through the PnP bios settings: I append
that report.

If anyone knows anything about this "I/O +10" bug/feature, and has any
idea about a workaround, I'd appreciate hearing about it.  Please
remove the obvious from my address if replying by email.

Regards,
Rohan.

========================================================================

   Subject: Q: Turn off ethernet card autoprobe on boot?
   Date: 1997/10/05
   Author: rcattig # mindspring O com (Craig Attig)

   I have an SMC Ultra ethernet card. Running ISAPNP.SYS on NT, it comes
   in as IRQ 10, Addr 0x300, Mem 0xCC000. And this config works for
   talking to another nearby machine.

   Booting into RH 4.2, however, the card is autoprobed and comes back as
   IRQ 10, >>> Addr 0x310 <<<. Mem 0xCC000. The card then does not seem
   to work -- no big surprise -- as ifconfig shows 0 packets for both TX
   and RX.

   I've tried to boot with 'linux ether=10,0x300,0,0,eth0' but this
   doens't seem to get around the autoprobe'd settings.

   How do I turn off autoprobing for this card?

========================================================================

   Subject: Re: Q: Turn off ethernet card autoprobe on boot?
   Date: 1997/10/05
   Author: rcattig # mindspring O com (Craig Attig)

   Lars,

   >> I have an SMC Ultra ethernet card. Running ISAPNP.SYS on NT, it
   comes
   >> in as IRQ 10, Addr 0x300, Mem 0xCC000. And this config works for
   >> talking to another nearby machine.
   >>
   >> Booting into RH 4.2, however, the card is autoprobed and comes back
   as
   >> IRQ 10, >>> Addr 0x310 <<<. Mem 0xCC000. The card then does not
   seem
   >> to work -- no big surprise -- as ifconfig shows 0 packets for both
   TX
   >> and RX.

   >It sounds like you're using a module for your card...
   >options smc-ultra io=0x300

   I've looked more closely into what's going on. SMC-ULTRA.C does
   correctly identify the card as running at addr 0x300 using autoprobe
   at boot, but upon 'ifconfig' it still comes up as set to addr=0x310.

   I've tried adding the line 'options smc-ultra io=0x300' to my
   /etc/conf.modules file, but this doesn't do anything (the card *is*
   correctly id'd, after all), and booting with the similar option 'linux
   options smc-ultra io=0x300', but to no avail. I've also tried to take
   down the card manually, 'ifconfig eth0 down' and bring it back up
   ('ifconfig eth0 inet 192.168.... bla bla bla) with ifconfig's
   'io_addr' option, but ifconfig seems to *on that option.

   Any ideas?

========================================================================

   Subject: Re: Q: Turn off ethernet card autoprobe on boot?
   Date: 1997/10/05

   I've finally mamanged to get things to work!!! I want to thank
   everybody who lent a hand and pitched in with advice. It helped --
   thank you!!

   Ultimately, I needed to change the PNP BIOS setting on my motherboard
   such that the IRQ's I know were taken were set aside as "Legacy ISA"
   IRQ's. Every IRQ I knew about I set up that way. Strnage thing is that
   'ifconfig' still reports the eth0 device as being at 0x310 when it's
   clearly not -- autoprobing comes up 0x300, and NT runs it as 0x300.
   But, hey, it works now, and that's all I care about. :)

========================================================================

 
 
 

WD 8013 NIC: Strange I/O address problem

Post by Mirce » Tue, 01 Jun 1999 04:00:00


I doubt it's the driver for wd80x3. All of the NICs that I use show the
same behavior, including wd8013, smc-Ultra, smc-EtherEZ, and 3c509. For
each of them, ifconfig reports an i/o address higher than the one the
card actually is at, as it shows in /proc/ioports. But all work well, so
I didn't look into it. As an example, I have in the machine I'm typing
on now a 3c509 at 0x300, which shows 0x310 in ifconfig. Go figure. It's
probably the midrange of the i/o space used, i.e 0x310 for 0x300-0x31f.

MST


> (..)
> It looks like the base I/O address and the upper memory range are both
> being bumped up.  When I put another WD in the system (which is
> reported by the SMC EZSETUP program as I/O 300 IRQ 10) it shows up at
> "Base address:0x310".
> (..)


 
 
 

WD 8013 NIC: Strange I/O address problem

Post by Rohan Ober » Tue, 01 Jun 1999 04:00:00


Thanks to all who replied to tell me that it's perfectly normal for
the wd.c driver to report an I/O address of (say) 310 when the card is
at 300.  

The 8013W card still won't ping anything, and I'm beginning to suspect
it's just not compatible with the computer (Compaq Prolinea 486DX/50).

(I would try to change the Compaq's BIOS settings, but pressing F10 or
anything else at boot time just brings up angry beeping noises, and
doesn't stop the computer from going ahead and booting.  If anyone
knows how I might get into the BIOS, do let me know...)

To try to debug the problem, I put back the two Intel EtherExpress
cards that work fine with this computer and verified that both eth0
(external network) and eth1 (internal network) ping fine.

Then I swapped out the eexpress on eth1 (io300, irq10) with one of the
8013W's.  Now eth0 still works but eth1 won't ping the other computer
that's on the internal network.  I ran linuxconf to try to get it to
persuade the card to play ball, but it didn't work.

In my now rather befuddled state I imagine this means that I've
narrowed down the problem to the SMC card compatability (after all,
the EtherExpress in the same slot at the same IRQ/IO worked fine two
minutes ago).  And I have three SMC cards that I've been
interchanging, so it seems unlikely that all of them are defective;
besides, they are detected fine at boot time.  

I don't see how it could be a driver problem as the SMC EZSETUP
utility reports these cards as 8013W, and I'm using the wd driver
which finds the card at system startup.

In case anyone sees anything I've missed that would explain why the
SMC's aren't working, here's the output of dmesg, ifconfig, route -n
and netstat -a.  I'm going back to the EtherExpress's for now, but
would really like to hear from anyone who thinks he knows how to get
the SMC's working!  :)

Regards,
Rohan.

(please remove TAKETHISOUT from my address if replying by email).

====================================================== dmesg

Memory: sized by int13 088h
Console: 16 point font, 400 scans
Console: colour VGA+ 80x25, 1 virtual console (max 63)
Calibrating delay loop.. ok - 24.93 BogoMIPS
Memory: 14932k/16384k available (612k kernel code, 384k reserved, 456k data)
This processor honours the WP bit even when in supervisor mode. Good.
Swansea University Computer Society NET3.035 for Linux 2.0
NET3: Unix domain sockets 0.13 for Linux NET3.035.
Swansea University Computer Society TCP/IP for NET3.034
IP Protocols: ICMP, UDP, TCP
Checking 386/387 coupling... Ok, fpu using exception 16 error reporting.
Checking 'hlt' instruction... Ok.

 (gcc version 2.7.2.3) #7 Sun May 30 13:34:06 EDT 1999
Starting kswapd v 1.4.2.2
hda: QUANTUM LPS210A, 201MB w/98kB Cache, CHS=723/15/38
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
eth0: EtherExpress at 0x270, IRQ 5, Interface 10baseT, 32k




eth1: WD80x3 at 0x300,  00 00 C0 65 20 2B WD8013, IRQ 10,
 shared memory at 0xcc000-0xcffff.
Partition check:
 hda: hda1 hda2
VFS: Mounted root (ext2 filesystem) readonly.
Adding Swap: 16524k swap-space (priority -1)

====================================================== ifconfig

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
          UP BROADCAST LOOPBACK RUNNING  MTU:3584  Metric:1
          RX packets:7 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0

eth0      Link encap:Ethernet  HWaddr 00:AA:00:40:99:29  
          inet addr:209.6.194.219  Bcast:209.6.194.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2328 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3331 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
          Interrupt:5 Base address:0x270

eth1      Link encap:Ethernet  HWaddr 00:00:C0:65:20:2B  
          inet addr:192.168.1.1  Bcast:192.168.1.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:15 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
          Interrupt:10 Base address:0x310 Memory:cc000-d0000

====================================================== route -n

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
209.6.194.0     0.0.0.0         255.255.255.0   U     0      0        4 eth0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        2 eth1
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        1 lo
0.0.0.0         209.6.194.218   0.0.0.0         UG    0      0        7 eth0

====================================================== netstat -a

Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State      
tcp        0      0 DEFAULT.sbo-smr.m:nterm shell3.shore.net:telnet ESTABLISHED
tcp        0      0 *:linuxconf             *:*                     LISTEN      
tcp        0      0 *:telnet                *:*                     LISTEN      
udp        0      0 *:syslog                *:*                                
raw        0      0 *:1                     *:*                                
Active UNIX domain sockets (including servers)
Proto RefCnt Flags       Type       State         I-Node Path
unix  2      [ ]         STREAM                   522    /dev/log
unix  2      [ ]         STREAM     CONNECTED     521    
unix  1      [ ACC ]     STREAM     LISTENING     471    /dev/log

 
 
 

WD 8013 NIC: Strange I/O address problem

Post by Rohan Ober » Tue, 01 Jun 1999 04:00:00


An update: I put an 8013WC in at eth1 (io300, irq10) and it pings
fine.  The 8013W's still do not work.  

Anyone know the difference between the 8013W and the 8013WC that might
explain this?  The 8013W's are marked WDC, 1990 and are jumpered to
"soft" io/irq/ram.  They pass all the SMC EZSTART tests.  The 8013WC
is marked SMC, 1992, similarly jumpered, and passes all the tests.

Regards,
Rohan


>Thanks to all who replied to tell me that it's perfectly normal for
>the wd.c driver to report an I/O address of (say) 310 when the card is
>at 300.  

>The 8013W card still won't ping anything, and I'm beginning to suspect
>it's just not compatible with the computer (Compaq Prolinea 486DX/50).

>(I would try to change the Compaq's BIOS settings, but pressing F10 or
>anything else at boot time just brings up angry beeping noises, and
>doesn't stop the computer from going ahead and booting.  If anyone
>knows how I might get into the BIOS, do let me know...)

>To try to debug the problem, I put back the two Intel EtherExpress
>cards that work fine with this computer and verified that both eth0
>(external network) and eth1 (internal network) ping fine.

>Then I swapped out the eexpress on eth1 (io300, irq10) with one of the
>8013W's.  Now eth0 still works but eth1 won't ping the other computer
>that's on the internal network.  I ran linuxconf to try to get it to
>persuade the card to play ball, but it didn't work.

>In my now rather befuddled state I imagine this means that I've
>narrowed down the problem to the SMC card compatability (after all,
>the EtherExpress in the same slot at the same IRQ/IO worked fine two
>minutes ago).  And I have three SMC cards that I've been
>interchanging, so it seems unlikely that all of them are defective;
>besides, they are detected fine at boot time.  

>I don't see how it could be a driver problem as the SMC EZSETUP
>utility reports these cards as 8013W, and I'm using the wd driver
>which finds the card at system startup.

>In case anyone sees anything I've missed that would explain why the
>SMC's aren't working, here's the output of dmesg, ifconfig, route -n
>and netstat -a.  I'm going back to the EtherExpress's for now, but
>would really like to hear from anyone who thinks he knows how to get
>the SMC's working!  :)

>Regards,
>Rohan.

>(please remove TAKETHISOUT from my address if replying by email).

>====================================================== dmesg

>Memory: sized by int13 088h
>Console: 16 point font, 400 scans
>Console: colour VGA+ 80x25, 1 virtual console (max 63)
>Calibrating delay loop.. ok - 24.93 BogoMIPS
>Memory: 14932k/16384k available (612k kernel code, 384k reserved, 456k data)
>This processor honours the WP bit even when in supervisor mode. Good.
>Swansea University Computer Society NET3.035 for Linux 2.0
>NET3: Unix domain sockets 0.13 for Linux NET3.035.
>Swansea University Computer Society TCP/IP for NET3.034
>IP Protocols: ICMP, UDP, TCP
>Checking 386/387 coupling... Ok, fpu using exception 16 error reporting.
>Checking 'hlt' instruction... Ok.

> (gcc version 2.7.2.3) #7 Sun May 30 13:34:06 EDT 1999
>Starting kswapd v 1.4.2.2
>hda: QUANTUM LPS210A, 201MB w/98kB Cache, CHS=723/15/38
>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
>Floppy drive(s): fd0 is 1.44M
>FDC 0 is a post-1991 82077
>eth0: EtherExpress at 0x270, IRQ 5, Interface 10baseT, 32k




>eth1: WD80x3 at 0x300,  00 00 C0 65 20 2B WD8013, IRQ 10,
> shared memory at 0xcc000-0xcffff.
>Partition check:
> hda: hda1 hda2
>VFS: Mounted root (ext2 filesystem) readonly.
>Adding Swap: 16524k swap-space (priority -1)

>====================================================== ifconfig

>lo        Link encap:Local Loopback  
>          inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
>          UP BROADCAST LOOPBACK RUNNING  MTU:3584  Metric:1
>          RX packets:7 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0

>eth0      Link encap:Ethernet  HWaddr 00:AA:00:40:99:29  
>          inet addr:209.6.194.219  Bcast:209.6.194.255  Mask:255.255.255.0
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:2328 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:3331 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0
>          Interrupt:5 Base address:0x270

>eth1      Link encap:Ethernet  HWaddr 00:00:C0:65:20:2B  
>          inet addr:192.168.1.1  Bcast:192.168.1.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:15 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0
>          Interrupt:10 Base address:0x310 Memory:cc000-d0000

>====================================================== route -n

>Kernel IP routing table
>Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
>209.6.194.0     0.0.0.0         255.255.255.0   U     0      0        4 eth0
>192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        2 eth1
>127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        1 lo
>0.0.0.0         209.6.194.218   0.0.0.0         UG    0      0        7 eth0

>====================================================== netstat -a

>Active Internet connections (including servers)
>Proto Recv-Q Send-Q Local Address           Foreign Address         State      
>tcp        0      0 DEFAULT.sbo-smr.m:nterm shell3.shore.net:telnet ESTABLISHED
>tcp        0      0 *:linuxconf             *:*                     LISTEN      
>tcp        0      0 *:telnet                *:*                     LISTEN      
>udp        0      0 *:syslog                *:*                                
>raw        0      0 *:1                     *:*                                
>Active UNIX domain sockets (including servers)
>Proto RefCnt Flags       Type       State         I-Node Path
>unix  2      [ ]         STREAM                   522    /dev/log
>unix  2      [ ]         STREAM     CONNECTED     521    
>unix  1      [ ACC ]     STREAM     LISTENING     471    /dev/log

 
 
 

1. ncr53c8xx and wd 8013 NIC problem

Hello

I have a problem with my ncr53c810 card (Asus SC200) and a SMC Elite 16
T network card (WD 8013). My machine runs under Debian Linux 2.2 and it
uses the ncr53c8xx driver which is compiled into the kernel. When the
NCR-bios of the motherboard is turned on the NIC is not working although
the wd.o module is loaded correctly and the eth0 interface is up. When I
turn the SDMS-bios support off everything works fine. At the moment I'm
booting from floppy and I can mount the SCSI partitions but I can't boot
from SCSI. So how to solve the SDMS-bios problem? Is it possible that
the bios is interfering with the memory of my NICs?

My NICs are on:
eth0: irq=10, io=0x300, mem=0xCC000
eth1: irq=3,  io=0x280, mem=0xD0000

My ncr53c810 is on irq=11, io=0xe400

My machine:
Debian 2.2 kernel 2.2.17, vanilla kernel, ncr53c8xx driver compiled into
kernel. To make SMC nic running according to ethernet HOWTO using kernel
parameter 'reserve=0x300,32,0x200,32 ether=10,0x300,eth0'
Asus P/I-TP55N motherboard, Asus SC200 SCSI adapter, 32 MB RAM, Pentium
133, 2 SMC Elite 16T network cards.

Kernelmessages concerning SCSI:
sym53c8xx: at PCI bus 0, device 12, function 0
sym53c8xx: not initializing, device not supported
ncr53c8xx: at PCI bus 0, device 12, function 0
ncr53c8xx: PCI_LATENCY_TIMER=0, bursting should'nt be allowed.
ncr53c8xx: 53c810 detected
ncr53c810-0: rev=0x01, base=0xdf800000, io_port=0xe400, irq=11
ncr53c810-0: ID 7, Fast-10, Parity Checking
ncr53c810-0: restart (scsi reset).scsi0 : ncr53c8xx - version 3.2a-2
scsi : 1 host.
  Vendor: IBM       Model: DCAS-34330        Rev: S60B
  Type:   Direct-Access                      ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
  Vendor: IOMEGA    Model: ZIP 100           Rev: E.08
  Type:   Direct-Access                      ANSI SCSI revision: 02
Detected scsi removable disk sdb at scsi0, channel 0, id 2, lun 0
  Vendor: JVC       Model: XR-W2010          Rev: 1.51
  Type:   WORM                               ANSI SCSI revision: 02
Detected scsi CD-ROM sr0 at scsi0, channel 0, id 6, lun 0
ncr53c810-0-<0,0>: tagged command queue depth set to 4
scsi : detected 1 SCSI cdrom 2 SCSI disks total.
ncr53c810-0-<6,*>: device did not report SYNC.
Uniform CD-ROM driver Revision: 3.11
ncr53c810-0-<0,*>: FAST-5 SCSI 5.0 MB/s (200 ns, offset 8)
SCSI device sda: hdwr sector= 512 bytes. Sectors= 8467200 [4134 MB] [4.1
GB]
ncr53c810-0-<2,*>: device did not report SYNC.

Thank you in advance.

regards

-Olaf

Sent via Deja.com http://www.deja.com/
Before you buy.

2. GlidePoint 'tap' support in X3.2?

3. linux swap problem

4. wd 8013 NIC and ncr53c8xx problem

5. set_new_handler problem

6. ncr53c8xx and wd 8013 NIC problem

7. Problems Migrating from Solaris 2.5 o 2.6..

8. wd 8013 changing base address?

9. wd 8013 networking problem

10. Ethernet: WD 8013 soft irq config?

11. SMC Elite16 as WD 8013 fails

12. SMC PLUS Elite 16T (WD 8013)