From owner-freebsd-questions Fri Feb 12 03:08:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA22479 for freebsd-questions-outgoing; Fri, 12 Feb 1999 03:08:42 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from isis.dynip.com ([139.141.220.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA22462 for ; Fri, 12 Feb 1999 03:08:19 -0800 (PST) (envelope-from root@isis.dynip.com) From: root@isis.dynip.com Received: (from root@localhost) by isis.dynip.com (8.9.2/8.9.1) id OAA29634 for freebsd-questions@freebsd.org; Fri, 12 Feb 1999 14:07:47 +0300 (AST) (envelope-from root) Message-Id: <199902121107.OAA29634@isis.dynip.com> Date: Fri, 12 Feb 1999 14:07:46 +0300 (AST) Reply-To: root@isis.dynip.com Subject: Re: (no subject) To: freebsd-questions@FreeBSD.ORG MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11 Feb, To: medeiros_ed_m@code21.npt.nuwc.navy.mil wrote: > On 11 Feb, Medeiros_Ed_M wrote: >> Sirs, >> >> I am trying to install,(under FreeBSD unix,) a Creative Labs Sound Blaster "Live" board, Model sb4670. This board is a PCI board. Is there a driver available for this card? If so can you direct me to where I can get one? >> Or can you tell me how to install the board with what is supplied in the stable Free BSD? Thank you. >> >> Ed Medeiros >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-questions" in the body of the message > Welcome .mil user > very sexy URL you have. > now to your question, here's a start point: > > 1. Read Handbook Entry of how to : > a-configure custom kernel > b-configure a sound blaster > 2. do the thing: > > cd /usr/src/sys/i386/conf > there's a LINT file, read it carefully > copy whatever lines to your MYKERNEL or whatever you call it. > recompile the kernel > reboot > see what happens, tell me. > > Here's my own MYKERNEL > > machine "i386" > cpu "I586_CPU" > ident MYKERNEL > maxusers 100 > config kernel root on wd0s1a > > #----------------------- CONTROLLER --------------------------------- > controller snd0 > controller isa0 > controller eisa0 > controller pci0 > controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr > controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr > controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr > controller ncr0 > controller ahb0 > controller ahc0 > controller scbus0 > controller pnp0 > #New Syscon Stuff > controller atkbdc0 at isa? port IO_KBD tty > device atkbd0 at isa? tty irq 1 > device vga0 at isa? port ? conflicts > device sc0 at isa? tty > #----------------------- OPTIONS --------------------------------- > # Allow user-mode programs to manipulate their local descriptor tables. > # This option is required for the WINE Windows(tm) emulator, and is > # not used by anything else (that we know of). > # > options USER_LDT #allow user-level control of i386 ldt > > options MATH_EMULATE #Support for x87 emulation > options INET #InterNETworking > options FFS #Berkeley Fast Filesystem > options NFS #Network Filesystem > options MSDOSFS #MSDOS Filesystem > options "CD9660" #ISO 9660 Filesystem > options PROCFS #Process filesystem > options MFS # Memory-Mapped File System 'RAM Disk' > options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] > options SCSI_DELAY=1500 #Be pessimistic about Joe SCSI device > options BOUNCE_BUFFERS #include support for DMA bounce buffers > options UCONSOLE #Allow users to grab the console > options FAILSAFE #Be conservative > options USERCONFIG #boot -c editor > options VISUAL_USERCONFIG #visual boot -c editor > options SYSVSHM > options SYSVSEM > options SYSVMSG > options "MD5" > options DDB > options DDB_UNATTENDED > options PERFMON > options NETATALK > options MROUTING > options TCPDEBUG > options COMPAT_LINUX > options XSERVER > options FAT_CURSOR > options KTRACE > options ATAPI > options ATAPI_STATIC > options IPFIREWALL > options IPFIREWALL_VERBOSE > options "IPFIREWALL_VERBOSE_LIMIT=100" > options IPFIREWALL_DEFAULT_TO_ACCEPT > options IPDIVERT > options QUOTA > #----------------------- DEVICE :SOUND BLASTER STUFF ------------------- > device sb0 at isa? port 0x220 irq 5 conflicts drq 1 vector sbintr > device sbxvi0 at isa? drq 5 > device sbmidi0 at isa? port 0x330 > device opl0 at isa? port 0x388 conflicts > device pca0 at isa? port IO_TIMER1 tty > # > # gsc0 The Scanner Driver (Wrong Driver / Address) - just put it to remind us > # that we don't have it working yet. > #device gsc0 at isa? port 0x300 tty drq 3 > device joy0 at isa? port "IO_GAME" > device sd0 > device od0 > device st0 > device cd0 > device acd0 > device npx0 at isa? port "IO_NPX" flags 0x1 irq 13 vector npxintr > device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr > device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr > #device sio2 at isa? port "IO_COM3" tty irq 11 vector siointr # com3 is now PnP > device lpt0 at isa? port? tty irq 7 vector lptintr > device de0 > device fxp0 > device vx0 > > #----------------------- DISK --------------------------------- > disk fd0 at fdc0 drive 0 > disk fd1 at fdc0 drive 1 > disk wd0 at wdc0 drive 0 > disk wd1 at wdc0 drive 1 > > #----------------------- PSEUDO-DEVICE --------------------------------- > #pseudo-device log > pseudo-device loop > pseudo-device ether > pseudo-device sl 1 > pseudo-device ppp 1 > pseudo-device vn 1 > pseudo-device tun 1 > pseudo-device pty 16 > pseudo-device gzip > pseudo-device fddi > pseudo-device sppp > pseudo-device bpfilter 4 > pseudo-device disc > pseudo-device speaker > pseudo-device snp 3 > pseudo-device ccd 4 > options PPP_BSDCOMP #PPP BSD-compress support > options PPP_DEFLATE #PPP zlib/deflate/gzip support > options PPP_FILTER #enable bpf filtering (needs bpfilter) > #New Syscon Stuff > pseudo-device splash > ############################ END ########################################### > > > > by the way what's the current decyphering mechanism in the NAVY <;-$) > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message