Jump to content

Audio driver for Realtek HD Audio Hardware? [Testing thread]


Recommended Posts

Posted

Thank you for your hard work, but alas no sound in win98. With this HDAICOUT version I do hear a pop at windows startup, so I guess it's on the right path, but no sound in windows. No sound after reboot from windows XP either, but the pop at startup is still there.

The internal speaker doesn't work, not in WinXP either, now that you mentioned it, I will look at it to see why.

 

Hdaicin.982 Hdaicin.XP2


Posted (edited)

Thanks for the log's.

I hope the pop you hear does mean that the HDA-controller is working with HDA2.DLL in Windows 98, otherwise things will become more complicated.

After analyzing HDAICIN.982/XP2 I found that your jack is connected to Port E  (Node ID 1D). Because there is (currently?) no speaker to deal with, I will concentrate on your headphones.

I made a print-screen of the playback part of the Functional Block Diagram of VT1708B:

VT1708BPlaybackcircuitry.png.d0b82d1ac2814ec06a5ec72c21fae527.png

In HDAICOUT_DEBUG_VT1708B.HDA I tried to:

1) fully 'open' the playback path from AOW0 (Node ID 10 = DAC0) to Mixer MW0 (Node ID 16) to Port D (Node ID 1C);

2) switch input of Port E (Node ID 1D) to AOW3 (Node ID 25 = DAC3), surpassing the mixer.

I was not sure about which Port (Node ID) was connected to the headphone jack. Earlier the Headphone Amplifier of Port D (Node ID 1C) was activated after reboot from XP (and NOT Node ID 1D).

I overlooked maybe AOW3 (Node ID 25) is connected to Stream_3 (I usually set DAC's to Stream 0). Apart from the picture, numbering of streams is mentioned nowhere in the datasheet! My 'GET' Verb in first DEBUG-version gave Stream 0 in the response.

I set AOW3 (Node ID 25) as connected to Stream 3 in the second DEBUG-version, together with some other changes I want to examine.
Please try, I will need HDAICIN.983 and if needed HDAICIN.XP3. Please listen carefully and report everything you can hear.

BTW make sure HDAICIN.983 is made after a VERY cold boot and not after shutting the computer down from Windows XP. With 'very cold boot' I mean shutting down your thin client, remove the power cable, press the power-on switch a few times and wait at least 2 minutes. Of course this is not applicable to the VERY warm reboot needed from Windows XP.

HDAICOUT_DEBUG2_VT1708B.HDA

Edit:

I wrote 'I usually set DAC's to Stream 0', but this is not true, my memory must have been playing tricks om me, I usually set DAC's to Stream 1 (but not this time). :whistle:

Intel's High Definition Audio Specification (Rev 1.0a on page 160): 'Although the link is capable of transmitting any stream 
number, by convention stream 0 is reserved as unused so that converters whose stream numbers 
have been reset to 0 do not unintentionally decode data not intended for them.
' Not earlier mentioned in this thread. :dubbio:

Edited by deomsh
Correction
Posted

The speaker is broken, I don't have a replacement on hand. I tried the new version of debug.

Very cold boot no pop, no sound. Reboot from XP, pop but no sound, tried several times, same behavior.

Hdaicin.983 Hdaicin.XP3

Posted

Interesting the 'Very cold boot no pop'. Can be a HDA-controller problem, but also that Stream 3 is not used by HDA2.DLL?

Next version, should work at least with warm reboot from Windows XP. But we come closer and closer to the same settings as used in my quasi-universal HDAICOUT.HDA, only specified on Node/ Widget level.

In an 'Alsa Information Script' containing VT1708B was mentioned 'enable_msi : 0', so on the level of the the HDA-controller. I looked in the ICH7 datasheet, it seems that MSI is enabled by default in the High Definition Audio Controller Registers. So disabling MSI with pcipatchB=$6200 is worth a try.

But as always: writing to chipset registers is at your own risk (if any).

Please try next version of HDAICOUT.HDA with the HDACFG.INI-value of:

pcipatchB=$0000

pcipatchB=$7900

pcipatchB=$6200

I don't need any log's for now, only your ears and (good) skills handling the files.

HDAICOUT_DEBUG3_VT1708B.HDA

Posted

The setting in HDACFG.INI was pcipatchB=$7900 for all the tests you told me so far. Tried the new version, results are as follows.

1. Off state to W98 with pcipatchB=$7900 - pop, no sound, reboot from XP, extremely faint pop but no sound.

2. Off state to W98 with pcipatchB=$0000 - pop, no sound, reboot from XP, no pop, no sound. Perhaps there was a pop, but I didn't pick it up.

3. Off state to W98 with pcipatchB=$6200 - pop, no sound, reboot from XP, extremely faint pop but no sound.

4 I did try again with HDAICOUT.HDA.000 with reboot from XP to have sound with all 3 pcipatchB settings, all work the same, I have sound. What I did notice with this one, that I didn't pick it up before, is, there is a double pop at startup.

Posted (edited)

Thanks a lot for your observations!

Maybe 'Stream 0' is simply the wrong stream. In your post from March, 4 I saw from HDAICIN.TXT I probably was using 'Stream 1' in that version of HDAICOUT.HDA.

To be sure, can you please upload after starting Windows XP the latest HDAICOUT.HDA, HDAICIN.TXT, HDALOG.TXT and HDACFG.INI from your Windows directory in your Windows 98SE installation? So latest WITH sound after reboot from Windows XP.

Edited by deomsh
Typo
Posted (edited)

Thanks. I checked everything.

Please try debug-version.

IF this version gives sound in your Windows 98SE installation, you can try in HDACFG,INI:

SleepingWidget=$10
VolumeWidget=$1D
OutputWidget=$10

If VolumeWidget is right, WAVEOUT.EXE should be working too.

I'd would like to see HDAICIN.TXT of VERY cold Windows 98 boot afterwards.

HDAICOUT_DEBUG4_VT1708B.HDA

Edited by deomsh
Typo
Posted

EUREKA....it works, volume adjust as well. THANK YOU so much, seems to be working very well so far, it is late, I will test more tomorrow.

 

HDAICIN.TXT

Posted

Good to hear.

I made a normal version of HDAICOUT.HDA for VT1708B with minimum number of verbs. 

I removed the GET-verbs and commented out Node ID 25, can be activated again at any time (and by switching the Selector Widget in Node ID 1D, or by enabling Input 5 in Node ID 16). 

Node ID 1C is still active, so a Speaker connected to that node can be driven. 

DAC0 at Node ID 10 is set to to Stream 1/ Channel 0 and 44.1kHz/ 16-bits. The commented-out verb just below is for switching to 48kHz/ 16-bits.

Headphone-amplifier is enabled for Node ID 1D, if this gives noise, switch to normal output (Commented-out verb just below).

I added Power Up verbs to all remaining nodes, just in case a laptop-user with codec VT1708B wants to try.

 I hope this (hopefully) final version is still working.

HDAICOUT_VT1708B.HDA.000

 

Posted

Wow....such a small file compared to the others, just 1.75k. It works, I listened to several MP3's on it. Thank You! If there's anything I can help you with, just let me know.

Too bad there isn't a project to create a universal audio driver or network driver for win9x, like Universal VBE. I have on this thin client UVBE for video, a dos driver for network and a win3.x driver for audio. Maybe with time.

Posted (edited)

Thanks for testing. As such we are done.

Actually there are a few loose ends I'd like to now about your system.

First is regarding wait-states in HDACFG.INI.

Defaults are:

wait1=$100

wait2=$100

I you have some spare time please test both wait1 and wait2 with following values: $80, $60, $40, $20 - until you are experiencing some sort of problems. If $20 is still good, then go on with $15, $10 and $5. Even lower better in steps of '1'. Always reboot Windows in between.

Also there is a (possible) reward: the lower the shorter you have to 'wait' during starting Windows (in my experience).

 

Edited by deomsh
Typo
Posted (edited)

does anyone have hdaicout.hda for alc887 chip (use for h81m-k asus mobo)?

Or i can use alc883 instead?

Edited by Phuc Truong

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...