no I don't think perarch had anything to do with it. I think you have a different problem than the one I created this bug for. Anyway I forgot one more command. When you do get the chance also run
sudo dmseg > dmesg.txt
but make sure you are booted from your custom compiled kernel when you run that command.
no I don't think perarch had anything to do with it. I think you have a different problem than the one I created this bug for. Anyway I forgot one more command. When you do get the chance also run
sudo dmseg > dmesg.txt
but make sure you are booted from your custom compiled kernel when you run that command.