vik, to clarify your comment:
>"The issue disappeared for a while, but has returned in the past month or so; I'm guess a kernel driver update fixed it, then regressed."
Could you please advise after which update specifically did this issue start happening with?
vik, to clarify your comment:
>"The issue disappeared for a while, but has returned in the past month or so; I'm guess a kernel driver update fixed it, then regressed."
Could you please advise after which update specifically did this issue start happening with?