[Alsa-devel] alsa probelm with RedHat 8.0 and kernel 2.4.20-4.11.acpi
Hi everybody, I installed the kernel 2.4.20 and the lates alsa drivers from planet ccrma. When starting the alsa drivers I get the following kernel oops: [EMAIL PROTECTED] root]# cat alsastart.log | ksymoops ksymoops 2.4.5 on i586 2.4.20-4.ll.acpi. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.20-4.ll.acpi/ (default) -m /boot/System.map-2.4.20-4.ll.acpi (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. Error (expand_objects): cannot stat(/lib/ext3.o) for ext3 ksymoops: No such file or directory Error (expand_objects): cannot stat(/lib/jbd.o) for jbd ksymoops: No such file or directory /usr/bin/find: /lib/modules/2.4.20-4.ll.acpi/build: Datei oder Verzeichnis nicht gefunden Error (pclose_local): find_objects pclose failed 0x100 Warning (map_ksym_to_module): cannot match loaded module ext3 to a unique module object. Trace may not be reliable. invalid operand: CPU:0 EIP:0010:[]Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010246 eax: 21b6 ebx: c3627860 ecx: 0021 edx: d09478e8 esi: edi: 0074 ebp: 0021 esp: c958bed0 ds: 0018 es: 0018 ss: 0018 Process modprobe (pid: 1109, stackpage=c958b000) Stack: d093d000 0246 c3627860 0021 d09475d4 d094f80a d093d3c8 d094f80a 0021 c975aae0 0001 0001 d094c000 d094f114 0021 d09510c8 d094f80a ffea c011a224 d094fcc8 Call Trace:[] [] [] [] [] [] [] [] [] [] [] Code: 0f 44 f0 a1 c8 75 94 d0 c7 44 24 08 00 00 00 00 25 b6 01 00 >>EIP; d093fc11 <[snd]snd_info_create_device+31/110> <= >>eax; 21b6 Before first symbol >>ebx; c3627860 <_end+32f1ec0/104d76c0> >>edx; d09478e8 <[snd]snd_minors_hash+8/40> >>esp; c958bed0 <_end+9256530/104d76c0> Trace; d09475d4 <[snd]sound_mutex+0/2c> Trace; d094f80a <[snd-timer]__kstrtab_snd_timer_global_register+2/40> Trace; d093d3c8 <[snd]snd_register_device+c8/120> Trace; d094f80a <[snd-timer]__kstrtab_snd_timer_global_register+2/40> Trace; d094f114 <[snd-timer]alsa_timer_init+a4/110> Trace; d09510c8 <[snd-timer]snd_timer_reg+0/1c> Trace; d094f80a <[snd-timer]__kstrtab_snd_timer_global_register+2/40> Trace; c011a224 Trace; d094fcc8 <[snd-timer]__kstrtab_snd_timer_system_resolution+420/1758> Trace; d094c060 <[snd-timer]snd_timer_instance_new+0/c0> Trace; c0108b0f Code; d093fc11 <[snd]snd_info_create_device+31/110> <_EIP>: Code; d093fc11 <[snd]snd_info_create_device+31/110> <= 0: 0f 44 f0 cmove %eax,%esi <= Code; d093fc14 <[snd]snd_info_create_device+34/110> 3: a1 c8 75 94 d0mov0xd09475c8,%eax Code; d093fc19 <[snd]snd_info_create_device+39/110> 8: c7 44 24 08 00 00 00 movl $0x0,0x8(%esp,1) Code; d093fc20 <[snd]snd_info_create_device+40/110> f: 00 Code; d093fc21 <[snd]snd_info_create_device+41/110> 10: 25 b6 01 00 00and$0x1b6,%eax 2 warnings and 3 errors issued. Results may not be reliable. The following rpms are installed: [EMAIL PROTECTED] root]# rpm -qa | grep alsa alsa-driver-0.9.2-4.1.cvs alsa-kernel-2.4.20-4.ll.acpi-0.9.2-4.1.cvs alsa-lib-0.9.2-4.cvs alsa-lib-devel-0.9.2-4.cvs alsa-utils-0.9.2-4.cvs alsa-tools-0.9.2-4.cvs Any ideas what goes wrong here? Everything works great with kernel 2.4.19 though. [EMAIL PROTECTED] --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] hdspconf - cool!
Thomas, Thanks very much for creating this new little configuration app for the HDSP devices. Very nice. I have one question. If I set the Sample Clock Source to 'Auto Sync', then I'm seeing the AutoSync Ref. box going between ADAT1/48K and no setting at all. It's just bouncing back and forth. I do not remember seeing this card do anything like that under Windows. I've also just noticed that if I set the clock at 48K, and then move it to AutoSync, I'm seeing the card going back and forth between master and slave. Kind of strange. Great start though. Very nice to have a cool little config utility! Thanks! Cheers, Mark --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] hdsp I/O-error
Hello again. Maybe these will mean something? This is /proc/asound/card0/hdsp when I've loaded the firmware in windows: RME Hammerfall DSP + Multiface (Card #1) Buffers: capture c0e0 playback c0c0 IRQ: 11 Registers bus: 0x1080 VM: 0xcf977000 Control register: 0x10080de Status register: 0x1200 Status2 register: 0x0703 FIFO status: 0 MIDI1 Output status: 0xff00 MIDI1 Input status: 0xff00 MIDI2 Output status: 0xff00 MIDI2 Input status: 0xff00 Buffer Size (Latency): 8192 samples (2 periods of 32768 bytes) Hardware pointer (frames): 0 Passthru: no Line out: on Firmware version: 5 Sample Clock Source: Internal 48 kHz Preferred Sync Reference: ADAT1 AutoSync Reference: None AutoSync Frequency: 0 System Clock Mode: Master System Clock Frequency: 48000 IEC958 input: Internal IEC958 output: Coaxial only IEC958 quality: Consumer IEC958 emphasis: off IEC958 NonAudio: off IEC958 sample rate: Error flag set ADAT1: No Lock SPDIF: No Lock Word Clock: No Lock ADAT Sync: No Lock Strangely, after I cat'ed it again right after, there were some changes: < Control register: 0x10080de > Control register: 0x100805c < Buffer Size (Latency): 8192 samples (2 periods of 32768 bytes) > Buffer Size (Latency): 4096 samples (2 periods of 16384 bytes) < Sample Clock Source: Internal 48 kHz > Sample Clock Source: Internal 32 kHz < System Clock Frequency: 48000 > System Clock Frequency: 32000 pd is quite verbose too, maybe this will tell something: # pd -rt -alsa -nomidi ALSA lib pcm_hw.c:1078:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed: Device or resource busy snd_pcm_open (output): Device or resource busy ALSA: sample width 4 bytes ALSA: set input channels to 14 ALSA: rate to 44100 fragsize b 64 nfrags a 27 ALSA lib pcm_hw.c:325:(snd_pcm_hw_hw_params) SNDRV_PCM_IOCTL_HW_PARAMS failed: Device or resource busy snd_pcm_hw_params (input): Device or resource busy ALSA: hw interface configured pd: pcm.c:5020: snd_pcm_sw_params_current: Assertion `pcm->setup' failed. Aborted (sampling rate doesn't change in /proc/asound/card0/hdsp) from /etc/modules.conf: alias char-major-116 snd alias snd-card-0 snd-hdsp options line_outs_monitor="1" alias char-major-14 soundcore alias sound-slot-0 snd-card-0 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-12 snd-pcm-oss -- Jaakko Prättälä [EMAIL PROTECTED] --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] VIA8235 SPDIF problems
Hi, I have a Shuttle SK41G machine. This has a VIA8235, with an Avance Logic ALC 650 Rev 0 on it. Problem: I want to use the digital out on this board talking to my digital receiver for normal audio. I also want to have AC3/DTS passthrough when playing DVDs. Something is playing up. Usually, I can get AC3 passthrough working for DVDs.. after a bit of random flailing at the mixer devices, but I can't always. I haven't been able to identify a consistent pattern of changes to make to make it 100% reliable. It just seems to "start working" eventually. I can't get non-AC3/DTS digital audio output to work at all. My decoder DOES light up its wee "Digital" light when I starting playing something, but there is no sound. Oddly enough, I'm pretty sure I DID have this working at one point, but I cannot get anything now. I'm changing: IEC958, IEC958 Input Monitor, IEC958 Output, IEC958 Playback AC97-SPSA, and Analog to IEC958 Output.. oh, and PCM, Master are set quite high. I've also tried sending the output to the "iec958/spdif" devices, but with no luck (although this does seem to change which combinations of mixer settings mean my decoder light the DIGITAL light) I'm using the latest CVS of ALSA, with Xine 1.0beta10. Why am I posting this here? I'm going to try messing with the code to try and fix this, but I'm hoping someone can suggest some things for me to try as I am hampered by a lack of VIA8235 docs. Finally, what are these "VIA DXS" mixer devices? I now have four of them and none of them seems to affect anything! --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] hdsp I/O-error
On Saturday 12 April 2003 22:45, Thomas Charbonnel wrote: > > Hi. More info. This is the /var/log/messages output when I run > > hdsploader. > > > > Apr 12 12:30:56 kiertotahti kernel: ALSA > > ../../alsa-kernel/pci/rme9652/hdsp.c:4104: card initialization pending : > > waiting for firmware > > Apr 12 12:31:03 kiertotahti kernel: ALSA > > ../../alsa-kernel/pci/rme9652/hdsp.c:644: wait for FIFO status <= 0 > > failed after 30 iterations > > Apr 12 12:31:03 kiertotahti kernel: ALSA > > ../../alsa-kernel/pci/rme9652/hdsp.c:3800: initializing firmware upload > > Apr 12 12:31:03 kiertotahti kernel: ALSA > > ../../alsa-kernel/pci/rme9652/hdsp.c:522: loading firmware > > Apr 12 12:31:03 kiertotahti kernel: ALSA > > ../../alsa-kernel/pci/rme9652/hdsp.c:548: finished firmware loading > > Apr 12 12:31:07 kiertotahti kernel: ALSA > > ../../alsa-kernel/pci/rme9652/hdsp.c:644: wait for FIFO status <= 127 > > failed after 5000 iterations > > Apr 12 12:31:07 kiertotahti kernel: ALSA > > ../../alsa-kernel/pci/rme9652/hdsp.c:3824: error creating alsa devices > > > > (I/O-box shows host error). > > Did the hardware show the typical led blinking sequence while the > firmware uploaded, and then the host error, or was the host error > showing from the beginning ? No blinking. The red led is on without a pause. This is so strange. The card is there enough for snd-hdsp to load but after that it's blocked. What could be blocking the fw load process and apps from using the card for I/O if the fw is loaded in windows? I really would love to know how to debug this. How could I try to seek the exact place where the communication breaks down? So far, I've compiled kernels (2.4.20, 2.4.19) trying out a few configurations (pcmcia in kernel and outside, acpi and no acpi irq's from bios or directly, just hoping to get lucky :-) but nothing. Everything looks the same as with rhl's 2.4.18. (Except that external pcmcia couldn't make a connection to the card for snd-hdsp to load.) [What about interrupts? They don't matter here, do they? In linux the pcmcia controller shares irq 11 with eth0. In winXP it gets irq 10 and shares it with something else I don't remember. I hope they aren't significant because I don't think I know how to change them (no bios options available).] -- Jaakko Prättälä [EMAIL PROTECTED] --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] rme9652 in kernel
well, it's simple, adjust the makefile so that hammerfall-mem.o comes before rme9652.o _J In the new year, Jeremy Hall wrote: > Hi, > > I built rme9652 in my kernel so that I could debug with kgdb. > Unfortunately it runs rme9652 before hammerfall_mem, so it refuses to > insert hammerfalls because of no memory, then it makes the memory but > doesn't bother to go back and check for the hammerfalls. Where is the > code that sets this order? > > _J > > > --- > This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger > for complex code. Debugging C/C++ programs can leave you feeling lost and > disoriented. TotalView can help you find your way. Available on major UNIX > and Linux platforms. Try it free. www.etnus.com > ___ > Alsa-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/alsa-devel > --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] rme9652 in kernel
Hi, I built rme9652 in my kernel so that I could debug with kgdb. Unfortunately it runs rme9652 before hammerfall_mem, so it refuses to insert hammerfalls because of no memory, then it makes the memory but doesn't bother to go back and check for the hammerfalls. Where is the code that sets this order? _J --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] HDSP 9652 - Some first results, but lockups and noactual audio
Thomas, Thanks for the response. I'm wondering if the whole problem could be that I've not run amixer at all? Is this required to actually route through the mixer of the HDSP 9652? In the previous driver the mixer was disabled, but if it is now enabled, then maybe I need to learn to use amixer and not alsamixer, which worker before? Mark On Sat, 2003-04-12 at 12:37, Thomas Charbonnel wrote: > [ I'm not CC-ing anymore to Planetccrma as I am not a subscriber, and > anyway Fernando's on alsa-devel ] > > Hi, > > Just a bit more info. By rebooting and doing a couple of power cycles on > > the external A/D/D/A I have been able to get the RME to acknowledge that > > it's seeing an ADAT sync at 44.1K, so I think at least the clock is > > being sent. > > > > What do you want to do here ? See the hdsp clock reported on you > external D/A device or sync the card with the external device ? > >From your previous post I see that your external device is sending a > 48kHz clock signal to the card ADAT1 input, but the card is ignoring it > because the clock mode is set to internal 44.1kHz. > If you want the card to slave to the external device, then you should : > * set the external device to the proper rate. > * switch the card to AutoSync mode : > amixer cset numid=11 0 > If you want the external device to be slaved : > * switch the card to the appropriate rate : > amixer cset numid=11 x > (amixer cget numid=11 will give you the options for x) > * switch the external device to slave mode. > > If the problem is as I think a mixer problem the clock signal should be > received and interpreted correctly by the external device even if no > audio signal is sent. > > > This specific external unit (AI-3 for now) supports a loopback, where > > the ADAT in can be looped and sent back on its ADAT out. In doing this, > > I cannot see the audio signal I send it, implying that it is actually > > not receiving one. > > > > Also, I sent the wave file recorded using jackrec to my Windows box. (A > > copy of a Yellowjackets tune) It plays fine, so it appears that jack and > > alsaplayer are working OK. > > > > Thanks in advance again. > > > > Cheers, > > Mark > > > > On Sat, 2003-04-12 at 10:37, Mark Knecht wrote: > > > [EMAIL PROTECTED] card0]# more /proc/asound/card0/hdsp > > > RME HDSP 9652 (Card #1) > > > Buffers: capture dde0 playback ddc0 > > > IRQ: 10 Registers bus: 0xe880 VM: 0xe0967000 > > > Control register: 0x1008098 > > > Status register: 0x6086a48 > > > Status2 register: 0x8061 > > > FIFO status: 0 > > > MIDI1 Output status: 0xff00 > > > MIDI1 Input status: 0xff80 > > > MIDI2 Output status: 0xff00 > > > MIDI2 Input status: 0xff5f > > > > > > Buffer Size (Latency): 1024 samples (2 periods of 4096 bytes) > > > Hardware pointer (frames): 1024 > > > Passthru: no > > > Line out: on > > > Firmware version: 1 > > > > > > Sample Clock Source: Internal 44.1 kHz > > > Preferred Sync Reference: ADAT1 > > > AutoSync Reference: ADAT1 > > > AutoSync Frequency: 48000 > > > System Clock Mode: Master > > > System Clock Frequency: 44100 > > > > > > IEC958 input: Internal > > > IEC958 output: Coaxial only > > > IEC958 quality: Consumer > > > IEC958 emphasis: off > > > IEC958 NonAudio: off > > > IEC958 sample rate: Error flag set > > > > > > ADAT1: Lock > > > ADAT2: No Lock > > > ADAT3: No Lock > > > SPDIF: No Lock > > > Word Clock: No Lock > > > ADAT Sync: No Lock > > > > > > [EMAIL PROTECTED] card0]# > > > > > > > [EMAIL PROTECTED] mark]$ cat /proc/asound/card0/hdsp > > RME HDSP 9652 (Card #1) > > Buffers: capture de60 playback de40 > > IRQ: 10 Registers bus: 0xe880 VM: 0xe0967000 > > Control register: 0x1008090 > > Status register: 0x2040008 > > Status2 register: 0x8041 > > FIFO status: 0 > > MIDI1 Output status: 0xff00 > > MIDI1 Input status: 0xff3d > > MIDI2 Output status: 0xff00 > > MIDI2 Input status: 0xff39 > > > > Buffer Size (Latency): 64 samples (2 periods of 256 bytes) > > Hardware pointer (frames): 0 > > Passthru: no > > Line out: on > > Firmware version: 1 > > > > Sample Clock Source: Internal 44.1 kHz > > Preferred Sync Reference: ADAT1 > > AutoSync Reference: ADAT1 > > AutoSync Frequency: 44100 > > System Clock Mode: Master > > System Clock Frequency: 44100 > > > > IEC958 input: Internal > > IEC958 output: Coaxial only > > IEC958 quality: Consumer > > IEC958 emphasis: off > > IEC958 NonAudio: off > > IEC958 sample rate: Error flag set > > > > ADAT1: Sync > > ADAT2: No Lock > > ADAT3: No Lock > > SPDIF: No Lock > > Word Clock: No Lock > > ADAT Sync: No Lock > > > > [EMAIL PROTECTED] mark]$ > > > > --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etn
Re: [Alsa-devel] hdsp I/O-error
> Hi. More info. This is the /var/log/messages output when I run hdsploader. > > Apr 12 12:30:56 kiertotahti kernel: ALSA > ../../alsa-kernel/pci/rme9652/hdsp.c:4104: card initialization pending : > waiting for firmware > Apr 12 12:31:03 kiertotahti kernel: ALSA > ../../alsa-kernel/pci/rme9652/hdsp.c:644: wait for FIFO status <= 0 failed > after 30 iterations > Apr 12 12:31:03 kiertotahti kernel: ALSA > ../../alsa-kernel/pci/rme9652/hdsp.c:3800: initializing firmware upload > Apr 12 12:31:03 kiertotahti kernel: ALSA > ../../alsa-kernel/pci/rme9652/hdsp.c:522: loading firmware > Apr 12 12:31:03 kiertotahti kernel: ALSA > ../../alsa-kernel/pci/rme9652/hdsp.c:548: finished firmware loading > Apr 12 12:31:07 kiertotahti kernel: ALSA > ../../alsa-kernel/pci/rme9652/hdsp.c:644: wait for FIFO status <= 127 failed > after 5000 iterations > Apr 12 12:31:07 kiertotahti kernel: ALSA > ../../alsa-kernel/pci/rme9652/hdsp.c:3824: error creating alsa devices > > (I/O-box shows host error). Did the hardware show the typical led blinking sequence while the firmware uploaded, and then the host error, or was the host error showing from the beginning ? --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] HDSP 9652 - Some first results, but lockups andno actual audio
[ I'm not CC-ing anymore to Planetccrma as I am not a subscriber, and anyway Fernando's on alsa-devel ] > Hi, > Just a bit more info. By rebooting and doing a couple of power cycles on > the external A/D/D/A I have been able to get the RME to acknowledge that > it's seeing an ADAT sync at 44.1K, so I think at least the clock is > being sent. > What do you want to do here ? See the hdsp clock reported on you external D/A device or sync the card with the external device ? >From your previous post I see that your external device is sending a 48kHz clock signal to the card ADAT1 input, but the card is ignoring it because the clock mode is set to internal 44.1kHz. If you want the card to slave to the external device, then you should : * set the external device to the proper rate. * switch the card to AutoSync mode : amixer cset numid=11 0 If you want the external device to be slaved : * switch the card to the appropriate rate : amixer cset numid=11 x (amixer cget numid=11 will give you the options for x) * switch the external device to slave mode. If the problem is as I think a mixer problem the clock signal should be received and interpreted correctly by the external device even if no audio signal is sent. > This specific external unit (AI-3 for now) supports a loopback, where > the ADAT in can be looped and sent back on its ADAT out. In doing this, > I cannot see the audio signal I send it, implying that it is actually > not receiving one. > > Also, I sent the wave file recorded using jackrec to my Windows box. (A > copy of a Yellowjackets tune) It plays fine, so it appears that jack and > alsaplayer are working OK. > > Thanks in advance again. > > Cheers, > Mark > > On Sat, 2003-04-12 at 10:37, Mark Knecht wrote: > > [EMAIL PROTECTED] card0]# more /proc/asound/card0/hdsp > > RME HDSP 9652 (Card #1) > > Buffers: capture dde0 playback ddc0 > > IRQ: 10 Registers bus: 0xe880 VM: 0xe0967000 > > Control register: 0x1008098 > > Status register: 0x6086a48 > > Status2 register: 0x8061 > > FIFO status: 0 > > MIDI1 Output status: 0xff00 > > MIDI1 Input status: 0xff80 > > MIDI2 Output status: 0xff00 > > MIDI2 Input status: 0xff5f > > > > Buffer Size (Latency): 1024 samples (2 periods of 4096 bytes) > > Hardware pointer (frames): 1024 > > Passthru: no > > Line out: on > > Firmware version: 1 > > > > Sample Clock Source: Internal 44.1 kHz > > Preferred Sync Reference: ADAT1 > > AutoSync Reference: ADAT1 > > AutoSync Frequency: 48000 > > System Clock Mode: Master > > System Clock Frequency: 44100 > > > > IEC958 input: Internal > > IEC958 output: Coaxial only > > IEC958 quality: Consumer > > IEC958 emphasis: off > > IEC958 NonAudio: off > > IEC958 sample rate: Error flag set > > > > ADAT1: Lock > > ADAT2: No Lock > > ADAT3: No Lock > > SPDIF: No Lock > > Word Clock: No Lock > > ADAT Sync: No Lock > > > > [EMAIL PROTECTED] card0]# > > > > [EMAIL PROTECTED] mark]$ cat /proc/asound/card0/hdsp > RME HDSP 9652 (Card #1) > Buffers: capture de60 playback de40 > IRQ: 10 Registers bus: 0xe880 VM: 0xe0967000 > Control register: 0x1008090 > Status register: 0x2040008 > Status2 register: 0x8041 > FIFO status: 0 > MIDI1 Output status: 0xff00 > MIDI1 Input status: 0xff3d > MIDI2 Output status: 0xff00 > MIDI2 Input status: 0xff39 > > Buffer Size (Latency): 64 samples (2 periods of 256 bytes) > Hardware pointer (frames): 0 > Passthru: no > Line out: on > Firmware version: 1 > > Sample Clock Source: Internal 44.1 kHz > Preferred Sync Reference: ADAT1 > AutoSync Reference: ADAT1 > AutoSync Frequency: 44100 > System Clock Mode: Master > System Clock Frequency: 44100 > > IEC958 input: Internal > IEC958 output: Coaxial only > IEC958 quality: Consumer > IEC958 emphasis: off > IEC958 NonAudio: off > IEC958 sample rate: Error flag set > > ADAT1: Sync > ADAT2: No Lock > ADAT3: No Lock > SPDIF: No Lock > Word Clock: No Lock > ADAT Sync: No Lock > > [EMAIL PROTECTED] mark]$ > --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] HDSP 9652 - Some first results, but lockups andno actual audio
> post-install snd-hdsp /usr/bin/hdsploader > [EMAIL PROTECTED] etc]# > > > [EMAIL PROTECTED] etc]# hdsploader > hdsploader - firmware loader for RME Hammerfall DSP cards > Looking for HDSP + Multiface or Digiface cards : > Card 0 : RME HDSP 9652 at 0xe880, irq 10 > [EMAIL PROTECTED] etc]# > > Note that you do not need to run hdsploader with the HDSP9652 card. Note too that one wouldn't need superuser privileges for the tool to work, anyway. > > [EMAIL PROTECTED] root]# lsmod > Module Size Used byNot tainted > ide-cd 35548 0 (autoclean) > cdrom 33344 0 (autoclean) [ide-cd] > snd-mixer-oss 16536 2 (autoclean) > snd-seq-midi5280 0 (unused) > snd-seq-midi-event 5928 0 [snd-seq-midi] > snd-seq49648 0 [snd-seq-midi snd-seq-midi-event] > snd-hdsp 39212 2 > snd-pcm85888 0 [snd-hdsp] > snd-page-alloc 8452 0 [snd-pcm] > snd-timer 20776 0 [snd-seq snd-pcm] > snd-rawmidi19712 0 [snd-seq-midi snd-hdsp] > snd-seq-device 6380 0 [snd-seq-midi snd-seq snd-rawmidi] > snd-hwdep 7008 0 [snd-hdsp] > snd44836 0 [snd-mixer-oss snd-seq-midi > snd-seq-midi-event snd-seq snd-hdsp snd-pcm snd-timer snd-rawmidi > snd-seq-device snd-hwdep] > soundcore 6724 5 [snd] > snd-hammerfall-mem 2976 0 [snd-hdsp] > autofs 13588 0 (autoclean) (unused) > bcm440031136 1 > ipt_REJECT 3928 6 (autoclean) > iptable_filter 2412 1 (autoclean) > ip_tables 14904 2 [ipt_REJECT iptable_filter] > ohci1394 29224 0 (unused) > ieee1394 60044 0 [ohci1394] > mousedev5588 0 (unused) > keybdev 2912 0 (unused) > hid22148 0 (unused) > input 5824 0 [mousedev keybdev hid] > usb-uhci 27116 0 (unused) > ehci-hcd 20488 0 (unused) > usbcore79840 1 [hid usb-uhci ehci-hcd] > ext3 71808 1 > jbd53908 1 [ext3] > [EMAIL PROTECTED] root]# > > > [EMAIL PROTECTED] root]# cat /proc/interrupts >CPU0 > 0:1977701 XT-PIC timer > 1: 8743 XT-PIC keyboard > 2: 0 XT-PIC cascade > 3: 2178 XT-PIC eth0 > 8: 1 XT-PIC rtc > 9: 0 XT-PIC ehci-hcd, usb-uhci, usb-uhci, usb-uhci > 10: 57026 XT-PIC hdsp > 11: 2 XT-PIC ohci1394 > 12: 48832 XT-PIC PS/2 Mouse > 14: 13159 XT-PIC ide0 > 15: 9355 XT-PIC ide1 > NMI: 0 > LOC:1977713 > ERR: 2364 > MIS: 0 > [EMAIL PROTECTED] root]# > > > [EMAIL PROTECTED] card0]# more /proc/asound/card0/hdsp > RME HDSP 9652 (Card #1) > Buffers: capture dde0 playback ddc0 > IRQ: 10 Registers bus: 0xe880 VM: 0xe0967000 > Control register: 0x1008098 > Status register: 0x6086a48 > Status2 register: 0x8061 > FIFO status: 0 > MIDI1 Output status: 0xff00 > MIDI1 Input status: 0xff80 > MIDI2 Output status: 0xff00 > MIDI2 Input status: 0xff5f > > Buffer Size (Latency): 1024 samples (2 periods of 4096 bytes) > Hardware pointer (frames): 1024 > Passthru: no > Line out: on > Firmware version: 1 > > Sample Clock Source: Internal 44.1 kHz > Preferred Sync Reference: ADAT1 > AutoSync Reference: ADAT1 > AutoSync Frequency: 48000 > System Clock Mode: Master > System Clock Frequency: 44100 > > IEC958 input: Internal > IEC958 output: Coaxial only > IEC958 quality: Consumer > IEC958 emphasis: off > IEC958 NonAudio: off > IEC958 sample rate: Error flag set > > ADAT1: Lock > ADAT2: No Lock > ADAT3: No Lock > SPDIF: No Lock > Word Clock: No Lock > ADAT Sync: No Lock > > [EMAIL PROTECTED] card0]# > This looks good to me. The way the matrix mixer is handled for the HDSP9652 series differs from the cardbus/pci Digiface/Multiface. It looks to me like the mixer offset from the iobase is wrong. This could explain both the absence of sound and the locks. I need to put a hand on a HDSP9652 card to investigate this. Thomas --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] HDSP 9652 - Some first results, but lockups and noactual audio
Hi, Just a bit more info. By rebooting and doing a couple of power cycles on the external A/D/D/A I have been able to get the RME to acknowledge that it's seeing an ADAT sync at 44.1K, so I think at least the clock is being sent. This specific external unit (AI-3 for now) supports a loopback, where the ADAT in can be looped and sent back on its ADAT out. In doing this, I cannot see the audio signal I send it, implying that it is actually not receiving one. Also, I sent the wave file recorded using jackrec to my Windows box. (A copy of a Yellowjackets tune) It plays fine, so it appears that jack and alsaplayer are working OK. Thanks in advance again. Cheers, Mark On Sat, 2003-04-12 at 10:37, Mark Knecht wrote: > [EMAIL PROTECTED] card0]# more /proc/asound/card0/hdsp > RME HDSP 9652 (Card #1) > Buffers: capture dde0 playback ddc0 > IRQ: 10 Registers bus: 0xe880 VM: 0xe0967000 > Control register: 0x1008098 > Status register: 0x6086a48 > Status2 register: 0x8061 > FIFO status: 0 > MIDI1 Output status: 0xff00 > MIDI1 Input status: 0xff80 > MIDI2 Output status: 0xff00 > MIDI2 Input status: 0xff5f > > Buffer Size (Latency): 1024 samples (2 periods of 4096 bytes) > Hardware pointer (frames): 1024 > Passthru: no > Line out: on > Firmware version: 1 > > Sample Clock Source: Internal 44.1 kHz > Preferred Sync Reference: ADAT1 > AutoSync Reference: ADAT1 > AutoSync Frequency: 48000 > System Clock Mode: Master > System Clock Frequency: 44100 > > IEC958 input: Internal > IEC958 output: Coaxial only > IEC958 quality: Consumer > IEC958 emphasis: off > IEC958 NonAudio: off > IEC958 sample rate: Error flag set > > ADAT1: Lock > ADAT2: No Lock > ADAT3: No Lock > SPDIF: No Lock > Word Clock: No Lock > ADAT Sync: No Lock > > [EMAIL PROTECTED] card0]# > [EMAIL PROTECTED] mark]$ cat /proc/asound/card0/hdsp RME HDSP 9652 (Card #1) Buffers: capture de60 playback de40 IRQ: 10 Registers bus: 0xe880 VM: 0xe0967000 Control register: 0x1008090 Status register: 0x2040008 Status2 register: 0x8041 FIFO status: 0 MIDI1 Output status: 0xff00 MIDI1 Input status: 0xff3d MIDI2 Output status: 0xff00 MIDI2 Input status: 0xff39 Buffer Size (Latency): 64 samples (2 periods of 256 bytes) Hardware pointer (frames): 0 Passthru: no Line out: on Firmware version: 1 Sample Clock Source: Internal 44.1 kHz Preferred Sync Reference: ADAT1 AutoSync Reference: ADAT1 AutoSync Frequency: 44100 System Clock Mode: Master System Clock Frequency: 44100 IEC958 input: Internal IEC958 output: Coaxial only IEC958 quality: Consumer IEC958 emphasis: off IEC958 NonAudio: off IEC958 sample rate: Error flag set ADAT1: Sync ADAT2: No Lock ADAT3: No Lock SPDIF: No Lock Word Clock: No Lock ADAT Sync: No Lock [EMAIL PROTECTED] mark]$ --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
