@John Hoff > Mike, depending on your answers to my many questions from today, if the only way we know to proceed is to build and test a patch, could you help with building the patch (or at least the basic framework of the patch so I can just plug in the CORB values)?
Absolutely. I'll write a patch and test it on my machine, after which I'll share it with you. In the mean time you could try Early Patching. Your Early Patching file will have an enormous [verb] section which will look like this [verb] 0x1a 0x707 0xc5 . . . Each line contains three space-separated hex values: Node ID, Verb ID, and Payload. You will have one line for each verb in the CORB dump, so that could be 1000s of lines. I think hda-verb < Early Patching < kernel patch, in the sense that a kernel patch has the highest-probability of success, hda-verb has the lowest, and Early Patching is somewhere in between. This is because I think that some codec values are read-write at initialization time but then become read-only at runtime (only Realtek, the ALC298 manufacturer, knows for sure*). A kernel patch allows us to write values at codec initialization time, whereas hda-verb is at runtime, and Early Patching is somewhere in between. *Perhaps we can know: I found a datasheet for the ALC269 [1]. I think the ALC269 is very similar to the ALC298 codec in our laptops. Among other things, the datasheet describes verb semantics. It's a nice supplement to the Intel HDA spec. I don't recall seeing anything about initialization-time vs runtime, but perhaps I have not read it closely enough - the datasheet is only somewhat less dense and technical than the Intel HDA spec so it's not an easy read! :) [1] https://www.hardwaresecrets.com/datasheets/alc269.pdf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851518/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
