On 6/27/07, Ken Restivo <ken@email-addr-hidden> wrote:
> -----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@email-addr-hidden> 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.
>
>
> 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.
>
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
> >
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@email-addr-hidden
http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
Received on Wed Jun 27 16:15:04 2007
This archive was generated by hypermail 2.1.8 : Wed Jun 27 2007 - 16:15:04 EEST