Opened 9 years ago

Last modified 9 years ago

#198 new defect

Initialization failed: codec is not ready > hang during boot

Reported by: thomabrown Owned by:
Priority: normal Milestone: ALSA Hardware Compatibility
Component: UNIAUD32 Version: 1.9.24
Severity: normal Keywords:


About 10% of the time, when I boot my main system (usually a cold boot), I get the following:


Universal Audio Driver for OS/2 and eComStation v1.9.24-SVNr542 Based on ALSA 1.0.21 Copyright 2005-2010 Netlabs Copyright 2000-2010 The ALSA Project

ERROR: Initialization failed OSS32_Initialize. FAILED<3>codec_ready: codec is not ready [0x700100]


OS/2 Universal Audio MMPM/2 Driver v1.9.5-SVNr534 Copyright 2000-2002 Innotek Systemberatung GmbH Copyright 2002 IBM Corporation Maintained by Netlabs

Unable to attach 32-bit driver SYS1201: The device driver H:\MMOS2\UNIAUD16.SYS specified in the DEVICE statement on line 217 of the CONFIG.SYS fiel was not installed. Line 217 is ignored. Press Enter to continue...

Pressing Enter does not good. I usually have to power cycle the machine. I have the feeling that if I have booted Windows first, this does not happen, but I have not kept any records of this.

Hardware: Tyan S2895 Thunder K8WE motherboard 2 x AMD Opteron 275 dual core CPUs 2 GiB RAM

eCS 2.0 Silver

Bldlevel: [h:\mmos2]bldlevel uniaud16.sys Build Level Display Facility Version 6.12.675 Sep 25 2001 (C) Copyright IBM Corporation 1993-2001 Signature: @#Netlabs:1.9#@##1## 22 Sep 2010 11:36:43 DAZAR1 ::::5::SVNr534@@Universal A udio MMPM/2 Driver for eComStation Vendor: Netlabs Revision: 1.09 Date/Time?: 22 Sep 2010 11:36:43 Build Machine: DAZAR1 FixPak? Version: SVNr534 File Version: 1.9.5 Description: Universal Audio MMPM/2 Driver for eComStation

[h:\mmos2]bldlevel uniaud32.sys Build Level Display Facility Version 6.12.675 Sep 25 2001 (C) Copyright IBM Corporation 1993-2001 Signature: @#Netlabs:1.9#@##1## 22 Sep 2010 11:53:22 DAZAR1 :1.0.21:::24::SVNr542@@Univ ersal Audio Driver for OS/2 and eComStation (ACPI) Vendor: Netlabs Revision: 1.09 Date/Time?: 22 Sep 2010 11:53:22 Build Machine: DAZAR1 ASD Feature ID: 1.0.21 FixPak? Version: SVNr542 File Version: 1.9.24 Description: Universal Audio Driver for OS/2 and eComStation (ACPI)


PCI: Bus 0 (PCI Express), Device Number 4, Device Function 0

Vendor 10DEh Nvidia Corp Device 0059h nForce4 AC'97 Audio Controller Command 0007h (I/O Access, Memory Access, BusMaster?) Status 00B0h (Has Capabilities List, Supports 66MHz,

Supports Back-To-Back Trans., Fast Timing)

Revision A2h, Header Type 00h, Bus Latency Timer 00h Minimum Bus Grant 02h, Maximum Bus Latency 05h Self test 00h (Self test not supported) PCI Class Multimedia, type Audio Subsystem ID 289510F1h Unknown Subsystem Vendor 10F1h Tyan Computer Address 0 is an I/O Port : 1800h..18FFh Address 1 is an I/O Port : 1400h..14FFh Address 2 is a Memory Address (0-4GiB) : C8002000h..C8002FFFh System IRQ 23, INT# A New Capabilities List Present:

Power Management Capability, Version 1.1

Supports low power State D1 Supports low power State D2 Does not support PME# signalling Current Power State : D0 (Device operational, no power saving)

[w:\tmp\down\netlabs\uniaud\not_ready]type alsahlp$ Uniaud32 version 1.9.24-SVNr542 <6>intel8x0_measure_ac97_clock: measured 51000 usecs (2480 samples)

<6>intel8x0: clocking to 47381

00-00: Intel ICH : NVidia CK804

: playback 1 : capture 1

00-01: Intel ICH - MIC ADC : NVidia CK804 - MIC ADC

: capture 1

00-02: Intel ICH - IEC958 : NVidia CK804 - IEC958

: playback 1

OSS32_WaveOpen: open error: -19

OSS32_WaveOpen: open error: -19

OSS32_Initialize: SUCCESS. Cards=1 U16: Uniaud16 v1.9.5-SVNr534 Midi Open 2 failed with error -19 Midi Open 3 failed with error -19 Couldn't find OPL3 device

What can I do to test or help debug this?


Change History (1)

comment:1 Changed 9 years ago by dazarewicz

  1. You could try the newer version of uniaud32: Version 1.9.25
  2. You could try the beta version of uniaud32: Version 2.1.2
  3. You could install the debug version of Uniaud32 (either one but probably 1.9.25) On a boot when you get the initialization failure, run UniLog?.cmd and attach the log to this ticket. If the system won't fully boot, you cannot capture a useful log. If you capture a log after a boot where there is no failure, you cannot capture a useful log.
Note: See TracTickets for help on using tickets.