Re: Soundblaster 64 PCI
This is the same problem I am having with a Soundblaster 16 PCI on
4.2-STABLE. I found a work around for it. It appears that there is
something that is being un-initialized by the FreeBSD es1371 driver that
other OS's do set. I have built a linux boot floppy, boot it, modprobe
the linux es1371 driver, and than reboot into FreeBSD and the problem is
gone. And until I power off the machine, the card works fine.
I have brought this up several times on the freebsd-multimedia list, but
have gone un-noticed each time.
Anyway, I have found a lame work around, until it is fixed properly.
Greg
* The Hermit Hacker ([EMAIL PROTECTED]) [010114 21:33]:
yup, just confirmed ... it does it with splay as well ...
On Sun, 14 Jan 2001, The Hermit Hacker wrote:
On Sun, 14 Jan 2001, Cameron Grant wrote:
If this is a known problem, I'll stop for now and watch out for fixes.
If it's not the expected behaviour from the PCM driver though, can
anyone advise?
Okay, just checked and it appears tha htis is the same error that I'm
seeing on mine, as reported yesterday ... not sure if its known or not,
but its not "just you" ...
are either of you using esound or xmms? if so, i know the cause of this and
it will be fixed shortly, once my primary development box recovers from
killing its cpu.
if not, i'll try to reproduce this.
for me, I tried using splay ... but, not sure how old my compile was, so
am just installing a new copy and will report back ...
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
Greg Rumple
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Soundblaster 64 PCI
I probably have the same card as you, I just went out and bought a soundblaster 16PCI because my new motherboard doesn't have any ISA slots. Unfortunately, the card is detected and does play sound, but it is soo distorted you can't really recognize anything. I was just wondering if you hard this distortion problem as well, I haven't seen anything on the lists about it until now. Thanks, Andrew On Mon, 15 Jan 2001, Greg Rumple wrote: This is the same problem I am having with a Soundblaster 16 PCI on 4.2-STABLE. I found a work around for it. It appears that there is something that is being un-initialized by the FreeBSD es1371 driver that other OS's do set. I have built a linux boot floppy, boot it, modprobe the linux es1371 driver, and than reboot into FreeBSD and the problem is gone. And until I power off the machine, the card works fine. I have brought this up several times on the freebsd-multimedia list, but have gone un-noticed each time. Anyway, I have found a lame work around, until it is fixed properly. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Soundblaster 64 PCI
i have the same problem with sounbblaster 16 pci. wondering if there will be a fix any time soon? On Mon, 15 Jan 2001, Greg Rumple wrote: This is the same problem I am having with a Soundblaster 16 PCI on 4.2-STABLE. I found a work around for it. It appears that there is something that is being un-initialized by the FreeBSD es1371 driver that other OS's do set. I have built a linux boot floppy, boot it, modprobe the linux es1371 driver, and than reboot into FreeBSD and the problem is gone. And until I power off the machine, the card works fine. I have brought this up several times on the freebsd-multimedia list, but have gone un-noticed each time. Anyway, I have found a lame work around, until it is fixed properly. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Soundblaster 64 PCI
On Sun, 14 Jan 2001, Michael Wells wrote: Hi all, I just got round to popping the lid on my machine and installing a Soundblaster 64 PCI card. I already had pcm in my kernel. It's working, but there are some Strange Things Happening. Firstly, here's /dev/sndstat: FreeBSD Audio Driver (newpcm) Jan 5 2001 12:50:04 Installed devices: pcm0: AudioPCI ES1371 at io 0xec00 irq 16 (1p/1r channels duplex) (Aside: is that really the chipset on the Soundblaster 64?). I get kernel warnings since I installed the card: Jan 14 13:00:15 sunrise /boot/kernel/kernel: pcm0: hwptr went backwards 2112 - 1888 I'm using FreeBSD Current, built on 5 January 2001. What I've got is some very strange sounds when I run mpg123 on a standard MP3 file. It's going through /dev/dsp and appears to play the samples at a very slow speed, with weird echoes. It's like a special effect. Using the -a flag with mpg123 allows me to play through /dev/audio, which sounds right except that it's distorted. At all volume levels, the audio sounds overdriven, and I know this is not due to impedance mismatches or faults elsewhere having used the card in Linux with the same cabling arrangements, amplifier etc. If this is a known problem, I'll stop for now and watch out for fixes. If it's not the expected behaviour from the PCM driver though, can anyone advise? Okay, just checked and it appears tha htis is the same error that I'm seeing on mine, as reported yesterday ... not sure if its known or not, but its not "just you" ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Soundblaster 64 PCI
If this is a known problem, I'll stop for now and watch out for fixes. If it's not the expected behaviour from the PCM driver though, can anyone advise? Okay, just checked and it appears tha htis is the same error that I'm seeing on mine, as reported yesterday ... not sure if its known or not, but its not "just you" ... are either of you using esound or xmms? if so, i know the cause of this and it will be fixed shortly, once my primary development box recovers from killing its cpu. if not, i'll try to reproduce this. -cg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Soundblaster 64 PCI
yup, just confirmed ... it does it with splay as well ...
On Sun, 14 Jan 2001, The Hermit Hacker wrote:
On Sun, 14 Jan 2001, Cameron Grant wrote:
If this is a known problem, I'll stop for now and watch out for fixes.
If it's not the expected behaviour from the PCM driver though, can
anyone advise?
Okay, just checked and it appears tha htis is the same error that I'm
seeing on mine, as reported yesterday ... not sure if its known or not,
but its not "just you" ...
are either of you using esound or xmms? if so, i know the cause of this and
it will be fixed shortly, once my primary development box recovers from
killing its cpu.
if not, i'll try to reproduce this.
for me, I tried using splay ... but, not sure how old my compile was, so
am just installing a new copy and will report back ...
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Soundblaster 64 PCI
Hi Cameron, all, I'm not really tied to any single application. Streaming an .au file from the command line into /dev/dsp does it, mpg123, XMMS...really, the same symptoms everywhere. Any ideas? Michael On Sun, Jan 14, 2001 at 09:08:47PM -, Cameron Grant ([EMAIL PROTECTED]) wrote: If this is a known problem, I'll stop for now and watch out for fixes. If it's not the expected behaviour from the PCM driver though, can anyone advise? Okay, just checked and it appears tha htis is the same error that I'm seeing on mine, as reported yesterday ... not sure if its known or not, but its not "just you" ... are either of you using esound or xmms? if so, i know the cause of this and it will be fixed shortly, once my primary development box recovers from killing its cpu. if not, i'll try to reproduce this. -cg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- www.wells.org.uk +44 7715 747252 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
