Date: Tue, 17 May 2005 10:54:51 -0700 From: Matt Crossley <moose@freebsdfreaks.net> To: Fafa Hafiz Krantz <fteg@london.com> Cc: questions@freebsd.org Subject: Re: Creative Sound Blaster Audigy LS Message-ID: <428A2FEB.2070301@freebsdfreaks.net> In-Reply-To: <20050517141549.AE7F74BEAD@ws1-1.us4.outblaze.com> References: <20050517141549.AE7F74BEAD@ws1-1.us4.outblaze.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Fafa Hafiz Krantz wrote: >That didn't really work :( >Any other suggestions? > >Thanks. > >-- > I'm using mine just fine... I didn't include mine in the kernel yet, I just tested with a kldload, in 5.4: kldload snd_emu10k1 from /var/log/messages: May 16 18:31:34 bsdmoose kernel: pcm0: <Creative Audigy (EMU10K2)> port 0xa000-0xa01f irq 18 at device 13.0 on pci0 May 16 18:31:34 bsdmoose kernel: pcm0: <SigmaTel STAC9721/23 AC97 Codec> bsdmoose# kldstat Id Refs Address Size Name 1 9 0xc0400000 5dde24 kernel 2 14 0xc09de000 56270 acpi.ko 3 1 0xc1e67000 17000 linux.ko 4 1 0xc298a000 6000 snd_emu10k1.ko 5 1 0xc2990000 18000 sound.ko Works like a charm. It used to be that I needed to compile the emu10kx drivers. Maybe if you included some more information, it would prove to be more useful. What is your dmesg saying when you boot up now? What did it say before? What happens with a kldload snd_emu10k1, followed by a kldstat (if it gave no error)? HTH, Matt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?428A2FEB.2070301>