05-16-2025, 05:32 AM
Thank you for the information.
Yes, we are now looking at the kernel and driver so different commands are needed. I wasn't expecting you to have records of these commands from before, but it is interesting that they are familiar to you.
It looks like you've fully installed LL6 to get the data.
This was one of the workarounds suggested.
If you are running LL6.x and everything is working and you are happy with it we can stop here.
If you want to continue with LL7, there are no guarantees of progress. As before, the best bet of fixing the LL7 setup is re-finding the commands you used earlier to get it working.
Getting the kernel and driver versions from the LL7 set up is preliminary information gathering which may help the search/bug reporting process. You can get the kernel/driver version information by booting a Live Media boot of LL7.x, confirming it does not work and then running the commands.
Yes, we are now looking at the kernel and driver so different commands are needed. I wasn't expecting you to have records of these commands from before, but it is interesting that they are familiar to you.
It looks like you've fully installed LL6 to get the data.
This was one of the workarounds suggested.
If you are running LL6.x and everything is working and you are happy with it we can stop here.
If you want to continue with LL7, there are no guarantees of progress. As before, the best bet of fixing the LL7 setup is re-finding the commands you used earlier to get it working.
Getting the kernel and driver versions from the LL7 set up is preliminary information gathering which may help the search/bug reporting process. You can get the kernel/driver version information by booting a Live Media boot of LL7.x, confirming it does not work and then running the commands.
stevef
clueless
clueless