> So I tried to collect as much information as I can about this freezing
> bug.
Try using the magic SysRq key to get information (see the
sysrq.txt file in the linux/Documentation directory of your
kernel sources; you will probably have to recompile your
kernel).
Duncan.
___
On Tue, 27 Nov 2001, Paul Davis wrote:
> enclosed below what happens when using ALSA, mmap mode and poll(2) on my
> trident card at 44100. the value of contiguous is the value returned
> by snd_pcm_mmap_begin() having been passed a value of 2048 as the
> "upper limit". the period size is 2048 fr
On Tue, 2001-11-27 at 16:12, Emmanuel Fleury wrote:
>
> Moreover, I don't know WHERE it is freezing. It must definitely be
> somewhere in the kernel (you can't blow up Linux like this without being
> directly in the kernel), but where precisely ??? Dunno.
>
> So, Hlp ! :-)
So I take it m
On Tue, 2001-11-27 at 18:46, Tom Browne wrote:
> Well, well...
>
> Looks like things might be alright after all. Swapping out the Savage4 for
> the TNT2 fixed the X11 latency problems, and the LL patch fixed the
> remaining glitches on the write test which the pre-empt+lockbreak combo
> failed t
Well, well...
Looks like things might be alright after all. Swapping out the Savage4 for
the TNT2 fixed the X11 latency problems, and the LL patch fixed the
remaining glitches on the write test which the pre-empt+lockbreak combo
failed to solve.
Here's the results (Celeron-II 1.2 @ 1.5, TUSL2-M
enclosed below what happens when using ALSA, mmap mode and poll(2) on my
trident card at 44100. the value of contiguous is the value returned
by snd_pcm_mmap_begin() having been passed a value of 2048 as the
"upper limit". the period size is 2048 frames, the buffer size is 2 *
period size. the fi
Well, with or without the option that you mentioned below, I'm not getting
any sound. Though pmidi and sbiload don't complain, I get no sound. I
can load /usr/share/apps/kmid/fm/std.o3 and
/usr/share/apps/kmid/fm/drums.o3 with:
sbiload -p 65:0 --opl3 /usr/share/apps/kmid/fm/std.o3 /usr/share/a
Hi,
So I tried to collect as much information as I can about this freezing
bug.
First I am running with a Debian testing/unstable (Sid). To 'celebrate'
the bug, I compiled two kernel 2.4.16, one smp and one mono (to see if
it was SMP related).
My hardware is:
- Dual-proc PentiumII@450MHz
- Moth
Jeffrey H. Ingber wrote:
> Wouldn't that require checking out the source files to read the
> INSTALL?
You can get the sources by many different ways.
The first one is probably to get it from the stable version from
the website. If you notice a bug or something and you want the last
cvs versi
Paul Davis wrote:
>
> so do you feel absolutely comfortable in asserting that for all the
> hardware that both OSS and ALSA support, ALSA's support is more or
> less as good as the OSS code? i just worry that people who don't want
> to see this change will argue that ALSA must get all of its low
Wouldn't that require checking out the source files to read the INSTALL?
Jeffrey H. Ingber (jhingber _at_ ix.netcom.com)
On Tue, 2001-11-27 at 10:27, Emmanuel Fleury wrote:
> Hi again,
>
> As I don't like that anybody loose time and to make it easier for
> beginner, I propose to Add some lines
On Tue, 27 Nov 2001, Paul Davis wrote:
> in general, there seem to have been a lot more people working on the
> OSS drivers than the ALSA ones.
as others have said, this should change if alsa is in the kernel tree.
this is a development kernel, and in an odd-numbered release, nothing is
assured
jaroslav - this happens on several different "consumer" audio
interfaces. an application waiting in poll(2) will return, but
snd_pcm_avail_update() and snd_pcm_mmap_begin() will report only a
single (or very small number of) frames available. do you consider
this an error, or should an application
On Tue, 27 Nov 2001, Steve Harris wrote:
> I've been getting reliable oops's when using the ens1371 driver with
> ardour. If ardour segfaults or is kill -9'd the kernel oopses inside the
> alsa 1371 driver.
> This is with current CVS alsa and back at least a few weeks.
> I can't provide the whole
I've been getting reliable oops's when using the ens1371 driver with
ardour. If ardour segfaults or is kill -9'd the kernel oopses inside the
alsa 1371 driver.
This is with current CVS alsa and back at least a few weeks.
I can't provide the whole oops as the interrupt hander is killed, hence no
Will that mean that alsa-driver will be in the kernel.
Where will alsa-lib, alsa-utils and alsa-tools go ?
Cheers
James
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
On Tue, 27 Nov 2001, Takashi Iwai wrote:
> > I have an AD1816a based ISA card. It doesn't work with the current Alsa
> > (though it does work with 0.5). I have no idea how to fix it, or where to find
> > someone to fix it (aside from here). I have no idea whether it's a generally
> > broken dri
There is a point ALSA cant reach without beeing in the kernel.
Because of this, it cant be better than OSS in all respects.
Use developement kernels for what they are intended for. Use 2.5.x for
ALSA.
Regards,
Robert
___
Alsa-devel
Hi,
At Tue, 27 Nov 2001 20:11:42 +0100,
I wrote:
>
> I think OPL3 synth can be easily implemented on ymfpci driver too.
The ALSA 0.9.0 driver already supports OPL3.
If you cannot use it as default, try to add an option
"snd_fm_port=0x388" to snd-card-ymfpci driver.
If it's ok, you can use sbilo
At Tue, 27 Nov 2001 10:00:49 -0800 (PST),
Ken Arromdee wrote:
>
> On Tue, 27 Nov 2001, Takashi Iwai wrote:
> > That's true. And not all ALSA drivers have been tested well on the
> > current version, especially ones for old ISA chips or SB (and its
> > compatible) driver. In such a case, "good"
At Tue, 27 Nov 2001 13:38:59 -0500 (EST),
Adam K Kirchhoff wrote:
>
> Currently, however, my Hoontech Digital-XG (yamaha-754 chip) seems to be
> better supported under OSS than Alsa. Both the FM synth and the rear and
> front channels are supported. Under Alsa, the FM synth is unsupported,
> a
Bob Ham wrote:
>
> On Tue, 2001-11-27 at 17:37, Emmanuel Fleury wrote:
>
> See, what you've done here is confuse "stable" with "developmental".
> Easy mistake to make.
Hum,
Don't confuse "developmental" and "crappy".
Easy mistake to make :-)
Regards
--
Emmanuel
My behaviour is addi
> On Tue, 27 Nov 2001, Paul Davis wrote:
>
> > >I monitor creative drivers, and they have not any extra features
> > >(except missing an user space linker for FX8010 DSP - different design of
> > >microcode maintaince). ALSA offers the wavetable synthesis for EMU10K1 for
> > >months, while the cr
On Tue, 27 Nov 2001, Takashi Iwai wrote:
> That's true. And not all ALSA drivers have been tested well on the
> current version, especially ones for old ISA chips or SB (and its
> compatible) driver. In such a case, "good" means "more stable" or
> "support more chips". That's what lack ALSA lac
On Tue, 2001-11-27 at 17:37, Emmanuel Fleury wrote:
> Well, I'm not very introduced to all this Alsa stuff right now, but what
> I expect from Alsa, before being part of the kernel, is to:
> STOP FREEZING MY DAMN COMPUTER
> I am not sure that Linus will be pleased about that !
See, what yo
On Tue, 27 Nov 2001, Emmanuel Fleury wrote:
> Bob Ham wrote:
>
> > On Tue, 2001-11-27 at 14:18, Paul Davis wrote:
> >
> > Do you feel absolutely comfortable in assuming that it is neccessary
> > for ALSA to have its drivers in "as good or better than" state for it
> > to be included in Linux
Bob Ham wrote:
> On Tue, 2001-11-27 at 14:18, Paul Davis wrote:
>
> Do you feel absolutely comfortable in assuming that it is neccessary
> for ALSA to have its drivers in "as good or better than" state for it
> to be included in Linux? Having Linux do sound the ALSA way is better
> than ha
On Tue, 27 Nov 2001, Nicolas DEVERGE wrote:
> Hi,
> I tried to use the current CVS version of the alsa lib and aserver tool.
> I would like to use two instances of aplay in the same time.
>
> First, I tried with this configuration :
>
> server.local {
> host localhost
> socket /tmp/alsa
> p
Suggestion, for people who haven't used CVS much and may not know what cvs
update does. Change:
> 3) Updating your snapshot
to
3) Updating your snapshot to latest version of the CVS sources
Chris
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https
On Tue, 2001-11-27 at 14:18, Paul Davis wrote:
> so do you feel absolutely comfortable in asserting that for all the
> hardware that both OSS and ALSA support, ALSA's support is more or
> less as good as the OSS code? i just worry that people who don't want
> to see this change will argue that AL
Hi,
I noticed a very little weird thing while I was installing alsa-lib.
I noticed that the newly created /usr/include/alsa directory was
set with the same umask than the root (for me it is 077).
As I am compile the sources as user, I immediatly noticed that the user
can access to /usr/include
Hi,
I tried to use the current CVS version of the alsa lib and aserver tool.
I would like to use two instances of aplay in the same time.
First, I tried with this configuration :
server.local {
host localhost
socket /tmp/alsa
port
}
pcm.shared_left {
type share
slave.pcm "plughw:
Hi again,
As I don't like that anybody loose time and to make it easier for
beginner, I propose to Add some lines in the INSTALL file.
If you want I can do the patches against the current cvs
(diff is my friend :-)).
Here is what I want to add:
Compiling from a CVS snapshot
==
At Tue, 27 Nov 2001 15:38:07 +0100 (CET),
Jaroslav Kysela wrote:
>
> On Tue, 27 Nov 2001, Paul Davis wrote:
>
> > >I monitor creative drivers, and they have not any extra features
> > >(except missing an user space linker for FX8010 DSP - different design of
> > >microcode maintaince). ALSA offe
On Tuesday 27 November 2001 14:18, Paul Davis wrote:
>
> so do you feel absolutely comfortable in asserting that for all the
> hardware that both OSS and ALSA support, ALSA's support is more or
> less as good as the OSS code? i just worry that people who don't want
> to see this change will argue
On Tue, 27 Nov 2001, Paul Davis wrote:
> >I monitor creative drivers, and they have not any extra features
> >(except missing an user space linker for FX8010 DSP - different design of
> >microcode maintaince). ALSA offers the wavetable synthesis for EMU10K1 for
> >months, while the creative drive
>I monitor creative drivers, and they have not any extra features
>(except missing an user space linker for FX8010 DSP - different design of
>microcode maintaince). ALSA offers the wavetable synthesis for EMU10K1 for
>months, while the creative driver offers only PCM & mixer capabilities.
so do y
On Tue, 27 Nov 2001, Paul Davis wrote:
> >> If nobody has comments, I'm ready to prepare a whole patch for Linus
> >> against the actual 2.5.1pre code.
>
> i think we need to be just a little careful how we approach this. i
> get the sense that many people feel that although ALSA has a much
> bet
>> If nobody has comments, I'm ready to prepare a whole patch for Linus
>> against the actual 2.5.1pre code.
i think we need to be just a little careful how we approach this. i
get the sense that many people feel that although ALSA has a much
better design than OSS, they also feel that the actual
I have compiled the driver 0.5.10b for the ESS 1869
chipset.
When I try to install the module I have some errors
(unresolved symbol).
The result of depmod is given below :
/lib/modules/2.2.10/misc/snd-card-es18xx.o: unresolved
symbol(s) snd_mpu401_uart_interrupt_Rsmp_69aea529 snd_register_in
> > If nobody has comments, I'm ready to prepare a whole patch for Linus
> > against the actual 2.5.1pre code.
Since there is no need for this patch to support 2.2 kernels, some
simplifications should be possible.
Duncan.
PS: I'm not saying that it is desirable to remove 2.2 support, it's just
On Tue, 27 Nov 2001 19:59, Josh Green wrote:
> > If nobody has comments, I'm ready to prepare a whole patch for Linus
> > against the actual 2.5.1pre code.
> >
> > Jaroslav
>
> I have some comments..
>
> Wooohooo!
> Yeah!
> Cool!
Absolutely... we are a
On Tue, 2001-11-27 at 00:32, Jaroslav Kysela wrote:
> On Mon, 26 Nov 2001, Dan Hollis wrote:
>
> > Now that kernel 2.5.0 tree is started, shouldn't we start pushing to get
> > ALSA into the tree?
>
> Let's go. Our latest patch against 2.5.0 is:
>
> ftp://ftp.alsa-project.org/pub/kernel-patches/
On Mon, 26 Nov 2001, Dan Hollis wrote:
> Now that kernel 2.5.0 tree is started, shouldn't we start pushing to get
> ALSA into the tree?
Let's go. Our latest patch against 2.5.0 is:
ftp://ftp.alsa-project.org/pub/kernel-patches/alsa-0.9.0beta9-k2.5.0-3310916.diff.bz2
The oss-move script (to cha
44 matches
Mail list logo
