From owner-freebsd-questions Sat May 13 17:19: 0 2000 Delivered-To: freebsd-questions@freebsd.org Received: from spike.brainlink.com (spike.brainlink.com [206.127.59.100]) by hub.freebsd.org (Postfix) with ESMTP id 66DEC37B9F4 for ; Sat, 13 May 2000 17:18:52 -0700 (PDT) (envelope-from spork@spike.brainlink.com) Received: (from spork@localhost) by spike.brainlink.com (8.9.3/8.9.3) id UAA16056 for freebsd-questions@freebsd.org; Sat, 13 May 2000 20:17:56 -0400 (EDT) (envelope-from spork) Date: Sat, 13 May 2000 20:17:56 -0400 From: Spike Gronim To: freebsd-questions@freebsd.org Subject: Soundblaster AWE64 under 4.0-STABLE Message-ID: <20000513201756.A15910@spike.brainlink.com> Reply-To: gronimw@stuy.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-PGP-Public-Key: http://www.gronim.com/spike/pubkey.asc X-PGP-fingerprint: 05 92 88 05 3C DB F2 40 AB 1D AE 2A F0 E5 FA A5 X-Geek-Code: http://www.gronim.com/spike/geekcode Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey. I've got a Soundblaster AWE64 PNP. I was using the Voxware drivers under 3.4-STABLE, and it worked perfectly. Using essentially the same drivers in essentially the same configuration on the same computer the sound card has stopped working. Nothing can open /dev/dsp, and 'cat /dev/sndstat' reports 'Device not configured'. I have used MAKEDEV to create the appropriate devices. Dmesg snippet: sb_reset_dsp failed sb_reset_dsp failed awe0 at port 0x620 on isa0 AWE32: not detected awe0: driver is using old-style compatability shims 'uname -a': FreeBSD spike.brainlink.com 4.0-STABLE FreeBSD 4.0-STABLE #0: Sun May 7 18:50:58 EDT 2000 root@spike.brainlink.com:/usr/obj/usr/src/sys/ZALEM4 i386 The relevant parts of the kernel configuration: device snd device sb0 at isa? port 0x220 irq 5 drq 1 device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device awe0 at isa? port 0x620 device opl0 at isa? port 0x388 I've tried: 1. The above with and without 'options PNPBIOS'. 2. Enabling only 'device pcm', with and without explicit irq/drq/port settings. 3. Enabling 'device pcm' and 'device sbc0' I'm stumped. Can anyone tell me what's causing the 'sb_reset_dsp failed' messages and which drivers I should be using? Is Voxware deprecated in favor of pcm? Have other people had similar problems with these cards? I have attached my full kernel config file, and I'm not subscribed to -questions so please cc: directly to me. Thank you. -- --Spike Gronim gronimw@stuy.edu "Oh yes? An obscene triangle which, has more courage than the word." #ZALEM4 config file. machine i386 cpu I686_CPU ident ZALEM maxusers 256 options SOFTUPDATES options IPFIREWALL options IPFIREWALL_VERBOSE options PNPBIOS options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies device isa device eisa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device ahc # AHA2940 and onboard AIC7xxx devices # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device cd # CD device pass # Passthrough device (direct SCSI access) #IDE. device ata0 at isa? port IO_WD1 irq 14 device ata device atadisk # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? # syscons is the default console driver, resembling an SCO console device sc0 at isa? # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer device ppi # Parallel port interface device device miibus # MII bus support device dc # DEC/Intel 21143 and various workalikes #Sound # device snd device sb0 at isa? port 0x220 irq 5 drq 1 device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device awe0 at isa? port 0x620 device opl0 at isa? port 0x388 #device pcm0 at isa? irq 10 drq 1 flags 0x0 #device pcm #device sbc0 at isa? port 0x220 irq 5 drq 1 flags 0x15 # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device md # Memory "disks" pseudo-device gif 4 # IPv6 and IPv4 tunneling pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message