24 Jun
2007
24 Jun
'07
7:01 p.m.
On 12/1/06, Dave Phillips <dlphillips(a)woh.rr.com> wrote:
Bill Allen wrote:
Hi Dave and everyone. I am still wrestling with this. I have the new ALSA
driver that supports my card, finally, but under 64studio I still get
20-some xruns a second, and Audacity is unable to connect to jackd.
PortAudio appears for a split second in the jack connection dialog, and
disappears. Some of you told me 64studio was preconfigured for low-latency
audio out of the "box" and all the apps were tuned to the distro, but it
doesn't seem to work that way for me.
Anyone know an up-to-date guide to low-latency audio on Debian or Linux?
There's still a lot of info out there that is obsolete, so I'm wary of
Google.
Just a note: I have been trying for several years to get low-latency audio
working right on Linux. This is a new machine, though, as of November 06,
and I had to wait 7 months for my audio card and wireless (still not working
right) to be nominally supported, so I haven't tried much for about 6
months. I'm still amazed at how everything just seems to work without
tweaking for some folks, and I'm wondering if there's something fundamental
I'm just not doing. My problems have baffled some of the very developers
who created drivers specifically for the hardware I have. What could be
wrong?
-Chuckk
--
http://www.badmuthahubbard.com
--
http://www.badmuthahubbard.com
At the risk of repeating myself, in the time that
I've been just
reading this thread (not to mention the time that you've been putting
into trying the stuff mentioned) I could have downloaded 64Studio, set
aside a 5-10 GB partition, installed it, and had a working system with
all the real-time patched AMD64 music-enabled system that you can get.
Yes, you've got to dual boot, I do it all the time. Ubuntu is my
family system that we use for work and play, but when I want to do
music I boot into 64Studio. It's simply a lot easier than trying to
make a general purpose distro into a music enabled one.
Hear the man. I started writing a similar reply yesterday, but Bill's
said it better here. Given the availability of multimedia-optimized
distros I just don't see the point of putting myself through what the
distro maintainers have already been through and mastered. Maybe it's an
age thing, at mine I get someone else to do the heavy lifting. :)
Really, I work with Linux audio software to make music. I lost interest
in mucking about with kernel configurations long ago. Yes, I'm glad I
know how to do some of that stuff by myself, but I no longer consider it
a necessary part of the process. I agree with Bill, use 64Studio,
PlanetCCRMA, or some other optimized distro and save yourself time and
energy.
Best,
dp
24 Jun
24 Jun
7:37 p.m.
On 6/24/07, Chuckk Hubbard <badmuthahubbard(a)gmail.com> wrote:
<SNIP>
Hi Dave and everyone. I am still wrestling with this. I have the new ALSA
driver that supports my card, finally, but under 64studio I still get
20-some xruns a second, and Audacity is unable to connect to jackd.
PortAudio appears for a split second in the jack connection dialog, and
disappears. Some of you told me 64studio was preconfigured for low-latency
audio out of the "box" and all the apps were tuned to the distro, but it
doesn't seem to work that way for me.
Anyone know an up-to-date guide to low-latency audio on Debian or Linux?
There's still a lot of info out there that is obsolete, so I'm wary of
Google.
Just a note: I have been trying for several years to get low-latency audio
working right on Linux. This is a new machine, though, as of November 06,
and I had to wait 7 months for my audio card and wireless (still not working
right) to be nominally supported, so I haven't tried much for about 6
months. I'm still amazed at how everything just seems to work without
tweaking for some folks, and I'm wondering if there's something fundamental
I'm just not doing. My problems have baffled some of the very developers
who created drivers specifically for the hardware I have. What could be
wrong?
-Chuckk
Chuck,
Sorry for your problems. However there isn't enough information to
help debug the problem. We'll need hardware specifics, info on the
kernel and how it's configured, what audio card drivers are loaded &
how you are attempting to run Jack, just to start with. We'll start
with that and see where it leads.
Please provide the output from the following commands:
uname -a
lspci
cat /proc/asound/cards
lsmod
cat /proc/interrupts
and whatever info you can provide on how you are starting Jack. If you
start it in a terminal then the command will be fin. If you use
qjackctl then you can find the command in the message window.
With that we can start to get an idea about what machine you are
working with and how you have attempted to set it up. From there
possibly we can find the mistake and get you going.
good luck,
Mark
26 Jun
26 Jun
7:26 a.m.
On 6/24/07, Mark Knecht <markknecht(a)gmail.com> wrote:
On 6/24/07, Chuckk Hubbard <badmuthahubbard(a)gmail.com> wrote:
<SNIP>
Chuck,
Sorry for your problems. However there isn't enough information to
help debug the problem. We'll need hardware specifics, info on the
kernel and how it's configured, what audio card drivers are loaded &
how you are attempting to run Jack, just to start with. We'll start
with that and see where it leads.
Please provide the output from the following commands:
uname -a
lspci
cat /proc/asound/cards
lsmod
cat /proc/interrupts
Hi Mark, thanks for your reply, and sorry I didn't respond sooner. I've run
those commands, and here is my output, and the command line and its results
from qjackctl...
Thanks, I appreciate you guys taking the time to help!
-Chuckk
64studio:/mnt/win/Linux# uname -a
Linux 64studio 2.6.22-rc4.062107 #1 PREEMPT Thu Jun 21 23:28:59 EDT 2007
x86_64 GNU/Linux
64studio:/mnt/win/Linux# lspci
00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 10)
00:01.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:04.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:05.0 PCI bridge: ATI Technologies Inc Unknown device 5a37
00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller
(rev 80)
00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller
(rev 80)
00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller
(rev 80)
00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 83)
00:14.1 IDE interface: ATI Technologies Inc Standard Dual Channel PCI IDE
Controller ATI (rev 80)
00:14.2 Audio device: ATI Technologies Inc SB450 HDA Audio (rev 01)
00:14.3 ISA bridge: ATI Technologies Inc IXP SB400 PCI-ISA Bridge (rev 80)
00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-PCI Bridge (rev 80)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM
Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Miscellaneous Control
01:05.0 VGA compatible controller: ATI Technologies Inc RS482 [Radeon Xpress
200M]
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8038 PCI-E
Fast Ethernet Controller (rev 14)
05:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN
Mini-PCI Card (rev 01)
08:09.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller
08:09.1 FireWire (IEEE 1394): Texas Instruments PCIxx12 OHCI Compliant IEEE
1394 Host Controller
08:09.2 Mass storage controller: Texas Instruments 5-in-1 Multimedia Card
Reader (SD/MMC/MS/MS PRO/xD)
64studio:/mnt/win/Linux# cat /proc/asound/cards
0 [SB ]: HDA-Intel - HDA ATI SB
HDA ATI SB at 0xc0000000 irq 16
64studio:/mnt/win/Linux# lsmod
Module Size Used by
nls_iso8859_1 5568 1
ntfs 193696 1
ppdev 9608 0
parport_pc 38376 0
lp 12936 0
parport 40460 3 ppdev,parport_pc,lp
thermal 15376 0
fan 5896 0
button 9312 0
processor 26940 1 thermal
ac 6280 0
battery 11464 0
ipv6 273320 10
md_mod 80796 1
dm_snapshot 17096 0
dm_mirror 22272 0
dm_mod 60240 2 dm_snapshot,dm_mirror
snd_seq_dummy 4356 0
snd_seq_oss 32448 0
snd_seq_midi 9408 0
snd_rawmidi 27104 1 snd_seq_midi
snd_seq_midi_event 8320 2 snd_seq_oss,snd_seq_midi
snd_seq 53632 6
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_seq_device 8788 5
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
sbp2 24968 0
scsi_mod 161816 1 sbp2
joydev 11520 0
tsdev 9280 0
pcmcia 42200 0
snd_hda_intel 307808 1
snd_pcm_oss 44384 0
snd_mixer_oss 17600 1 snd_pcm_oss
pcspkr 3456 0
psmouse 40988 0
yenta_socket 27596 1
snd_pcm 87436 2 snd_hda_intel,snd_pcm_oss
snd_timer 25096 2 snd_seq,snd_pcm
bcm43xx 427808 0
firmware_class 11264 2 pcmcia,bcm43xx
rsrc_nonstatic 12096 1 yenta_socket
pcmcia_core 42844 3 pcmcia,yenta_socket,rsrc_nonstatic
serio_raw 7684 0
ohci1394 35208 0
ieee1394 99928 2 sbp2,ohci1394
rng_core 5896 1 bcm43xx
snd 61992 11
snd_seq_oss,snd_rawmidi,snd_seq,snd_seq_device,snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore 9312 1 snd
i2c_piix4 9612 0
snd_page_alloc 10576 2 snd_hda_intel,snd_pcm
i2c_core 27608 1 i2c_piix4
sky2 45256 0
ieee80211softmac 35008 1 bcm43xx
ehci_hcd 34188 0
shpchp 34076 0
ohci_hcd 22404 0
pci_hotplug 17096 1 shpchp
evdev 11136 6
64studio:/mnt/win/Linux# cat /proc/interrupts
CPU0
0: 447351 IO-APIC-edge timer
1: 555 IO-APIC-edge i8042
8: 0 IO-APIC-edge rtc
12: 6248 IO-APIC-edge i8042
14: 9543 IO-APIC-edge ide0
16: 429 IO-APIC-fasteoi eth0, HDA Intel
17: 1393 IO-APIC-fasteoi bcm43xx
19: 2 IO-APIC-fasteoi ohci_hcd:usb1, ohci_hcd:usb2,
ehci_hcd:usb3
20: 1 IO-APIC-fasteoi yenta
21: 393 IO-APIC-fasteoi acpi, ohci1394
NMI: 0
LOC: 447226
ERR: 0
====================
qjackctl messages:
05:00:06.080 Patchbay deactivated.
05:00:06.126 Statistics reset.
JACK tmpdir identified as [/dev/shm]
05:00:06.234 MIDI connection graph change.
05:00:06.358 MIDI connection change.
05:00:30.468 Startup script...
05:00:30.469 artsshell -q terminate
JACK tmpdir identified as [/dev/shm]
can't create mcop directory
Creating link /home/chuckk/.kde/socket-64studio.
05:00:31.211 Startup script terminated with exit status=256.
05:00:31.211 JACK is starting...
05:00:31.211 /usr/bin/jackd -dalsa -dhw:0 -r44100 -p1024 -n2
11:33 a.m.
Chuckk Hubbard wrote:
On 6/24/07, *Mark Knecht* <markknecht(a)gmail.com
<mailto:markknecht@gmail.com>> wrote:
On 6/24/07, Chuckk Hubbard <badmuthahubbard(a)gmail.com
<mailto:badmuthahubbard@gmail.com>> wrote:
<SNIP>
Chuck,
Sorry for your problems. However there isn't enough information to
help debug the problem. We'll need hardware specifics, info on the
kernel and how it's configured, what audio card drivers are loaded &
how you are attempting to run Jack, just to start with. We'll start
with that and see where it leads.
Please provide the output from the following commands:
uname -a
lspci
cat /proc/asound/cards
lsmod
cat /proc/interrupts
Hi Mark, thanks for your reply, and sorry I didn't respond sooner.
I've run those commands, and here is my output, and the command line
and its results from qjackctl...
Thanks, I appreciate you guys taking the time to help!
-Chuckk
64studio:/mnt/win/Linux# uname -a
Linux 64studio 2.6.22-rc4.062107 #1 PREEMPT Thu Jun 21 23:28:59 EDT
2007 x86_64 GNU/Linux
64studio:/mnt/win/Linux# lspci
00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 10)
00:01.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:04.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:05.0 PCI bridge: ATI Technologies Inc Unknown device 5a37
00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host
Controller (rev 80)
00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host
Controller (rev 80)
00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host
Controller (rev 80)
00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 83)
00:14.1 IDE interface: ATI Technologies Inc Standard Dual Channel PCI
IDE Controller ATI (rev 80)
00:14.2 Audio device: ATI Technologies Inc SB450 HDA Audio (rev 01)
00:14.3 ISA bridge: ATI Technologies Inc IXP SB400 PCI-ISA Bridge (rev 80)
00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-PCI Bridge (rev
80)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8
[Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8
[Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8
[Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8
[Athlon64/Opteron] Miscellaneous Control
01:05.0 VGA compatible controller: ATI Technologies Inc RS482 [Radeon
Xpress 200M]
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8038
PCI-E Fast Ethernet Controller (rev 14)
05:00.0 Network controller: Broadcom Corporation Dell Wireless 1390
WLAN Mini-PCI Card (rev 01)
08:09.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller
08:09.1 FireWire (IEEE 1394): Texas Instruments PCIxx12 OHCI Compliant
IEEE 1394 Host Controller
08:09.2 Mass storage controller: Texas Instruments 5-in-1 Multimedia
Card Reader (SD/MMC/MS/MS PRO/xD)
64studio:/mnt/win/Linux# cat /proc/asound/cards
0 [SB ]: HDA-Intel - HDA ATI SB
HDA ATI SB at 0xc0000000 irq 16
64studio:/mnt/win/Linux# lsmod
Module Size Used by
nls_iso8859_1 5568 1
ntfs 193696 1
ppdev 9608 0
parport_pc 38376 0
lp 12936 0
parport 40460 3 ppdev,parport_pc,lp
thermal 15376 0
fan 5896 0
button 9312 0
processor 26940 1 thermal
ac 6280 0
battery 11464 0
ipv6 273320 10
md_mod 80796 1
dm_snapshot 17096 0
dm_mirror 22272 0
dm_mod 60240 2 dm_snapshot,dm_mirror
snd_seq_dummy 4356 0
snd_seq_oss 32448 0
snd_seq_midi 9408 0
snd_rawmidi 27104 1 snd_seq_midi
snd_seq_midi_event 8320 2 snd_seq_oss,snd_seq_midi
snd_seq 53632 6
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_seq_device 8788 5
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
sbp2 24968 0
scsi_mod 161816 1 sbp2
joydev 11520 0
tsdev 9280 0
pcmcia 42200 0
snd_hda_intel 307808 1
snd_pcm_oss 44384 0
snd_mixer_oss 17600 1 snd_pcm_oss
pcspkr 3456 0
psmouse 40988 0
yenta_socket 27596 1
snd_pcm 87436 2 snd_hda_intel,snd_pcm_oss
snd_timer 25096 2 snd_seq,snd_pcm
bcm43xx 427808 0
firmware_class 11264 2 pcmcia,bcm43xx
rsrc_nonstatic 12096 1 yenta_socket
pcmcia_core 42844 3 pcmcia,yenta_socket,rsrc_nonstatic
serio_raw 7684 0
ohci1394 35208 0
ieee1394 99928 2 sbp2,ohci1394
rng_core 5896 1 bcm43xx
snd 61992 11
snd_seq_oss,snd_rawmidi,snd_seq,snd_seq_device,snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore 9312 1 snd
i2c_piix4 9612 0
snd_page_alloc 10576 2 snd_hda_intel,snd_pcm
i2c_core 27608 1 i2c_piix4
sky2 45256 0
ieee80211softmac 35008 1 bcm43xx
ehci_hcd 34188 0
shpchp 34076 0
ohci_hcd 22404 0
pci_hotplug 17096 1 shpchp
evdev 11136 6
64studio:/mnt/win/Linux# cat /proc/interrupts
CPU0
0: 447351 IO-APIC-edge timer
1: 555 IO-APIC-edge i8042
8: 0 IO-APIC-edge rtc
12: 6248 IO-APIC-edge i8042
14: 9543 IO-APIC-edge ide0
16: 429 IO-APIC-fasteoi eth0, HDA Intel
17: 1393 IO-APIC-fasteoi bcm43xx
19: 2 IO-APIC-fasteoi ohci_hcd:usb1, ohci_hcd:usb2,
ehci_hcd:usb3
20: 1 IO-APIC-fasteoi yenta
21: 393 IO-APIC-fasteoi acpi, ohci1394
NMI: 0
LOC: 447226
ERR: 0
====================
qjackctl messages:
05:00:06.080 Patchbay deactivated.
05:00:06.126 Statistics reset.
JACK tmpdir identified as [/dev/shm]
05:00:06.234 MIDI connection graph change.
05:00:06.358 MIDI connection change.
05:00:30.468 Startup script...
05:00:30.469 artsshell -q terminate
JACK tmpdir identified as [/dev/shm]
can't create mcop directory
Creating link /home/chuckk/.kde/socket-64studio.
05:00:31.211 Startup script terminated with exit status=256.
05:00:31.211 JACK is starting...
05:00:31.211 /usr/bin/jackd -dalsa -dhw:0 -r44100 -p1024 -n2
------------------------------------------------------------------------
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
No idea whether this is all the problem. Try and check the 'Realtime'
checkbox in the qjackctl settings-window and put the 'priority' value to
something like 70 - dunno why realtime is allways deactivated by default
- even in audio-distros.
make sure the -R and -P options appear in the output:
/usr/bin/jackd -R -P70 -u -dalsa -dhw:0 -r44100 -p64 -n2
There is a reasonably recend howto for building low-latency kernels on
debian here:
http://forums.debian.net/viewtopic.php?t=13123
it worked for me with a 2.6.21 kernel just yesterday, but i recommend
audio distros - lost so much time trying to do things i don't know
anything about.
Another helpful source of information is this:
http://tapas.affenbande.org/wordpress/?page_id=3
regards, d.
12:33 p.m.
Hi Chuck,
A few comments embedded below.
- MArk
On 6/26/07, Chuckk Hubbard <badmuthahubbard(a)gmail.com> wrote:
<SNIP>
64studio:/mnt/win/Linux# uname -a
Linux 64studio 2.6.22-rc4.062107 #1 PREEMPT Thu Jun 21 23:28:59 EDT 2007
x86_64 GNU/Linux
OK, running 64-bit. I do also, although I'm Gentoo.
I'm not certain from this kernel name that this is a real-time kernel.
Most of the time they include some form or '-rt' in the name. Not a
requirement that the name say -rt but if you're not running a real
time kernel then all bets are off for real time performance.
64studio:/mnt/win/Linux# lspci
<SNIP>
00:14.2 Audio device: ATI Technologies Inc SB450 HDA
Audio (rev 01)
<SNIP>
02:00.0 Ethernet controller: Marvell Technology Group
Ltd. 88E8038 PCI-E
Fast Ethernet Controller (rev 14)
05:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN
Mini-PCI Card (rev 01)
<SNIP>
OK, so you are running the Intel-HDA which lots of other folks have
had problems with. My son's machine has one and has trouble with
real-time performance although I haven't tried to fix it yet.
64studio:/mnt/win/Linux# cat /proc/asound/cards
0 [SB ]: HDA-Intel - HDA ATI SB
HDA ATI SB at 0xc0000000 irq 16
<SNIP>
OK, looking at the list above you have a *lot* of modules loaded.
Again, not necessarily a problem but when I see things like
thermal 15376 0
fan 5896 0
button 9312 0
processor 26940 1 thermal
ac 6280 0
battery 11464 0
this makes me think about power management which has caused me and
others problems with RT performance over the years. Do you need them?
At least for debugging it might be wise to not use anything you don't
absolutely need until you get to the root of the problem.
64studio:/mnt/win/Linux# cat /proc/interrupts
<SNIP>
16: 429 IO-APIC-fasteoi eth0, HDA Intel
<SNIP>
You are sharing the sound card's hardware interrupt line with a NIC.
If this is a desktop machine you might want to change the NIC's slot
and share it with something else for simplicity.
====================
qjackctl messages:
<SNIP>
Creating link /home/chuckk/.kde/socket-64studio.
05:00:31.211 Startup script terminated with exit status=256.
05:00:31.211 JACK is starting...
05:00:31.211 /usr/bin/jackd -dalsa -dhw:0 -r44100 -p1024 -n2
And finally it seems that Jack is not running with real-time turned
on. If it was I would expect to see
/usr/bin/jackd -R .......
Check how you are starting Jack in QJC. There is a button you must
push to turn on real time performance.
Also I'm thinking that someone else recently said they had to run the
Intel-HDA with variables like:
-r48000 -n3
or possibly
-r44100 n3
You should Google a bit for specifics on that. Some on-board sound
cards don't work well at all sample rates.
Hope this helps,
Mark
12:35 p.m.
On 6/26/07, Chuckk Hubbard <badmuthahubbard(a)gmail.com> wrote:
64studio:/mnt/win/Linux# cat /proc/asound/cards
0 [SB ]: HDA-Intel - HDA ATI SB
HDA ATI SB at 0xc0000000 irq 16
Well there's your problem. Maybe. Has anyone got an hda-intel setup
that works well with jack? IIRC, hda-intel is problematic in that
each manufacturer's implementation of this "standard" is different. I
could be totally wrong here though.
Also, your eth0 shares an interrupt with the hda-intel. If you unplug
eth0, does anything change?
27 Jun
27 Jun
7:16 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, Jun 26, 2007 at 10:35:20AM -0400, Paul Coccoli wrote:
On 6/26/07, Chuckk Hubbard
<badmuthahubbard(a)gmail.com> wrote:
hda-intel is, I'm told, complete shit. ALSA developers basicaly told me to forget
about it ever working right; the chip sucks and is poorly-documented. Each laptop
manufacturer implements it their own way, and doesn't document it, just hacks around
it in their proprietary drivers. Look around the ALSA list to find out more.
Also, there is nothing wrong with the ac, battery, temperature, and other ACPI modules.
In fact you may need them in order for your CPU to run safely (i.e. temperature
warnings).
It's the cpufreq stuff that you should definitely remove from the kernel. Or blacklist
it in udev/hotplug. Basically yank all the governors and run without any. There is no
governor anywhere.
64studio:/mnt/win/Linux# cat /proc/asound/cards
0 [SB ]: HDA-Intel - HDA ATI SB
HDA ATI SB at 0xc0000000 irq 16
Well there's your problem. Maybe. Has anyone got an hda-intel setup
that works well with jack? IIRC, hda-intel is problematic in that
each manufacturer's implementation of this "standard" is different. I
could be totally wrong here though.
Also, your eth0 shares an interrupt with the hda-intel. If you unplug
eth0, does anything change?
I had firewire sharing an interrupt with eth0, for a while, and no problems. I wasn't
doing heavy network activity while recording or mixing though.
- -ken
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGgiqie8HF+6xeOIcRApGkAJkB4+0aw+WEupTqmnuTq5VgSa2flwCgkb0j
Js7IsSpXrMN+ze2MDUpdZ44=
=rhby
-----END PGP SIGNATURE-----
10:15 a.m.
On 6/27/07, Ken Restivo <ken(a)restivo.org> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, Jun 26, 2007 at 10:35:20AM -0400, Paul Coccoli wrote:
cpufreq with the userspace governor controlled with powernowd works
fine here with rt and jack. As i mentioned before, buying a soundcard
that isn't crap can only help. ;)
Loki
On 6/26/07, Chuckk Hubbard
<badmuthahubbard(a)gmail.com> wrote:
hda-intel is, I'm told, complete shit. ALSA developers basicaly told me to
forget about it ever working right; the chip sucks and is poorly-documented.
Each laptop manufacturer implements it their own way, and doesn't document
it, just hacks around it in their proprietary drivers. Look around the ALSA
list to find out more.
Also, there is nothing wrong with the ac, battery, temperature, and other
ACPI modules. In fact you may need them in order for your CPU to run safely
(i.e. temperature warnings).
It's the cpufreq stuff that you should definitely remove from the kernel. Or
blacklist it in udev/hotplug. Basically yank all the governors and run
without any. There is no governor anywhere.
64studio:/mnt/win/Linux# cat /proc/asound/cards
0 [SB ]: HDA-Intel - HDA ATI SB
HDA ATI SB at 0xc0000000 irq 16
Well there's your problem. Maybe. Has anyone got an hda-intel setup
that works well with jack? IIRC, hda-intel is problematic in that
each manufacturer's implementation of this "standard" is different. I
could be totally wrong here though. >
11:23 a.m.
Am Mittwoch, 27. Juni 2007 schrieb Loki Davison:
On 6/27/07, Ken Restivo <ken(a)restivo.org>
wrote:
Some time back I decided that I don't need another userspace-tool eating
cycles when the kernel can do better. Thats why I use the powersave, ondemand
and performance governours on both my pcs. I only need to remember to use
either powersave (always minimal frequency for laptops on battery) or
performance (always maximum frequency) before starting jack.
jack bails out on changes off the cpu-frequency. So not using a governour that
changes the freq helps... And without jackd running the ondemand-governour
helps saving energy...
Arnold
--
visit http://www.arnoldarts.de/
---
Hi, I am a .signature virus. Please copy me into your ~/.signature and send me
to all your contacts.
After a month or so log in as root and do a rm / -rf. Or ask your
administrator to do so...
It's the cpufreq stuff that you should
definitely remove from the kernel.
Or blacklist it in udev/hotplug. Basically yank all the governors and run
without any. There is no governor anywhere.
cpufreq with the userspace governor
controlled with powernowd works
fine here with rt and jack. 
24 Jun
24 Jun
9:32 p.m.
New subject: Real-time kernel
Hi Chuckk,
|--==> Chuckk Hubbard writes:
CH> Hi Dave and everyone. I am still wrestling with this. I have the new ALSA
CH> driver that supports my card, finally, but under 64studio I still get
CH> 20-some xruns a second, and Audacity is unable to connect to jackd.
CH> PortAudio appears for a split second in the jack connection dialog, and
CH> disappears. Some of you told me 64studio was preconfigured for low-latency
CH> audio out of the "box" and all the apps were tuned to the distro, but
it
CH> doesn't seem to work that way for me.
What version of 64 Studio are you using? The official latest 1.0
stable release, could be out of date with respect to new hardware. You
may want to try the 1.4.0 testing release
http://www.64studio.com/node/1
and do a network upgrade against the testing repository (see the file
in /etc/apt/sources.list.d/64studio.list) to get the very latest
kernel (2.6.21-rt17)
Ciao!
Free
26 Jun
26 Jun
5:16 a.m.
New subject: Real-time kernel
On 6/24/07, Free Ekanayaka <free.ekanayaka(a)gmail.com> wrote:
Hi Chuckk,
|--==> Chuckk Hubbard writes:
CH> Hi Dave and everyone. I am still wrestling with this. I have the
new ALSA
CH> driver that supports my card, finally, but under 64studio I still
get
CH> 20-some xruns a second, and Audacity is unable to connect to jackd.
CH> PortAudio appears for a split second in the jack connection dialog,
and
CH> disappears. Some of you told me 64studio was preconfigured for
low-latency
CH> audio out of the "box" and all the apps were tuned to the distro,
but it
CH> doesn't seem to work that way for me.
What version of 64 Studio are you using? The official latest 1.0
stable release, could be out of date with respect to new hardware. You
may want to try the 1.4.0 testing release
http://www.64studio.com/node/1
and do a network upgrade against the testing repository (see the file
in /etc/apt/sources.list.d/64studio.list) to get the very latest
kernel (2.6.21-rt17)
Hi Free, thanks for the suggestion. I was told by an ALSA developer a while
back that I'd need 1.0.14. It didn't work at the time, but after I
recompiled with a 2.6.21 kernel patched up to 2.6.22 it was in there. I'll
run the commands Mark gave me and provide some more info...
Glad to see there's a testing version!
-Chuckk
--
http://www.badmuthahubbard.com
24 Jun
24 Jun
11:12 p.m.
On 6/25/07, Chuckk Hubbard <badmuthahubbard(a)gmail.com> wrote:
On 12/1/06, Dave Phillips
<dlphillips(a)woh.rr.com> wrote:
I also had problems for ages getting my soundcard to work. After a
long time i found a good solution. I bought a decent soundcard. Got
cardbus on the laptop? grab an echo cardbus thing. They are cheap on
ebay in the USA. I got my Gina3g from the USA for 200 USD. Pretty damn
cheap compared to a new guitar or bass. If you have firewire you can
try that too after looking what cards work. The cardbus is easier
though.
Loki
Bill Allen wrote:
Hi Dave and everyone. I am still wrestling with this. I have the new ALSA
driver that supports my card, finally, but under 64studio I still get
20-some xruns a second, and Audacity is unable to connect to jackd.
PortAudio appears for a split second in the jack connection dialog, and
disappears. Some of you told me 64studio was preconfigured for low-latency
audio out of the "box" and all the apps were tuned to the distro, but it
doesn't seem to work that way for me.
Anyone know an up-to-date guide to low-latency audio on Debian or Linux?
There's still a lot of info out there that is obsolete, so I'm wary of
Google.
Just a note: I have been trying for several years to get low-latency audio
working right on Linux. This is a new machine, though, as of November 06,
and I had to wait 7 months for my audio card and wireless (still not working
right) to be nominally supported, so I haven't tried much for about 6
months. I'm still amazed at how everything just seems to work without
tweaking for some folks, and I'm wondering if there's something fundamental
I'm just not doing. My problems have baffled some of the very developers
who created drivers specifically for the hardware I have. What could be
wrong?
-Chuckk
At the risk of repeating myself, in the time that
I've been just
reading this thread (not to mention the time that you've been putting
into trying the stuff mentioned) I could have downloaded 64Studio, set
aside a 5-10 GB partition, installed it, and had a working system with
all the real-time patched AMD64 music-enabled system that you can get.
Yes, you've got to dual boot, I do it all the time. Ubuntu is my
family system that we use for work and play, but when I want to do
music I boot into 64Studio. It's simply a lot easier than trying to
make a general purpose distro into a music enabled one.
Hear the man. I started writing a similar reply yesterday, but Bill's
said it better here. Given the availability of multimedia-optimized
distros I just don't see the point of putting myself through what the
distro maintainers have already been through and mastered. Maybe it's an
age thing, at mine I get someone else to do the heavy lifting. :)
Really, I work with Linux audio software to make music. I lost interest
in mucking about with kernel configurations long ago. Yes, I'm glad I
know how to do some of that stuff by myself, but I no longer consider it
a necessary part of the process. I agree with Bill, use 64Studio,
PlanetCCRMA, or some other optimized distro and save yourself time and
energy.
Best,
dp
11:59 p.m.
On 6/24/07, Loki Davison <loki.davison(a)gmail.com> wrote:
On 6/25/07, Chuckk Hubbard <badmuthahubbard(a)gmail.com> wrote:
ALSA
Thanks Loki. My soundcard works though. The wireless does not, but I'm
just posting here to find out how to improve my audio performance.
-Chuckk
On 12/1/06, Dave Phillips
<dlphillips(a)woh.rr.com> wrote:
>
> Bill Allen wrote:
>
> > At the risk of repeating myself, in the time that I've been just
> > reading this thread (not to mention the time that you've been
putting
> > into trying the stuff mentioned) I
could have downloaded 64Studio,
set
> > aside a 5-10 GB partition, installed
it, and had a working system
with
> > all the real-time patched AMD64
music-enabled system that you can
get.
> > Yes, you've got to dual boot, I do
it all the time. Ubuntu is my
> > family system that we use for work and play, but when I want to do
> > music I boot into 64Studio. It's simply a lot easier than trying to
> > make a general purpose distro into a music enabled one.
>
> Hear the man. I started writing a similar reply yesterday, but Bill's
> said it better here. Given the availability of multimedia-optimized
> distros I just don't see the point of putting myself through what the
> distro maintainers have already been through and mastered. Maybe it's
an
> age thing, at mine I get someone else to do
the heavy lifting. :)
>
> Really, I work with Linux audio software to make music. I lost
interest
> in mucking about with kernel configurations
long ago. Yes, I'm glad I
> know how to do some of that stuff by myself, but I no longer consider
it
a
necessary part of the process. I agree with Bill, use 64Studio,
PlanetCCRMA, or some other optimized distro and save yourself time and
energy.
Best,
dp
Hi Dave and everyone. I am still wrestling with this. I have the new driver that supports my card, finally, but under
64studio I still get
20-some xruns a second, and Audacity is unable to connect to jackd.
PortAudio appears for a split second in the jack connection dialog, and
disappears. Some of you told me 64studio was preconfigured for
low-latency
audio out of the "box" and all the apps
were tuned to the distro, but it
doesn't seem to work that way for me.
Anyone know an up-to-date guide to low-latency audio on Debian or Linux?
There's still a lot of info out there that is obsolete, so I'm wary of
Google.
Just a note: I have been trying for several years to get low-latency
audio
working right on Linux. This is a new machine,
though, as of November
06,
and I had to wait 7 months for my audio card and
wireless (still not
working
right) to be nominally supported, so I
haven't tried much for about 6
months. I'm still amazed at how everything just seems to work without
tweaking for some folks, and I'm wondering if there's something
fundamental
I'm just not doing. My problems have baffled
some of the very
developers
who created drivers specifically for the hardware
I have. What could be
wrong?
-Chuckk
I also had problems for ages getting my soundcard to work. After a
long time i found a good solution. I bought a decent soundcard. Got
cardbus on the laptop? grab an echo cardbus thing. They are cheap on
ebay in the USA. I got my Gina3g from the USA for 200 USD. Pretty damn
cheap compared to a new guitar or bass. If you have firewire you can
try that too after looking what cards work. The cardbus is easier
though.
25 Jun
25 Jun
12:05 a.m.
On 6/25/07, Chuckk Hubbard <badmuthahubbard(a)gmail.com> wrote:
On 6/24/07, Loki Davison
<loki.davison(a)gmail.com> wrote:
What do you mean by works really? My previous soundcard was fine for
playing mp3s but useless for recording with jack or doing anything
without xruns. New card, no problems. Works very well.
Loki
On 6/25/07, Chuckk Hubbard <badmuthahubbard(a)gmail.com> wrote:
ALSA
Thanks Loki. My soundcard works though. The wireless does not, but I'm
just posting here to find out how to improve my audio performance.
-Chuckk
On 12/1/06, Dave Phillips
<dlphillips(a)woh.rr.com> wrote:
>
> Bill Allen wrote:
>
> > At the risk of repeating myself, in the time that I've been just
> > reading this thread (not to mention the time that you've been
putting
> > into trying the stuff mentioned) I
could have downloaded 64Studio,
set
> > aside a 5-10 GB partition, installed
it, and had a working system
with
> > all the real-time patched AMD64
music-enabled system that you can
get.
> > Yes, you've got to dual boot, I do
it all the time. Ubuntu is my
> > family system that we use for work and play, but when I want to do
> > music I boot into 64Studio. It's simply a lot easier than trying to
> > make a general purpose distro into a music enabled one.
>
> Hear the man. I started writing a similar reply yesterday, but Bill's
> said it better here. Given the availability of multimedia-optimized
> distros I just don't see the point of putting myself through what the
> distro maintainers have already been through and mastered. Maybe it's
an
> age thing, at mine I get someone else to do
the heavy lifting. :)
>
> Really, I work with Linux audio software to make music. I lost
interest
> in mucking about with kernel configurations
long ago. Yes, I'm glad I
> know how to do some of that stuff by myself, but I no longer consider
it
a
necessary part of the process. I agree with Bill, use 64Studio,
PlanetCCRMA, or some other optimized distro and save yourself time and
energy.
Best,
dp
Hi Dave and everyone. I am still wrestling with this. I have the new driver that supports my card, finally, but under
64studio I still get
20-some xruns a second, and Audacity is unable to connect to jackd.
PortAudio appears for a split second in the jack connection dialog, and
disappears. Some of you told me 64studio was preconfigured for
low-latency
audio out of the "box" and all the apps
were tuned to the distro, but it
doesn't seem to work that way for me.
Anyone know an up-to-date guide to low-latency audio on Debian or Linux?
There's still a lot of info out there that is obsolete, so I'm wary of
Google.
Just a note: I have been trying for several years to get low-latency
audio
working right on Linux. This is a new machine,
though, as of November
06,
and I had to wait 7 months for my audio card and
wireless (still not
working
right) to be nominally supported, so I
haven't tried much for about 6
months. I'm still amazed at how everything just seems to work without
tweaking for some folks, and I'm wondering if there's something
fundamental
I'm just not doing. My problems have baffled
some of the very
developers
who created drivers specifically for the hardware
I have. What could be
wrong?
-Chuckk
I also had problems for ages getting my soundcard to work. After a
long time i found a good solution. I bought a decent soundcard. Got
cardbus on the laptop? grab an echo cardbus thing. They are cheap on
ebay in the USA. I got my Gina3g from the USA for 200 USD. Pretty damn
cheap compared to a new guitar or bass. If you have firewire you can
try that too after looking what cards work. The cardbus is easier
though.
26 Jun
26 Jun
5:09 a.m.
On 6/24/07, Loki Davison <loki.davison(a)gmail.com> wrote:
On 6/25/07, Chuckk Hubbard <badmuthahubbard(a)gmail.com> wrote:
Thanks Loki. My soundcard works though. The wireless does not, but I'm
just posting here to find out how to improve my audio performance.
-Chuckk
What do you mean by works really? My previous soundcard was fine for
playing mp3s but useless for recording with jack or doing anything
without xruns. New card, no problems. Works very well.
Loki
I'm glad that worked for you, but with the number of times I've been told
stuff would just work fine with no problems if I switched, and then it
hasn't, I'm not ready to believe all my problems will disappear if I go
spend more money.
-Chuckk
--
http://www.badmuthahubbard.com
On 6/24/07, Loki Davison
<loki.davison(a)gmail.com> wrote:
>
> On 6/25/07, Chuckk Hubbard <badmuthahubbard(a)gmail.com> wrote:
> > On 12/1/06, Dave Phillips <dlphillips(a)woh.rr.com> wrote:
> > >
> > > Bill Allen wrote:
> > >
> > > > At the risk of repeating myself, in the time that I've been just
> > > > reading this thread (not to mention the time that you've been
> putting
> > > > into trying the stuff mentioned) I could have downloaded
64Studio,
> set
> > > > aside a 5-10 GB partition, installed it, and had a working
system
> with
> > > > all the real-time patched AMD64 music-enabled system that you
can
> get.
> > > > Yes, you've got to dual boot, I do it all the time. Ubuntu is my
> > > > family system that we use for work and play, but when I want to
do
> > > > music I boot into 64Studio.
It's simply a lot easier than trying
to
> > > > make a general purpose distro
into a music enabled one.
> > >
> > > Hear the man. I started writing a similar reply yesterday, but
Bill's
> > > said it better here. Given the
availability of
multimedia-optimized
> > > distros I just don't see the
point of putting myself through what
the
> > > distro maintainers have already
been through and mastered. Maybe
it's
> an
> > > age thing, at mine I get someone else to do the heavy lifting. :)
> > >
> > > Really, I work with Linux audio software to make music. I lost
> interest
> > > in mucking about with kernel configurations long ago. Yes, I'm
glad I
> > > know how to do some of that stuff
by myself, but I no longer
consider
> it
> > > a necessary part of the process. I agree with Bill, use 64Studio,
> > > PlanetCCRMA, or some other optimized distro and save yourself time
and
> > > energy.
> > >
> > > Best,
> > >
> > > dp
> > >
> > >
> > Hi Dave and everyone. I am still wrestling with this. I have the
new
> ALSA
> > driver that supports my card, finally, but under 64studio I still
get
> > 20-some xruns a second, and Audacity is
unable to connect to jackd.
> > PortAudio appears for a split second in the jack connection dialog,
and
> > disappears. Some of you told me
64studio was preconfigured for
> low-latency
> > audio out of the "box" and all the apps were tuned to the distro,
but it
> > doesn't seem to work that way for
me.
> > Anyone know an up-to-date guide to low-latency audio on Debian or
Linux?
> > There's still a lot of info out
there that is obsolete, so I'm wary
of
> > Google.
> > Just a note: I have been trying for several years to get low-latency
> audio
> > working right on Linux. This is a new machine, though, as of
November
> 06,
> > and I had to wait 7 months for my audio card and wireless (still not
> working
> > right) to be nominally supported, so I haven't tried much for about
6
> > months. I'm still amazed at how
everything just seems to work
without
> > tweaking for some folks, and I'm
wondering if there's something
> fundamental
> > I'm just not doing. My problems have baffled some of the very
> developers
> > who created drivers specifically for the hardware I have. What
could
be
wrong?
-Chuckk
I also had problems for ages getting my soundcard to work. After a
long time i found a good solution. I bought a decent soundcard. Got
cardbus on the laptop? grab an echo cardbus thing. They are cheap on
ebay in the USA. I got my Gina3g from the USA for 200 USD. Pretty damn
cheap compared to a new guitar or bass. If you have firewire you can
try that too after looking what cards work. The cardbus is easier
though.
6451
days inactive
6454
days old
linux-audio-user@lists.linuxaudio.org
14 comments
8 participants
participants (8)
-
Arnold Krille -
Chuckk Hubbard -
David Adler -
Free Ekanayaka -
Ken Restivo -
Loki Davison -
Mark Knecht -
Paul Coccoli