Thanks we will do some investigation and post back a result.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2022-01-04
Yes, thank You. It might have been an issue with the "SMC" down in the boot sectors, a second security boot in one of the latest Lenovo PC:s, as You should administer during booting from the installation media. I have now closed it and everything going smooth now.
Thank You!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, I have the same problem with a dual boot windows / Q4OS on an Asus PC (T110). I am new to linux, and I do not understand the answer. What should I do?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I found the solution to my problem in the connection configuration: my wifi terminal appeared twice with the same name, one of which was marked "never used". I deleted it and discover has been working normally ever since.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Here are the screenshoot.
Thanks we will do some investigation and post back a result.
Yes, thank You. It might have been an issue with the "SMC" down in the boot sectors, a second security boot in one of the latest Lenovo PC:s, as You should administer during booting from the installation media. I have now closed it and everything going smooth now.
Thank You!
So, should we close this report?
Hello, I have the same problem with a dual boot windows / Q4OS on an Asus PC (T110). I am new to linux, and I do not understand the answer. What should I do?
@Thierry Berger
Please run commands in terminal:
$ ping -c4 google.com
$ ping -c4 8.8.8.8
and post back the terminal output.
I found the solution to my problem in the connection configuration: my wifi terminal appeared twice with the same name, one of which was marked "never used". I deleted it and discover has been working normally ever since.
Closing the report.