Michael wrote: > On Sunday, 14 July 2024 10:44:30 BST Dale wrote: >> Well, this was about codec support. It seems I had none of them >> available. I likely enabled more than needed but if it isn't needed, it >> just ignores them, so I've read anyway. This is a sort list. >> >> [*] Support initialization patch loading for HD-audio >> <*> Build Realtek HD-audio codec support >> <*> Build Analog Devices HD-audio codec support >> <*> Build IDT/Sigmatel HD-audio codec support >> <*> Build VIA HD-audio codec support >> <*> Build HDMI/DisplayPort HD-audio codec support >> <*> Build Cirrus Logic codec support >> < > Build Cirrus Logic HDA bridge support >> <*> Build Conexant HD-audio codec support >> <*> Build Creative CA0110-IBG codec support >> <*> Build Creative CA0132 codec support >> <*> Build C-Media HD-audio codec support >> <*> Build Silicon Labs 3054 HD-modem codec support >> >> >> With those and a few others, it works. I suspect the Realtek is the one >> needed but it may need the HDMI one as well. I just set the same as on >> my main rig. It works. It seems the card itself had the right driver, >> just not the bit that tells the card how to process the sound. > You can build them as modules, see which of these are loaded successfully and > disable the rest. Some are generic, e.g. > > "Build HDMI/DisplayPort HD-audio codec support" > > Say Y or M here to include HDMI and DisplayPort HD-audio codec support in snd- > hda-intel driver. This includes all AMD/ATI, Intel and Nvidia > HDMI/DisplayPort > codecs. > > Others are more specific to individual OEM chips, like e.g. Realtek with its > proprietary audio converter driver. >
That's true but I wasn't sure which ones I had to have so I just enabled them all. I figured if it worked on my main rig, it would work on the new rig since the audio part is almost identical. That would save me the trouble of trying to load and remove modules until I figured out which ones it needed and which ones it didn't. Basically, it was faster this way. >> It's getting close. Any day now. It has been a adventure. That pesky >> LG monitor or that HDMI cable caused some issues tho. I'm looking to >> buy either 4K or 8K cables next. Be ready for the future. ;-) > I think the future is DP rather than HDMI, which works with AMD's FreeSync > and > Nvidia's G-Sync, assuming both card and monitor support this. You can also > chainload monitors from a single DP connection. However, cable bandwidth and > functionality requirements are dictated by the specification of the devices > you connect to your card. A 16K capable DP 2.1, or a 10K capable HDMI 2.1b > won't make any difference when you're connecting 1920x1080 (i.e. sub-2K) > display panels. I don't buy cables often, so I tend to buy the highest > specification available at the time to future proof, as the monitors and TVs > are increasingly made available at higher resolutions and refresh rates. I think you right. One reason I was able to get the monitor as cheap as I did, it is considered old tech now. Things are moving toward 4k and such. I was looking at the 4K cables but then ran up on a cable that is braided. Those braided things are tough. I'd be more worried about wearing out the connector than damaging the cable. I could only find the braided ones in the 8K version. Still, future proof for me for a long time to come. I might get 4k monitor and card the next go around. I suspect 8K will be a ways off. One thing I want to do, replace that cable that would not work with the new monitor and was used on the LG monitor when we was arguing with it. Something funny about that cable. It's amazing how much technology changes tho. What gets me, some things are a lot faster or bigger but cost is not all that bad given the improvement. I still think CPUs are a bit pricey tho. I put out 8 Hickory trees this morning. I also picked my poor sis-n-law some tomatoes. I also gave some to a neighbor. Also making two jars of pepper sauce today. I hear my pillow calling me pretty good. Battery draining pretty fast. o_- Dale :-) :-)
