ATI IXP SB4x0 [1002:437b] HDA failed to get vendor and revision parameters

[siarzhuk]

Current version of HDA driver (hrev35333) cannot work with the following audio hardware:

device Multimedia controller (Audio device) [4|3|0]
  vendor 1002: ATI Technologies Inc
  device 437b: IXP SB4x0 High Definition Audio Controller 

Observed behavior:

1. No corresponding entry is in the Media Preferences.
   

2. The system boot syslog report following info about the HDA initialization:
   

HDA: Detected controller @ PCI:0:20:2, IRQ:3, type 1002/437b (1462/725a)
IRA: publish_devices
IRA: find_device
loaded driver /boot/system/add-ons/kernel/drivers/dev/audio/hmulti/hda
hda: HDA v1.0, O:4/I:4/B:0, #SDO:1, 64bit:yes
hda: Failed to get vendor and revision parameters
hda: no active codec
hda: ERROR: No such device(-2147454969)

Feel free to ask for more required information, testing etc.

[siarzhuk]

Some news here: this behaviour is observed in case Haiku was loaded in VESA mode. In case of normal boot there are much more HDA traces in the syslog. Unfortunately it is not possible to check the sound functionality because of lack of graphics support on this hardware. :-D I'll put mentioned graphics problem in separate ticked and lock current one as blocked by it.

But why the HDA function can be dependent on graphics hardware at all?

[siarzhuk]

Blocked by #1729. Until that ticket will be not fixed on my hardware it is not possible to check audio functions in normal Haiku session. Using fail-safe video mode bring the audio hardware in "hda: no active codec" state.

[siarzhuk]

(In #1729) Replying to axeld:

I have the following graphics hardware on one of our PCs:

device Display controller (VGA compatible controller, VGA controller) [3|0|0]
  vendor 1002: ATI Technologies Inc
  device 5a61: RC410 [Radeon Xpress 200]

This is normal PC with onboard graphics with external LCD Monitor attached to VGA output.

I observe the above described behavior with hrev35333. Just after the system finishes coloring all boot icons the monitor first display an "Invalid signal range" message for one second than goes to "No signal" state. It is only possible to boot with fail-safe video mode.

What happens if you press "Command + Control + Escape" after a while?

No effect on the screen but lot of tracing in the debug output. Look into attached softdc-07-2.log for details after "sync: device 3 couldn't sync: Operation not supported" line. Yes, I have pressed Alt-Ctrl-Esc and Ctrl-Alt-Esc twice. :-)

Also, if that doesn't help, can you log into the system, and execute the following application?

The specific of this PC is that there is the only possibility to load Haiku - booting from the Live-CD. I have compiled this "DPMS reset" program but with "return 1;" and replaced the /boot/system/bin/ReadOnlyBootPrompt with it's executable. ;-) I do this just to automaticaly force it to be started during loading Live-CD session. Unfortunately that doesn't help to switch the display on.

[siarzhuk]

(In #1729) Doesn't our Track handle mid-air collisions???? That's bad. :-(

[siarzhuk]

Note the debug output for booting Haiku on this hardware in normal mode: ​http://dev.haiku-os.org/attachment/ticket/1729/softdc-07-2.log There are much more HDA tracing than booting with fail-safe graphics.

[pulkomandy]

Removing HDA audio tickets from Beta2 milestone, no one has worked on it and opensound is available at least as a stopgap.

[korli]

Please check with hrev53923 or newer.

[korli]

no feedback, closing.