The server in both cases is the same hardware configuration. It employs:
Processor: AMD Athlon 64x1 Dual Processor 4200+ x 2
Graphics: GeForce 440/PC1e/SSE2
Bus ID PCI:4:0:0
PCI Device ID 0x0de0
PCI Vendor ID 0x10de
lspci -v correctly identifies the nvidia kernel driver, and the audio device as the nVidia GF108 High Def Audio Controller.
Working through ala-info.txt, the reports for each system are identical up to the HDA-Intel Codec Information header except for the kernel version, of course, and the following:
f16 shows a sound related modprobe: snd-hda-intel: enable_msi=0 probe_mask=0x108. Under the following 'Loaded sound module options' header, enable_msi : 0 is within the listing fo rmodule snd-hda-intel.
f17 does not show the modprobe of snd-hda-intel at all, although the module is shown under loaded. However, enable_msi is set to -1. Further, there is no sound.config file found anywhere in this system.
Under the 'HDA-Intel Codec information' header,
f16 identifies the codec: Nvidia GPU 14 HDMI/DP at address 3 and the alsa device nodes have been set up for address 3. That has always worked, and is the sole sound card in the server.
But
f17 does not see the world in this way at all. It sets up the configuration for addresses 0, 1 and 2 as well as 3. The codec detail for address3 is identical to that of f16
Reviewing the ALSA/HDA dmesg file:
In
f16 we find: microcode: AMD CPU family 0xf not supported; hda_intel: codec_mask forced to 0x8. That makes sense, because those settings were establised by modprobe earlier.
For
f17: we read (Note that use of the override may cause unknown side effects.); hda_intel: Disabling MSI
So, msi comes back to bite me again.
Since the hardware is unchanged, I have to assume the kernel upgrade affects this or there is a change in the level of hardware support between the 2 configurations.
At this stage in the cycle, I don't hold out any hope that f17 final will be of any help but I'm hoping somebody out there might have a path to a solution for us here.
GJW
Linear Mode
