Hi Marco
Having said that I don't think this is the *general* case with the ALC268 because as I have mentioned a user has reported success with the ALC268 under Linux and a recent hg snapshot with both the "test" and "auto" models.
Strange.
Not really. There's very strong evidence that the silicon may be different and this sort of thing occurs from time to time. While you may have an actual ALC-268 chip on your mainboard, someone else may have an ALC268 core integrated into some other chip vendor's jungle chip. The other issue is that different vendors choose to integrate the codec chips in different ways - different pin-to-jack mappings, use of GPIOs etc etc. With this sort of thing going on it's really no surprise to me that one ALC268-based system works while another does not.
I have uploaded the driver to http://rapidshare.com/files/89478591/ALC268_Compal.rar (but I left out the Vista stuff). Do you think it's possible to find out _what_ makes the problem with this?
I've had a quick look at the contents and nothing jumps out at me. Others with more experience with the windoze driver structure and knowledge of how various files are used may have more success.
My past experience has shown that in cases like this the best approach is to poke at the hardware until you find something that works. Admittedly that's becoming less feasible as time goes on and the hardware gets more complex and the fragility of hardware increases the likelihood of permanent damage.
Regards jonathan