> Via Data Sheets (PDF format)
>
> http://www.via.com.tw/jsp/en/datasheet/datasheets.jsp

Thanks.  It's a JavaScript form, it seems, so I need get to a sandbox
account before I can look at that stuff.


> What processor?

Okay, let's just save time and I'll post the whole dmesg output.  (^&

 /~~~ dmesg

NetBSD 1.5 (rkrGENERIC) #5: Fri Feb 16 18:42:00 CST 2001
    root@rkr1:/usr/src/sys/arch/i386/compile/rkrGENERIC
cpu0: AMD K7 (Athlon) (686-class)
total memory = 127 MB
avail memory = 115 MB
using 1658 buffers containing 6632 KB of memory
BIOS32 rev. 0 found at 0xfb220
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 product 0x0305 (rev. 0x02)
ppb0 at pci0 dev 1 function 0: VIA Technologies product 0x8305 (rev. 0x00)
pci1 at ppb0 bus 1
pci1: i/o space, memory space enabled
pcib0 at pci0 dev 7 function 0
pcib0: VIA Technologies VT82C686A (Apollo KX133) PCI-ISA Bridge (rev. 0x22)
pciide0 at pci0 dev 7 function 1: VIA Tech VT82C586A IDE Controller (rev. 0x10)
pciide0: bus-master DMA support present
pciide0: primary channel configured to compatibility mode
wd0 at pciide0 channel 0 drive 0: <Maxtor 52049H4>
wd0: drive supports 16-sector pio transfers, lba addressing
wd0: 19541 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 40020624 sectors
wd0: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5
pciide0: primary channel interrupting at irq 14
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 (using DMA data transfers)
pciide0: secondary channel configured to compatibility modeatapibus0 at pciide0 channel 1
cd0 at atapibus0 drive 0: <ATAPI 48X CDROM, 48XCDROM Ver3.30, VER-3.3> type 5 cdrom removable
cd0: 32-bit data port
cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2
pciide0: secondary channel interrupting at irq 15
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 (using DMA data transfers)
uhci0 at pci0 dev 7 function 2: VIA Technologies VT83C572 USB Controller (rev. 0x10)
uhci0: interrupting at irq 5
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: VIA Technologie UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1 at pci0 dev 7 function 3: VIA Technologies VT83C572 USB Controller (rev. 0x10)
uhci1: interrupting at irq 5
usb1 at uhci1: USB revision 1.0
uhub1 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
viapm0 at pci0 dev 7 function 4
auvia0 at pci0 dev 7 function 5: VIA VT82C686A AC'97 Audio (rev H)
auvia0: interrupting at irq 10
auvia0: ICE17 codec; headphone, 18 bit DAC, 18 bit ADC, Unknown 3D
audio0 at auvia0: full duplex, mmap, independent
ahc0 at pci0 dev 8 function 0
ahc0: interrupting at irq 11
ahc0: aic7860 Single Channel A, SCSI Id=7, 3/255 SCBs
scsibus0 at ahc0 channel 0: 8 targets, 8 luns per target
tlp0 at pci0 dev 13 function 0: Macronix MX98715AEC-x Ethernet, pass 2.5
tlp0: interrupting at irq 10
tlp0: Ethernet address 00:80:c6:f9:bc:35
tlp0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX
vga1 at pci0 dev 14 function 0: S3 ViRGE/DX (rev. 0x01)
wsdisplay0 at vga1: console (80x25, vt100 emulation)
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
pmsi0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pmsi0 mux 0
lpt0 at isa0 port 0x378-0x37b irq 7
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
sysbeep0 at pcppi0
isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support
npx0 at isa0 port 0xf0-0xff: using exception 16
isapnp0: no ISA Plug 'n Play devices found
viaenv0 at viapm0
biomask eb65 netmask ef65 ttymask ffe7
scsibus0: waiting 2 seconds for devices to settle...
ahc0: target 3 synchronous at 10.0MHz, offset = 0xf
cd1 at scsibus0 target 3 lun 0: <YAMAHA, CRW6416S, 1.0c> SCSI2 5/cdrom removable
ahc0: target 4 synchronous at 10.0MHz, offset = 0xf
st0 at scsibus0 target 4 lun 0: <Seagate, STT8000N, 3.22> SCSI2 1/sequential removable
st0: drive empty
IPsec: Initialized Security Association Processing.
ulpt0 at uhub0 port 1 configuration 1 interface 0
ulpt0: vendor 0x0832 product 0x5850, rev 1.00/1.04, addr 2, iclass 7/1
boot device: wd0
root on wd0a dumps on wd0b
root file system type: ffs
wsdisplay0: screen 1 added (80x25, vt100 emulation)
wsdisplay0: screen 2 added (80x25, vt100 emulation)
wsdisplay0: screen 3 added (80x25, vt100 emulation)
wsdisplay0: screen 4 added (80x25, vt100 emulation)
wsmux1: connecting to wsdisplay0
uhub0: port error, restarting port 2
uhub0: port error, restarting port 2
ukbd0 at uhub0 port 2 configuration 1 interface 0
ukbd0: Microsoft Natural Keyboard Elite, rev 1.00/1.04, addr 3, iclass 3/1
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
pckbc: cmd failed
pckbc: cmd failed
pckbc: cmd failed
pckbc: cmd failed
pckbc: cmd failed
pckbc: cmd failed
pckbc: cmd failed
pckbc: cmd failed
pckbc: cmd failed

 \___ dmesg

(The ``pckbc: cmd failed'' stuff is because I'm using a USB keyboard.  I
think that what's happening is that the keyboard controller is trying to
turn on an LED on the PS/2 keyboard, but since there is none attached, it
complains.  So, those correspond to occasions when I've hit the CapsLock,
or similar, since booting.  I don't remove the pckbc config option since I
normally have the keyboard attached to the PS/2 connector.  Short of
finding some way to tell if there *is* a PS/2 keyboard attached, I assume
that this is correct behavior and haven't worried about it.)


> What is the Manufacturer of the Motherboard?

I believe that it's a Microstar K7T Pro (MS-6330) motherboard.


> Bios updates:
>
> http://directory.google.com/Top/Computers/Hardware/Components/BIOS/
>
> A Bios update site: http://abios.com/
>
>
> Might just need a Bios flash, this cures a bunch of problems.

I'll need to install a floppy disk drive and dig up some kind of DOS boot
disk to run the flash update tool, yes?  (Is it even possible for such a
tool to exist in NetBSD w/o a kernel hack?)


  ``I probably don't know what I'm talking about.'' --rauch@math.rice.edu