Manuel Bouyer wrote:
> 
> On Tue, Aug 29, 2000 at 05:57:19AM -0700, Bill Hudspeth wrote:
> > Sorry Manuel  :)
> >
> > Here it is.
> >
> > ====================================================================
> > NetBSD 1.4.2 (GENERIC) #3: Wed Mar 15 23:41:54 PST 2000
> >     toddpw@vader.toddpw.net:/usr/src/sys/arch/i386/compile/GENERIC
> > cpu0: family 5 model 8 step c
> > cpu0: AMD K6-2 (586-class)
> > real mem  = 167313408
> > avail mem = 151371776
> > using 2068 buffers containing 8470528 bytes of memory
> > mainbus0 (root)
> > pci0 at mainbus0 bus 0: configuration mode 1
> > pci0: i/o enabled, memory enabled
> > pchb0 at pci0 dev 0 function 0
> > pchb0: VIA Technologies VT82C597 (Apollo VP3) Host-PCI Bridge (rev.
> > 0x04)
> > ppb0 at pci0 dev 1 function 0: VIA Technologies VT82C598 (Apollo MVP3)
> > PCI-AGP (rev. 0x00)
> > pci1 at ppb0 bus 1
> > pci1: i/o enabled, memory enabled
> > pcib0 at pci0 dev 7 function 0
> > pcib0: VIA Technologies VT82C586 (Apollo VP) PCI-ISA Bridge (rev. 0x47)
> > pciide0 at pci0 dev 7 function 1: VIA Technologies VT82C586A IDE
> > Controller
> > pciide0: bus-master DMA support present
> > pciide0: primary channel configured to compatibility mode
> > wd0 at pciide0 channel 0 drive 0: <SAMSUNG WA32162A>
> > wd0: drive supports 16-sector pio transfers, lba addressing
> > wd0: 2060MB, 4186 cyl, 16 head, 63 sec, 512 bytes/sect x 4219488 sectors
> > wd0: 32-bits data port
> > wd0: drive supports PIO mode 4, DMA mode 2
> > pciide0: primary channel interrupting at irq 14
> > pciide0: secondary channel configured to compatibility mode
> > atapibus0 at pciide0 channel 1
> > cd0 at atapibus0 drive 0: <FX162T4, , p01> type 5 cdrom removable
> > cd0: 32-bits data port
> > cd0: drive supports PIO mode 3, DMA mode 2
> > sd0 at atapibus0 drive 1: <IOMEGA  ZIP 100       ATAPI, , 14.A> type 0
> > direct removable
> > sd0: drive offline
> > sd0: 32-bits data port
> > pciide0: secondary channel interrupting at irq 15
> > wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 (using DMA data
> > transfers)
> > cd0(pciide0:1:0): using PIO mode 3, DMA mode 1 (using DMA data
> > transfers)
> > sd0(pciide0:1:1): using PIO mode 3
> > pchb1 at pci0 dev 7 function 3
> > pchb1: VIA Technologies VT82C586 (Apollo VP) Power Management Controller
> > (rev. 0x10)
> > vga1 at pci0 dev 8 function 0: S3 ViRGE/DX (rev. 0x01)
> > wsdisplay0 at vga1: console (80x25, vt100 emulation)
> > rl0 at pci0 dev 9 function 0: RealTek 8139 Ethernet (id 0x8139)
> > rl0: interrupting at irq 10
> > rl0: Ethernet address: 00:48:54:65:76:f6
> > ukphy0 at rl0 phy 7: Generic IEEE 802.3u media interface
> > ukphy0: OUI 0x000000, model 0x0000, rev. 0
> > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> > Fujitsu Limited (4th PCI Vendor ID) product 0x0480 (miscellaneous
> > communications) at pci0 dev 10 function 0 not configured
> 
> Ok, I guess this is your modem. Can you tell me how you got the port
> for serialconfig under linux ? It should be possible to make this work under
> NetBSD but I need more infos :)
> 
> --
> Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
> --

The instructions came straight out of the Actiontec manual, on
setting up a Linux connection. Once I issued the setserial command,
and configured KPPP, I was online. It is definitely a PCI card.

Thanks,

Bill