From owner-freebsd-current Tue May 4 23:48:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.bgnett.no (post.bgnett.no [194.54.96.133]) by hub.freebsd.org (Postfix) with ESMTP id 2BD9F14FD0 for ; Tue, 4 May 1999 23:48:15 -0700 (PDT) (envelope-from erik@habatech.no) Received: from intranett (post.lyssand.com [194.54.98.163]) by post.bgnett.no (8.8.8/8.8.8) with SMTP id IAA03189 for ; Wed, 5 May 1999 08:48:09 +0200 (CEST) (envelope-from erik@habatech.no) Message-ID: <009b01be96c3$90063e70$589a4cc0@intranett.lyssand.com> From: "Erik H. Bakke" To: Subject: PCM problem solved (?) Date: Wed, 5 May 1999 08:49:53 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In what may have seemed a desperate move to try to find out where the sound drivers decided to stop, I took a look at my config file. I tried to change the attachment of the pcm device from isa? to nexus?, trying to move it closer to the source of the interrupts. (This is with = an SB PCI 128) When I had rebuilt the kernel and rebooted, the error messages seemed a bit different. It was actually suggested that I should try to use pcm0 instead of pcm1. A quick remake of the devices, and suddenly, the sound was back. Will this approach solve the problems for you other people with the same problem? Regards. -- Erik H. Bakke Habatech AS erik@habatech.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message