On 20/7/22 09:46, Stephen Morris wrote:
On 9/7/22 23:29, Stephen Morris wrote:
On 6/7/22 09:23, Roger Heflin wrote:
Error -110 is timeout, meaning the device did not respond to the
commands.
It usually means the hardware in question is in a bad/locked up state
so the kernel is unable to init
On 9/7/22 23:29, Stephen Morris wrote:
On 6/7/22 09:23, Roger Heflin wrote:
Error -110 is timeout, meaning the device did not respond to the
commands.
It usually means the hardware in question is in a bad/locked up state
so the kernel is unable to init it.
If the issue is after a suspend/resu
On 6/7/22 09:23, Roger Heflin wrote:
Error -110 is timeout, meaning the device did not respond to the commands.
It usually means the hardware in question is in a bad/locked up state
so the kernel is unable to init it.
If the issue is after a suspend/resume then try below:
Other notes indicate
Error -110 is timeout, meaning the device did not respond to the commands.
It usually means the hardware in question is in a bad/locked up state
so the kernel is unable to init it.
If the issue is after a suspend/resume then try below:
Other notes indicate this:
Please create the file /etc/modp
On 4/7/22 22:42, Tim via users wrote:
On Mon, 2022-07-04 at 18:15 +1000, Stephen Morris wrote:
The package must have been updated as when I looked yesterday it
didn't supply any of those files, unless I looked at the file list
from the wrong package
dnf history
See what got updated when.
Tha
On Mon, 2022-07-04 at 18:15 +1000, Stephen Morris wrote:
> The package must have been updated as when I looked yesterday it
> didn't supply any of those files, unless I looked at the file list
> from the wrong package
dnf history
See what got updated when.
--
uname -rsvp
Linux 3.10.0-1160.71.
On 4/7/22 12:13, Samuel Sieb wrote:
On 7/3/22 03:12, Stephen Morris wrote:
On 3/7/22 19:05, Stephen Morris wrote:
On 30/6/22 09:08, Stephen Morris wrote:
Hi,
I booted into Fedora this morning and had no network available
because wifi had not been started. Dmesg showed the following messag
On 7/3/22 03:12, Stephen Morris wrote:
On 3/7/22 19:05, Stephen Morris wrote:
On 30/6/22 09:08, Stephen Morris wrote:
Hi,
I booted into Fedora this morning and had no network available
because wifi had not been started. Dmesg showed the following message:
iwlwifi: probe of :05:00.0 f
On 3/7/22 19:05, Stephen Morris wrote:
On 30/6/22 09:08, Stephen Morris wrote:
Hi,
I booted into Fedora this morning and had no network available
because wifi had not been started. Dmesg showed the following message:
iwlwifi: probe of :05:00.0 failed with error -110
There is not
On 30/6/22 09:08, Stephen Morris wrote:
Hi,
I booted into Fedora this morning and had no network available
because wifi had not been started. Dmesg showed the following message:
iwlwifi: probe of :05:00.0 failed with error -110
There is not an issue with the wifi router as my wife
Hi,
I booted into Fedora this morning and had no network available
because wifi had not been started. Dmesg showed the following message:
iwlwifi: probe of :05:00.0 failed with error -110
There is not an issue with the wifi router as my wife was using the
internet on her laptop at
11 matches
Mail list logo
