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 0000: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 the time. Also, when I looked at the wifi definition it said the wifi was last used 3 hours ago, but it has been over 9 hours since I shutdown my pc and that was from Windows, so where is networkmanager (assuming Fedora is still using networkmanager) getting its information from? I am using KDE for my desktop.
regards, Steve
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 0000: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 the time. Also, when I looked at the wifi definition it said the wifi was last used 3 hours ago, but it has been over 9 hours since I shutdown my pc and that was from Windows, so where is networkmanager (assuming Fedora is still using networkmanager) getting its information from? I am using KDE for my desktop.
The wifi device was working for a while (last used on 29/6/2022) but I think it stopped working after putting on a bunch of update packages, and further updates have not resolved the issue. Nmcli doesn't seem to be able to see a wifi device but lspci can see the Wifi 6 AX200 controller.
regards, Steve
users mailing list --users@lists.fedoraproject.org To unsubscribe send an email tousers-leave@lists.fedoraproject.org Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure
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 0000: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 the time. Also, when I looked at the wifi definition it said the wifi was last used 3 hours ago, but it has been over 9 hours since I shutdown my pc and that was from Windows, so where is networkmanager (assuming Fedora is still using networkmanager) getting its information from? I am using KDE for my desktop.
The wifi device was working for a while (last used on 29/6/2022) but I think it stopped working after putting on a bunch of update packages, and further updates have not resolved the issue. Nmcli doesn't seem to be able to see a wifi device but lspci can see the Wifi 6 AX200 controller.
Looking in dmesg, iwlwifi doesn't seem to be loading the firmware for the AX200. Looking at /lib/firmware there are a whole bunch of iwlwifi- files but none of them appear to be for the AX200. The iwlax2xx-firmware package is installed but it doesn't install any files in /lib/firmware and seems to be for an Asterisk. Given that the wifi was working for a while and loading firmware, how do I determine where the firmware has gone?
regards, Steve
regards, Steve
users mailing list --users@lists.fedoraproject.org To unsubscribe send an email tousers-leave@lists.fedoraproject.org Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure
users mailing list --users@lists.fedoraproject.org To unsubscribe send an email tousers-leave@lists.fedoraproject.org Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure
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 0000:05:00.0 failed with error -110
Were there any other messages around that? Without any other context, that looks like a hardware error.
The wifi device was working for a while (last used on 29/6/2022) but I think it stopped working after putting on a bunch of update packages, and further updates have not resolved the issue. Nmcli doesn't seem to be able to see a wifi device but lspci can see the Wifi 6 AX200 controller.
nmcli will only see it if the module successfully initializes the hardware.
Looking in dmesg, iwlwifi doesn't seem to be loading the firmware for the AX200. Looking at /lib/firmware there are a whole bunch of iwlwifi- files but none of them appear to be for the AX200. The iwlax2xx-firmware package is installed but it doesn't install any files in /lib/firmware and seems to be for an Asterisk. Given that the wifi was working for a while and loading firmware, how do I determine where the firmware has gone?
I don't know how you're seeing a connection to Asterisk, but it certainly installs a *lot* of files into /usr/lib/firmware (108 of them).
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 message:
iwlwifi: probe of 0000:05:00.0 failed with error -110
Were there any other messages around that? Without any other context, that looks like a hardware error.
The wifi device was working for a while (last used on 29/6/2022) but I think it stopped working after putting on a bunch of update packages, and further updates have not resolved the issue. Nmcli doesn't seem to be able to see a wifi device but lspci can see the Wifi 6 AX200 controller.
nmcli will only see it if the module successfully initializes the hardware.
Looking in dmesg, iwlwifi doesn't seem to be loading the firmware for the AX200. Looking at /lib/firmware there are a whole bunch of iwlwifi- files but none of them appear to be for the AX200. The iwlax2xx-firmware package is installed but it doesn't install any files in /lib/firmware and seems to be for an Asterisk. Given that the wifi was working for a while and loading firmware, how do I determine where the firmware has gone?
I don't know how you're seeing a connection to Asterisk, but it certainly installs a *lot* of files into /usr/lib/firmware (108 of them).
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. But whatever the issue was wifi is now working and dmesg is showing the same messages as it did on 29/6/2022, which is a bit disconcerting as potentially it now seems that wifi support is only randomly working?
regards, Steve
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
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.
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.
Thanks Tim, I'll check that out.
I've booted directly into Fedora this morning and the wifi is not working again, its back to the situation of getting probe error -110 without ever trying to load the adapter's firmware. I've seen another thread on the net where someone else was raising an issue with the same wifi adapter with Fedora 34, where that person was saying it seemed to work if he booted into Windows first, and it's now looking like I'm getting the same issue. I'm assuming this is a kernel issue, so what is the linux kernel not doing that windows does do to activate the hardware (its not an issue specific to Fedora as I get the same lack of wifi issue under Ubuntu as well)?
regards, Steve
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/modprobe.d/iwlwifi.conf with content
options iwlwifi remove_when_gone=1
as some of these issues are suspend/resume issues where it does not get init'ed right on resume.
On Tue, Jul 5, 2022 at 5:39 PM Stephen Morris samorris@netspace.net.au wrote:
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.
Thanks Tim, I'll check that out.
I've booted directly into Fedora this morning and the wifi is not working again, its back to the situation of getting probe error -110 without ever trying to load the adapter's firmware. I've seen another thread on the net where someone else was raising an issue with the same wifi adapter with Fedora 34, where that person was saying it seemed to work if he booted into Windows first, and it's now looking like I'm getting the same issue. I'm assuming this is a kernel issue, so what is the linux kernel not doing that windows does do to activate the hardware (its not an issue specific to Fedora as I get the same lack of wifi issue under Ubuntu as well)?
regards, Steve
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
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 this:
Please create the file /etc/modprobe.d/iwlwifi.conf with content
options iwlwifi remove_when_gone=1
as some of these issues are suspend/resume issues where it does not get init'ed right on resume.
In my case its not as suspend/resume process. I get this issue on a cold start of the machine where I boot into directly into Fedora/Ubuntu and the wifi device is not activated. If I boot into Windows and run Windows for a while then warm boot from Windows into Fedora the wifi device is available and wifi activates. What I've seen on the net is someone else raising the same issues with Fedora 34 and the same wifi device, but the support people the person was reporting the issue to said they couldn't help him because at the time Fedora 34 was out of life. I'll try the iwlwifi.conf method and see if it makes any difference.
regards, Steve
On Tue, Jul 5, 2022 at 5:39 PM Stephen Morris samorris@netspace.net.au wrote:
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.
Thanks Tim, I'll check that out.
I've booted directly into Fedora this morning and the wifi is not working again, its back to the situation of getting probe error -110 without ever trying to load the adapter's firmware. I've seen another thread on the net where someone else was raising an issue with the same wifi adapter with Fedora 34, where that person was saying it seemed to work if he booted into Windows first, and it's now looking like I'm getting the same issue. I'm assuming this is a kernel issue, so what is the linux kernel not doing that windows does do to activate the hardware (its not an issue specific to Fedora as I get the same lack of wifi issue under Ubuntu as well)?
regards, Steve
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
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/resume then try below:
Other notes indicate this:
Please create the file /etc/modprobe.d/iwlwifi.conf with content
options iwlwifi remove_when_gone=1
as some of these issues are suspend/resume issues where it does not get init'ed right on resume.
In my case its not as suspend/resume process. I get this issue on a cold start of the machine where I boot into directly into Fedora/Ubuntu and the wifi device is not activated. If I boot into Windows and run Windows for a while then warm boot from Windows into Fedora the wifi device is available and wifi activates. What I've seen on the net is someone else raising the same issues with Fedora 34 and the same wifi device, but the support people the person was reporting the issue to said they couldn't help him because at the time Fedora 34 was out of life. I'll try the iwlwifi.conf method and see if it makes any difference.
I put the specified command into iwlwifi.conf and it makes not difference, the wifi is not available on booting directly into linux. Just one further question , if connected to ethernet how do you try switching to wifi if networkmanager doesn't show any of the wifi ssid's so that you can try connecting to them?
regards, Steve
regards, Steve
On Tue, Jul 5, 2022 at 5:39 PM Stephen Morris samorris@netspace.net.au wrote:
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.
Thanks Tim, I'll check that out.
I've booted directly into Fedora this morning and the wifi is not working again, its back to the situation of getting probe error -110 without ever trying to load the adapter's firmware. I've seen another thread on the net where someone else was raising an issue with the same wifi adapter with Fedora 34, where that person was saying it seemed to work if he booted into Windows first, and it's now looking like I'm getting the same issue. I'm assuming this is a kernel issue, so what is the linux kernel not doing that windows does do to activate the hardware (its not an issue specific to Fedora as I get the same lack of wifi issue under Ubuntu as well)?
regards, Steve
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
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 it.
If the issue is after a suspend/resume then try below:
Other notes indicate this:
Please create the file /etc/modprobe.d/iwlwifi.conf with content
options iwlwifi remove_when_gone=1
as some of these issues are suspend/resume issues where it does not get init'ed right on resume.
In my case its not as suspend/resume process. I get this issue on a cold start of the machine where I boot into directly into Fedora/Ubuntu and the wifi device is not activated. If I boot into Windows and run Windows for a while then warm boot from Windows into Fedora the wifi device is available and wifi activates. What I've seen on the net is someone else raising the same issues with Fedora 34 and the same wifi device, but the support people the person was reporting the issue to said they couldn't help him because at the time Fedora 34 was out of life. I'll try the iwlwifi.conf method and see if it makes any difference.
I put the specified command into iwlwifi.conf and it makes not difference, the wifi is not available on booting directly into linux. Just one further question , if connected to ethernet how do you try switching to wifi if networkmanager doesn't show any of the wifi ssid's so that you can try connecting to them?
regards, Steve
I have found an article on the net that has resolved the issue with the wifi device not being available in Linux if I don't boot into Windows first. The article specified that "Fast Boot" needs to be disabled in the bios, I already had it disabled because of its functionality (if active it requires a Windows utility to cause the next boot to boot into the bios, which as far as I am aware is not available for Linux), and more importantly, "Fast Boot" must be disabled in Windows as well. Thankyou to everyone who provided assistance with this issue.
regards, Steve
regards, Steve
On Tue, Jul 5, 2022 at 5:39 PM Stephen Morris samorris@netspace.net.au wrote:
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.
Thanks Tim, I'll check that out.
I've booted directly into Fedora this morning and the wifi is not working again, its back to the situation of getting probe error -110 without ever trying to load the adapter's firmware. I've seen another thread on the net where someone else was raising an issue with the same wifi adapter with Fedora 34, where that person was saying it seemed to work if he booted into Windows first, and it's now looking like I'm getting the same issue. I'm assuming this is a kernel issue, so what is the linux kernel not doing that windows does do to activate the hardware (its not an issue specific to Fedora as I get the same lack of wifi issue under Ubuntu as well)?
regards, Steve
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
users@lists.stg.fedoraproject.org