Hi Chris, On Fri, Apr 30, 2021 at 07:37:10PM -0400, Chris McCrae wrote: > Long time stalker, first time caller, so go easy please :-) (I've > already learned I need to use plain text mode ... what's next?) > > Recently acquired an Asus PN62S (Intel) as a media centre frontend > (currently testing with Xubuntu 20.04 and a 5.10 kernel, and the most > current BIOS available). Having an integrated IR was part of the > selling features. However, getting it to be recognized by my system > has become a challenge that I am getting obsessed with. There's very > little to find online on this device that is current, but there has > been some recent conversation on this list about the same device, on a > related machine, the PN50 (AMD). I'm hoping that the knowledge here > may lead to a solution for my issue. > > I can provide more detail on request, but at the moment I am focusing > on the DSDT as a possible suspect. I do not have the 16 byte issue > that the PN50 experiences. Mine is defined as 8 bytes, which is > compatible with the ite-cir driver. My issue is that there appears to > be no attempt to bind the device to the driver (but it is visible in > lsmod)... no messages about the driver in dmesg at all. My thought is > that the definition of the device in DSDT may somehow give it enough > information (ITE8708) to know the driver could be needed, but not the > correct information to make it work. > > An earlier message provided only part of the device definition in DSDT > for the PN50. I would like to be able to see the full definition for > it from the PN50, to see if anything is significantly different. > Ideally, if I had the full DSDT as a starting point, I could compare > other areas such as motherboard resources. It would be great if we could see the entries for the IR device in your DSDT. There is a guide here https://wiki.archlinux.org/title/DSDT on how to do that. Thanks Sean
