Re: [Fwd: panic: don't do that ?]
Olivier Houchard wrote: Ooops sorry. They have to be applied in /sys/dev/sound/pcm. My bad, next time I'll make them against /usr/src :) Thanks! That did the trick. Where I have to keep an eye is to the "device busy" problem, since it doesn't appear immediately. CU, David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Fwd: panic: don't do that ?]
Olivier Houchard wrote: I'm afraid I don't know anything about that. The oid doesn't exist for me if I don't load the kernel module. That's my fault for being imprecise. I forgot to mention that I had snd_pcm.ko loaded, but nothing else. I believe it has been fixed on -CURRENT. You may try this patch : http://people.FreeBSD.org/~cognet/sound.c.diff Thanks for the patch, I'll try it. AFAIK, The device being busy issue is fixed by Brian Feldman's recent commit. You can find the patch here : http://people.FreeBSD.org/~cognet/dsp.c.diff Thanks for this one also, will test both. CU, David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Fwd: panic: don't do that ?]
On Wed, Feb 12, 2003 at 12:23:53AM +0100, David Vidal Rodr?guez wrote:
Hi,
> 1)
> If they aren't loaded (I forgot them on the 1st try by mistake), the
> kernel panics if I try to change hw.snd.maxautovchans (that odd "bwrite:
> buffer is not busy???" message again!). That shouldn't happen: if I
> don't have any soundcards, this oid shouldn't _exist_ either!
I'm afraid I don't know anything about that. The oid doesn't exist for
me if I don't load the kernel module.
> 2)
> If they're loaded, an attempt to unload snd_via82c686.ko results in a
> panic with the funny message in the subject. But: Aren't modules
> supposed to be unloadable? What's the fun with modules then?
I believe it has been fixed on -CURRENT. You may try this patch :
http://people.FreeBSD.org/~cognet/sound.c.diff
> Any hints on solving this?
>
> My attempt to load modules instead of the monolithic solution (which
> always works) comes due to an odd behaviour of pcm0 (multiplexed with
> hw.snd.pcm0.vchans=8) telling that some /dev/dsp{W,}0.[0-7] devices are
> busy after their first usage. I wanted to address it by unloading the
> affected module and loading it again, but... that'll panic the system.
AFAIK, The device being busy issue is fixed by Brian Feldman's recent commit.
You can find the patch here :
http://people.FreeBSD.org/~cognet/dsp.c.diff
Cheers,
Olivier Houchard
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
[Fwd: panic: don't do that ?]
Hi!
I've sent this post to comp.unix.bsd.freebsd, and I've been told that I
should report the problem to this list, so...
Original Message
Hi folks!
I was trying to modularize the sound in my 5.0R machine, which has two
sound cards:
$ dmesg | grep pcm.:
pcm0: port 0xb000-0xb003,0xb400-0xb403,0xb800-0xb8ff irq
9 at device 4.5 on pci0
pcm1: port 0xa000-0xa03f irq 9 at device 10.0 on pci0
In order for them to work properly as modules, the files
snd_{pcm,via82c686,es137x}.ko have to be loaded in the beginning AFAIK.
Or else they won't be recognized and will be given as PCI devices with
"no driver attached".
Well, two issues:
1)
If they aren't loaded (I forgot them on the 1st try by mistake), the
kernel panics if I try to change hw.snd.maxautovchans (that odd "bwrite:
buffer is not busy???" message again!). That shouldn't happen: if I
don't have any soundcards, this oid shouldn't _exist_ either!
2)
If they're loaded, an attempt to unload snd_via82c686.ko results in a
panic with the funny message in the subject. But: Aren't modules
supposed to be unloadable? What's the fun with modules then?
Any hints on solving this?
My attempt to load modules instead of the monolithic solution (which
always works) comes due to an odd behaviour of pcm0 (multiplexed with
hw.snd.pcm0.vchans=8) telling that some /dev/dsp{W,}0.[0-7] devices are
busy after their first usage. I wanted to address it by unloading the
affected module and loading it again, but... that'll panic the system.
Has someone had something similar?
Thanks in advance,
David.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
