Changes between Version 3 and Version 4 of EndUserInfo


Ignore:
Timestamp:
Sep 22, 2008, 10:48:34 PM (16 years ago)
Author:
Lewis Rosenthal
Comment:

Clarified support for pre-AC'97 cards; clarified role of experimental uniaud32.sys; added What is Uniaud? section

Legend:

Unmodified
Added
Removed
Modified
  • EndUserInfo

    v3 v4  
    55(N.B.: FAQ coming soon.)
    66
     7== What is Uniaud? ==
     8
     9Uniaud is a generic audio device driver which derives some of its functionality from the Linux [http://www.alsa.com ALSA Project]. Uniaud supports a broad range of PCI audio cards and chipsets including but not limited to [http://en.wikipedia.org/wiki/AC97 AC'97] and High Definition ([http://en.wikipedia.org/wiki/Intel_High_Definition_Audio HDA]) [http://en.wikipedia.org/wiki/Audio_codec audio codecs]. It also supports at least one ISA sound card. In fact, Uniaud supports most audio chipsets on the market.
     10
    711== Card Selection ==
    812
    913If you don't already have an audio card, or you are shopping for a system board with onboard audio, you should review our [SupportedHardware Supported Hardware Matrix].
    1014
    11 Generally, current audio cards come in two basic flavors: HDA and AC'97. HDA (High Definition Audio) is a newer spec defined by Intel in 2004 which specifically brings the ability of more sound channels at higher quality than previously available. Naturally, this new functionality requires newer hardware and software support. The Uniaud Project is making great strides to support this newer specification, but there is still much work to be done. (For more on HDA, see [http://en.wikipedia.org/wiki/Intel_High_Definition_Audio Wikipedia's page].)
     15Generally, current (new, off-the-shelf, 4th quarter, 2008) audio cards come in two basic flavors: [http://en.wikipedia.org/wiki/Intel_High_Definition_Audio HDA] and [http://en.wikipedia.org/wiki/AC97 AC'97]. HDA (High Definition Audio) is a newer spec defined by Intel in 2004 which specifically brings the ability of more sound channels at higher quality than previously available. Naturally, this new functionality requires newer hardware and software support. The Uniaud Project is making great strides to support this newer specification, but there is still much work to be done.
    1216
    13 Non-HDA hardware in recent years has made use of the AC'97 codec, also released by Intel, but back in 1997 (see [http://en.wikipedia.org/wiki/AC97 here] for more specifics). Uniaud has fairly good support for AC'97 devices.
     17Non-HDA hardware in recent years has made use of the AC'97 codec developed by [http://en.wikipedia.org/wiki/Intel_Architecture_Labs Intel Architecture Labs] in 1997. Uniaud has fairly good support for AC'97 devices.
    1418
    15 Creative Labs Sound Blaster Audigy cards seem to present their own set of problems for Uniaud and under Linux, for [http://www.alsa.com/ ALSA] (on which much of Uniaud is based). If you would like to help with the debugging effort on this hardware, then please feel free. Just be warned that you may be in for a bumpy ride before getting pleasant tones to your ears.
     19Pre-AC'97 cards are also generally supported, including at least one ISA card. If you have an older system with 16-bit ISA slots, or a newer one which does indeed have one, Uniaud may just work for you.
    1620
    17 So, in order of ease of use, one would likely choose:
     21Creative Labs Sound Blaster Audigy SE cards seem to present their own set of problems for Uniaud and under Linux, for [http://www.alsa.com/ ALSA] (on which much of Uniaud is based). If you would like to help with the debugging effort on this hardware, then please feel free. Just be warned that you may be in for a bumpy ride before getting pleasant tones to your ears. (Note that the original Audigy cards are fairly well supported.)
     22
     23So, for brand new cards, and in order of ease of use, one would likely choose:
    1824
    1925  1. AC'97 based devices
    20   2. HDA based devices or Sound Blaster (the latter is probably less likely to result in a system hang, but more likely to currently result in no sound)
     26  2. HDA based devices or Sound Blaster Audigy SE (the latter is probably less likely to result in a system hang, but more likely to currently result in no sound)
    2127
    2228== Driver Selection ==
     
    2531
    2632  1. A non-HDA build of Uniaud, currently at the 1.1.4 RC6 level, and available [ftp://ftp.netlabs.org/pub/uniaud/uniaud114RC6.zip here], or
    27   2. The above overlaid with the latest HDA-enabled component (uniaud32.sys), currently at the 1.9.6 level (see [VersioningInfo Versioning Info] for more details), which is available [http://download.smedley.info/uniaud32-1.9.6.zip here].
     33  2. The above overlaid with the latest (experimental) HDA-enabled uniaud32.sys, currently at the 1.9.6 level (see [VersioningInfo Versioning Info] for more details), which is available [http://download.smedley.info/uniaud32-1.9.6.zip here].
    2834
    2935== Basic Installation: Common ==
     
    3541== Installing HDA Support ==
    3642
    37 To provide HDA support, you should download the HDA component as mentioned above. Unzip the distribution to a safe location, peruse the readme, and copy uniaud32.sys on top of the one previously installed in your \MMOS2 directory. Once this is done, as an added precaution, you may want to disable system sounds (these have been known to cause hangs as the desktop comes up, presumably due to the overlapping of them as one event follows quickly after the other). Shut down and reboot (the driver must be loaded from CONFIG.SYS, so merely restarting the desktop will not produce the desired effect).
     43To provide HDA support, you should download the (experimental) HDA-enabled uniaud32.sys as mentioned above. Unzip the distribution to a safe location, peruse the readme, and copy uniaud32.sys on top of the one previously installed in your \MMOS2 directory. Once this is done, as an added precaution, you may want to disable system sounds (these have been known to cause hangs as the desktop comes up, presumably due to the overlapping of them as one event follows quickly after the other). Shut down and reboot (the driver must be loaded from CONFIG.SYS, so merely restarting the desktop will not produce the desired effect).
    3844
    3945== Troubleshooting ==