Hi all,
I have this small question:
Is it possible (I presume it is) to alter mixer settings in Alsa by
invoking some kind of a system call using shell (i.e. how the RME hdsp
can have its stuff altered)?
If so, what is the range of values that describe the loudest and softest
levels?
Finally, a
> > alsasound script calls alsactl and card-specific scripts (if any).
> > this should be avoided in the case of partial load.
>
> Yes, I took care of executing them just for the cards that had been
> loaded.
>
> > IIRC, modprobe returns 0 even if called with the existing module.
> > (if the loa
I'm having some redefinition errors (struct work_struct,
__WORK_INITIALIZER, et al found in workqueue.h in the kernel source)
while trying to compile ALSA driver 0.9.0rc7. My kernel is 2.4.20-2.21
RPM from the RedHat 8.1 beta. Any ideas on the following?
In file included from ../alsa-kernel/c
I am having one new problem with the 9.0rc8a driver on a fairly standard
redhat 8.0 box.
The system has an athlon cpu and up through the rc6 version, when
I built the rpms, I got the (expected) alsa-driver-xxx.athlon.rpm
and alsa-kernel-xx.athlon.rpm. However at 7.1 this stopped and only
the i386
I have pretty much the same problem as you.
Does anyone know what the problem may be?
On Thu, 2003-02-27 at 04:04, Pattrick Hueper - proQrent GmbH wrote:
> Hi all,
>
> about a week ago, i reported problems with alsa 0.9.0 rc7 and VIA 8233.
>
> I got the tip to try rc6, but that did not help eit
> > Thanks! I started working on differentiating in the alsasound alsa
> > startup script between a full start (all modules are loaded when
> > alsasound executes) and a partial start (some of the modules are already
> > loaded when alsasound executes and it has to load the rest).
> >
> > The fir
On Mon, 3 Mar 2003 18:39:27 +0100
Christian Heimanns <[EMAIL PROTECTED]> wrote:
> via82xx_cur_ptr
Hi Folks,
I still have the problems discribed in my first mail. I have found three
older messages from users having the same/similar problem:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg06240.h
Hi all,
A while ago I posted this message, although mixed with some other false
assumptions of mine -- apologies for my ignorance( see:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg05286.ht
ml thread) and then did the same thing just a couple days ago with the
whole output log as requested (s
My SB-Live 5.1 (emu10k1) worked with ALSA 0.9.0beta10.
If I use 'pmidi' to play midi files with internal Wavetable, it is OK!
But if I send MIDI messages via rawmidi device, only MPU401 can be Tx/Rx
successfully.
Eg: cat MIDI_MESSAGES_FILE > /dev/snd/midiC0D0(MPU401)OK!!
cat MI
At Wed, 5 Mar 2003 11:29:45 +0100,
Jan Kr�mer wrote:
>
> Hi
> First a Disclaimer, I have no clue of low-level or alsa development, and i am
> only describing what I found by wildly experimenting...
>
> Thing is, I have the above mentioned Sound card and like to run Linux, today I
> got fed up w
I wrote a c code to send MIDI message "NOTE ON" to sequencer, but I get
"Segmentation fault".
What's wrong with it?
#include
#include
#include
#include
#define MPUOUT_CLIENT 73
#define MPUOUT_PORT 0
main(){
MIDI_IO();
}
void MIDI_IO(){
int portid;
snd_seq_t *ctxp;
snd_seq_event_t ev
Uhm, what do you mean? I don't understand. Are you surprised I don't have
those lines? If so, that should be cleared now :-)
I'm really a little surprised that you don't hear anything. Are you really
really sure, your mixer channels are unmuted and not equal zero? Also, I'd
check the other ou
Hi
First a Disclaimer, I have no clue of low-level or alsa development, and i am
only describing what I found by wildly experimenting...
Thing is, I have the above mentioned Sound card and like to run Linux, today I
got fed up with not being able to use the SPDIF Out, and looked around the
sour
At 04 Mar 2003 19:01:24 -0800,
Fernando Pablo Lopez-Lezcano wrote:
>
> > > > >lists about this and to do it cleanly it would be nice to have available
> > > > >in /proc/asound the list of modules currently loaded. That is not
> > > > >available today (I think Takashi said he might add that)."
> >
Hi,
I have had problems finding a Linux driver for the soundcard on my new
machiine, until I came across ALSA. What a massive relief. This
machine was delivered without an O/S (as requested), and it was
fantastic to finally hear some sounds from my speakers.
I have one slight problem though. I
At Wed, 05 Mar 2003 10:04:10 +0200,
Andrei Boros wrote:
>
> I looked into the file memory_wrapper.c and the second patch you sent me
> sets this.
> I think it should read :
> #include
yep, it's a typo. sorry.
>
> After this, the driver compilation succeeded.
>
> I deleted the snd-* modules,
Takashi Iwai, [EMAIL PROTECTED] wrote:
>
> Mike Kriz's e-mail address has changed. Please contact him personally for his
> new address if you actually know him.,,Unsolicited e-mail will be reported.
Sorry, but who is Mike Kriz?
Maybe you sent this message to the wrong person?
I check all my
On a Slackware 7.0 system, kernel 2.2.23, alsa-0.9-rc7:
I have 2 sound cards: a Hercules Gamesurround Fortissimo II and an old
Opti924 ISA card.
The Hercules works.
The Opti924 is another story. After reading on the ALSA site that 924
chipset is supported by the snd-opti92x-ad1848 driver, I ran
Takashi Iwai wrote:
>
> hmm, pci_compat_22.c looks unchanged. could you check whether the
> patch was correctly applied?
Well, the patch you sent me modifies pci_compat_22.c
When I first applied it I got an error in acore/misc.c HUNK 1 failed.
I applied the patch again with -l and it went in co
19 matches
Mail list logo
