Mathew Kanner <[EMAIL PROTECTED]> wrote:
> On Nov 25, Don Lewis wrote:
> > On 25 Nov, Don Lewis wrote:
> > > On 25 Nov, Artur Poplawski wrote:
> > >> Artur Poplawski <[EMAIL PROTECTED]> wrote:
> > >>
> > >>> Hello,
> > >>>
On Nov 25, Don Lewis wrote:
> On 25 Nov, Don Lewis wrote:
> > On 25 Nov, Artur Poplawski wrote:
> >> Artur Poplawski <[EMAIL PROTECTED]> wrote:
> >>
> >>> Hello,
> >>>
On 25 Nov, Don Lewis wrote:
> On 25 Nov, Artur Poplawski wrote:
>> Artur Poplawski <[EMAIL PROTECTED]> wrote:
>>
>>> Hello,
>>>
>>> On a 5.1-RE
On 25 Nov, Artur Poplawski wrote:
> Artur Poplawski <[EMAIL PROTECTED]> wrote:
>
>> Hello,
>>
>> On a 5.1-RELEASE and 5.2-BETA machines I have
Artur Poplawski <[EMAIL PROTECTED]> wrote:
> Hello,
>
> On a 5.1-RELEASE and 5.2-BETA machines I have been able to cause a panic
> like this:
Hello Paolo,
See below.
On Oct 20, Paolo Pisati wrote:
> from my dmesg:
> [snip]
> exclusive sleep mutex pcm0:mixer (pcm mixer) r = 0 (0xc2d34540) locked @
> /usr/src/sys/dev/sound/pcm/mixer.c:322
Could you try deleting the snd_mtxlock and snd_mtxunlock in
mixer_hwvol_init() in
On Mon, Oct 20, 2003 at 10:37:00AM -0700, Kris Kennaway wrote:
> Unfortunately none of the sound developers have been interested in
> looking at the locking problems in the code.
=(
> > acquiring duplicate lock of same type: "pcm channel"
> > 1st pcm0:record:0 @ /usr/src/sys/dev/sound/pcm/sound
On Mon, Oct 20, 2003 at 07:15:19PM +0200, Paolo Pisati wrote:
>
> from my dmesg:
> [snip]
> pcm0: port 0xb800-0xb8ff irq 5 at device 1.0 on pci2
> pcm0: failed to enable memory mapping!
> pcm0:
> malloc() of "64" with the following non-sleepable locks held:
> exclusive sleep mutex pcm0:mixer (pc
> Is anything printed on the console (or the first vty)?
>
> > Andre Guibert de Bruet | Enterprise Software Consultant >
> > Silicon Landmark, LLC. | http://siliconlandmark.com/>
Nope. I get complete blackout - I'm unable to switch vtys, move mouse,
start a new process, etc. Just like a crash
On Thu, 7 Aug 2003 [EMAIL PROTECTED] wrote:
> I have problems with my 5.1-Release and 5.1-STABLE boxes:
> they freeze if I play anything different from audio CDs.
> The cards are ESS 1938, options pcm is in the kernel.
> If I try to run xmms/mpg123/KDE or any other application related
> with art
I'm definitely seeing this, and I assumed it's related to my witness
complain about cmi (though it only started recently -- but, then, this
message has only been added recently, afaik).
I have no sound problems, though. In between crashes for other problems,
that is.
La Temperanza wrote:
I hav
Can it be possible that this would be related to the problem I'm having
with xmms on -release right now? Except that -release don't have WITNESS
stuff enabled?
I guess I should try enabling debugging.
Just a shot in the dark...
A.
Lars Eggert wrote:
Got thsi when opening gnomemeeting2 while
Hi,
> Since rescent -CURRENT is stable enough, I have the chance to find
> out remaining pcm problem. My MP box no more has double fatal fault
> and turns into random sleep. The random sleep happens after pcm having
> its own problem.
>
> uname -av is
> FreeBSD cartier.home 5.0-CURRENT Fr
On Sat, Dec 07, 2002 at 01:00:44AM +0800, Clive Lin wrote:
> Hi,
>
> Since rescent -CURRENT is stable enough, I have the chance to find
> out remaining pcm problem. My MP box no more has double fatal fault
> and turns into random sleep. The random sleep happens after pcm having
> its own probl
x27;[EMAIL PROTECTED]'; [EMAIL PROTECTED]
> Subject: RE: pcm / mic
>
>
> > Hi,
> >
> > i cant record from /dev/dsp with the record device 'mic'. Is
> > there support
> > for the microphone input?
> >
>
> What sound card are you using?
&g
> Hi,
>
> i cant record from /dev/dsp with the record device 'mic'. Is
> there support
> for the microphone input?
>
What sound card are you using?
Scott
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
At 04:30 PM 4/15/2002 +0100, you wrote:
>--- John Angelmo <[EMAIL PROTECTED]> wrote:
> > I wonder how the pcm sound support is in 5.0?
>
>Hmm, I am using the emu10k1 aka Sound Blaster 1024 Live!, which has some
>locking problems, but apart from that I dont think there is any other
>problems AFAIK
Hiten Pandya wrote:
> --- John Angelmo <[EMAIL PROTECTED]> wrote:
>
>>I wonder how the pcm sound support is in 5.0?
>
>
> Hmm, I am using the emu10k1 aka Sound Blaster 1024 Live!, which has some
> locking problems, but apart from that I dont think there is any other
> problems AFAIK. :)
>
>
>
--- John Angelmo <[EMAIL PROTECTED]> wrote:
> I wonder how the pcm sound support is in 5.0?
Hmm, I am using the emu10k1 aka Sound Blaster 1024 Live!, which has some
locking problems, but apart from that I dont think there is any other
problems AFAIK. :)
> I didn't get it working in 4.5 but perh
In message <006501c0fa71$7fa71a40$0504020a@haveblue> "Cameron Grant" writes:
: while i've not tested either of these chips for a while (lack of slots,
: anyone know of a motherboard with ~20 pci and ~10 isa slots?) i can't think
: of any changes that might cause this except possibly the introducti
It seems Cameron Grant wrote:
> > I'm having problems with both an internal VIA'686 and a PCI base
> > ESS Solo1, both seem to loose interrupts. The interrupts doesn't
> > even show up in a vmstat -i / systat so something is definitly
> > wrong. BTW the exact same HW work just fine with -stable ?
> I'm having problems with both an internal VIA'686 and a PCI base
> ESS Solo1, both seem to loose interrupts. The interrupts doesn't
> even show up in a vmstat -i / systat so something is definitly
> wrong. BTW the exact same HW work just fine with -stable ?
while i've not tested either of these
Hello,
Thank you for advices. Now I obtain same environment as of pre-devfs days.
From: Alex Kapranoff <[EMAIL PROTECTED]>
Date: Fri, 2 Feb 2001 15:29:09 +0300
> Yep. I have these in my /etc/rc.devfs:
> =
> ln -fs /dev/audio1.0 /dev/audio
> ln -fs /dev/dsp1.0 /dev/dsp
> ln -f
> On Fri, Feb 02, 2001 at 04:11:29PM +0900, Yoshihiro Koya wrote:
> > Hello,
> >
> > I did make world a couple days ago. The system was built from cvsup'd
> > source on Jan 30:
> > >--
> > elf make world started on Tue Jan 30 06:2
On 02-Feb-01 Yoshihiro Koya wrote:
> Hello,
>
> I did make world a couple days ago. The system was built from cvsup'd
> source on Jan 30:
>>--
> elf make world started on Tue Jan 30 06:23:38 JST 2001
>>
On Fri, Feb 02, 2001 at 04:11:29PM +0900, Yoshihiro Koya wrote:
> Hello,
>
> I did make world a couple days ago. The system was built from cvsup'd
> source on Jan 30:
> >--
> elf make world started on Tue Jan 30 06:23:38 JST 2001
On 20-Jan-01 Donald J . Maddox wrote:
> This is directly traceable to entropy harvesting by /dev/*random.
> I know it's not an option if you need to use ssh, but not loading
> random.ko will fix the sound problems when moving the mouse or
> typing. It doesn't fix the 'hwptr went backwards' messa
OK, please try this, then; change the HARVEST_RING_SIZE in
sys/dev/random/yarrow.h to a smaller power-of-2 (256 or 128 would
be good), and let me know how that helps-or-not.
Thanks!
M
> If it helps at all, it's marginal. I still get skips.
>
> On Sat, Jan 20, 2001 at 05:36:08PM +0200, Mark Mu
If it helps at all, it's marginal. I still get skips.
On Sat, Jan 20, 2001 at 05:36:08PM +0200, Mark Murray wrote:
> > This is directly traceable to entropy harvesting by /dev/*random.
> > I know it's not an option if you need to use ssh, but not loading
> > random.ko will fix the sound problems
> This is directly traceable to entropy harvesting by /dev/*random.
> I know it's not an option if you need to use ssh, but not loading
> random.ko will fix the sound problems when moving the mouse or
> typing. It doesn't fix the 'hwptr went backwards' messages, though.
Please tell me if
sysctl
This is directly traceable to entropy harvesting by /dev/*random.
I know it's not an option if you need to use ssh, but not loading
random.ko will fix the sound problems when moving the mouse or
typing. It doesn't fix the 'hwptr went backwards' messages, though.
On Fri, Jan 19, 2001 at 11:42:32P
In message <[EMAIL PROTECTED]> Sean Kelly writes:
: I did not have this behavior in -STABLE, but now I do since I upgraded
: to -CURRENT.
-current's interrupt latency is horrible these days, which seems to
manifest itself in problem with the sound driver. I have a -current
laptop and get all kin
Are you really using the latest FREEBSD_5.0_CURRENT ?
I have just
device pcm
in my kernel config (without PNPBIOS) and the SBLive
works fine (many thanks to Cameron for his nice driver).
Make sure that the line
dev/sound/pci/emu10k1.c optional pcm pci
is not commented (in /usr/src/s
Thanks Steve,
That did it, I figured it was something minor I had screwed up.
Aaron
On Mon, 13 Mar 2000, Steve Coltrin wrote:
> >I am using the new pcm driver which works great, however, I managed to
> >remove the ln -s to dsp. I do not know what it was linked and 'sh MAKEDEV
> >snd' links d
>I am using the new pcm driver which works great, however, I managed to
>remove the ln -s to dsp. I do not know what it was linked and 'sh MAKEDEV
>snd' links dsp to dsp. How can I fix this?
>
>pcm0: port 0xef00-0xef3f irq 7 at device 16.0 on pci0
^
sh MAKEDEV snd0 (you would use 'snd1' if
Christopher T. Griffiths stated:
> Hello,
>
> I am trying to get the pcm device to work under current on my Thinkpad
> 600e.
>
> Here is my kernel line:
>
> # Sound card support
> device pcm0at isa? port ? irq 5 drq 1 flags 0x10
>
>
> I also made the device in /dev with:
> ./MAKE
On Wed, Feb 23, 2000 at 03:26:07PM -0800, R Joseph Wright wrote:
> On Wed, 23 Feb 2000, Brooks Davis wrote:
> > On Wed, Feb 23, 2000 at 12:27:49PM -0800, R Joseph Wright wrote:
> > > Beautiful. Thank you :)
> > > What about for isa cards? Which one is used for them now?
> >
> > I gave my only
On Wed, 23 Feb 2000, Brooks Davis wrote:
> On Wed, Feb 23, 2000 at 12:27:49PM -0800, R Joseph Wright wrote:
> > Beautiful. Thank you :)
> > What about for isa cards? Which one is used for them now?
>
> I gave my only ISA sound card to Camran so I can't say for sure, but if
> you hardware the
On Wed, Feb 23, 2000 at 01:23:22PM -0800, Brooks Davis wrote:
> On Wed, Feb 23, 2000 at 12:27:49PM -0800, R Joseph Wright wrote:
> > Beautiful. Thank you :)
> > What about for isa cards? Which one is used for them now?
>
> I gave my only ISA sound card to Camran so I can't say for sure, but if
On Wed, Feb 23, 2000 at 12:27:49PM -0800, R Joseph Wright wrote:
> Beautiful. Thank you :)
> What about for isa cards? Which one is used for them now?
I gave my only ISA sound card to Camran so I can't say for sure, but if
you hardware the probe address the card ends up at that number and I
th
> > The first pcm device is now pcm0 not pcm1 for PCI devices. Did you do a
> > "MAKEDEV snd0" after upgrading. My es1371 is working great streaming
> > mp3s off of my.mp3.com using xmms.
> >
> Beautiful. Thank you :)
> What about for isa cards? Which one is used for them now?
See the output
On Wed, 23 Feb 2000, Brooks Davis wrote:
> On Wed, Feb 23, 2000 at 12:15:39PM -0800, R Joseph Wright wrote:
> > In 4.0, the pcm sound driver works with my es1371 chipset soundcard for
> > playing cds. But I cannot play mp3s. When I use mpg123, I get the error
> > message "can't open /dev/dsp!"
On Wed, Feb 23, 2000 at 12:15:39PM -0800, R Joseph Wright wrote:
> In 4.0, the pcm sound driver works with my es1371 chipset soundcard for
> playing cds. But I cannot play mp3s. When I use mpg123, I get the error
> message "can't open /dev/dsp!"
> This is an improvement over 3.4, however, where
> Just to let someone know, my ViBRA16X is still having the problem with
> static.
i've replicated it, but have no idea of the cause. i'll probably rework the
sb driver when i rip it and the ess driver apart, but that will wait until
i get an ess card.
- cameron
To Unsubscribe: send ma
On Sat, 29 Jan 2000, Nick Hibma wrote:
> > > I too notice these problems of mpg123 skipping during disk activity or X
> > > graphics ops but I have always had these problems, both with -STABLE and
> > > -CURRENT. I notice this with xmms too. So this is nothing new.
> >
> > Isn't this simply a ty
Nick Hibma wrote:
> Pressing Ctrl-Z repeats the same quarter second fragment forever.
I know the pcm driver uses a circular buffer. Maybe a small chunk of
the sound gets stuck in the buffer, and when you press ^Z, the app is
unable to tell the sound driver to break out of the loop. Also,
RealP
> > I too notice these problems of mpg123 skipping during disk activity or X
> > graphics ops but I have always had these problems, both with -STABLE and
> > -CURRENT. I notice this with xmms too. So this is nothing new.
>
> Isn't this simply a typical issue of IDE hardware? I too notice xmms
> s
Nick Hibma writes:
>
> The output of my ESS 1869 stutters whenever there is no new data fed to
> it. For example pressing Ctrl-Z, or heavy disk usage (normally making
> mpg123 jump). The stuttering is repetition of one short fragment of
> about a quarter of a second, indefinitely
>
> An
* Nick Hibma ([EMAIL PROTECTED]) [000125 12:42]:
> The output of my ESS 1869 stutters whenever there is no new data fed to
> it. For example pressing Ctrl-Z, or heavy disk usage (normally making
> mpg123 jump). The stuttering is repetition of one short fragment of
> about a quarter of a second, in
It is rumoured that Devin Butterfield had the courage to say:
> I too notice these problems of mpg123 skipping during disk activity or X
> graphics ops but I have always had these problems, both with -STABLE and
> -CURRENT. I notice this with xmms too. So this is nothing new.
Isn't this simply a
On Tue, 25 Jan 2000, Donn Miller wrote:
> Nick Hibma wrote:
>
> > The output of my ESS 1869 stutters whenever there is no new data fed to
> > it. For example pressing Ctrl-Z, or heavy disk usage (normally making
> > mpg123 jump). The stuttering is repetition of one short fragment of
> > about a
Nick Hibma wrote:
> The output of my ESS 1869 stutters whenever there is no new data fed to
> it. For example pressing Ctrl-Z, or heavy disk usage (normally making
> mpg123 jump). The stuttering is repetition of one short fragment of
> about a quarter of a second, indefinitely
I can confirm thi
> On Dec 24, Mike Smith wrote:
> > > On Dec 24, [EMAIL PROTECTED] wrote:
> > > > On -CURRENT: Fri Dec 24 08:38:50 EST 1999,
> > > > I'm getting the following when I enabled pcm and sbc in the kernel:
> > > >
> > > > unknown0: at port 0x220-0x22f irq 5 drq 1,0 on isa0
> > > > sbc0: at port 0x388
On Dec 24, Mike Smith wrote:
> > On Dec 24, [EMAIL PROTECTED] wrote:
> > > On -CURRENT: Fri Dec 24 08:38:50 EST 1999,
> > > I'm getting the following when I enabled pcm and sbc in the kernel:
> > >
> > > unknown0: at port 0x220-0x22f irq 5 drq 1,0 on isa0
> > > sbc0: at port 0x388-0x38f on isa0
According to [EMAIL PROTECTED]:
> (I couldn't find the device to create in /dev except for /dev/snd0 and
> /dev/snd1, so that is what I made.)
Bad. Just use "sh MAKEDEV snd0". It will create suitable devices (old Voxware,
pcm and newpcm all use the same devices) for any sound card.
--
Ollivier
On 24 Dec, Bryan Liesner wrote:
> On Fri, 24 Dec 1999 [EMAIL PROTECTED] wrote:
>
> <>unknown0: at port 0x220-0x22f irq 5 drq 1,0 on isa0
> <>sbc0: at port 0x388-0x38f on isa0
> <>sbc0: alloc_resource
> <>device_probe_and_attach: sbc0 attach returned 6
> <>unknown1: at port 0x208-0x20f on isa0
> On Dec 24, [EMAIL PROTECTED] wrote:
> > On -CURRENT: Fri Dec 24 08:38:50 EST 1999,
> > I'm getting the following when I enabled pcm and sbc in the kernel:
> >
> > unknown0: at port 0x220-0x22f irq 5 drq 1,0 on isa0
> > sbc0: at port 0x388-0x38f on isa0
> > sbc0: alloc_resource
> > device_prob
Hi,
On Fri, Dec 24, 1999 at 08:52:51AM -0500, [EMAIL PROTECTED] wrote:
> unknown0: at port 0x220-0x22f irq 5 drq 1,0 on isa0
> sbc0: at port 0x388-0x38f on isa0
> sbc0: alloc_resource
> device_probe_and_attach: sbc0 attach returned 6
> unknown1: at port 0x208-0x20f on isa0
> unknown2: at port
On Fri, 24 Dec 1999 [EMAIL PROTECTED] wrote:
<>unknown0: at port 0x220-0x22f irq 5 drq 1,0 on isa0
<>sbc0: at port 0x388-0x38f on isa0
<>sbc0: alloc_resource
<>device_probe_and_attach: sbc0 attach returned 6
<>unknown1: at port 0x208-0x20f on isa0
<>unknown2: at port 0x330-0x331 irq 9 on isa0
On Dec 24, [EMAIL PROTECTED] wrote:
> On -CURRENT: Fri Dec 24 08:38:50 EST 1999,
> I'm getting the following when I enabled pcm and sbc in the kernel:
>
> unknown0: at port 0x220-0x22f irq 5 drq 1,0 on isa0
> sbc0: at port 0x388-0x38f on isa0
> sbc0: alloc_resource
> device_probe_and_attach: sb
[Followup to myself]
With the latest changes to the pcm driver, a downgrade of channel.c to
1.8 doesn't help any more:
I cannot hear anything while playing something (in my case with mpg123).
A verbose output of mpg123 shows me that the application seems to hang
after a few write()'s to the sound
On Tue, 7 Dec 1999, Oliver Fromme wrote:
> --- dev/sound/isa/sb.c.orig Tue Dec 7 02:30:19 1999
> +++ dev/sound/isa/sb.cTue Dec 7 02:30:19 1999
> @@ -1261,6 +1261,10 @@
> u_int32_t logical_id = isa_get_logicalid(dev);
>
> switch(logical_id) {
> + case 0x0100: /* @
(Replying to myself...)
Oliver Fromme wrote in list.freebsd-current:
> I have today upgraded a machine from some 3.1-stable to the
> latest -current snapshot (19991204). Now the ISA PnP soundcard
> doesn't work anymore (it worked fine before, using the pcm
> driver). It is an Avance Logic A
My collegue just made my day :-)
device pcm0 at isa? port 0x220 irq 5 drq 1 flags 0x15
did it.
/Jesper
On Mon, Nov 29, 1999 at 03:22:45PM +0100, Jesper Skriver wrote:
> Hi,
>
> Just managed to get hold of a old Soundblast
According to Marc van Woerkom:
> device pcm0 at pci0
>
> in the kernel configuration file.
Try
device pcm0
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED]
FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999
To Unsubscribe: send mail to [EMA
On Fri, Sep 24, 1999 at 11:52:26PM -0400, Wes Morgan wrote:
> I noticed a little quirk in the pcm driver -- it is reversing the channels
> in my sb16! The first couple times I play a certain mp3 that starts out
> (normally) in the left channel, it plays correctly in the left channel.
> Then sudde
> On Fri, 3 Sep 1999, Kenneth Culver wrote:
> > > What motherboard? What version of BIOS? Is the BIOS version the latest?
> > >
> > Well, I figured it out I think. It is Award BIOS, and it's the latest
> > version. I have 2 VooDoo 2's and at the place I had them, they were
> > causing problems,
> On Fri, 3 Sep 1999, Kenneth Culver wrote:
> > Also, my bios is really freaky. It refuses to assign any irqs except
> > 10 and 11 to installed PCI devices. I can't figure it out. I've
> > completely rearranged everything and it still refuses to work
> > properly.
>
> The BIOS usually lets you ma
On Fri, 3 Sep 1999, Kenneth Culver wrote:
> Also, my bios is really freaky. It refuses to assign any irqs except
> 10 and 11 to installed PCI devices. I can't figure it out. I've
> completely rearranged everything and it still refuses to work
> properly.
The BIOS usually lets you mark IRQs as 're
Oops, forgot my pnpinfo output
Checking for Plug-n-Play devices...
Card assigned CSN #1
Vendor ID CSC4236 (0x3642630e), Serial Number 0x
PnP Version 1.0, Vendor Version 5
Device Description: Crystal Codec
Logical Device ID: CSC 0x630e #0
Device Description: WSS/SB
TAG Start
On 29-May-99 Osokin Sergey wrote:
>
> Hello!
> pcm driver for SB 128 PCI in -current is broken...
># dmesg | more
> .
> es0: irq 5 at device 11.0 on pci0
> pcm0: using I/O space register mapping at 0xe800
>
>
> play, waveplay, wmsound dont' work correct.
> Does someone have any idea?
>
> The same happens with snd0 instead of pcm. It looks like it can't
> register the interrupt handler - is it now supposed to be registered in
> a different way (perhaps via nexus)?
>
I'm seeing the exact same problem, only with the Voxware driver and a PAS16.
I've held off upgrading the soun
On Wed, May 05, 1999 at 08:49:53AM +0200, Erik H. Bakke wrote:
> 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 clos
On 2 May, Vallo Kallaste wrote:
> The sound broke for me between Apr.20 and 21. My onboard Vibra16X
> doesn't work either with pcm or Voxware drivers. Voxware complains
> about second DMA (1/3) and pcm just simply emits silence. Apr.20
> kernel works well.
FreeBSD 4.0-CURRENT #6: Sun Apr 25 20:0
On Sun, 2 May 1999, Vallo Kallaste wrote:
> On Sat, May 01, 1999 at 04:22:25PM +0800, Peter Wemm
> wrote:
>
> > I've run two systems with PCM right since the first newbus commit, and it's
> > worked for me. Admittedly I don't use it all that often, but it's never
> > paniced and I don't recall
On Sat, May 01, 1999 at 04:22:25PM +0800, Peter Wemm
wrote:
> I've run two systems with PCM right since the first newbus commit, and it's
> worked for me. Admittedly I don't use it all that often, but it's never
> paniced and I don't recall getting any more sound problems than usual.
>
> I che
On Sat, 1 May 1999, Doug Rabson wrote:
> On Sat, 1 May 1999, Zach Heilig wrote:
>
> > I found the commit that "broke" sound (beyond that, I don't know how
> > to fix it):
>
> Now this is interesting. You are saying that the previous mega-commit (the
> new-bus one) didn't break sound? That gives
On Sat, 1 May 1999, Zach Heilig wrote:
> I found the commit that "broke" sound (beyond that, I don't know how
> to fix it):
Now this is interesting. You are saying that the previous mega-commit (the
new-bus one) didn't break sound? That gives us a bit more to go on.
--
Doug Rabson
I found the commit that "broke" sound (beyond that, I don't know how
to fix it):
peter 1999/04/21 00:26:31 PDT
Modified files:
sys/alpha/isaisa.c
sys/alpha/pcipcibus.c
sys/cam cam_xpt.c
sys/dev/ata ata-all.c
sys/i386/i386
I'm using a _PnP_ card, and mine comes up as:
pcm1 (CS423x/Yamaha/AD1816 sn 0x) at 0x530-0x537 irq 5 drq
0 flags 0x11 on isa
When I use NAS I get an interesting 'riffing' effect (last 2 second
sample repeated over and over). The only way to shut it up is to kill the
NAS server. Killing
On Sat, May 01, 1999 at 04:22:25PM +0800, Peter Wemm wrote:
> vortexia wrote:
> > Heh, the panic problem might be solved, but Ive just cvsupped with the
> > latest 4.0-CURRENT and the problems with pcm are definatly not over, Im
> > getting very jerky sound, its repeating bits of it over and over..
hrmmm strange, I booted this system with a 3.0-STABLE drive just now and I
have no problems with the sound, so Im not sure what it is, but its
definatly not hardware.
Cheers
Andrew
On Sat, 1 May 1999, Peter Wemm wrote:
> vortexia wrote:
> > Heh, the panic problem might be solved, but Ive just c
> Do you have 'npx0 at isa?' in your config file by any chance?
Whoops! That's the problem; I failed to see that change in GENERIC
despite having scrolled past it more than several times. My face is
red. :)
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-
vortexia wrote:
> Heh, the panic problem might be solved, but Ive just cvsupped with the
> latest 4.0-CURRENT and the problems with pcm are definatly not over, Im
> getting very jerky sound, its repeating bits of it over and over... and I
> get messages like this while trying to play mp3s with mpg1
Heh, the panic problem might be solved, but Ive just cvsupped with the
latest 4.0-CURRENT and the problems with pcm are definatly not over, Im
getting very jerky sound, its repeating bits of it over and over... and I
get messages like this while trying to play mp3s with mpg123:
May 1 10:12:16 main
On Fri, 30 Apr 1999, Jordan K. Hubbard wrote:
> > It must be something that entered the tree late yesterday afternoon or
> > an interaction between devices.
>
> Same here...
>
> FreeBSD 4.0-CURRENT #0: Wed Apr 28 23:21:40 PDT 1999
> j...@zippy.cdrom.com:/usr/src/sys/compile/ZIPPY
> ...
> pcm
> It must be something that entered the tree late yesterday afternoon or
> an interaction between devices.
Same here...
FreeBSD 4.0-CURRENT #0: Wed Apr 28 23:21:40 PDT 1999
j...@zippy.cdrom.com:/usr/src/sys/compile/ZIPPY
...
pcm0 at port 0x220 irq 5 drq 1 flags 0x13 on isa0
pcm0: interrupting
In article <199904301717.kaa03...@troutmask.apl.washington.edu>,
Steve Kargl wrote:
> John Polstra wrote:
> >
> > Well, it's worse than broken. Merely including pcm0 in the kernel
> > config file causes instant panic on boot-up with my machine (new
> > kernel built last night from fresh sources
John Polstra wrote:
> In article ,
> Doug White wrote:
>
> > Yes, we know that audio is broken; it's been broken since April 20th.
>
> Well, it's worse than broken. Merely including pcm0 in the kernel
> config file causes instant panic on boot-up with my machine (new
> kernel built last night
In article ,
Doug White wrote:
> Yes, we know that audio is broken; it's been broken since April 20th.
Well, it's worse than broken. Merely including pcm0 in the kernel
config file causes instant panic on boot-up with my machine (new
kernel built last night from fresh sources):
BIOS basemem
I have a question.I am subscribed to -current, but am wondering how
much of -current applies to the Alpha port? I am also subscribed to
freebsd-alpha too.FYI, I am running -current of a few days ago and it
is running great on my alpha.
William
To Unsubscribe: send mail to majord...@freeb
On Wed, 28 Apr 1999, vortexia wrote:
> I cvsupped from 3.1-RELEASE today to 4.0-CURRENT and since then PCM sound
> has been screwed. Im using a crystal sound card, anyone having similar
> problems?
Someone's not reading -current, obviously.
Yes, we know that audio is broken; it's been broken si
Ken,
I can't offer you any help, just moral support :P - mine just broke too.
Same message.
Andrew.
On Thu, 22 Apr 1999, Kenneth Wayne Culver wrote:
> Date: Thu, 22 Apr 1999 22:50:46 -0400 (EDT)
> From: Kenneth Wayne Culver
> To: freebsd-current@freebsd.org
> Subjec
For some reason, when I rebuilt the kernel after a cvsup this morning,
sound will no longer work. It gives this kernel warning when I try to play
sound:
timeout flushing dbuf_out, chan 1 cnt 0xff00 flags 0x00c1
sound worked fine yesterday, before I cvsupped.
Can anyone give me an idea as t
Russell Cattelan wrote:
> I haven't been able to track down exactly where this
> is occuring, but disabling pcm allows eliminates the crash.
>
> The build is current as of Sun 18th.
>
> The one strange thing about this box, it has
> two sounds cards. A build in Yamaha OPL-3 (really really crappy)
95 matches
Mail list logo
