I see you're using kernel 6.2 now, but previously had kernel 6.5. So it looks like the issue is bug 2028165 and you should stick to kernel 6.2 to avoid that problem. Did I miss anything?
I see you're using kernel 6.2 now, but previously had kernel 6.5. So it looks like the issue is bug 2028165 and you should stick to kernel 6.2 to avoid that problem. Did I miss anything?