It's also handy if you don't have external speakers hooked up to a
machine, and want something better than beeps.
Would it be a useful exercise for the minority(?) of users who use this
driver to either see if it can be effectively newbussed or turned into
a port or both?
i'd quite like to see it r
Having a port of ALSA would sure round out 5.2 nicely, and would get you
MIDI support: http://www.alsa-project.org/
I think you wouldn't really do anyone a favour, including the ALSA
folks, if you went and made a port right now. The ALSA project is still
not at 1.00 status and still quite in-flux
_mtx_lock_flags() at _mtx_lock_flags+0x43
mixer_reinit() at
ds_ps_resume()
bus_generic_resume()
bus_generic_resume()
bus_generic_resume()
bus_generic_resume()
bus_generic_resume()
apm_resume()
apm_processevent()
apm_do_suspend()
apm_timeout()
softclock()
ithread_loop()
fork_exit()
fork_trampoline()
--On 01 December 2002 10:26 +0100 Marc Recht
<[EMAIL PROTECTED]> wrote:
Hi!
I'm seeing this lately:
acquiring duplicate lock of same type: "pcm channel"
1st pcm0:record:0 @ /usr/src/sys/dev/sound/pcm/sound.c:191
2nd pcm0:play:0 @ /usr/src/sys/dev/sound/pcm/sound.c:191
please test the patc
I have no idea why, but this commit broke kernel building:
cc -c -O -pipe -mcpu=athlon -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I.
-I/usr/src/sys -I/usr/src/sys/dev -I/usr/src
> on -CURRENT though /dev/dsp seems to be conjured up by the devfs system
> and i have simply been unable to find a way to make it point my prefered
> device node ... in my case /dev/dsp1.
>
> Am i missing something obvious here ... or is it simply not possible on
> -CURRENT to do something simil
> and the sound cracks/stops playing for the fraction of a second. seems
> like it happens more often during disk or network activity ( i mount
> /usr/ports via nfs, and when i build a port it happens all the time). the
> soundcard is a sblive. i searched the archive for this problem, but didnt
>
> > from what i can see, identcpu.c fetches the cpu name using a cpuid
> > instruction.
>
> The part cpuid gives you is "AuthenticAMD".
> The fancy name is determined by switching on the Id.
read identcpu.c. you are correct for k6 and lesser processors. the code in
question is around line 323:
> What about new Durons based on the Palomino core? The problem is
> that as far as I know they have nothing in their name (like XP in
> Athlon's case) that distinguishes them from older Durons based on
> the Thunderbird core, while they do support SSE in addition to
> 3DNow and MMX. Perhaps it wo
> > The sound driver interface provides the application writer the choice to
set
> > the buffering they require. This patch has obvious implications for the
> > ordering of ioctl's that we may not want to introduce.
>
> Yes, OSS interface allows for that, but currently FreeBSD doesn't fully
> pro
> pcm0: unable to map register space
> pci1: at device 0.1 (no driver attached)
my guess is that this is an intel 443mx chipset. that message, "unable to
map register space" is not generated by the ich/443mx driver, so i doubt
it's actually a sound issue. in other words, prod mike until he fix
> I suppose it "uses" it, but why does it lock it for extended periods of
> time. KDE can't even use the sound driver while this is happening.
set sysctl hw.snd.verbose as high as it'll go (3, with the latest code) and
cat /dev/sndstat. it'll tell you the pid of the process using each channel.
> Same here, but with an SB64 PCI (chipset ES1370). So it's not limited
> to SB16 cards.
fixed in sys/dev/sound/pcm/sound.c rev 1.56, just committed.
-cg
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> 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
> Oh, sorry - yes, I can... I watched the pcm interrupt (irq 9 on my box)
> increment using vmstat -i. I had seen something in the archives about
that
> not happening.
is there any other device using irq 9?
-cg
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-cu
> Apr 19 15:09:31 zorba /boot/kernel/kernel: pcm0: play interrupt timeout,
channel dead
> Apr 19 15:19:00 zorba /boot/kernel/kernel: pcm0: play interrupt timeout,
channel dead
can anyone suffering from this problem confirm that the hardware is
generating interrupts?
use 'systat -vm 1' to watch w
> Stopped at _mtx_lock_sleep+0x2e2: movb 0x1d5(%edx),%al
> _mtx_lock_sleep
> snd_mtxlock
> ad1816_lock
fix just committed, sys/dev/sound/isa/ad1816.c rev 1.18.
you must be the only freebsd user on the planet with an ad1816. :)
-cg
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "un
> just upgraded my tree and did a reinstall ... trace is:
>
> resource_list_alloc(c0d9eec0,c0d90180,c0d99b80,4,c0d4a30c) at
resource_list_alloc+0xd3
> isa_alloc_resource() @ +0xd0
> bus_alloc_resource() @ +0x5f
> opti_detect @ +0x99
> mss_detect @ +0x52
> mss_probe @ +0x30a
> device_probe_child @
> says: pcm1: at port
> 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on
> isa0
you have a bogus device pcm0. you probably have a mistake in your hints
file.
-cg
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> Mixer stuff was modified couple days ago. Does anyone have working
> ich driver? I got original driver from
more than that, a couple of weeks would be closer.
> http://www.katsurajima.seya.yokohama.jp/ich/index.en.html but now this
> site is dead. Does author (Katsurajima Naoto) of this dri
> > 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
> I have a SB32 isa-card.
what revision of sys/dev/sound/isa/sb16.c ?
-cg
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> in the near future, i intend to commit my kobjified newpcm. this gives us
> several benefits, including:
>
> * easier extensibility- new optional methods can be added to
> ac97/mixer/channel classes without having to fixup every driver.
>
> * forward compatibility for drivers, provided no new m
in the near future, i intend to commit my kobjified newpcm. this gives us
several benefits, including:
* easier extensibility- new optional methods can be added to
ac97/mixer/channel classes without having to fixup every driver.
* forward compatibility for drivers, provided no new mandatory met
> the sound card is a Crystal Semiconductor CS 4624 controller with CS 4297A
> AC97 codec, pcic0 is a TI PCI-1450 PCI-CardBus Bridge.
>
> sound output results in "pcm0: play interrupt timeout, channel dead".
try turning off apm and all power saving in the bios setup.
-cg
To Unsubscri
> Now the volume states are often wedged when the machine boots up, eg only
> one channel is used of the two, or the volume level is
> drastically different
> on the two channels. The best part is, mixer(8) does not show any of this,
> and setting it to different values does not seem to influence
> SB128 sound support has been broken over a week now. I don't who has
> made changes on 26th Oct but after these changes I can't get any sound
> out of my machine. Sources cvsupped 25th Oct still worked fine.
should be fixed now. (sys/dev/sound/pci/es137x.c rev 1.25)
-cg
To Unsubs
> First of all (using -current of 26 October) I was not able to attach pcm
to
> my Yamaha OPL-SAx soundcard in my Toshiba Tecra8000 when using snd_pcm.ko.
> Using a statically compiled driver though I had no trouble whatsoever. The
> module was pre-loaded at boot time.
snd_pcm is the core module,
> > In -CURRENT cvsupped as of today, the mixer no longer works. anything
that
> > tries to access the mixer just says "Operation not permitted"
>
> using devfs?
i just committed a fix; devfs was not the problem.
-cg
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebs
> In -CURRENT cvsupped as of today, the mixer no longer works. anything that
> tries to access the mixer just says "Operation not permitted"
using devfs?
-cg
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> According to Cameron Grant:
> > this is a known problem. it seems the neomagic driver never worked
right,
> Well, it used to work :)
it used to *appear* to work.
> > so when newpcm became dependant on interrupts it ceased functioning.
now we
> > trap the lack of irqs
> The first time I run mpg123, it does nothing (that is, no sound is
emitted)
> and afterwards, /dev/dsp can't be opened at all...
> Any idea ?
this is a known problem. it seems the neomagic driver never worked right,
so when newpcm became dependant on interrupts it ceased functioning. now we
t
> # For PnP/PCI sound cards
> #device pcm
> #device sbc
> #device csa
>
> # For non-PnP cards:
> device pcm0 at isa? irq 10 drq 1 flags 0x0
> device sbc0 at isa? port 0x220 irq 5 drq 1 flags 0x15
> device csa
> device gusc0 at isa? port 0x220 irq 5 drq 1 flags 0x13
this is wrong.
try:
options P
> 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
would everyone who currently has an issue outstanding with newpcm please
report it to me in the next few days directly, please, so i can get an idea
of what needs work before release. i need as much detail as possible.
- cameron
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubs
i have just committed a driver for the neomagic chips. please test and post
results.
- cameron
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> bus_dmamap_load: Too many segs! buf_len = 0xdf00
> bus_dmamap_load: Too many segs! buf_len = 0xdf00
argh, forgot something. try mss.c rev 1.44, sb.c rev 1.48.
- cameron
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
the panics should be fixed now with sb.c rev 1.47, mss.c rev 1.43.
- cameron
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> Donn> "ba ba ba ba ba ba ba ba ba ba ba ba ba ba". I have the ESS
> Donn> 1868, of course. Well, I (wisely) saved my old kernel as
> Donn> /kernel.good and just booted into that.
>
> Donn> Could you also say what was fixed if you get around to it? I'd
> Donn> to learn a little more about the
> I've got a ESS1879 as well. Try the following patch, Cameron sent me.
i commited an equivalent fix this morning.
- cameron
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> On Sat, 18 Dec 1999, Donn Miller wrote:
>
> > I just rebuilt my kernel from a recent cvsup. Of course, I have
> >
> > device pcm0
> > device sbc0
> >
> > in my kernel config file. When I try to play a realaudio clip
> > with Linux rvplayer (RealPlayer 5.0), rvplayer downloads
Doug Rabson wrote:
> > Unfortunately I can't get it working on my SB16PNP with previously
worked
> > flamessly with "oldpcm". I've did as you suggested - as it seems to be
pnp card
> > I've removed all "at isa0 ", rebuilded and rebooted. But with the
new
> > kernel I've observed 2 things: (1)
apologies for this message being late.
newpcm has now been committed in -current, with functional trident 4dwave,
es1370, sb and mss support. minimal changes to kernel config should be
required:
pci devices:
device pcm0
isa pnp devices:
controller pnp0
device pcm0
non-pnp isa devices:
device
to let newpcm out of the cage so you can all get your grubby little hands on
it.
http://www.vilnya.demon.co.uk/newpcm+dfrpnp-19990807.diff.gz
this is a patch against a recent -current. if you have a pci or isapnp
soundcard, you should have pnp0 and pcm0 in your kernel config as
appropriate. is
44 matches
Mail list logo
