Hi All!

I got a A7v133 motherboard.

This mother board is provided with 2 IDE controller, the first based on
VIA chipset and the other is a Promise ATA100 (with raid support).

I tried to boot with both latest NetBSD/1386 snapshot and current but i
got the following errors:

NetBSD 1.5U (GENERIC) #1: Thu Apr 26 16:56:29 UTC 2001
    root@netapp:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: AMD Athlon Model 4 (Thunderbird) (686-class), 857.71 MHz
cpu0: features 183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR>
cpu0: features 183f9ff<PGE,MCA,CMOV,FGPAT,PSE36,MMX,FXSR>
total memory = 65060 KB
avail memory = 54896 KB
using 838 buffers containing 3352 KB of memory
BIOS32 rev. 0 found at 0xf0f50
mainbus0 (root)
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled
pchb0 at pci0 dev 0 function 0
pchb0: VIA Technologies VT8363 KT133 System Controller (rev. 0x03)
ppb0 at pci0 dev 1 function 0: VIA Technologies VT8363 KT133 PCI to AGP
Bridge (rev. 0x00)
pci1 at ppb0 bus 1
pci1: i/o space, memory space enabled
vga1 at pci1 dev 0 function 0: ATI Technologies Rage XL AGP 2x (rev.
0x65)
wsdisplay0 at vga1: console (80x25, vt100 emulation)
pcib0 at pci0 dev 4 function 0
pcib0: VIA Technologies VT82C686A (Apollo KX133) PCI-ISA Bridge (rev.
0x40)
pciide0 at pci0 dev 4 function 1: VIA Tech VT82C586A IDE Controller
(rev. 0x06)
pciide0: bus-master DMA support present
pciide0: Ultra/33 capable
pciide0: primary channel configured to compatibility mode
wd0 at pciide0 channel 0 drive 0: <IBM-DPTA-372050>
wd0: drive supports 16-sector PIO transfers, LBA addressing
wd0: 19574 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 40088160
sectors
wd0: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 4 (Ultra/66)
wd1 at pciide0 channel 0 drive 1: <QUANTUM FIREBALLlct20 20>
wd1: drive supports 8-sector PIO transfers, LBA addressing
wd1: 19470 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 39876480
sectors
wd1: 32-bit data port
wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
pciide0: primary channel interrupting at irq 14
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33) (using
DMA data transfers)
wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33) (using
DMA data transfers)
pciide0: secondary channel configured to compatibility mode
pciide0: disabling secondary channel (no drives)
uhci0 at pci0 dev 4 function 2: VIA Technologies VT83C572 USB Controller
(rev. 0x16)
uhci0: interrupting at irq 10
usb0 at uhci0: USB revision 1.0uhub1 at usb1
uhub1: VIA Technologie UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
pchb1 at pci0 dev 4 function 4
pchb1: VIA Technologies VT82C686A SMBus Controller (rev. 0x40)
rtk0 at pci0 dev 11 function 0: RealTek 8139 10/100BaseTX
rtk0: interrupting at irq 5
rtk0: Ethernet address 00:00:b4:aa:c7:66
ukphy0 at rtk0 phy 7: Generic IEEE 802.3u media interface
ukphy0: OUI 0x000000, model 0x0000, rev. 0
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pciide1 at pci0 dev 17 function 0: Promise Ultra100/ATA Bus Master IDE
Accelerator (rev. 0x02)
pciide1: bus-master DMA support present
pciide1: primary channel configured to native-PCI mode
pciide1: using irq 5 for native-PCI interrupt
pciide1: disabling primary channel (no drives)
pciide1: secondary channel configured to native-PCI mode
wd2 at pciide1 channel 1 drive 0: <QUANTUM FIREBALLP LM20.5>
wd2: drive supports 16-sector PIO transfers, LBA addressing
wd2: 19595 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 40132503
sectors
wd2: 32-bit data port
wd2: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 4 (Ultra/66)
wd3 at pciide1 channel 1 drive 1: <QUANTUM FIREBALLlct20 20>
wd3: drive supports 8-sector PIO transfers, LBA addressing
wd3: 19470 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 39876480
sectors
wd3: 32-bit data port
wd3: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
wd2(pciide1:1:0): using PIO mode 4, Ultra-DMA mode 4 (Ultra/66) (using
DMA data transfers)
wd3(pciide1:1:1): using PIO mode 4, Ultra-DMA mode 4 (Ultra/66) (using
DMA data transfers)
isa0 at pcib0
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
pckbc0 at isa0 port 0x60-0x64
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
lpt0 at isa0 port 0x378-0x37b irq 7
pcppi0 at isa0 port 0x61
midi0 at pcppi0: PC speaker
sysbeep0 at pcppi0
isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support
npx0 at isa0 port 0xf0-0xff: using exception 16
fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
isapnp0: no ISA Plug 'n Play devices found
biomask ff65 netmask ff65 ttymask ffe7
pciide1:1: bogus intr <---------------------------------???????
boot device: wd0dump device: 
file system (default generic): nfd\^H \^Hs
root on rtk0
nfs_boot: trying DHCP/BOOTP
nfs_boot: BOOTP server: 151.36.176.69
nfs_boot: my_addr=151.36.176.68
nfs_boot: my_mask=255.255.0.0
root on moondust.practive.org:/usr/home/andrea/netbsd

/---- I got these when i mount the filesystems --/
pciide0:0:0: lost interrupt
        type: ata tc_bcount: 2048 tc_skip: 0
pciide0:0:0: bus-master DMA error: missing interrupt, status=0x60
wd0: transfer error, downgrading to Ultra-DMA mode 1
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 1 (using DMA data
transfers)
wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33) (using
DMA data transfers)
wd0a: DMA error writing fsbn 16 of 16-19 (wd0 bn 79; cn 0 tn 1 sn 16),
retrying
wd0: soft error (corrected)
pciide0:0:1: lost interrupt
        type: ata tc_bcount: 2048 tc_skip: 0
pciide0:0:1: bus-master DMA error: missing interrupt, status=0x60
wd1: transfer error, downgrading to Ultra-DMA mode 1
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 1 (using DMA data
transfers)
wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 1 (using DMA data
transfers)
wd1a: aborted command, interface CRC error writing fsbn 16 of 16-19 (wd1
bn 79; cn 0 tn 1 sn 16), retrying
wd1: soft error (corrected)


After that the filesystem came up correctly (or so seems) but i got
system panic when i try to configure raidframe.
The promise controller ,instead, works without errors.

Any Idea?


Bye!