ncr53c8xx and wd 8013 NIC problem

ncr53c8xx and wd 8013 NIC problem

Post by phun.. » Thu, 09 Nov 2000 04:00:00



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.

 
 
 

ncr53c8xx and wd 8013 NIC problem

Post by phun.. » Thu, 09 Nov 2000 04:00:00


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.

 
 
 

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. Help - Linux won't boot off floppy

3. VTxxx terminal installation

4. wd 8013 NIC and ncr53c8xx problem

5. Xtank - Netrek

6. WD 8013 NIC: Strange I/O address problem

7. Errors in the VM - detailed

8. wd 8013 networking problem

9. Ethernet: WD 8013 soft irq config?

10. wd 8013 changing base address?

11. SMC Elite16 as WD 8013 fails

12. SMC PLUS Elite 16T (WD 8013)