deomsh Posted July 11, 2024 Posted July 11, 2024 (edited) While reading some old posts I realized we didn't try new functionality of HDA2.DLL version 9.L to select 'Codec index'. If you like, you can add some lines to HDACFG.INI. New entry [HDA] should look like this: [HDA] TSR=TSR Found PCI_VID=$8086 PCI_DID=$293E PCI_BUS=$00 PCI_DEVICE=$1B PCI_FUNCTION=$0 SEARCH=FALSE BTW first three entries are present already, so you only have to add last FOUR lines. I interpret 'PCI_FUNCTION=$0' as general codec address, but so far I am not aware of any succesfull testing of this feature. If you want to try: check after reboot if 'Codec index' changes. Edited July 11, 2024 by deomsh Typo
gab24 Posted July 11, 2024 Author Posted July 11, 2024 (edited) 3 hours ago, deomsh said: While reading some old posts I realized we didn't try new functionality of HDA2.DLL version 9.L to select 'Codec index'. If you like, you can add some lines to HDACFG.INI. New entry [HDA] should look like this: [HDA] TSR=TSR Found PCI_VID=$8086 PCI_DID=$293E PCI_BUS=$00 PCI_DEVICE=$1B PCI_FUNCTION=$0 SEARCH=FALSE BTW first three entries are present already, so you only have to add last FOUR lines. I interpret 'PCI_FUNCTION=$0' as general codec address, but so far I am not aware of any succesfull testing of this feature. If you want to try: check after reboot if 'Codec index' changes. I have added the last four line into HDACFG.INI on [HDA], but after a reboot the Codec index is the same ($2). Edited July 11, 2024 by gab24
deomsh Posted July 11, 2024 Posted July 11, 2024 And what happens if you delete these four lines and only add SEARCH=FALSE to [HDA_293E8086,3621103C] below the line PCI_FUNCTION=$0 ?
gab24 Posted July 11, 2024 Author Posted July 11, 2024 10 minutes ago, deomsh said: And what happens if you delete these four lines and only add SEARCH=FALSE to [HDA_293E8086,3621103C] below the line PCI_FUNCTION=$0 ? I have now made the modification in HDAcfg.ini, but after a reboot the Codec index is still $2.
deomsh Posted July 11, 2024 Posted July 11, 2024 Maybe I have been on the wrong track and is this function ment to set the PCI-device manually (so the HD-Audio Controller, who communicates with the codec). I did a wide internet-search on 8086:293E, always 00:1b.0 is mentioned, so same as your values. So best REMOVE lines in HDACFG.INI I suggested above. The fact that HDALOG.TXT first identifies the right codec on $0 and than switches to codec $2 can also mean a timing problem. Especially because Verbinterface=$1 didn't work on your system. Timings can be adjusted. I suggest to experiment with the wait-states in steps of 50 (msec), up to 1000 (1 second). Your current values in HDACFG.INI are: wait1=$100 wait2=$100 Best first go UP, so starting with $150 both. Check HDALOG.TXT after each reboot too.
gab24 Posted July 12, 2024 Author Posted July 12, 2024 22 hours ago, deomsh said: Maybe I have been on the wrong track and is this function ment to set the PCI-device manually (so the HD-Audio Controller, who communicates with the codec). I did a wide internet-search on 8086:293E, always 00:1b.0 is mentioned, so same as your values. So best REMOVE lines in HDACFG.INI I suggested above. The fact that HDALOG.TXT first identifies the right codec on $0 and than switches to codec $2 can also mean a timing problem. Especially because Verbinterface=$1 didn't work on your system. Timings can be adjusted. I suggest to experiment with the wait-states in steps of 50 (msec), up to 1000 (1 second). Your current values in HDACFG.INI are: wait1=$100 wait2=$100 Best first go UP, so starting with $150 both. Check HDALOG.TXT after each reboot too. I have removed this lines from HDACFG.INI on [HDA]: PCI_BUS=$00 PCI_DEVICE=$1B PCI_FUNCTION=$0 and in [HDA_293E8086,3621103C]: SEARCH=FALSE i tried all timings from 100ms - 1000ms in 50ms steps (and between a reboot). But the Codec index is still $2.
deomsh Posted July 12, 2024 Posted July 12, 2024 Sorry to hear that. In my opinion on the side of Watler's HDA-driver nothing can be done further. But how about the Setup of your laptop? Are their for instance energy-savings which can be switched off? I found some manual of your laptop, but this was not clear for me.
gab24 Posted July 12, 2024 Author Posted July 12, 2024 18 minutes ago, deomsh said: Sorry to hear that. In my opinion on the side of Watler's HDA-driver nothing can be done further. But how about the Setup of your laptop? Are their for instance energy-savings which can be switched off? I found some manual of your laptop, but this was not clear for me. No problem. Before I came to this forum, I never thought that the audio would work on my notebook. But now, thanks to your help and your skills, it works. I am happy with the ability to control the volume via HDAICOUT.HDA. i installed Windows 98 SE witout ACPI-Support (with the parameter /p i). I had to do this because otherwise I have problems with it.
deomsh Posted July 12, 2024 Posted July 12, 2024 Setup /p i is always good. On my 2011 (desktop) motherboard needed too. But I ment your laptop's BIOS setup. Are there any switches regarding energy savings or MSI?
gab24 Posted July 13, 2024 Author Posted July 13, 2024 9 hours ago, deomsh said: Setup /p i is always good. On my 2011 (desktop) motherboard needed too. But I ment your laptop's BIOS setup. Are there any switches regarding energy savings or MSI? What does MSI mean? No, I didn't find any settings in the BIOS regarding energy saving.
deomsh Posted July 13, 2024 Posted July 13, 2024 Sad. MSI is Message Signaled Interrupts (PCI-bus mechanism). Personally I do not understand them, but MSI was mentioned in a Linux source in relation to the High Definition Audio Controller. If you want to read more: https://wiki.osdev.org/PCI
gab24 Posted July 13, 2024 Author Posted July 13, 2024 4 hours ago, deomsh said: Sad. MSI is Message Signaled Interrupts (PCI-bus mechanism). Personally I do not understand them, but MSI was mentioned in a Linux source in relation to the High Definition Audio Controller. If you want to read more: https://wiki.osdev.org/PCI I didn't find anything like that in the BIOS.
deomsh Posted July 14, 2024 Posted July 14, 2024 I have done some reading in the ICH9 datasheet. It seems MSI is disabled by default. Maybe you are lucky if you enable MSI with 'pcipatchB=$6281' (if my reading/ hex-counting of Intel's io-controller-hub-9-datasheet, paragraph 18.1.27 is correct). As always: at your own risk (if any). Do not forget to study HDALOG.TXT too, if you want to try.
gab24 Posted July 14, 2024 Author Posted July 14, 2024 5 hours ago, deomsh said: I have done some reading in the ICH9 datasheet. It seems MSI is disabled by default. Maybe you are lucky if you enable MSI with 'pcipatchB=$6281' (if my reading/ hex-counting of Intel's io-controller-hub-9-datasheet, paragraph 18.1.27 is correct). As always: at your own risk (if any). Do not forget to study HDALOG.TXT too, if you want to try. I set the value at pcipatchB in HDAcfg.ini and made a copy of HDALOG.TXT. But after a restart the codec index was still at $2. There were no changes in HDALOG.TXT
deomsh Posted July 14, 2024 Posted July 14, 2024 In that case I think were done. You tried 'pcipatchB=$7900' earlier. You know what to do if you want your headphones back.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now