VOGONS


First post, by theamtrakvirus

User metadata
Rank Newbie
Rank
Newbie

So after a nightmare trying to get Windows XP (32 bit) installed on my Alienware M17x r1, I managed to get it almost fully working... except for sound. At first I tried the default driver Snappy Driver Installer gave me for it but that would just give me code 10 errors no matter what and not work at all. I tried a number of different drivers I found searching around supposedly working on XP but only 1-2 actually would even install. Eventually I tried a couple others in SDI that would finally get rid of the code 10 error but then I encountered a completely different issue now. The sound will not route through the inbuilt speakers on the laptop. It will route through the headphone jack fine and when I boot into a live operating system (such as Hiren's Boot CD x64 which has a startup chime) the speakers work fine so I know it's not a hardware issue. I've tried plugging and unplugging a pair of headphones both at the desktop and with a game running to try and get it to recognize the speakers but it doesn't work. With headphones it works perfectly fine so I'm fairly certain the driver is doing what it's supposed to do, but these drivers seem a bit... crap for lack of a better term. The ones I've gotten working seem to treat it as a desktop and not a laptop going off what software it comes with shows so I'm not sure if that's part of the issue or not. I don't really want to install 64 bit xp on here since I'd like to retain compatibility with older things if I want to run them if I can absolutely avoid it.

Reply 1 of 5, by giantclam

User metadata
Rank Member
Rank
Member

I can only offer some background, as I've been through this before, on linux, wrt (intel) HDA audio codecs ....basically, it's the mixer. In linux, one can use modules options (model='xxxx' or a character array to initialize mixer elements correctly)....

The ones I've gotten working seem to treat it as a desktop and not a laptop

Roughly correct, but it's actually worse than that ~ many desktop mainboards (same audio codec but different brands) have differing mixer initializations ...ie; works on an Asus board, doesn't work on a Gigabyte ... even though both mobo's employ the same chipset & audio codec...

With headphones it works perfectly fine so I'm fairly certain the driver is doing what it's supposed to

Yep, driver for the IDT 92HD73C is working fine, just the mixer array is screwed-up .... (trying to get 5.1 surround sound in linux working hits the same small horrorshow trying to get the 5 channels appearing at the right audio port)

AFAIK the windows drivers initialize in similar fashion...ie; the codec driver loads first to enable the mixer, then the mixer params are applied ~ I have no idea where those params are stored in windows (a .inf file or registry entries) ; someone more savvy with windows may be able to steer you right here, as essentially it's just those params that need modifying.

HTH

Reply 2 of 5, by theamtrakvirus

User metadata
Rank Newbie
Rank
Newbie

Actually what you've said here is a lot more useful than you might think. I went into the other driver folders that wouldn't install and compared a few things to the one that did install and I notice there's a bunch of .ini files for various models of these chips. I wonder if taking one from the official Dell install that was provided for it for Vista and putting it in the IDT folder that's part of the actual install on this laptop might solve my problems. Guess there's one way to find out and if worst comes to worst safe mode is a thing for a reason.

Reply 3 of 5, by theamtrakvirus

User metadata
Rank Newbie
Rank
Newbie

Well, with some combination of drivers and ini files I did manage to get it to detect it as a laptop but it didn't change much otherwise, in fact something along the way broke more stuff as the game I've been testing on it started crashing after I did all that. Clearly that's at least part of the issue but there's more going on that's preventing it from working as intended.

Reply 4 of 5, by giantclam

User metadata
Rank Member
Rank
Member

Yeah, it'll be the mixer, for sure .... I've had fun getting audio to work in linux, on multiple laptop machines ~ I had a lenovo here once, that exhibited the same problem as you describe ...ie; works at headphone jack, not main speakers. For example here I'd reference something like https://temposemi.com/products/pclaptop-hd/ to find out what I'm up against. In the lenovo case, it was something goofy like the headphone jack sense logic was 'upside down' as it were -- change a 0 to a 1 and it works as expected. You likely stand the best chance, by rolling back to the drivers that only worked in headphones. From there, you know the codec itself is working, and it's just the audio output path that needs changing. The difference between laptop & desktop here, would be the lack of HD_AUDIO/AC97 font panel port (at a guess)...

...I could be wrong, but at a guess with the headphones working setup, it's not actually the driver perse ~ as mentioned, it's more than likely and installed .inf/.ini file or registry key, because coincidences don't happen =)

I just found this thread ~ https://forums.opensuse.org/t/no-sound-idt-hi … n-audio/70852/8 ...*my* gut feeling is it's the same thing -- headphone jack detection

HTH

Reply 5 of 5, by theamtrakvirus

User metadata
Rank Newbie
Rank
Newbie

More than likely that yes, it is the mixer screwing things up. I've now seen three different versions of the mixer in my quest of driver combining (I'm sure installing 10+ versions of a driver is doing wonders on Windows). What I find quite odd is the driver from SDI that gets it to work at all is a Gateway driver apparently. None of the Dell drivers get it working. Even the official driver which I hadn't tried since it was for 64 bit Vista (unsurprisingly) didn't work at first. However once I get the Gateway one installed that gets the audio service running 'good enough'(?) for it to allow me to install one of the Dell drivers. I really need to pin down which one it is so I don't lose track in the 7 or 8 I've tried. Now I just gotta figure out how to translate that Linux fix into Windows..