24 Sep
2004
24 Sep
'04
8:44 p.m.
I'm now the proud owner of a Delta 1010LT. Unfortunately getting it to
run on Linux is proving a chore. So far I've googled a big (maybe I'm a
useless googler), and looked at the alsa-project website
So from those things I figured I would do the following...
modified my /etc/modules.d/alsa file to this
_____________________________________________________
# Alsa 0.9.X kernel modules' configuration file.
# $Header:
/home/cvsroot/gentoo-x86/media-sound/alsa-driver/files/alsa-modules.conf-rc,v
1.1 2002/12/21 06:31:52 agenkin Exp $
# ALSA portion
alias char-major-116 snd
# OSS/Free portion
alias char-major-14 soundcore
##
## IMPORTANT:
## You need to customise this section for your specific sound card(s)
## and then run `update-modules' command.
## Read alsa-driver's INSTALL file in /usr/share/doc for more info.
##
## ALSA portion
alias snd-card-0 snd-ice1712
# OSS/Free portion - card #1
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
alias /dev/mixer snd-mixer-oss
alias /dev/dsp snd-pcm-oss
alias /dev/midi snd-seq-oss
# Set this to the correct number of cards.
options snd cards_limit=1
_________________________________________
Run the following command
#modprobe snd-ice1712;modprobe snd-pcm-oss;modprobe
snd-mixer-oss;modprobe snd-seq-oss
________________________________________
made a .asoundrc file with the following in it
pcm.ice1712 {
type hw
card 0
}
ctl.ice1712 {
type hw
card 0
}
Simple version just so I can get some playback
_______________________________________
I did the whole modules-update and restart of alsa (yes I'm using Gentoo)
I get this error when I try to run aplay
root@upstairs glenn # aplay -D ice1712 test.wav
ALSA lib pcm.c:1972:(snd_pcm_open_noupdate) Unknown PCM ice1712
aplay: main:507: audio open error: No such file or directory
_______________________________________
Basically I've just been trying to follow this
http://alsa-project.org/alsa-doc/doc-php/template.php?company=Midiman&c…
I was using a Soundblaster Live! and wanted a 1010LT with the purpose of
doing live multitrack recording with Ardour. Please tell me I can do it
because that was the main purpose of buying the card in the first place.
Cheers for any direction pointing.
Glenn
24 Sep
24 Sep
9:14 p.m.
On Sat, 2004-09-25 at 13:27, Glenn McCord wrote:
Run the following command
#modprobe snd-ice1712;modprobe snd-pcm-oss;modprobe
snd-mixer-oss;modprobe snd-seq-oss
modprobe handles module dependancies automatically, you only need to
modprobe snd-ice1712. (And not even that if the boot procedure runs the
alsasound script)
________________________________________
made a .asoundrc file with the following in it
pcm.ice1712 {
type hw
card 0
}
ctl.ice1712 {
type hw
card 0
}
Simple version just so I can get some playback
_______________________________________
I did the whole modules-update and restart of alsa (yes I'm using Gentoo)
I get this error when I try to run aplay
root@upstairs glenn # aplay -D ice1712 test.wav
ALSA lib pcm.c:1972:(snd_pcm_open_noupdate) Unknown PCM ice1712
aplay: main:507: audio open error: No such file or directory
You said that you made an .asoundrc file. Did you make it for root, and
is it in root's homedir? (I'm presuming you're trying to run it as root
from the command prompt).
The error message seems to be coming from alsa not recognizing the name
ice1712, and it should recognize it if the .asoundrc is correct.
btw. A better place than ~/.asoundrc is /etc/asound.conf . That file is
the global (for all users) configuration file.
If this doesn't get you ahead, try running "lsmod" and see if
snd-ice1712 comes up on the list.
When you get the device running, don't forget to use envy24control to
set your levels.
Sampo
9:25 p.m.
On Saturday 25 September 2004 03:27 am, Glenn McCord wrote:
I'm now the proud owner of a Delta 1010LT.
Unfortunately getting it to
run on Linux is proving a chore. So far I've googled a big (maybe I'm a
useless googler), and looked at the alsa-project website
So from those things I figured I would do the following...
modified my /etc/modules.d/alsa file to this
_____________________________________________________
# Alsa 0.9.X kernel modules' configuration file.
# $Header:
/home/cvsroot/gentoo-x86/media-sound/alsa-driver/files/alsa-modules.conf-rc
,v 1.1 2002/12/21 06:31:52 agenkin Exp $
# ALSA portion
alias char-major-116 snd
# OSS/Free portion
alias char-major-14 soundcore
##
## IMPORTANT:
## You need to customise this section for your specific sound card(s)
## and then run `update-modules' command.
## Read alsa-driver's INSTALL file in /usr/share/doc for more info.
##
## ALSA portion
alias snd-card-0 snd-ice1712
# OSS/Free portion - card #1
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
alias /dev/mixer snd-mixer-oss
alias /dev/dsp snd-pcm-oss
alias /dev/midi snd-seq-oss
# Set this to the correct number of cards.
options snd cards_limit=1
I would have just run alsaconf as su...but I think this looks ok...
_________________________________________
Run the following command
#modprobe snd-ice1712;modprobe snd-pcm-oss;modprobe
snd-mixer-oss;modprobe snd-seq-oss
________________________________________
made a .asoundrc file with the following in it
pcm.ice1712 {
type hw
card 0
}
ctl.ice1712 {
type hw
card 0
}
Simple version just so I can get some playback
_______________________________________
I did the whole modules-update and restart of alsa (yes I'm using Gentoo)
I get this error when I try to run aplay
root@upstairs glenn # aplay -D ice1712 test.wav
ALSA lib pcm.c:1972:(snd_pcm_open_noupdate) Unknown PCM ice1712
aplay: main:507: audio open error: No such file or directory
1010LT has 8 analogue ins and outs...it does not know which to send to here??
Also, get the Envy24control app for your alsa version. It's a "must have"
for
the Delta 1010. You will also need to adjust levels for the seperate
channels.
_______________________________________
Basically I've just been trying to follow this
http://alsa-project.org/alsa-doc/doc-php/template.php?company=Midiman&c…
Delta+1010-LT&chip=Envy24&module=ice1712#opt
I was using a Soundblaster Live! and wanted a 1010LT with the purpose of
doing live multitrack recording with Ardour. Please tell me I can do it
because that was the main purpose of buying the card in the first place.
Have no fear...you can do all that and MUCH more. I had the same transitional
plan you did...and I'm VERY happy withj my 1010LT.
I use a distro that has rpms and alsa is built into the kernel so I'm not
sure. It looks to me like oyur starting from scratch with alsa...
Also, at the bottom of that alsa page there's some .asoundrc examples...the
one for the "hoontech" works well. It shows 10 ins and 12 outs which is odd
but it does give you your multi channel functionality.
Cheers
Cheers for any direction pointing.
Glenn
25 Sep
25 Sep
1:04 a.m.
<>
Have no fear...you can do all that and MUCH more. I had the same
transitional
plan you did...and I'm VERY happy withj my 1010LT.
I use a distro that has rpms and alsa is built into the kernel so I'm not
sure. It looks to me like oyur starting from scratch with alsa...
Also, at the bottom of that alsa page there's some .asoundrc
examples...the
one for the "hoontech" works well. It shows 10 ins and 12 outs which
is odd
but it does give you your multi channel functionality.
Okay, so I've done all that and the card can record and playback with
ardour and jack. However xmms is packing a sad. It comes up with that
all to familiar dialog box saying taht I should check if the correct
output is selected, that no program is blocking the soundcard, or that
the soundcard is configured properly. If I change the output to OSS
instead of ALSA, it works but I'm sure I should be able to get that
thing working with alsa.
To make matters worse, a small tragedy is unfolding on my Linux box.
Once upon a time with my SB Live! I could have hundreds of programs
running, playing, doing whatever and I would never ever get a single
xrun. I don't know what I have done lately, whether it was from
upgrading to xorg or having two soundcards in one machine but now I get
xruns all over the show. Jack doesn't cut ardour out anymore but there
is all the clipping and popping in the recording.
I have spent countless hours getting xruns to go away. To have them
mysteriously show up again is such a <enter really violent expletive
here>. I even went from xorg 6.8 to 6.7 to xfree86 just to see if that
got rid of them. I went back to the SB Live! and they were still there.
I have 1GB free and no other settings bar the ones mentioned in this
thread have changed and now I may as well count 3 days of my life gone
when I get around to fixing it again. <sigh>
Anyhow, would having two cards in the machine be screwing things up? Has
anyone got some advice to get xmms to use alsa?
I'm a gentooer by the way. There aint too much stuff about 1010LTs on
the forums.
Cheers,
Glenn
6:07 a.m.
On Friday 24 September 2004 07:47 pm, Glenn McCord wrote:
What settings in jack?
<>
Have no fear...you can do all that and MUCH more. I had the same
transitional
plan you did...and I'm VERY happy withj my 1010LT.
I use a distro that has rpms and alsa is built into the kernel so I'm not
sure. It looks to me like oyur starting from scratch with alsa...
Also, at the bottom of that alsa page there's some .asoundrc
examples...the
one for the "hoontech" works well. It shows 10 ins and 12 outs which
is odd
but it does give you your multi channel functionality.
Okay, so I've done all that and the card can record and playback with
ardour and jack. However xmms is packing a sad. It comes up with that
all to familiar dialog box saying taht I should check if the correct
output is selected, that no program is blocking the soundcard, or that
the soundcard is configured properly. If I change the output to OSS
instead of ALSA, it works but I'm sure I should be able to get that
thing working with alsa.
To make matters worse, a small tragedy is unfolding on my Linux box.
Once upon a time with my SB Live! I could have hundreds of programs
running, playing, doing whatever and I would never ever get a single
xrun. I don't know what I have done lately, whether it was from
upgrading to xorg or having two soundcards in one machine but now I get
xruns all over the show. Jack doesn't cut ardour out anymore but there
is all the clipping and popping in the recording.
I have spent countless hours getting xruns to go away. To have them
mysteriously show up again is such a <enter really violent expletive
here>. I even went from xorg 6.8 to 6.7 to xfree86 just to see if that
got rid of them. I went back to the SB Live! and they were still there.
I have 1GB free and no other settings bar the ones mentioned in this
thread have changed and now I may as well count 3 days of my life gone
when I get around to fixing it again. <sigh>
Graphics are the biggest killer for system rescources AFAIK but it could be
kernel stuff too...maybe
Anyhow, would having two cards in the machine be screwing things up? Has
anyone got some advice to get xmms to use alsa?
adding another pci device can change your irq's around...
try /dev/proc/interrupts and see where your 1010LT is. Needs to be preferably
not on shared irq and with only like rtc, system stuff before it.
I'm a gentooer by the way. There aint too much stuff about 1010LTs on
the forums.
Cheers,
Glenn
11:20 a.m.
Russell Hanaghan wrote:
The thing is, I've always used KDE with multiple windows going and
verbose messages scrolling down consoles and I managed to tweak
everything to work perfectly. I can't see how the kernel could get upset
over a new PCI card. All the audio specific things get turned off in a
2.4.26 setup.
Is this good?
root@upstairs glenn # cat /proc/interrupts
CPU0
0: 16024 XT-PIC timer
1: 198 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 4389 XT-PIC ICE1712
8: 2 XT-PIC rtc
9: 0 XT-PIC acpi, usb-ohci, usb-ohci
11: 10635 XT-PIC eth0, nvidia
12: 6789 XT-PIC PS/2 Mouse
14: 10827 XT-PIC ide0
15: 19 XT-PIC ide1
NMI: 0
ERR: 0
On Friday 24 September 2004 07:47 pm, Glenn McCord
wrote:
What settings in jack?
jackstart -v -R -d alsa -d hw:0
Yeah, I know I have optimistic settings but it has worked flawlessly
until now.
<>
Have no fear...you can do all that and MUCH more. I had the same
transitional
plan you did...and I'm VERY happy withj my 1010LT.
I use a distro that has rpms and alsa is built into the kernel so I'm not
sure. It looks to me like oyur starting from scratch with alsa...
Also, at the bottom of that alsa page there's some .asoundrc
examples...the
one for the "hoontech" works well. It shows 10 ins and 12 outs which
is odd
but it does give you your multi channel functionality.
Okay, so I've done all that and the card can record and playback with
ardour and jack. However xmms is packing a sad. It comes up with that
all to familiar dialog box saying taht I should check if the correct
output is selected, that no program is blocking the soundcard, or that
the soundcard is configured properly. If I change the output to OSS
instead of ALSA, it works but I'm sure I should be able to get that
thing working with alsa.
To make matters worse, a small tragedy is unfolding on my Linux box.
Once upon a time with my SB Live! I could have hundreds of programs
running, playing, doing whatever and I would never ever get a single
xrun. I don't know what I have done lately, whether it was from
upgrading to xorg or having two soundcards in one machine but now I get
xruns all over the show. Jack doesn't cut ardour out anymore but there
is all the clipping and popping in the recording.
I have spent
countless hours getting xruns to go away. To have them
mysteriously show up again is such a <enter really violent expletive
here>. I even went from xorg 6.8 to 6.7 to xfree86 just to see if that
got rid of them. I went back to the SB Live! and they were still there.
I have 1GB free and no other settings bar the ones mentioned in this
thread have changed and now I may as well count 3 days of my life gone
when I get around to fixing it again. <sigh>
Graphics are the biggest killer for system rescources AFAIK but it could be
kernel stuff too...maybe
Anyhow, would
having two cards in the machine be screwing things up? Has
anyone got some advice to get xmms to use alsa?
adding another pci device can change your irq's around...
try /dev/proc/interrupts and see where your 1010LT is. Needs to be preferably
not on shared irq and with only like rtc, system stuff before it.
I'm a
gentooer by the way. There aint too much stuff about 1010LTs on
the forums.
Cheers,
Glenn
11:41 a.m.
On Sun, 26 Sep 2004 01:03:19 +1200
Glenn McCord <clari_player(a)paradise.net.nz> wrote:
Is this good?
No, it's not.
root@upstairs glenn # cat /proc/interrupts
CPU0
0: 16024 XT-PIC timer
1: 198 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 4389 XT-PIC ICE1712
8: 2 XT-PIC rtc
9: 0 XT-PIC acpi, usb-ohci, usb-ohci
11: 10635 XT-PIC eth0, nvidia
12: 6789 XT-PIC PS/2 Mouse
14: 10827 XT-PIC ide0
15: 19 XT-PIC ide1
Here's the order of interrupt priority on a non-APIC machine:
0, 1, 8, 9, 10, 11, 12, 13, 14, 15, 3, 4, 5, 6, 7
0 is the highest priority
7 is the lowest priority
5 is way down on the list, just about everything else has priority
over it. I have a Delta 1010, and rarely run into xruns. My IRQs are:
xtc:~% cat /proc/interrupts
CPU0
0: 2947127195 XT-PIC timer
1: 796739 XT-PIC keyboard
2: 0 XT-PIC cascade
8: 1 XT-PIC rtc
9: 12759493 XT-PIC ICE1712
10: 195005487 XT-PIC eth0, nvidia
12: 13312679 XT-PIC PS/2 Mouse
14: 180887 XT-PIC ide0
15: 1987385 XT-PIC ide1
I've turned off the USB ports on my machine as well as acpi, which handles
OS-directed configuration and power management.
--
======================================================================
Joe Hartley - UNIX/network Consultant - jh(a)brainiac.com
Without deviation from the norm, "progress" is not possible. - FZappa
12:06 p.m.
Great, that's good help and a useful link
As it turned out I did the most noob thing ever and was forgetting to
type in -R so I had
jackstart -v -d alsa -d hw:0 instead of
jackstart -v -R -d alsa -d hw:0
It's 1:30am here and that's when I noticed. I typed it out wrong right
from the onset and was using the consoles history to execute it. As a
result I never noticed the absence of the -R!
So now I have good recording power again but xmms still packs a sad.
I'll try out the IRQ thing tomorrow (or is that today?)
Thanks, everyone.
Joe Hartley wrote:
On Sun, 26 Sep 2004 01:03:19 +1200
Glenn McCord <clari_player(a)paradise.net.nz> wrote:
Is this good?
No, it's not.
root@upstairs glenn # cat /proc/interrupts
CPU0
0: 16024 XT-PIC timer
1: 198 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 4389 XT-PIC ICE1712
8: 2 XT-PIC rtc
9: 0 XT-PIC acpi, usb-ohci, usb-ohci
11: 10635 XT-PIC eth0, nvidia
12: 6789 XT-PIC PS/2 Mouse
14: 10827 XT-PIC ide0
15: 19 XT-PIC ide1
Here's the order of interrupt priority on a non-APIC machine:
0, 1, 8, 9, 10, 11, 12, 13, 14, 15, 3, 4, 5, 6, 7
0 is the highest priority
7 is the lowest priority
5 is way down on the list, just about everything else has priority
over it. I have a Delta 1010, and rarely run into xruns. My IRQs are:
xtc:~% cat /proc/interrupts
CPU0
0: 2947127195 XT-PIC timer
1: 796739 XT-PIC keyboard
2: 0 XT-PIC cascade
8: 1 XT-PIC rtc
9: 12759493 XT-PIC ICE1712
10: 195005487 XT-PIC eth0, nvidia
12: 13312679 XT-PIC PS/2 Mouse
14: 180887 XT-PIC ide0
15: 1987385 XT-PIC ide1
I've turned off the USB ports on my machine as well as acpi, which handles
OS-directed configuration and power management.
12:20 p.m.
On Sun, 26 Sep 2004 01:50:03 +1200
Glenn McCord <clari_player(a)paradise.net.nz> wrote:
So now I have good recording power again but xmms
still packs a sad.
I'll try out the IRQ thing tomorrow (or is that today?)
Good luck! It took me a while to tweak things to where I got a stable
system, but now that I do, I love it! The Delta 1010's an amazing piece
of gear.
--
======================================================================
Joe Hartley - UNIX/network Consultant - jh(a)brainiac.com
Without deviation from the norm, "progress" is not possible. - FZappa
2:56 p.m.
Just FYI - in the latest Musician's Friend they have the 1010LT on sale
for $219US.
Jan
On Sat, 2004-09-25 at 09:03, Joe Hartley wrote:
On Sun, 26 Sep 2004 01:50:03 +1200
Glenn McCord <clari_player(a)paradise.net.nz> wrote:
So now I have good recording power again but xmms
still packs a sad.
I'll try out the IRQ thing tomorrow (or is that today?)
Good luck! It took me a while to tweak things to where I got a stable
system, but now that I do, I love it! The Delta 1010's an amazing piece
of gear.
2:55 p.m.
You definitely want to turn off acpi. I didn't turn USB off since I use
it fro uploading pictures from my camera. Try moving the 1010LT card
around to see if you can get it on IRQ 9 or 10 by itself. I have almost
the same setup and I have:
CPU0
0: 15340768 XT-PIC timer
1: 6854 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 0 XT-PIC usb-uhci, usb-uhci
8: 1 XT-PIC rtc
10: 33774 XT-PIC ICE1712
11: 1858859 XT-PIC eth0, nvidia
12: 351739 XT-PIC PS/2 Mouse
14: 627800 XT-PIC ide0
15: 1548341 XT-PIC ide1
It took me a few tries to get it to this point. Note that I don't have
anything on IRQ 9. I was unable to get it there but since I got IRQ 10
for my card it's OK.
Jan
On Sat, 2004-09-25 at 08:23, Joe Hartley wrote:
On Sun, 26 Sep 2004 01:03:19 +1200
Glenn McCord <clari_player(a)paradise.net.nz> wrote:
Is this good?
No, it's not.
root@upstairs glenn # cat /proc/interrupts
CPU0
0: 16024 XT-PIC timer
1: 198 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 4389 XT-PIC ICE1712
8: 2 XT-PIC rtc
9: 0 XT-PIC acpi, usb-ohci, usb-ohci
11: 10635 XT-PIC eth0, nvidia
12: 6789 XT-PIC PS/2 Mouse
14: 10827 XT-PIC ide0
15: 19 XT-PIC ide1
Here's the order of interrupt priority on a non-APIC machine:
0, 1, 8, 9, 10, 11, 12, 13, 14, 15, 3, 4, 5, 6, 7
0 is the highest priority
7 is the lowest priority
5 is way down on the list, just about everything else has priority
over it. I have a Delta 1010, and rarely run into xruns. My IRQs are:
xtc:~% cat /proc/interrupts
CPU0
0: 2947127195 XT-PIC timer
1: 796739 XT-PIC keyboard
2: 0 XT-PIC cascade
8: 1 XT-PIC rtc
9: 12759493 XT-PIC ICE1712
10: 195005487 XT-PIC eth0, nvidia
12: 13312679 XT-PIC PS/2 Mouse
14: 180887 XT-PIC ide0
15: 1987385 XT-PIC ide1
I've turned off the USB ports on my machine as well as acpi, which handles
OS-directed configuration and power management. 
6:04 p.m.
On Sat, 2004-09-25 at 12:52, Jan Depner wrote:
You definitely want to turn off acpi. I didn't
turn USB off since I use
it fro uploading pictures from my camera. Try moving the 1010LT card
around to see if you can get it on IRQ 9 or 10 by itself. I have almost
the same setup and I have:
CPU0
0: 15340768 XT-PIC timer
1: 6854 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 0 XT-PIC usb-uhci, usb-uhci
8: 1 XT-PIC rtc
10: 33774 XT-PIC ICE1712
11: 1858859 XT-PIC eth0, nvidia
12: 351739 XT-PIC PS/2 Mouse
14: 627800 XT-PIC ide0
15: 1548341 XT-PIC ide1
It took me a few tries to get it to this point. Note that I don't have
anything on IRQ 9. I was unable to get it there but since I got IRQ 10
for my card it's OK.
Actually, you should probably leave it alone. The important thing is
not which IRQ it's on, it's more important that the IRQ not be shared.
Once you start moving PCI cards around you might have a hard time
getting the system to put the sound card on a non-shared IRQ.
The interrupt priorities mentioned by the previous poster are not a big
deal here. I believe these only determine which interrupt the CPU sees
first if they happen to fire at the *exact* same time. But, Linux
allows interrupts to nest (aka to interrupt other interrupts). So, even
if you get a USB and a soundcard interrupt at the exact same time and
the processor sees the USB one first, the soundcard interrupt will
literally interrupt the USB interrupt handler. So interrupts are
serviced immediately, even if the system is alreasy handling another
interrupt. Anyway, this is all a matter of nanoseconds or microseconds,
not enough to affect audio latency.
ACPI can definitely cause problems, but if it seems to be working,
there's no reason to disable it.
Lee
26 Sep
26 Sep
10:53 a.m.
I also just set up my delta1010 and have been experiencing
similar problems.
My IRQ setup looks like this:
[root@Katanya jos]# cat /proc/interrupts
CPU0
0: 155588356 XT-PIC timer
1: 11683 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 23383 XT-PIC usb-uhci, usb-uhci, ICE1712
8: 1 XT-PIC rtc
9: 6 XT-PIC acpi, ohci1394, usb-uhci
11: 385494 XT-PIC ehci_hcd, eth0, Intel 82801DB-ICH4
12: 908490 XT-PIC PS/2 Mouse
14: 511812 XT-PIC ide0
15: 2422 XT-PIC ide1
NMI: 0
ERR: 0
From previous info on this thread, it looks like my card is
in, like, the *worst* possible position. And my little Ice Cube
P4 box only has one PCI slot, and the Delta1010 is in it.
Joe Hartley wrote:
I've turned off the USB ports on my machine as
well as acpi,
which handles OS-directed configuration and power management.
Then Lee Revell wrote:
The interrupt priorities mentioned by the previous
poster are
not a big deal here. I believe these only determine which
interrupt the CPU sees first if they happen to fire at the
*exact* same time. But, Linux allows interrupts to nest
(aka to interrupt other interrupts). So, even
if you get a USB and a soundcard interrupt at the exact same time and
the processor sees the USB one first, the soundcard interrupt will
literally interrupt the USB interrupt handler. So interrupts are
serviced immediately, even if the system is alreasy handling another
interrupt. Anyway, this is all a matter of nanoseconds or
microseconds, not enough to affect audio latency.
ACPI can definitely cause problems, but if it seems to be working,
there's no reason to disable it.
Since moving my card is not an option, and I'd really like to
keep my USB functional, I'm wondering if anybody has any advice
on how to tweak my particular system?
Thanks for any help.
~Jos~
12:04 p.m.
On Sat, 25 Sep 2004 15:47:25 -0400
Lee Revell <rlrevell(a)joe-job.com> wrote:
Actually, you should probably leave it alone. The
important thing is
not which IRQ it's on, it's more important that the IRQ not be shared.
[ snip ]
The interrupt priorities mentioned by the previous poster are not a big
deal here. I believe these only determine which interrupt the CPU sees
first if they happen to fire at the *exact* same time.
I respectfully disagree; the IRQ is very important to the system!
There's a ton of detail why at http://www.pcguide.com/ref/mbsys/res/irq/func.htm
It's worth noting that many motherboards have a way of assigning IRQs
to particular slots in the BIOS. That might be what you need to get IRQ 9
assigned to the sound card. If the 1010 is at 5, which is often used
for the parallel port, just about every other peripheral will be ahead
of it, taking precedence.
--
======================================================================
Joe Hartley - UNIX/network Consultant - jh(a)brainiac.com
Without deviation from the norm, "progress" is not possible. - FZappa
12:26 p.m.
On Sun, 26 Sep 2004 09:47:47 -0400
Joe Hartley <jh(a)brainiac.com> wrote:
I respectfully disagree; the IRQ is very important to
the system!
There's a ton of detail why at
http://www.pcguide.com/ref/mbsys/res/irq/func.htm
It's worth noting that many motherboards have a way of assigning IRQs
to particular slots in the BIOS. That might be what you need to get
IRQ 9 assigned to the sound card. If the 1010 is at 5, which is often
used for the parallel port, just about every other peripheral will be
ahead of it, taking precedence.
My bios is especially weird. It assigns irq 5 to my soundcard no
matter what slot it is in. But if i insert an scsi adapter it then gets
irq 5 no matter what slot and the soundcard gets irq3 no matter what
slot. So it seems to assign irq's based on the device class or
something. And since 3 and 5 are rather low priority irq's i kinda
dislike it.
http://roht.informatik.uni-halle.de/~ladischc/pic_priorities.html
might help if you use an XT-PIC [dunno if it's safe to use on recent
kernels, etc..]. Just tried it and it didn't do anything bad to my
system [seemingly].
http://roht.informatik.uni-halle.de/~ladischc/ioapic_priorities.html
for APIC systems [don't work with 2.6.x kernels according to author]
flo
27 Sep
27 Sep
1:26 p.m.
Joe Hartley wrote:
On Sat, 25 Sep 2004 15:47:25 -0400
Lee Revell <rlrevell(a)joe-job.com> wrote:
Since I was one of the original folks bringing attention to this subject
I'd like to try and clear up a couple of things, if possible, and if
not, then make them a little muddier.
1) Interrupt priorities have been a problem since the days of DOS and
slow computers. However Linux is not DOS, computers are much faster, and
things probably work better today. That said, better does not generally
mean perfect and some sound thinking on the part of the user is usually
time well spent.
2) If someone is having consistent sound problems with their card is it
almost certanly *not* an interrupt problem. Consistent sound problems
are most generally wrong/bad drivers, bad levels, or something else
which is hosed up way to much for interrupts to make a difference.
3) In a lightly loaded system with a good kernel a good sound card will
probably run fine on any interrupt. (At least with higher latencies)
After all, if there are no competing interrupts then your sound card is
the first *active* interrupt. The hardware can certainly handle this easily.
4) Interrupt positioning makes the biggest difference for systems that
experience an occasional problem. An occasional xrun can be difficult to
track down. It might be caused by some other interrupt source delaying
system access to the sound card, or possibly something else entirely. We
don't know and probably will never know, so we adjust priorities in
favor of the sound card since we don't know what else to do. In my
experience this helps. (While this experience is mostly under Windows, I
freely shared when we started talking about this topic. Take it for what
it's worth.)
5) None of these numbers apply to APIC based systems, but I beleive the
*logic* of the problem still does. The processor can only work on one
task at a time. Interrupts help direct the processor to work on a
certain high-priority task. Adjusting your interrupts to make the sound
card higher priority can only help. It can't hurt. That said it may not
solve your problems. Unofrtunately today we seem to have no tools to
optimize interrupts in APIC based systems. This is disapointing and I
hope it will change some day.
In a perfect world adjusting priorities would be the last thing you'd
do, and then only when somethign didn't work well. It would be nice to
just plug the card in and have it work. However, they don't and it's
very disappointing (to me anyway) to try using your system for a long
period of time and then to have to tear it apart to move cards later on.
I'd rather do it once. For this reason, and really only for this reason,
I suggest trying to get your card on a 'good' interrupt early on as it
saves you having to mess things up later. That said, if the rest of the
system has problems then interrupt priorities won't fix those.
Don't know if this clarifies or obscures. Take it for what it's worth,
or more reasonably, what you paid for it.
cheers,
Mark
Actually, you should probably leave it alone. The
important thing is
not which IRQ it's on, it's more important that the IRQ not be shared.
[ snip ]
The interrupt priorities mentioned by the previous poster are not a big
deal here. I believe these only determine which interrupt the CPU sees
first if they happen to fire at the *exact* same time.
I respectfully disagree; the IRQ is very important to the system!
There's a ton of detail why at http://www.pcguide.com/ref/mbsys/res/irq/func.htm
It's worth noting that many motherboards have a way of assigning IRQs
to particular slots in the BIOS. That might be what you need to get IRQ 9
assigned to the sound card. If the 1010 is at 5, which is often used
for the parallel port, just about every other peripheral will be ahead
of it, taking precedence.
3:11 p.m.
New subject: [linux-audio-user] Getting the Echo Mona Laptop to work
Hi all,
I'm trying to get my Echo Mona Laptop card to work, and I've done a lot
of progress thanks to Giuliano Pochini and Ivica Ivo Bukvic, but I'm not
there yet.
The alsa drivers written by Giuliano Pochini, though not currently part
of alsa cvs, are reported to be working for the PCI version of the card.
Echo (the manufacturer) has assured there is no difference in their
windows dirver for the pci card and the pcimcia card, so the linux
drivers should work for the PCMCIA card as well.
The current state:
-My machine recognizes the card properly as (using lspci):
04:00.0 Multimedia controller: Motorola: Unknown device 3410 (rev 01)
When hotplugging the card, the drivers are called correctly, but midway
through loading, there is an error, and the drivers halt. The strange
thing when loading is that the card reports a different serial number
each time the card is loaded. This points to a data corruption problem
somewhere.
This problem looks a lot like a problem discussed in the past on this
list for the Hammerfall PCMCIA card, where people (Ivica in particular)
were having trouble with the Cardbus bridge registers. The problem was
solved by manually changing those registers.
I apparently have the same problem, since the registers for windows are
different for the registers on linux (I checked the registers using
hexdump -v /proc/bus/pci/02/01.0).
The registers are similar but have something like 15 values that differ.
I tried changing the registers manually using setpci, but the problem is
that when changing some values, other values I had already changed
reverted to their old values, and some values could not be changed at all.
So my questions are:
Should the registers for windows and linux be exactly the same or is it
normal to have variations?
How can I force the registers for the cardbus bridge to take on the
values I get on windows?
Thanks very much,
Andrés
PD. Here are the registers for windows:
00=4C 01=10 02=42 03=AC 04=07 05=00 06=10 07=02
08=00 09=00 0A=07 0B=06 0C=08 0D=20 0E=82 0F=00
10=00 11=E0 12=EF 13=FF 14=A0 15=00 16=00 17=02
18=02 19=03 1A=03 1B=20 1C=00 1D=D0 1E=EF 1F=FF
20=00 21=D0 22=EF 23=FF 24=00 25=80 26=FF 27=F4
28=00 29=70 2A=FF 2B=F8 2C=00 2D=EE 2E=00 2F=00
30=FC 31=EE 32=00 33=00 34=00 35=ED 36=00 37=00
38=FC 39=ED 3A=00 3B=00 3C=0B 3D=01 3E=00 3F=04
40=28 41=10 42=D4 43=00 44=01 45=00 46=00 47=00
48=00 49=00 4A=00 4B=00 4C=00 4D=00 4E=00 4F=00
50=00 51=00 52=00 53=00 54=00 55=00 56=00 57=00
58=00 59=00 5A=00 5B=00 5C=00 5D=00 5E=00 5F=00
60=00 61=00 62=00 63=00 64=00 65=00 66=00 67=00
68=00 69=00 6A=00 6B=00 6C=00 6D=00 6E=00 6F=00
70=00 71=00 72=00 73=00 74=00 75=00 76=00 77=00
78=00 79=00 7A=00 7B=00 7C=00 7D=00 7E=00 7F=00
80=21 81=D0 82=24 83=30 84=00 85=06 86=00 87=00
88=81 89=00 8A=0F 8B=00 8C=02 8D=30 8E=03 8F=05
90=C0 91=A6 92=64 93=60 94=00 95=00 96=00 97=00
98=00 99=00 9A=00 9B=00 9C=00 9D=00 9E=00 9F=00
A0=01 A1=00 A2=12 A3=FE A4=00 A5=00 A6=C0 A7=00
A8=00 A9=00 AA=00 AB=00 AC=00 AD=00 AE=00 AF=00
B0=00 B1=00 B2=00 B3=00 B4=00 B5=00 B6=00 B7=00
B8=00 B9=00 BA=00 BB=00 BC=00 BD=00 BE=00 BF=00
C0=00 C1=00 C2=00 C3=00 C4=00 C5=00 C6=00 C7=00
C8=00 C9=00 CA=00 CB=00 CC=00 CD=00 CE=00 CF=00
D0=00 D1=00 D2=00 D3=00 D4=00 D5=00 D6=00 D7=00
D8=00 D9=00 DA=00 DB=00 DC=00 DD=00 DE=00 DF=00
E0=00 E1=00 E2=00 E3=00 E4=00 E5=00 E6=00 E7=00
E8=00 E9=00 EA=00 EB=00 EC=00 ED=00 EE=00 EF=00
F0=00 F1=00 F2=00 F3=00 F4=00 F5=00 F6=00 F7=00
F8=00 F9=00 FA=00 FB=00 FC=00 FD=00 FE=00 FF=00
and for linux (notice you have to switch the order of the pairs):
0000000 104c ac42 0007 0210 0000 0607 a808 0082
0000010 1000 2000 00a0 0200 0400 b004 0000 2040
0000020 f000 207f 0000 2080 f000 20bf 4000 0000
0000030 40fc 0000 4400 0000 44fc 0000 01ff 0700
0000040 1028 00d4 0001 0000 0000 0000 0000 0000
0000050 0000 0000 0000 0000 0000 0000 0000 0000
0000060 0000 0000 0000 0000 0000 0000 0000 0000
0000070 0000 0000 0000 0000 0000 0000 0000 0000
0000080 f021 3024 0600 0000 0081 000f 3002 0503
0000090 a6c0 6064 0000 0000 0000 0000 0000 0000
00000a0 0001 fe12 8000 00c0 0000 0000 0000 0000
00000b0 0000 0000 0000 0000 0000 0000 0000 0000
00000c0 0000 0000 0000 0000 0000 0000 0000 0000
00000d0 0000 0000 0000 0000 0000 0000 0000 0000
00000e0 0000 0000 0000 0000 0000 0000 0000 0000
00000f0 0000 0000 0000 0000 0000 0000 0000 0000
See registers: 0D, 10,12,13, 18,19, 1B, 1A, 1E,1F,
21,23,23, 25, 26,27, 29,2A,2B,2D, 31, 35, 39, 3C, 3F,
81, A5
28 Sep
28 Sep
7:46 a.m.
Hi!
I have a delta 1010lt, and had a lot of problems first. We couldn't really
solve them. We suspected that a slot was damaged and we just plugged it into
another slot, and from that day on my card runs perfectly. I think it is even
syharing its irq with my ethernet card. So if not tried already, do try to
change the slot. And another thing is: Don't use any alsa driver before 0.9.6
for your card. There was a bug - or more than one -, but this was mainly
solved in 0.9.6. But for good dshare, dmix and so on, better take 1.0.x
drivers.
Btw.: If you're looking for a nice .asoundrc for your card, when it's up and
running, drop a note.
I hope that hleps in any way!
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net - the Linux TextBased Studio guide
9:04 a.m.
Julien Claassen wrote:
Hi!
I have a delta 1010lt, and had a lot of problems first. We couldn't really
solve them. We suspected that a slot was damaged and we just plugged it into
another slot, and from that day on my card runs perfectly. I think it is even
syharing its irq with my ethernet card. So if not tried already, do try to
change the slot. And another thing is: Don't use any alsa driver before 0.9.6
for your card. There was a bug - or more than one -, but this was mainly
solved in 0.9.6. But for good dshare, dmix and so on, better take 1.0.x
drivers.
Btw.: If you're looking for a nice .asoundrc for your card, when it's up and
running, drop a note.
Yes please. That will come in very handy.
I hope that hleps in any way!
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net - the Linux TextBased Studio guide
I still have some niggling questions...
1. When I start the machine and try and run jackstart, it complains that
the device in busy. I end up doing a # /etc/init.d/alsasound restart
in order to fix it.
2. I'm sure I used to be able to have jack running and be able to use
other sound apps at the same time. i.e I could have jack running for
ardour and then be able to use xmms at the same time. Instead I get this
glenn@upstairs glenn $ xmms
** WARNING **: alsa_setup_mixer(): Failed to find mixer element: PCM
ALSA lib pcm_hw.c:1155:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed:
Device or resource busy
** WARNING **: alsa_setup(): Failed to open pcm device (default): Device
or resource busy
3. Trying to run fluidsynth will only work if I use it with alsa rather
than through jack. It gives this error when I have xmms going
glenn@upstairs glenn $ fluidsynth -a alsa -m alsa_seq
/usr/share/sfbank/4gmgsmt.sf2
fluidsynth: warning: Failed to pin the sample data to RAM; swapping is
possible.
ALSA lib pcm_hw.c:1155:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed:
Device or resource busy
fluidsynth: error: The "default" audio device is used by another application
Failed to create the audio driver
As a side note. fluidsyth seems to totally butcher the midi. Even with
the same soundfont, fluidsyth never sounds like it does with a
soundblaster Live! using sfxload.
My 1010LT works, it's just a nuisance to have to tweak around all the
discrepencies that are cropping up. I'm sure I must have had two sound
apps running at the same time once before.
Thanks,
Glenn
3 Oct
3 Oct
7:20 p.m.
Hi!
It seems you got no answer to all your other questions. So here are some
propositions:
Do you have another audio server (artsd etc.) running? This comes along with
guis.
Is your alsa running in the first place? Check at /proc/asound for more
details about driver state.
Fluidsynth: I only use it with jack (I still use 1.0.3, I don't know about
the latest version and the drivers...)
How did you start your jack before? I start it:
jackd -R -d alsa -d hw:3,0 -r 44100 (my card is 4th card in the system, only
nominally :-))
If you do it like that, all channels on your delta would be busy. If you can
define good pcm-devices (vai .asoundrc) you could only block part of your
channels. (I didn't manage that).
Try to check a few of these things... I hope I didn't tell you all the
things you knew already. If there are more specific questions, try the
alsa-user oder jack-mailingslists, they'd know more.
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net - the Linux TextBased Studio guide
7144
days inactive
7153
days old
linux-audio-user@lists.linuxaudio.org
19 comments
11 participants
participants (11)
-
Andres Cabrera -
Florian Schmidt -
Glenn McCord -
Jan Depner -
Joe Hartley -
Jos Laake -
Julien Claassen -
Lee Revell -
Mark Knecht -
Russell Hanaghan -
Sampo Savolainen