Re: [Alsa-devel] 0.9.2 Unresolved symbol errors with RH
At 03 Apr 2003 16:00:55 -0800, J. Scott Amort <[EMAIL PROTECTED]> wrote: > > Just to update, as has been posted on the user list - 0.9.0rc7 and later > does not work on RH 8.1 beta or the now released 9 (I can confirm this, > and also can confirm that 0.9.0rc6 DOES work on both). It has been > suggested that the conflict is with Redhat's kernel patches, as 0.9.2 > works with the official kernel 2.4.20, and/or that it is perhaps related > to the new RedHat NPTL implementation and changes made to the alsa > driver since 0.9.0rc6 (which works with this new POSIX implementation). > Can any developer confirm this, or perhaps narrow down where I should > start working? I'm not a stellar programmer, but since it doesn't > appear that anyone else is taking this problem on (if anyone is, PLEASE > let me/us know!), I figure I'd take a try, otherwise I'll be stuck with > 0.9.0rc6 forever! it's most likely related with the rh's backport patch for workqueue. how does linux/workqueue.h look like? does it define __WORK_INITIALIZER() macro? anyway, please report which symbols are left unresolved. ciao, Takashi --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] RME Digi 96 Control
Hello everybody, I have written a GUI control for RME Digi 96 cards. It is based on GTK+. The sources can be downloaded here: http://www.robertvetter.com/rmedigi96control.html Bug reports and suggestions are welcome. Robert Vetter --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Fwd: via82xx problem
At Fri, 4 Apr 2003 00:07:25 +0200, Jordi Mallach wrote: > > [1 ] > On Thu, Apr 03, 2003 at 12:15:55PM +0200, Takashi Iwai wrote: > > most of ALSA-native apps should have options (or config) to choose the > > pcm device. for example, > > > > % aplay -Dhw:0,1 foo.wav > > > > but in your case, i guess it won't fix the problem, because it's > > VIA8233A. please make sure that /proc/asound/card0/pcm0p/info shows > > the subdevices_count = 1. if it's 4, a driver bug. > > It does show subdevices_count: 1. Hmm. What's wrong with it being VIA? > :) > > > do you hear any sounds or completely silent? > > Completely silent, although XMMS "reproduces" the ogg. then perhaps it's not a bug of via82xx part. is the mixer configuration correct? please attach /etc/asound.state to be sure. also, please try the latest cvs version. i changed a bit via82xx.c yesterday. > > i know there have been bug reports about the stuttering sounds, and > > bugs on UT and quake (most likely OSS-mmapped apps). but the silence > > seems like a different problem. > > When I try to tell alsa-xmms about hw:0,1 or hw:0,0, both cases show the > error: "snd_mixer_attach: no such file or directory". What mixer device > should I be trying to use? By default, alsa-xmms sets "PCM". don't know. it sounds like rather a bug of alsa-xmms (or alsa-lib). ciao, Takashi --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] SPDIF and cs46xx ?
On Mon, Mar 31, 2003 at 01:47:52PM +0200, Dr. Werner Fink wrote: > Hmmm ... I've put some lines into cmipci.c to support setting of > the seconf/third status bits within the 2*192 status bits of > the S/P-DIF stream for supporting none audio data PCM streams > (with this it should also possible to support 20 or 24 bits per > PCM word) -> See USE_AES_IEC958 cpp macro in cmipci.c. > > IMHO this way should be possibel for all sound chips which are > not able to provide a hardware setup of the status bits of the > S/P-DIF stream but able to put out raw data (e.g. 32 bit S/P-DIF > words) with doubled sample clock onto the S/P-DIF out plug. Hello again, sorry to ask again :-( I have just installed latest alsa CVS of drivers,lib and utils and still get a: pr 4 13:37:43 localhost vdr[20035]: S/P-DIF: Period size not available: Invalid argument Apr 4 13:37:43 localhost vdr[20035]: S/P-DIF: unable to establish BitStreamOut for none audio PCM Apr 4 13:37:43 localhost vdr[20035]: REPLAY: can't open spdif interface Should I change anything anywhere? Or buy a card with cmipci? (Well I like the Digifire 7.1 I have now, which has also an integrated Firewire...). Thank you very much, Grégoire http://ulima.unil.ch/greg ICQ:16624071 mailto:[EMAIL PROTECTED] --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] HDSP 9652 Status Request
On Thu, 2003-04-03 at 21:46, Thomas Charbonnel wrote: > > Hi, > >I'm just checking in to see what progress has been made on getting > > this patch Paul did to support RME's new firmware for the HDSP series > > into CVS. I've been literally down for 4-5 weeks now waiting for this. I > > am completely unable to run Alsa at all without this patch. > > > >Can someone please provide an update on where all of this has > > progressed to? > > > > Thanks, > > Mark > > Hi Mark, > > I have been working on this patch for a moment. It is nearly finished > now. Unfortunately I couldn't spend much time on it this week. I'll be > back on it this evening. Expect a release quite soon. It'll be done by > the end of the week-end. Exciting features include : 96 kHz support, > midi I/O done in a tasklet, firmware loading from userspace application > (for multiface & digiface users, comes handy if the power supply of the > io box gets disconnected, avoids a reboot), plus nice fltk GUI to > control and display card settings (sample rate, preferred sync source, > spdif bits, sync state, etc...). You'll have to wait a little more for > the totalmix clone, but it's nearly finished too. > > Thomas > > Thomas, Thanks for the update. I wait patiently, if not anxiously, to be able to use Linux again. Over the last two weeks I've gone back to Windows, written 6 new pieces using Acid Pro and Pro Tools. I look very forward to getting Linux support operational again so that I can add all of these soft synths into the mix. Thanks for all your hard work. Cheers, Mark --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] via8xxx invalid cur_ptr
I am getting messages like the following in my logs using kernel 2.4.20-xfs and alsa 0.9.2 release: Apr 3 23:27:52 ccs kernel: ALSA ../alsa-kernel/pci/via82xx.c:675: invalid via82xx_cur_ptr, using last valid pointer What does this mean and have you fixed it yet? Thanks. -- John Covici [EMAIL PROTECTED] --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] SPDIF and cs46xx ?
sorry to ask again :-( I have just installed latest alsa CVS of drivers,lib and utils and still get a: pr 4 13:37:43 localhost vdr[20035]: S/P-DIF: Period size not available: Invalid argument Apr 4 13:37:43 localhost vdr[20035]: S/P-DIF: unable to establish BitStreamOut for none audio PCM Apr 4 13:37:43 localhost vdr[20035]: REPLAY: can't open spdif interface Should I change anything anywhere? Or buy a card with cmipci? (Well I like the Digifire 7.1 I have now, which has also an integrated Firewire...). I would like to get to the bottom of this problem. Let's try figure out exactly which lines of code produces thoose messages: "S/P-DIF: Period size not available: Invalid argument" and "S/P-DIF: unable to establish BitStreamOut for none audio PCM" /Benny --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Re: More Midisport 2x2 troubles
On Friday 04 April 2003 06:21, Ivica Bukvic wrote: > Yet, I still cannot get the second port of the Midisport 2x2 to become > available no matter what. /proc/asound/cards lists only one midisport > 2x2 device (which is ok, I guess, since even Fernando's webpage mentions > that this is the case with the latest CVS stuff), but even in the > /proc/asound/card2 (which is indexed as such) it only lists one midi > port. Same is the case with the /dev/snd/midi* stuff. > > I would at this point like to know if this is a bug (so that I can stop > wasting time on it) and if so, will it be addressed any time soon, and > furthermore what will be the future approach to this issue, will the > notion of assigning one /dev/midi device for each port prevail, or will > we have to access other ports on the same device through alsa's > hw:0, kind of approach, or perhaps something completely > different. Hi, I think that the USB audio/midi driver did not change its behavior since 0.9.0rc4, and Clemens (who wrote the midi part) already explained the basic concepts. The second MIDI port in a Midisport2x2 is not a device, but a sub-subdevice, and its difficult to work with it using OSS tools. That's why I am using the VirMIDI driver to access it. The VirMIDI driver copies its inputs to its output ports, and also has OSS support. To clarify, let me show an example. This is the relevant part of my /etc/modules.conf: alias snd-card-0 snd-ens1371 alias snd-card-1 snd-usb-audio alias snd-card-2 snd-usb-audio alias snd-card-3 snd-virmidi options snd cards_limit=4 options snd-ens1371 index=0 options snd-usb-audio index=1,2 vid=0x0763,0x0582 pid=0x1110,0x0005 options snd-virmidi index=3 midi_devs=2 alias sound-slot-0 snd-card-0 alias sound-slot-1 snd-card-1 alias sound-slot-2 snd-card-2 alias sound-slot-3 snd-card-3 With this setup, my Midisport2x2 is the ALSA client 72 (no matter which USB port i used to plug it). This is what I get from /proc/asound/seq/clients: Client 64 : "Rawmidi 0 - ES1371" [Kernel] Port 0 : "ES1371" (RWeX) Client 72 : "Rawmidi 1 - Midisport 2x2" [Kernel] Port 0 : "Midisport 2x2 Port 0" (RWeX) Port 1 : "Midisport 2x2 Port 1" (RWeX) Client 80 : "Rawmidi 2 - UM-2" [Kernel] Port 0 : "UM-2 Port 0" (RWeX) Port 1 : "UM-2 Port 1" (RWeX) Client 88 : "Virtual Raw MIDI 3-0" [Kernel] Port 0 : "VirMIDI 3-0" (RWeX) Client 89 : "Virtual Raw MIDI 3-1" [Kernel] Port 0 : "VirMIDI 3-1" (RWeX) In the OSS raw MIDI world: /dev/midi00 (14, 2) is the ES1371 MIDI port /dev/midi01 (14, 18) is the Midisport2x2 1st port /dev/midi02 (14, 34) is the UM-2 1st port /dev/midi03 (14, 50) is the 1st VirMIDI port /dev/amidi3 (14, 61) is the 2nd VirMIDI port There is nothing usable on /dev/amidi0, /dev/amidi1 or /dev/amidi2. To play with the second port of the Midisport2x2 and OSS, you first connect the VirMIDI client to the Midisport 2nd port with something like this: $ aconnect 88:0 72:1 Now, everything you send to /dev/midi03 is played on the second Midisport output port. To record, you should make another connection: $ aconnect 72:1 88:0 And now you can read from /dev/midi03 what is received from the second Midisport input port. To use the ALSA rawmidi API with these ports, you must remember that there aren't subdevices, but sub-subdevices. In my case: ES1371 MIDI port is "hw:0", or "default" Midisport2x2 1st port is "hw:1,0,0" Midisport2x2 2nd port is "hw:1,0,1" UM-2 1st port is "hw:2,0,0" UM-2 2nd port is "hw:2,0,1" VirMIDI 1st port is "hw:3,0" VirMIDI 2nd port is "hw:3,1" As you can see, there is lot of fun. Enjoy ;-) Regards, Pedro -- ALSA Library Bindings for Pascal http://alsapas.alturl.com --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] SPDIF and cs46xx ?
On Fri, Apr 04, 2003 at 08:01:37PM +0200, Benny Sjostrand wrote: > I would like to get to the bottom of this problem. > Let's try figure out exactly which lines of code produces thoose > messages: "S/P-DIF: Period size not available: Invalid argument" and > "S/P-DIF: unable to establish BitStreamOut for none audio PCM" The whole archive could be found under http://prdownloads.sourceforge.net/sourceforge/bitstreamout/ And I have put the file spdif.c under http://ulima.unil.ch/greg/linux/spdif.c In this file, there are the errors messages, unfortunately it's far too complicated for my basic programming knowledge ;-) Thank you very much, Grégoire http://ulima.unil.ch/greg ICQ:16624071 mailto:[EMAIL PROTECTED] --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-user] Re: [Alsa-devel] Redhat 9.0 also has the snd.o unresolved symbol schedule_work issue
Sounds like a real possibility, but I do not know nearly enough about how the ALSA drivers work to agree or disagree. > This is most likely (AFAIK) because redhat ships their kernel with NPTL > (Native POSIX Thread Library). > >>From the release notes: > > Red Hat Linux 9 includes the Native POSIX Thread Library (NPTL), a new > implementation of POSIX threads for Linux. This library provides > performance improvements and increased scalability for i686 or better > processors. > > This thread library is designed to be binary compatible with the old > LinuxThreads implementation; however, applications that rely on the > places where the LinuxThreads implementation deviates from the POSIX > standard will need to be fixed. Notable differences include: > > - Signal handling has changed from per-thread signal handling to POSIX > process signal handling. > > - getpid() returns the same value in all threads. > > - Thread handlers registered with pthread_atfork are not run if vfork() > is used - no manager thread > > -- > > I could be wrong but this is where I think the problem is... > > > On Sun, 2003-03-30 at 16:19, Jason Corekin wrote: >> Good news I have Alsa 0.9.2 working on RedHat 9.0 working with kernel >> version 2.4.20. The catch is that I had to replace the RedHat kernel >> with the stock kernel from www.kernel.org. So the problem has to be >> in the changes that RedHat made to their kernel. I have to give >> credit to Kmberry and Lance A. Brown, for pointing out that RedHat >> plays around with the kernel before releasing it >> The only thing that I have not yet tried to do is to rework the >> symlinks to make sure that the Alsa code knows where to find the right >> kernel dependencies. Since I do not know if there is any thing that I >> am now missing from not running on the RedHat kernel or not it would >> be nice to at least have some modules compatible with their kernel, >> but I'm not too worried about it. >> I hope this helps. >> >> Jason Corekin >> >> >> >> On Sat, 2003-03-29 at 14:23, Jason Corekin wrote: >> > I work for HP and I just downloaded the new RH 9.0 iso's from our >> internal source yesterday. After upgrading from RH 8.0 and the >> 2.4.18 kernel I tried to update my Alsa drivers to work with the >> new 2.4.20 kernel and found that althought the Alsa 0.9.2 drivers >> had compiled and installed without trouble the would not load. >> Instead I am getting the error unresolved symbol schedule_work. >> > >> > Now I know that there have been numerous similar complaints on the >> user mailing list, but since nobody seems to be privinding and >> answer and since I saw no mention of this error on the development >> list I thought that I would send out this mail to both lists and >> see if I could get a little bit more of a response. >> > >> > I have a Yamahaa Waveforce 192XG, a 1.2Ghz Duron, 128MB of ram, and >> a ECS K7S5A motherboard. But since this appears to be a layer >> other then the hardware driver layer and has been reported with to >> be affecting numerous cards, I really don't think that my hardware >> config will be of much importance. >> > >> > Jason Corekin >> > >> > >> > >> > --- >> > This SF.net email is sponsored by: >> > The Definitive IT and Networking Event. Be There! >> > NetWorld+Interop Las Vegas 2003 -- Register today! >> > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en >> > ___ >> > Alsa-devel mailing list >> > [EMAIL PROTECTED] >> > https://lists.sourceforge.net/lists/listinfo/alsa-devel > -- > Edward Muller > > Interlix - President > > Web Hosting - PC Service & Support > Custom Programming - Network Service & Support > > Phone: 417-862-0573 > Cell: 417-844-2435 > Fax: 417-862-0572 > > http://www.interlix.com --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] 0.9.2 Unresolved symbol errors with RH
The symbol is "schedule_work". There is more info on the user list, but this is the critical info. Jason Corekin > At 03 Apr 2003 16:00:55 -0800, > J. Scott Amort <[EMAIL PROTECTED]> wrote: >> >> Just to update, as has been posted on the user list - 0.9.0rc7 and >> later does not work on RH 8.1 beta or the now released 9 (I can >> confirm this, and also can confirm that 0.9.0rc6 DOES work on both). >> It has been suggested that the conflict is with Redhat's kernel >> patches, as 0.9.2 works with the official kernel 2.4.20, and/or that >> it is perhaps related to the new RedHat NPTL implementation and >> changes made to the alsa driver since 0.9.0rc6 (which works with this >> new POSIX implementation). Can any developer confirm this, or perhaps >> narrow down where I should start working? I'm not a stellar >> programmer, but since it doesn't appear that anyone else is taking >> this problem on (if anyone is, PLEASE let me/us know!), I figure I'd >> take a try, otherwise I'll be stuck with 0.9.0rc6 forever! > > it's most likely related with the rh's backport patch for workqueue. how > does linux/workqueue.h look like? > does it define __WORK_INITIALIZER() macro? > > anyway, please report which symbols are left unresolved. > > > ciao, > > Takashi > > > --- > This SF.net email is sponsored by: ValueWeb: > Dedicated Hosting for just $79/mo with 500 GB of bandwidth! > No other company gives more support or power for your dedicated server > http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ > ___ > Alsa-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/alsa-devel --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] [bug] cs46xx: sound way too fast and chopped
Hi, I'm using the CS46xx sound chip in my Thinkpad A21m with a 2.4.20 kernel and alsa 0.9.2, compiled by gcc (GCC) 3.2.3 20030309 (Debian prerelease). At unpredictable times, the sound becomes very silent, and it appears as if it was playing many times faster than it should. Only very short snippets of sound (<1ms, not intelligible) are played with lots of silence in between. This happens a lot when the computes is busy doing other things besides playing sounds (such as intense hard drive activity). It has happened to me once at least through every movie that I've watched (using mplayer, if that helps) recently. Seeking in XMMS has also caused that kind of problem before. lspci -v: 00:05.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24 [CrystalClear SoundFusion Audio Accelerator] (rev 01) Subsystem: IBM: Unknown device 0153 Flags: bus master, slow devsel, latency 64, IRQ 11 Memory at f4122000 (32-bit, non-prefetchable) [size=4K] Memory at f400 (32-bit, non-prefetchable) [size=1M] Capabilities: [40] Power Management version 2 lspci -vn: 00:05.0 Class 0401: 1013:6003 (rev 01) Subsystem: 1014:0153 Flags: bus master, slow devsel, latency 64, IRQ 11 Memory at f4122000 (32-bit, non-prefetchable) [size=4K] Memory at f400 (32-bit, non-prefetchable) [size=1M] Capabilities: [40] Power Management version 2 Best regards and thank you for your help, Andreas -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage! --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
